After a power outage this weekend, when HASS came back up I lost all automations related to my Sonoff Orb 4-Way smart switch, and one of my GE 800 Z-Wave switches no longer responds, though it still works manually pressing the switch.
I’ve re-entered the automations, but I can’t get the switch so come back to home assistant. Is the only path forward deleting, resetting it, and re-adding it? I’ve never had this happen. I’m not 100% sure the power outage caused the issue. I updated the core this weekend also. I think that was before the outage, but I hadn’t checked to see if everything was there after the update/before the outage.
You must log in or # to comment.
Have you tried re-interviewing the devices as a first step?
I was looking for that. Your note jogged my memory and I was able to find it. Strangely, the device was saying that it was being interviewed. I’ve rebooted home assistant again. When I tried to reinterview, it fails immediately. I see the following in the log:
2026-04-07 20:58:16.157 CNTRLR [Node 009] Beginning interview - last completed stage: None 2026-04-07 20:58:16.158 CNTRLR [Node 009] new node, doing a full interview... 2026-04-07 20:58:16.159 CNTRLR » [Node 009] querying protocol info... 2026-04-07 20:58:16.159 DRIVER one or more queues busy 2026-04-07 20:58:16.160 DRIVER » [REQ] [GetNodeProtocolInfo] 2026-04-07 20:58:16.160 SERIAL » 0x010500410009b2 (7 bytes) 2026-04-07 20:58:16.163 SERIAL « [ACK] (0x06) 2026-04-07 20:58:16.165 SERIAL « 0x010a0141d39c0104100100ee (12 bytes) 2026-04-07 20:58:16.166 SERIAL » [ACK] (0x06) 2026-04-07 20:58:16.167 DRIVER « [RES] [GetNodeProtocolInfo] 2026-04-07 20:58:16.167 CNTRLR « [Node 009] received response for protocol info: basic device class: Routing End Node generic device class: Binary Switch specific device class: Binary Power Switch node type: End Node is always listening: true is frequent listening: false can route messages: true supports security: false supports beaming: true maximum data rate: 100000 kbps protocol version: 3 2026-04-07 20:58:16.168 CNTRLR [Node 009] Interview stage completed: ProtocolInfo 2026-04-07 20:58:16.169 CNTRLR » [Node 009] pinging the node... 2026-04-07 20:58:16.170 DRIVER » [Node 009] [REQ] [SendDataBridge] │ source node id: 1 │ transmit options: 0x01 │ callback id: 83 └─[NoOperationCC] 2026-04-07 20:58:16.170 SERIAL » 0x010f00a900010009010001000000005302 (17 bytes) 2026-04-07 20:58:16.175 SERIAL « [ACK] (0x06) 2026-04-07 20:58:16.178 SERIAL « 0x010401a90152 (6 bytes) 2026-04-07 20:58:16.179 SERIAL » [ACK] (0x06) 2026-04-07 20:58:16.180 DRIVER « [RES] [SendDataBridge] was sent: true 2026-04-07 20:58:16.234 SERIAL « 0x011d00a953010005007f7f7f7f7f00010100000000020300007f7f7f7f7f1d (31 bytes) 2026-04-07 20:58:16.235 SERIAL » [ACK] (0x06) 2026-04-07 20:58:16.236 DRIVER « [REQ] [SendDataBridge] callback id: 83 transmit status: NoAck, took 50 ms routing attempts: 3 protocol & route speed: Z-Wave, 40 kbit/s routing scheme: Direct TX channel no.: 1 2026-04-07 20:58:16.237 CNTRLR [Node 009] The node did not respond after 1 attempts, it is presumed dead 2026-04-07 20:58:16.238 CNTRLR [Node 009] The node is dead. 2026-04-07 20:58:16.240 CNTRLR [Node 009] ping failed: The node did not acknowledge the command (ZW0204) 2026-04-07 20:58:16.241 CNTRLR [Node 009] Interview attempt (1/5) failed, node is dead.Tried rebuilding routes to the node and saw similar node is not responding messages in the log. Strange that the physical switch still works though.
I’ve had occasional problems with z-wave devices that stop responding. The fix has required power cycling them at the breaker box, then re-interviewing and rebuilding routes. Hope that works in your case.