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

kan84 · November 24, 2021, 5:23pm

Were you able to get pressed down events working?

kklicker · November 24, 2021, 6:32pm

Yes, I was able to get this working after they updated Z-Wave JS.

kan84 · November 25, 2021, 1:25pm

Do you mind posting the automation or blueprint if any?

kklicker · November 25, 2021, 9:46pm

Here is an example of using the KeyHeldDown event:

- alias: Make Monique's light go bright
  initial_state: 'on'
  trigger:
  - platform: event
    event_type: zwave_js_value_notification
    event_data:
      node_id: 6
      property_key_name: '001'
      value: KeyHeldDown
  action:
  - service: script.turn_on
    entity_id: script.ramp_light
    data:
      variables:
        direction: up
        light: light.monique_light

and also an example of when the key is released:

- alias: Random effect Ceiling Light
  description: ''
  trigger:
  - platform: event
    event_type: zwave_js_value_notification
    event_data:
      node_id: 16
      property_key_name: '001'
      value: KeyReleased
  condition: []
  action:
  - service: wled.preset
    entity_id: light.wled_2
    data:
      preset: 2
  - service: wled.effect
    entity_id: light.wled_2
    data:
      effect: '{{ states(''sensor.light_effect'') }}'

Hope it makes sense.

kan84 · November 26, 2021, 2:27am

Thank you!

kklicker · November 27, 2021, 5:18pm

You’re welcome, hope it helps.

kzelnick · November 30, 2021, 5:09am

i see the following in my logs
question on mqtt broker logs i get the following

INFO APP: GET /health/zwave 200 1.240 ms - 1873

Fairly new to the z wave mqtt broker should is see this, happens every two minustes
it seems to slow things down

checking12 · November 30, 2021, 8:54am

I do have zwave slowness sometimes, but cant figure out which part is causing it.
What do you see that makes you think it slows things down?

firstof9 · November 30, 2021, 7:28pm

It doesn’t slow anything down.
That’s a health check to make sure the container/addon is working.

kzelnick · December 1, 2021, 12:01am

thanks still failry new to z wave and js vs mqtt so trying to understand all of the nuances and differences. For now i am sticking with mqtt

euromem · December 6, 2021, 3:47am

Hate to appear as a complete noob here, but here I am…
I am running HA Blue with Z-Wave JS and the AEON Gen5 Z-Wave stick and the Z-Wave JS to MQTT add-on.
Can someone please explain whether I need to update in the Z-Wave JS config panel or not as it tells me a newer config version is available?
I thought Z-Wave JS was native now and I would not have to do updates like this or am I wrong?
Honestly afraid to break my Z-Wave network after the switch from Vera left me traumatized.
Many thanks.

freshcoast · December 6, 2021, 5:41am

You don’t need to update unless you have a device that needs a new or updated device config file, and the new version has that update. If you don’t know, then you probably don’t need to update.

finity · December 6, 2021, 3:50pm

But just to answer the question more generally…

the zwavejs2mqtt add-on is separate from the zwavejs integration.

the zwavejs integration is built-in to HA but the add-on is not so you will get a new updated integration automatically when you update HA (if there are any) but you will need to update the zwavejs2mqtt add-on (or even the zwavejs ad-on) manually when one becomes available. But as mentioned above only if you need it.

euromem · December 8, 2021, 8:19pm

As someone who has always done updates in almost everything else, I have been super cautious with HA as I have lost my entire Z-Wave network more than once and it’s a little annoying having to roll back.
Thanks for the info.

euromem · December 8, 2021, 8:20pm

Thanks for taking the time to reply. I don’t seem to notice anything untoward, so I think I will let sleeping dogs lit.
Thanks again.

gregg098 · December 8, 2021, 8:36pm

I’m using Docker and just run a script to backup my source folders before doing any kind of upgrades. It takes about 5 seconds to run and rolling back is super easy.

For example, my backupall.sh script.

#!/bin/bash
sudo zip -q -r "/home/gregg/backup/$(date +"%F") hass.zip" /srv/docker/homeassistant/config
sudo zip -q -r "/home/gregg/backup/$(date +"%F") nodered.zip" /srv/docker/nodered -x "/srv/docker/nodered/node_modules/*"
sudo zip -q -r "/home/gregg/backup/$(date +"%F") zwavejs.zip" /srv/docker/zwavejs
sudo zip -q -r "/home/gregg/backup/$(date +"%F") zigbee.zip" /srv/docker/zigbee2mqtt

Haven’t used Hass OS since the Hassio days, but I’d assume snapshots are even easier to deal with.

moto2000 · December 14, 2021, 9:37pm

Not sure if you used the z-waveJS addon lately, but you can do all those things you mentioned:

finity · December 15, 2021, 3:58am

THat screen has nothing to do with the zwavejs add-on.

That is the zwavejs integration configuration page.

You get the same page whether you use the zwavejs add-on, the zwavejs2mqtt add-on, the standalone zwavejs2mqtt docker container, etc.

moto2000 · December 15, 2021, 4:38am

My point was that the functionality he said wasn’t there, is actually there…

Bohemian · December 28, 2021, 10:20pm

I finally took the plunge to move from the previous deprecated Z-Wave 1.4 to Z-Wave JS and must admit that I’m underwhelmed. Mainly because with this implementation, several of my devices have less supported sensors / entities than the older deprecated version.

This ranges from the just plain silly (a flood detector that not longer reflects actual flood status) to really inconvenient (no ability to properly read alarm status from my Yale lock). So, existing automations which I’ve come to rely on no longer function since the stimuli are absent.

I’m tempted to ‘simply’ revert back (if that is even possible) to a previous backup and wait until this Z-wave JS integration catches up to where the old one was. But being future proof but with less functional capabilities is a tricky tradeoff.