Issues with new setup

Setup, Configuration and Use Installation
1
  • Platform information:
    • Hardware:x86_64, 12GB RAM, Zooz 800 USB Stick, GoControl GC-TBZ48
    • OS: Archlinux
    • Java Runtime Environment: docker image
    • openHAB version: 4.3.5
  • Issue of the topic: general issues with z wave

I started setting up a new controller to eventually move to my parents house and I only have 1 z wave device I plan to connect to the USB stick, the GZ-TBZ48. I managed to add the z wave controller but I couldn’t get it to associate the HVAC device (GZ-TBZ48) by using the “scan” button on the z wave binding.

Eventually I tried using :

docker run -ti --rm -p 8091:8091 -p 3000:3000 --device=/dev/ttyACM0:/dev/zwave -v $(pwd)/store:/usr/src/app/store zwavejs/zwave-js-ui:latest

and I was able to associate the hvac device there without security enabled but i was forced to set a handful of unique security keys (i just type 32 1’s, then 2’s, etc. for each field, a total of 6).

when i saw this worked, i went back to OH to try to add the device and it didn’t magically appear, but when i did the scan and woke the device with a button press (didn’t go through inclusion, etc. no the HVAC device) – it found the device but it never fully synchronized. i’m not sure if its b/c it was associated to the USB stick with a different key or not (i assume no b/c i claims no security was used).

one thing that’s interesting though is i frequently see this error message from openhab:

2025-07-16 21:22:57.777 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2025-07-16 21:22:57.778 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2025-07-16 21:23:00.931 [WARN ] [.core.thing.binding.BaseThingHandler] - Attempt to apply invalid configuration 'Configuration[{key=controller_softreset; type=Boolean; value=false}, {key=security_networkkey; type=String; value=D0 68 C2 56 ED B5 5D EA 1D 00 42 5F 54 F5 DB 4A}, {key=security_inclusionmode; type=BigDecimal; value=2}, {key=controller_sisnode; type=BigDecimal; value=0}, {key=controller_maxawakeperiod; type=BigDecimal; value=20}, {key=controller_sync; type=Boolean; value=false}, {key=controller_master; type=Boolean; value=true}, {key=inclusion_mode; type=BigDecimal; value=1}, {key=port; type=String; value=/dev/zwave}, {key=controller_wakeupperiod; type=BigDecimal; value=7200}, {key=controller_exclude; type=Boolean; value=false}, {key=heal_time; type=BigDecimal; value=2}, {key=controller_inclusiontimeout; type=BigDecimal; value=30}, {key=controller_hardreset; type=Boolean; value=false}]' on thing 'zwave:serial_zstick:7a3578ec85' blocked. This is most likely a bug: {controller_sisnode=The value must not be less than 1.}
2025-07-16 21:26:55.150 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 1: Device discovery could not resolve to a thingType! Manufacturer data not known.
2025-07-16 21:26:55.154 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.
2025-07-16 21:26:55.157 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:7a3578ec85:node2' to inbox.
2025-07-16 21:32:02.304 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2025-07-16 21:32:02.305 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2025-07-16 21:32:05.361 [WARN ] [.core.thing.binding.BaseThingHandler] - Attempt to apply invalid configuration 'Configuration[{key=controller_softreset; type=Boolean; value=false}, {key=security_networkkey; type=String; value=D0 68 C2 56 ED B5 5D EA 1D 00 42 5F 54 F5 DB 4A}, {key=security_inclusionmode; type=BigDecimal; value=2}, {key=controller_sisnode; type=BigDecimal; value=0}, {key=controller_maxawakeperiod; type=BigDecimal; value=20}, {key=controller_sync; type=Boolean; value=false}, {key=controller_master; type=Boolean; value=true}, {key=inclusion_mode; type=BigDecimal; value=1}, {key=port; type=String; value=/dev/zwave}, {key=controller_wakeupperiod; type=BigDecimal; value=7200}, {key=controller_exclude; type=Boolean; value=false}, {key=heal_time; type=BigDecimal; value=2}, {key=controller_inclusiontimeout; type=BigDecimal; value=30}, {key=controller_hardreset; type=Boolean; value=false}]' on thing 'zwave:serial_zstick:7a3578ec85' blocked. This is most likely a bug: {controller_sisnode=The value must not be less than 1.}

i’ve tried setting that sisnode value from the default(?) of 1 to 2 (from the ui) but its odd that it claims it has a value less than 1.

i’ll fidle around with updating the security key that openhab had for the usb stick to the all 1’s or 2’s, … values and see if it eventually works but this has been an uphill struggle so far.

2

I figured out how to “reset” an old zwave dongle ( usb-Zooz_800_Z-Wave_Stick ) so I switched and this one worked flawlessly on the first try.

My guess is the issue is that openhab doesn’t quite support the much newer zooz 800 usb stick ( ZST39LR) as I started getting recurring “bridge error” messages. Luckily I’m still within the return window at Amazon.

3

Have you checked out zwavejs?

4

i found it and tried it while trying to find something else to test the dongle with and after a bit of a struggle i was able to get it to work there. i ended up returning the dongle since i was able to use zwavejs to do a factory reset on another adapter.

for anybody who does a search, the Zooz 800 Series Z-Wave Long Range S2 USB Stick ZST39 LR does not work on openahb yet so it might be best to avoid it.

5

There was an issue with the Zooz 800 zstick on the OH Zwave binding as explained here. I suspect that was your issue because the symptom is the sisnode message you noted.

6

thanks, that does seem related but i’ve since returned the device since i didn’t want to wait too close to the return window expiring.