Zwave stops working after hass 0.50 upgrade

Configuration
1

After upgrade to 0.50 zwave stops working for me. In the ozw log the following messages appear:

Blockquote
2017-07-30 21:07:04.238 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xe199ad88
2017-07-30 21:07:05.239 Info, mgr, Driver for controller /dev/zwave pending removal
2017-07-30 21:07:05.239 Detail, Notification: DriverRemoved
2017-07-30 21:07:05.239 Always, ***************************************************************************
2017-07-30 21:07:05.239 Always, ********************* Cumulative Network Statistics *********************
2017-07-30 21:07:05.239 Always, *** General
2017-07-30 21:07:05.239 Always, Driver run time: . . . 5 days, 2 hours, 37 minutes
2017-07-30 21:07:05.239 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 1082
2017-07-30 21:07:05.239 Always, Total messages successfully received: . . . . . . . . . . 1082
2017-07-30 21:07:05.239 Always, Total Messages successfully sent: . . . . . . . . . . . . 402
2017-07-30 21:07:05.239 Always, ACKs received from controller: . . . . . . . . . . . . . 417
2017-07-30 21:07:05.239 Always, *** Errors
2017-07-30 21:07:05.239 Always, Unsolicited messages received while waiting for ACK: . . 0
2017-07-30 21:07:05.239 Always, Reads aborted due to timeouts: . . . . . . . . . . . . . 0
2017-07-30 21:07:05.239 Always, Bad checksum errors: . . . . . . . . . . . . . . . . . . 0
2017-07-30 21:07:05.239 Always, CANs received from controller: . . . . . . . . . . . . . 0
2017-07-30 21:07:05.239 Always, NAKs received from controller: . . . . . . . . . . . . . 0
2017-07-30 21:07:05.239 Always, Out of frame data flow errors: . . . . . . . . . . . . . 0
2017-07-30 21:07:05.239 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 0
2017-07-30 21:07:05.240 Always, Messages dropped and not delivered: . . . . . . . . . . . 10
2017-07-30 21:07:05.240 Always, ***************************************************************************
2017-07-30 21:07:05.240 Detail, WriteMsg Wait Timeout m_currentMsg=00000000
2017-07-30 21:07:07.246 Info, mgr, Driver for controller /dev/zwave removed
2017-07-30 21:07:08.246 Error, mgr, Manager::GetDriver failed - Home ID 0xe199ad88 is unknown
2017-07-30 21:07:08.246 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2017-07-30 21:07:08.246 Info, mgr, GetSendQueueCount() failed - _homeId -510022264 not found

Has anyone a hint to solve the problem?

2

Wait for a bit until all the components are updated in the background. It could take 15 to 20 minutes. Once done try a reboot.

3

Does not run after waiting for 12 hours. :frowning:

4

Did you reboot?

5

Have you worked through the breaking changes in zwave from earlier versions.

6

Yes, I have no zwave covers.

But I found the problem:

The ozw_config is missing. Before it was in

/home/homeassistant/.homeassistant/deps/python_openzwave/ozw_config/

and now the directory is gone. After removing it in the configuration of hass it works.

One question:

Is the ozw_config with the securitykey obsolete now?

7

I have the same problem you had…

My /home/homeassistant/.homeassistant/deps/python_openzwave/ozw_config/ is gone…

After removing it from the configuration it worked but the communication with my Kwikset lock got worse.
Is there something about the network_key, which is still on the configuration.yaml but I changed the config ozw in that directory…

Do I need to change again (uncomment those lines for the secure nodes) in any other directory now???

Thanks

8

The security key should be in the options.XML file in the config directory or added to configuration.yaml file.