http://wiki.mios.com/api.php?action=feedcontributions&feedformat=atom&user=CharlieoMiOS - User contributions [en]2026-04-18T15:08:17ZUser contributionsMediaWiki 1.19.8http://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-02-25T06:48:34Z<p>Charlieo: </p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-2010 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that its only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
<br> <br />
<br />
'''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>'''<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click '''Advanced''', then click '''Logs '''and then '''Show Z-Wave jobs'''. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However it will only work as a gateway once you plug it back into the AC, so you <u>can’t test it while it’s still unplugged</u>.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a handheld controller (meaning the buttons work but it doesn't pass thru HomeLink commands) and only works as a Gateway when it’s plugged in.<br />
<br />
<br />
(if the directions in the WDHA-12 manual for pairing your car don't work- try [http://www.homelink.com homelink.com] and select the programming tab. Choose "program a garage door opener" from wayne dalton and pick your vehicle. It will provide you the proper sequence of things to do in your vehicle while following the WDHA instructions for the button presses on the gateway)</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-02-25T06:45:50Z<p>Charlieo: </p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-2010 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that its only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
<br> <br />
<br />
'''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>'''<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click '''Advanced''', then click '''Logs '''and then '''Show Z-Wave jobs'''. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However it will only work as a gateway once you plug it back into the AC, so you <u>can’t test it while it’s still unplugged</u>.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a handheld controller (meaning the buttons work but it doesn't pass thru HomeLink commands) and only works as a Gateway when it’s plugged in.<br />
<br />
<br />
(if the directions in the WDHA-12 manual for pairing your care dont work- try [http://www.homelink.com homelink.com] and select the programming tab. Choose "pragram a garage door opener' from wayne dalton and pick your vehicle. It will provide you the proper sequence of things to do in your vehicle while following the WDHA instructions for the button presses on the gateway)</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-24T02:27:16Z<p>Charlieo: </p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-2010 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
<br> <br />
<br />
'''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>'''<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click '''Advanced''', then click '''Logs '''and then '''Show Z-Wave jobs'''. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However it will only work as a gateway once you plug it back into the AC, so you <u>can’t test it while it’s still unplugged</u>.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a handheld controller (meaning the buttons work but it doesn't pass thru HomeLink commands) and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-24T02:24:50Z<p>Charlieo: /* How to Configure Vera with Wayne-Dalton WDHA-12 Gateway */</p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-2010 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
<br> <br />
<br />
'''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>'''<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click '''Advanced''', then click '''Logs '''and then '''Show Z-Wave jobs'''. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/ZWave_Add_ControllerZWave Add Controller2010-01-24T02:21:20Z<p>Charlieo: </p>
<hr />
<div>With most Z-Wave devices, you add them to Vera's Z-Wave network by clicking the 'Add other Z-Wave devices' on the 'Devices' tab in Vera's menu and following the instructions where you remove Vera's black Z-Wave dongle and carry it to your Z-Wave device. But, battery-operated handheld controllers are special cases. To add them you leave Vera's black dongle connected, bring them to Vera, and chose the 'Add Z-Wave Controller' option instead. In general, when adding these handheld controllers, there are a few more steps, as explained below. Most in-wall controllers that are connected to your house's electricity (i.e. ''not'' battery operated) can be added like any other Z-Wave device and do not need to be treated like the battery operated controllers. (See '''Supported controllers/gateways''' below for a list.) <br />
<br />
To assign the scene to a button on a handheld remote or scene controller, create the scene, click 'Add Event' next to the scene, choose the scene controller or handheld remote, choose the event 'A Scene is Activated', and pick the scene or button ID, such as 3 for button 3 on a scene controller. In a traditional Z-Wave network, handheld remotes and scene controllers can only control certain scene-capable light switches and lamp modules. But Vera automatically extends the capabilities of Z-Wave so all the commands in your scene will be activated when you press the button.<br />
<br />
For any commands in the scene that go to scene capable devices, namely Z-Wave scene capable light switches and lamp modules, Vera will program the scene controller or remote to talk directly to those scene capable devices. And, if the remote or scene controller has Up/Down or Off buttons, they will be sent directly to the scene capable devices. For any commands you assign to the scene which are not for scene-capable devices, like door locks, thermostats, non-scene capable lamp modules, etc., Vera will monitor the button pushes on your scene controller or handheld remote and automatically take care of the rest of the commands.<br />
<br />
The first step is to add the controller into Vera. <br />
<br />
== Adding battery operated handheld controllers to Vera ==<br />
<br />
[[Image:AddZ-Wave.jpg|thumb|center|512px|Add Z-Wave Controller Screen]] <br />
<br />
When you want to add a handheld Z-Wave controller, go to Vera's [[Quick Start|setup page]], choose the "Devices" tab, and click the "Add Z-Wave controller" link or button. You will have 60 seconds to add the controller to an existing Z-Wave network, by bringing the handheld controller within 3 feet (1 meter) of Vera and pressing the buttons on the handheld controller. This process is different for each handheld controller, and is often given different names. A chart of some popular Z-Wave handheld controllers is shown below, along with the steps to add the controller to Vera, and what the process is called. Vera shows the status and progress in blue at the top of the page, starting with: "''Running: Job is waiting: Ready...''", which means Vera is waiting for your handheld controller to start. <br />
<br />
If you cannot add the controller to Vera, it's possible the controller is already part of another Z-Wave network. In this case, you must first reset the controller before you can add it to Vera. Instructions for resetting some popular controllers are shown below.<br />
<br />
== Adding in-wall scene controllers to Vera ==<br />
<br />
As mentioned above, in general you can add these devices like any other Z-Wave device and don't need to use the 'Add Z-Wave Controller' link. <br />
<br />
== '''Supported controllers/gateways''' ==<br />
<br />
'''These devices are added by bringing the controller near Vera and choosing 'Add Z-Wave Controller'.''' <br />
<br />
The 'Add Sequence' is how you tell the controller to add to Vera. The 'Reset Sequence' is how you clear the controller if it's already been added to another Z-Wave network and can't be added to Vera. <br />
<br />
{| cellpadding="2" border="1"<br />
|-<br />
! Manufacturer <br />
! Device Type <br />
! Model no. <br />
! Version <br />
! Specs <br />
! Product Review <br />
! Add Sequence <br />
! Reset Sequence <br />
! Notes<br />
|-<br />
| Cooper Wiring Devices <br />
| Handheld Controller <br />
| RFHDCSG <br />
| <br> <br />
| [http://store.homeseer.com/store/RFHDCSG---Z-Wave-Handheld-Controller-Cooper-Aspire-RF-P477C56.aspx Link] <br />
| [http://store.homeseer.com/store/RFHDCSG---Z-Wave-Handheld-Controller-Cooper-Aspire-RF-P477C56.aspx Link] <br />
| Menu, Settings, Replicate, Receive, From Unknown Controller <br />
| Menu, Settings, Reset <br />
| Works well with Vera. Can transfer devices from Vera to the handheld but doesn't transfer device names. Also very expensive.<br />
|-<br />
| Intermatic <br />
| Handheld Controller <br />
| HA07 <br />
| <br> <br />
| [http://www.intermatic.com/images/instruction_sheets/158ha11645-art.pdf Link] <br />
| <br> <br />
| <br> <br />
| <br> <br />
| Read [[Intermatic Handheld Remotes]]<br />
|-<br />
| GE/Jasco Products<br />
| Handheld Controller <br />
| Z-Wave Home Theater Remote-45608 <br />
| <br> <br />
| [http://www.jascoproducts.com/z-wave/Z-Wave-Products.asp Link] <br />
| [http://www.myhomeserver.com/?page_id=236 Link] <br />
| Read the detailed instructions here: [[GE_Home_Theater_45608]]<br />
| RESET: Z-Wave Setup mode, scroll to NETWORK, press OK and displays RESET. Click OK to reset the Z-wave on remote. This will not remove the remote from Vera's network. So if it's already been added to Vera's network follow the instructions here: [[GE_Home_Theater_45608]]<br />
| Works well with Vera, Also controls A/V devices and includes X10 IR codes and Logitech Squeezebox IR codes, blue blacklit buttons, LCD screen allows editing labels of scenes, devices, etc. Can also control Z-Wave and A/V devices using macros so you can "play DVD" and the lights will dim with this command. VERY NICE REMOTE!<br />
|-<br />
| Wayne Dalton <br />
| Gateway <br />
| WDHA-12R <br />
| &nbsp;?? <br />
| [http://www.waynedaltonstore.com/product/74171410873.html Link] <br />
| [http://www.zwaveworld.com/prodrevs/091406/reviews-pg4.php Link] <br />
| See detailed instructions here: [[Wayne-Dalton_WDHA-12]] <br />
| <br> <br />
| Shows as Z-Wave controller and enables use of Homelink car remote, so can now turn on/off All Z-wave devices from car. '''This gateway is required for the 3-button remote sold by them.''' Translates commands to Z-Wave Scenes. As of firmware 1.0.602 it's working with Vera, it's seen as a secondary controller.<br />
|-<br />
| Wayne Dalton <br />
| Handheld Controller <br />
| WDHC-20 <br />
| &nbsp; <br />
| &nbsp; <br />
| &nbsp; <br />
| Add Zwave Controller in Vera, on remote; HOME, hold SETUP until HOME blinks twice, enter 967, HOME blinks twice if successful. Create the scenes and assign them to the scene controller as described earlier. Click 'Save', and then go to the device and click Configure node right now on Vera, and repeat on remote. <br />
| &nbsp; <br />
| I added this about a week ago, and typed this from memory, so it may not work 100%, but I know it does have to be programmed on the remote twice. Only On works, couldn't find setting for Off, don't have a dimmer to test Bright/Dim.<br />
|-<br />
| Innovus <br />
| Handheld Controller <br />
| SmoothRemote <br />
| <br />
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smoothremote-00120001-tech.pdf Link] <br />
| <br />
| <br />
1. Add Z-Wave Controller on Vera<br>2. Press 3 times shift (Button 9)<br>3. Configure device on Vera (Associations)<br>4. To transfer your config settings, repeat step 1 &amp; 2<br> <br />
<br />
| <br />
| Device can be configured using Vera. Has no scene buttons, so you can not trigger scenes with it (V1.0.616) which hopefully will be changed in further versions. Button 8 is always "ALL ON / ALL OFF"<br />
|}<br />
<br />
<br> <br />
<br />
<br> '''These devices are added like normal Z-Wave devices by choosing 'Add other Z-Wave devices' on Vera's menu and bringing Vera's Z-Wave dongle to the device''' <br />
<br />
{| cellpadding="2" border="1"<br />
|-<br />
! Manufacturer <br />
! Device Type <br />
! Model no. <br />
! Version <br />
! Specs <br />
! Product Review <br />
! Add Sequence <br />
! Reset Sequence <br />
! Notes<br />
|-<br />
| Cooper <br />
| 5 Scene Controller <br />
| RFWDC <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| Read [[Cooper Scene Controller]]<br />
|-<br />
| Leviton <br />
| 4 Scene Controller <br />
| RZCS4 <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| Read [[Leviton Scene Controller]]<br />
|-<br />
| Leviton <br />
| 1 Scene Controller <br />
| RZCZ1-1LX <br />
| Unknown <br />
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=106&products_id=116 Link] <br />
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=106&products_id=116 Link] <br />
| [http://www.leviton.com/OA_HTML/ibcGetAttachment.jsp?cItemId=4K.TQNnHt8AaVpmZu8gZrg&label=IBE&appName=IBE&LC12RP=qKakohvv7vJh2mB6bpElERJ8:S&LC12RP_pses=ZG4A2E9F82D5405FB0AA12ACDF90AC2545B909744B9ED50C8FDF1E42E5DDB0DBDAA696B9BE833B1E5A5FAF3CD3DD6FEF48EE84A0FF16567733 Link] <br />
| <br> <br />
| Read [[Leviton Scene Controller]]<br />
|}<br />
<br />
== '''Unsupported / Partially supported controllers/gateways''' ==<br />
<br />
Not working as of firmware version wl500gP-1.0.584.trx <br />
<br />
{| cellpadding="2" border="1"<br />
|-<br />
! Manufacturer <br />
! Model <br />
! Specs <br />
! Product Review <br />
! Notes<br />
|-<br />
| Sylvania <br />
| SH50201 <br />
| &nbsp;<br />
| &nbsp;<br />
| '''"all on" and "all off" buttons work but scene buttons are not supported at this time. (3/28/2009)''' <br />
To program this controller put vera in add controller mode and then hit "menu", then press right arrow until you see setup. Press ok. Righ arrow to copy remote control. Press ok. Right arrow to receive information and click ok. Wait for vera to confirm the controller was added. <br />
<br />
|-<br />
| ACT HomePro <br />
| ZTH100 <br />
| &nbsp;<br />
| &nbsp;<br />
| Sylvania is a rebranded ACT Homepro '''"all on" and "all off" buttons work but scene buttons are not supported at this time. (3/28/2009)'''<br />
|-<br />
| Merten<br />
| 1-gang radio push button 5051.., 5061.., 5071..<br />
| [http://www.merten.de/download/DL_doku/V5051_581_01_web.pdf Link]<br />
| &nbsp;<br />
| Use scene no. 0 for button 0 and scene no. 255 for button 1 (2009-09-30, firmware 1.0.900)<br />
|-<br />
| Merten<br />
| 2-gang radio push button 5052.., 5062.., 5072..<br />
| [http://www.merten.de/download/DL_doku/V5051_581_01_web.pdf Link]<br />
| &nbsp;<br />
| Only buttons 0 and 1 work; use scene no. 0 for button 0 and scene no. 255 for button 1 (2009-09-30, firmware 1.0.900)<br />
|}<br />
<br />
== '''Troubleshooting''' ==<br />
<br />
In case your controller it's not working please follow this steps before submitting a trouble report.<br />
<br />
1. Open Vera's Dashboard <br><br />
2. Go to Advanced and enable Verbose Logging <br><br />
3. Go to Location choose your timezone and synchronize your watch <br><br />
4. Go to Devices->Zwave->More Zwave Options tab and where it says <br><br />
"House/Node", make note of the node ID of your dongle (node x.y where x is the node id). <br> <br />
5. Go to Devices->Zwave tab, if you have any devices called "ZWave Controller/Scene Controller" besides the built-in <br>one, be sure to rename them so you can tell which is which. <br />
Also be sure 'scenes as events' is not checked for this controller. <br><br />
6. Go to Devices->Zwave, expand your controller properties by clicking on the "+" sign near it and then press 'Custom Zwave Settings'.<br> <br />
Under Associations add group 2 and when you click 'set', add 2 associations: both the device you want to control *and* the <br><br />
"ZWave Controller" (ie Vera's dongle), which is probably in the 'unassigned' area. <br><br />
Press SAVE and wait until the 'Please wait.... configuring' is done. <br><br />
7. Press every button on your controller and note the exact time at which you've press it. <br><br />
8. Go to Advanced->Tech Support and submit a trouble report in which you have to indicate <br><br />
- the controller make and model and a link to its user manual <br><br />
- the controller's NodeID <br><br />
- the time when you hit 'configure right now' and when you hit each button <br></div>Charlieohttp://wiki.mios.com/index.php/ZWave_Add_ControllerZWave Add Controller2010-01-24T02:19:50Z<p>Charlieo: </p>
<hr />
<div>With most Z-Wave devices, you add them to Vera's Z-Wave network by clicking the 'Add other Z-Wave devices' on the 'Devices' tab in Vera's menu and following the instructions where you remove Vera's black Z-Wave dongle and carry it to your Z-Wave device. But, battery-operated handheld controllers are special cases. To add them you leave Vera's black dongle connected, bring them to Vera, and chose the 'Add Z-Wave Controller' option instead. In general, when adding these handheld controllers, there are a few more steps, as explained below. Most in-wall controllers that are connected to your house's electricity (i.e. ''not'' battery operated) can be added like any other Z-Wave device and do not need to be treated like the battery operated controllers. (See '''Supported controllers/gateways''' below for a list.) <br />
<br />
To assign the scene to a button on a handheld remote or scene controller, create the scene, click 'Add Event' next to the scene, choose the scene controller or handheld remote, choose the event 'A Scene is Activated', and pick the scene or button ID, such as 3 for button 3 on a scene controller. In a traditional Z-Wave network, handheld remotes and scene controllers can only control certain scene-capable light switches and lamp modules. But Vera automatically extends the capabilities of Z-Wave so all the commands in your scene will be activated when you press the button.<br />
<br />
For any commands in the scene that go to scene capable devices, namely Z-Wave scene capable light switches and lamp modules, Vera will program the scene controller or remote to talk directly to those scene capable devices. And, if the remote or scene controller has Up/Down or Off buttons, they will be sent directly to the scene capable devices. For any commands you assign to the scene which are not for scene-capable devices, like door locks, thermostats, non-scene capable lamp modules, etc., Vera will monitor the button pushes on your scene controller or handheld remote and automatically take care of the rest of the commands.<br />
<br />
The first step is to add the controller into Vera. <br />
<br />
== Adding battery operated handheld controllers to Vera ==<br />
<br />
[[Image:AddZ-Wave.jpg|thumb|center|512px|Add Z-Wave Controller Screen]] <br />
<br />
When you want to add a handheld Z-Wave controller, go to Vera's [[Quick Start|setup page]], choose the "Devices" tab, and click the "Add Z-Wave controller" link or button. You will have 60 seconds to add the controller to an existing Z-Wave network, by bringing the handheld controller within 3 feet (1 meter) of Vera and pressing the buttons on the handheld controller. This process is different for each handheld controller, and is often given different names. A chart of some popular Z-Wave handheld controllers is shown below, along with the steps to add the controller to Vera, and what the process is called. Vera shows the status and progress in blue at the top of the page, starting with: "''Running: Job is waiting: Ready...''", which means Vera is waiting for your handheld controller to start. <br />
<br />
If you cannot add the controller to Vera, it's possible the controller is already part of another Z-Wave network. In this case, you must first reset the controller before you can add it to Vera. Instructions for resetting some popular controllers are shown below.<br />
<br />
== Adding in-wall scene controllers to Vera ==<br />
<br />
As mentioned above, in general you can add these devices like any other Z-Wave device and don't need to use the 'Add Z-Wave Controller' link. <br />
<br />
== '''Supported controllers/gateways''' ==<br />
<br />
'''These devices are added by bringing the controller near Vera and choosing 'Add Z-Wave Controller'.''' <br />
<br />
The 'Add Sequence' is how you tell the controller to add to Vera. The 'Reset Sequence' is how you clear the controller if it's already been added to another Z-Wave network and can't be added to Vera. <br />
<br />
{| cellpadding="2" border="1"<br />
|-<br />
! Manufacturer <br />
! Device Type <br />
! Model no. <br />
! Version <br />
! Specs <br />
! Product Review <br />
! Add Sequence <br />
! Reset Sequence <br />
! Notes<br />
|-<br />
| Cooper Wiring Devices <br />
| Handheld Controller <br />
| RFHDCSG <br />
| <br> <br />
| [http://store.homeseer.com/store/RFHDCSG---Z-Wave-Handheld-Controller-Cooper-Aspire-RF-P477C56.aspx Link] <br />
| [http://store.homeseer.com/store/RFHDCSG---Z-Wave-Handheld-Controller-Cooper-Aspire-RF-P477C56.aspx Link] <br />
| Menu, Settings, Replicate, Receive, From Unknown Controller <br />
| Menu, Settings, Reset <br />
| Works well with Vera. Can transfer devices from Vera to the handheld but doesn't transfer device names. Also very expensive.<br />
|-<br />
| Intermatic <br />
| Handheld Controller <br />
| HA07 <br />
| <br> <br />
| [http://www.intermatic.com/images/instruction_sheets/158ha11645-art.pdf Link] <br />
| <br> <br />
| <br> <br />
| <br> <br />
| Read [[Intermatic Handheld Remotes]]<br />
|-<br />
| GE/Jasco Products<br />
| Handheld Controller <br />
| Z-Wave Home Theater Remote-45608 <br />
| <br> <br />
| [http://www.jascoproducts.com/z-wave/Z-Wave-Products.asp Link] <br />
| [http://www.myhomeserver.com/?page_id=236 Link] <br />
| Read the detailed instructions here: [[GE_Home_Theater_45608]]<br />
| RESET: Z-Wave Setup mode, scroll to NETWORK, press OK and displays RESET. Click OK to reset the Z-wave on remote. This will not remove the remote from Vera's network. So if it's already been added to Vera's network follow the instructions here: [[GE_Home_Theater_45608]]<br />
| Works well with Vera, Also controls A/V devices and includes X10 IR codes and Logitech Squeezebox IR codes, blue blacklit buttons, LCD screen allows editing labels of scenes, devices, etc. Can also control Z-Wave and A/V devices using macros so you can "play DVD" and the lights will dim with this command. VERY NICE REMOTE!<br />
|-<br />
| Wayne Dalton <br />
| Gateway <br />
| WDHA-12R <br />
| &nbsp;?? <br />
| [http://www.waynedaltonstore.com/product/74171410873.html Link] <br />
| [http://www.zwaveworld.com/prodrevs/091406/reviews-pg4.php Link] <br />
| See detailed instructions here: [http://wiki.micasaverde.com/index.php/Wayne-Dalton_WDHA-12] <br />
| <br> <br />
| Shows as Z-Wave controller and enables use of Homelink car remote, so can now turn on/off All Z-wave devices from car. '''This gateway is required for the 3-button remote sold by them.''' Translates commands to Z-Wave Scenes. As of firmware 1.0.602 it's working with Vera, it's seen as a secondary controller.<br />
|-<br />
| Wayne Dalton <br />
| Handheld Controller <br />
| WDHC-20 <br />
| &nbsp; <br />
| &nbsp; <br />
| &nbsp; <br />
| Add Zwave Controller in Vera, on remote; HOME, hold SETUP until HOME blinks twice, enter 967, HOME blinks twice if successful. Create the scenes and assign them to the scene controller as described earlier. Click 'Save', and then go to the device and click Configure node right now on Vera, and repeat on remote. <br />
| &nbsp; <br />
| I added this about a week ago, and typed this from memory, so it may not work 100%, but I know it does have to be programmed on the remote twice. Only On works, couldn't find setting for Off, don't have a dimmer to test Bright/Dim.<br />
|-<br />
| Innovus <br />
| Handheld Controller <br />
| SmoothRemote <br />
| <br />
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smoothremote-00120001-tech.pdf Link] <br />
| <br />
| <br />
1. Add Z-Wave Controller on Vera<br>2. Press 3 times shift (Button 9)<br>3. Configure device on Vera (Associations)<br>4. To transfer your config settings, repeat step 1 &amp; 2<br> <br />
<br />
| <br />
| Device can be configured using Vera. Has no scene buttons, so you can not trigger scenes with it (V1.0.616) which hopefully will be changed in further versions. Button 8 is always "ALL ON / ALL OFF"<br />
|}<br />
<br />
<br> <br />
<br />
<br> '''These devices are added like normal Z-Wave devices by choosing 'Add other Z-Wave devices' on Vera's menu and bringing Vera's Z-Wave dongle to the device''' <br />
<br />
{| cellpadding="2" border="1"<br />
|-<br />
! Manufacturer <br />
! Device Type <br />
! Model no. <br />
! Version <br />
! Specs <br />
! Product Review <br />
! Add Sequence <br />
! Reset Sequence <br />
! Notes<br />
|-<br />
| Cooper <br />
| 5 Scene Controller <br />
| RFWDC <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| Read [[Cooper Scene Controller]]<br />
|-<br />
| Leviton <br />
| 4 Scene Controller <br />
| RZCS4 <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| Read [[Leviton Scene Controller]]<br />
|-<br />
| Leviton <br />
| 1 Scene Controller <br />
| RZCZ1-1LX <br />
| Unknown <br />
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=106&products_id=116 Link] <br />
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=106&products_id=116 Link] <br />
| [http://www.leviton.com/OA_HTML/ibcGetAttachment.jsp?cItemId=4K.TQNnHt8AaVpmZu8gZrg&label=IBE&appName=IBE&LC12RP=qKakohvv7vJh2mB6bpElERJ8:S&LC12RP_pses=ZG4A2E9F82D5405FB0AA12ACDF90AC2545B909744B9ED50C8FDF1E42E5DDB0DBDAA696B9BE833B1E5A5FAF3CD3DD6FEF48EE84A0FF16567733 Link] <br />
| <br> <br />
| Read [[Leviton Scene Controller]]<br />
|}<br />
<br />
== '''Unsupported / Partially supported controllers/gateways''' ==<br />
<br />
Not working as of firmware version wl500gP-1.0.584.trx <br />
<br />
{| cellpadding="2" border="1"<br />
|-<br />
! Manufacturer <br />
! Model <br />
! Specs <br />
! Product Review <br />
! Notes<br />
|-<br />
| Sylvania <br />
| SH50201 <br />
| &nbsp;<br />
| &nbsp;<br />
| '''"all on" and "all off" buttons work but scene buttons are not supported at this time. (3/28/2009)''' <br />
To program this controller put vera in add controller mode and then hit "menu", then press right arrow until you see setup. Press ok. Righ arrow to copy remote control. Press ok. Right arrow to receive information and click ok. Wait for vera to confirm the controller was added. <br />
<br />
|-<br />
| ACT HomePro <br />
| ZTH100 <br />
| &nbsp;<br />
| &nbsp;<br />
| Sylvania is a rebranded ACT Homepro '''"all on" and "all off" buttons work but scene buttons are not supported at this time. (3/28/2009)'''<br />
|-<br />
| Merten<br />
| 1-gang radio push button 5051.., 5061.., 5071..<br />
| [http://www.merten.de/download/DL_doku/V5051_581_01_web.pdf Link]<br />
| &nbsp;<br />
| Use scene no. 0 for button 0 and scene no. 255 for button 1 (2009-09-30, firmware 1.0.900)<br />
|-<br />
| Merten<br />
| 2-gang radio push button 5052.., 5062.., 5072..<br />
| [http://www.merten.de/download/DL_doku/V5051_581_01_web.pdf Link]<br />
| &nbsp;<br />
| Only buttons 0 and 1 work; use scene no. 0 for button 0 and scene no. 255 for button 1 (2009-09-30, firmware 1.0.900)<br />
|}<br />
<br />
== '''Troubleshooting''' ==<br />
<br />
In case your controller it's not working please follow this steps before submitting a trouble report.<br />
<br />
1. Open Vera's Dashboard <br><br />
2. Go to Advanced and enable Verbose Logging <br><br />
3. Go to Location choose your timezone and synchronize your watch <br><br />
4. Go to Devices->Zwave->More Zwave Options tab and where it says <br><br />
"House/Node", make note of the node ID of your dongle (node x.y where x is the node id). <br> <br />
5. Go to Devices->Zwave tab, if you have any devices called "ZWave Controller/Scene Controller" besides the built-in <br>one, be sure to rename them so you can tell which is which. <br />
Also be sure 'scenes as events' is not checked for this controller. <br><br />
6. Go to Devices->Zwave, expand your controller properties by clicking on the "+" sign near it and then press 'Custom Zwave Settings'.<br> <br />
Under Associations add group 2 and when you click 'set', add 2 associations: both the device you want to control *and* the <br><br />
"ZWave Controller" (ie Vera's dongle), which is probably in the 'unassigned' area. <br><br />
Press SAVE and wait until the 'Please wait.... configuring' is done. <br><br />
7. Press every button on your controller and note the exact time at which you've press it. <br><br />
8. Go to Advanced->Tech Support and submit a trouble report in which you have to indicate <br><br />
- the controller make and model and a link to its user manual <br><br />
- the controller's NodeID <br><br />
- the time when you hit 'configure right now' and when you hit each button <br></div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-23T07:32:38Z<p>Charlieo: </p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-2010 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
<br />
<br />
'''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>'''<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click Advanced, then click Logs and then Show Z-Wave jobs. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-23T07:31:46Z<p>Charlieo: </p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-2010 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>'''<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click Advanced, then click Logs and then Show Z-Wave jobs. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-23T07:31:13Z<p>Charlieo: </p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-10 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u></u>'''<br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>'''<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click Advanced, then click Logs and then Show Z-Wave jobs. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/User:CharlieoUser:Charlieo2010-01-23T07:29:20Z<p>Charlieo: User:Charlieo moved to Wayne-Dalton WDHA-12</p>
<hr />
<div>#REDIRECT [[Wayne-Dalton WDHA-12]]</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-23T07:29:20Z<p>Charlieo: User:Charlieo moved to Wayne-Dalton WDHA-12</p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-10 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>''' <br />
<br />
<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click Advanced, then click Logs and then Show Z-Wave jobs. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-23T07:26:51Z<p>Charlieo: Wayne-Dalton WDHA-12</p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-10 based on Vera firmware 1.0.979)<br> <br />
<br />
<br> <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>''' <br />
<br />
'''<u></u>''' <br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>''' <br />
<br />
<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click Advanced, then click Logs and then Show Z-Wave jobs. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-23T07:25:26Z<p>Charlieo: </p>
<hr />
<div>== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-10 based on Vera firmware 1.0.979)<br> <br />
<br />
<br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br> <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br> <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br> <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br> <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br> <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br> <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.&nbsp; <u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] '''<u></u>'''<br />
<br />
'''<u></u>'''<br />
<br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>''' <br />
<br />
<br> Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br> <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click Advanced, then click Logs and then Show Z-Wave jobs. <br />
<br />
<br> <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-23T07:23:21Z<p>Charlieo: </p>
<hr />
<div>== '''<span style="font-size: 12pt;" />How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==<br />
<br />
(written Jan-10 based on Vera firmware 1.0.979) <br />
<br />
<br><br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
<br><br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
'''<u>Step 1 – Set up Vera.</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
<br><br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
<br><br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
<br><br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
<br><br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
<br><br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller. <br />
<br />
<br><br />
<br />
<u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] <br />
'''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.</u>'''<br />
<br />
<br />
Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
<br><br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
'''<u>Step 4 – Test.</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
<br><br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click Advanced, then click Logs and then Show Z-Wave jobs. <br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink.</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/Wayne-Dalton_WDHA-12Wayne-Dalton WDHA-122010-01-23T07:18:22Z<p>Charlieo: Wayne-Dalton WDHA-12</p>
<hr />
<div>&lt;meta content="text/html; charset=utf-8" http-equiv="Content-Type"&gt;&lt;/meta&gt;&lt;meta content="Word.Document" name="ProgId"&gt;&lt;/meta&gt;&lt;meta content="Microsoft Word 11" name="Generator"&gt;&lt;/meta&gt;&lt;meta content="Microsoft Word 11" name="Originator"&gt;&lt;/meta&gt;&lt;link href="file:///C:%5CDOCUME%7E1%5Ccharlieo%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml" rel="File-List"&gt;&lt;/link&gt;<!--[if gte mso 9]><xml><br />
<w:WordDocument><br />
<w:View>Normal</w:View><br />
<w:Zoom>0</w:Zoom><br />
<w:PunctuationKerning/><br />
<w:ValidateAgainstSchemas/><br />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
<w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
<w:Compatibility><br />
<w:BreakWrappedTables/><br />
<w:SnapToGridInCell/><br />
<w:WrapTextWithPunct/><br />
<w:UseAsianBreakRules/><br />
<w:DontGrowAutofit/><br />
<w:UseFELayout/><br />
</w:Compatibility><br />
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel><br />
</w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
<w:LatentStyles DefLockedState="false" LatentStyleCount="156"><br />
</w:LatentStyles><br />
</xml><![endif]-->&lt;style&gt;&lt;!-- /* Font Definitions */ @font-face {font-family:"MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4; mso-font-alt:"Kozuka Mincho Pro R"; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} @font-face {font-family:"\@MS Mincho"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; mso-bidi-font-size:12.0pt; font-family:Arial; mso-fareast-font-family:"MS Mincho"; mso-bidi-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --&gt; &lt;/style&gt;<!--[if gte mso 10]><br />
<style><br />
/* Style Definitions */<br />
table.MsoNormalTable<br />
{mso-style-name:"Table Normal";<br />
mso-tstyle-rowband-size:0;<br />
mso-tstyle-colband-size:0;<br />
mso-style-noshow:yes;<br />
mso-style-parent:"";<br />
mso-padding-alt:0in 5.4pt 0in 5.4pt;<br />
mso-para-margin:0in;<br />
mso-para-margin-bottom:.0001pt;<br />
mso-pagination:widow-orphan;<br />
font-size:10.0pt;<br />
font-family:"Times New Roman";<br />
mso-fareast-font-family:"Times New Roman";<br />
mso-ansi-language:#0400;<br />
mso-fareast-language:#0400;<br />
mso-bidi-language:#0400;}<br />
</style><br />
<![endif]--> <br />
<br />
'''<u><span style="font-size: 12pt;">How to Configure Vera with</span></u>''' <u>Wayne-Dalton WDHA-12 Gateway&lt;o:p&gt;&lt;/o:p&gt;</u> <br />
<br />
(written Jan-10 based on Vera firmware 1.0.979) <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.<span style="">&nbsp; </span>Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort). <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
The Gateway is configured as a secondary Z-wave controller which means that it’s only role is to forward commands to Vera.<span style="">&nbsp; </span>Once configured as a secondary controller, it no longer speaks directly to devices, rather it only forwards commands to Vera (the primary controller in the configuration below) which in turn sends on the commands to devices.<span style="">&nbsp; </span>The Gateway has 3 scene buttons and each can be attached to a different scene in Vera. <br />
<br />
<br> <br />
<br />
[[Image:Co1b.jpg]]<br> <br />
<br />
<br> <br />
<br />
&lt;meta content="text/html; charset=utf-8" http-equiv="Content-Type"&gt;&lt;/meta&gt;&lt;meta content="Word.Document" name="ProgId"&gt;&lt;/meta&gt;&lt;meta content="Microsoft Word 11" name="Generator"&gt;&lt;/meta&gt;&lt;meta content="Microsoft Word 11" name="Originator"&gt;&lt;/meta&gt;&lt;link href="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_filelist.xml" rel="File-List"&gt;&lt;/link&gt;&lt;link href="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_editdata.mso" rel="Edit-Time-Data"&gt;&lt;/link&gt;<!--[if !mso]><br />
<style><br />
v\:* {behavior:url(#default#VML);}<br />
o\:* {behavior:url(#default#VML);}<br />
w\:* {behavior:url(#default#VML);}<br />
.shape {behavior:url(#default#VML);}<br />
</style><br />
<![endif]--><!--[if gte mso 9]><xml><br />
<w:WordDocument><br />
<w:View>Normal</w:View><br />
<w:Zoom>0</w:Zoom><br />
<w:PunctuationKerning/><br />
<w:ValidateAgainstSchemas/><br />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
<w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
<w:Compatibility><br />
<w:BreakWrappedTables/><br />
<w:SnapToGridInCell/><br />
<w:WrapTextWithPunct/><br />
<w:UseAsianBreakRules/><br />
<w:DontGrowAutofit/><br />
<w:UseFELayout/><br />
</w:Compatibility><br />
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel><br />
</w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
<w:LatentStyles DefLockedState="false" LatentStyleCount="156"><br />
</w:LatentStyles><br />
</xml><![endif]-->&lt;style&gt;&lt;!-- /* Font Definitions */ @font-face {font-family:"MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4; mso-font-alt:"Kozuka Mincho Pro R"; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} @font-face {font-family:"\@MS Mincho"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; mso-bidi-font-size:12.0pt; font-family:Arial; mso-fareast-font-family:"MS Mincho"; mso-bidi-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --&gt; &lt;/style&gt;<!--[if gte mso 10]><br />
<style><br />
/* Style Definitions */<br />
table.MsoNormalTable<br />
{mso-style-name:"Table Normal";<br />
mso-tstyle-rowband-size:0;<br />
mso-tstyle-colband-size:0;<br />
mso-style-noshow:yes;<br />
mso-style-parent:"";<br />
mso-padding-alt:0in 5.4pt 0in 5.4pt;<br />
mso-para-margin:0in;<br />
mso-para-margin-bottom:.0001pt;<br />
mso-pagination:widow-orphan;<br />
font-size:10.0pt;<br />
font-family:"Times New Roman";<br />
mso-fareast-font-family:"Times New Roman";<br />
mso-ansi-language:#0400;<br />
mso-fareast-language:#0400;<br />
mso-bidi-language:#0400;}<br />
</style><br />
<![endif]--><!--[if gte mso 9]><xml><br />
<o:shapedefaults v:ext="edit" spidmax="1028"/><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
<o:shapelayout v:ext="edit"><br />
<o:idmap v:ext="edit" data="1"/><br />
</o:shapelayout></xml><![endif]--> '''<u>Step 1 – Set up Vera&lt;o:p&gt;&lt;/o:p&gt;</u>''' <br />
<br />
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with. <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.&lt;o:p&gt;&lt;/o:p&gt;</u>''' <br />
<br />
Make sure you’re logged in to Vera. <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
On the Gateway, press copy button <u>AND THEN</u> press Scene 1 button (despite what the Gateway instructions say, if you press copy and Scene 1 at the same time the process doesn’t seem to work).<span style="">&nbsp; </span>Hold both buttons until all three LEDs light up and then release both. <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
Immediately after above, go to Vera Dashboard, click '''Setup''', then click '''Devices''' and then click '''Z-Wave'''.<span style="">&nbsp; </span>Now click “'''Add Z-Wave controller'''”.<span style="">&nbsp; </span>Within 60 seconds you will see “device detected.<span style="">&nbsp;<br />
</span>Added Node n” <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;<br />
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again. <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:54pt;height:45pt;z-index:2'<br />
filled="f" strokecolor="red" strokeweight="3pt"/><![endif]--><!--[if !vml]--><!--[endif]--><!--[if gte vml 1]><v:shapetype id="_x0000_t75"<br />
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"<br />
filled="f" stroked="f"><br />
<v:stroke joinstyle="miter"/><br />
<v:formulas><br />
<v:f eqn="if lineDrawn pixelLineWidth 0"/><br />
<v:f eqn="sum @0 1 0"/><br />
<v:f eqn="sum 0 0 @1"/><br />
<v:f eqn="prod @2 1 2"/><br />
<v:f eqn="prod @3 21600 pixelWidth"/><br />
<v:f eqn="prod @3 21600 pixelHeight"/><br />
<v:f eqn="sum @0 0 1"/><br />
<v:f eqn="prod @6 1 2"/><br />
<v:f eqn="prod @7 21600 pixelWidth"/><br />
<v:f eqn="sum @8 21600 0"/><br />
<v:f eqn="prod @7 21600 pixelHeight"/><br />
<v:f eqn="sum @10 21600 0"/><br />
</v:formulas><br />
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/><br />
<o:lock v:ext="edit" aspectratio="t"/><br />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" style='position:absolute;<br />
margin-left:270pt;margin-top:2.75pt;width:208.5pt;height:78.7pt;z-index:-2'<br />
wrapcoords="-41 0 -41 21492 21600 21492 21600 0 -41 0"><br />
<v:imagedata src="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_image002.png"<br />
o:title=""/><br />
<w:wrap type="tight"/><br />
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller. <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
<u>Note:</u> In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.<span style="">&nbsp; </span>This does not seem to matter. <br />
<br />
[[Image:Co2a.jpg]] <br />
<br />
<br> <br />
<br />
&lt;meta content="text/html; charset=utf-8" http-equiv="Content-Type"&gt;&lt;/meta&gt;&lt;meta content="Word.Document" name="ProgId"&gt;&lt;/meta&gt;&lt;meta content="Microsoft Word 11" name="Generator"&gt;&lt;/meta&gt;&lt;meta content="Microsoft Word 11" name="Originator"&gt;&lt;/meta&gt;&lt;link href="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_filelist.xml" rel="File-List"&gt;&lt;/link&gt;<!--[if gte mso 9]><xml><br />
<w:WordDocument><br />
<w:View>Normal</w:View><br />
<w:Zoom>0</w:Zoom><br />
<w:PunctuationKerning/><br />
<w:ValidateAgainstSchemas/><br />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
<w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
<w:Compatibility><br />
<w:BreakWrappedTables/><br />
<w:SnapToGridInCell/><br />
<w:WrapTextWithPunct/><br />
<w:UseAsianBreakRules/><br />
<w:DontGrowAutofit/><br />
<w:UseFELayout/><br />
</w:Compatibility><br />
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel><br />
</w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
<w:LatentStyles DefLockedState="false" LatentStyleCount="156"><br />
</w:LatentStyles><br />
</xml><![endif]-->&lt;style&gt;&lt;!-- /* Font Definitions */ @font-face {font-family:"MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4; mso-font-alt:"Kozuka Mincho Pro R"; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} @font-face {font-family:"\@MS Mincho"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; mso-bidi-font-size:12.0pt; font-family:Arial; mso-fareast-font-family:"MS Mincho"; mso-bidi-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --&gt; &lt;/style&gt;<!--[if gte mso 10]><br />
<style><br />
/* Style Definitions */<br />
table.MsoNormalTable<br />
{mso-style-name:"Table Normal";<br />
mso-tstyle-rowband-size:0;<br />
mso-tstyle-colband-size:0;<br />
mso-style-noshow:yes;<br />
mso-style-parent:"";<br />
mso-padding-alt:0in 5.4pt 0in 5.4pt;<br />
mso-para-margin:0in;<br />
mso-para-margin-bottom:.0001pt;<br />
mso-pagination:widow-orphan;<br />
font-size:10.0pt;<br />
font-family:"Times New Roman";<br />
mso-fareast-font-family:"Times New Roman";<br />
mso-ansi-language:#0400;<br />
mso-fareast-language:#0400;<br />
mso-bidi-language:#0400;}<br />
</style><br />
<![endif]--> '''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.&lt;o:p&gt;&lt;/o:p&gt;</u>''' <br />
<br />
Click '''Scenes'''.<span style="">&nbsp; </span>Click '''Add scene'''. <span style="">&nbsp;</span>Then click '''Add event''', select your scene controller in the '''Devices''' popup and then select Event type “'''A scene is activated'''”.<span style="">&nbsp; </span>Then name the event and type in the digit 1, 2 or 3 in “'''scene number'''” corresponding to the Gateway scene number/button you want to use.<span style="">&nbsp; </span>Finally, choose among the commands available for your device.<span style="">&nbsp; </span> <br />
<br />
&lt;span style="" /&gt; <br />
<br />
<span style="">[[Image:Co3a.jpg]]</span> <br />
<br />
<br> <br />
<br />
&lt;meta content="text/html; charset=utf-8" http-equiv="Content-Type"&gt;&lt;/meta&gt;&lt;meta content="Word.Document" name="ProgId"&gt;&lt;/meta&gt;&lt;meta content="Microsoft Word 11" name="Generator"&gt;&lt;/meta&gt;&lt;meta content="Microsoft Word 11" name="Originator"&gt;&lt;/meta&gt;&lt;link href="file:///C:\DOCUME~1\charlieo\LOCALS~1\Temp\msohtml1\01\clip_filelist.xml" rel="File-List"&gt;&lt;/link&gt;<!--[if gte mso 9]><xml><br />
<w:WordDocument><br />
<w:View>Normal</w:View><br />
<w:Zoom>0</w:Zoom><br />
<w:PunctuationKerning/><br />
<w:ValidateAgainstSchemas/><br />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
<w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
<w:Compatibility><br />
<w:BreakWrappedTables/><br />
<w:SnapToGridInCell/><br />
<w:WrapTextWithPunct/><br />
<w:UseAsianBreakRules/><br />
<w:DontGrowAutofit/><br />
<w:UseFELayout/><br />
</w:Compatibility><br />
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel><br />
</w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
<w:LatentStyles DefLockedState="false" LatentStyleCount="156"><br />
</w:LatentStyles><br />
</xml><![endif]-->&lt;style&gt;&lt;!-- /* Font Definitions */ @font-face {font-family:"MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4; mso-font-alt:"Kozuka Mincho Pro R"; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} @font-face {font-family:"\@MS Mincho"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; mso-bidi-font-size:12.0pt; font-family:Arial; mso-fareast-font-family:"MS Mincho"; mso-bidi-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:.8in .8in .8in .8in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --&gt; &lt;/style&gt;<!--[if gte mso 10]><br />
<style><br />
/* Style Definitions */<br />
table.MsoNormalTable<br />
{mso-style-name:"Table Normal";<br />
mso-tstyle-rowband-size:0;<br />
mso-tstyle-colband-size:0;<br />
mso-style-noshow:yes;<br />
mso-style-parent:"";<br />
mso-padding-alt:0in 5.4pt 0in 5.4pt;<br />
mso-para-margin:0in;<br />
mso-para-margin-bottom:.0001pt;<br />
mso-pagination:widow-orphan;<br />
font-size:10.0pt;<br />
font-family:"Times New Roman";<br />
mso-fareast-font-family:"Times New Roman";<br />
mso-ansi-language:#0400;<br />
mso-fareast-language:#0400;<br />
mso-bidi-language:#0400;}<br />
</style><br />
<![endif]--> '''<u>Step 4 – Test.&lt;o:p&gt;&lt;/o:p&gt;</u>''' <br />
<br />
On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed.<span style="">&nbsp; </span> <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
As a double check, you can look at Vera’s logs.<span style="">&nbsp; </span>Click Advanced, then click Logs and then Show Z-Wave jobs. <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
&lt;o:p&gt;&nbsp;&lt;/o:p&gt; <br />
<br />
'''<u>Optional – Step 5 – Connect to HomeLink&lt;o:p&gt;&lt;/o:p&gt;</u>''' <br />
<br />
To configure a HomeLink controller so that HomeLink triggers the Gateway which in turn triggers a Vera scene, follow the instructions in the WDHA-12 manual.<span style="">&nbsp; </span>One thing to know that the Gateway manual doesn’t tell you:<span style="">&nbsp; </span>To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.<span style="">&nbsp;<br />
</span>However, it will only work as a gateway, once you plug it back into the AC, so you can’t test it while it’s still unplugged.<span style="">&nbsp; </span>It turns out that when the Gateway is unplugged it works as a controller and only works as a Gateway when it’s plugged in.</div>Charlieohttp://wiki.mios.com/index.php/File:Co3a.jpgFile:Co3a.jpg2010-01-23T07:16:07Z<p>Charlieo: uploaded a new version of "Image:Co3a.jpg"</p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co3a.jpgFile:Co3a.jpg2010-01-23T07:14:07Z<p>Charlieo: uploaded a new version of "Image:Co3a.jpg"</p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co3a.jpgFile:Co3a.jpg2010-01-23T07:12:38Z<p>Charlieo: </p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co2a.jpgFile:Co2a.jpg2010-01-23T07:10:35Z<p>Charlieo: </p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co1b.jpgFile:Co1b.jpg2010-01-23T07:07:58Z<p>Charlieo: uploaded a new version of "Image:Co1b.jpg"</p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co1b.jpgFile:Co1b.jpg2010-01-23T07:06:01Z<p>Charlieo: </p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co1a.jpgFile:Co1a.jpg2010-01-23T07:03:45Z<p>Charlieo: </p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co3.jpgFile:Co3.jpg2010-01-23T06:59:39Z<p>Charlieo: </p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co2.jpgFile:Co2.jpg2010-01-23T06:59:23Z<p>Charlieo: </p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Co1.jpgFile:Co1.jpg2010-01-23T06:58:43Z<p>Charlieo: </p>
<hr />
<div></div>Charlieohttp://wiki.mios.com/index.php/File:Wayne_Dalton_WDHA-12_page2.jpgFile:Wayne Dalton WDHA-12 page2.jpg2010-01-23T06:30:20Z<p>Charlieo: Instructions for setting up Wayne Dalton WDHA-12 wireless gateway (for use with HomeLink and WD remotes) with Vera. Page 2 of 2.</p>
<hr />
<div>Instructions for setting up Wayne Dalton WDHA-12 wireless gateway (for use with HomeLink and WD remotes) with Vera. Page 2 of 2.</div>Charlieohttp://wiki.mios.com/index.php/File:Wayne_Dalton_WDHA-12_page1.jpgFile:Wayne Dalton WDHA-12 page1.jpg2010-01-23T06:29:08Z<p>Charlieo: Instructions for setting up Wayne Dalton WDHA-12 wireless gateway (for use with HomeLink and WD remotes) with Vera. Page 1 of 2.</p>
<hr />
<div>Instructions for setting up Wayne Dalton WDHA-12 wireless gateway (for use with HomeLink and WD remotes) with Vera. Page 1 of 2.</div>Charlieo