#zwavejs logs - Stuck in inclusion mode?

1 messages · Page 1 of 1 (latest)

hardy ivy
#

I'm seeing these in my logs
2024-11-18T19:34:55.635Z CNTRLR Received Smart Start inclusion request (Z-Wave Long Range) 2024-11-18T19:34:55.636Z CNTRLR NWI Home ID not found in provisioning list, ignoring request... 2024-11-18T19:35:01.660Z CNTRLR Received Smart Start inclusion request 2024-11-18T19:35:01.660Z CNTRLR NWI Home ID not found in provisioning list, ignoring request... 2024-11-18T19:35:01.727Z CNTRLR Received Smart Start inclusion request 2024-11-18T19:35:01.729Z CNTRLR NWI Home ID not found in provisioning list, ignoring request... 2024-11-18T19:35:01.810Z CNTRLR Received Smart Start inclusion request 2024-11-18T19:35:01.812Z CNTRLR NWI Home ID not found in provisioning list, ignoring request...
I've restarted the container (zwavejs-ui), but it still continues. I did try to include a device yesterday, but it added successfully, but when I tried a new device, it did not (and I'm still not sure why).

Is there a way to reboot/reset the controller to get it out of the inclusion state (note, the Web UI has no indication that the controller is being doing inclusion).

silent rain
#

It's not in inclusion state, it's just receiving smartstart requests from a device

#

seems the device is spamming the requests

hardy ivy
#

How would I identify the offending device?

silent rain
#

I don't think there's any way to do that.

hardy ivy
#

🙁

silent rain
#

If you have something that's powered and not included, try removing power.

hardy ivy
#

I'll try that. I did have a device that I was trying to add, but it's been failing to add in the web interface. Perhaps that's the device, but the web interface is not recognizing the device.

silent rain
#

Debug logs provide more information

#

Apparently I have some new battery device I haven't unpacked that is doing the same thing. Normally they aren't powered.

sinful eagle
#

And normally battery powered devices stop doing that after a while

silent rain
#

Mine's been going for weeks.

#

My oldest logs go back to Nov. 2nd, and it's literally this annoying node's smartstart request.

#

Would be nice to go from NW Home ID to DSK part, but that doesn't look feasible since two of the bytes are clobbered?

sinful eagle
#

Those ids sent by the devices for SmartStart inclusion are a part of the DSK with some clobbered bits.
Given the DSK you can determine the NWI or Auth home ID, but not vice versa