Connected, but not responding to Variable inquiries

[RWB]

I am seeing the same weird issue.

If you manually reset one of the non responsive Xenons does it start working as expected?

I’m avoiding having to manually reset by having the Boron call a function on the Xenons to trigger a System.reset() which causes the Xenon to reset and then it reconnects and starts working again.

Here is the code I use to remotely rest the Xenons:

Electron vs. Boron – “living on the edge” – what has changed with the cellular connection?

Make sure you put the code below on the Borons and Xenons so you will be able to reset the Xenons out in the field should they stop responding to Borons request. It’s helping bring Xenons back online after a reset or firmware flash of the Boron during my testing. I put this on the Boron int handleReset(String command) { Mesh.publish("reset", "ok"); return 1; } void setup() { Particle.function("reset", handleReset); } and this on the Xenons void handleNeedReset(const char *event, …

It’s weird cause the Xenons respond to the Borons function call over Mesh but it does not respond to other incoming mesh request for some reason.

I can force this to happen most of the time by hitting the reset on the Boron and once it’s back online and the Xenons reconnect and breath Cyan they do not respond to Mesh Publishes but will respond to a Mesh function call.

Can you test if after resetting the Argon via the reset pin if the Xenons stop responding unless manually reset most of the time?

I’m using the most recent 0.9 firmware.

@will @Joe This is the kind of behavior I was trying to explain yesterday.