for me, all the scenarii are detected from KeyPressed to KeyPressedx5. KeyHeldDown and KeyReleased work too.
1 Like
Hi,
i do only see three entities for the button, in the event logg i log actions when i push the button, but there is no entity_id only device_id. What entity do you use in the automation?
thx
You do not need entity_id, I use the device_id, from the log, as trigger in the automation
platform: event
event_data:
device_id: XXXX
value: KeyPressed
event_type: zwave_js_event
what’s wrong? All push actions are logged correct in event log but nothing is happening with my automation
alias: Push test
description: ‘’
trigger:
- platform: event
event_data:
event_data:
device_id: cf2b1df058f78e12760bf2a152568ed3
value: KeyPressed
event_type: zwave_js_event
action: - service: light.turn_on
data:
flash: short
target:
entity_id: light.kitchen_table_d1
this is working for me:
alias: bouton on
description: ''
trigger:
- platform: event
event_data:
device_id: XXX
value: KeyPressed
event_type: zwave_js_event
condition:
- condition: state
entity_id: light.led_bibliotheque_1
state: 'off'
action:
- service: light.turn_on
data: {}
target:
entity_id: light.led_bibliotheque_1
mode: single
Thx!
Copied your config and updated it with my entities. Whola! everything worked!
1 Like
Hello,
following the new HA core revision 2021.4, the zwave_event is no more working. It breaks all my automations using this button. It has been replaced by the event zwave_js_value_notification or zwave_js_notification. In our case the button trgigger zwave_js_value_notification.
But in my case, it almost not working. the event is triggering only for the scenes KeyHeldDown and KeyReleased and not everytime… All the others scene are no not working anymore. 
Is it working for you?
Actually, I had the opposite experience. Following that same upgrade, all of my button’s event values are received by HA (almost) reliably. Before this upgrade, your two were (almost) the only ones that worked. Bad luck!
that’s really strange…
it’s definitelly not a reliable button… do you know what is the rev of your button? which zwave stick do you use?
The box says FGPB-101-7, it is running firmware 3.2 and my controller is a Z-Wave.Me Razberry daughtercard (on a Pi 3B+).
If you haven’t noticed, by the way, you can now view and edit configuration parameters for Z-Wave devices. There is a whole set of toggles for “Scenes sent to the controller: Key pressed 1 time” and so on. It must be worth your while to check how those are set.
It works perfectly for me with the following code when running 2021.4:
trigger:
- platform: event
event_data:
device_id: XXX
value: KeyPressed (or KeyPressed2x etc)
event_type: zwave_js_value_notification
What happens when you listen to the zwave_js_value_notification event in the Developer Tools?
When I Listen to the zwave_js_value_notification event, it triggers an event only for KeyHeldDown or KeyReleased scenes. Nothing happens for KeyPressed and it’s not 100% reliable.
what is stange is that when I listen for * and then I press the button I have the folowing state change:
"event_type": "state_changed",
"data": {
"entity_id": "sensor.button_battery_level",
"old_state": {
"entity_id": "sensor.button_battery_level",
"state": "100.0",
"attributes": {
"unit_of_measurement": "%",
"friendly_name": "button: Battery level",
"device_class": "battery"
},
"last_changed": "2021-04-10T16:31:19.678049+00:00",
"last_updated": "2021-04-10T16:31:19.678049+00:00",
"context": {
"id": "1fd462d680e6fc127fa03c7692b22530",
"parent_id": null,
"user_id": null
}
},
"new_state": {
"entity_id": "sensor.button_battery_level",
"state": "100.0",
"attributes": {
"unit_of_measurement": "%",
"friendly_name": "button: Battery level",
"device_class": "battery"
},
"last_changed": "2021-04-10T16:31:29.040956+00:00",
"last_updated": "2021-04-10T16:31:29.040956+00:00",
"context": {
"id": "b1049051782e06adf203281955456a96",
"parent_id": null,
"user_id": null
}
}
},
it means that something happen but it’s not recognized as a scene.
I noticed, thank you. But all the scenes are ticked.
please could you shqre your button configuration : Key Pressed 1 time – command sent to 2nd asso …
It looks like it’ my turn to be in trouble with this button.
I tried to remove the node from the zwave network and it did not work. I never add this issue before.
Sure.
Key Pressed 1 time - command = Toggle Switch On/Off
Key Pressed 1 time - value = 255
Key Pressed 2 times - command = Switch On
Key Pressed 2 times - value = 99
Key Pressed 3 times - command = No Action
Key Pressed 3 times - value = 255
Key Pressed 1 time - command = Toggle Switch On/Off
Key Pressed 1 time - value = 255
Key Pressed 2 times - command = Switch On
Key Pressed 2 times - value = 99
Key Pressed 3 times - command = No Action
Key Pressed 3 times - value = 255
Key Held Down - command = Alternate Brightening / Dimming
and then all the toggles are on.
thank you. I have exactly the same button configuration.
Hi guys. Just started a blueprint for The Button with Z-Wave JS.
Help would be welcome, I still does not have understood how to enable 2 click and 3 click actions
As of a day or two ago, my button is not reliably generating zwave_js_value_notifications again. It was working fine for a couple of weeks. I’ll count that as good luck.
This button is really a nightmare. For me, it’s 100% useless now. I can’t even remove this node.
I will buy a button from Aeotec.
Does your issue started after the add-on update?
To be honest, if it’s working I just have it next to the front door and knock it when I leave the house then knock it when I come back. That doesn’t happen all that often at the moment so I might not have noticed precisely when it went funny again. I don’t think it was associated with an update this time, but I could be wrong.
It does sound like you have the same symptoms as me. When it is playing up, hitting it 4, 5 or 6 times to make something happen is pure fantasy. You can physically do that of course, but the associated messages are just not sent.
You might find that it is only 25 to 50% useless if you listen for ButtonHeldDown. That seems to be the most reliable one even when it is misbehaving.