I have noticed that the advanced settings of a device look quite different on mobile and desktop. Given Athoms favouring of the mobile app, I might have thought that the mobile version would be better, but the desktop version is much better.
Here is what the iOS mobile looks like:
Notice the repetition of the label. I thought this was the driver’s problem. Then i looked at it on the desktop app and it is what I would have expected the settings to look like. There is no repetition.
There is so much wasted space on the mobile app. Those selections could be so much closer together if the label above the control was not shown, since it is shown in the control it self. This device many, many settings so there is so much scrolling on this page because of this wasted space.
Is this something that is wrong with the driver? Or is this something that is wrong with the Homey mobile app coding on iOS?
It could be a driver issue as it seems each parameter is defined in a separate group.
Ah, that might be it.
I am trying to help out on a driver that someone else wrote.
One of my suggestions was to do some logical grouping of the parameters because there are over 100 by the looks of it. Grouping seems like a necessity.
I am having an issue where I am changing the strings in the compose.json files but they are not changing in the app on the homey, even though I have verified that the driver I am bulding is the one being used on my homey.
Do you know if there is a trick to getting the json files processed again and updated? I would have thought that would have happened automatically when I did a homey app run --remote.
I can’t remember if this applies to settings, but things like capabilities are only read when a device is added, so maybe try deleting and adding the device.
I figured it out.
Since I am not the original author, I made some bad assumptions. Namely, since there were files called driver.compose.json etc, I assumed that the project was using homeycomponse. It was not. So when I was changing the .compose files, the system was happily using the un-edited app.json file instead.
I ran homey app compose to convert it to use compose and now editing the compose.json files work great for making changes.
