Thanks for the reply, Francis.
The problem is that there’s no button name/entity to select.
In Developer Tools -> Events I can listen for zha_events. If I press a button I get:
Event 4 fired 09:33:
{
“event_type”: “zha_event”,
“data”: {
“device_ieee”: “00:12:4b:00:1c:d6:10:45”,
“unique_id”: “00:12:4b:00:1c:d6:10:45:1:0x0006”,
“endpoint_id”: 1,
“cluster_id”: 6,
“command”: “toggle”,
“args”: []
},
“origin”: “LOCAL”,
“time_fired”: “2020-08-14T08:33:43.675881+00:00”,
“context”: {
“id”: “dcfaf613de0811ea8a66857578c757a4”,
“parent_id”: null,
“user_id”: null
}
}
So the button is actually working, but I can’t find a way to access it in HA or Node-Red.
Jim
Thanks Jason - looks like it’s going to be a tough one to crack - and far beyond my skills!
Jim
Yes ,me to I’m going to spend time on the weekend with the documentation and see if I can work it our, I’m not a programmer.
You can request it on the github site if you follow the links from the ZHA documentation. From the device in ZHA, you gather the “signature” and request the developers to help out.
I had a similar problem, I couldn’t find the 8 identities from my 8ch remote paired with Sonoff bridge.
I managed to solve it with catching MQTT messages in NodeRed so I didn’t even need the entities in HA
I’m new to ZHA as well, can you listen for the zha_events from that device ID?
Here is an example for SmartThings Button.
I sorted my problem out - see this post, it may help:
Jim
There is a HACS add on to turn an event into a sensor.
Jason
Thanks Jason.
I’ve had a look at it and it seems a bit of a ‘faff’ to set it up, compared to Node Red. (I’m finding that most things are easier to do and trouble shoot in Node Red.)
Jim
Hi,
How did you get this far, I have tried
and get nothing?
I recommend that you try Node Red, - it’s very much easier.
Jim
Hi, Installed the Integration from Hacs but unsure about configuration
I selected any other for integration firing events to listen for.
This is my log from hza_event
Event 1 fired 5:22:
{
"event_type": "zha_event",
"data": {
"device_ieee": "00:12:4b:00:1f:91:92:1f",
"unique_id": "00:12:4b:00:1f:91:92:1f:1:0x0006",
"endpoint_id": 1,
"cluster_id": 6,
"command": "toggle",
"args": []
},
"origin": "LOCAL",
"time_fired": "2020-08-20T04:22:23.187561+00:00",
"context": {
"id": "bec98dbae29c11eaabda8592a0fd5882",
"parent_id": null,
"user_id": null
}
}
I tried this configuration
This is what I am seeing, bad_state ?
This is the device info
Any pointers to guide me on the configuration?
Regards,
What Radio are you using?
flashed with Tasmota
I know the Switch is working as I have it set up as an automation, Trigger type event, event type zha_event and works fine.
Anyone know how to solve this without resorting to 3rd party HACS?
I see so many problems with people losing HACS configs during updates I’ve avoided it!
Would really like to see HA properly support events to entities…?
Thanks
You do realise a button press is not an entity, its an event?
In the case of the ZB01 it appears that a short press is a toggle, two press in short succession gives ON and a long press gives us OFF
Use ZHA Event in Automation as a trigger.if you do not want to use third party app.
- id: '1597858866707'
alias: ZHA Button
description: ''
trigger:
- event_data:
command: toggle
device_ieee: 00:12:4b:00:1f:91:92:1f
event_type: zha_event
platform: event
condition: []
action:
- data: {}
entity_id: switch.ceiling_lights
service: switch.toggle
mode: single
Knowing the device_ieee value is there a way to configure the events so that they can be picked by the UI or even modify the device yaml to define them there (that would be best IMHO)
For a HA beginner like myself it is not 100% clear where this automation definition would go, sorry.
M
Ah well, automations.yaml would be the place it seems in case someone else is hunting.
Seems to work, in my case for a Sengled light, but still feels like a hack.
