Was running 2.3.4.127 on a C7 hub with no (other than the occasional frustrating failure) significant problems. Had an Aeotec socket that had switched on. Upgraded to 2.3.4.129 and noticed socket would not switch off. Ran Z-Wave repair and node unreachable, however the events page show this device is regularly reporting back voltage and power usage. Ran second Z-Wave Repair and got multiple nodes failures including this one. Upgraded to 2.3.4.130 and no change. Reverted to 2.3.4.127 and have two nodes failed including this one. However, it is still reporting back. any ideas?
Shut down the hub from the settings menu. Unplug power to the hub (at the wall not the hub) for 2 minutes and power back up. That should fix you. (also .130 is now available)
1 Like
Though this is tempting, best practice says to stay away from a full repair, at least on the c7. It generates a ton of traffic and doesn't really help.
First line of defense for zwave issues affecting multiple nodes!
1 Like
Where do I find best practice?
Thanks. This has at least made the node controllable. However, it still say node unreachable when I do a Z-Wave repair.
What kind of device is this? Line powered or LSS/FLiRS?
1 Like
Generally speaking I get them from reading the forums. Not saying there aren't situations where a full repair won't help, but from what I've read it seems to be something folks don't do.
1 Like
is it a mains powered device or battery?
1 Like
Mains (it's an AEOTEC Socket).
1 Like
As long as it's controllable I wouldn't worry too much about it
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
