![]() Sender and payload fields are required for a valid envelope. Looking at the MQTT traffic with a program like mosquitto_sub will tell you it's working, but you won't get much useful information out of it. !12345678 is the address of the gateway device.The device will uplink and downlink raw ( protobuf) packets to the msh/ prefix: ![]() This includes messages and position information. IMPORTANT: When MQTT is turned on, you are potentially broadcasting your entire mesh traffic onto the public internet. If you use a custom MQTT broker (ie set mqtt_server), the mqtt_encryption_enabled setting applies, which by default is false. If you use the default meshtastic MQTT server, packets are always encrypted. All packets are sent to the broker, whether they originate from another device on the mesh, or the gateway node itself. In addition, some packet types are serialized or deserialized from/to JSON messages for easier use in consumers. When MQTT enabled, the Meshtastic device simply uplinks and/or downlinks every raw protobuf packet that it sees to the MQTT broker. Using or emitting packets directly in/from smart home control software such as Home Assistant or other consumers that can work with JSON messages.eg plotting temperature readings in Grafana, or device positions in Traccar. Using a custom MQTT broker and a translator program to decode the raw protobuf packets and translate them into a plain text form for use in other systems.Using a custom MQTT broker to bridge several mesh networks together, via the internet (or just a local IP network).This makes your devices appear on the world map, and provides a limited copy of your mesh traffic, translated into JSON. Connecting your mesh to the official Meshtastic MQTT broker.Meshtastic devices with wifi hardware (ESP32) are able to connect to an MQTT broker to uplink and downlink mesh packets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |