Zwave fails to include device | Home Assistant | Page 1

modest nimbus Nov 3, 2025, 4:53 AM

#

Zwave is just failing to include this device. Factory resets and exclusions are not helping. There's no diagnostic information in the home assistant logs that I can see. Just a red light after about 30 seconds of the device trying to include.

modest nimbus Nov 3, 2025, 4:54 AM

#

modest nimbus Zwave is just failing to include this device. Factory resets and exclusions are ...

What's really frustrating is that my wall is open with live bare wires so I can get to the gizmo, and I can't close it up until it's resolved.

#

There's no useful diagnostic logging for inclusion that I can see. It's just not very helpful

#

Somehow it's sort of half included now, maybe? I've managed to get home assistant to try an inclusion (I have NO idea how) and it's spinning at "get device info".

#

Nevermind, it was just an illusion

#

Still stuck at "This device has been provisioned but is not yet included in the network."

#

I've been working at this for four hours now

#

This is a nightmare. I have to keep the cats away from the live wires while I try and figure out what to do

#

I have opened a support ticket with zooz, but they've not responded either

#

What's frustrating is that sometimes it sort of half appears in HA. I'll get like the first stage of inclusion show up with no profiles loaded.

#

It should be noted that my zwave network seems to be healthy enough to install updated firmware on another device.

#

So I don't think it's mesh health being a problem

deep cypress Nov 3, 2025, 6:31 AM

#

modest nimbus What's frustrating is that sometimes it sort of half appears in HA. I'll get lik...

Share Z-Wave logs. If you are getting this far, the logs should tell us what's wrong.

modest nimbus Nov 3, 2025, 11:59 AM

#

As far as I can tell not a single line about this.. I'll check again later today after work.

modest nimbus Nov 3, 2025, 12:49 PM

#

Ok. After about the 20th attempt at inclusion, including using zwavejsui or my preferred home assistant, it finally included. No idea what was different about this attempt vs the previous 19.

modest nimbus Nov 3, 2025, 3:42 PM

#

is there a limit to how many devices can be on a zwave network?

upper relic Nov 3, 2025, 3:47 PM

#

232 in mesh, 1000+ in LR

modest nimbus Nov 3, 2025, 3:47 PM

#

hmmmm. so it's not 15 or so?

#

