HomeAssistant Docker and Aeotech ZWave

jmcgee · December 20, 2018, 11:41pm

I got tired of corrupted cards on my RPI so I installed Docker CE on Ubuntu 18.04 machine. It’s running mythtv backend so on all the time anyway.
I installed HomeAssistant in Docker:

docker run -d --name=“home-assistant” -v /home/mythuser/homeassistant:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant

I can’t get it to recognize the Zwave USB stick that was working on RPI.
I have tried /dev/ttyUSB0

dmesg | grep USB
[ 1311.545205] usb 3-10: Product: CP2102 USB to UART Bridge Controller
[ 1311.548216] usb 3-10: cp210x converter now attached to ttyUSB0
[ 1328.604768] usb 3-4: USB disconnect, device number 2
[ 1333.551824] usb 3-4: new full-speed USB device number 11 using xhci_hcd
[ 1333.701176] usb 3-4: New USB device found, idVendor=0764, idProduct=0501
[ 1333.701181] usb 3-4: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 1333.704370] hid-generic 0003:0764:0501.0006: hiddev0,hidraw1: USB HID v1.10 Device [CPS CP1500PFCLCD] on usb-0000:00:14.0-4/input0
[104602.479669] usb 3-10: USB disconnect, device number 10
[104602.480010] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[104606.542233] usb 3-10: new full-speed USB device number 12 using xhci_hcd
[104606.691765] usb 3-10: New USB device found, idVendor=10c4, idProduct=ea60
[104606.691771] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[104606.691775] usb 3-10: Product: CP2102 USB to UART Bridge Controller
[104606.694849] usb 3-10: cp210x converter now attached to ttyUSB0

mythuser@amethi:~$ lsusb -v

Bus 002 Device 002: ID 8087:8000 Intel Corp.
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x8087 Intel Corp.
idProduct 0x8000
bcdDevice 0.05
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 12

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.15
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12

Bus 001 Device 002: ID 8087:8008 Intel Corp.
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x8087 Intel Corp.
idProduct 0x8008
bcdDevice 0.05
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.15
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 3
bMaxPacketSize0 9
idVendor 0x1d6b Linux Foundation
idProduct 0x0003 3.0 root hub
bcdDevice 4.15
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 31
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
bMaxBurst 0

Bus 003 Device 008: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d Logitech, Inc.
idProduct 0xc016 Optical Wheel Mouse
bcdDevice 3.40
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 52
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10

Bus 003 Device 011: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0764 Cyber Power System, Inc.
idProduct 0x0501 CP1500 AVR UPS
bcdDevice 0.01
iManufacturer 3
iProduct 1
iSerial 2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 439
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 10

Bus 003 Device 005: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x04f2 Chicony Electronics Co., Ltd
idProduct 0x0402 Genius LuxeMate i200 Keyboard
bcdDevice 1.57
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 65
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 146
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10

Bus 003 Device 012: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x10c4 Cygnal Integrated Products, Inc.
idProduct 0xea60 CP210x UART Bridge / myAVR mySmartUSB light
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 2
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.15
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12

jmcgee · December 20, 2018, 11:58pm

Also:

mythuser@amethi:~$ ls -ltr /dev/tty*|tail -n 1
crw–w---- 1 root tty 4, 7 Dec 20 17:38 /dev/tty7

And it doesn’t like /dev/tty7 either

mythuser@amethi:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 008: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 003 Device 011: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 003 Device 005: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Bus 003 Device 012: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

finity · December 21, 2018, 6:58am

the output of lsusb on my NUC with the z stick inserted is:

finity@NUC:~$ lsusb
Bus 002 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 005: ID 0451:16a8 Texas Instruments, Inc.
Bus 002 Device 004: ID 0658:0200 Sigma Designs, Inc.
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

the AEOTEC Z Stick Gen 5 is the Sigma Designs device (ID 0658:200)

I don’t see that device in your list so I don’t think the stick is working for some reason.

jmcgee · December 21, 2018, 10:59pm

I had a similiar problem with this same stick on Raspberry Pi when I got it.

Pretty sure it is the
Cygnal Integrated Products, Inc. CP210x UART Bridg

