I have two shade devices and an automation that sets them to 50% in the middle of the night. I leave up a dashboard with those devices on it. Up until recently, when I looked at the dashboard, the two shades showed 50%. Recently, however, the dashboard shows one at 0% and one at 50%. I happen to know that they were both at 0% when the automation ran. And I happen to know that the physical shades were both at 50% in the morning.
I refreshed the dashboard and that didn't help. Then I looked at the offending shade device and it showed 0%. When I tapped the Refresh command it instantly updated to 50%. It strikes me strange that Hubitat can't keep track even when it tells the shade to move.
I'm wondering whether this was broken in a recent firmware update? I'm running 2.3.5.121 on C-5 hardware.
Changes to hub firmware have primarily to address issues with the new C-8 hubs. I guess it is possible that something changed in the C-5 firmware as well, but I suspect that is unlikely. If you have backup of earlier firmware, you can always roll back to an earlier firmware and see if that fixes the issue.
Remember that the Lutron devices are being controlled directly by the Lutron Pro hub. The integration between the Lutron Pro hub and Hubitat hub area only to allow Hubitat to trigger Lutron events and to receive status update from Lutron.
You also indicate that you were checking the device status in the dashboard. Thus, there is another interface between Hubitat and the dashboard that might be problematic.
Use the Lutron app on your smartphone to find out if Lutron is controlling the shades properly and reporting the status properly. Since the issue seems to affect only one of the two Lutron shades, the problem is likely related to one of the two shades. That device might not be reporting status properly back to the Lutron hub.
It's unlikely the problem is on the Lutron side, unless Hubitat is expecting a push notification that never comes. The shades are controlled correctly as determined by visual inspection!
The story gets stranger. I poked around the devices and the Lutron app trying to see if a setting was off. I had other shades that get closed by automation at night, and for years the dashboard never showed the right values in the morning. Now, after poking around, I noticed that all of the dashboards are working correctly. No change to the configuration, shades or the Lutron hub. The issue is (was) clearly on the Hubitat side. Maybe something in the Lutron app needed to update itself. Who knows, but if it keeps working I'm happy.
Does Hubitat poll the hub or expect notifications? Is it possible that it wasn't polling correctly and calling up the app fixed that?
BTW, I'm looking forward to transferring my config to my newly-arrived C-8 hub.
Well, it stopped working again. Rebooting the hub didn't fix the problem. I have two shades that are identically configured. I manually closed both of them by dragging the sliders to 0, one after the other.
As you can see from the Lutron Telnet log, the commands sent to the Lutron Hub and the responses received are identical for device 14 (Middle Shade) and 15 (Right Shade). However, the Middle Shade sets the position to 0 and correctly goes into the Shade is closed state, whereas the Right Shade only gets one event, "Right Shade is closing" at 01:08:24.502 and lacks the other three events. Since the hub is receiving the exact same stream from the Lutron for both shades, the problem seems to be on the hub side.
It's almost like the second message about device 15 at 01:08:25.565 is getting lost in the hub.
I've worked around this (mostly) by using Metering set at 500ms. I could probably go lower.
There's clearly a bug here somewhere. How do I get some attention to this? Even an acknowledgment that the issue is on the bug list would be appreciated.
I found it best to create a group of shades (a scene in the Lutron app) then in Hubitat's Lutron integration app, add a device of type k (keypad) with id 1.
Open live logging and observe the button id of the pushed event as you execute each scene in the Lutron app.
Then just build a rule to send a button push event with the specific button id to the Lutron Keypad device.
