I have a quick question. I am using PLEG to use a virtual switch (multiswitch) to turn on and off my AC’s via a Remotec ZXT-120. The virtual Switch works fine for what I want to do, but if I make changes from the thermostat device on Vera i.e. OFF/Cool (On) the multiswitch does not change state to reflect that change. I know I can create a PLEG scene to toggle the state of the multiswitch based on the AC state, but I was thinking that it would just create a continuous loop. Am I wrong to think this? Is there a better way to do the program?
Thanks for letting me know. I hope there is a solution for this.
Sounds like you just need to create a trigger on the state of the thermostat device, then change the multi-switch to match.
Post a status report in PDF and we can make suggestions…
Ok. I attached the Status Report. I thought of doing what you suggested, but then thought I would get stuck in an infinite loop of one trying to match the other. Am I thinking of it wrong?
Have a look at this solution, it might work for your case.
[size=2px]http://forum.micasaverde.com/index.php/topic,47377.0.html[/size]
You need to add triggers on the actual thermostat devices as well. Then you can use sequence expressions to determine which (virtual switch versus actual thermostat) was changed last.
Something like what I do to sync two physical thermostats… http://forum.micasaverde.com/index.php/topic,30792.msg221170.html#msg221170
You need to add triggers on the actual thermostat devices as well. Then you can use sequence expressions to determine which (virtual switch versus actual thermostat) was changed last.
Something like what I do to sync two physical thermostats… http://forum.micasaverde.com/index.php/topic,30792.msg221170.html#msg221170[/quote]
Ok so I had a look at this. One thing I am not understanding though is what does the No part of the condition do? I may be missing something here.
ModeMismatch2ndFloorChanged No (SecondFloorMode ne ThirdFloorMode) and (ThirdFloorMode; SecondFloorMode)
ModeMismatch3rdFloorChanged No (SecondFloorMode ne ThirdFloorMode) and (SecondFloorMode; ThirdFloorMode)
You need to add triggers on the actual thermostat devices as well. Then you can use sequence expressions to determine which (virtual switch versus actual thermostat) was changed last.
Something like what I do to sync two physical thermostats… http://forum.micasaverde.com/index.php/topic,30792.msg221170.html#msg221170[/quote]
Ok so I had a look at this. One thing I am not understanding though is what does the No part of the condition do? I may be missing something here.
ModeMismatch2ndFloorChanged No (SecondFloorMode ne ThirdFloorMode) and (ThirdFloorMode; SecondFloorMode)
ModeMismatch3rdFloorChanged No (SecondFloorMode ne ThirdFloorMode) and (SecondFloorMode; ThirdFloorMode)[/quote]
That is condition option “Repeat” is No. It would be No by default…
You need to add triggers on the actual thermostat devices as well. Then you can use sequence expressions to determine which (virtual switch versus actual thermostat) was changed last.
Something like what I do to sync two physical thermostats… http://forum.micasaverde.com/index.php/topic,30792.msg221170.html#msg221170[/quote]
Ok so I had a look at this. One thing I am not understanding though is what does the No part of the condition do? I may be missing something here.
ModeMismatch2ndFloorChanged No (SecondFloorMode ne ThirdFloorMode) and (ThirdFloorMode; SecondFloorMode)
ModeMismatch3rdFloorChanged No (SecondFloorMode ne ThirdFloorMode) and (SecondFloorMode; ThirdFloorMode)[/quote]
That is condition option “Repeat” is No. It would be No by default…[/quote]
Ahhh ok. Thanks for the help!