Buttongrid should display item values like Text in BasicUI

[hemagi]

Is your feature request related to a problem? Please describe.

I like the Buttongrid feature in the sitemap, e.g. to control blinds.

If one sets up a label like

Buttongrid item=Lam_EZ_pos label="Esszimmer [%d %%]" staticIcon="blinds" { ... }

the current value of Lam_EZ_pos is not displayed.

Describe the solution you'd like

The Buttongrid label should behave like the Text label.
In the example the slat position 0 to 100 should be displayed.

Describe alternatives you've considered

Additional context

[lolodomo]

I don't understand the title. Is it a request for change for the Android app or for Basic UI. Why Basic UI is mentioned?

[hemagi]

It is a request to change the app because this is what my family and I uses day by day.

I additionally use the basic UI in a browser on my laptop, so I would appreciate that this is changed, too. But I see that the app is more modern with more working functionality.

[lolodomo]

Even if we can have small difference in rendering between app, it is important to have the same understanding of any kind of sitemap element between all applications supporting it.

[hemagi]

I understand your concerns, but don't see an issue.

The android app and the standard basic UI differ in some points, e.g. a slider to enter at setpoint or a clock to enter a time.
Especially the icon of a buttongrid item is dynamic in the app showing the state, but static in the basic UI.

The value of an item is neither displayed in the app nor displayed in the basic UI, for reasons I do not know, even if one enter it in the buttongrid item label. It is ignored.

Showing the value of a buttongrid item like in a text item is the only consitent solution, if one decides to do so.

And I do not see any reason why it should not be displayed. If one would not want to see the value, the label can be set accordingly.

[mueller-ma]

Can you post screenshots of the app and Basic UI to see the different behavior?

[hemagi]

What are you asking for?

• The clock for entering the time in the app (Input control, inputHint="time") does not exist in Basic UI. There you either can enter the time or select hour an minute from a pull down menue.
• The slider for entering a value in the app (Setpoint control) does not exist in Basic UI. There only the arrows are available.

Regarding the buttongrid, in the app the switch icon in Buttongrid item=sw_item icon="switch" { ... } changes its color between red and green, depending on the sw_item's state.
In Basic UI the icon stays green and does not change, even if the switch is off.

[lolodomo]

Regarding the buttongrid, in the app the switch icon in Buttongrid item=sw_item icon="switch" { ... } changes its color between red and green, depending on the sw_item's state.
In Basic UI the icon stays green and does not change, even if the switch is off.

You are allowed to open issue for Basic UI at the right place.
For this one, I made the icon not dynamic, I have to remember what was my reason but it would be easy to enable it.

Rather than listing all the differences between the Android app and Basic UI (I don't thing it was @mueller-ma requested), please come back to explain what is your request for change regarding Buttongrid because I believe it is not clear, neither for me nor for @mueller-ma . We even did not understand clearly if this is something working differently in Android app and Basic UI.

[hemagi]

Regarding my original request, there is no difference between the app and Basic UI. Both do not show any value of the buttongrid item, even if it is set like [%d %%] in the label.

I was asking here because the app development is more dynamic than Basic UI, with much more releases.

At least for me a change in the app is more valueable than in Basic UI. In case of Basic UI, I need to install a new release of openHAB in order to use any changes in Basic UI, that means, now I need to wait for and have to decide whether I want to install openHAB 5.

So I would appreciate if you would change the app's behavior, as described in the OP.

Currently I combine Text and Buttongrid like

Text item=Lam_EZ_pos label="Esszimmer [%d %%]" staticIcon="blinds"
Buttongrid { ... }

which leads to a similar result, with a wider spacing in the app and a separating line in Basic UI.

[lolodomo]

In the original buttongrid syntax, the item attribute is a little different from other sitemap elements as it used to condition all the cells.

@mueller-ma : what is your opinion ? We could add the item value in the header row ?
Edit: in Basic UI, there is no current case where the value is present in the header row, we are using the same header row for Buttongrid, Video, Mapview and Webview elements.

[hemagi]

I see the issue, I was not ware of it.

For me

Text [item=<itemname>] [label="<labelname>"] [icon=<iconref>] [staticIcon=<iconref>]

and

Buttongrid [item=<itemname>] [label="<labelname>"] [icon=<iconref>] [staticIcon=<iconref>] ...

are the same, because I only use the syntax

Buttongrid [item=<itemname>] [label="<labelname>"] [icon=<iconref>] [staticIcon=<iconref>]
{
    Button ...
    Button ...
}

and never Buttongrid ... buttons=[ ... ], because the latter is not very comfortable and hard to read.

So for me "Text" and "Buttongrid" are the more or less the same and should behave the same