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.
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.
No. It will only appear if you are using an event trigger in an automation.
trigger:
- platform: event
event_type: zwave_js_event
...
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.
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.
It is available. It’s not being listened to. That list only shows events that are listened to. I don’t know how else to spell that out to you. If there’s nothing to action off an event, then home assistant doesn’t listen to it.
Notice how that list doesn’t have anything with a 0?? Otherwise that page would be 1000s of events long.
And just to clarify, You can create any event. You can create an event called Mariusthvdb ant trigger off it if you wanted.
FYI, Daniel Lando did not partake in the development of the new integration.
Hahah yes, I see that and have several manually created events in my production.
Evenso, Mariusthvdb isnt listed on the right side under available events?
I was under the apparently wrong impression the events would be ‘fixed’ to the Events - Home Assistant , events created by integrations like they were listed before on the deprecated integration Z-Wave - Home Assistant and the incidental manually created events.
Now imagine this binary_sensor.front_door_is_open in the zwave entities. How do I create an automation using the interface alone, which listens to the zwave_js_event of this binary changing?
I get this:
and when continuing see:
where the trigger field doesnt offer the zwave_js_event option:
If changing a state or value, or even toggling a switch don’t register a zwave_js_event, the (my) question is what does?
Like @Mariusthvdb, i was thinking that zwave js will send an event like zwave.node_event was doing.
Sorry @petro if we don’t understand 
Now, i don’t know how to catch the BASIC_SET command when motion is detected by my motion detector
It does not take 4 seconds to reach its final brightness. In fact, I have reconfigured from the default timing of steps from 3 to 2 (from OZW config).
Not a major issue at all, just something I noticed.
Sorry to disagree, but please, by all means, correct me if I’m wrong.
Even if he did not take part in the integration, he did develop both ZWaveJS and ZWaveJS2MQTT.
Also, please refer to the following: https://www.home-assistant.io/blog/2021/02/03/release-20212/
I have captured a little part of this link in the below image. The last name in the otherwise alphabetically sorted list is Daniel Lando. So, I don’t see how we would be having this thread without his work…
zwave-js maps the Basic Set message to some other value by default.
Also the HS-MS100 is supposed to support the Notification command class, which HA represents with some standard binary_sensor entities. There shouldn’t be any reason to rely on Basic Set.
You should either have some other entity to use, or disabled entities with the “basic” name. Do you not see any entities?
