Differences

This shows you the differences between two versions of the page.

--- packet:xrouter:mqtt-iface [2024/02/17 02:58] – g8pzt
+++ packet:xrouter:mqtt-iface [2025/02/22 02:31] (current) – g8pzt
@@ Line 1: / Line 1: @@
 ====== XRouter Tour - MQTT API ======
+[[packet:xrouter:tour|Back to Tour Index Page]]
 XRouter includes an MQTT client and an MQTT broker, both of which could be used for providing future Sysop and/or user interfaces. A proof of concept has been done, but it needs someone with vision and creativity to develop this further.
@@ Line 7: / Line 9: @@
 The point of this is to decouple the data from its presentation, allowing yet-to-be-written applications to obtain, format and present data in whatever form they wish.
-Using MQTT, you can inject and/or extract data at each ISO layer, and receive event notifications. This can be done via XRouter's own broker, or the client can send the data to an external broker. For the proof of concept experiments, XRouter pushed the data to a public broker, and the user interface was in another country.
+Using MQTT, you can inject and/or extract data at each ISO layer, and receive event notifications. This can be done via XRouter's own broker, or the client can send the data to an external broker. For the proof of concept experiments, XRouter pushed the data to a public broker, and the user interface was in another country. This is the browser-based chat section of that demo, written by Mitch AB4MW...
+{{xrwebchat.png}}
 Want to see the raw KISS data from one of XRouter's interfaces? No problem, just subscribe to "xrouter/kiss/{nodecall}/rcvd/{ifacenum}". Want to send a chat message? Simply send it to the topic "xrouter/put/{nodecall}/chat". Want to get a nodes list? Use the topic "xrouter/get/{nodecall}/nodes".
@@ Line 15: / Line 19: @@
 **Next:** [[ packet:xrouter:telnet-interfaces | Telnet Interfaces]]
+[[packet:xrouter:tour|Back to Tour Index Page]]