This totally hosed my Zwave network that has been rock solid for years now. Documentation is not well written and has cost many hours of troubleshooting. There should be standards before coming out of beta.
Thats why it is still in beta. What issues did you run into, perhaps submit issues so they can be rectified. The software clearly states it is still in development so you only have yourself and what has been written as guides by others here so far.
I have a small zwave network so didn’t run into any issues but users with larger networks like yourself should definitely detail what specific things you encountered to improve it.
Been in IT and Development for many years and understand beta releases, however this is more like a ALPHA release then a beta. And IMO it should not be published out to the masses, To many issues, documentation is not well written, and just not mapped out very well.
2 Likes
If you really do work in IT, then I’m sure you recognise the risks you take when you CHOOSE to install software that is very clearly marked BETA.
1 Like
That’s not the point @ccollinscj is trying to make. He is saying that the way it was released it does not deserve a BETA status, which I agree with. Very unorganized release. I was unable to find any official documentation describing changes and mentioning removal of the current config gui and all of the features tied to it. I don’t even see anything describing what is wrong with the current Z-Wave functionality and why is it getting replaced. This is a huge breaking change for people. My network is small and I was able to rollback, but i did have to spend some time getting things to run properly after realizing that this “BETA” crippled my current Z-Wave situation and added absolutely nothing of value.
1 Like
If everything was working fine for you on the existing installation, I have to ask, why did you move to the new Beta then? Lack of documentation should have been a warning?
As for why?
- the existing integration is using OZW 1.4, which is > 4 years old and hasn’t been maintained upstream for almost 2 years.
- Plenty of issues with 1.4, such as “hacks” to support central scene, hundreds of bugs fixed in 1.6, new features/functionality on the backend, and architectual decisions made in 1.4 days that don’t work so well in this day and age. Spend a few minutes searching the forums for issues with 1.4 would clearly show its “age”
Please remember, this is a community driven integration. As volunteers we only have so much time each day to work on this, and with 3000+ Z-Wave devices on the market, no way we can figure out every single use case, or potential issue people will face by ourselves. Hence the Beta Release.
Its unfortunate you had issues with it, but there is 0 I can do to help you and thus “mature” the new solution (at least on the OpenZWave side) with feedback such as “crippled” my network.
As I pointed out in another thread (So when is OpenZWave (OZW) version 1.6 coming to Home Assistant?) I’d encourage you, if you are up-to it, to contribute in a positive matter to this release, instead of a blanket criticism. Its very discouraging to those that put in hundreds of hours writing and supporting code .
9 Likes
@Fishwaldo I moved because I like tinkering with things. It’s not a problem for me if i blow up the entire install. And this is not just blanket baseless criticism. I enjoy Home Assistant immensely and have been running it for almost 2 years. I don’t have a stable install I break things and i fix them. I love it. And I appreciate the work you guys put into it. But you have to agree that just throwing couple more lines of info into readme would’ve been a good idea. Just to avoid misunderstandings like this.
2 Likes
Do keep in mind Fishwaldo is the openzwave maintainer and has no control over the documentation or code provided for the OpenZwave Integration in Home Assistant.
Tried the new integration, set up all my devices an got it all responding, but now it won’t start up and the log reports this
INFO (SyncWorker_15) [supervisor.docker.interface] Clean addon_core_zwave application
20-07-05 11:16:56 ERROR (SyncWorker_5) [supervisor.docker] Can’t start addon_core_zwave: 403 Client Error: Forbidden (“endpoint with name addon_core_zwave already exists in network hassio”)
Well, you guys have convinced me… I will be waiting to mess with Open Z-Wave until it is out of beta or I see a lot more maturity in it. I just got my first 3 Z-Wave devices transitioned from my SmartThings hub last night. It took me hours just to figure that out. I was considering trying to dig deeper into Open Z-Wave today, but I am thinking I may just wait for the general release at this point.
1 Like
My HASS is running under Debian 10 and I have a RaZberry hat in my Pi that is accessible via IP:port using ser2net and I’ve been using it with HomeSeer like a Z-Net via IP:port. Is there a way to do this in HA OpenZWave?
Either IP:Port & ser2net
or socat & ser2net
or maybe usbip server/client??
It would be easier to just run ozwdaemon on your Pi.
Duh! Sometimes one tends to overlook the obvious!
Thanks…
You could of course use some sort of USB over IP solution and connect to it the same way you would with the old ZWave, some people have been successful (some not). But if you already have a Pi serving as the USB host, then it feels like unnecessary overhead.
I can’t seem to use usbip as the RaZberry HAT is a UART on the Pi and does not have a USB ID. Nor can I use ser2net / socat since everything I look at in HASS seems to requires a local physical USB serial port and the socat creates a symlink for /dev/ttyAMA0 to /dev/pts/1 and the symlinked /dev/ttyAMA0 is not an option in pulldowns.
I’ve installed docker and openzwave/ozwdaemon:allinone-latest on my Pi (192.168.1.101) but I’m somewhat at a loss as how to properly configure it. I’ve installed mosquito and the MQTT integration on my HASS machine (192.168.1.104) but it seems to want a local ozwdaemon…
Sorry, missed the razberry part. I haven’t heard of anyone using any network serial access with that.
I’ve installed docker and openzwave/ozwdaemon:allinone-latest on my Pi (192.168.1.101) but I’m somewhat at a loss as how to properly configure it. I’ve installed mosquito and the MQTT integration on my HASS machine (192.168.1.104) but it seems to want a local ozwdaemon…
There’s a pretty extensive example to configure the container on the github page. What part is tripping you up? GitHub - OpenZWave/qt-openzwave: QT5 Wrapper for OpenZWave
You configure the MQTT integration to connect to your mosquitto broker, and configure the ozw docker container with the same broker.
So I started from square one…
Installed Mosquitto with anonymous; true
MQTT integration popped up & I configured it
On Pi, started a docker with:
docker run -d \
--name ozwd \
--restart=unless-stopped \
--security-opt seccomp=unconfined \
--device=/dev/ttyAMA0 \
-v $PWD/ozw:/opt/ozw/config \
-e MQTT_SERVER="192.168.1.104" \
-e USB_PATH="/dev/ttyAMA0" \
-e OZW_NETWORK_KEY="0xBC,0x87,0xD5,0xE2,0x51,0xB3,0xA7,0x44,0x05,0x20,0xEA,0x0E,0xBC,0xF9,0xD6,0x17" \
-p 1983:1983 \
-p 5901:5901 \
-p 7800:7800 \
openzwave/ozwdaemon:allinone-latest
VNC to 192.168.1.101:5901 shows me this:
In Integrations I now see this…
Do I need to configure it as the final step or is it just the local equivalent of the ozwd that’s now running on my Pi?
I am not seeing anything in MQTT Explorer…
After quite a few hours of tinkering I’ve discovered that my dockerized ozwdaemon will work with my spare Nortek HUSBZB-1 but not with my RaZberry card which it is supposed to. I created two docker containers to test and the ttyUSB0 one works fine with the Nortek…
docker run -d \
--name ozw_AMA0 \
--restart=unless-stopped \
--security-opt seccomp=unconfined \
--device=/dev/ttyAMA0 \
-v $PWD/ozw:/opt/ozw/config \
-e MQTT_SERVER="192.168.1.104" \
-e USB_PATH="/dev/ttyAMA0" \
-e OZW_NETWORK_KEY="0xBC,0x87,0xD5,0xE2,0x51,0xB3,0xA7,0x44,0x05,0x20,0xEA,0x0E,0xBC,0xF9,0xD6,0x17" \
-p 1983:1983 \
-p 5901:5901 \
-p 7800:7800 \
openzwave/ozwdaemon:allinone-latest
docker run -d \
--name ozw_USB0 \
--restart=unless-stopped \
--security-opt seccomp=unconfined \
--device=/dev/ttyUSB0 \
-v $PWD/ozw:/opt/ozw/config \
-e MQTT_SERVER="192.168.1.104" \
-e USB_PATH="/dev/ttyUSB0" \
-e OZW_NETWORK_KEY="0xBC,0x87,0xD5,0xE2,0x51,0xB3,0xA7,0x44,0x05,0x20,0xEA,0x0E,0xBC,0xF9,0xD6,0x17" \
-p 1983:1983 \
-p 5901:5901 \
-p 7800:7800 \
openzwave/ozwdaemon:allinone-latest
I also found this link which explains that I do need to add the OZW (Beta) integration as the final step in connecting HA with OZW.
Now if I could only get OZW to talk to my RaZberry card…
If you have the RaZberry connected to your Pi now? If so do a ls -al /dev/serial/by-id/* and post it here.
I would try image allinone-build-150, the latest builds have known issues. If that’s not successful, post the contents of the ozwdaemon.log