SOLVED: Can't get Aoetec Z-Stick to work with HassOS

ryanjg117 · October 7, 2019, 10:42pm

Howdy, I’m a Newbie McNoobsler when it comes to Hassbian and Raspberry PI in general, so my apologies up front. I’m trying to setup my Raspberry PI3 as a home automation hub with an Aeotec Z-Stick Gen5. I have successfully installed the OS, setup wi-fi, and can login and configure Home Assistant through the web interface. No problems there.

I’ve enabled z-wave through the additional code in the configuration.yaml file as follows:

zwave:
  usb_path: /dev/ttyACM0

My Z-Stick does appear on the dashboard, but I can’t seem to actually add any z-wave devices. I’m fiddling with a First Alert smoke/carbon detector and am unable to get the Z-Stick to detect it, and I’m following the First Alert z-wave pairing instructions. I never get a rapid flash out of my Z-Stick, indicating a successful pairing.

In the Z-Wave area of the Configuration section, slicking “Add Node” appears to do nothing. The LEDs on the Z-Stick don’t change to blinking blue (it just keeps cycling the disco lights). Removing the z-stick and clicking Add Node or Add Node Secure also appears to do nothing. There are no flashing lights to indicate it has gone into Inclusion mode.

Attempting to use the Z-Stick remotely, by clicking the action button, never results in any devices being successfully paired either. I have brought the z-stick back to the hub, reset it, and nothing changes.

I’ve checked the log and there doesn’t appear to be any errors, so not really sure what the issue might be?

pocket · October 8, 2019, 12:48am

I use Hass.IO instead of Hasbian, so some of the following may not apply.

Did you check the OZW_Log.txt log? Do you see any errors? Do you see any entities for the First Alert device under Developer Tools > States?

Under Configuration>Devices, do you see AEON Labs ZW090 Z-Stick Gen5 US? If you click on it, and click again on the Z-Wave icon, you should see the status card for the device. Toward the top of the card, it should say ready.

Do you have access to your system command line (e.g. via SSH)? Try to turn the blinking LED on and off using the following commands:

echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00

echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00

Here are a couple links from Aeotec:

https://aeotec.freshdesk.com/support/solutions/folders/6000146720

https://aeotec.freshdesk.com/support/solutions/articles/6000096809-cannot-add-include-a-device-to-z-stick-gen5-troubleshooting-

I hope this helps.

firstof9 · October 8, 2019, 1:23am

This is normal they don’t change when plugged into a computer.

Expected result as you removed the stick from the computer.

This is not recommended for inclusion of devices into the zwave network.

Does the zwave control panel show up for you under Configuration ?

What does the output of lsusb and ls -al /dev/tty* show?

What does the home-assistant.log show? (Example: cat /home/homeassistant/.homeassistant/home-assistant.log | grep zwave)

ryanjg117 · October 8, 2019, 3:59am

Rob, thanks for the tips. To answer your questions:

