Thank you @Mariano_Colmenarejo for creating this virtual device.
I am using this driver where only one switch needs to be on, and all others are off. This driver eliminates loop issue when routine are used to activate/deactivate other switches, and run forever in circles.
It replicates Home Mode, or SmartThings Home Monitor functionality, where only one state is active.
I am planning to use this for my 4 zone drip irrigation timer, where only one zone can run at the same time.
Another use, I have used switchboard with 3 switches, to control 3 different lights with single Ikea dimmer remote. This Switchboard is displayed on Fire tablet, with Ikea Dimmer next to it. However I have plans to upscale the dimmer.
I have created automations, where when one of this switches are active, and Ikea Dimmer is pushed up or down, it changes light level +/- 5%, and when dimmer is held up or down, it changes light temperature by +/- 100K. Each switch on SwitchBoard is named for individual set of lights in the same room.
This way I can change level and temperature on 3 different set of lights with single dimmer and this Switchboard.
My intention is to swap Ikea dimmer for different device: Smart Knob, as driver for it became available, created by @erickv.
To introducing these changes and if some user has already made some automation in his system, I will not do the automatic update,since the automations created with switchBoards old version would stop working when it is updated automatically without prior notice.
In this way, the best thing is for each user to migrate their devices to the new version of the driver when it suits them best.
The current version will automatically be called Virtual Switches Mc-(OLD).
The procedure to migrate the devices to the new version:
Install in your Hub the new version Virtual Switches Mc
Add new device and search nearby. The new MAIN Virtual Switch device will be created
You can see the Total Devices created in the MAIN Virtual Switch that you already had installed. You can refresh the device so that it is updated.
On each device you want to migrate, make a driver change in the app and choose the new Virtual Switches Mc driver.
You will not lose the automations created for Virtual Mirror devices.
For automations of Virtual SwitchBoards you need edit and modified them. Only the custom names of the switchBoards will be reinitialized, since the system does not recover them when changing drivers.
Once you have migrated all your devices to the new driver and the total counter is 0 then you can delete the MAIN device and the driver -(OLD)
I tested the migration process with all device types and works fine
I accidently deleted the Main Mirror Creator tile from the app, driver is still installed. I have tried for 2 days to readd the main Creator device by scan nearby but it isn’t being discovered. Any advice?
Edited to add I have rebooted the V3 hub several times, cleared app cache and even force stopped ST app
It appears that latest ST app update did remove the option to select ENABLE or DISABLE in multi-switches when selected in THAN for automations.
Could you confirm this change? Because this kills your “mirror” solution.
@Mariano_Colmenarejo another user is asking if its possible to add assignable action to virtual dashboard driver, when switch is on to do something, like for buttons. It would be only single action, not 3.
Could switch icon be added to the icon list and would it be possible to see from dashboard which switch is active? I use maximum five switches and it’d be useful to see which is active. This way I could use only one virtual device to run my change my modes and to see which mode is on.