I haven’t played with Rules much, but this would be the other option:
The engineering team mentioned the mirror functions can be achieved using the Rules API and the changes condition.
It is different depending on the capability configuration to set the attribute value.
For example, the Switch capability has two enum commands that don’t receive any arguments.
In this case, we need to check the change to a specific value (“on”/“off”) and send the same value to the other device.
This sample shows how we can mirror the switch events of a multi-component device that has a switch in two components (light and main), that’s also why only one deviceID is used.
{
"name":"Mirror switch events of main and light components",
"actions":[
{
"if":{
"changes":{
"equals":{
"left":{
…
jaragonCR:
So right now the only useful tile is Water T, I guess everyone has Outside T and depending on your settings Circuit 1 is always the pump and 3 pressure side cleaner, it’s a hard bargain, I guess it would be profile dependent?
That’s exactly the challenge… This device is too configurable and the ST app is too rigid. Come up with your pick, and I’ll set that profile to match your preference.