16:39:24.009 Info, Serial port /dev/ttyAMA0 opened (attempt 1) 16:39:24.009 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1) 16:39:24.009 Info, Opening controller /dev/ttyAMA0 16:39:24.008 Info, mgr, Added driver for controller /dev/ttyAMA0 16:39:24.008 Warning, Failed - Network Key Not Set 16:39:24.008 Info, Setting Up Provided Network Key for Secure Communications 16:39:21.291 Always, OpenZwave Version Starting Up
![lsusb details lsusb details](https://cdn.shopify.com/s/files/1/2578/8918/products/BKTNFPLSUSBRV_g3_2048x.jpg)
If I look a the logs under Configuration | Z-Wave | Logs I see: While I see it listed in the Hass.io | System | Hardware:Īnd I see it listed if (from the Linux CLI) I type: lsusb Saved and rebooted and can see the Z-Wave option under Configuration.Įverything appears fine until I get to the Z-Wave setup and it doesn’t look like the OS is recognizing the Aeotec fully. Modded the configuration.yaml file to include (after making sure the device was correct per the Hass.io | System | Hardware values): Set up the basics (Configuration and SSH add-ins) and plugged in the Aeotec.
![lsusb details lsusb details](https://linuxhint.com/wp-content/uploads/2018/04/u7.png)
Nothing plugged into the Raspberry Pi 3b except network, power.
#LSUSB DETAILS INSTALL#
Started a clean install of Hassio 1.11 RPi3b 32-bit image on a fresh SD card (and actually have wiped/retried this x2 then again w./ another card just in case).
![lsusb details lsusb details](https://i2.wp.com/img-blog.csdnimg.cn/20200413171636672.png)
I had monkeyed around with (just syncing some things manually) but then did a factory reset of my Aeotec USB Z-Stick Gen5 to factory defaults.