So I have a mesh of 3 Xenons and an Argon in very close proximity. The Argon subscribes to MQTT and the message content is a colour, it then propagates this colour value around the 3 Xenons using a mesh publish/ subscribe from each and then back to the Argon. The LEDs change accordingly. This is then published onto MQTT as a different colour and so the loop should continue endlessly. In practice I get around 300ms as a loop time so that’s OK’ish. However this loop only runs for about 60 seconds before a subscribe is missed. So it looks like some form of delivery confirmation (ACK) may be required… or I hope this improves in the next release. The missed publish message doesn’t seem to be ‘detectable’ as such, more akin to UDP. It’s not a dependable delivery.
Some observations… The lack of pulsing cyan or flashing green is no indicator that a mesh doesn’t exist. Pulsing cyan doesn’t guarantee cloud connectivity. The cloud is significantly confused by which devices are available at any time. Very unreliable indications of mesh status. Frequent non recovery requiring router power cycle (and occasional repeater power cycle) to recover.