Open Zwave test trouble

I did try a test on using Open Zwave instead of normal Z-wave.
I used the try method mentiond in: How to test the OZW Beta without fully switching over

I didn’t get it running
I do run a MQTT broker separate from HA in a Docker, so I installed in the config.yaml:
broker: my IP
username: my username
password: my password.
restarted HA

I stopped the current running Z-Wave.
Installed Open Zwave and configured it with my dongle USb path by serial-id and Network key i used with the standard zwave integration
That went wrong because I did use in the past the standard network key (not smart). Open Zwave give an error on that! (It is not allowed to use the standard network key)
So I did make a new key
Started the open Zwave addon
After that I did + the open zwave at integrations.
It did say that the integration succeeded

Then I opened the webui.
The webui is opening but I do see a grey window with grayed out headers, so I can not do anything.
In the open Zwave log I do see zwave node coming in, so it looks like something is happening with the open zwave???

What am I doing wrong?
Is it because of a different network key?
Or Do I need to do something different?

part of the open zwave log:

[20200817 19:51:31.123 CEST] [ozw.library] [debug]: Detail - Node: 7 Notification: Notification - Node Asleep 
[20200817 19:51:31.123 CEST] [ozw.library] [info]: Info - Node: 8 Sending (Query) message (Callback ID=0x22, Expected Reply=0x04) - ZWavePlusInfoCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x5e, 0x01, 0x25, 0x22, 0xb7 
[20200817 19:51:31.123 CEST] [ozw.notifications] [debug]: Notification pvt_ozwNotification NotificationTypes::Notification_Code_NodeAsleep Thread:  0x7fcde21f8d48 
[20200817 19:51:31.124 CEST] [ozw.mqtt.publisher] [debug]: Publishing Event ozwNotification 
[20200817 19:51:31.124 CEST] [ozw.library] [info]: Info - Node: 8 Encrypted Flag is 0 
[20200817 19:51:31.135 CEST] [ozw.library] [debug]: Detail - Node: 8   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 
[20200817 19:51:31.135 CEST] [ozw.library] [debug]: Detail - Node: 8   ZW_SEND_DATA delivered to Z-Wave stack 
[20200817 19:51:31.151 CEST] [ozw.library] [debug]: Detail - Node: 8   Received: 0x01, 0x07, 0x00, 0x13, 0x22, 0x00, 0x00, 0x02, 0xcb 
[20200817 19:51:31.151 CEST] [ozw.library] [debug]: Detail - Node: 8   ZW_SEND_DATA Request with callback ID 0x22 received (expected 0x22) 
[20200817 19:51:31.152 CEST] [ozw.library] [info]: Info - Node: 8 Request RTT 27 Average Request RTT 27 
[20200817 19:51:31.152 CEST] [ozw.library] [debug]: Detail - Node: 8   Expected callbackId was received 
[20200817 19:51:31.162 CEST] [ozw.library] [debug]: Detail - Node: 8   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x08, 0x09, 0x5e, 0x02, 0x01, 0x05, 0x00, 0x07, 0x00, 0x07, 0x00, 0xad 
[20200817 19:51:31.163 CEST] [ozw.library] [info]: Info - Node: 8 Response RTT 38 Average Response RTT 38 
[20200817 19:51:31.163 CEST] [ozw.library] [info]: Info - Node: 8 ZW+ Info - Version 1, Role 5, NodeType 0, InstallerIcon 1792, deviceType 1792 
[20200817 19:51:31.164 CEST] [ozw.library] [info]: Info - Node: 8 ZWave+ Info Received from Node 8 
[20200817 19:51:31.164 CEST] [ozw.library] [info]: Info - Node: 8   Zwave+ Node Type  (0x00) - Z-Wave+ node. Mandatory Command Classes: 
[20200817 19:51:31.164 CEST] [ozw.library] [info]: Info - Node: 8     NONE 
[20200817 19:51:31.164 CEST] [ozw.library] [info]: Info - Node: 8   Zwave+ Device Type  (0x0700) - On/Off Power Switch. Mandatory Command Classes: 
[20200817 19:51:31.165 CEST] [ozw.library] [info]: Info - Node: 8     COMMAND_CLASS_DEVICE_RESET_LOCALLY 
[20200817 19:51:31.165 CEST] [ozw.library] [info]: Info - Node: 8     COMMAND_CLASS_ZWAVEPLUS_INFO 
[20200817 19:51:31.165 CEST] [ozw.library] [info]: Info - Node: 8     0x59 (Not Supported)

screenshot webui:

Please elaborate on the “standard network key” ?

