My HAs server just died - something Z-Wave is responsible

Hi,

I’m sitting at work minding my own business when I receive a monitoring alert telling me my HAss server is not contactable. Since it’s lunchtime(ish) I SSH in to the machine at home to see what’s going to.

Long story short - HAss can’t restart and the only thing in the log after the usual startup stuff is this message every 60 seconds

2018-09-20 14:12:20 ERROR (Dummy-39) [openzwave] Error in manager callback
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/openzwave/network.py", line 982, in zwcallback
    self._handle_notification(args)
  File "/usr/local/lib/python3.6/site-packages/openzwave/network.py", line 1576, in _handle_notification
    **{'network': self, 'args': args})
  File "/usr/local/lib/python3.6/site-packages/pydispatch/dispatcher.py", line 338, in send
    **named
  File "/usr/local/lib/python3.6/site-packages/pydispatch/robustapply.py", line 55, in robustApply
    return receiver(*arguments, **named)
  File "/usr/src/app/homeassistant/components/zwave/node_entity.py", line 126, in network_node_changed
    self.node_changed()
  File "/usr/src/app/homeassistant/components/zwave/node_entity.py", line 167, in node_changed
    self.maybe_schedule_update()
  File "/usr/src/app/homeassistant/components/zwave/node_entity.py", line 51, in maybe_schedule_update
    self.hass.add_job(self._schedule_update)
  File "/usr/src/app/homeassistant/core.py", line 218, in add_job
     self.loop.call_soon_threadsafe(self.async_add_job, target, *args)
  File "uvloop/loop.pyx", line 1258, in uvloop.loop.Loop.call_soon_threadsafe.   
  File "uvloop/loop.pyx", line 603, in uvloop.loop.Loop._call_soon
  File "uvloop/loop.pyx", line 607, in uvloop.loop.Loop._call_soon_handle
  File "uvloop/loop.pyx", line 636, in uvloop.loop.Loop._check_closed
RuntimeError: Event loop is closed

As I said, that just repeats every 60 seconds. Nothing else is happening

As I mentioned I haven’t touched it. Numerous restarts haven’t changed anything.

Anyone know what this error is trying to tell me? Or why something just decided to break?

Thanks

Steve