Zwave implementation

So, I have been on HA for some time now. I have really enjoyed messing with the interface and adding devices but…….

The Zwave implementation is really lacking. I don’t even know where to start other than ALL of my zwave devices don’t update correctly? From my thermostat to light switches all of them eventually fail to update.

Does anyone have a fix for the updating a zwave device?

For example I just bought a Ecolink Flood/Freeze sensor. Thinking that it would update correctly but no it doesn’t. Just like my thermostat (zwave) it doesn’t even know what universe it’s currently in and I never know what or when my device is active or not.

Just disappointed that it (zwave) worked well in Smartthings but in HA, I couldn’t tell you via the interface that a zwave action is happening or not because most of the time it’s just stuck on the last thing it communicated. So, why can’t zwave be updated like everything else? Can you ping the devices so we know what is happening?

Just frustrated and not wanting to move everything over to Wi-Fi connected devices.

Please step up your game Home Assistant or how can I help you help me or the community!

You can start your troubleshooting by mentioning what Z-Wave integration you are using!

I’m pretty sure that the current preferred integration is Z-Wave JS to MQTT, and I have never observed ANY of the problems that you’ve described in my two months of using it. The web interface does Z-Wave pings, shows connection stats, and even draws a connection diagram to show how each device is connected in the mesh…

2 Likes

Sure, I think I listed a device above but the other device is a CT-101 thermostat and other GE zwave switches. I am currently using Z-Wave JS to MQTT and can get a sensor to update by refreshing the device in the console. Do you know how to do that? Just curious because you never ever had an issue with the Zwave module in HA.

I am not saying that you might not have an issue but there is an issue for sure. Maybe there are other explanations other than yours. Just saying…

I addition to thebother info what kind of ZWave stick are you using?

1 Like

The original (ancient) GE Z-Wave switches were known to have problems reporting their status to controllers. Hubitat deals with them by offering a Z-Wave polling app, that periodically queried those devices and updated their status in the hub to match. The last of my ancient GE Z-Wave switches phased itself out (died) right before I migrated to HA, so I do not know if/how a similar Z-Wave polling is implemented in HA…

I am using a GoControl HUSBZB-1.

As for the GE switches, you are absolutely correct. I never had issues with them or status polling issues but I am down to my last few. I only have an issue with 1 and not all of my switches. And yes it’s one of my GE switches.

As I look in HA this morning my Ecolink sensor I just added yesterday still shows the wrong poll. It still shows wet and not clear. It’s got a red light on the device that when its wet it will turn on the red light. The light is off and HA says it’s still wet.

Look under the disabled entities for that device, enable the binary_sensor, and disable and forget about the one that currently isn’t working.

I have enabled all devices and found one that works correctly. Haven’t added a new zwave sensor for ever and forgot about the disabled sensors. Thank you.

There are a handful of “special” devices, including that Ecolink, where the disabled entities are the working ones. Not really obvious unless you happen to already know…