Z Wave mesh stopping working

Hello. Funny I was just about to post my “findings” since it has been stable for almost a week now. I had a micro 128GB usb stick in the RPi and it had been working fine for months, it was for my backups of the SD card.

I took it out as a test and it was scorching hot, I mean hot hot! It never got hot before. So I have taken it out and replaced with about usb storage and it has been perfect. I think the heat from it must have caused issues with the USBs

Very very odd one

Fingers crossed it was just a faulty usb device!!

Year, well I think, this still fits the power issue. Because if it gets hot, it obviously drains power.
I think the following is happening.

  1. you turn on HA and everything works fine. In the beginning. The power budget is not exhausted right away.
  2. but eventually multiple devices will drain power at the same time, and you pi cant keep up. Thus you zwave stick might fail occasionally because its not getting enough power.
  3. Now there seems to be another bug that kicks in. I guess its either the driver or open-zwave, that are not able to recover the zwave stick correctly. It ends up in some kind of stall state, where it still works partially.

Thinking about it, because we can recover our network just by restarting HA, I assume it is acutally open-zwave that fails. Maybe we have to bring it forward to them.

In my case, I could switch the connection of the zwave stick from a multiport adapter to a native usb port. Its only running for ~5h yet, but I’m positive, that it is fixed by now.

Zwave worked fine with the reduced baudrate, until the 0.52 update this weekend. Now it’s a complete disaster. Anybody else having problems with 0.52?

Hello all, turned out that my zwave issue was power supply related as well. It wasn’t the power supply itself, but the USB cable between the powersupply and the Pi3. After changing that cable for one that felt a bit more sturdy/thicker, my zwave problems have disappeared.

I’ve also been having lots of Z-Wave issues probably for the last 10 versions. It could go a month without issues, but lately it’s been daily. My issues are ONLY with Z-Wave, and my ZigBee stuff (via Xiaomi Gateway) have been solid, and fast. Like others here, I’m using an Aeotec Z-Stick Gen5, but unlike others here, I am running HASS in a CentOS 7 LXC ontop of Proxmox 4, with the USB device passed through. I just enabled debugging in zwave config, and immediately saw this, not that I have a clue how to resolve.

2017-09-03 05:18:35 ERROR (Dummy-24) [openzwave] Error in manager callback
Traceback (most recent call last):
  File "/opt/homeassistant/deps/lib/python3.5/site-packages/openzwave/network.py", line 948, in zwcallback
    self._handle_value_added(args)
  File "/opt/homeassistant/deps/lib/python3.5/site-packages/openzwave/network.py", line 1478, in _handle_value_added
    'value' : self.nodes[args['nodeId']].values[args['valueId']['id']]})
  File "/usr/lib/python3.5/site-packages/pydispatch/dispatcher.py", line 338, in send
    **named
  File "/usr/lib/python3.5/site-packages/pydispatch/robustapply.py", line 55, in robustApply
    return receiver(*arguments, **named)
  File "/usr/lib/python3.5/site-packages/homeassistant/components/zwave/__init__.py", line 287, in log_all
    pprint(_obj_to_dict(value))
  File "/usr/lib64/python3.5/pprint.py", line 53, in pprint
    printer.pprint(object)
  File "/usr/lib64/python3.5/pprint.py", line 139, in pprint
    self._format(object, self._stream, 0, 0, {}, 0)
  File "/usr/lib64/python3.5/pprint.py", line 167, in _format
    p(self, object, stream, indent, allowance, context, level + 1)
  File "/usr/lib64/python3.5/pprint.py", line 189, in _pprint_dict
    context, level)
  File "/usr/lib64/python3.5/pprint.py", line 346, in _format_dict_items
    context, level)
  File "/usr/lib64/python3.5/pprint.py", line 176, in _format
    stream.write(rep)
UnicodeEncodeError: 'ascii' codec can't encode character '\xf4' in position 10: ordinal not in range(128)

Any ideas what might have \xf4 and why it’s giving problems? Not sure if that’s related to my issue, but my symptoms are just like others in this thread.

Hi all. Just an update on my original issue. After trying different power supply, different HASS versions, etc., the only thing that worked was getting the Zstick closer to the switches.

Originally I was within range per Z-Wave specs (about 60ft from switches, now it’s about 5 ft); however, old home, plaster walls, etc. the only thing that resolved the problem was moving the controller. No issues since then, about 6 weeks now.

Mine has also been stable since moving to a docker on my NAS. However I am removing z wave devices and replacing with flashed SonOff devices.