Wayne-Dalton WDHA-12

From MiOS
(Difference between revisions)
Jump to: navigation, search
(Wayne-Dalton WDHA-12)
 
m
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
&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>
+
[[Category:User Instructions]]
<w:WordDocument>
+
[[Category:Hardware]]
  <w:View>Normal</w:View>
+
== '''How to Configure Vera with Wayne-Dalton WDHA-12 Gateway''' ==
  <w:Zoom>0</w:Zoom>
+
  <w:PunctuationKerning/>
+
  <w:ValidateAgainstSchemas/>
+
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
+
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
+
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
+
  <w:Compatibility>
+
  <w:BreakWrappedTables/>
+
  <w:SnapToGridInCell/>
+
  <w:WrapTextWithPunct/>
+
  <w:UseAsianBreakRules/>
+
  <w:DontGrowAutofit/>
+
  <w:UseFELayout/>
+
  </w:Compatibility>
+
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
+
</w:WordDocument>
+
</xml><![endif]--><!--[if gte mso 9]><xml>
+
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
+
</w:LatentStyles>
+
</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]>
+
<style>
+
  /* Style Definitions */
+
table.MsoNormalTable
+
{mso-style-name:"Table Normal";
+
mso-tstyle-rowband-size:0;
+
mso-tstyle-colband-size:0;
+
mso-style-noshow:yes;
+
mso-style-parent:"";
+
mso-padding-alt:0in 5.4pt 0in 5.4pt;
+
mso-para-margin:0in;
+
mso-para-margin-bottom:.0001pt;
+
mso-pagination:widow-orphan;
+
font-size:10.0pt;
+
font-family:"Times New Roman";
+
mso-fareast-font-family:"Times New Roman";
+
mso-ansi-language:#0400;
+
mso-fareast-language:#0400;
+
mso-bidi-language:#0400;}
+
</style>
+
<![endif]-->
+
  
'''<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>  
+
(written Jan-2010 based on Vera firmware 1.0.979)<br>  
  
(written Jan-10 based on Vera firmware 1.0.979)
+
<br>
 
+
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
  
 
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).  
 
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).  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
<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.  
+
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>  
Line 61: Line 19:
 
<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]>
+
'''<u>Step 1 – Set up Vera.</u>'''  
<style>
+
v\:* {behavior:url(#default#VML);}
+
o\:* {behavior:url(#default#VML);}
+
w\:* {behavior:url(#default#VML);}
+
.shape {behavior:url(#default#VML);}
+
</style>
+
<![endif]--><!--[if gte mso 9]><xml>
+
<w:WordDocument>
+
  <w:View>Normal</w:View>
+
  <w:Zoom>0</w:Zoom>
+
  <w:PunctuationKerning/>
+
  <w:ValidateAgainstSchemas/>
+
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
+
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
+
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
+
  <w:Compatibility>
+
  <w:BreakWrappedTables/>
+
  <w:SnapToGridInCell/>
+
  <w:WrapTextWithPunct/>
+
  <w:UseAsianBreakRules/>
+
  <w:DontGrowAutofit/>
+
  <w:UseFELayout/>
+
  </w:Compatibility>
+
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
+
</w:WordDocument>
+
</xml><![endif]--><!--[if gte mso 9]><xml>
+
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
+
</w:LatentStyles>
+
</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]>
+
<style>
+
/* Style Definitions */
+
table.MsoNormalTable
+
{mso-style-name:"Table Normal";
+
mso-tstyle-rowband-size:0;
+
mso-tstyle-colband-size:0;
+
mso-style-noshow:yes;
+
mso-style-parent:"";
+
mso-padding-alt:0in 5.4pt 0in 5.4pt;
+
mso-para-margin:0in;
+
mso-para-margin-bottom:.0001pt;
+
mso-pagination:widow-orphan;
+
font-size:10.0pt;
+
font-family:"Times New Roman";
+
mso-fareast-font-family:"Times New Roman";
+
mso-ansi-language:#0400;
+
mso-fareast-language:#0400;
+
mso-bidi-language:#0400;}
+
</style>
+
<![endif]--><!--[if gte mso 9]><xml>
+
<o:shapedefaults v:ext="edit" spidmax="1028"/>
+
</xml><![endif]--><!--[if gte mso 9]><xml>
+
<o:shapelayout v:ext="edit">
+
  <o:idmap v:ext="edit" data="1"/>
+
</o:shapelayout></xml><![endif]--> '''<u>Step 1 – Set up Vera&lt;o:p&gt;&lt;/o:p&gt;</u>'''  
+
  
 
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with.  
 
Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with.  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
<br>
  
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.&lt;o:p&gt;&lt;/o:p&gt;</u>'''  
+
'''<u>Step 2 – Turn Gateway into secondary controller and link to Vera.</u>'''  
  
 
Make sure you’re logged in to Vera.  
 
Make sure you’re logged in to Vera.  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
<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.  
 
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.  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
<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;
 
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;
 
</span>Added Node n”  
 
</span>Added Node n”  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
<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;
 
For some reason, it appears that you need to perform this step 2 a second time for it to work properly.<span style="">&nbsp;
 
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again.  
 
</span>The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again.  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
<br>
  
 
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;
 
<!--[if gte vml 1]><v:oval id="_x0000_s1027" style='position:absolute;
Line 169: Line 73:
 
   o:title=""/>
 
   o:title=""/>
 
  <w:wrap type="tight"/>
 
  <w:wrap type="tight"/>
</v:shape><![endif]--><!--[if !vml]--><!--[endif]-->The Gateway is now configured as a secondary controller.  
+
</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.  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
[[Image:Co2a.jpg]] '''<u></u>'''
 
+
<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.
+
 
+
[[Image:Co2a.jpg]]  
+
  
 
<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>
+
'''<u></u>'''  
<w:WordDocument>
+
  <w:View>Normal</w:View>
+
  <w:Zoom>0</w:Zoom>
+
  <w:PunctuationKerning/>
+
  <w:ValidateAgainstSchemas/>
+
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
+
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
+
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
+
  <w:Compatibility>
+
  <w:BreakWrappedTables/>
+
  <w:SnapToGridInCell/>
+
  <w:WrapTextWithPunct/>
+
  <w:UseAsianBreakRules/>
+
  <w:DontGrowAutofit/>
+
  <w:UseFELayout/>
+
  </w:Compatibility>
+
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
+
</w:WordDocument>
+
</xml><![endif]--><!--[if gte mso 9]><xml>
+
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
+
</w:LatentStyles>
+
</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]>
+
<style>
+
/* Style Definitions */
+
table.MsoNormalTable
+
{mso-style-name:"Table Normal";
+
mso-tstyle-rowband-size:0;
+
mso-tstyle-colband-size:0;
+
mso-style-noshow:yes;
+
mso-style-parent:"";
+
mso-padding-alt:0in 5.4pt 0in 5.4pt;
+
mso-para-margin:0in;
+
mso-para-margin-bottom:.0001pt;
+
mso-pagination:widow-orphan;
+
font-size:10.0pt;
+
font-family:"Times New Roman";
+
mso-fareast-font-family:"Times New Roman";
+
mso-ansi-language:#0400;
+
mso-fareast-language:#0400;
+
mso-bidi-language:#0400;}
+
</style>
+
<![endif]--> '''<u>Step 3 – Assign Gateway scene buttons to Vera scenes.&lt;o:p&gt;&lt;/o:p&gt;</u>'''  
+
  
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>
+
'''<u></u>'''  
  
&lt;span style="" /&gt;  
+
'''<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>
  
 
<span style="">[[Image:Co3a.jpg]]</span>  
 
<span style="">[[Image:Co3a.jpg]]</span>  
Line 231: Line 91:
 
<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>
+
'''<u>Step 4 – Test.</u>'''  
<w:WordDocument>
+
  <w:View>Normal</w:View>
+
  <w:Zoom>0</w:Zoom>
+
  <w:PunctuationKerning/>
+
  <w:ValidateAgainstSchemas/>
+
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
+
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
+
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
+
  <w:Compatibility>
+
  <w:BreakWrappedTables/>
+
  <w:SnapToGridInCell/>
+
  <w:WrapTextWithPunct/>
+
  <w:UseAsianBreakRules/>
+
  <w:DontGrowAutofit/>
+
  <w:UseFELayout/>
+
  </w:Compatibility>
+
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
+
</w:WordDocument>
+
</xml><![endif]--><!--[if gte mso 9]><xml>
+
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
+
</w:LatentStyles>
+
</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]>
+
<style>
+
/* Style Definitions */
+
table.MsoNormalTable
+
{mso-style-name:"Table Normal";
+
mso-tstyle-rowband-size:0;
+
mso-tstyle-colband-size:0;
+
mso-style-noshow:yes;
+
mso-style-parent:"";
+
mso-padding-alt:0in 5.4pt 0in 5.4pt;
+
mso-para-margin:0in;
+
mso-para-margin-bottom:.0001pt;
+
mso-pagination:widow-orphan;
+
font-size:10.0pt;
+
font-family:"Times New Roman";
+
mso-fareast-font-family:"Times New Roman";
+
mso-ansi-language:#0400;
+
mso-fareast-language:#0400;
+
mso-bidi-language:#0400;}
+
</style>
+
<![endif]--> '''<u>Step 4 – Test.&lt;o:p&gt;&lt;/o:p&gt;</u>'''  
+
  
 
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>  
 
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>  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
<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.  
+
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'''.  
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
<br>
  
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
+
'''<u>Optional – Step 5 – Connect to HomeLink.</u>'''  
 
+
'''<u>Optional – Step 5 – Connect to HomeLink&lt;o:p&gt;&lt;/o:p&gt;</u>'''  
+
  
 
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;
 
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;
</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.
+
</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.
 +
 
 +
 
 +
(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)

Latest revision as of 21:33, 17 April 2010

[edit] How to Configure Vera with Wayne-Dalton WDHA-12 Gateway

(written Jan-2010 based on Vera firmware 1.0.979)


The Wayne-Dalton WDHA-12 Gateway funnels commands from HomeLink devices and WD keychain remote controls into Vera.  Neither can speak directly to Vera (even though the WD keychain device is a Z-wave device of a sort).


The Gateway is configured as a secondary Z-wave controller which means that its only role is to forward commands to Vera.  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.  The Gateway has 3 scene buttons and each can be attached to a different scene in Vera.


Co1b.jpg


Step 1 – Set up Vera.

Make sure you already have Vera working with at least one scene so that you have one less variable to be concerned with.


Step 2 – Turn Gateway into secondary controller and link to Vera.

Make sure you’re logged in to Vera.


On the Gateway, press copy button AND THEN 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).  Hold both buttons until all three LEDs light up and then release both.