The standard zwave network key is:

0x2e, 0xcc, 0xab, 0x1c, 0xa3, 0x7f, 0x0e, 0xb5, 0x70, 0x71, 0x2d, 0x98, 0x25, 0x43, 0xee, 0x0c

I do use that key with the normal z-wave. (I realize now that was not a smart choice)

The log is then saying using this key with open zwave:

[cont-init.d] executing... 
[20:09:01] FATAL: 
[20:09:01] FATAL: The add-on detected that the Z-Wave network key used
[20:09:01] FATAL: is from the documented example.
[20:09:01] FATAL: 
[20:09:01] FATAL: Using this key is insecure, because it is publicly
[20:09:01] FATAL: listed in the documentation.
[20:09:01] FATAL: 
[20:09:01] FATAL: Please check the add-on documentation on how to
[20:09:01] FATAL: create your own, secret, "network_key" and replace
[20:09:01] FATAL: the one you have configured.
[20:09:01] FATAL: 
[20:09:01] FATAL: Click on the "Documentation" tab in the OpenZWave
[20:09:01] FATAL: add-on panel for more information.
[20:09:01] FATAL: 
[cont-init.d] exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] executing...

But My devices are using the standard key, so they will not connect with an new key I guess.
I can only use an new key by pairing all devices again I guess?
(There are 50 of them out there!)

That’s an example key. There is no ‘standard key’ you always generate one yourself.
Do you have any nodes that are secure nodes (examples are door locks and garage doors)?

As far as I know not.
But I changed the network key with the standard Z-wave. After that all nodes are not responsive anymore
after changing back, they respond again

In Open Zwave I did make a new key for the test
resulting as mentioned in the first message above

This usually means you included the devices securely and they will need to be excluded and added again. Unless you have devices that REQUIRE secure inclusion do not use it. It adds something like 200% overhead to the zwave network using secure messages.

Devices the require it are usually access control devices like door locks, garage doors, etc. Some sensors require it but not many.

So it means I do need to unpair and pair all my devices again?
Is this also causing the empty webui in open zwave?
Because I’m not able to add any node in the webUI?
Or is something else wrong beside the secured devices?

Yes, if anything for your own security/piece of mind.

No on that screen you click the Open menu, and the bottom Start button in the dialog box that comes up.

I did try that also without luck.
It is giving to start buttons.
One giving AMCO as device and something in a second box I don’t know anymore
Do I need to enter something in the boxes, before pressing start?

Yess something happening. Thanks.
I do see some devices (not all) (I think only the powered vices are showing up)

But this is a good basis to start again.

I think I will unpair and pair all devices again as unsecured
Then I wil try Open zwave again

Thanks for the help

I do see the devices in the webui.
But If I look in HA at entity I do see the devices (I think) but can not switch or do something with them?
Or are these the old entitys from the old zwave?

1 Like

You cannot use your own MQTT broker and the OpenZWave addon. The OZW addon requires the MQTT addon. You can use the standalone docker ozwdaemon docker container instead.

This is a restriction imposed by the Addon only. If you use the ozwdaemon standalone container you can use any key you like. Of course, using a publicly available key is not a great idea, but then again consider if you think someone will know the HA key and try to hack your devices, and the cost of re-pairing all of the devices.

However, I do echo the advice of only secure including the devices that need it, so maybe it’s a good time to start over if you’re migrating.

1 Like

The tutorial is telling you can use your own MQTT.
I also believe it is working because I do see activity in the Log?

Assuming you are talking about the post you linked to originally, I don’t think it says that. All it mentions is that an MQTT broker is required.

The OpenZWave Addon requires the MQTT Addon and uses it as the broker automatically. See item #4 in the linked docs.
The OpenZWave Container can use any MQTT broker.

If you want to use your own MQTT broker, then you cannot use the OZW Addon.

I also believe it is working because I do see activity in the Log?

Which log, the open zwave log? If so, no, that has nothing to do with the MQTT part of this. That just shows the z-wave network is up and running and it’s talking to a broker. In the addon case, it’s talking to the embedded broker.

1 Like

Thanks again.
Then I now know why it is not working :relaxed:

It looks like the MQTT part is not working

That explains a lot. My Zwave network is extremely slow.
I will change my setup by switching my secure devices to unsecure.
Thanks for the important tip!

1 Like

I checked my devices today and did find out that about 12 devices out of 40 I did pair secured. ( I really don’t know why I did???)
So today I did unpair these devices and paired them unsecure again.
Now it looks like the zwave network is better responding and I also can change my security key.
I’m happy. Again thanks for this good advice and given information

1 Like