Unable to pair Sonoff Zigbee SNZB-01/WB-01 Buttons

[jimford]

I’ve got 2 Sonoff SNB-01 buttons, and neither of them work in HA.

I’ve tried pairing with a Sonoff Bridge flashed with Tasmota, and also a zigbee2mqt USB dongle. They appear to be paired, but in fact are not. The only entities I get are for battery state - but not the switch state. A Sonoff motion sensor and door/window sensor paired and work fine.

(This page:

Zigbee Home Automation

implies that there is a particular way to report issues like this, using a template, but I can’t find a specific page to do so!)
Jim

[francisp (Francis)]

You won’t see a switch. You should listen to the events the button produces.

[jimford]

Thanks fot the reply, Francis.
I’m not sure what you mean. There’s no entity state to listen to, only the battery state entity - ‘eWeLink WB01 4510d61c power’. Maybe I’m misunderstanding the way the button works.

Jim

[meremortal (Jason)]

I think they will need a quirk to work, worst zigbee 3.0 devices seem to need a quirk with ZHA despite them being able to fallback to HA1.2. The developers, and the do a fantastic job, seem to say it’s because the manufacturer doesn’t follow the standard. However, I have zigbee 3.0 certified devices which still need quirks so not sure.

[francisp (Francis)]

Sonoff zigbee button SNZB-01 issue (only in cloud mode)

Go to configuration, automations… create new automation with any name, by trigger select your button name and if you want to use long, double or single click. After that select the acton (for example, to turn off one light). [boton]

[jimford]

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

[jimford]

Thanks Jason - looks like it’s going to be a tough one to crack - and far beyond my skills!
Jim

[meremortal (Jason)]

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.

[aceindy]

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

[meremortal (Jason)]

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.

Samsung Smarthings Button

Walked into Best Buy today and they had the Samsung Smarthings Button on sale for $14.99. I have been wanting a button to run different automation’s or scripts in each room for a while. This button paired with zha out of the box and has a temp sensor. At first I tried to do a standard automation using the binary sensor, but the switch would only show on no matter if I did press, double press, or hold. Started looking on the forum and found a couple of post that got close but no cigar. Then …

[jimford]

I sorted my problem out - see this post, it may help:

Help with parsing zha_event with switch node

I’ve got a Sonoff SNZB-01 button, which on a single click outputs: { "event_type": "zha_event", "data": { "device_ieee": "00:12:4b:00:1c:d6:0f:66", "unique_id": "00:12:4b:00:1c:d6:0f:66:1:0x0006", "endpoint_id": 1, "cluster_id": 6, "command": "toggle", "args": [] }, "origin": "LOCAL", "time_fired": "2020-08-15T15:19:19.567805+00:00", "context": { "id": "b0b71de5df0a11ea9377b72c061ccbbc", "parent_id": null, …

Jim

[meremortal (Jason)]

There is a HACS add on to turn an event into a sensor.

azogue/eventsensor

Jason

[jimford]

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

[MarkB1 (Mark Booth)]

Hi,
How did you get this far, I have tried

and get nothing?

[jimford]

I recommend that you try Node Red, - it’s very much easier.
Jim

[MarkB1 (Mark Booth)]

@meremortal

There is a HACS add on to turn an event into a sensor.

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,

[meremortal (Jason)]

What Radio are you using?

[MarkB1 (Mark Booth)]

ZBBridge - SONOFF Official

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.

[MarkB1 (Mark Booth)]

Sorted

works like a charm, thanks to the Author Eugenio.

[dougle03 (Peter Kay)]

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