In the addon configuration.
Please read before posting 
I’m this close 
of stopping my journey with HA.
The dashboard and the flexibilty I really love. The integration with Hue, Somfy and other network connected devices is really good, but the zwave integration is causing me headache and frustration.
I have not tried other zwave devices than 2 wall plugs of different vendors and both are not discovered as suspected (unknown all the way). I can speak of other nodes and if they will include as suspected.
Also trying to work with the OpenZwave integration (together with MQTT) is not a succes. The addon disables over and over and there is no simple (dummy proof) manual found by me…
When I started the journey I was aware it could end up in changing config files and being not as plain forward as hoped for (Homey) but this is no fun for me…
I will stop for a few days and hope to be motivated again over the weekend…
thanks anyway for the support
You can always “integrate” your existing zwave bridge…
Yes… this would be the most easiest way… just use mqtt and we are good to go. But… this whole exercise was just to remove the existing bridge away and turn over to HA (old bridge is getting old and faced some issues already and replacing it with a new similar one would be a costly one)
I thought I did configure everything correctly from MQTT addon(default and no changes to the config) to OpenZwave addon where I only added to the config
device: /dev/ttyACM0
network_key: >-
0x27, 0x54, 0x7a, 0x5d, 0x50, 0x34, 0x03, 0x2e, 0x70, 0x29, 0xcb, 0xdc, 0x80,
0x6d, 0x84, 0x81
next I added the OpenZwave integration and received a notification MQTT integration was not configured. So I did with a mqtt user/pw created in HA.
Started everything (after reboot of HA) and the ozw addon is not starting.
When I check the log of the OpenZwave addon I see
ozwadmin: Settings Path is at “/root/.config/OpenZWave/ozw-admin.conf”
ozwadmin: Checking “/data/ozw/config” for manufacturer_specific.xml
ozwadmin: Checking “/data/ozw/config” for options.xml
ozwadmin: DBPath: “/data/ozw/config/”
ozwadmin: userPath: “/data/ozw/config/”
ozwadmin: Settings Path: “/root/.config/OpenZWave/ozw-admin.conf”
ozwadmin: Using Saved Network Cache Size: 1000
QT_MESSAGE_PATTERN: %{backtrace} is not supported by this Qt build
[20201023 10:57:33.754 CEST] [ozwadmin] [info]: OZWCore Initilized QTOpenZwave(0x1dd2e60) QTOZWManager(0x1dd3860)
[20201023 10:57:33.849 CEST] [default] [warning]: QVncServer created on port 5900
[20201023 10:57:36.489 CEST] [ozw.library] [debug]: Detail - Node: 255 Removing current message
[20201023 10:57:36.490 CEST] [ozw.library] [info]: Info - Node: 0 HttpThread Exiting.
[20201023 10:57:36.490 CEST] [ozw.library] [info]: Info - Node: 0 mgr, Driver for controller /dev/ttyACM0 removed
[20201023 10:57:36.491 CEST] [ozw.manager] [debug]: Driver Removed for “/dev/ttyACM0”
[20201023 10:57:36.491 CEST] [ozw.manager] [debug]: OZW Serial Port Closed
[20201023 10:57:36.491 CEST] [ozw.daemon] [info]: Shutting Down “ozwdaemon” Version: “0.1.0”
[20201023 10:57:36.491 CEST] [ozw.daemon] [info]: OpenZWave Version: “1.6.1210”
[20201023 10:57:36.492 CEST] [ozw.daemon] [info]: QT-OpenZWave Version: “1.2.0”
[20201023 10:57:36.492 CEST] [ozw.daemon] [info]: QT Version: 5.12.5
1603443456: Socket error on client qt-openzwave-1, disconnecting.
In exit
[cont-finish.d] executing container finish scripts…
[cont-finish.d] mqtt.sh: executing…
1603443456: mosquitto version 1.6.8 terminating
1603443456: Saving in-memory database to /data/mosquitto.db.
[10:57:37] INFO: Ensure upstream MQTT server has the correct OZW status
[cont-finish.d] mqtt.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
and later
[20201023 10:57:32.476 CEST] [ozw.library] [critical]: Fatal - Node: 255 Z-Wave Interface is not a Supported Library Type: Bridge Controller
[20201023 10:57:32.476 CEST] [ozw.library] [critical]: Fatal - Node: 255 Z-Wave Interface should be a Static Controller Library Type
[20201023 10:57:32.476 CEST] [ozw.library] [debug]: Detail - Node: 0 Notification: Controller Library is not a type we support
[20201023 10:57:32.477 CEST] [ozw.library] [debug]: Detail - Node: 255 Notification: DriverFailed: /dev/ttyACM0
which I don’t understand. When using /dev/ttyACM0 in the default integrated Zwave the USB stick is noticed and working (I can include devices and see lights blinking)
What am I missing… please be gentle as I’m a simple guy trying to figure out and all the Youtube videos is saw and website I red made it look simple
Try this again
Tried this, rebooted HA, but no luck. Same errors…
I’m starting to have serious doubts with the USB stick. I have request a RMA and ordered a new one just to rule the usb stick out… Will receive it tomorrow so hopefully this will be the right move
Always nice to report back what a new zwave USB stick resulted in.
It was like a EUREKA moment… just put in the plug, install ozw and mqtt broker and works like a charm
Always frustrating when hardware is failing, but to start with a faulty device was unexpected and not the first what came to mind… glad it is solved and the faulty stick is returned to sender
yes that was the one… and I only can acknowledge that it is crap… case closed
Haha, yes. And don’t look back :-).
** I had two of those on my longer time ago z-way adventure… 1st one did not work well, 2nd broke after firmware update…