Let's start talking about the new Z-wave JS integration

You’re not wrong, he did take part in some ZwaveJS development but The integration, addon, python server were all created by the devs listed here. I would assume you’d want to thank him where he’ll see it and then here you’d be thanking the developers who put it into HA. Just my 2c. It would be akin to thanking samsung for the sansung home assistant integration. Doesn’t make sense, does it?

Ok, I see your point now.
Peace out.

I don’t know what i did, but now it’s almost work. Basic sensor goes to value 255 when there is a motion. I test it many times this weekend and it works only now, i don’t know what i missed!
It’s not detect as a binary_sensor but i will create a template.

How does zwavejs work when the device configs get updated? I’ve been running zwavejs2mqtt (with zwave_js version 6.1.2) for a while, which did not include support for the ZEN30 switch. ZwaveJS 6.1.3 was released that included support for that switch, which was also included in the zwavejs2mqtt 1.1.0 release today. I’ve upgraded the mqtt container, but the control panel still shows the the device as unknown, and the associated HA device also shows it as unknown. I have verified that the zen30 configuration files are in the container, and it appears to be like the product code lines up.

Is there something special i need to do in order to get the zwavejs app to refresh?

https://github.com/zwave-js/node-zwave-js/pull/1660 shows there is a bug where product id and type are switched. I don’t think your ZEN30 will show up until that is patched.

1 Like

aha, thank you. i missed that PR

@jsternadel
I’m using ser2net (TCP port 4000) on my Pi (192.168.1.101) for ttyAMA0.
ZWaveJS is on HA Blue ODROID (192.168.1.104) and ZWave Serial Port is tcp://192.168.1.101:4000

Yeah, thats the one I was thinking of.

FYI - YES this process DOES work; I have two zsticks, I modded one with a higher gain antenna and transferred the network from my old Zstick to the new modded one. Works well!

PS: when ever I back up I make two separate backup runs.

PPS: I run HA on a VM so just deselect the ZSTICK usb from the HA VM, and assign to Windows VM and run the backup tool., then switch back (all remotely to the vm host). It’s easy, so I’m more likely to backup this way.

I added this to my bookmarks to check out along with usb_ip. Now to find out if I can run a Pi with a PoE hat and power a ConBee and Aotec stick off of it. If it works I can put the pi anywhere I can run cat6 and get HA on my docker server in the basement rack. Thanks for this.

One of the beautiful things about the ZwaveJS server is that the websocket server does not need to be on “localhost”. Rather than using USB-over-IP to relocate the USB stick itself you can just run the ZwaveJS server of the remote machine and point the HA Integration to it.

A raspberry PI should prove more than enough to get this done.

I currently run Zigbee services this way, using Zigbee2mqtt on a tiny machine centrally located in my house. I plan to run the ZwaveJS server on the same machine when I make the switch and place both dongles on it. That way even when I upgrade the whole OS on the server HA runs on the Zwave & Zibbee networks keep right on running.

1 Like

For anyone not seeing a zwave_js_event triggered, but you see it in the zwave js logs, make sure your HA software is up to date. I was a few revs back and once I updated, i saw it.

I’m seeing this in my supervisor log…

21-02-09 00:35:48 INFO (SyncWorker_0) [supervisor.docker.interface] Stopping addon_a0d7b954_zwavejs2mqtt application
21-02-09 00:35:48 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Server disconnected
21-02-09 00:35:48 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.3:8099 ssl:default [Connect call failed ('172.30.33.3', 8099)]
21-02-09 00:35:49 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.3:8099 ssl:default [Connect call failed ('172.30.33.3', 8099)]
21-02-09 00:35:52 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_a0d7b954_zwavejs2mqtt application
21-02-09 00:35:52 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/zwavejs2mqtt/aarch64 with version 0.4.0
21-02-09 00:35:52 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.3:8099 ssl:default [Connect call failed ('172.30.33.3', 8099)]
21-02-09 00:35:58 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.3:8099 ssl:default [Connect call failed ('172.30.33.3', 8099)]
21-02-09 00:36:05 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message='Invalid response status', url=URL('http://172.30.33.3:8099/socket.io/?EIO=4&transport=websocket&sid=IAW5GdkGu_lHpOoOAAAA')

Any ideas what might be wrong?

Thanks to all the devs. Just upgraded to 2021.2.2 and also the new ZwaveJS2MQTT version and between the two of them, it fixed 2 of 3 remaining issues I have.

  1. First Alert ZCOMBO now reports alarm_level and alarm_type. I have a template binary sensor from there. I dont think they ever implemented a binary_sensor at the hardware level so its always been setup through a template binary_sensor in Home Assistant.

  2. Everspring Flood Detector now reports a binary sensor instead of Uknown. All the other sensors dont seem to work, but it properly reports on/off for wet/dry which is all that matters.

Final remaining issue is the ability to set parameters mainly for Innoveli Red switch notifications. Anyone know when this might get integrated?

Did you have any z-wave locks that now got the alarm_type and alarm_level sensors? I was holding off on moving to zwave_js until I saw that this update supposedly added support for alarm_type and alarm_level but I still do not have them being created. I do see the event though, so not a huge deal. Would just be easier to not have to change a bunch of automations and what not…

I do have them (they were disabled), but they dont do anything. I enabled them on my BE469 and they initially showed up as Unknown. Restarted Home Assistant just in case and same thing. Did a few remote, manual, and code operations and no updates.
My locks do show events OK, but state changes are hit and miss.

I removed one lock to re-add it thinking that would help generate the sensors (I had to exclude and re-include secure devices when moving from Old Z-wave to OZW Beta) but now I am having trouble getting it to add… not sure if this is even a necessary step… it seems the page to add and remove nodes stops doing anything to the controller… unless I am not being patient enough and it is still completing something…

Any update when GoControl Garage door devices will support cover?

1 Like

How to remove a removed node from the UI list?