Zwavejs: Z-Wave controller status has changed to Unresponsive

[Smith]

As I have common problems with adding zwave-lr device to c8 hub with smartstart (any solutions for this yet ?) i decided to switch to c8-pro with zwavejs in hope that it will improve something.

Install/restore of zwave/etc went ok. all devices worked. after switching to zwavejs in settings and reboot all devices were in pending state. After looking in log turned out that it stuck in loop of

Z-Wave controller status has changed to Ready
Z-Wave controller status has changed to Unresponsive
Z-Wave controller status has changed to Ready
Z-Wave controller status has changed to Unresponsive

Reboots/shutdowns didn't help. Switching to legacy stack (Everything works) and back to zwavejs didn't help. i am on latest software version

I looked into zwavejs log, looks like zwave stack fails to communicate with controller. I have 60kb log that I can upload if needed.

Any suggestions ?

[dnickel]

There are quite a few threads about this including responses from the HE staff.
These messages don't really affect the operation of ZW and it is something we live with until the next firmware release.
I believe there are issues with the latest release that the staff weren't happy with so we are on an earlier stable one that give these messages.

[Smith]

i couldn't find any threads about this specific problem.

and if you will read what I wrote, zwave with zwavejs doesn't work at all.

[dnickel]

Sorry, I only focused on the error messages I've seen since JS came in.
Have you tried re-interviewing a few devices so see if they come back?
JS node interview.
node is decimal
192.168.1.250/hub/zwave2/reinterview?node=176

[Smith]

based on zwavejs logs, as i wrote, it looks like zwave controller simply doesn't work. communication between zwavejs to controller all the time seems to die.

you can't reinterview nodes if controller doesn't work

[dnickel]

True.
I was just grasping at straws since everything was Pending.
Very odd ZIP works so at least it's not the radio.
tagging @bcopeland

[Smith]

i got loop of following messages with small variations

2025-09-14 11:24:50.182DRIVER » [Node 025] [REQ] [SendDataBridge] - │ source node id: 1 - │ transmit options: 0x25 - │ callback id: 43 - └─[NoOperationCC]

2025-09-14 11:24:50.179SERIAL » 0x010f00a900010019010025000000002b4e (17 bytes)

2025-09-14 11:24:50.174CNTRLR Switching to 16-bit node IDs successful

2025-09-14 11:24:50.171DRIVER « [RES] [SerialAPISetup] - command: SetNodeIDType - success: true

2025-09-14 11:24:50.168SERIAL « 0x0105010b800171 (7 bytes)

2025-09-14 11:24:50.165SERIAL « [ACK] (0x06)

2025-09-14 11:24:50.162DRIVER » [REQ] [SerialAPISetup] - command: SetNodeIDType - node ID type: 16 bit

2025-09-14 11:24:50.159SERIAL » 0x0105000b800273 (7 bytes)

2025-09-14 11:24:50.154CNTRLR Switching serial API to 16-bit node IDs...

2025-09-14 11:24:50.151DRIVER » [REQ] [StartWatchdog]

2025-09-14 11:24:50.150SERIAL » 0x010300d22e (5 bytes)

2025-09-14 11:24:50.145CNTRLR Currently active command will be retried...

2025-09-14 11:24:50.144CNTRLR Starting hardware watchdog...

2025-09-14 11:24:50.142CNTRLR Serial API restarted unexpectedly.

2025-09-14 11:24:50.139DRIVER « [REQ] [SerialAPIStarted] - wake up reason: WatchdogReset - watchdog enabled: false - generic device class: 0x02 - specific device class: 0x07 - always listening: false - supports Long Range: true

---

2025-09-14 11:30:03.240CNTRLR Currently active command will be retried...

2025-09-14 11:30:03.237SERIAL » [ACK] (0x06)

2025-09-14 11:30:03.235SERIAL « 0x0114000a03000302070a5e5556226c748a8f989f018a (22 bytes)

2025-09-14 11:30:01.656SERIAL » [ACK] (0x06)

2025-09-14 11:30:01.653SERIAL « 0x010401a90152 (6 bytes)

2025-09-14 11:30:01.650SERIAL « [ACK] (0x06)

2025-09-14 11:30:01.648DRIVER » [Node 025] [REQ] [SendDataBridge] - │ source node id: 1 - │ transmit options: 0x25 - │ callback id: 43 - └─[NoOperationCC]

2025-09-14 11:30:01.646SERIAL » 0x010f00a900010019010025000000002b4e (17 bytes)

