Looks similar to what I have except I haven’t pinned the usb path yet. I have a hunch that is what is wrong. I need to double check what it is connected to.
I’ve confirmed: /dev/ttyACM0 is the path by running: ll /dev/tty*
with it plugged in and removed. I will pin it with udev once I get it working the first time.
Find the configuration folder (contains options.xml) in my case it was: /srv/homeassistant/lib/python3.5/site-packages/python_openzwave/ozw_config It will change depending on python version
Plug the stick in
Find out what the device is run ls -al /dev/tty* run this and take note of any that show ttyUSB#, ttyACM# or ttyAMA#.
Unplug the stick and run the command again taking note of the one that disappeard
here is my way of enabling Aeotec Z-Stick Gen5 for centos 7 with installed Anaconda3. I use “ana” user.
Probably could be done in more elegant way but this worked for me.
Martin
add user ana and make him sudoer
sudo useradd ana
sudo passwd ana
sudo usermod -aG wheel ana
add user to dialout group
sudo usermod -G dialout -a ana
install Anaconda3 under /home/ana/anaconda3/
During the installation, allow Anaconda to path, so pip or python will call Anaconda stuff
I have read this entire topic, but cannot get the Z-Wave gen5 stick working.
I am using the Hass.io raspberry pi docker image. I am not able to get a full shell, so I cannot do most of the instructions here.
Is there some other way to get it working on hass.io? Or do I need to drop the RPI3 and do a manual install on some linux machine?
For docker you also need a device flag and to run it as privileged. Further you can’t do the udev rules and symlinks, you need to find out the actual dev location.
But how am I supposed to do any of this when all I have is the hass.io shell with just some basic commands? I must be missing something? Is there a way to gain full root access on the latest rpi build?
I have read every single thread on this site regarding this issue. I have wasted countless hours on this one stupid thing and I have to let any other future stranger that may be in the same pit as I know: User permissions don’t take effect until you relogin your shell.