Thanks for tagging me, @johnconstantelo.
For this cases, it’s important to consider:
-
The property
numberOfButtons
is used as a reference only, it doesn’t create the number of buttons specified, it is correct to use child devices for that purpose. -
The DTH “Tuya Battery Switch” creates a child using the predefined child button handler and, as @Martin_Rourke said, they are considered separated devices because the
isComponent
property was set to false. I can see both parent and child devices available from the Automations.
@Martin_Rourke, from the first time you installed this DTH, you weren’t able to see the parent there? -
The content on each view (Dashboard - main, Detail, and Automation) depends on the device presentation, one is generated by default when the device is created, but you can create a custom one where you can remove/add the capabilities you want to appear on each view. This also includes:
a. Changing the capability values range
b. The options available from a list (no matter they have a supportedValues attribute or not)
c. Display order the capabilities cards
d. Presentation for Multi-Component Devices (when you have child devices as components)
Note: Not all standard capabilities have the Automation View configured.
Up to now, only one standard capability can be shown at the Dashboard View.
-
@mwav3, the
supportedButtonValues
needs an extra configuration on the Automations View because not all the devices use this property. This post has an example of this.
Feel free to post further questions.