Openhab 3 group average causing weird results

I have 3 windows in my master bedroom.
Each window has blinds which are controlled using a dimmer
These are in a group. My group i want to have an average of the dimmers.

When i set this. If i adjust any of the blinds. the average is working for the group. but its almost as if its using sendCommand instead of postupdate.
In oh2, the group average would update fine, but in Oh3, the group average updates, but the blinds then start going from one percent to the next and back again, because every time the group average updates, its almost as if its sending the command again.
My oh3 setup in the main UI

My old OH2 setup in my .items file

Group:Dimmer:AVG blindsLoungelocation "Blinds [SCALE(blinds.scale):%s]" (mapDB)


I don’t have a solution, but here seems to be someone having a similar issue:


This sounds familiar…

Is this only happening using the new Ui?

Can you try to use BasicUI (sitemaps).


I think we’d need to see your events.log for this

Yep only in the new UI

I haven’t got the log working yet. I’ll do it now and post it


I agree, that this seems to be the same issue, I did not see that the group-average were involved.

I was able to reproduce with four items (without any links):

  • item_group (group:Dimmer)
    • item1 (Dimmer)
    • item2 (Dimmer)
    • item3 (Dimmer)

The code of the UI page is:

  label: items
  - component: oh-block
    config: {}
        - component: oh-grid-cells
          config: {}
              - component: oh-cell
                  action: group
                  actionGroupPopupItem: Item_goup
masonry: null

Klicking on the cell opens the group “Item_goup” where you can control each item but also the group.

I changed only item1 to 85 but got:

2021-01-11 08:38:50.993 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Item1' received command 85
2021-01-11 08:38:51.004 [INFO ] [hab.event.GroupItemStateChangedEvent] - Item 'Item_goup' changed from 60.00000000 to 72.33333300 through Item1
2021-01-11 08:38:51.029 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Item1' changed from 48 to 85
2021-01-11 08:38:51.118 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Item_goup' received command 72
2021-01-11 08:38:51.123 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Item1' received command 72
2021-01-11 08:38:51.126 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Item2' received command 72
2021-01-11 08:38:51.128 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Item3' received command 72
2021-01-11 08:38:51.137 [INFO ] [hab.event.GroupItemStateChangedEvent] - Item 'Item_goup' changed from 72.33333300 to 68.00000000 through Item1
2021-01-11 08:38:51.138 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Item1' changed from 85 to 72
2021-01-11 08:38:51.140 [INFO ] [hab.event.GroupItemStateChangedEvent] - Item 'Item_goup' changed from 68.00000000 to 70.00000000 through Item2
2021-01-11 08:38:51.142 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Item2' changed from 66 to 72
2021-01-11 08:38:51.144 [INFO ] [hab.event.GroupItemStateChangedEvent] - Item 'Item_goup' changed from 70.00000000 to 72.00000000 through Item3
2021-01-11 08:38:51.147 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Item3' changed from 66 to 72

That really looks like the UI widget is generating unwanted commands in response to a state update.

Thanks for the update. Yes its a bug as far as i can see. For now, ive got the group seperate and not averaging the child dimmers. Until this is fixed.

Also, if you are in Model page, and you click on a single dimmer, change the value. then click on the group dimmer, it sends the command. So it seems as though it sends a command whenever the dimmer is actively on the screen

It’s not likely to get fixed unless you report as an issue in github, against the Main UI I would guess. You’ve got a reproducible demo.

Yeah im just looking now on where to report it. do you have a link?


yep found it, thanks will post now

If someone searches - the bug-report is here:

Thanks Peter. I created that yesterday

1 Like

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.