ZWave slow or no response

[covrig]

Home Assistant release: 0.45.0 Python release: 3.5.2 Component/platform: ZWave. Using gen 5 Aeotec. Description of problem: Slow, serious lag (+30s) or no response on Zwave command (toggle on/off switch or light, change color etc.) after the last update. I skipped 0.44. The switch goes back to the previous position by itself. Expected: Immediate response.

Problem-relevant configuration.yaml entries and steps to reproduce:

zwave:
  usb_path: /dev/ttyACM0
  #config_path: /srv/homeassistant/src/python-openzwave/openzwave/config

The zwave config_path was commented out as of 0.45. OZW_Log.txt

[cmsimike]

FWIW i skipped .44 because I didn't want to deal with the manual zwave library install, opting to wait for .45 from .43, and I have not experienced this.

[snjoetw]

I've seems this sometimes with my setup. Check if you zwave device is in "dead" state or not (under zwave panel).

Usually a hass restart will fix dead state. Probably a bug in 0.45?

[covrig]

@snjoetw Sadly, all Zwave devices behave like this. It's something more.

[turbokongen]

From your log:

2017-05-23 20:05:31.005 Info, Setting Up Provided Network Key for Secure Communications
2017-05-23 20:05:31.006 Warning, Failed - Network Key Not Set

Fix that, and all will be good :)

[covrig]

@turbokongen Thanks for the answer. I moved options.xml to the configuration directory (HASS) but for some reason the network key option was commented although it wasn't before. I removed the comment, rebooted the system and I still see this lag and unresponsiveness for all the Zwave switches and lights. New OZW_Log.txt

[turbokongen]

Is it your original network key that you used in your old file? If it is the wrong one, the behaviour will be the same. I ask, because there are no NONCES messages in your log. Also a lot of timeouts on your nodes.

[covrig]

@turbokongen It might be the case, although I just copied the old file (from /srv/homeassistant/src/python-openzwave/openzwave/config - Pi). It should be the original key. Do I have more options.xml files? It's been some time since I played with the network key.

Just as a side note: I have a lot of Fibaro sockets, an Aeotec multisensor, a smart lock, an Aeon energy meter, a Fibaro water sensor and some Zipato bulbs. Everything was fine before the update.

[turbokongen]

Since it was commented out, that tells me it was replaced at some point overwriting your changes to it. If you don't have a copy of the key, your only option is to reset the network and start over with a new key. Just to be clear, you do have secure devices on your network?

[covrig]

@turbokongen I have a secure lock. The network key I have in the file is the correct one. I checked the backups.The lock opens and closes but with a huge delay. I removed it just to debug the problem. The new OZW_Log.txt

[turbokongen]

Yes, last log show that you have the correct key in place. NONCES are transmitted. But, there are timeouts on several of your nodes: 30, 31 and 4. Are these your problematic nodes?

[covrig]

@turbokongen Sorry. Had to go out for a bit. Indeed those are some special nodes. However, all the nodes are laggy and unresponsive now. Well, with node 4 I always had problems but it never influenced the others that much (beside some weird alarms it was sending to the sockets forcing them to switch off.. but I fixed that for some months now). It is an Aeotec Multisensor 6. Node 30 is the lock and it is currently with the batteries removed. Node 31 is a Zipato light bulb. It is a new addition to the group and it is slow as heck and not properly configured for HASS (max brightness is wrong, no temperature control). I had more of them but I removed the rest. Currently it is disconnected.

[covrig]

I am going to close it. I still have the lag but it isn't because of HASS. I think some nodes are problematic.