Here is

mythuser@amethi:~/homeassistant$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 008: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 003 Device 011: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 003 Device 005: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Then inserted the stick and
mythuser@amethi:~/homeassistant$ lsusb

Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 016: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 003 Device 008: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 003 Device 011: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 003 Device 005: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and dmesg with it plugged in:

[104602.480010] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[104602.480051] cp210x 3-10:1.0: device disconnected
[104606.542233] usb 3-10: new full-speed USB device number 12 using xhci_hcd
[104606.691765] usb 3-10: New USB device found, idVendor=10c4, idProduct=ea60
[104606.691771] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[104606.691775] usb 3-10: Product: CP2102 USB to UART Bridge Controller
[104606.691779] usb 3-10: Manufacturer: Silicon Labs
[104606.691783] usb 3-10: SerialNumber: 0001
[104606.692835] cp210x 3-10:1.0: cp210x converter detected
[104606.694849] usb 3-10: cp210x converter now attached to ttyUSB0
[122759.766197] perf: interrupt took too long (5003 > 5002), lowering kernel.perf_event_max_sample_rate to 39750
[173111.472150] usb 3-10: USB disconnect, device number 12
[173111.472409] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[173111.472439] cp210x 3-10:1.0: device disconnected
[173118.666571] usb 3-8: new full-speed USB device number 13 using xhci_hcd
[173118.816163] usb 3-8: New USB device found, idVendor=10c4, idProduct=ea60
[173118.816169] usb 3-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[173118.816174] usb 3-8: Product: CP2102 USB to UART Bridge Controller
[173118.816177] usb 3-8: Manufacturer: Silicon Labs
[173118.816181] usb 3-8: SerialNumber: 0001
[173118.817164] cp210x 3-8:1.0: cp210x converter detected
[173118.817293] cp210x 3-8:1.0: failed to get vendor val 0x370b size 1: -71
[173118.817302] cp210x 3-8:1.0: querying part number failed
[173118.818493] cp210x ttyUSB0: failed get req 0x4 size 2 status: 1
[173118.818532] cp210x: probe of ttyUSB0 failed with error -5
[173165.348906] usb 3-8: USB disconnect, device number 13
[173165.349080] cp210x 3-8:1.0: device disconnected
[174660.236039] ata4: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
[174660.236048] ata4: irq_stat 0x00400040, connection status changed
[174660.236056] ata4: SError: { HostInt PHYRdyChg 10B8B DevExch }
[174660.236065] ata4: hard resetting link
[174660.948001] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[174660.949685] ata4.00: configured for UDMA/133
[174660.949692] ata4: EH complete
[174664.268024] usb 3-8: new full-speed USB device number 14 using xhci_hcd
[174664.396158] usb 3-8: Device not responding to setup address.
[174664.604154] usb 3-8: Device not responding to setup address.
[174664.812027] usb 3-8: device not accepting address 14, error -71
[174664.940030] usb 3-8: new full-speed USB device number 15 using xhci_hcd
[174665.090051] usb 3-8: New USB device found, idVendor=10c4, idProduct=ea60
[174665.090057] usb 3-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[174665.090061] usb 3-8: Manufacturer: Silicon Labs
[174665.090065] usb 3-8: SerialNumber: 0001
[174665.091149] cp210x 3-8:1.0: cp210x converter detected
[174665.092832] cp210x ttyUSB0: failed set request 0x3 status: -32
[174665.092849] cp210x: probe of ttyUSB0 failed with error -32
[187429.391784] usb 3-8: USB disconnect, device number 15
[187429.391973] cp210x 3-8:1.0: device disconnected
[187440.842833] usb 3-8: new full-speed USB device number 16 using xhci_hcd
[187440.992717] usb 3-8: New USB device found, idVendor=10c4, idProduct=ea60
[187440.992723] usb 3-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[187440.992727] usb 3-8: Product: CP2102 USB to UART Bridge Controller
[187440.992731] usb 3-8: Manufacturer: Silicon Labs
[187440.992734] usb 3-8: SerialNumber: 0001
[187440.993828] cp210x 3-8:1.0: cp210x converter detected
[187440.995775] usb 3-8: cp210x converter now attached to ttyUSB0
[188362.803610] usb 3-8: USB disconnect, device number 16
[188362.803865] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[188362.803893] cp210x 3-8:1.0: device disconnected
[188396.082806] usb 3-8: new full-speed USB device number 17 using xhci_hcd
[188396.766981] usb 3-8: Device not responding to setup address.
[188396.974974] usb 3-8: Device not responding to setup address.
[188397.182809] usb 3-8: device not accepting address 17, error -71
[188397.310850] usb 3-8: new full-speed USB device number 18 using xhci_hcd
[188397.461609] usb 3-8: New USB device found, idVendor=10c4, idProduct=ea60
[188397.461615] usb 3-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[188397.461619] usb 3-8: SerialNumber: 0001
[188397.462752] cp210x 3-8:1.0: cp210x converter detected
[188397.464646] usb 3-8: cp210x converter now attached to ttyUSB0

