I was hoping the new dongle + firmware would fix these problem, but they are still occurring after these upgrades.
Problem #1)
I have a Global Scene that is is not fully functional. It is triggered by an event timer set to run @ 0930 every Monday through Friday. The scene does the following:
Turn off all the lights in the house, except one that is triggered by a motion sensor (non-z-wave) AND Set Heat Setpoint to 64 (and leave it) AND Set Cool Setpoint to 79 (and leave it). [That maybe too much of a range as I am looking at it now, which I may tighten up later, but I donāt think it has anything to do with my problem]
The Lighting part of the scene works just fine, but the Thermostat part does not set the setpoints at all. Itās as if the thermostat did not get the command. I can manually set the setpoints, but this scene cannot set them. I have the Wayne Dalton Thermostat.Do you think the scene is choking on setting to setpoints on the thermostat at the same time?
The Scene used to work just fine, on a different Vera firmware no doubt, but it doesnāt work any longer.
Problem #2)
On a related note: another one of my scenes, involving the WD thermostat does not operate correctly either. Itās my āWatch Movieā which is supposed to turn off all the lights in the Loft as well as turn the Thermostat to OFF then in 2 hours go back to previous settings. (I have a pretty loud fan, and donāt like to have volume issues while watching a movie)
The Thermostat will indeed turn off, but it will not go back to previous settings in 2 hoursā¦it just never turns back on. Is it possible Vera is accounting for the previous setpoints, but forgetting to turn the thermostat back on heat or cool or whatever it was set at previous to the scene firing?
I was using the WD Homelink Bridge with my car garage door opener, and I learned something I donāt like about scenes. Scenes are re-triggerable! This means the āgo back to previous stateā is very breakable.
If you press the scene button twice (because of delays in Zwave, you not sure it heard you the first time). You end up breaking the previous states.
Start condition - the light is on.
Scene press one - turn light off for 15 secs, then return to previous state. (which is on)
Scene press two - turn light off for 15 secs, then return to previous state. (which is now OFF).
Soooā¦ If in this case you pushed the buttone twice in 15 seconds, then light will never turn back on. So you might need a scene called āIām done watching the movieā.
Iād like to see scenes with a timer and or event in them which blocks re-entrance into the scene.
Worst case, at 3 in the morning I could release the blocks.
Jacobly: if you are trying to have a certain temp trigger an action it will not work in current software version, it used to work in 616 but not in 979, itās a known issue, there used to be a < or > choice in temp based triggers and it is gone now, not sure what kind of logic they replaced it with but it doesnāt work, last time I tested where it says āa temp is reachedā it really behaves as " a temp below X (your value) is reached"
I just thought I would give a little update with what I found on the two problems. (Sorry for the delayed response, but the with the holidays, I hadnāt had a chance to get back to testing thisā¦)
Problem #1) So, I went ahead and removed the cool setpoint so only one setpoint (Heat) is the one being triggered by the timer event. This actually seemed to work today!
It really would be nice if Vera/WD Tstat could handle two set points at the same time, so I guess I will just have to update this scene with the seasons.
Problem #2) Iām thinking this one might be a problem with Veraās programming, or maybe this is actually the same problem I am having with #1!!! (Setting two settings on the TStat simultaneouslyā¦ meaning the āGo back to previous settingsā could be causing Vera to send āHeatā and the previous āSetpoint(s)ā at the same time and the Tstat just stops expecting commands)
I havenāt had a chance to test it yet, but I went ahead and changed the setting from āGo to previous settingā to āHeat.ā Iām hoping the Tstat is smart enough to remember itās own previous Heat and Cool Setpoints, Anyone have experience with this?
I guess this will be another scene I will have to update with the seasons too!
LVince: Great info to know about triggering scenes! Iāll have to keep this in mind when I am pressing buttons on my HA07!
I had the same problem with my timer triggered scenes to set the heat and cool setpoint on my Trane Thermosat. The odd this is that it is able to see both setpoints, when I run the scene manually, but when the timer triggers it only the heat setpoint gets set. When I looked at the zwave job log, I saw that when triggered by the timer, the job created to set the cool setpoint says it was superceded [sic] by the job to set the heat setpoint. I just created extra scenes, so I only set one setpoint at a time. I would be interested in what your zwave job log says when your scene fails.
I was able to test the āWatch Movieā scene after changing the thermostat part of the scene from āOFF, after 2 hours, return to previous settingā to āOFF, after 2 hours, HEAT.ā
The scene now works!
Yup, Madas, I could agree with you moreā¦it would be nice if these bugs were fixed soon!
ya, i could never get any of my lighting scenes to work properly with āreturn to previous settingā. which means iām going to have to fiddle with a couple of my scenes lest the lighting gets turned off while someone is watching a movie
I am on version 979 and have the same problem trying to set both heat and cool setpoints via a scene assigned to one of the 4-button controllers. I can set either the heat or the cool setpoints individually through a scene, but if I try to set both, only one registers - only heat most of the time.
Has this been corrected in 987, 994 and/or UI3? Any help is appreciated since this is a nuisance.
I submitted a trouble ticket on this last week. I thought I had done it a while back, but I couldnāt find any record of it. Iām told that Aaron is looking into it.
Best Home Automation shopping experience. Shop at Ezlo!
