Ok, the remove/add worked just fine to order the Sensors again.
But the first part… with uiComponent I don’t understand…
uiComponent specifies what type of UI (On/Off, Button, Slider, Sensor etc. etc.) But don’t understand how I can decide which of the different UI “pages” that should be the “Master” that always is displayed when the user “opens” a device.
There are another command, “uiQuickAction”: true/false, but that determines what will react if a user just pushes on the device, not when it is opened.
Okay, if you add a button OnOff with suffix (like onoff.button1) it will then open the device in the Toggle tab (instead of button tab).
But it seems that the Button page is puth as opening tab when you have a real onoff capability (prbably because that would also be the QuickUI button, so no need to open with that tab.
Just did various testing with AVDs and some web-api-playground manipulation, but it looks like that is not possible, sorry
Not as long as you also have buttons at least.
That’s correct only for HP19.
On HP23, the HomeyApp displays standard capabilities first and then custom capabilities (or sub-cababilities). So it’s not in the correct order defined in the driver Json.
I discussed this witb Emile on Slack short time ago. Perhaps we’ll get a grouping i. sensor page.
So if you are using only standard capabilities, it should be displayed in Json order. If not, it gets mixed up in mobile app / WebApp.
As it’s the same behaviour, it seems tl be the WebAPI of HP23 that’s returning the capability list in wrong order.