and disconnected it:

mythuser@amethi:~/homeassistant$ dmesg | tail -20
[187440.992731] usb 3-8: Manufacturer: Silicon Labs
[187440.992734] usb 3-8: SerialNumber: 0001
[187440.993828] cp210x 3-8:1.0: cp210x converter detected
[187440.995775] usb 3-8: cp210x converter now attached to ttyUSB0
[188362.803610] usb 3-8: USB disconnect, device number 16
[188362.803865] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[188362.803893] cp210x 3-8:1.0: device disconnected
[188396.082806] usb 3-8: new full-speed USB device number 17 using xhci_hcd
[188396.766981] usb 3-8: Device not responding to setup address.
[188396.974974] usb 3-8: Device not responding to setup address.
[188397.182809] usb 3-8: device not accepting address 17, error -71
[188397.310850] usb 3-8: new full-speed USB device number 18 using xhci_hcd
[188397.461609] usb 3-8: New USB device found, idVendor=10c4, idProduct=ea60
[188397.461615] usb 3-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[188397.461619] usb 3-8: SerialNumber: 0001
[188397.462752] cp210x 3-8:1.0: cp210x converter detected
[188397.464646] usb 3-8: cp210x converter now attached to ttyUSB0
[188672.605122] usb 3-8: USB disconnect, device number 18
[188672.605437] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[188672.605486] cp210x 3-8:1.0: device disconnected

finity · December 22, 2018, 4:41am

What model of AEOTEC Stick do you have?

But back to your specific issue, try:

ls /dev/tty*

with both the stick inserted and removed to see which device is different. That will tell you the device address of the stick.

Then I recommend making the device address persistent in your install so you won’t need to deal with this again.

jmcgee · December 22, 2018, 1:59pm

I see no change. It is a GEN5 AEOTEC USB stick.

ls /dev/tty*

/dev/tty /dev/tty18 /dev/tty28 /dev/tty38 /dev/tty48 /dev/tty58 /dev/ttyS0 /dev/ttyS19 /dev/ttyS29

/dev/tty0 /dev/tty19 /dev/tty29 /dev/tty39 /dev/tty49 /dev/tty59 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3

/dev/tty1 /dev/tty2 /dev/tty3 /dev/tty4 /dev/tty5 /dev/tty6 /dev/ttyS10 /dev/ttyS20 /dev/ttyS30

/dev/tty10 /dev/tty20 /dev/tty30 /dev/tty40 /dev/tty50 /dev/tty60 /dev/ttyS11 /dev/ttyS21 /dev/ttyS31

/dev/tty11 /dev/tty21 /dev/tty31 /dev/tty41 /dev/tty51 /dev/tty61 /dev/ttyS12 /dev/ttyS22 /dev/ttyS4

/dev/tty12 /dev/tty22 /dev/tty32 /dev/tty42 /dev/tty52 /dev/tty62 /dev/ttyS13 /dev/ttyS23 /dev/ttyS5

/dev/tty13 /dev/tty23 /dev/tty33 /dev/tty43 /dev/tty53 /dev/tty63 /dev/ttyS14 /dev/ttyS24 /dev/ttyS6

