I have Ring Alarm (as secondary controller) joined my existing z-wave network. Everything (ring and non-ring devices) works fine, except one thing: Ring z-wave controller is keeping removing my battery powered (non-ring) devices.
By battery device I mean the non-FLiRS battery device (sleeping device)
To reproduce:
- Prepare a z-wave controller (with S2 support, I’m using z-way)
- Add ring alarm as a secondary controller (Z-Wave Protocol -> Learn Mode)
- Include a sleeping device to primary controller
- Wait several days (in my last case, 10 days)
- The sleeping device is disappeared from primary controller
From the zniffer, it looks exactly like running a “Remove Failed” on a battery device:
- Ring alarm sends multiple NOPs to the device with no ACK (of course, the device is sleeping)
- Ring alarm send a message to primary controller (Command Class 0x0D, parameter is the node id of the sleeping device)
- Primary controller logged that the sleeping device was removed
I suspect this is because ring alarm didn’t query the sleeping device and doesn’t know it’s sleeping. I would also guess that if I initiate the inclusion from Ring, it will probably query the node properly and get Wakeup CC Report.
But ideally, the ring alarm shouldn’t try to remove a node on its own (especially when joined as secondary).