I can’t figure out what the conditions are for triggering this event.
From the name I thought it would be when the temperature reaches one of the set-points - there’s a choice of Heat or Cool which looks like it would distinguish which set-point.
However, there’s also a temperature setting which has thrown me. Is this a UI error and the temp setting should not be there? If not, then what is this for and have I mis-understood the whole event?
I could not find any documentation on this so if there is then just point me to it please.
Thanks,
Neil
The only reference I could find in the Wiki for “set point” is on this page:
[url=http://wiki.micasaverde.com/index.php/UI_Notes]http://wiki.micasaverde.com/index.php/UI_Notes[/url]
Specifically, look in the section:
“List of commands and parameters to send to devices”
After reading the notes there, I certainly would have come to the same conclusions you did about the “Thermostat Set Point Is Reached” event!
Good luck finding out more!
Thanks LibraSun.
Do any micasa folks know the definitive answer to this?
Neilios
I’ve been experimenting with this and can’t get it to trigger - is it broken.
Does no-one use this Event type?
I just got the TZ43 today and the general features all work with the .862 Beta but I am having the same trouble getting any of those triggers to operate.
I’m going to chime in on this, despite the fact that I use a different thermostat (Wayne-Dalton WDTC-20) and my Vera remains at .616 firmware:
During my first test of the “Thermostat set point has been reached” event, I set up a simple scene with these parameters:
center Thermostat < 79 deg. (F), (then) Turn living room lamp ‘On’.[/center]
The test is on-going, and I’ve noticed the following inconsistencies:
(1) My home’s initial temperature was reported by both the thermostat and Vera as 79 deg. F.
(2) After running non-stop for an hour with the thermostat’s internet set point at 75 deg. F., the thermostat has been showing a decreased “current temp” of 78 most of that time.
(3) Vera, meanwhile, continued to show “current temp” as 79 deg. F … only when the thermostat “current temp” dropped to 77 did Vera’s display match at 77 deg.
(4) Regardless, the lamp (command) never turned ‘On’! (Whether the scene ran internally, I’m unsure … I set no other notification.)
In short, I think I’m in the same boat as earlier posters commenting on this trigger/event not working as advertised or hoped. But I hasten to add that the term “SET POINT” is misleading in this context: I’m quite sure MCV intended the scene’s “set point” input to be an arbitrary value, not corresponding in any way to the thermostat’s internal “Set Point” (as set in ‘Devices’).
Hope this feedback helps. Because now I’m freezing and the test must end! 
Here it is, two weeks later, and no definitive explanation has been forthcoming. In fact, now that I’ve upgraded to Luup, I’m even MORE confused (because there are more options for thermostat events). Here’s where I feel the confusion lies:
-
There’s now a “Temperature goes above” event with a bizarre choice of “Off, Cool, Heat, Auto … degrees” for “temperature”. And why is this event necessary (see #2, below)?
-
The “Temperature is reached” event offers only two “comparrison” [misspelled] operators: < or >, which I realize are universally-accepted signs for “less than” and “greater than”, but plenty of folks would appreciate a reminder of which is which, so text labels should be included.
2b. Why isn’t an ‘=’ or ‘>=’ etc. offered for “Temperature is reached”? In fact, most people would equate (no pun intended) “reached” with =, and probably assume that <= is implied for COOL mode, while >= should likewise be implied for HEAT mode. Am I the only one confused by this?
- As was discussed earlier, WHY is there a ‘temperature’ field for the “Thermostat COOL/HEAT set point is reached” events?? Even when testing this feature in 616, Vera did not seem to trigger this event. These event modes require more documentation.
I’d like to get this to work as well.
I have banvils that should turn off in the middle of the night if the temperature drops below a set threshold.
It doesn’t work though.
Wow, it just took me five minutes to figure out what a Banvil is:
Fans! 
Yeah, so I actually asked this exact question about three weeks ago after I first installed my Thermostat. I did actually get an event to trigger, although it seemed to work backwards. I used the “Temperature is Reached” trigger and set it to “> 80”. However, I almost immediately received an alert on this event when the temperature was only reading 76. At that point I assumed I had gotten the operator backwards (which doesn’t make sense to me) but I also just gave up and didn’t do any further testing.
And a more general question…with these kinds of alerts, how often will they be triggered? Would it be everytime the device is polled? Is there a way to limit an alert to once/day so you don’t get the same alert at every polling?