FGR-224 reports intermediate state while shutter is still in movement and doesn't report final value

[l30.l 0]

I have several FGRM-222 and I just replaced one of them with a FGR-224.

I notice that when I set a new value trough ZWave, specially if there is a big gap, for instance going from 0 to 100, I get an intermediate report in the middle, for example at 50, but I don't get one when the shutter actually stops moving. So the shutter is actually at 100 but in my UI it's stuck at 50.

I had to implement a manual refresh every 5 seconds to mitigate that.

Is there a proper way to handle that?

Edited May 2, 2025 by l30.l
typo in the title

[m.roszak 763]

Which Hub are you using? Could you provide some details?

[l30.l 0]

I'm using openhab but it's not related to my hub. I debugged the zwave messages emitter by the module.

[m.roszak 763]

According to specification, device should not report the state to the lifeline destination when controlled from it as a source.

Please login or register to see this image.

/monthly_2025_05/image.png.5732a76db944402ac7923ffa81c4049a.png" />

 

So, Hub implementation should assume that device will go to the position and present it as device won't report it automatically.

There is also encapsulation class called "Supervision" which FGR224 supports, this allows to have direct response about performed action (In progress) and follow-up report with end state (Success of the action).
Not sure if openhub support it. 

 

So, device works according to the current Z-Wave specification, if there is something to fix - its in openhub firmware