Site updated at 2018-02-09 20:35:40 UTC
This commit is contained in:
parent
2880a479a3
commit
e86103a2fa
27 changed files with 85 additions and 77 deletions
|
@ -218,7 +218,7 @@ The device type is <code class="highlighter-rouge">c</code> (character special)
|
|||
<h3><a class="title-link" name="network-key" href="#network-key"></a> Network Key</h3>
|
||||
<p>Security Z-Wave devices require a network key before being added to the network using the Add Secure Node button in the Z-Wave Network Management card. You must set the <em>network_key</em> configuration variable to use a network key before adding these devices.</p>
|
||||
<p>An easy script to generate a random key:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>cat /dev/urandom | tr -dc <span class="s1">'0-9A-F'</span> | fold -w 32 | head -n 1 | sed -e <span class="s1">'s/\(..\)/0x\1, /g'</span> -e <span class="s1">'s/, $//'</span>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>cat /dev/urandom | tr -dc <span class="s1">'0-9A-F'</span> | fold -w 32 | head -n 1 | sed -e <span class="s1">'s/\(..\)/0x\1, /g'</span> -e <span class="s1">'s/, $//'</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry for network_key</span>
|
||||
|
@ -233,7 +233,7 @@ The device type is <code class="highlighter-rouge">c</code> (character special)
|
|||
<h2><a class="title-link" name="troubleshooting" href="#troubleshooting"></a> Troubleshooting</h2>
|
||||
<h3><a class="title-link" name="component-could-not-be-set-up" href="#component-could-not-be-set-up"></a> Component could not be set up</h3>
|
||||
<p>Sometimes the device may not be accessible and you’ll get an error message upon startup about not being able to set up Z-Wave. Run the following command for your device path:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>ls -l /dev/ttyAMA0
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>ls -l /dev/ttyAMA0
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>You should then see something like this:</p>
|
||||
|
@ -241,13 +241,13 @@ The device type is <code class="highlighter-rouge">c</code> (character special)
|
|||
</code></pre>
|
||||
</div>
|
||||
<p>The important pieces are the first piece <code class="highlighter-rouge">crw-rw----</code> and the group <code class="highlighter-rouge">dialout</code>. If those are different then, for your device path, run:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>sudo chgrp dialout /dev/ttyAMA0
|
||||
sudo chmod g+rw /dev/ttyAMA0
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo chgrp dialout /dev/ttyAMA0
|
||||
<span class="gp">$ </span>sudo chmod g+rw /dev/ttyAMA0
|
||||
</code></pre>
|
||||
</div>
|
||||
<h3><a class="title-link" name="device-path-changes" href="#device-path-changes"></a> Device path changes</h3>
|
||||
<p>If your device path changes when you restart, see <a href="http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/">this guide</a> on fixing it.</p>
|
||||
<h3><a class="title-link" name="unable-to-install-python_openzwave" href="#unable-to-install-python_openzwave"></a> Unable to install python_openzwave</h3>
|
||||
<h3><a class="title-link" name="unable-to-install-python-openzwave" href="#unable-to-install-python-openzwave"></a> Unable to install Python Openzwave</h3>
|
||||
<p>If you’re getting errors like:</p>
|
||||
<div class="highlighter-rouge"><pre class="highlight"><code>openzwave-embed/open-zwave-master/libopenzwave.a: No such file or directory
|
||||
</code></pre>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue