My experience so far with a new no brand Z-wave 800 device

barrymac · January 5, 2024, 10:51pm

I’m totally new to openhab and smart home stuff in general

I’m running openhab in docker on linux and the device has been recognised and shows as being online.

The device is this one, described as having model number Z-GW800-V01

lsusb -v -s 006:004

Bus 006 Device 004: ID 1a86:55d4 QinHeng Electronics 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x1a86 QinHeng Electronics
  idProduct          0x55d4 
  bcdDevice            4.43
  iManufacturer           1 SiliconLabs
  iProduct                2 Z-Wave 800 Dongle
  iSerial                 3 533D004242
  bNumConfigurations      1

I haven’t been able to see any included devices, although they seem to act like they are connected, but it’s the first time I’m using any zwave devices so I’m not that sure.

I get this in events log:

cat archives/docker/volumes/openhab_userdata/_data/logs/events.log | grep zwave
2024-01-05 20:29:43.016 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:serial_zstick:b275003e2e' changed from UNINITIALIZED (HANDLER_MISSING_ERROR): Handler factory not found to UNINITIALIZED (NOT_YET_READY)
2024-01-05 20:29:53.074 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:serial_zstick:b275003e2e' changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2024-01-05 20:29:53.093 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:serial_zstick:b275003e2e' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2024-01-05 20:32:37.163 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:serial_zstick:b275003e2e' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

and this in openhab logs:

2024-01-05 20:29:53.013 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Creating ZWave discovery service for zwave:serial_zstick:b275003e2e with scan time of 60
2024-01-05 20:29:53.014 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Active zwave:serial_zstick:b275003e2e
2024-01-05 20:29:53.015 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2024-01-05 20:29:53.087 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Initializing ZWave serial controller.
2024-01-05 20:29:53.088 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initializing ZWave Controller zwave:serial_zstick:b275003e2e.
2024-01-05 20:32:33.564 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM1'
2024-01-05 20:32:33.574 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Starting receive thread
2024-01-05 20:32:33.582 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2024-01-05 20:32:33.582 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initialising ZWave controller
2024-01-05 20:32:33.605 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Scheduling network mesh heal for 6 hours time.
2024-01-05 20:32:36.618 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 15 E9 
2024-01-05 20:32:36.619 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2024-01-05 20:32:36.675 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 20 DC 
2024-01-05 20:32:36.676 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2024-01-05 20:32:36.706 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 07 FB 
2024-01-05 20:32:36.707 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2024-01-05 20:32:36.773 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 06 96 0F 65 
2024-01-05 20:32:36.774 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2024-01-05 20:32:36.790 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 56 AA 
2024-01-05 20:32:36.792 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2024-01-05 20:32:36.812 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 02 FE 
2024-01-05 20:32:36.813 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2024-01-05 20:32:36.907 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 05 F9 
2024-01-05 20:32:36.908 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2024-01-05 20:32:37.086 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 1: Serializing from file /openhab/userdata/zwave/network_cc3622be__node_1.xml
2024-01-05 20:32:37.161 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Controller: Incoming Network State Event true
2024-01-05 20:32:37.172 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@741c56a2
2024-01-05 20:32:37.201 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 41 01 BB 
2024-01-05 20:32:37.203 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2024-01-05 20:32:37.217 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 1: Adding command class COMMAND_CLASS_NO_OPERATION to the list of supported command classes.
2024-01-05 20:32:37.223 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 1: Adding command class COMMAND_CLASS_BASIC to the list of supported command classes.
2024-01-05 20:32:37.235 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 1: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@6a74ef95
2024-01-05 20:32:37.236 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 1: Serializing to file /openhab/userdata/zwave/network_cc3622be__node_1.xml

which seems pretty positive, however no devices show up. I’ve tried a Heimann HS1HT-Z temp humidity sensor which is listed as supported and various Neo Coolcam door sensors and smart plugs.

I do notice this however:

2024-01-05 22:36:41.873 [DEBUG] [g.zwave.internal.ZWaveConfigProvider] - ZWave product zwave:serial_zstick has no references!
2024-01-05 22:36:41.875 [DEBUG] [g.zwave.internal.ZWaveConfigProvider] - ZWave product zwave:device has no references!

which seems to suggest it might just not be a recognised device yet, and maybe I just need to add it to the device database?

apella12 · January 5, 2024, 11:36pm

Welcome to OH forum. Sorry first post is a problem. Worse, I’m not sure what is going on, except that the controller is not responding to messages (TX).

There is a debug log viewer here. and your snippet shows is
bad 800 log 2024-01-05 182022

what it should look like is this.

My guess is that it has something to do with Docker. Have you reviewed the Docker installation regarding USB devices? Look at the bottom of the docs. Docker | openHAB an 800 stick is usually /dev/ttyUSB0, but as noted it could be different.