Switch not updating status

I have a Leviton Dimmer that will not update status if it’s on or off. The unit works with manual control within the app
This is a new issue after a recent update.

I have a rule that triggers based on the light Turning in and it’s stopped recently.
Switch is currently off.

Could you confirm that the device is Z-Wave plus? If not, is it setup in the Z-Wave device poller app?

Assuming it is either a plus device or setup in the poller app, it might be that the hub and the device are not properly communicating. This could be due to a Z-Wave mesh issue. Posting the Z-Wave mesh details will allow community members to help identify potential issues.

Finally, to confirm the issue was not introduced with the last platform version, it is possible to go back to the previous one by going to http://Hubitat.local:8081

1 Like

This is a ZWave Plus device

I am 1-2 months in from ST to HE swap.

ST just did mesh’s repair so I’m no Preevy in identifying mesh details

This device is further out that some but not the furthest away from the hub.

There could still be Z-Wave issues, especially if some devices didn’t pair correctly (called “ghost”). Sharing a (or multiple) screenshot(s) of your Z-Wave details will allow community members to identify potential mesh issues, including the presence of Ghost devices.

These can cause havoc on the mesh (I experienced that a while back and got some great help from the community!)

Also, if your Z-Wave firmware is not updated to the last version, it should be as there are some fixes that were made available from Silabs that are present in the latest versions. You can look for a “Firmware update” button on the Z-Wave Details screen.

1 Like

I removed the device and added it back. It’s reporting now.

As far as the ZWave firmware update I started to do this but the notes stated you may have to remove and add devices back.

I have over 60 devices that are Z wave. I was unwilling to risk it.

1 Like

I’ve not heard of anyone having issues with the ZWave firmware update, but I understand.

Glad to hear it’s reporting now!

2 Likes

You're confusing two different things:

  1. Updating the hub's z-wave radio's firmware, which is the button indicated in @Sebastien's response to your post. You need to do this for a stable z-wave network because the initial firmware provided for 700-series controllers had many defects in it. Updating this firmware will not make you have to exclude/include any devices.
  2. Updating the firmware of individual z-wave devices, which is done in a different app. This may require you to exclude/include the device whose firmware was updated. Updating the firmware of individual z-wave devices is entirely at your discretion - and most often not necessary.
3 Likes

I will check that and update. I have several other issues now. Govee and Hubitat apps not working, local app connection. Etc. I’m digging through all of these issues at this moment

Some of these issues may be caused by the hub’s z-wave radio getting inundated by messages from devices.

I got it back up. Two reboots

I tried the ZWave Firmware update. It just sits there for awhile.

Are there any errors in the logs?

Once I got the system running again. I wanted to wait to try tonight. I will try and report logs tonight.

Should the ZWave firmware update be pretty quick ?

1 Like

The Z-Wave Radio’s firmware update should indeed be relatively quick. Though I think it can take in the 15 minute range sometimes… It’s been a while since I updated…

1 Like

This si what i get when i try the ZWave firmware update. My hub has continued to act up on certain Zwave devices... Normally a reboot or two solves it but I am not use to having to reboot alot like


this..

Can you post a screenshot of your entire z-wave settings page after a power-cycle? For the power-cycle, do a shutdown from the menu.

1 Like

That’s not normal - I wonder if these issues might not be related… I’ll second @aaiyar’s recommendation to post your entire Z-Wave settings page.

1 Like

What I have noticed is a lag in device response. Once the lag happens, the devices stop updating and rules stop firing.
I then need to reboot.

This AM before I left for work, a rule stopped firing- this rule was based off a Z wave switch position.
Below are my ZWave Details






1 Like

There are 5 ghosts that should be removed - 0x25, 0x2B, 0x39, 0x3D, 0x4F

1 Like