ZWaveError: Timeout while waiting for a callback from the controller (ZW0200)
    at Driver.sendMessage (file:///opt/node_modules/zwave-js/src/lib/driver/Driver.ts:7121:23)
    at ZWaveController.stopInclusionInternal (file:///opt/node_modules/zwave-js/src/lib/controller/Controller.ts:2923:22)
    at ZWaveController.stopInclusion (file:///opt/node_modules/zwave-js/src/lib/controller/Controller.ts:2900:29)
    at ControllerMessageHandler.handle (file:///opt/node_modules/@zwave-js/server/dist-esm/lib/controller/message_handler.js:64:62)
    at Client.receiveMessage (file:///opt/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)
    at WebSocket.<anonymous> (file:///opt/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45)
    at WebSocket.emit (node:events:518:28)
    at Receiver.receiverOnMessage (/opt/node_modules/@zwave-js/server/node_modules/ws/lib/websocket.js:1220:20)
    at Receiver.emit (node:events:518:28)
    at Receiver.dataMessage (/opt/node_modules/@zwave-js/server/node_modules/ws/lib/receiver.js:596:14)```

#

is this error message relevant?

upper relic Nov 3, 2025, 3:52 PM

#

See if any of these apply to your case. https://zwave-js.github.io/zwave-js/#/troubleshooting/common-issues?id=timeout-while-waiting-for-an-ack-from-the-controller

#

Actually, "callback", not sure if I've seen that one.

modest nimbus Nov 3, 2025, 3:54 PM

#

i mean, it's trying to do inclusion

upper relic Nov 3, 2025, 3:54 PM

#

Definitely not a good thing to see.

modest nimbus Nov 3, 2025, 3:54 PM

#

and that stack trace is about inclusion.

#

ok. another inclusion attempt has failed, after 5 minutes "No device found after 5 minutes... "

upper relic Nov 3, 2025, 3:54 PM

#

Could try re-plugging the USB stick.

modest nimbus Nov 3, 2025, 3:54 PM

#

and then i get that error a few seconds later

#

maybe.

#

i have a second usb stick that is zwave capable as well - i've debated switching to it, but haven't so far because "it's not broken, don't fix it". but perhaps it is now?

upper relic Nov 3, 2025, 3:55 PM

#

What controller is this one?

modest nimbus Nov 3, 2025, 3:56 PM

#

current controller is a silabs 700 jobbie i got about 5? years ago

upper relic Nov 3, 2025, 3:56 PM

#

Have you updated the firmware?

modest nimbus Nov 3, 2025, 3:57 PM

#

yes, several times. i wrote the howto on how to update it from the command line on linux ;P

#

back well before zwavejs supported doing it itself

#

and the only general option was to use a windows PC

#

probably a clue to it's age 😉

#

v7.17.2 is what i currently have on there

#

zwavejs reports no updates, tho i believe there are several available. but again "not broke, don't fix"

#

to be precise, i have the "Silicon Labs Z-Wave Controller SLUSB7000A UZB-7"

#

amusingly, in the lsusb page, it reports identically to the zha-1 stick "Silicon Labs CP210x UART Bridge"

upper relic Nov 3, 2025, 4:01 PM

#

Yeah that's ancient

#

Firmware service is not supported for that.

modest nimbus Nov 3, 2025, 4:02 PM

#

as i said, i'm aware of it's antiquity

upper relic Nov 3, 2025, 4:02 PM

#

I'm running 7.21.7 on mine. Haven't tested an inclusion lately though.

modest nimbus Nov 3, 2025, 4:03 PM

#

hmmm

#

does this support the NVram dump/import to newer stick?

#

cos i got an aotec 10 pro stick the other month for zigbee stuff, because zwave is way too restrictive.

#

(i figure why not support all three! i have the zha1 matter stick too!)

#

i'm going to try inclusion from zwave-js-ui a minute

upper relic Nov 3, 2025, 4:07 PM

#

I think that version is supported.

modest nimbus Nov 3, 2025, 4:09 PM

#

The jankyness is real

#

if i force reboot zwavejsui (using the restart function) it sometimes shows up a new node...

#

2025-11-03 11:19:12.242 ERROR Z-WAVE: [Node 047] Interview FAILED: The node is dead```

#

it's not dead tho, it's very much alive and blinking. The zwave controller is the other size of the wall.

#

i can't get it much closer.

#

OK. it's kinda found it again. Node 48 now. But it's halfway dead in the interview process.

📎 message.txt

#

same as what I saw earlier.

upper relic Nov 3, 2025, 4:23 PM

#

https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

modest nimbus Nov 3, 2025, 4:23 PM

#

heck knows if i can get it to do this again.

#

it's utterly random when this happens.

#

Grrr. I hate "Unable to remove because the device responded to a ping"

deep cypress Nov 3, 2025, 4:28 PM

#

Exclude it normally

modest nimbus Nov 3, 2025, 4:28 PM

#

well, that was insane.

deep cypress Nov 3, 2025, 4:28 PM

#

Don't force remove it.

modest nimbus Nov 3, 2025, 4:28 PM

#

so, it's up now.

modest nimbus Nov 3, 2025, 4:28 PM

#

deep cypress Exclude it normally

doesn't work.

#

just nothing happens.

deep cypress Nov 3, 2025, 4:29 PM

#

Ok it really sounds like you have a terrible connection to the device

#

Is your stick on a USB extension cable?

modest nimbus Nov 3, 2025, 4:29 PM

#

i doubt it? it's literally right next to the stick.

#

see that picture, behind that fibreboard is the stick and the computer.

#

anyway, it works now.

#

how i got it to work: i had to force restart zwavejsui.

deep cypress Nov 3, 2025, 4:30 PM

#

deep cypress Is your stick on a USB extension cable?

👆🏻?

modest nimbus Nov 3, 2025, 4:30 PM

#

not this one. the other two are tho. and this mobo doesn't have wifi enabled.

deep cypress Nov 3, 2025, 4:30 PM

#

Yeah so that's a problem

upper relic Nov 3, 2025, 4:30 PM

#

https://zwave-js.github.io/zwave-js/#/troubleshooting/first-steps

modest nimbus Nov 3, 2025, 4:30 PM

#

i'm aware. see above: it's been working for 6 years.

deep cypress Nov 3, 2025, 4:30 PM

#

Directly plugging in Z-Wave sticks is a no-go

deep cypress Nov 3, 2025, 4:31 PM

#

modest nimbus i'm aware. see above: it's been working for 6 years.

Well you provided a counter example

modest nimbus Nov 3, 2025, 4:31 PM

#

up until last night.

#

and only these specific devices.

deep cypress Nov 3, 2025, 4:31 PM

#

Try it

modest nimbus Nov 3, 2025, 4:31 PM

#

why do i have to reboot zwavejsui to get it to work?

deep cypress Nov 3, 2025, 4:31 PM

#

It makes more of a difference than you think

deep cypress Nov 3, 2025, 4:31 PM

#

modest nimbus why do i have to reboot zwavejsui to get it to work?

Got Z-Wave logs of this?

modest nimbus Nov 3, 2025, 4:31 PM

#

yes. see above

#

that's literally the logs

#

sorry it wasn't debug level

upper relic Nov 3, 2025, 4:32 PM

#

not driver logs either

modest nimbus Nov 3, 2025, 4:33 PM

#

i think i've got them somewhere here.

#

hang on.

#

how do i find them inside the zwavejsui container?

upper relic Nov 3, 2025, 4:33 PM

#

In your store directory or from the Store page

#

Not really worth troubleshooting until a USB extension is installed. That has fixed problems for other users too many times to count.

modest nimbus Nov 3, 2025, 4:34 PM

#

heh. 66megs

modest nimbus Nov 3, 2025, 4:34 PM

#

upper relic Not really worth troubleshooting until a USB extension is installed. That has fi...

if you say so.

#

i'm 99% sure it's irrelevant here.

upper relic Nov 3, 2025, 4:35 PM

#

Heard that before

#

And if it isn't, well at least one thing is crossed off the list.

deep cypress Nov 3, 2025, 4:37 PM

#

modest nimbus if you say so.

There's a reason this is step 1 in the Z-Wave JS troubleshooting docs. Trust me.

modest nimbus Nov 3, 2025, 4:38 PM

#

well, i'm reviewing the driver logs here. it seems to be talking fine to it, then my very very chatty "hey here's a power update" thing comes along and the whole interview collapses.

deep cypress Nov 3, 2025, 4:38 PM

#

And that's another one of the frequent issues 🫣

modest nimbus Nov 3, 2025, 4:39 PM

#

my real question isn't this tho - it's why it completely failed to even include the thing until i restarted zwavejsui

#

still scrolling back in the logs. 66megs

deep cypress Nov 3, 2025, 4:43 PM

#

Maybe the firmware got stuck. Restarting Z-Wave JS UI also restarts the stick.

deep cypress Nov 3, 2025, 4:43 PM

#

modest nimbus still scrolling back in the logs. 66megs

Zip it and share it. Those logs compress very well.

modest nimbus Nov 3, 2025, 4:43 PM

#

I'm about 99% sure zwavejs crashed.

#

                                 │ RSSI: -54 dBm
                                 └─[CRC16CCCommandEncapsulation]
                                   └─[MultiChannelCCCommandEncapsulation]
                                     │ source:      2
                                     │ destination: 0
                                     └─[MeterCCReport]
                                         meter type:  Electric
                                         scale:       kVarh
                                         rate type:   Consumed
                                         value:       3.596
                                         time delta:  10 seconds
                                         prev. value: 3.596
2025-11-03 11:18:54.162 DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                 ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                   ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                  ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                 ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                 ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝

#

note that i was trying to include from about 10:40 onwards...

#

those are successive log entries in the log file

deep cypress Nov 3, 2025, 4:44 PM

#

Odd

modest nimbus Nov 3, 2025, 4:44 PM

#

do we have a preferred file share?

#

it was definitely logging the UI logs between those times.

#

hmmm. i think it's too big to directly attach in discord.

#

📎 zwavejs_2025-11-03.tar.gz

#

nevermind!

#

early on you'll find my extremely frustrated attempts to include a previous device that has exactly the same behaviour

#

that's Node 46. Node 8 is the chatty cathy that sends power updates every few seconds.

#

node 47 is the same device that became node 48. i'm pretty sure inclusion is crashing zwavejsui sometimes, and it's a silent crash

#

i don't know what caused the restart at 11:18 - i was chatting on here at the time as you can see...

#

actually, i did force it twice didn't i

upper relic Nov 3, 2025, 4:49 PM

#

Might see if there's anything in the docker logs

#

sometimes exceptions are printed there

modest nimbus Nov 3, 2025, 4:50 PM

#

those are the logs you saw earlier i think.

#

(they're from the home assistant addon "log" panel for zwavejsui)

#

ok. i'm going to install this in a wall a minute. i'll be back shortly.

modest nimbus Nov 4, 2025, 2:33 AM

#

OK. trying again, again!

#

It did the half inclusion thing - it's got some configuration, but it's not correct...

#

the stick is on a usb extension about 6 foot from the computer...

#

it took several reinterviews for the device to show up properly, as well as a couple of rebuild routes. the zwavejsui didn't crash this time tho.

deep cypress Nov 4, 2025, 1:14 PM

#

Couple of things:

2025-11-03 00:05:49.642 DRIVER « [RES] [GetBackgroundRSSI]
                                   channel 0: -81 dBm
                                   channel 1: -84 dBm
                                   channel 2: -84 dBm
                                   channel 3: -75 dBm

You have extremely high background noise. For a 700 series controller, these values should be around -100, or even less.

This could be caused by the excessive power meter reporting you already mentioned.
Node 8 sticks out like a sore thumb (73000 reports over the duration of the logfile). That's one report every 1.15 seconds, which is significantly too much for a stable mesh.
Node 35 has about 12k, half outgoing, half incoming, because it sends its reports using Supervision. The rest are fairly quiet.

#

For example, do you really need to know that the kVar reading on channel 2 changed by 0.002 in the last 10 seconds?

2025-11-03 11:34:19.060 DRIVER « [Node 008] [REQ] [BridgeApplicationCommand]
                                 │ RSSI: -54 dBm
                                 └─[CRC16CCCommandEncapsulation]
                                   └─[MultiChannelCCCommandEncapsulation]
                                     │ source:      2
                                     │ destination: 0
                                     └─[MeterCCReport]
                                         meter type:  Electric
                                         scale:       kVar
                                         rate type:   Consumed
                                         value:       0.314
                                         time delta:  10 seconds
                                         prev. value: 0.312

#

I wouldn't be surprised that if you turn that single device off, 95% of your issues go away.

modest nimbus Nov 5, 2025, 8:09 PM

#

I mean, it's entire job is to report power consumption. I'll see if there's config to turn it down a bit, but what's the point of having it if it isn't doing it's job?

#

Node 35 is a new dimmer switch I installed the other day. (Node 8 has been doing it's thing since about 2021)

modest nimbus Nov 5, 2025, 8:12 PM

#

deep cypress Couple of things: ``` 2025-11-03 00:05:49.642 DRIVER « [RES] [GetBackgroundRSSI]...

Thanks much for the info about snr: I honestly had no idea that was bad.

#

I mean, I have no idea how I'll fix it, the em noise is just high here- lots of suburban houses with lots of wifis and bluetooths and everything else

#

Pretty sure wrapping it in tinfoil would dramatically improve snr, but might impact the performance of the device

deep cypress Nov 10, 2025, 7:27 AM

#

modest nimbus I mean, I have no idea how I'll fix it, the em noise is just high here- lots of ...

wifi/bluetooth are not using the same frequencies. They should not affect your Z-Wave noise levels.

deep cypress Nov 10, 2025, 7:28 AM

#

modest nimbus I mean, it's entire job is to report power consumption. I'll see if there's conf...

That's kind of the problem with power meters on Z-Wave. They are often too chatty for a healthy network. The key lies in tuning the reports well:
https://zwave-js.github.io/zwave-js/#/troubleshooting/first-steps?id=reduce-reports-from-the-network

Z-Wave JS - Z-Wave driver written entirely in JavaScript/TypeSc...

Z-Wave driver written entirely in JavaScript/TypeScript

deep cypress Nov 10, 2025, 11:04 AM

#

FWIW, the time delta your node 8 reports looks like it is actually violating the Z-Wave specification by a factor of 3:

#Zwave fails to include device