Closed jmgiaever closed 3 years ago
The key is specified with the OZW_NETWORK_KEY
environment variable, which is not set in your docker command. It is missing from the example in the instructions, but the docker compose example and the list of supported environment variables show it. https://github.com/OpenZWave/qt-openzwave#using-the-standalone-image
Hi,
Thanks for your reply, but it doesn't seem to help to add
-e OZW_NETWORK_KEY="0x65, 0x79, 0x17, 0x3B, 0xE0, 0x8C, 0x3F, 0x7F, 0x8F, 0xB1, 0x13, 0x90, 0x06, 0x00, 0x74, 0x6A"
to the command. The log now states:
2020-11-07 21:25:42.184369742 [20201107 21:25:42.184 UTC] [ozw.daemon] [info]: Network Key Specified in Enviroment is Valid
But
[...]
2020-11-07 21:25:45.834496136 [20201107 21:25:45.834 UTC] [ozw.library] [info]: Info - Node: 255 Encrypted Flag is 0
[...]
2020-11-07 21:44:21.603846939 [20201107 21:44:21.603 UTC] [ozw.library] [info]: Info - Node: 1 Encrypted Flag is 0
I tried to reset the device too, by pressing the «action button» on the back of it for 20 seconds until it flashes blue.
EDIT: Pressing «add node» results in
2020-11-07 21:47:23.424830630 [20201107 21:47:23.424 UTC] [ozw.mqtt.commands] [info]: Processed Message for "addnode" : "{\"secure\": false}"
You are including it unsecurely.
There is no other option than «add node» (except from remove node). Should there be a button «add secure node», like the built-in Z-wave integration of Home Assistant? If so, I guess it's not there because the key is not applied to the stick?
That would be a question for Home Assistant (the answer is yes, it will be added).
ozwdaemon is working correctly, you've now got the key properly added and so you just need to turn on the secure flag when you add it. For now, either use the service call in HA, use MQTT, or use the ozw-admin application.
Just to clearify:
You never added the node securely, so what are you expecting to happen?
The USB-stick? How do I add it securely, except providing the network key for the command?
USB-stick = Aeotec Z-Stick Gen 5 = Controller
Like you said, HA doesn't have a secure add button.
you just need to turn on the secure flag when you add it. For now, either use the service call in HA, use MQTT, or use the ozw-admin application.
Those are the 3 options.
Again, thanks for your reply, but this new «integration» is somewhat lacking documentation to make it easy for users to move over to the new solutions. I appreciate that you take you time to guide me through this.
I though that the «add secure node» maybe was missing because the network-key "was missing". The configuration tab also said the key was =0 and the log said the stick had «Encrypted flag is 0».
I have succesfully added the node securely with
{
"secure": true,
"instance_id": 1
}
from Home Assistant.
Can I kindly ask if you are using HA? Is it so that it should not be an «add secure node» button? For what I see in the OZW impl of HA, they try to determine if it secure or not. I'm just trying to find out where to file the bug that it doesn't show up in my installation.
Remember the OZW integration is in beta, and the UI especially is a work in progress. It is not complete at all. The missing secure option is known. Feel free to submit an issue/feature request with HA (not here) if you are concerned though. https://github.com/home-assistant/frontend/issues/new/choose
For what I see in the OZW impl of HA, they try to determine if it secure or not
I'm not sure what you mean by this. The code you linked is the service call. It's just assigning the secure flag based on the parameters you set.
Yes, I do remember. But I also hope that feedback from users will help make it better.
Thanks for your help.
Hi,
Sorry. Not sure if my subject is good, but I'm not sure what is wrong as I'm not able to add secure nodes with ozwdaemon. My stick is an Aeotec Z Stick Gen 5 (not the revised version). I guess it's something that is not applied to the stick upon boot.
I'm booting with the following command:
It boots successfully, with the following output:
I'm honestly not sure what the problem can be, but I have tries to change the network key many times. I've also tried to remove spaces from
to
and use lowercase characters without success as I read that someone had success with removing them. Also tried to use lowecase letters too.