After looking at the flood of packets more closely, it turns out it was a combination of factors: a faulty IR sensor in the lock caused rapid flipping of the sensor's state, and the flood control timeout was set to 0...

Yeah, the debug trace shows that the node had an ID of 0. How can this happen (since the node has been functioning well for months before)?

I flashed the EEPROM and reinstalled the sketch, after which I was able to include it with a valid node ID.

I have deleted the device from the Vera UI and re-included it. This time I got a new on/off switch device in Ver with an ID of 0;0. Toggling the switch in Vera doesn't affect the node, but using the pushbutton on the node will sometimes update the switch in the Vera UI. And the node still reacts to commands sent to other nodes.

At this stage, would it make sense to clear the node's EEPROM and start over?

No duplicates: the Arduino nodes have IDs ("altid" in the Vera UI) of 1;255, 4;255 and 5;255, the corresponding On/Off switches show 1;0, 4;0 and 5;0.

Interestingly the faulty node shows a "chip" icon whereas all the working nodes display a generic Z-wave icon (the other nodes are configured as repeaters though, that's the only difference)

I have a MySensors network using a Vera controller. I recently upgraded the Vera to UI7 which may be related; I'm not sure at which time my troubles started. My MySensors gateway and devices are on v1.4.1 of the library.

Up till recently everything worked fine, and most devices continue to work fine. I have one node that no longer works correctly. This node is 1 of 3 devices that share the same sketch, exposing a single on/off function. If I operate the switch in the Vera UI, the node does not respond, but I can see the transmission light blink on the MySensors gateway (no error light). The node has a transmission and error light as well, and manually operating the node (they have a pushbutton for that) results in a green light but no change on the Vera UI.

The strange thing is: this node will sometimes react to commands sent to the other 2 nodes that have the same sketch: turning one of those other 2 nodes on or off will result in the faulty node turning on / off as well.

Anything I can do to further debug this, or is there a way to exclude and re-include this node into the network?

After looking at the flood of packets more closely, it turns out it was a combination of factors: a faulty IR sensor in the lock caused rapid flipping of the sensor's state, and the flood control timeout was set to 0...

I have a MySensor network with 4 nodes (3 window openers and 1 node to monitor a doorlock, rain, and temperature), using an Ethernet Arduino as a gateway, and the MySensors plugin on a Vera (UI5). This setup has worked flawlessly for about 6 months. No downtime, no resets required, no transmission or range issues, and instant response.

This week, one of the nodes stopped responding. As it turns out, that Arduino had somehow forgotten its sketch, and reverted to the default sketch (blinking light). I reloaded the correct sketch into the node, and after that it was working again. The node appears to have retained its settings, and no re-inclusion into the MS network was necessary.

Soon after that, everything stopped working correctly. Symptoms:

• Nodes no longer responding to commands from Vera.
• Vera no longer receiving temperature and status updates.
• Resetting the Gateway and Vera seems to fix things for a short while. Soon after a reset, the nodes will respond only intermittently and/or after a delay.
• After a reset, the Rcv led on the Gateway will sometimes blink for minutes on end. When reading the serial port I can see hundreds of packets coming in. During this flood, transmissions may or may not work.

All nodes and gateway running the 1.4 MS sketches.

It seems one node is responsible for the network flooding. It's the node with the rain sensor, having another node as parent. The sketch for that node already has flood control built in (rain sensors have a tendency to rapidly flip between states), and the Tx led on that node shows that the high level code is not actively making transmissions (not sure about the low level MS network libraries though). If I do make the node send an update (by opening / closing the lock for instance), the node shows a successful transmission.

Unplugging this node returns the rest of the network to a working state.

What could be causing this network flooding? As I've already established, there's nothing in my code that causes a multitude of packets to be sent. Could it be an issue with the mesh network? I've no idea how to diagnose the issue much less repair it.

I was wondering if it's possible to hook up the radio to different D pins of the Arduino and modify or configure the MySensor libraries accordingly? There are some nice LCD screens for Arduino out there but many use some D pins used by the radio module. The lazy solution would be to use 2 Arduinos, but better to have one.