Home Assistant dies after running for a while

Configuration
1

Hi everyone,

Unfortunately, my home assistant dies after running for a while. I am running Hassbian on a Raspberry Pi 3+. I checked over SSH with systemctl systemstatus before leaving home today and got this output:

Feb 18 07:10:23 hassbian hass[1379]: File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/zwave/node_entity.py”, line 51, in maybe_schedule_update
Feb 18 07:10:23 hassbian hass[1379]: self.hass.add_job(self._schedule_update)
Feb 18 07:10:23 hassbian hass[1379]: File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py”, line 246, in add_job
Feb 18 07:10:23 hassbian hass[1379]: self.loop.call_soon_threadsafe(self.async_add_job, target, *args)
Feb 18 07:10:23 hassbian hass[1379]: File “/usr/lib/python3.5/asyncio/base_events.py”, line 618, in call_soon_threadsafe
Feb 18 07:10:23 hassbian hass[1379]: self._check_closed()
Feb 18 07:10:23 hassbian hass[1379]: File “/usr/lib/python3.5/asyncio/base_events.py”, line 357, in _check_closed
Feb 18 07:10:23 hassbian hass[1379]: raise RuntimeError(‘Event loop is closed’)
Feb 18 07:10:23 hassbian hass[1379]: RuntimeError: Event loop is closed

I am not very good with Linux and all that. Anyone that can give me instructions on how I can figure out what’s wrong when I get home tonight?

2

Software is pretty stable so usually run forever unless you run out of storage, run out of memory or hardware issue.

Some people have issue with SD card failure or db get to large and eat all storage that cause this issue.

Verify there is storage remaining on device
After, maybe swap in another SD if you have handy.

3

Seems to be a Z-wave issue, but I have no idea why that would crash the frontend…

2019-02-20 15:14:07 ERROR (Dummy-27) [openzwave] Error in manager callback
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.5/site-packages/openzwave/network.py”, line 952, in zwcallback
self._handle_value_changed(args)
File “/srv/homeassistant/lib/python3.5/site-packages/openzwave/network.py”, line 1504, in _handle_value_changed
‘value’ : self.nodes[args[‘nodeId’]].values[args[‘valueId’][‘id’]]})
File “/srv/homeassistant/lib/python3.5/site-packages/pydispatch/dispatcher.py”, line 338, in send
**named
File “/srv/homeassistant/lib/python3.5/site-packages/pydispatch/robustapply.py”, line 55, in robustApply
return receiver(*arguments, **named)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/zwave/node_entity.py”, line 138, in network_node_changed
self.node_changed()
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/zwave/node_entity.py”, line 179, in node_changed
self.maybe_schedule_update()
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/zwave/node_entity.py”, line 51, in maybe_schedule_update
self.hass.add_job(self._schedule_update)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py”, line 246, in add_job
self.loop.call_soon_threadsafe(self.async_add_job, target, *args)
File “/usr/lib/python3.5/asyncio/base_events.py”, line 618, in call_soon_threadsafe
self._check_closed()
File “/usr/lib/python3.5/asyncio/base_events.py”, line 357, in _check_closed
raise RuntimeError(‘Event loop is closed’)

4

Maybe zwave logging or docker logging

Found this yesterday

5

Side note…

I noticed memory links or high cpu use in other app containers crashing HA a while back.after that I began limiting could and RAM for my containers to 1.5 or double Dev recommendations for all my containers

I’ve also had system updates affecting python affect HA or docker if I didn’t reboot shortly after

6

Hmm, that could be the thing yeah. I am running Hassbian, which is in a virtual environment. No clue how that works compared to docker. Could this still be the case?

7

Zwave issue…yes.

Sorry, mixed your issue with someone having similar with do keep install

Would still look at storage/SD card to be sure