today my rollershutters should go down at a time I configured in a rule. This worked fine the last weeks. Yesterday and today one rollershutter didn´t close as it should. The log looks good:
2024-11-22 17:13:00.007 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'RolloSchlafzimmer' received command 80
2024-11-22 17:13:00.024 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'RolloSchlafzimmer' predicted to become 80
2024-11-22 17:13:00.027 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'RolloSchlafzimmer' changed from 0 to 80
but it did not move at all.
Is there a way to make sure a device or the rollershutter in this example really did what it was supposed to do? Any control mechanism?
PS the rollershutter is controlled via a shelly device, I think 2PM.
That happens to me every so often with zigbee blinds. It seems they miss the command.
I don’t know if it is possible to query the actual state of the blind, but you can always put a delay in the rule, say 1 second and send the command again.
I don’t have any Shelly devices but the listing on Amazon says the 2PM monitors consumption. You might be able to save the consumption value in a helper item before triggering the blinds to close, trigger the close, and then use a timer to start another rule a minute or so later. The second rule would compare the current consumption value to the first, and send some sort of notification if there was not enough electric used.
Your Item likely has auto-update on. Therefore it updates as soon as the command is received and changes the State instantly. If the binding you are using can update (not sure if what you use for shelly can or cannot), then you can turn off auto-update and see if then reports the true position. I don’t have any direct experience with shelly, so this is all theoretical.
@rossko57 has a nice write up on auto-update here: Autoupdate - a primer. It’s a little old, but I think it’s still accurate.
I built a retry/redeliver command profile a year ago to try to tackle this exact problem. I was supposed to PR to the basic profiles of Smarthome/J, but never got around to do it.
