10:12:55.601 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘shutter_bad_julie’ received command 100
10:12:55.628 [INFO ] [arthome.event.ItemStatePredictedEvent] - shutter_bad_julie predicted to become 100
10:12:55.643 [INFO ] [smarthome.event.ItemStateChangedEvent] - shutter_bad_julie changed from 0 to 100
10:12:57.341 [INFO ] [smarthome.event.ItemStateChangedEvent] - shutter_bad_julie changed from 100 to 8
So it only sends one status update after 1 sec … time to move from 0% to 8%, but it doesn’t send final/end status “changed from 8 to 100” when rollershutter is at 100% …
When real/physical buttons are used … no zwave status % update is send (?)
(Also have an old Fibaro Rollershutter 2 frg-222 and there both cases are ok)
Saw workarounds with REFRESH and so … but is there a real solution for his?
So that FRG-223 does send status itself?
Please can you provide a debug level log for this. What I can’t tell is if the updates are from polling, or if the updates are coming from autonomous association notifications (which should be the case, but possibly this isn’t happening).
When using the physical switches an update is send
12:28:14.663 [INFO ] [smarthome.event.ItemStateChangedEvent] - shutter_julie_links changed from 56 to 25
My FGR-233 (FW5.1) is working pretty good. When I send command UP the blinds are moving up full open (0), but then reported 41. On DOWN they are closing full(100), but reported 93. When I send 35 it moves to the position I want, but reports 52.
BTW at that position the blinds are fully closed, but opened as much as needed to let the air flow thru. The lowest blind has not moved in this position at all. I figured out 35% is the value to bring the blinds in this position by try and error.
Any hint how get the readings more reliable would be highly appreciated.
Thanks for the hint. I think that’s the right direction, but the maximum value for the poll delay is 15000 (=15 sec.). The blinds needs about 30 sec. for a full run.
In the log you can see the polling is done after 15 seconds and the blinds reported 58%, which is pretty ok for that time. 15 seconds later the motor stopped, but the state is not updated anymore.
Do you know, if this 15000 limit is from the device or from the thing definition and could be changed?
2020-11-29 15:09:36.258 [nt.ItemStatePredictedEvent] - SZRoll_BCtrl predicted to become UP
2020-11-29 15:09:36.321 [vent.ItemStateChangedEvent] - SZRoll_BCtrl changed from 58 to 0
2020-11-29 15:09:39.346 [vent.ItemStateChangedEvent] - SZRoll_Meter_w changed from 0 to 126.1
2020-11-29 15:09:51.495 [vent.ItemStateChangedEvent] - SZRoll_BCtrl changed from 0 to 58
2020-11-29 15:09:51.503 [GroupItemStateChangedEvent] - gBlinds changed from 0 to 58 through SZRoll_BCtrl
2020-11-29 15:10:06.746 [vent.ItemStateChangedEvent] - SZRoll_Meter_w changed from 126.1 to 0
Neither - it’s defined in the binding. If it’s too short at 15 seconds, you probably should just disable it as it’s meant to provide a quick poll after the command and long delays were never intended.