2025-09-14 11:30:01.643CNTRLR Switching to 16-bit node IDs successful

2025-09-14 11:30:01.638DRIVER « [RES] [SerialAPISetup] - command: SetNodeIDType - success: true

2025-09-14 11:30:01.636SERIAL « 0x0105010b800171 (7 bytes)

2025-09-14 11:30:01.634SERIAL « [ACK] (0x06)

2025-09-14 11:30:01.632SERIAL « [ACK] (0x06)

2025-09-14 11:30:01.629SERIAL » 0x0105000b800273 (7 bytes)

2025-09-14 11:30:01.623DRIVER » [REQ] [StartWatchdog]

2025-09-14 11:30:01.621SERIAL » 0x010300d22e (5 bytes)

2025-09-14 11:30:01.615CNTRLR Starting hardware watchdog...

2025-09-14 11:30:01.612CNTRLR Serial API restarted unexpectedly.

2025-09-14 11:30:01.609DRIVER « [REQ] [SerialAPIStarted] - wake up reason: WatchdogReset - watchdog enabled: false - generic device class: 0x02 - specific device class: 0x07 - always listening: false - supports Long Range: true

[Smith]

bump

anyone ?

[jtp10181]

You mentioned reboot and shut down, did you pull power for 30 seconds so the radio will fully power off? Also how is hub being powered, see info below:

@jtp10181

Z-Wave Issues

For partial or total loss of Z-Wave control (radio seems dead), before doing anything else please shut down the hub from settings and unplug for 30 seconds, then re-plug to boot back up. This will allow the radios to fully power down and restart. A regular reboot only restarts the platform and not the radio hardware.

...

Official Hubitat Documentation Resources:
Hubitat Docs: Z-Wave Details
Hubitat Docs: How to Troubleshoot Z-Wave

What info to provide for troubleshooting assistance:

• How is Hub being powered? Supplied power block or other (explain)
  • PoE power (with splitter) is known to cause major Z-Wave issues on the C-8 hub.
  • See this post for detailed write up on PoE testing: PoE and the C8

Also, since you said it works fine on ZIP, what is your actual issue with SmartStart and LR? You never said what the original problem was, just that is was a "common" problem???

---

@bcopeland Seen this before?

2025-09-14 11:24:50.139DRIVER « [REQ] [SerialAPIStarted] - wake up reason: WatchdogReset - watchdog enabled: false - generic device class: 0x02 - specific device class: 0x07 - always listening: false - supports Long Range: true

[Smith]

yes. i did power it down for 30 sec. made a little dance. sprinkled holy water and sacrificed a lamb to gods of zwave.

common problem with smartstart and LR it's that it doesn't work. the one that discussed here S2 bootstrapping - Unknown status code - #3 by jsprince3

[jtp10181]

The bootstrapping issue AFAIK is NOT resolved by Zwave JS, and it will also follow with a migration. So if you migrated from the C8 to the Pro you just moved the issue to the new hub. The only known fix is to start from a fresh hub and/or reset the zwave radio. Not recommended unless you REALLY need LR.

You could try the trick mentioned in here (click link below to see full post) if you want, no one else has confirmed if it worked for anyone else or not.

Zooz ZSE70 & Smartstart & Smartstart Manager - Add as LR

I was just going to post that other thread you found. I skimmed through it, and it is relatively confusing. TLDR: Typically you have to reset the z-wave radio and rebuild everything to fix the constant bootstrapping error when pairing LR devices. However, someone just recently has found a trick that is working for them, may work for others. After Step 5 exclude, since you already have it sitting in SmartStart in LR mode the device will immediately try to pair as LR. It will either get the …

[Smith]

regardless, there is still an issue of zwavejs doesn't working at all. i have 600kb lzwave js log generated in a few minutes showing same messages as i posted above.

with regards to "trick" and that problem is following between hubs and to zwavejs: i am very interested to see some kind of official statement from hubitat team on this topic. is there one ?

[jtp10181]

I tagged the z-wave dev above. Tagging @bobbyD also in case he has seen this before (see zwave WatchdogReset error above).

Did you migrate to the C8 Pro or was this a fresh setup?

I have some other ideas but I will wait for staff feedback before going down that rabbit hole. I would just switch back tp ZIP while you wait.

You could also submit a warranty case if you want: Warranty – Hubitat Support

[Smith]

i migrated from c8 that was migrated from c7. i already switched to zip. actually tried few times going back and forth