ZWave Freak Out Overnight

I have two binary sensors associated to the Gen 5 Z Wave stick. I used the AIO installer originally. Everything works perfectly during the day. I go to sleep and then nothing works. Here is the error message when I restart home assistant. I think it goes away once I reboot RPI. (To test in a second - just tested, hard reboot of RPI fixes it and sensors are recognized) The only thing I can think of is that the automation of soft reset and heal network overnight somehow breaks it. I’ll remove these automations and test it tonight.

16-06-23 06:49:47 homeassistant.bootstrap: Error during setup of component zwave
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/”, line 72, in init
raise ZWaveException(u"Can’t find device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))
File “/usr/lib/python3.4/”, line 181, in format_exception
return list(_format_exception_iter(etype, value, tb, limit, chain))
File “/usr/lib/python3.4/”, line 146, in _format_exception_iter
for value, tb in values:
File “/usr/lib/python3.4/”, line 125, in _iter_chain
context = exc.context
AttributeError: ‘NoneType’ object has no attribute ‘context

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/”, line 157, in _setup_component
if not component.setup(hass, config):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/”, line 200, in setup
File “/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/”, line 75, in init
raise ZWaveException(u"Error when retrieving device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))
openzwave.object.ZWaveException: ‘Zwave Generic Exception : Error when retrieving device /dev/ttyACM0 : ['Traceback (most recent call last):\n', ' File “/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/”, line 72, in init\n raise ZWaveException(u"Can\'t find device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))\n', ' File “/usr/lib/python3.4/”, line 181, in format_exception\n return list(_format_exception_iter(etype, value, tb, limit, chain))\n', ' File “/usr/lib/python3.4/”, line 146, in _format_exception_iter\n for value, tb in values:\n', ' File “/usr/lib/python3.4/”, line 125, in _iter_chain\n context = exc.context\n', “AttributeError: 'NoneType' object has no attribute 'context'\n”]’


Firstly, the heal automation is no longer necessary as it happens automatically (0.20 I think). But for your (our) setup, the Soft Reset bricks the Z-Stuck until you restart. I had this exact same issue - everything was fine until I kicked of the reset in an automation then everything Z-Wave stopped.

Thanks @aimc. I deleted these from my configuration file. Surprised these are still on the wiki page.

1 Like

How do you disable the soft reset? I was noticing that my zwave was dying in the middle of the night (approx 2;30 - 3:00), figured it was because of the automatic heal. Didn’t realize there was a soft reset in there as well

I actually added the automation myself. I deleted the lines from my automation yaml file. I’ll report back tonight on what happens!

I understand. Thought it was like the Autoheal that is included now