I use openHAB Android app for a long time. I gouped light switches and I placed this group in the sitemap using Default item=gLight_Switches. All switches come from Z-Wave or Tasmota/MQTT binding. Recently I added a new switch to the group from Zigbee2MQTT with homeassistant auto discovery. I configured this switch the same way as others, but it looks different in the Android app. Any advice where can I find the root cause?
You are right, this is the Android app, but it is also the same sitemap that I use in the regular version of BasicUI. However I’ve just noticed that problem with weird switch button exists in the Android app only. Do you know why it might be?
@Lolodomo@mueller-ma@digitaldan I guess we should unify this, but I’m not sure which direction is more correct?
Falling back to command options if mappings aren’t given seems like a safe choice, but should we include item options or not?
In Basic UI, if no mappings are provided, there is also an exception for RollerShutter and Switch item to use the corresponding widget and not the widget with buttons:
OK, revisiting this, iOS does the same thing, and so did we. I think it’s just the ‘2 options or mappings’ special case that wrongly takes precedence over the 'is switch item’s case.
I’ll submit a PR.