Problem with status changes on Aeotec ZW116 Nano Switch

Hi,

I’ve recently bought an Aeotec ZW116 Nano Switch because it was the only Z-wave switch capable of 10A loads that I could find.

The problem is that the UI in HASS fails to correctly update the state after an event have been fired, i.e. the UI says ‘on’ while the switch is actually ‘off’ and vise versa. Is any one else having the same or similar problem and perhaps also a solution to the problem because this is really annoying…

/Magnus

That sounds familiar, happens to my nano switch from time to time. Mine also loses connectivity altogether every 2-3 weeks, and the only way to fix this is to flip the circuit breaker.
To avoid the inconsistent switch state, I am trialing the following config:

zwave:
  ...
  device_config:
    switch.aeotec_zw116_nano_switch_my_switch:
      refresh_value: true
      polling_intensity: 1

I tend to believe that the situation has improved, but can’t say for sure.

The funny is that it all seems to work just fine when I use the “developer tool” available in HASS, so it seems to be glitch in the GUI nothing more, nothing less…

The switch works properly when I use use the developer tools and when it use within automations but the state of the switch is not updating properly in the GUI

What is parameter 80 on the switch set to?

Parameter 80 is set to “Hail CC when using the external switch to switch the loads” which according to the definition in open-zwave file seems to be equal to “3”

Any ideas of what it should be set to work properly in hass?

/Magnus

I “bruteforced” all the options, which was kind of fast due to only 4 options and now it works… I now use mode 1 (basic) on parameter 80

So many kudos to squirtbrnr for your input!

/M

You beat me to it before I could reply. Setting parameter 80 to basic reports is probably best. Hail CC floods the z-wave network with reports on every little change and can cause communication issues.

Also the state of the switch may not update properly if the gateway is not a direct neighbor of the device. I have a few switches where physical interaction doesn’t update the switch in HA because they are too far from the gateway so they must be polled even though there is a “repeater” in between. Repeaters don’t repeat broadcast messages from devices other than the gateway. But broadcast messaging is how some devices get around the licensing issue of instant status updates.

1 Like

Hi!
Have you fix this problem?

Did you read the whole thread? The 2 posts before yours provide the answer.

Thank you.
Where can I find and change this parameter?