theAgingApprentice / HexaFloorRide

Arduino based six legged robot project
MIT License
0 stars 0 forks source link

MQTT message format inconsistent #136

Open nerdoug opened 1 year ago

nerdoug commented 1 year ago

MQTT messages as seen in mosquitto have different layouts for the first couple of fields:

agingApprentice/HexaFloorRide94B97E5F48B8/health End-to-end network services estabished
agingApprentice/checkin HexaFloorRide94B97E5F48B8 has IP of 10.0.0.186
HexaFloorRide94B97E5F48B8/commands help
agingApprentice/HexaFloorRide94B97E5F48B8/help TEST - Issues test message to terminal.

In the new concise message format it looks like this:

aa/hfr48B8/health End-to-end network services estabished
aa/checkin hfr48B8 has IP of 10.0.0.186
hfr48B8/commands help
aa/hfr48B8/help TEST - Issues test message to terminal.

Not quite what the order should be, and if it's different for messages from robot vs. messages from MQTT.fx

theAgingApprentice commented 1 year ago

Lest revisit the MQTT topic tress structure and make sure we are happy with it. Then we can make all messages consistent. Somewhere we documented the current structure. Will look in Twipi project etc to see if we can find it.