My zwave network has stopped responding. Last lines of the OZW log:
2018-11-17 21:39:54.914 Info, mgr, Driver for controller /dev/ttyACM0 removed
2018-11-17 21:39:55.915 Error, mgr, Manager::GetDriver failed - Home ID 0xe9b633bd is unknown
2018-11-17 21:39:55.915 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2018-11-17 21:39:55.915 Info, mgr, GetSendQueueCount() failed - _homeId -373935171 not found
Any idea how to rectify this?
Is that after shutting down HomeAssistant?
Well I was making a number of changes to HA so I did restart repeatedly today.
Unplugging and replugging the usb zwave stick and restarting HA seems to have fixed it.
One more reason to drop zwave.
Nothing wrong with Zwave, the errors you posted I’ll try to break down.
2018-11-17 21:39:54.914 Info, mgr, Driver for controller /dev/ttyACM0 removed
This is the Zwave network being stop, completely normal when you shutdown HA.
2018-11-17 21:39:55.915 Error, mgr, Manager::GetDriver failed - Home ID 0xe9b633bd is unknown
2018-11-17 21:39:55.915 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2018-11-17 21:39:55.915 Info, mgr, GetSendQueueCount() failed - _homeId -373935171 not found
These bits are because something was attempting to send a Zwave command, likely a polling request, after the network was stopped, again completely nothing abnormal.
Keep in mind a network wide heal command goes out around midnight each night to keep the mesh network healthy. This does cause a bit of latency but it usually doesn’t last long.
How many nodes are on your network?
Are any of them mains powered?
Any battery powered nodes?
Thanks for the information. All I know is:
I had no zwave sensors. I could not heal or start the network. HA restart did not fix it. I had to physically unplug the USB stick, plug it back in and restart HA to get my senors back.
None of my sensors are battery powered.
The last person who had that issue ended up fixing it by replacing their Pi’s power supply.
Do you by chance happen to be using a Pi as well?
I do use a Pi. With a 7Amp 5V meanwel power supply. Power isn’t the problem. Something went wrong during the many restarts for config updates I did yesterday.
I have the same exact issue. Zwave network stopped working after multiple restarts of zwave. Here is my OZW log:
2019-01-28 17:20:24.354 Always, OpenZwave Version 1.4.3322 Starting Up
2019-01-28 17:20:36.698 Info, Setting Up Provided Network Key for Secure Communications
2019-01-28 17:20:36.699 Info, mgr, Added driver for controller /dev/ttyAMA0
2019-01-28 17:20:36.699 Info, Opening controller /dev/ttyAMA0
2019-01-28 17:20:36.699 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2019-01-28 17:20:36.699 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2019-01-28 17:20:36.700 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-01-28 17:20:36.700 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-01-28 17:20:36.701 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-01-28 17:20:36.701 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-01-28 17:20:36.701 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-01-28 17:20:36.701 Detail,
2019-01-28 17:20:36.701 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-01-28 17:20:36.701 Detail, contrlr, Notification: DriverFailed
I’ve also seen this issue and also solved it by plugging the ZWave stick into a different USB port…from what I’ve noticed, ideally the ZWave network should be fully up (i.e. all non-battery devices marked as “ready” in HA) before restarting, otherwise it will cause issues.
I’ve also tried plugging the zwave stick into different ports as well but it didn’t help the issue. I also factory reset the zwave stick.
You’ll need to fix the path to your USB stick. Are you running Hass.io?
Check your zwave configuration in the Configuration > Integrations > ZWave menu
Thanks for the reply. I’m not using Hass.io. Is there some config file I need to update that I don’t know about? I just set the path of the z wave stick in the configuration.yaml file. I have a z wave tab in HA but no nodes are showing.
Enter the command: ls -al /dev/tty*
If you see a ttyACM0 try changing your config to use /dev/ttyACM0
Hi. Thanks for that. I did change the path to dev/ttyACM0 a few days back but the problem still persists. I also bought another z wave stick but it did not fix the problem so I can rule out the hardware itself. I also read about the pi3 having issues with using the same port at WiFi and Bluetooth. I disabled those on the pi3 but that did not help either. At this point I might just reinstall.
Try this: sudo apt-get install libudev-dev
Another good suggestion. I have tried reinstalling that too but it didn’t help.
Does the log show ACM0 attempts when you changed it?
You know the logs still shows binding to AMA even though I state A C M in the configuration.yaml file.
01-30 01:28:47.285 Info, Opening controller /dev/ttyAMA0
2019-01-30 01:28:47.286 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
Plugging the USB stick into another port usually changes the device tty identity ttyACM0 and ttyACM1 There are other situations that can cause the device ID to change. To avoid this use the result of
ls -al /dev/serial/by-id/ in your configuration. That value will not change.
What device are you using?
