Z-Wave Network issues after update to 12.8.0

Two days ago my Homey Pro (early 2023) started to have z-wave network issues. The Homey had updated to 12.8.0 at 4am that morning. Devices that had been in place for many months started to loose connection to the network and became erratic when I sent commands form the Homey App to them or had a flow run to toggle them off or on. I tried to reset a Enbrighten 700 Tamper Resistant Plug and a Zooz motion detector (both had been working great) but now when I try to add them with the homey super close, the inclusion process failed after I go thru the wizard to add them. I can trigger the inclusion through steps 1 and 2 on the app, but then the app says its adding the device and fails 10 seconds later saying it cannot connect to the device. This happened on the Zooz motion and Enbrighten plug.

I am at a loss of what to try - I really would hate to have to factory reset all the devices and reset the Homey. Anyone else have z-wave issues after the update?

As always after Homey firmware updates: try taking your Homey off power for a good 10 minutes.

Thanks for the reply. I have tried taking Homey down for at least 10 minutes. I turned of the power to the whole house. I removed the ZooZ device and factory reset it - not it will not connect back to the Homey at all. The Enbrighten plug got reset too and I placed the Homey about 3 feet away to try and connect. It did recongize when I tried to include it but it failed saying it lost connection to the device. It

When trying to control a device that says it is connected, I get an error like below:

2025-10-16T14:01:14.114Z
[ProcessSendData]: To node: 59 with data: 0x9f03e100ec9f159b125d0ce5cc25ef8909500f4f and txOptions: TRANSMIT_OPTION_ACK,TRANSMIT_OPTION_AUTO_ROUTE,TRANSMIT_OPTION_EXPLORE
2025-10-16T14:01:14.810Z
Node[59]: [COMMAND_CLASS_SWITCH_BINARY] {“Current Value (Raw)”:{“type”:“Buffer”,“data”:[255]},“Current Value”:“on/enable”,“Target Value (Raw)”:{“type”:“Buffer”,“data”:[255]},“Target Value”:“on/enable”,“Duration (Raw)”:{“type”:“Buffer”,“data”:[0]},“Duration”:“Already at the Target Value”}
2025-10-16T14:01:28.158Z
[ProcessSendData]: Marked node 59 as noAckNode
2025-10-16T14:01:28.160Z
Transmit failed with TRANSMIT_COMPLETE_NO_ACK - txStatusReport: {“wTransmitTicks”:“0x562”,“bRepeaters”:“0x0”,“rssi_values_incoming_0”:“0x7f”,“rssi_values_incoming_1”:“0x7f”,“rssi_values_incoming_2”:“0x7f”,“rssi_values_incoming_3”:“0x7f”,“rssi_values_incoming_4”:“0x7f”,“bACKChannelNo”:“0x0”,“bLastTxChannelNo”:“0x1”,“bRouteSchemeState”:“0x7”,“pLastUsedRoute_0”:“0x0”,“pLastUsedRoute_1”:“0x0”,“pLastUsedRoute_2”:“0x0”,“pLastUsedRoute_3”:“0x0”,“pLastUsedRoute_4”:“0x2”,“bRouteTries”:“0x24”,“bLastFailedLinkFrom”:“0x55”,“bLastFailedLinkTo”:“0xa”,“bUsedTxPower”:“0x0”,“bMeasuredNoiseFloor”:“0x0”,“bDestinationAckUsedTxPower”:“0x0”,“bDestinationAckMeasuredRssi”:“0x0”,“bDestinationAckMeasuredNoiseFloor”:“0x0”}
2025-10-16T14:01:28.161Z
Command[1245] end: sendData
2025-10-16T14:01:29.008Z
Node[59]: [COMMAND_CLASS_SECURITY_2] {“Sequence Number (Raw)”:{“type”:“Buffer”,“data”:[229]},“Sequence Number”:229,“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[1]},“Properties1”:{“SOS”:true,“MOS”:false},“Receivers Entropy Input (Raw)”:{“type”:“Buffer”,“data”:[166,39,78,195,183,135,40,142,253,226,211,169,109,239,216,99]},“Receivers Entropy Input”:{“type”:“Buffer”,“data”:[166,39,78,195,183,135,40,142,253,226,211,169,109,239,216,99]}}

Doesn’t seem like the device’s response is making it back to the Homey.

Hi Rick,
As z-wave user you’d know you need to have the device not 3 feet, but 3 fingers away during the pair process :wink:

All z-wave knowledge base articles:
https://support.homey.app/hc/en-us/search?utf8=âś“&query=z-wave

Wewnt back and was like 3 fingers away and still the communication is lost on the final stage of adding the device. I have a brand new outlet I will try to pair over the weekend and see what happens.

What crossed my mind: what about restoring a backup?
(plus, if you perform the offline USB backup before installing firmware updates, it’s even possible to revert the firmware version).

Well after some thought and ChatGPT checking. It may be the multiple flicker blubs we recently added to the fixtures in the house. I suspect they may be throwing alot of EMI into the network. The time we changed the bulbs to the time the network became unstable correlate.

1 Like