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

Tags: #<Tag:0x00007f7398bc7308> #<Tag:0x00007f7398bc71c8> #<Tag:0x00007f7398bc70d8> #<Tag:0x00007f7398bc7010>

Hello, I have two zigbee SNZB-01 (using Sonoff LAN integration on HACS), one is on the same LAN, connected to Home Assistant directly (with a CC2531) and it works just fine, I control 3 different devices with single click, double click and long lasting click.

Another SNZB-01 is connected on the cloud, trough a sonoff zigbee bridge, and HA considers it not a device, just a binary_sensor… so I cant use double click or long lasting click, It’s just “on” and “off”… and it takes ages (sometimes 3-4 minutes) since the click to change state.

I see the problem is not the button since when its connected on the same LAN it works like charm, just like the first button.

Any ideas?

@mabusdogma
I take this opportunity because I am just looking for how to do the programming of zigbee smart switch. in HA or Node-Red ?, because i just see power entity

“it works just fine, I control 3 different devices with single click, double click and long lasting click.”
how you do it ?

thank you

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).

ok , but on your entity do you see more think then just de power (battery entity)lke on de red cercle i think is my problem , i have no choise to turn on , off or toggle , did you ?

thank so much for your reply

Yes, you should see more. Do you have installed HACS and the Sonoff integration?
You need it in order to see and control everything.

Another thing, the ZigBee switch power should be on the same LAN of home assistant…

I actually resolve my own original problem: being not on LAN but in the cloud, makes your devices to lose some features.

yes i have hacs and sonoff alexitt intergration with more 50 devices, but I had some problem i the pass with de zigbee bridge in ewelink like de scenario won’t stay on or the device lost the name.
So i all ready flash with tasmota and Zha in HA
Now i have this zigbee devices : 3 motion , 1 BASICZBR3 , 3 TH-01 all work great but my 4 snzb-01 smart switch just give me the battery sensor(or power).
install … reintall … restart and restart :smile: .

this is my log went i log de devices :

command 2 double clic
command 1 for clic
command 0 for long press

If you or somebody else have solution it will be great after 3 day of research

1 Like

Here is the continuation of my investigation, I have a blank version of HA aside on another computer, I also have a zigbee cc2531 dongle key, which I tested and unfortunately without success … I use Zha and not zigbee2mqtt and you?

I use zigbee2mqtt and no tasmota but the original software.

Mmm maybe it could be the zha or the tasmota, it looks different

1 Like

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. 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.
Jim

3 Likes

Ok i tested on zigbee2mqtt with my dongle USB and it WORK wow , after connecting i clic single , double , long press and zigbee2mqtt Fund de code. So my switch is not broken.

Try to continue to research solution for ZHA. Thank

1 Like

So here is the way I have found to have all my devices in HA for now, I am using the sonoff dongle key, for the 4 switches and the BASICZBR3 To try to extend the network with zigbee2mqtt.
And I use the zonoff zigbee bridge with tasmota for all the rest of the devices since its signal is strong And device setup is easy.
so i have 2 network , i think is not the best way to do it but …

Weird thing that happened, I have a TH-01 which is broken on my desk the switch to activate the network search is broken but the battery was still inside. with Zha I had tried to activate it by removing and re-inserting the battery sometimes and without success, but when I installed zigbee2mqtt it was detected automatically, I am very happy.

@jimford
I also had the problem sometimes when trying with zigbee2mqtt here is how I succeeded with the four switches.
Remove device in mqtt.
Remove the battery.
Restart the ad-on zigbee2mqtt.
Replace the battery. And activate the pairing mode
it work for me , took me sometimes three or four times before I got the button as well as the signal, the battery still extends present.

I also have the same issue with the wi-fi switches SNZB-01. Other devices - the temp and humidity sensor TH-01, and the motion sensor SNZB-03 are working fine.

I have a tasmota based sonoff zigbee bridge. Running Hassio V4.12

Here is a part of the logfile. Somehow it seems the SNZB-01 just does not install properly.

