2018-12-02 15:06:14.366 Always, OpenZwave Version 1.4.3254 Starting Up
2018-12-02 15:06:17.171 Info, Setting Up Provided Network Key for Secure Communications
2018-12-02 15:06:17.171 Warning, Failed - Network Key Not Set
Another poster got around the error by moving the network key to an options file, but before I do that, do you see anything wrong with the way I have it now?
A quick scan doesn’t reveal anything wrong and where you have it does work. It is easier to keep backed up and tracked where you have it than putting in options.xml You might just try generating a new one and try again. ???
@fletch101e you need to add the network_key entry in network_key: .storage/core.config_entries
storage is a hidden directory (note the dot preceding storage in the path
I just tried this to check but you can leave the network_key entry in configuration.yaml file and then remove the .storage/core.config_entries. Restart HA and the core.config_entries file will be recreated with the network_key entry.
That worked thanks!
The setting in the core_config_entries had the key set to “null”
I put in my key and restarted. It seemed to take longer to reboot than normal but it worked as no more error message in the log file,
re: your second reply,
So you are saying it needs to be in the core_config_entries just for the first time and I can take it out and put it back to null? Is there any reason I should take it out?
You could have just deleted the core_config_entries file and restarted HA. HA builds the core_config_entries file from entries in configuration.yaml. If the core_config_entries file doesn’t exist it rebuilds the file. What you have now is correct so just leave it.
Ok I think I get it now. If I had put in the key the first time, it would have worked, It only generates the file if it’s not already there.
I want to try and add a switch . Do you know if I need to remove it from my existing hub (wink) or can I just put the switch in inclusion mode and reprogram?
Note there is a way to reset the whole zwave network, but I did not want to do that because:
1 I wanted to make sure Home assistant was going to work before I changed everything over.
2) Right now Home assistant only gives me manual control over my switches. Need to figure out how to make it come on and off automatically at a set time as my outside lights come on at sunset/ off at sunrise
Anyway for anyone wanting to convert from wink to HA one switch at a time, this worked for me.
Go to wink app and exclude the switch. I had to do it 3 times before it worked. I proved this as the switch disappeared from the app.
I then went to HA>configuration>Zwave and then ADD Node…then held down switch for about 7 seconds, then clicked 1 time. Then went back to HA and selected heal network , then hit save.
This worked the very first time.
Hope this helps …
Devices registered to a hub can’t be paired to a new hub without removing the the old pairing. Otherwise someone near by could add them to their hub and control your lights. When adding new devices, fresh out of the package, I always first exclude them, just in case it was a store return that got put back on the shelf.
I kinda figured that but was hoping I was wrong. Thanks for your help the other night. I really thought Zwave was going to be a serious pain to set up and it’s not been bad at all. Wink was more difficult though that was about 4 years ago when they were new.
With help from a couple of guys on this board I got my first timer working last night. Have another one for tonight at sunset. if it works , then I pull the garage light from wink and put it in HA.
Yea I saw that. Honestly it is actually easier to add nodes in HA than Wink. I never would have believed that but so far HA adds the nodes on the very first try. I will probably stay with them for zigbee , though.