Trying to use visibleCondition along with embedded configs. These are the configs you can add directly into the device profile. Is visible condition allowed for embedded defintions:
components:
- id: main
capabilities:
- id: switch
version: 1
- id: switchLevel
version: 1
config:
visibleCondition:
component: main
capability: switch
version: 1
value: switch.value
valueType: string
operator: EQUALS
operand: 'on'
In the example above, just tried to show/hide the switchLevel based on the status of the switch.
nayelyz
(SmartThings Developer Support)
January 16, 2023, 8:09pm
2
Hi, @blueyetisoftware !
Someone asked about these configurations and here I put the feedback from the team:
Accepting this configuration is a work in progress, that’s why it isn’t fully documented. The team is aware of the requirement for it.
Currently, it doesn’t replace the usage of a custom device presentation as not all properties are accepted.
Yes, it should work for any capability
This was set to 1 because there were some inconsistencies observed creating routines that turned on the device with a 0% level in the dimmer as 0 represents “off”.
You can still send a 0% value through the API even if the presentation doesn’t allow it, the default range of the capability is 0-100%
Basically, not all embedded configurations will take effect because it’s a work in progress, that’s why it isn’t documented yet.
1 Like
Thanks. I actually did see documentation for it, which is why I started messing with it. Just not sure if visibleCondition
is allowed. All of the examples change values
and that its all I have seen work so far.
Docs
nayelyz
(SmartThings Developer Support)
January 16, 2023, 9:15pm
4
Aah right, this was the update from last week. I’ll ask the team again to see if there’s an update or visibleCondition is still not supported.
1 Like
nayelyz
(SmartThings Developer Support)
January 17, 2023, 11:29pm
5
Hi, @blueyetisoftware
Following up, I confirmed with the team that visibleCondition
isn’t supported yet in the embedded configurations.
2 Likes