Z-wave problems in 0.79.3

[Tukun (Øyvind)]

I am having problems with hass.io after upgrading to 0.79.3.
When I am trying to toggle a light, the toggle goes back to off immediately after turning it on.
The lamp sometimes turns on, sometimes not. If not and I continue clicking on, nothing happening. The toogle just returns to off position.

This is on a fibaro wall switch.
Anybody else having same z-wave issue?

[tom_l]

Similar problem and advice here:

Switch state too slow

I just installed an Aeotec Nano Z-Wave Switch. Works fine but the state reply is slow. The switch on Home Assistant gives up before receiving the state from the switch. Which looks like it takes sometimes up to ten seconds. (I am watching the state node in node red). In Home Assistant, I turn the switch on and the light controlled by the Nano turns on almost immediately. But since Home Assistant doesn’t see the state, it turns the switch off. Can this state reply timeout be increase, or i…

Check your zwave mesh.
Look at the OZW log.
Check your device has the latest firmware.

[stevemann (Stephen Mann (YAML-challenged))]

Thanks. Since changing parameter 80 from Hail CC to Basic, the problem hasn’t recurred.

[Tukun (Øyvind)]

Thanks!
I can’t find parameter 80. I can see that people suggest firmware update. I can’t upgrade the firmware via Aeotec z-stick right?

[bryanbr (Bryan Bredehoeft)]

Hi Tom_l, having similar problem with Fibaro Wall-Plug + Aeotec Z-Wave USB Stick.
I checked Fibaro’s website and cannot find how to update firmware for Wall-Plug. Is that what you meant?

[Tukun (Øyvind)]

I have done some Googeling.
It seems like the only way to upgrade the firmware on Fibaro products is to go trough their gateway. On other words, there are no way for us to upgrade it trough Home Assistant and Aeotec Z-wave stick.

It’s strange that it is not raised a issue against this, because I know more people having the same problem, where you can’t toggle light on\off.

[bryanbr (Bryan Bredehoeft)]

I will look into logs, I believe it is mesh network that is getting tripped up, so may need to remove device and re-add. Which is always a pain for me.

[tom_l]

Did you map your mesh to make sure you have a god set of redundant paths?

[Klagio]

@tom_l

Check your zwave mesh.
Did you map your mesh to make sure you have a god set of redundant paths?

How do you do that, there is a software for it?

[tom_l]

Z-Wave graph (without the python)

Hi folks. If this is considered bad etiquette, please feel free to kill post. I really liked having the ZWave Graph that @OmenWild had setup, but when I moved my setup to docker last week (hey, I was on vacation and felt the itch to change something). I didn’t feel like trying to figure out why it had broken, and hadn’t liked the external python script method anyway (personal preference, just more things to break). So I satisfied multiple itches at once, and converted what he had written to a …

[tom_l]

@stevemann

Since changing parameter 80 from Hail CC to Basic, the problem hasn’t recurred.

Thanks for the info. I’ve been having problems with an Aeotec smart switch not turning on (it is well connected with three paths back to the controller). Status reports were set to None instead of Hail or Basic. I have another switch that works just fine like this. I’m going to try setting the problem device to Basic.