Immediately after above, go to Vera Dashboard, click Setup, then click Devices and then click Z-Wave.  Now click “Add Z-Wave controller”.  Within 60 seconds you will see “device detected.  Added Node n”


For some reason, it appears that you need to perform this step 2 a second time for it to work properly.  The second time you do this, Vera will recognize that the device has previously been detected and will display the node number again.


The Gateway is now configured as a secondary controller.  Note: In the Devices list, Vera will show the “red gear” status (as below) indicating that the device is not properly configured.  This does not seem to matter.

Co2a.jpg


Step 3 – Assign Gateway scene buttons to Vera scenes.
Click Scenes.  Click Add scene.  Then click Add event, select your scene controller in the Devices popup and then select Event type “A scene is activated”.  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.  Finally, choose among the commands available for your device. 


Co3a.jpg


Step 4 – Test.

On the Gateway, press the scene number/button that you assigned in Step 3 and confirm that the proper commands are executed. 


As a double check, you can look at Vera’s logs.  Click Advanced, then click Logs and then Show Z-Wave jobs.


Optional – Step 5 – Connect to HomeLink.

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.  One thing to know that the Gateway manual doesn’t tell you:  To “pair” (the HomeLink term is “teach”) the HomeLink controller with the Gateway, the Gateway must be unplugged from the AC.  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.  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.


(if the directions in the WDHA-12 manual for pairing your car don't work- try 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)

Personal tools