HassIO has a hardware tab in the main supervisor it’ll tell you if it sees it.
I forget exactly but, it is something with holding the button on the stick for some time to reset etc., lookup on aeotec website support.
try:
$> lsusb
You should see something like this:
Bus 00? Device 00?: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Of course, your “Bus” and “Device” numbers could be different (hence the “?”).
@firstof9, I clicked the Hardware button and this is what was displayed:
* serial:
* /dev/ttyAMA0
* /dev/ttyACM0
* input:
* disk:
* gpio:
* gpiochip0
* gpiochip128
* audio:
* 0:
* name: bcm2835_alsa - bcm2835 ALSA
* type: ALSA
* devices:
* [object Object]
* [object Object]
I don’t see anything that looks like a z-wave device, but am not sure what I am looking for.
@Joedoe, when I type lsusb, I get
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:2514
Bus 001 Device 002: ID 0424:2514
Bus 001 Device 005: ID 0424:7800
Bus 001 Device 004: ID 0658:0200
I don’t see any mention of the aeotec.
I don’t have experience with Rasberry Pi but and thought general linux commands might give same output… apparently not. So, I think this thread might help you: Persistant USB names
Try to go through it and run the commands listed to compare output.
Thanks for the link @Joedoe. Unfortunately these instructions seem to be beyond my limited linux skills. While I have ssh set up to the Raspberry Pi it’s apparently not the right kind of ssh and the commands don’t work for me.
Did you read this reply?: Persistant USB names
Don’t worry about the “persistent” name part. First make sure your HAS configuration has the right USB port. For that, you need to find the Z-wave stick and confirm its port. I hope that makes sense.
I really appreciate your efforts to help me. Further down in that thread there is this comment:
“You have to ssh to the hassio host OS, not the ssh addon. Refer to https://home-assistant.io/developers/hassio/debugging/ for instructions.”
I tried following those directions for setting up ssh to the host, but its a bit much for me with the public and private keys and all that.
Do you know if there is any simpler way to determine which port the z-wave controller is plugged into?
How did you run the commands I suggested before? I am assuming it is through terminal. If so, you already have access you need.
If not, Is it through Home Assistant? I really don’t know if that option is available on Raspberry Pi version of HASS…
Something to try: Unplug the zwave stick and run the commands you found so far. Plug it back in and run them again and notice any differences. That might help you narrow things down.
Some suggested reading: Raspberry Pi - USB
Video: Check the Vendor ID and Product ID of attached USB devices - Raspberry Pi
It would help you better if you get acquainted with hardware you are working with.
Google – The question you are asking is probably asked many times on different forums.
Not having any Raspberry Pi experience, it is very difficult for me to help you better other than keep pointing to sources online.
I used the HassIO add-in store to install the ssh add in. Then, through the terminal, I ssh into the Raspberry. For some reason, this form of ssh provides very limited access to the Pi. To get fuller access, I need to set up that other ssh, described here: https://developers.home-assistant.io/docs/en/hassio_debugging.html
I am wondering if I might be better off Hassbian rather than Hass.io. As I understand it, hass.io shields the user from the operating system, preventing easy access to many things. Whereas with hassbian, I think there is full access to all the linux stuff.
IMHO, hardware based solution (i.e. Raspberry Pi etc.) is great but it will start to show limitations (i.e. CPU power etc.,) when you start stacking other things on like Node-Red, Mqtt, Grafana and other packages, camera streaming and so forth.
Again, this is an opinion I have after reading posts of some users switching out of RPi.
which-home-assistant-install-is-right
If your setup is small and not so demanding, it might be easy to get started but, if you search a bit, you’ll find some docker examples of Home Assistant with complete stack of above mentioned software and it is super easy to get started, and update etc. I have very few devices now but, in future, that might change and adding in automations etc., I suspect RPi won’t be able to handle. So, I never bothered to begin with.
Having said that (without actual experience of RPi), I am pretty sure there are many (if not, the majority) very happy members here running it on RPi. So, its your call. 
FYI, literally just now, I learned the difference between Hassbian and HASSIO. 
I run HASS in Docker on a dedicated Linux instance.
Did you ever get this to work in hassio?
Currently I am plugging the Aeotec in to a USB 2.0 hub, it is recognized and found in ssh on - /dev/ttyAMA0.
However I get the same logfile as the one you posted in the beginning of this thread.
You’ll need to provide more info for proper assistance.
Are you running HassOS?
or
Are you running HassIO in Docker on Deb/Cent/etc?
Apologies!
I’m running Hassio on a raspberry pi 4.
Using HassOS or Raspbian?
Apparently, there is an issue with the Aeotec stick and the Pi4.
Hi Everyone,
Got it to work… I used a USB 3.0 hub to connect with the USB 3.0 port on the Raspberry pi4.
Then I added the integration through the config file in Configuration.yaml rather then via the integration menu.
I used this hub; Sabrent 4-Port USB 3.0 Hub with Individual LED Power Switches (HB-UM43) bought through Amazon:
I’m having a similar issue trying to add nodes. My sd card crapped the bed, I replaced it and restored a backup. They z wave network works fine but unable to add new nodes. I get a similar message saying the command failed. Using the aeotek gen 5 stick as well. Any ideas?
OS?
Pi4 or Pi3 or Other?
Paste the first 10 lines of your OZW_Log.txt.
HASSIO 0.104.3
Pi3
2020-01-21 21:06:23.972 Always, OpenZwave Version 1.4.3452 Starting Up
2020-01-21 21:06:35.619 Info, Setting Up Provided Network Key for Secure Communications
2020-01-21 21:06:35.620 Info, mgr, Added driver for controller /dev/ttyACM0
2020-01-21 21:06:35.620 Info, Opening controller /dev/ttyACM0
2020-01-21 21:06:35.620 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
2020-01-21 21:06:35.621 Info, Serial port /dev/ttyACM0 opened (attempt 1)
2020-01-21 21:06:35.622 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-01-21 21:06:35.622 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-01-21 21:06:35.622 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-01-21 21:06:35.622 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
and here’s the log from where it fails to include a node:
2020-01-21 21:44:08.576 Detail, Notification: ControllerCommand - Starting
2020-01-21 21:44:08.577 Detail,
2020-01-21 21:44:08.577 Info, contrlr, Sending (Command) message (Callback ID=0xa9, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0xa9, 0xd8
2020-01-21 21:44:08.629 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0xa9, 0x07, 0x00, 0x00, 0x1c
2020-01-21 21:44:08.630 Detail,
2020-01-21 21:44:08.630 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-01-21 21:44:08.630 Info, contrlr, ADD_NODE_STATUS_FAILED
2020-01-21 21:44:08.630 Detail, contrlr, Removing current message
2020-01-21 21:44:08.630 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-01-21 21:44:08.630 Detail, Notification: ControllerCommand - Failed
2020-01-21 21:44:08.631 Detail,
2020-01-21 21:44:08.631 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-01-21 21:44:08.683 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0xa9, 0x06, 0x00, 0x00, 0x1d
2020-01-21 21:44:08.684 Detail,
2020-01-21 21:44:08.684 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-01-21 21:44:08.684 Detail, Node006, Expected reply was received
2020-01-21 21:44:08.684 Detail, Node006, Message transaction complete
2020-01-21 21:44:08.684 Detail,
2020-01-21 21:44:08.684 Detail, contrlr, Removing current message
2020-01-21 21:44:08.684 Detail, Notification: ControllerCommand - Completed