/dev/tty14 /dev/tty24 /dev/tty34 /dev/tty44 /dev/tty54 /dev/tty7 /dev/ttyS15 /dev/ttyS25 /dev/ttyS7

/dev/tty15 /dev/tty25 /dev/tty35 /dev/tty45 /dev/tty55 /dev/tty8 /dev/ttyS16 /dev/ttyS26 /dev/ttyS8

/dev/tty16 /dev/tty26 /dev/tty36 /dev/tty46 /dev/tty56 /dev/tty9 /dev/ttyS17 /dev/ttyS27 /dev/ttyS9

/dev/tty17 /dev/tty27 /dev/tty37 /dev/tty47 /dev/tty57 /dev/ttyprintk /dev/ttyS18 /dev/ttyS28

mythuser@amethi:~/homeassistant$ ls /dev/tty*

/dev/tty /dev/tty18 /dev/tty28 /dev/tty38 /dev/tty48 /dev/tty58 /dev/ttyS0 /dev/ttyS19 /dev/ttyS29

/dev/tty0 /dev/tty19 /dev/tty29 /dev/tty39 /dev/tty49 /dev/tty59 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3

/dev/tty1 /dev/tty2 /dev/tty3 /dev/tty4 /dev/tty5 /dev/tty6 /dev/ttyS10 /dev/ttyS20 /dev/ttyS30

/dev/tty10 /dev/tty20 /dev/tty30 /dev/tty40 /dev/tty50 /dev/tty60 /dev/ttyS11 /dev/ttyS21 /dev/ttyS31

/dev/tty11 /dev/tty21 /dev/tty31 /dev/tty41 /dev/tty51 /dev/tty61 /dev/ttyS12 /dev/ttyS22 /dev/ttyS4

/dev/tty12 /dev/tty22 /dev/tty32 /dev/tty42 /dev/tty52 /dev/tty62 /dev/ttyS13 /dev/ttyS23 /dev/ttyS5

/dev/tty13 /dev/tty23 /dev/tty33 /dev/tty43 /dev/tty53 /dev/tty63 /dev/ttyS14 /dev/ttyS24 /dev/ttyS6

/dev/tty14 /dev/tty24 /dev/tty34 /dev/tty44 /dev/tty54 /dev/tty7 /dev/ttyS15 /dev/ttyS25 /dev/ttyS7

/dev/tty15 /dev/tty25 /dev/tty35 /dev/tty45 /dev/tty55 /dev/tty8 /dev/ttyS16 /dev/ttyS26 /dev/ttyS8

/dev/tty16 /dev/tty26 /dev/tty36 /dev/tty46 /dev/tty56 /dev/tty9 /dev/ttyS17 /dev/ttyS27 /dev/ttyS9

/dev/tty17 /dev/tty27 /dev/tty37 /dev/tty47 /dev/tty57 /dev/ttyprintk /dev/ttyS18 /dev/ttyS28

sebk-666 · December 22, 2018, 2:13pm

Something seems to be wrong with your ZStick.
I also have the ZStick Gen5 and it shows up like @finity’s:

# lsusb | grep Aeotec
Bus 003 Device 005: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB

If yours shows up as a USB to serial device, it looks like it’s in some kind of recovery mode.
If you have a Windows machine, try plugging it in there and maybe running a firmware upgrade.

Sebastian

finity · December 22, 2018, 2:28pm

I don’t see anything in that list that looks even close to what you should see.

It should be a ttyUSB0, USB1, ACM0 or ACM1 or something like that.

jmcgee · December 23, 2018, 4:03am

I agree, something happened to the stick. I saw no firmware to flash on Aeotec. Saw instructions but just had instructions to save firmware, then how to reflash it later. But no firmware on the site. Even if I had it, something is wrong with the stick anyway. I ordered another.

daphatty · December 23, 2018, 9:56pm

Have you tried resetting the stick to factory defaults?

FWIW, I just migrated my Home Assistant installation (Hassio on RPI to Home Assistant on Ubuntu Server) and my Gen 5 stick comes up as Sigma Designs.

Also, I came across this tutorial that outlines a method of checking the Aeotec Stick with a third party tool. Only limitation is that the tool is Windows only but it works really well.

