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

Yep, so no need to have “zwave_js_event” list on the right?

image

I start to listen but it’s empty :frowning:

That’s only added when you have an automation that triggers off the event

1 Like

I didn’t know that’s where they came from.

wowww i’m lost…
With the old Zwave integration, i was using this automation:

- alias: 'Update motion'
  trigger:
  - platform: event
    event_type: zwave.node_event
    event_data:        
      entity_id: zwave.homeseer_express_controls_hsm100_wireless_multi_sensor
      basic_level: 255
  action:
  - service: input_boolean.turn_on
    entity_id: input_boolean.mouvement_salon
  - delay: '00:00:25'
  - service: input_boolean.turn_off
    entity_id: input_boolean.mouvement_salon

How can i translate to the new js_event ?

You have to watch for the events generated by the zwavejs integration and capture the event data that you want to use from that event. then fill in the info to your trigger.

Ok thanks for your quick reply :slight_smile:
So, i’m listening on js event, but it’s empty…

Strange thing is that “Basic Level” is show by the Zwave JS but it doesn’t move, it stays at “0”

Have you triggered the motion sensor?

I migrated from OZW (beta) to ZWaveJS using the ZWaveJS2MQTT add on (only using the ZWaveJS WS, MQTT disabled). I only have 1 Zwave Device, a GE/Jasco 14294 dimmer. In my OZW configuration, I had to update update verifyChanges = True in order to keep the state in sync with the physical button. I’m assuming since I did not need to re-pair the device, this migrated over.

All states are being reported, however there is a 3-4 second delay when turning on the switch from HA before the state is updated. Turning off via HA the state updates almost immediately. Is there something I should look at?

seems you’re missing out on a binary sensor, which the motion sensor would always create? I have the odd _basic sensor (on a fibaro flood level sensor) but that device too creates binary sensors for the main purpose.

btw, you’re saying you use the core zwave JS add-on and integration? I ask, because you have the zwave_js_event listed, and I cant find these in the events

The device updates when the dimmer reaches it’s position. Does your dimmer take 4 seconds to reach it’s final resting brightness? If so, then it’s working as expected.

already covered…

I finished migrating to zwave JS using the add-on, starting from scratch on a different controller. It works beautifully now. It’s very fast and responsive.

Thanks again to all the help I received from @petro and others on discord.

1 Like

Yes !

@Mariusthvdb, i’m using zwave JS add-on and integration and i haven’t got the zwave_js_event listed.

@petro, i don’t really understand when you say “when you have an automation that triggers off the event”

exactly because you wrote that above, I made an automation in the interface using the zwave device…
my first in the ui, so very uncomfortable with that. I’ve now created it to trigger on the device, but guess it should trigger on an event to make the event zwave_js_event show up?

Nothing in a drop_down though when I click Event (gebeurtenis).

in the UI, there’s no field showing a zwave_js_event, so how we can create an automation using that is beyond me for now.
O well, shouldn’t be easy…

Answer this question:

Do you have an automation that uses zwave_js_event? If the answer to that question is Yes, it will appear in the Available Events list. IF the answer is no, it will not.

1 Like

No. It will only appear if you are using an event trigger in an automation.

trigger:
  - platform: event
    event_type: zwave_js_event
    ...

:man_facepalming: That’s also been covered a few posts up.

Let's start talking about the new Z-wave JS integration - #448 by stban1983

really sorry, but shaking your head doesn’t make this very obvious…

this seems to be a catch22. we can only see the zwave_js_event in the Available events, if we use it in an event trigger in an automation. To find out which events are available we have to listen to events generated by the zwavejs integration.

So how are we able to enter that into the listen to event field on the event page, if its not used because it isn’t listed yet…

I am not trolling, this is extremely unclear. for me.

I would have expected the zwave_js_event to be created upon installing the zwavejs integration, and be available in the automation editor by default.

You literally use your fingers and type it out.

2 Likes

of course, that is on base of need to know, and hardly a great UI experience/design, but even after doing that, nothings happening for now. Guess turning a switch on /off doesn’t constitute an event.

Ill need to re-read https://www.home-assistant.io/integrations/zwave_js/#events for it to become clear.
And yes, I did read the zwave_js_event mentioned there, but as explained, would have thought that to be automatically available because of installing the integration, and several devices.