probably nothing … please check if there is anything in the logs while trying it again.
also if you check the device simplisafe what is the current value of state variable status?
edit: may be compare it to armed home instead of home?
Sorry I was literally falling asleep as I was working this last night, so gave up. It appears even though the 'Case Sensitive' flag was in the off position, this was the issue. Status is reporting as OFF, HOME and AWAY; where I was using off, home and away.
I have this working through virtual switches, but no way to directly interact with HSM?
In effect I am trying to slave HSM to SS actions such that when the SS keypad is used, HSM keeps up.
Awesome app by the way.
@bangali
In your operator list what exactly is the UP ARROW for compared to greater or less than?
I'm monitoring a single clamp of my 1st gen AEON HEM. and would like to only trigger when the power rises above. Currently everytime it reports it's turning off a switch when I really only need it to turn ON above a certain value and off below. I'm thinking that might be what those arrows are for?
yup … up arrow is rises above and down is falls below.
1 Like
I read in a different thread that you used WATO so that you could extract ecobee thermostat cooling stages to control your ceiling fans? This is EXACTLY what I want to do! Help me understand the steps you did to get there. I have loaded WATO and looking to see how to do this. It isn't obvious to me how you did this when I look at the available attributes of the ecobee.
My desire is:
When I have the ecobee in Cooling mode I want to monitor the ecobee call for the first stage of cooling and when it is on I want to turn on my cooling fan low speed, and the second stage of cooling to turn on high speed.
I don't want to duplicate the wheel and use a smart-app as I did in ST to control the fan but use the existing ecobee cooling control algorithms to stage my cooling fan speeds in stages that can be viewed and setpoint changed from the ecobee screen.
was that using WATO or maybe it was using rooms manager?
updated github with the following changes:
Version 4.0.1
* 2018-12-26 cleaned up settings bug
* 2018-12-24 added option to use attribute value as first parameter in device command
1 Like
Will WATO allow me to set one dimmer to another dimmer's level? I want to create something that says when Dimmer 1 turns on, set level to Dimmer 2's level. I installed and it wasn't obvious whether it can do this, and if so, how to do it.
dont think that would work today.
added support to check for any changes to attribute value in latest version on github. so when the attribute value of a device changes you can set another device to the same attribute value.
this will partially allow what you are looking as in if level changes on 1 light another light can be set to the same level.
i know its not exactly what you asked but this was a quick holiday pass. 
I appreciate the quick response...that sounds a lot like the "track dim" feature in RM.
My use case is probably a bit unique, so that won't solve my problem unfortunately.
I have some dimmers that I fade up at sunrise over 30 minutes, and fade down at sunset over 30 minutes. I use a virtual dimmer for each one to track the "target" level of each dimmer. Target level changes independent of current dimmer's state...if the dimmer turns off, it stays off but the target level continues to change. If the dimmer is manually changed, that's fine, but the target level continues to change independent of the current level. Then, if the dimmer turns off and back on, it should go directly to it's target level.
I have this working ok in RM, but it takes 5 rules per dimmer to make it happen. My workaround for not being able to set one dimmer to another's current level is to enable Track Dim, decrement the target level by 1, wait 1 second, then raise it by 1 back to it's original level. It works, but it's hacky.
It's no big deal if WATO doesn't do this...don't add it just for me since I have it working a different way. Just was asking if it already had this capability, as this would really simplify things.
you could this in rooms manager with a single room for all dimmers.
I just added support for the operator changes using attribute value from device to use as parameter for command on another device was already there. 
1 Like
had a few minutes so now you can do things like this:
thats when a switch turns on set one or more other switches to the same level as that switch or another switch or some such variation of that. 
1 Like
Ahhh works perfectly, thanks! But you didn't listen, I told you not to add it 
But I'm glad you did
1 Like
I currently do this in RM with 2 rules - on/off tracking, then dimmer level tracking. In a perfect world I could do it with one rule that would match level on the secondary dimmer when:
- Primary turns on
- Primary changes level
I can't find a way to do it in less than 2 rules though - in RM or WATO.
I am getting much nicer performance from this new WATO capability vs my hacked up decrement/increment logic, thank you
1 Like
Not sure there's a way. In RM you can have two triggers, but can't directly set one dimmer to the other. In WATO, you can set one dimmer to the other, but can only have one trigger.
good!
you also mentioned the setup you were using and i knew this would simplify things quite a bit for you and for other users trying the same.
1 Like
i guess i could add additional triggers but then someone else is going to ask for multiple command support and soon i will be rebuilding RM. 
one learns to never say never but for now going to stick with When any Attribute Then this command Otherwise that command framework … so one of each.
sorry.
2 Likes
