Hi all,
so i am not smart enough to figure out my zwave problem,
and can not even find any log files to help me. So this is what happened.
i crashed my system had to reformat. i am using a raspberry pi4 4 gigs.
Iam running Home Assistant OS 5.12 with core-2021.3.2. Now that we know that. I had a crash and had to reformat
when I put my Hubzusb1 stick back in and added zigbee. Everything was good all my devices came up, But whe i put zwave integration
my siren worked but neither lock worked tried everything to get old locks out and reinstall to no avail. So i decided to get a new zwave stick since the
hubzusb1 stick has old zwave stack any way. So i purchased an Aotec gen5 zwave stick. But now even though my new stick is there at /dev/ttyACM0 even though the hubzusb stick
was at /dev/ttyUSB0 when i try to install the zwavejs integration it just says Failed to set Z-Wave JS configuration.I have tried installing the older beta version and even though
it says success it never starts the network. I do have mosquitto mcqq installed can any one help please please please
I have tried putting it in manually by adding to my config file this
zwave:
usb_path: /dev/ttyACM0
device_config: !include zwave_device_config.yaml
but when I do I get
Logger: homeassistant.components.hassio
Source: components/hassio/init.py:454
Integration: Hass.io (documentation, issues)
First occurred: 10:52:16 AM (2 occurrences)
Last logged: 10:56:11 AM
Error loading /config/configuration.yaml: in “/config/configuration.yaml”,
line 26, column 18: Unable to read file /config/zwave_device_config.yaml.
I had issues with my Hubzusb1 stick.
I had a Aeotec stick that I originally planned.
The Aeotec stick for some reason played more nicely with my devices.
Also if you’re fed up with possible corrupted devices in your Aeotec stick you can just hold the button down for however many seconds to clear everything and start again.
Overall I’m removing Z-Wave from my life as soon as financially feasible.
My kwickset lock supports a Zigbee card swap but they’re so expensive.
My family’s approval rating of the lock would probably only go up with a nicer lock, so it’sa tough sell.
A bit off-topic, but can you point to where you found the documentation for the zwave_device_config.yaml layout? I’m having issues with basic zwave devices that do not seem to respond to certain requests and then end up as offline.
in case you are interested you can symlink your devices using udev rules. so no matter what they are you can always have something like /dev/zwave and it will always point to your device
here is my rule, but it is specific to my device and my setup.
root@hass:/etc/udev# cd rules.d/
root@hass:/etc/udev/rules.d# ls
99-usb-serial.rules
root@hass:/etc/udev/rules.d# cat 99-usb-serial.rules
SUBSYSTEM==“tty”, ATTRS{idProduct}==“0200”, ATTRS{idVendor}==“0658”, SYMLINK+=“zwave”
root@hass:/etc/udev/rules.d#
i had the supervisor addon configured wrong i just put in location but the new js integration actually has a drop down menu letting you choose which device i could see the aotec stick and just pointed it to it
yes or because like me, after reading one line of the instructions and not doing the correct research and thinking I already know this. Arrogant and stupid, That’s user error