2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0000] Attribute id: 4 value: eWeLink
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0000] Attribute id: 5 value: TH01
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0000] Attribute id: 4 value: eWeLink
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0000] Attribute id: 5 value: MS01
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0000] Attribute id: 4 value: eWeLink
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0000] Attribute id: 5 value: TH01
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0xbef7:1:0x0000] Attribute id: 4 value: eWeLink
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0xbef7:1:0x0000] Attribute id: 5 value: WB01
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for None None (60:a4:23:ff:fe:1d:bc:bf)
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Found custom device replacement for 60:a4:23:ff:fe:1d:bc:bf: <class 'bellows.zigbee.application.EZSPCoordinator'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for eWeLink TH01 (00:12:4b:00:1f:84:1e:4d)
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {11, 13} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.lutron.lzl4bwhl01remote.LutronLZL4BWHL01Remote2'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because profile_id mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.osram.a19twhite.A19TunableWhite'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {3} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rom001.PhilipsROM001'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rwl020.PhilipsRWL020'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {1, 2} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rwl021.PhilipsRWL021'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {1, 2} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for eWeLink MS01 (00:12:4b:00:1f:90:cd:e4)
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {11, 13} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.lutron.lzl4bwhl01remote.LutronLZL4BWHL01Remote2'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because profile_id mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.osram.a19twhite.A19TunableWhite'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {3} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rom001.PhilipsROM001'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rwl020.PhilipsRWL020'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {1, 2} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rwl021.PhilipsRWL021'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {1, 2} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for eWeLink TH01 (00:12:4b:00:1f:84:e0:96)
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {11, 13} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.lutron.lzl4bwhl01remote.LutronLZL4BWHL01Remote2'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because profile_id mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.osram.a19twhite.A19TunableWhite'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {3} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rom001.PhilipsROM001'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rwl020.PhilipsRWL020'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {1, 2} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rwl021.PhilipsRWL021'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {1, 2} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for eWeLink WB01 (00:12:4b:00:1f:91:56:88)
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {11, 13} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.lutron.lzl4bwhl01remote.LutronLZL4BWHL01Remote2'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because profile_id mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.osram.a19twhite.A19TunableWhite'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {3} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rom001.PhilipsROM001'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rwl020.PhilipsRWL020'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {1, 2} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.rwl021.PhilipsRWL021'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {1, 2} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor'>
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0000] Attribute id: 4 value: eWeLink
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0000] Attribute id: 5 value: TH01
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0000] Attribute id: 7 value: 3
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0000] Attribute id: 4 value: eWeLink
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0000] Attribute id: 5 value: MS01
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0500] Attribute id: 1 value: 13
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0500] Attribute id: 2 value: 1
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0500] Attribute id: 0 value: 0
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0000] Attribute id: 7 value: 3
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0001] Attribute id: 32 value: 32
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0001] Attribute id: 33 value: 200
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0000] Attribute id: 4 value: eWeLink
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0000] Attribute id: 5 value: TH01
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0000] Attribute id: 7 value: 3
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0001] Attribute id: 32 value: 32
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0001] Attribute id: 33 value: 200
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0001] Attribute id: 32 value: 32
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x3846:1:0x0001] Attribute id: 33 value: 200
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0402] Attribute id: 0 value: 2033
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0xbef7:1:0x0000] Attribute id: 4 value: eWeLink
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0xbef7:1:0x0000] Attribute id: 5 value: WB01
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0xbef7:1:0x0001] Attribute id: 32 value: 41
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0xbef7:1:0x0001] Attribute id: 33 value: 200
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x42d4:1:0x0405] Attribute id: 0 value: 6206
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0402] Attribute id: 0 value: 2340
2020-09-01 14:41:53 DEBUG (MainThread) [zigpy.appdb] [0x94ee:1:0x0405] Attribute id: 0 value: 5221
type or paste code here
1 Like

Can you share steps to run zigbe2mqtt with the original software? I stucked on running it:

