Some ZWave devices not updating status after moving to ZWave JS

Hello,

A couple of my older ZWave switches do not update status in HA if turned on/off manually. They worked before I moved to ZWave JS. Everything works if I use HA, but it does not work if I do manual switch. My newer switches work without any issues.

Is there any way to fix this? I do not want to use zwave mqtt add-on because sounds like it is not official add-on and will be removed some time in a future.

2 Likes

I’m having the same issue with GE/Jasco switches. I’ll be watching this thread and if I find anything I’ll swing by here to mention it.

I am having the same issues with Inovelli switches. Works just fine turning on and off from the home assistant tab but if I do a manual press, sometimes home assistant doesn’t update the device status.

This may be the same as this issue, reported for older Qubino Flush 2 relays.
https://github.com/zwave-js/node-zwave-js/issues/2012

It looks like that the problem could be because of the older firmware. The older switches have this issue. Do you know if there is a way to update firmware for my light switches?

Any solutions? ZWN-RSM2 here worked fine before

I had to setup Z-Wave JS to MQTT.

I’m having the same issue with my Jasco switches. Anyone found a fix or workaround yet?

I had the same issue with most of my Leviton DZ6HD. It was related to an old firmware, see my post here

Any idea how to update Jasco switches?

Can you explain how that helps if I don’t have Ring devices?

I am sorry, my mistake. I use “Z-Wave JS to MQTT” for this.

1 Like

I just realized I was mistaken. The switches I’m having trouble with are WD500Z-1 by Nortek Security & Control LLC. Anyone seen a fix for those?

I found with my ZWN-RSM2 modules, I needed to update the lifeline to target endpoint 0. The “default” or original did not have a target endpoint. After making the change, all manual switch changes reappear automatically :slight_smile:

how do you change that parameter? I’m quite new to the z-wave stuff, sorry if it’s a simple question.

Via the web interface, select the node you wish to change, expand, select “groups” . You should see an entry for “lifeline” to your zwave master with a “blank” target endpoint (If not, that’s also a problem). Simply add a new lifeline with 0 for the target endpoint. This appeared to address the issue on my configuration (YMMV).

1 Like

thanks. I think that’s my problem, I don’t see any entry for lifelines on my devices that have trouble reporting status of manual switch changes. It’s weird all my dimmers are the same model, some don’t have the lifeline entry and don’t report the status and others have the lifeline entry and report the status properly

Thanks Mike, this solved my problems with my ZWN-RSM2s!

(side note: have you ever gotten an association working with these devices for RSM2->RSM2 behaving like a 3 way?)

I’m having this issue with pretty much all of my nodes. Except when I try to add the group info, I cannot save the entry because there are no groups to apply. One of my nodes has an entry, but its not pointing to an endpoint. When I delete it and reenter the line to point to the zero endpoint, it just goes back to empty…not sure what Im missing here.

When I enter this line with a target endpoint, after hitting save it goes back to none.

image

Specifically for the GE 12730 fan controller, this is an old device and doesn’t support the Association command class. It is not a Z-Wave Plus device, thus there’s no requirement for there to be a Lifeline group association. It’s no surprise then that trying to create non-existent associations would fail. For old devices like these, you need to setup polling if you need accurate state.

In my personal usage, the 12730 will only update its state on single button presses, e.g. pressing the button on or off. It does not report intermediate speeds (holding the on button). Knowing the exact speed was not important for me though, so I didn’t bother with polling.

1 Like