jmcgee · December 24, 2018, 11:05pm

Yes, I have tried resetting it with paperclip. It will not respond to that. I did get this back from Aeotec. Not sure why I would need to to do this or how, since it working for other folks on 18.04:

CP210x is a different serial driver that is used apart from Sigma Designs driver in this case. It is likely utilizing a different driver in this case which is fine if it works.

My suggestion is to ensure that you install the CDC ACM.ko module from the kernel of Linux.

Cheers,
Chris Cheng
Field Application Engineer
Aeotec Inc.

Keeze · December 24, 2018, 11:37pm

Dump question: did you give docker acces to the right USB port?:

--device=/dev/ttyUSB0

And is the user running docker added to the group dailout?

Cheers,
Kees

jmcgee · December 27, 2018, 1:11am

Ok so I got the new Aeotec stick and it shows up in dmesg at /ttyACM0

I put that in the homeassistant running in docker and it can’t find it.
How so I know what user is running homeassistant in docker?
Is it same user that logged into machine?

finity · December 27, 2018, 2:32am

Ok now that the stick is actually being correctly recognized by the system you need to add your docker user to the dialout group and add the stick to the docker run command as suggested by @Keeze above.

The docker user is normally the user that you used to install docker.

The command to do that is:

sudo usermod -G dialout <docker user>

And you probably will want to use a different way to reference the z stick in HA to keep the USB path persistent thru reboots or you will be fighting that issue too.

ee1 · December 29, 2018, 8:58pm

You should be able to see what user docker is running as like this:

ps aux | grep docker

Mine appears to be running as root:

root       620  0.0  1.4 506408 29876 ?        Ssl  Nov07  45:40 /usr/bin/dockerd --raw-logs
root       647  0.3  1.2 236204 25936 ?        Ssl  Nov07 230:33 docker-containerd --config /var/run/docker/containerd/containerd.toml
root      1203  0.0  0.1   7508  4056 ?        Sl   Nov07   0:06 docker-containerd-shim -namespace moby -workdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/772847712e5bdd2094db77a2fe7d43d11642c74af9818394f594b3635429d06b -address /var/run/docker/containerd/docker-containerd.sock -containerd-binary /usr/bin/docker-containerd -runtime-root /var/run/docker/runtime-runc

Maybe not the best idea running as root, but works for me and it appears that because of this I don’t need to add any users to the dialout group.

as @finity said, give the stick a static name so it won’t change on reboot / replugs. Here’s how I do it:

cd /etc/udev/rules.d
sudo nano usbcustom.rules
SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="zwave"

Then as stated above by @Keeze pass that to docker. I do believe order of docker parameters mattered when I was playing with it. Here’s what I do:

sudo docker run -d --name="home-assistant" -v /home/<username removed>/hass:/config -v /etc/localtime:/etc/localtime:ro --net=host --device=/dev/zwave:/dev/zwave:rwm --restart unless-stopped homeassistant/home-assistant

Good luck, hope it helps. My examples are from Ubuntu 14. And as a side note I believe the best install of HASS is on docker on linux on a “proper” machine like youre doing. Upgrades are very easy and easy to backup and revert if necessary. No finicky rPi sdcards for me.

jmcgee · January 2, 2019, 6:37pm

ps aux | grep docker
root 3018 0.0 0.0 1234960 14720 ? Ssl 2018 8:38 /usr/bin/dockerd -H unix://
mythuser 13787 0.0 0.0 14428 976 pts/0 S+ 12:32 0:00 grep --color=auto docker
root 21085 0.0 0.0 10744 856 ? Sl 2018 1:05 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/d3c1580f1562c2222455539d6f0d05eecc72ef919ca0747f62a9711e0a1cd2d1 -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-runc

So, is mythuser or root running docker?

“mythuser@amethi:~$ members dialout
mythtv nut mythuser”

jmcgee · January 2, 2019, 6:41pm

