The colorpicker for iOS does not at all follow the basic UI on web or on Android. For example it completely lacks the on/off buttons which makes it near impossible to use to simply turn on a color light. Is there any reason for this being different suddenly on iOS? One argument I guess could be that it simply is a color picker. However, to me it makes no sense that there is a “Basic UI“ which then has different functionality based on which app it is accessed from. Suddenly half the household can not turn the lights on properly.
I am not sure what policies are in place (if any) for the Android and iOS apps but to me this feels like a move in the complete wrong direction and more or less completely ruins the point of “basic ui“ and sitemaps if they randomly look different, but especially have different functionality.
This also goes against the openhab documentation which states
This element is a combined control for something like a rgb or rgbw light where you can adjust brightness as well es the color hue. The down-button decreases brightness to zero and switches the light off. The up-button sets brightness to full but keeps the previous color (hue). The middle button opens an overlay to fine-tune your color when you click on it. In the overlay, a color wheel lets you pick the hue and a slider allows to set the brightness. The content of this middle button can also show what is the current color.
Official one? But looks like you use the main ui rather than sitemap?
I think for phone use “as a remote” the sitemaps are a lot better for multiple reasons than main UI. One thing with main ui on phone is that you accidentally turn on lights (sliders) to 50% as you scroll in the middle of the display which drives me crazy. But that really is a whole other story.
Thanks for the detailed report and the documentation reference — this is exactly the kind of feedback that helps move things forward.
Brightness up/down buttons for the color picker sitemap element are on the way and will be included in an upcoming release. The down-button behavior (decrease to zero / switch off) and up-button behavior (set to full brightness) as described in the docs will be there.
On the broader question of iOS vs. Android parity: yes, there will always be some differences. The iOS and Android apps are maintained by separate contributors, each working within their respective platform’s UI paradigms and constraints. The goal is functional equivalence where it matters — not pixel-perfect mirroring.
openHAB is a community project, so the fastest path to closing gaps like this one is exactly what you did: file a clear report with a specific reference to the docs. Or, if you’re up for it, a PR is always welcome.
