I could have durfed that up. Neither the parent or child show up in the apps list. I can only get to the child is to go to logs and click on info. I think I will remove both and pay better attention to getting them both filled out. I'll let you know
Not getting better. I deleted the APP codes for both parent and Child. Removed the two thermostats I had. Copied and pasted both th eparent and Child code to New APP. Saved. They show up in the App Code listing but not the APPs . So I have no way to run the app. I tried two different browsers, cleared cache.
I found that too when I tried it. Not sure if it's a bug as I would have thought temperature would be a decimal but that gave bad parameter. Tagging Bruce in case it is a bug. @bravenel
it's not a bug if you're entering "%value%" because that's a string. You'd have to enter an actual decimal or integer to use the other parameters, but then the rule wouldn't work to sync a real temp sensor and a virtual thermostat's temp, which is the purpose of the rule @napalmcsr posted.
I'm just not very good at this rule/logic stuff so it took me a minute to realize that.
no no, it seems to be working fine. I was just trying to explain to @Geoff_T that the purpose of the rule is to take the temperature from each trigger event, i.e. %value%, and push that to the virtual thermostat. Hence the need for a string.
If one were to try to enter an actual decimal or integer instead, every time the rule ran, it would set the virtual thermostat to that decimal/integer that was entered in the rule action settings.
@napalmcsr do you have any suggestion how to sync two virtual thermostat setpoints? I'm trying to create a rule similar to what you posted above, using a %value% string, but it doesn't seem to be working.
Ideally, the rule would be something like:
if thermostat setpoint A changes, set thermostat B to new A setpoint
if thermostat setpoint B changes, set thermostat A to new B setpoint
I can't even get the first half of it to work. Any help would be appreciated!
a bit of a kludge, I can't directly put %value into set thermostat, but I can do it by making it a local var... @bravenel can probably tell us a better way.
I'm going to make that change, trivial to allow it. Consequences of misuse are on the user. Haha, like don't put the most recent color temperature of some bulb into a thermostat.