From 2720713e9ee162f9bbed771cf935f7693d941490 Mon Sep 17 00:00:00 2001 From: mastakebob <47671816+mastakebob@users.noreply.github.com> Date: Tue, 26 Mar 2019 18:34:48 -0400 Subject: [PATCH] Update device-specific.markdown (#9042) Updates include an alternate way of turning off the aeotec z wave 'disco lights' that is known to work on the latest Hass.io and Pi configuration (using ttyACM0 instead of the the by serial id method). Also provides additional guidance on how to properly insert the aeotec nanomote xml code into the zwcfg*.xml file. --- source/_docs/z-wave/device-specific.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown index 1ebb5083945..288eb1d57e0 100644 --- a/source/_docs/z-wave/device-specific.markdown +++ b/source/_docs/z-wave/device-specific.markdown @@ -45,6 +45,8 @@ Turn on "Disco lights": $ echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00 ``` +If the above two commands give errors about not having that device, you should try replacing the `/dev/serial/by-id/usb-0658_0200-if00` with `/dev/ttyACM0` or `/dev/ttyACM1` (depending on which tty your aeotec stick is addressed to). + ### {% linkable_title Razberry Board %} You need to disable the on-board Bluetooth since the board requires the use of the hardware UART (and there's only one on the Pi3). You do this by adding the following to the end of `/boot/config.txt`: @@ -298,6 +300,8 @@ Press circle and plus simultaneously to wake up the device. +Once you've added the NanoMote to your z-wave network, you'll need to update your zwcfg*.xml file with the below xml data. Stop Home Assistant and open your zwcfg*.xml file (located in your config folder). Find the NanoMote device section and then its corresponding `CommandClass` section with id="91". Replace the entire CommandClass section with the below xml data. Save the file and restart Home Assistant. + ```xml