For some reason, none of the Strip devices react to On/Off commands immediately. The commands get first cashed but do execute if Refresh is pressed.
On this hub, I only have 2 devices – the Power strip and a Leviton Plug.
The Plug works correctly.
For some reason, none of the Strip devices react to On/Off commands immediately. The commands get first cashed but do execute if Refresh is pressed.
On this hub, I only have 2 devices – the Power strip and a Leviton Plug.
The Plug works correctly.
Is this a v1 or a v2 strip? I know some people have reported that the current states do not update reliably on the v1 (likely a driver issue, perhaps a regression caused by fixes for the v2).
it's V2 and the FW is 2.2
Everything worked on 2.2.5.131
Interesting. I have a v2 on firmware 2.2. and it's working as expected for me on 2.2.6 in any way I can test (on/off commands from Hubitat for each outlet work, physical changes are reported more or less immediately, and power reporting and whatnot seem to be reporting as expected).
If you believe the problems are related to 2.2.6, you could try reverting to 2.2.5 using the diagnostic tool to see if it helps (if you've used any new 2.2.6 apps like Basic Rules, you'll also probably want to restore a matching 2.2.5 database to avoid problems, otherwise I'm not aware of any breaking changes). Otherwise, besides possible mesh issues, since it sounds like you only have two devices, I'm not sure what the problem could be.
Some additional testing:
The strip does execute commands sent via Maker API; and so, it is just the web interface that's not updating.
Of course, I've got assets
Connected another strip. This one works properly.
The only difference I can see is that the working strip, and all components, under State Variables, show
* pendingSwitch : false
whereas the first strip shows TRUE.
Probably, tomorrow, will climb stairs to see if rejoining will help.