Devices not always showing correct status in Hubitat

I'm new to Hubitat so please be kind since this is all new. I did read a lot on this forum trying to make it work before starting a new topic.

I'm finding the reporting of the device's current state to not always correct. For example, a light will be off but the dashboard and the device detail will show that it is on. I will need to hit refresh to have it update to the correct state of the device. I also noticed a few times that devices in my rules, groups, or scenes not always turning on(or off) devices when commanded. This problem is very random so it is very hard for me to troubleshoot the cause. In the 6+ months of using the Qolsys panel to control my zwave devices, I don't remember ever having this problem. It has been rock solid and always showed the correct state of the zwave devices.

Some history....

Only owned the Hubitat for 2 weeks and moved my z-wave devices from my Qolsys alarm panel to Hubitat for better control and automation ability. The Qolsys automation was very limited and could only, in my opinion, do very basic automation. All of my zwave devices are new (less than 7 months old) Jasco/GE zwave plus devices, except 1 zooz Water Valve, Minostat MP21Z outlet switch and 5 Singled Zigbee bulbs. All for Zwave Plus devices and s2 capable. No battery-operated devices.

I first started excluding all of the zwave devices(51 devices) from the Qolsys panel except zwave door locks and zwave garage door controller. That went very smoothly. Then started adding the zwave devices to Hubitat with the closest devices first to build a solid mesh network. All devices were added with S2 security. I did notice, which I thought was odd, that two devices never asked for the S2 5 digit code so they weren't added with security. I didn't think that would matter since they were only light for lighting control and one zooz water valve. In troubleshooting, I did exclude and reinclude all devices that were missing security so they are now all S2.

I did integrate the Qolsys panel into Hubitat so I can see current alarm states and when contact sensors are opened for automation uses. FYI, I did notice the issue with device states not always updating before I integrated the Qolsys panel into Hubitat so I don't think that is the cause of my problem.

What I have done so far, looked for ghost devices, repaired mesh, made sure the hub is updated, proper shutdown and restarting of hub after leaving power off for 20+ minutes, made sure the correct device drives were used, and power cycled all zwave devices.

Additional information, on the Zwave details page in setting, all devices have at least a LWR RSSI: +20dB and all device show a single route to the hub...if I'm reading it correctly.

Does anyone have anything that I should check? Any help would be appreciated.

Kenny


1 Like

I believe the short-hand is TL:DR... but I'm not one to use those online things...

But I am also not one to read long posts, like I am also inclined to post :-).

The crux of what you should establish to begin with is does the status in the Device Details page for each device report correctly. If this is the case, then that is good. If not, then it is likely something in the communication between the device and HE that is the problem. If the status on the Device Details page is consistent, then you need to investigate further downstream, in automations and/or other apps of interest.

Once you establish this, then we can move on to what may be the next focus of troubleshooting.

Are the switches in question "regular" Z-Wave or Z-Wave "Plus"??

1 Like

I was worried the first post was getting too long:grinning:

Here is an example of what I last remember seeing, The bathroom light was off but my dashboard will show the light is on. If I go to the device details page for the light, its current state will show as on until I hit refresh.

All zwave devices for Z-Wave Plus.

I've found that it depends on which dashboard link you are using, Local or Cloud. I'm almost always using the dashboards while I am home. The local dashboard stays in sync, the cloud dashboard stops staying in sync after a while and needs to be refreshed to show the correct status. Because of this I always use the local dashboard unless I am away from home.

Maybe someone can explain why my water valve didn't close when it was commanded to close from within a rule.

The Water Valve event shows a "command-close" but the device's current state shows open. Am I missing something? I can press the "close" from within the device details...the valve does close correctly.

Screenshot 2024-01-01 163208


It seems your system has some kind of problem receiving the status back from Z-Wave devices. I appears the water valve (also Z-Wave) may be acting the same way.

1 Like

@Eric.C.Miller may be correct in that there may be an issue with the device communicating with HE, but the two debug log entries of a close immediately followed by an on is interesting, although that doesn't seem to be reflected in the Events....

What driver are you using for the device?

Beyond this, unfortunately Z-Wave and water valve's are two things I don't have experience with, so not sure how much more help I may be...

It looks like @jtp10181 's Titan driver, so I wonder if anything jumps out at him. I'm using that driver on my 2 Titans, and it's been awesome.

@kenny_a_davis - is the Titan's firmware up-to-date? Latest is v1.19

1 Like

The water valve problem I just showed was the most recent thing I noticed. It doesn't seem to be just one device that is having problems, so I don't think it has anything to do with the Titan water valve driver. The last few times I tested the rule that closes the water valve, it worked fine.

Could help to do the following:

  • Open a Live Logs page, ensure info and debug logging is enabled on devices and the automations, and then execute any automations that you have noticed are resulting in failed responses from devices. Share those logs for the device(s)/app. You can filter which devices/apps show up in your logs using this field at the top of the logs page:
    image

If you can catch a devices not updating and capture device & app logs that may help to get a better understanding of what's not working

LAN integrations can sometimes overrun the hub w/messaging - are you running any other LAN integrations aside from the Qoisys integration?

1 Like

Some sort of Z-Wave mesh issue is most likely.

The command-close means the command was called. The lack of a follow up event report from the device could mean either that it never got the command, or that it changed state but the reply never got back to the hub.

This could possibly be resolved with a proper outbound supervision implementation on the driver but it is a PITA to do correctly. This could be setup to retry commands if the device does not reply to the supervised requests.

2 Likes

So how common is it for a device not to follow up that it was turned on or respond to a command? I seem to be seeing it very often.

Tonight, All of my outside light didn't turn on when activated by the room light app. Three devices, porch, pole and driveway light. The porch is showing that it is off.

In the device event, it shows command-on but nothing after...

If I refresh the device it still shows off, does that mean Hubitat sent the command but the porch light didn't receive the command from Hubitat?

Most likely

Not very common at all. Usually it would be the message got lost somewhere. This is not common with a solid mesh. Like I said above, points to mesh issues.

1 Like

What is the best way to troubleshoot mesh issues? Is there something I should be looking for specifically on the zwave details page to find mesh issues?

See Z-Wave Issues section on this post: ‼ READ FIRST - Before Posting in Get Help

I see you posted the details up above, I will see if I can spot anything in there.


Mesh looks pretty good, how long since last reboot when you took those screenshots?

I don't see anywhere that you said what hub model you have and what platform version it is running?

Leaning towards possibly some other issue on the hub causing a problem. Go to past logs and filter by error and warn types, post a screenshot of whatever shows up.

I’m wondering if it’s the 50 devices included with S2 security that’s overwhelming the mesh and causing messages to be lost. I’ve never heard of anyone doing that.

I think @coreystup can speak to that. He has stated before he uses all S2 and has no issues.

It does not really add much overhead, and there are 0 packet errors listed.

It is possible that the devices having issues do not handle S2 very well (device firmware), or that the driver being used is not properly coded for S2 devices looking for supervision responses.

1 Like

What driver are your Enbrighten switches/dimmers using?