Button Press event - WDHA-12?

Community Playground General Discussions
#3

Thanks Axan. I’ll try that. How did you know this?

Charlie

#4

it was posted when one of the new luup firmwares came out + I actually have wdha-12 plus few other controllers (Ha07C, HA09C)

#5

I haven’t tried adding the WDHA-12 with the latest firmware, but search the threads for how to do this. I had to add it twice to get it to work. Don’t know why, but it’s a common occurrence.

#6

most controllers need to be added at least twice. No idea why but that was the case with few I use.

#7

Well I haven’t been successful but I may still not be doing the right thing.

First off, I do know that WDHA-12 and Vera are working together because I have also hooked up a WD zwave light dimmer and that works fine. In this scenario, I am using Vera to send a command -to- the WDHA-12 to turn on/off/dim the light. All good.

The scenario where I’m having trouble is the reverse where I’m trying to get WDHA-12 to send a command -to Vera- for my Schlage lock. I don’t know how to do this. I have WDHA-12 showing up as a scene controller and I have also created a scene to lock the Schlage. What I don’t understand is how to have the WDHA-12 trigger the scene on Vera. Descriptions as to which specific screens and what do to on them would be very helpful.

Thanks again,
Charlie

#8

Charlie, I may be doing this backward, but this is what I do.

I build a scene called ‘Button 1’.
I added an event called ‘button 1’ with device ‘scene controller’ and event type ‘a scene is activated’
When it asks what scene number, the buttons are scene 1 or 2 or 3.

(I found the hard part was syncing the buttons in my car to the WDHA-12.)

Then I added the commands for that event.

I don’t have the lock (yet), but this turned on my Christmas lights when I pressed the button.

Hopefully there is an attachment that makes sense here.
update with attachment.

#9

Hi,

The error saying that folder is full was resolved. It should be enough for 1000 <= 192kb pictures/attachments.

#10

Hi all,

Since I had so much trouble getting to the point where this was working and I got valuable help here, I’ve drafted some detailed instructions that others may benefit from…and it would be great if someone here would review them. Any takers?

After review, is there some way to get them posted on the Wiki?

Charlie

#11

[quote=“LVince, post:8, topic:165346”]…

(I found the hard part was syncing the buttons in my car to the WDHA-12.)

…[/quote]

I’m not clear on the WDHA-12. Sounds like i CAN use it to take ‘homelink’ commands form the garage door buttons built into my car and translate them into z-wave scenes.

I’m i understanding it?

I thought i needed their X10->zwave bridge but sounds like i can just use the WDHA-12?

#12

Yes, the WDHA-12 is a gateway between any homelink controller and Vera. Homelink sends a command to WDHA-12 which in turn forwards it as a scene activation command to Vera.

#13

ohhh- i NEED that. ;D

just dont tell my wife…

:wink:

#14

Charlieo,
Nice job on the write-up on the wiki. Very clear and professional.

#15

Thanks @charlie for the writeup, I just ordered one of these to attach a “startup” scene to the 2nd button in the wife’s car for when she gets home.

For anyone following the threads, the Wiki page is located here:

 http://wiki.micasaverde.com/index.php/Wayne-Dalton_WDHA-12
#16

thanks for the wiki page- was GREAT.

#17

anyone know why this is? (the red cog - unable to configure)

vera bug specific to the WDHA-12? vera bug with all secondary controllers? or something wrong with the WDHA-12?

#18

exellent job, this kind of documentation is so helpful! 8)

#19

Has anyone been successful getting this to work in UI3?

#20

Michealk,

The red cog is a normal finding… it remains red in Vera because this is a battery operated device that does not get polled on a regular basis. This would drain the battery if it was getting polled all the time.

I think it is a problem with all the secondary controllers because they do not pair correctly with Vera. All of my previously created scenes (Via UI2) still work fine in UI3…but I can’t seem to get it to program new scene associations…hoping MCV gets back with me on my open ticket here soon.

Hope this helps!

#21

I’m not sure the red cog is “right” to be honest (I put a bug report in for it actually)

I was under the impression that the wdha was ac powered when in an outlet- it’s only when you set it up that it uses the 9v battery- or so I thought? So vera should just hold any configuration data till it gets plugged in and ‘wakes up’- like it does with battery operated 3 in 1 sensors.

if nothing else vera should realize it cant configure and not bother so leave the red cog off.

#22

All I am saying is that Vera has displayed the red cog for battery powered scene controllers for quite some time… It is a little confusing, I’ll give you that, but I’m not sure if it would be considered a “bug” as it has been this way since they added the secondary scene controller feature.

As I stated a few posts back in this thread, I think there is something wrong with the code in associating scenes to secondary controllers. (IE the WDHA-12, HA 07, etc) Hopefully they will fix this code bug soon.