Ok…
It’s possible write a routine to mirroring active scene of one virtual switcher??
If first virtual switcher scene change a second virtual switcher change to same active scene???
Not right now since there’s no method to set a specific scene that takes a number, the idea was always to control it with relative commands like next or previous.
What is exactly the use case so the mirroring is needed?
Edit: I’ve implemented it anyway, will publish the update in a couple days after some testing. For the mirroring, Rules API are needed since the app routines cannot copy values.
New version 2026-04-08 improves direct control with scene numbers.
The switcher always had a list of actions like Next, Previous or Scene 5 but the relative scene steps were limited to +/- 1 or +/- 2 and specific scenes were a list and not a number.
Now there are actions with actual numbers:
- Specific scene 5 is exactly the same as picking Scene 5 in the list.
- Relative scene step -1 is exactly the same as picking Previous.
The interesting part is that you can programatically set the scene number with Rules API automations, for instance to mirror the scene number of another scene switcher.
How to mirror a scene switcher
To copy the current scene of a switcher into another whenever it changes, creating a rule in the advanced website (AWA) is needed.
The rule is a simple “if the original scene changes, pass to the mirror the original scene” but, as usual, it is incredibly verbose. In the following rule, you have to replace the original switcher device ID in two places and the switcher that acts as mirror in one. The device IDs can be copied directly from the devices section of the AWA.
Check that the “mirror” has the same or more Number of scenes to cycle defined in the settings than the original, otherwise you’ll have unexpected results. Also, double check the IDs and actions for potential infinite loops.
[
{
"if": {
"changes": {
"operand": {
"device": {
"devices": [
"ORIGINAL-SWITCHER-DEVICE-ID"
],
"component": "main",
"capability": "panelorange55982.activeScene",
"attribute": "scene"
}
}
},
"then": [
{
"command": {
"devices": [
"MIRRORED-COPY-SWITCHER-DEVICE-ID"
],
"commands": [
{
"component": "main",
"capability": "panelorange55982.changeActiveScene",
"command": "changeScene",
"arguments": [
{
"device": {
"devices": [
"ORIGINAL-SWITCHER-DEVICE-ID"
],
"component": "main",
"capability": "panelorange55982.activeScene",
"attribute": "scene"
}
}
]
}
]
}
}
]
}
}
]
When you paste it in the AWA has to look like this:
Now the mirrored switch replicates the scene number of the original.
1 Like
Hi,
I use your driver to control 15 color scenarios, because it’s not possible change the switching delay by routines i use 2 virtual switchers for animation. Each one with different time switching delay…
My scenario:
15 routines for each switcher when i want 2 leds
more 15 routines for each switcher when i want 3 leds
15+15+15+15 =60 routines!!!
I cannot set the simple rule “if switch1 or switch2 then..” because i have a lot of conditions to met at same time. Using your driver with “reactive current” i can reduce some animation routines but will create a lot of others routines with “reactive current” to met all conditions and pre conditions for my needs…
With mirroring option a can do the same using only 30 routines… First virtual switcher to set color scenarios with a time delay for long spanning and second virtual switcher with different time delay that when activated mirror to first virtual switcher…
1 Like
Thank you very much to implement this in your excellent driver…
Now i rid off 30 animation routines and a lot more routines needed to maintain use of second virtual switcher operating only when some conditions are met…
Very good! Excellent work… THANK YOU!!!
1 Like
No problem! Deleting routines no longer needed always brings joy! So is it already working as expected with the reduced routine count?
On the first reading I didn’t fully get the whole scenario but I believe I get it now, make the second switcher cycle the scenes of the first switcher with its own timer so you don’t need to create routines with the second switcher. That’s a great workaround indeed!
It’s working like a charm… I’m very happy with results and happy to free some hub memory…
Thanks
1 Like
A question I forgot, that different time delay is a fixed delay always or do you use the Additional random offset feature too?
For now I’m using fixed time on 2 switchers but I’m thinking to add another one to try this additional time delay option…
1 Like
OK! I’m working on an interesting update so you can free more hub memory 
but it will be for fixed times only.
Ok. I’m looking forward to seeing…