Prevent roller shutter rule from firing more than once + inconsistent Z-Wave state reported

[rossko57]

I’ll add that you could use MIN or MAX group functions if you are looking for all member shutters one way.

@shutterfreak

AT_Shutter_N predicted to become UP

These messages come from autoupdate, having a pre-emptive guess at the outcome of a command. Where you’re expecting a timely update from a real device, it’s usually sensible to set autoupdate false for that Item.

@shutterfreak

AT_Shutter_N apparently didn’t report its state change

That’s something worth looking into, on the zwave side (about which I know nothing but has already been discussed).

But - I don’t see the other shutters reporting either, in the events.log snip you’ve shown us. Maybe they do later, but the events shown look to me like they are results of autoupdate predictions.

[shutterfreak (Olivier Biot)]

@mstormi

I replaced the OR(UP,DOWN) in the group definitions.

You already said that but didn’t say what you’ve replaced it with.

Here you are:

Group:Rollershutter:OR(0, 100)  gShutter  "Roller Shutter"  <rollershutter>  (Home)				["Rollershutter"]

@mstormi

The point is that group state isn’t a meaningful value with range like data types such as a roller shutter (no matter if you use OR, SUM, AVG or whatever).

Good to know.

@rossko57

AT_Shutter_N predicted to become UP

These messages come from autoupdate, having a pre-emptive guess at the outcome of a command. Where you’re expecting a timely update from a real device, it’s usually sensible to set autoupdate false for that Item.

I keep learning

So you would suggest that I set autoupdate="false" in the Rollershutter item bindings?

[rossko57]

@shutterfreak

So you would suggest that I set autoupdate="false"

That’s up to you. But given the interest in the reported state, you probably don’t want autoupdate’s interference.

@shutterfreak

Group:Rollershutter:OR(0, 100)

I don’t think the logic group functions work very well with non-bool member states.
The number based functions MIN/MAX/AVG are more appropriate here?

First step would be get your member shutters updating convincingly though.