Thank you for sharing this, the team just asked me to check again. I’ll confirm to them this is solved.
About the “untitled” issue happening again. Is there someone that still has this issue after clearing the cache or restarting the app?
I’ll check what could’ve happened with the team but it’s important to know if this was solved automatically or not…
CC @Mariano_Colmenarejo, @philh30, @johnconstantelo, @TAustin
Whatever was done Friday night appears to have been reversed Sunday night. Anything that has translations is back to showing properly (though with duplicate labels). Any capability created somewhat recently without translations is back to showing the capability and attribute names instead of the labels defined in presentations. My older capabilities without translations are still showing as Unknown.
ok, thank you for your confirmation. The team mentioned it was due to an issue in the backend that affected the labels shown but it was fixed, so, your work with translations isn’t lost.
About units in the detail view, there’s a workaround I found that is concatenating this value in the state label:
Android update to 18.104.22.168 has removed the double labels on single-attribute custom capabilities - only the capability label shows, no attribute label. Both continue to show on multi-attribute capabilities.
Multi-attribute meaning more than one attribute, regardless of the presentation. Below are both custom capabilities. The bottom one has a supported modes attribute, and continues to show two labels even though there’s only one attribute displayed.
I would guess the fix applies only to capabilities with single attribute.
Multy attribute capabilities are not affected, even if only single attribute is used in presentation (for this matter, even supported values attribute breaks the fix)
My guess is that this is due to another issue, that changes to capability presentations are not always propagated (or propagated very slow).
I changed a name of existing capability and then updated the device profile with the new name, then repaired the device and could see the change immideately. This is for several capabilities
Well, I think they have chosen the wrong solution.
If some custom capabilities do not have a defined name, the defined label will be displayed. This is not logical
It would not be more correct: If there is a defined Label, it shows the name of the label.
In the names of the capabilities you can add abbreviations or numbers to differentiate them from other similar ones, since you cannot use versions of the capabilities.
On the other hand I do not agree that it is working as they say.
I have all the custom capabilities with defined names and some show the name of the capability and others show the name of the label.
It seems that there must be something else that they do not tell us or do not know why.
Example legendabsolute60149.randomOnOff1: (in APP shown the label) legendabsolute60149.randomOnOff2: (in APP shown the Capability Name)
name: Random On Off 1
- name: value
What I have never understood is why on earth they started using the capability names in the first place. Surely the whole point of there being a label name was to use it as the label? If I wanted to see the capability name in the label I would have put it in the label.
I seem to vaguely remember it was all to do with multi-attribute custom capabilities. All I ever wanted to be able to do with those is use more than one of the attributes in the presentation in the same way I would do multiple single attribute capabilities. There is no more reason to group attributes from the same capability together than there is to arbitrarily group separate single attribute capabilities together (so please stop displaying temperature and humidity together without asking, they could be from sensors in two different continents).