This is my first post, but I have been reading up on Vera for a couple of months now after seeing a review on Engadget. Thanks to this forum, I’ve got my system set up with a bunch of RadioShack GE dimmers, 3-way dimmers, on/off, and 3-way on/off switches. Got two schlage deadbolts, and one schlage lever lock, as well as the Trane thermostat (in addition to a handful of lamp modules and an outlet). The information you guys put out in solving your vera issues has been invaluable to me.
My question relates to the Wayne Dalton WDHA-12. I read the wiki, and have searched the forum, but can’t find a solution relating to my specific problem. I have my garage door wired up to a 110V relay, which is hooked up to a switched outlet. When I run my “garage door opener” scene, everything works fine, and it also works in my “coming home” or “leaving for the day” scenes. It works both by running it from the dashboard, as well as from SQ Remote on my iPhone.
The problem comes when I execute a scene from my WDHA-12. When I activate a scene, everything executes perfectly, but my switched outlet that is hooked up to my garage door opener executes twice! So while the garage door is halfway up, the outlet power cycles again, effectively stopping my door half way up (as if I had pressed the opener button while it was half way up). I’ve removed the WDHA-12 from my network a few times, re-added it a few times, reset it to factory settings a few times, replaced the battery, plugged it in, and unplugged it. Nothing I do seems to help fix this problem.
I want to get to the point where I can press the homelink button on my truck and have the garage door shut and execute the appropriate scene, but I need to get this resolved before I can get that far. As it stands right now, if I were to press the button and leave, my garage door would get stuck halfway open! Does anybody have an idea as to what I can do to fix this? Thank you so much in advance!
This sounds like both the WDHA-12 and Vera are actuating your appliance module.
It all depends on how you programmed it i guess, I have a WDHA-12 and have never really used it, but I expect it works like other scene controllers where the scene downloads also the controller and Vera.
I guess there might be a few ways to do this, but if you have a HRDS1 or similar then I would think about using the garage door plug-in that @woodsby wrote:
Its a nicer solution as it doesn’t require a scene for activation within the dashboard, it essentially appears as a lock; however in your leaving or arriving scene etc, you then associate a scene for either lock or unlock.
In theory, only Vera should then try to actuate the lock.
There are other ways to fix it I think, but thats the way I would do it as the garage door plugin adds polish.
Thanks for the response, Strangely. I don’t have a door sensor yet (have to put on the brakes to keep peace in the home, lol), but whenever I get one, that looks like a good solution.
Do you have any idea how to only let Vera control the scene, rather than having both do it? How could I tell for sure that was the case?
[quote=“ontheheel, post:1, topic:167883”][…]
I want to get to the point where I can press the homelink button on my truck and have the garage door shut and execute the appropriate scene, but I need to get this resolved before I can get that far.[…][/quote]
I use the WD gateway to turn on 3 lights, plus unlock a door. I can check tonight if there is an issue controlling an outlet, like you described. Is it a GE outlet?
The added value of Vera is that it can run parts of a scene that cannot normally be done by the scene controller. In my case that is the unlocking of the door. In your case, the WD gateway should be able to do it all. I don’t think there’s a way to manipulate that.
[quote=“strangely, post:7, topic:167883”]True but it would be nice to have both scenes controlled from Vera to keep it consistent.
I’ll see what mine does later when I try the same thing.[/quote]
Agreed. It’s a workaround (as requested), not a fix. I’ll try adding an outlet to my setup tonight and see what happens. Paired with your findings and the OP’s, we should hopefully be able to sort it.
Added an outlet to a scene on the WD gateway. That works fine. Just switching the outlet. Is controlled directly by the gateway (so works without power to Vera).
Now, since this is for a garage door relay, I think you may have set up the command to switch off the outlet after say 5 seconds? And programmed the same for when manually operating the button on the outlet?
Switching on the outlet through the scene on the WD gateway, also triggers the second scene for manually pressing the button on the outlet. These 2 almost simultaneously expiring timers interfere. Not sure how the outlet gets turned back on though. But the effect was that the outlet would be on, then switched off after 5 seconds, quickly come back on, and quickly back off. Which I think is what you described.
If you leave out the off-after-5-seconds timer in the WD scene (or set it to something larger than the manual button), it works fine.
Ok, just tried unplugging Vera, and the WD did not execute any scenes, so I think that rules out two commands being sent.
As far as the scenes go, I have only one scene associated with a button press at a time.
For instance:
Coming home (during daytime) = outlet on, then off after five seconds. 15 seconds later, back door unlocks.
Coming home (during night) = outlet on, then off after five seconds. 10 seconds later, certain lights turn on in the house. 15 seconds after that, back door unlocks.
Leaving for the day = outlet on, then off after five seconds. 10 seconds later, all lights turn off in the house. 15 seconds after that, the back door locks.
I have the two coming home scenes assigned to the same button, but they are differentiated with luup code to determine when it is night or day.
Originally, I had everything run all at once (this was before the new z-wave firmware was released), and it would get bogged down, and sometimes the garage outlet wouldn’t switch back off for 30-45 seconds. I spaced everything out with timers, and the scens run perfectly now…when I execute them from dashboard or SQ remote. When the WDHA-12 starts the scene, not so much.
That sounds like you did not re-include the WD to Vera after setting up the scenes, so they can be programmed into the WD.
As far as the scenes go, I have only one scene associated with a button press at a time.
[...]
I have the two coming home scenes assigned to the same button, but they are differentiated with luup code to determine when it is night or day.
So, are you saying these are 2 separate scenes in Vera?
If so, then you have 2 concurrent timers interfering, sort of like in my test case, depending on your Luup code, because both scenes execute (whereas you would only kick off one of them if you go through the GUI). Try changing the timing of the outlet in 1 scene to 10 seconds. Or better yet, integrate it all into a single scene. That way, you can also re-include the WD, so it runs most of the scene and get slightly better response times.
All of the steps are actually run in the individual scenes. I just have three different scenes that include the garage door sequence. Each of the different scenes (executed at different times) runs the garage door outlet on, then off five seconds later. There are no other commands running for another 10 seconds after the outlet has turned back off, so there are no concurrent timers expiring at the same time.
Only one will run at a time, however, since one will run during the day, and one will run during the night. I tested them separately before they were both assigned to the same button, and the problem was still present. Also, the leaving home scene has the same problem.
How would I combine both scenes into a single scene to run separate commands depending upon if it was daytime or night?
Currently, for my night scene, I have: return luup.is_night() so that it will only execute after sundown and before sunrise, and conversely, for my daytime coming home i have: return luup.is_day().
There is no luup.is_day(), so your 2 coming home scenes may run concurrently. When you observe the GUI when you press the button on the WD, do you see both scenes running?
That doesn’t explain everything, because you say the leaving scene has the same issue.
lol, I guess putting code in there that doesn’t do anything probably isn’t a good idea. is there a way to get the same effect with different syntax? I’ve only run it in the daytime, so the night scene hasn’t run concurrently when I’ve tested the button and watch the scenes in dashboard.