ls /dev/tty*
/dev/tty /dev/tty16 /dev/tty24 /dev/tty32 /dev/tty40 /dev/tty49 /dev/tty57 /dev/tty8 /dev/ttyS13 /dev/ttyS21 /dev/ttyS3
/dev/tty0 /dev/tty17 /dev/tty25 /dev/tty33 /dev/tty41 /dev/tty5 /dev/tty58 /dev/tty9 /dev/ttyS14 /dev/ttyS22 /dev/ttyS30
/dev/tty1 /dev/tty18 /dev/tty26 /dev/tty34 /dev/tty42 /dev/tty50 /dev/tty59 /dev/ttyACM0 /dev/ttyS15 /dev/ttyS23 /dev/ttyS31
/dev/tty10 /dev/tty19 /dev/tty27 /dev/tty35 /dev/tty43 /dev/tty51 /dev/tty6 /dev/ttyprintk /dev/ttyS16 /dev/ttyS24 /dev/ttyS4
/dev/tty11 /dev/tty2 /dev/tty28 /dev/tty36 /dev/tty44 /dev/tty52 /dev/tty60 /dev/ttyS0 /dev/ttyS17 /dev/ttyS25 /dev/ttyS5
/dev/tty12 /dev/tty20 /dev/tty29 /dev/tty37 /dev/tty45 /dev/tty53 /dev/tty61 /dev/ttyS1 /dev/ttyS18 /dev/ttyS26 /dev/ttyS6
/dev/tty13 /dev/tty21 /dev/tty3 /dev/tty38 /dev/tty46 /dev/tty54 /dev/tty62 /dev/ttyS10 /dev/ttyS19 /dev/ttyS27 /dev/ttyS7
/dev/tty14 /dev/tty22 /dev/tty30 /dev/tty39 /dev/tty47 /dev/tty55 /dev/tty63 /dev/ttyS11 /dev/ttyS2 /dev/ttyS28 /dev/ttyS8
/dev/tty15 /dev/tty23 /dev/tty31 /dev/tty4 /dev/tty48 /dev/tty56 /dev/tty7 /dev/ttyS12 /dev/ttyS20 /dev/ttyS29 /dev/ttyS9

And I enter
/dev/ttyACM0
into the ha zwave config.
It says:
Z-Wave validation failed. Is the path to the USB stick correct?

finity · January 2, 2019, 10:15pm

Something else to try is that, since the new device registry concept has come along, you can look i the /.storage/core.config_entries to see if it lists a failed zwave stick install that’s blocking your existing good stick from being discovered correctly.

If there is a zwave entry there then I would stop HA, make a backup of the file with a different name (add .old to the end or something) then delete the original file and restart HA so it recreates a new one.

gbboy · January 2, 2019, 10:38pm

If you haven’t already, you need to recreate your docker container with the device path e.g.

docker run -itd --name=home-assistant -v /local-path-to-ha:/config -v /etc/localtime:/etc/localtime:ro --privileged --device /dev/ttyACM0 --restart=always --net=host homeassistant/home-assistant

– device /dev/ttyACM0 allows your container to see the location of the plugged in Aeotec device. If you are using docker-compose you would add the devices e.g.

devices:
  - /dev/ttyACM0:/dev/ttyACM0

Then you can either manually add zwave: and its settings to configuration.yaml or use the integration.

jmcgee · January 4, 2019, 12:13am

OK, I removed the existing home assistant container.

docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bffcad58848f portainer/portainer “/portainer” 5 hours ago Up 5 hours 0.0.0.0:9000->9000/tcp gracious_payne
mythuser@amethi:~/homeassistant$ docker run -itd --name=home-assistant -v /home/mythuser/homeassistant:/config -v /etc/localtime:/etc/localtime:ro --privileged --device /dev/ttyACM0 --restart=always --net=host homeassistant/home-assistant
191e9f173d02410c7a3461f91a708d29ee4005f385355b75cc43746a8898bfb0
mythuser@amethi:~/homeassistant$ docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
191e9f173d02 homeassistant/home-assistant “python -m homeassis…” 5 seconds ago Up 4 seconds home-assistant
bffcad58848f portainer/portainer “/portainer” 5 hours ago Up 5 hours 0.0.0.0:9000->9000/tcp gracious_payne

But now it does not respond to a web page:
http://192.168.1.105:8123/