I haven’t seen the OZW_Log.txt, but is that the same log I can generate on the Z-Wave configuration page? If so, I don’t see any errors. Here’s a snippet of the last few entries (I clicked Add Node and Cancel Command.

2019-10-07 20:55:15.971 Detail, Queuing (Controller) Add Device
2019-10-07 20:55:15.971 Info, Add Device
2019-10-07 20:55:15.971 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
2019-10-07 20:55:15.972 Detail, Notification: ControllerCommand - Starting
2019-10-07 20:55:15.973 Detail,
2019-10-07 20:55:15.973 Info, contrlr, Sending (Command) message (Callback ID=0x0a, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
2019-10-07 20:55:15.976 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x01, 0x00, 0x00, 0xb9
2019-10-07 20:55:15.977 Detail,
2019-10-07 20:55:15.977 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-10-07 20:55:15.977 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2019-10-07 20:55:15.977 Detail, Node001,   Expected callbackId was received
2019-10-07 20:55:15.977 Detail, Node001,   Expected reply was received
2019-10-07 20:55:15.977 Detail, Node001,   Message transaction complete
2019-10-07 20:55:15.977 Detail,
2019-10-07 20:55:15.977 Detail, contrlr, Removing current message
2019-10-07 20:55:15.977 Detail, Notification: ControllerCommand - Waiting
2019-10-07 20:55:15.980 Info, WriteNextMsg Controller nothing to do
2019-10-07 20:55:19.627 Info, Cancel Add Node
2019-10-07 20:55:19.627 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2019-10-07 20:55:19.627 Detail, Notification: ControllerCommand - Canceled
2019-10-07 20:55:19.628 Detail,
2019-10-07 20:55:19.628 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2019-10-07 20:55:19.717 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x06, 0x00, 0x00, 0xbe
2019-10-07 20:55:19.717 Detail,
2019-10-07 20:55:19.717 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-10-07 20:55:19.717 Info, contrlr, ADD_NODE_STATUS_DONE
2019-10-07 20:55:19.717 Detail, Node006,   Expected reply was received
2019-10-07 20:55:19.718 Detail, Node006,   Message transaction complete

Under Configuration > Devices, I do see the Z-Stick. I can open its properties and I see it is READY.

I installed Putty and setup an SSH Server. I was able to enter the commands you provided and the second one deactivated the disco lights, which is great since I sleep in this same room.

ryanjg117 · October 8, 2019, 4:14am

You mentioned that remotely pressing the action button is not recommended for inclusion, so what is best practice if I’m trying to add an already-installed switch in the house and cannot physically take the Raspberry Pi3 to the switch?

When I enter “lsusb” I get:

Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 002: ID 0424:9514
Bus 001 Device 004: ID 0658:0200

And here’s what I get with -al /dev/tty*:

crw-rw-rw-    1 root     root        5,   0 Oct  7 20:50 /dev/tty
crw-rw----    1 root     audio     166,   0 Oct  7 20:50 /dev/ttyACM0
crw-rw----    1 root     audio     204,  64 Oct  7 20:50 /dev/ttyAMA0

ryanjg117 · October 8, 2019, 4:16am

And just one point of clarification (if it matters), I am actually running Hassio, not Habsian as I incorrectly stated earlier. Noob, as I said.

sparkydave · October 8, 2019, 4:22am

Although possibly not recommended as mentioned by firstof9, I have successfully taken my z-stick out and used the ‘standard’ Aeotec pairing method for many devices. Once you plug it back into your HA server you need to do a reboot and then the new devices should come up in the z-wave config panel

pocket · October 8, 2019, 4:57am

It looks like you have a connected device – Node006. Have you looked at Developer Tools > States to see if there’s a entity for your First Alert device? As a Z-wave device, it’s probably at the end of the list. If it’s there, go to Configuration > Entity Registry to see what data are available from it. After that, you’ll need to make some entries into your configuration files so you can display, record, and plot the history of the data. For a CO/smoke detector, perhaps a entity badge to display status is all you’ll need.

https://www.home-assistant.io/docs/z-wave/entities/#alarm

BTW, have you started looking at the Lovelace user interface yet?

https://www.home-assistant.io/lovelace/

firstof9 · October 8, 2019, 11:36am

Take your phone to the switch you are attempting to include. Access your Home Assistant web page via your phone, tap Configuration -> Zwave -> Add (Secure) Node, then press the button(s) needed on said switch to included it to your network per the device’s manual.

Note secure is only needed on devices that require it and isn’t really recommended for devices such as switches, you’d use this for things like door locks and garage door openers.

Sometimes on occasion after including a node it doesn’t show up, in those cases restart Home Assistant and it’ll show up once everything loads up.

ryanjg117 · October 9, 2019, 12:40am

Got it solved. It actually wasn’t a problem with the Z-Stick, but the sloppy instructions included with the First Alert device. It mentioned opening and closing the battery tray while holding the test button, but they failed to mention that you have to hold the test button for a couple of seconds after closing the battery tray.

Now that I have this device added, what cool things can I do with it? Setup an alert to notify me when it has triggered or is low battery?

firstof9 · October 9, 2019, 12:58am

Depending on the sensors exposed you can have it notify you when any attribute changes really.