In OpenZWave it is configuration (one of the XML files), so not on the stick.
1 Like
Hi!
I am having some trouble getting this to work.
So far what i have managed is:
i have installed the hassio addon:
Open Z-Wave Daemon
Then i have installed the hacs addon:
Z-Wave over MQTT (Pre-Release)
Also i have installed the Mosquito addon.
Now - everything seems to startup - and i can test the MQTT from the Dev tools.
I am also able to start the GUI ( qt ) - but i have nothing in there.
I have mapped my z-wave usb stick to its location:
/dev/serial/by-id/usb-0658_0200_E3040B02-4A02-0110-2C30-07170124EDB0-if00
My device is the:
Sigma Designs Generic Z-Wave Plus USB Dongle
When i look in the log for the hacs addon it says:
2020-02-03 22:56:13,976 INFO supervisord started with pid 6
2020-02-03 22:56:14,979 INFO spawned: âwebsockifyâ with pid 31
2020-02-03 22:56:14,980 INFO spawned: âozwadminâ with pid 32
2020-02-03 22:56:14,983 INFO spawned: âxvfbâ with pid 33
2020-02-03 22:56:14,986 INFO spawned: âmosquittoâ with pid 34
2020-02-03 22:56:14,989 INFO spawned: âx11vncâ with pid 35
2020-02-03 22:56:14,992 INFO spawned: âozwdaemonâ with pid 36
2020-02-03 22:56:16,031 INFO success: websockify entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-02-03 22:56:16,031 INFO success: ozwadmin entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-02-03 22:56:16,031 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-02-03 22:56:16,031 INFO success: mosquitto entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-02-03 22:56:16,031 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-02-03 22:56:16,031 INFO success: ozwdaemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-02-03 22:58:30,163 INFO exited: ozwadmin (exit status 0; expected)
2020-02-03 22:58:30,164 INFO spawned: âozwadminâ with pid 65
2020-02-03 22:58:31,711 INFO success: ozwadmin entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
It might be a noob thing - but how do i proceed?
br Ronni
I have two aeotec sticks, one used by the HA ZWave integration, and one by zwave2mqtt on the same NUC.
The QT-OpenZWave readme says Iâll have to remove my existing zwave integration.
What Iâd like to do is to replace the zwave2mqtt part with QT-OpenZWave, since today that one manages only devices that are supported.
Is this possible?
And one more question: Is it/will it be possible to have two QT-OpenZWave integrations, one per stick?
Also have an Aeon Labs z-wave stick, this make me think that it would be a good idea to back it up. I said this because I was very afraid with last 105 HA release that gives a lot of problems to my z-wave config. Had to rollback. So whatâs would be the best way backing up the z-wave network and stick???
Aeotec has backup software for the Z stick Gen 5 for free on their website.
Iâm using z-wave integration for a couple of years now. The Z-Network is some sort of unstable, there are exceptions in home-assistant log with catches. Index out of bounds error and all this for years now. I think z-wave integration in Home-Assistant is broken by "no"design!
TRĂ DFRI uses Zigbee not zwave
who is talking about tradfri here?
I based it off the majority of your posts regarding tradfri, youâve only posted once for assistance with a zwave device.
What makes you think zwave is unstable?
so you guessed wrong!
@unstable the fact, that nearly every reboot I have to restart home-assistant to see all nodes. and all three to six month I have to reset my zwave stick and rebuild the network by hand. The fact, that the log is full of exceptions like this:
Feb 07 15:17:37 homeserver start.sh[558]: Traceback (most recent call last):
Feb 07 15:17:37 homeserver start.sh[558]: File âsrc-lib/libopenzwave/libopenzwave.pyxâ, line 512, in libopenzwave.notif_callback
Feb 07 15:17:37 homeserver start.sh[558]: IndexError: list index out of range
Feb 07 15:17:37 homeserver start.sh[558]: UnboundLocalError: local variable ânâ referenced before assignment
Feb 07 15:17:37 homeserver start.sh[558]: Exception ignored in: âlibopenzwave.notif_callbackâ
Feb 07 15:17:37 homeserver start.sh[558]: UnboundLocalError: local variable ânâ referenced before assignment
and so on
Thereâs something up with your instance then. Iâve never seen those errors nor had to reset my stick/rebuild my network.
Thatâs a non-fatal error.
This sounds similar to the ModemManager issue thatâs in the troubleshooting section of the Docs.
Sounds like a hardware issue, Iâve never had to reset my zwave stick in the past 3+ years of using it with Home Assistant.
Ignoring exceptions and no bounds checking may not be a fatal error but itâs a completely unacceptable programming style.
What is a ModemManager and what has it to do with z-wave?
Obviously there are people that have the luck home-assistants open-zwave integration is working, otherwise nobody would use it. But the fact, that it works for you is clearly no sine of error freenes.
You best believe I had the idea of a hardware issue too, but Iâve already changed my stick and do still have the problems.
And the fact of the ugly programming style mixed with errors extremely looks like simply bad software.
1 Like
I donât even have a gui on this machine⌠no no modem manager
Your wording seems inaccurate. Modemmanager has nothing to do with GUI or no GUI.
1 Like
Is there anyway to install the ozwdeamon if your not using Hassio?
I think Docker is the recommended install for now.
1 Like
Yep just looked at that. But thereâs no suppoer for mqtt authentication 
[local@homeserver ~] (130) $ ps ax | grep -i modem.*manager
4526 pts/1 S+ 0:00 grep -i modem.*manager