ygerlovin
(Yakov Gerlovin)
May 21, 2022, 6:49am
236
@iwry
This is the current behaviour of virtual switch. Virtual switch was designed to serve as routine trigger in Alexa ( in addition to other things) and Alexa does not allow this for regular switches. Hence a hiden contact sensor capability was added to vSwitch.
There is a feature request in virtual switch driver thread tor this
I would appreciate if a contact sensor was optional. Because it appears in every security application and adds noise to the event log.
I don’t own Alexa
And there is ongoing discussion how to solve this
Hi,
For virtual things driver it could be useful to allow users to decide weather their virtual switch should be seen in STHM.
The current implementation creates a virtual switch with switch and contactSensor capabilities. This allows to use it as trigger in Alexa routine. The device config hides the contact sensor, so it is not shown in detailed view. It looks like a normal switch, except it triggers STHM events.
I wonder how it is possible to allow the user to exclude the device from STHM from device detailed view.
I tried to use visibleCondition to hide contactSensor, but STHM still sees it as a contact sensor.
I could create a special profile without contact sensors. However, I already have 13 profiles only for virtual switch, each one has different icon. To keep the same functi…