Vision Z-Wave Gen.5 only supported in v1.6 OZW (sort of solved) Topic is solved

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
myaccount
Posts: 6
Joined: Sun Dec 22, 2019 9:01 pm

Vision Z-Wave Gen.5 only supported in v1.6 OZW (sort of solved)

Post by myaccount »

Edit; Title was: "Think, just maybe, I got a Home Assistant permission problem."

Trying to get a Vision Z-Wave Gen.5 going with Home Assistant.

Code: Select all

Bus 001 Device 048: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB

Code: Select all

[ 3576.052727] usb 1-1.4: new full-speed USB device number 46 using dwc_otg
[ 3576.132726] usb 1-1.4: device descriptor read/64, error -32
[ 3576.322740] usb 1-1.4: device descriptor read/64, error -32
[ 3576.512732] usb 1-1.4: new full-speed USB device number 47 using dwc_otg
[ 3576.592776] usb 1-1.4: device descriptor read/64, error -32
[ 3576.782730] usb 1-1.4: device descriptor read/64, error -32
[ 3576.893143] usb 1-1-port4: attempt power cycle
[ 3577.712716] usb 1-1.4: new full-speed USB device number 48 using dwc_otg
[ 3577.735317] cdc_acm 1-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 3577.738408] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device

Code: Select all

ls -al /dev/serial/by-id/usb-0658_0200-if00
lrwxrwxrwx 1 root root 13 Aug  4 18:58 /dev/serial/by-id/usb-0658_0200-if00 -> ../../ttyACM0

Code: Select all

ls -al /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 Aug  4 18:58 /dev/ttyACM0

Code: Select all

id homeassistant
uid=997(homeassistant) gid=997(homeassistant) groups=997(homeassistant),10(uucp),20(dialout)
Yes, I added myself to uucp in desperation, since there was a post were it was the solution.

It complains about my config no matter.

sudo nano /mnt/dietpi_userdata/homeassistant/configuration.yaml

Code: Select all

#frontend:
# themes: !include darktheme.yaml
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
rfxtrx:
  device: /dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_DO3RWCBN-if00-port0
#  device: /dev/ttyUSB0

switch:
  platform: rfxtrx
  automatic_add: True

zwave:
#  usb_path: /dev/ttyACM0
  usb_path: /dev/serial/by-id/usb-0658_0200-if00
  config_path: /mnt/dietpi_userdata/homeassistant/deps/lib/python3.8/site-packages/python_openzwave/ozw_config
#aeotec/zw090.xml
  network_key: 0x11, 0x13, 0x1C, 0x75, 0x30, 0x1C, 0x81, 0x61, 0x1D, 0x7E, 0x15, 0xD4, 0x15, 0x1A, 0x11, 0x11
  debug: true
And the config.xml is in this dir: /mnt/dietpi_userdata/homeassistant/deps/lib/python3.8/site-packages/python_openzwave/ozw_config

At first I thought it was a power problem and hooked up a 2.0 usb 2A hub, then well, I hooked up a 3.0 hub 2A with 1,5A on some ports. But, alas no.

Thoughts?
Thanks in advance, been at this since 09:00, I'm "blind" by now.
Last edited by myaccount on Wed Aug 05, 2020 4:27 pm, edited 2 times in total.
myaccount
Posts: 6
Joined: Sun Dec 22, 2019 9:01 pm

Re: Think, just maybe, I got a Home Assistant permission problem.

Post by myaccount »

Nope, problem is that zu1401jp.xml support is in openzwave v.1.6, not v.1.4 that's in homeassistant.

Search words: zu1401 zu1401-5 (windows drivers) as I suppose this forum is indexed by all watching google.

So, will mark title as solved soon I hope with: Utilize OpenZWave’s ozwdaemon in home assistant.

There is the "maybe problem" of the kernel reporting it as a:

Code: Select all

Bus 001 Device 048: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Post Reply