Zigbee2MQTT:info  2020-09-08 18:43:48: Starting Zigbee2MQTT version 1.14.4 (commit #unknown)

Zigbee2MQTT:info  2020-09-08 18:43:48: Starting zigbee-herdsman...
Zigbee2MQTT:error 2020-09-08 18:43:48: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-09-08 18:43:48: Failed to start zigbee
Zigbee2MQTT:error 2020-09-08 18:43:48: Exiting...
Zigbee2MQTT:error 2020-09-08 18:43:48: Error: Error while opening serialport 'Error: Error: No such file or directory,

I also have this issue. I have:

  • SNZB-03 (motion sensor)
  • SNZB-02 (temperature sensor)
  • SNZB-04 (door sensor)

and they all work fine but…

the SNZB-01 (wireless switch) was easy to add to my Zigbee integration, but does not show the button state, only the battery state.

That’s normal ‘danielmurtagh’.
For reasons I don’t understand, an entity is not created as such for the motion sensor. To use the sensor you need to monitor the event bus for a zha-event produced by the button.
Here’s a Node-RED flow that I created to test a button:

[{"id":"be4429a7.7b2b3","type":"tab","label":"Flow 4","disabled":false,"info":""},{"id":"3a6725d4.62d622","type":"switch","z":"be4429a7.7b2b3","name":"","property":"payload.event.command","propertyType":"msg","rules":[{"t":"eq","v":"toggle","vt":"str"},{"t":"eq","v":"on","vt":"str"},{"t":"eq","v":"off","vt":"str"}],"checkall":"true","repair":false,"outputs":3,"x":270,"y":300,"wires":[["85ee1c58.53547"],["61570751.41b5d"],["3a5eeed8.15850a"]]},{"id":"46fd050.9989afc","type":"server-events","z":"be4429a7.7b2b3","name":"Button","server":"93de20d5.59f72","event_type":"zha_event","exposeToHomeAssistant":false,"haConfig":[{"property":"name","value":""},{"property":"icon","value":""}],"x":70,"y":200,"wires":[["4c499f2f.00b788"]]},{"id":"61570751.41b5d","type":"api-call-service","z":"be4429a7.7b2b3","name":"Effect 2","server":"93de20d5.59f72","version":1,"debugenabled":false,"service_domain":"light","service":"turn_on","entityId":"light.lohas_bulb2","data":"{\"effect\":4,\"profile\":\"relax\"}","dataType":"json","mergecontext":"","output_location":"","output_location_type":"none","mustacheAltTags":false,"x":480,"y":300,"wires":[[]]},{"id":"85ee1c58.53547","type":"api-call-service","z":"be4429a7.7b2b3","name":"Red","server":"93de20d5.59f72","version":1,"debugenabled":false,"service_domain":"light","service":"turn_on","entityId":"light.lohas_bulb2","data":"{\"color_name\": \"red\"}","dataType":"json","mergecontext":"","output_location":"","output_location_type":"none","mustacheAltTags":false,"x":470,"y":220,"wires":[[]]},{"id":"3a5eeed8.15850a","type":"api-call-service","z":"be4429a7.7b2b3","name":"Off","server":"93de20d5.59f72","version":1,"debugenabled":false,"service_domain":"light","service":"turn_off","entityId":"light.lohas_bulb2","data":"","dataType":"json","mergecontext":"","output_location":"","output_location_type":"none","mustacheAltTags":false,"x":470,"y":380,"wires":[[]]},{"id":"4c499f2f.00b788","type":"switch","z":"be4429a7.7b2b3","name":"Button 2","property":"payload.event.unique_id","propertyType":"msg","rules":[{"t":"eq","v":"00:12:4b:00:1c:d6:10:45:1:0x0006","vt":"str"}],"checkall":"true","repair":false,"outputs":1,"x":120,"y":300,"wires":[["3a6725d4.62d622"]]},{"id":"93de20d5.59f72","type":"server","z":"","name":"Home Assistant","legacy":false,"addon":true,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":false,"cacheJson":true}]

(I thoroughly recommend that you use node-red. I find it far easier to use than YAML, with its paranoid indentation!)
Jim

Yes after a bit of research it is as Jim says. There is no entity.

The reason (I think) it is not an entity is that it has no defined state ie there is nothing “set” on the switch. It is a momentary press (or long press) which generates an event. You can do whatever you want with that event to trigger actions that change the state of other entities. After you release the switch though the SNZB-01 is not in any different state to what it was before. I think that is why it is not an entity. Here is how to use it in HA:

How did you pair the SNZB-04? It won’t pair with my bridge

Hi tc23,

I followed this Dr Zzs video: https://www.youtube.com/watch?v=xc_HGvrOxp8 and didnt have any major issues.

The pairing button can be a little tricky to access, so you may need to open up the box and remove the circuit board so you can access the button.

Also, Zigbee pairing can sometimes be a little temperamental so you might need to attempt to pair a few times before its successful. Also important to have the device as close as possible to your Zigbee bridge.

Hi @jimford and @pgv

Thanks very much for that information, it totally makes sense and I have now set up an event bus monitor and triggers based on Jim’s example and its working perfectly for my 8x sonoff zigbee switches!

Thanks for taking the time to share your knowledge.

Daniel.

Thanks @danielmurtagh, thats what finally did the trick was taking the panel off so I could see the led flash. Got it paired, although it came in as an unknown manufacturer, which doesn’t matter since I renamed it. Very impressed with the tasmota’d zigbee bridge. Have it in my basement and the door sensor on my third floor and its reacting perfectly with no other zigbee repeaters in the middle