Sonoff SNZB-01 Button with beta Zigbee Button driver

Devices & Integrations
41

the only reason i was asking is i ave just tried the driver and it still isnt working if i knew the driver version number i could check i had the updated driver.
thanks
martin

42

I use the beta channel and the version is now 2022-09-06T18:49:01.843782918. The previous version started 2022-08-23 …

Only one of my two versions has received the new version so far (but I’ve just dealt with that using the CLI).

1 Like
43

thanks ,
ive only just noticed it has the date lol
its working fine now .

44

Hello @nayelyz

The buttons seemed to work fine for several tests of routines tied to press and double press yesterday afternoon, but when I went to use them today they are not working again. The button press is observed in the ST App but the routines are not firing. I also just noticed that button presses are only intermittently making it into the devices “History”.

45

Please, help us compare if the events from the buttons are being received in the driver by getting the driver’s logs.

For this, you need to install the SmartThings CLI and run the following command:

smartthings edge:drivers:logcat --hub-address=x.x.x.x

Note: Remember to replace x.x.x.x with the Hub’s IP address that you can see in the IDE or your router’s configuration. The CLI will ask you to enter the number of the list that belongs to the driver. You can also use the flag --all to see the logs of all drivers.

46

Additional info while I was gathering logs.

The button is used in two routines as follows:

  1. Single push - turn OFF SHM (Disarmed)
  2. Double push - turn ON SHM (Armed - Stay)

Scenarios:

  1. SHM is turned on manually using ST app. Pushing button once does NOT turn off SHM.
2022-09-09T00:54:56.633560066+00:00 TRACE Zigbee Button  Received event with handler zigbee
2022-09-09T00:54:56.643809605+00:00 INFO Zigbee Button  <ZigbeeDevice: d8295c52-7fca-4436-9620-59bca50233ec [0xCCD6] (Arm Disarm Button)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xCCD6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x7C, rssi: -69, body_length: 0x0003, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x3F, ZCLCommandId: 0x02 >, < Toggle ||  > > >
2022-09-09T00:54:56.663295191+00:00 TRACE Zigbee Button  Found ZigbeeMessageDispatcher handler in zigbee_button -> eWeLink Button
2022-09-09T00:54:56.668611865+00:00 INFO Zigbee Button  Executing ZclClusterCommandHandler: cluster: OnOff, command: Toggle
2022-09-09T00:54:56.674891723+00:00 INFO Zigbee Button  <ZigbeeDevice: d8295c52-7fca-4436-9620-59bca50233ec [0xCCD6] (Arm Disarm Button)> emitting event: {"attribute_id":"button","capability_id":"button","component_id":"main","state":{"value":"pushed"}}
2022-09-09T00:54:56.758866381+00:00 DEBUG Zigbee Button  Sonoff Button 2 device thread event handled
  1. SHM is turned on by a different routine. Pushing button once does NOT turn of SHM.
2022-09-09T00:59:25.487992836+00:00 TRACE Zigbee Button  Received event with handler zigbee
2022-09-09T00:59:25.498677503+00:00 INFO Zigbee Button  <ZigbeeDevice: d8295c52-7fca-4436-9620-59bca50233ec [0xCCD6] (Arm Disarm Button)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xCCD6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x50, rssi: -80, body_length: 0x0003, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x40, ZCLCommandId: 0x02 >, < Toggle ||  > > >
2022-09-09T00:59:25.518984169+00:00 TRACE Zigbee Button  Found ZigbeeMessageDispatcher handler in zigbee_button -> eWeLink Button
2022-09-09T00:59:25.524949169+00:00 INFO Zigbee Button  Executing ZclClusterCommandHandler: cluster: OnOff, command: Toggle
2022-09-09T00:59:25.537714836+00:00 INFO Zigbee Button  <ZigbeeDevice: d8295c52-7fca-4436-9620-59bca50233ec [0xCCD6] (Arm Disarm Button)> emitting event: {"attribute_id":"button","capability_id":"button","component_id":"main","state":{"value":"pushed"}}
2022-09-09T00:59:25.564389169+00:00 DEBUG Zigbee Button  Sonoff Button 2 device thread event handled
  1. SHM is off. SHM is successfully turned ON by button double push. Pushing buttone once then successfully turns OFF SHM. This log shows the double press (SHM On) followed by the single press (SHM Off).
2022-09-09T01:01:56.354173241+00:00 TRACE Zigbee Button  Received event with handler zigbee
2022-09-09T01:01:56.363277241+00:00 INFO Zigbee Button  <ZigbeeDevice: d8295c52-7fca-4436-9620-59bca50233ec [0xCCD6] (Arm Disarm Button)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xCCD6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x68, rssi: -74, body_length: 0x0003, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x41, ZCLCommandId: 0x01 >, < On ||  > > >
2022-09-09T01:01:56.381323241+00:00 TRACE Zigbee Button  Found ZigbeeMessageDispatcher handler in zigbee_button -> eWeLink Button
2022-09-09T01:01:56.386689908+00:00 INFO Zigbee Button  Executing ZclClusterCommandHandler: cluster: OnOff, command: On
2022-09-09T01:01:56.392913908+00:00 INFO Zigbee Button  <ZigbeeDevice: d8295c52-7fca-4436-9620-59bca50233ec [0xCCD6] (Arm Disarm Button)> emitting event: {"attribute_id":"button","capability_id":"button","component_id":"main","state":{"value":"double"}}
2022-09-09T01:01:56.412030575+00:00 DEBUG Zigbee Button  Sonoff Button 2 device thread event handled
2022-09-09T01:02:10.583455581+00:00 TRACE Zigbee Button  Received event with handler zigbee
2022-09-09T01:02:10.592472581+00:00 INFO Zigbee Button  <ZigbeeDevice: d8295c52-7fca-4436-9620-59bca50233ec [0xCCD6] (Arm Disarm Button)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xCCD6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8C, rssi: -65, body_length: 0x0003, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x42, ZCLCommandId: 0x02 >, < Toggle ||  > > >
2022-09-09T01:02:10.610245581+00:00 TRACE Zigbee Button  Found ZigbeeMessageDispatcher handler in zigbee_button -> eWeLink Button
2022-09-09T01:02:10.615532915+00:00 INFO Zigbee Button  Executing ZclClusterCommandHandler: cluster: OnOff, command: Toggle
2022-09-09T01:02:10.621977248+00:00 INFO Zigbee Button  <ZigbeeDevice: d8295c52-7fca-4436-9620-59bca50233ec [0xCCD6] (Arm Disarm Button)> emitting event: {"attribute_id":"button","capability_id":"button","component_id":"main","state":{"value":"pushed"}}
2022-09-09T01:02:10.641135915+00:00 DEBUG Zigbee Button  Sonoff Button 2 device thread event handled
2022-09-09T01:02:14.107827916+00:00 DEBUG Zigbee Button  driver device thread event handled

FWIW - With the DTH the button could successfully turn off SHM regardless of how it was turned on and could always successfully turn it on from being off.

Thanks!!

47

I don’t know what is going on but those logs aren’t showing the state_change set to true as the fixed driver should.

48

The driver version is listed in the ST app as 2022-09-06T18.43.46.315616255.

I played with it for a while more last night and its very repeatable. If the button turns SHM on it can then always turn it off. I can do on/off many times and it always works. But if SHM is turned on via another routine or manually in the App, the button can never turn it off. Weird, huh? :slight_smile:

49

So built around the same time but not the same version. I think you are using the driver version from the default channel (aka ‘production’) which hasn’t had the fixes applied yet. @nayelyz just a heads up, the fix is only in the beta channel, the production version is still busted.

There are only three active fingerprints in the production Zigbee Button driver. One is the SmartSense button and the other two are for this button. Bizarrely they seemed to have been added about two days after it entered beta a month ago, which seems rather premature. I wonder if that was unintentional.

50

I’m sure you’re right! When I saw the driver date change from 08-23 to 09-06 I just assumed that the fix had been migrated to production. I think @nayelyz must have thought the same when she asked us to verify that it was now working. I really appreciate you’re pointing this out!

51

Thank you both, @orangebucket, @ktdt00
I already mentioned this to the engineering team. I’ll let you know their feedback.

52

Hi, @ktdt00!
I sent you a DM to get some information the engineering team requested. Please, help us by checking the message.

53

Hi,

I’m trying to utilise the new Edge driver with my SNZB01, but cannot get it to discover as anything other than a “Thing”. If I install the Zigbee Thing driver, it detects as that instead but I have tried the Zigbee Button from the official Edge driver set, the RDG and now the one in this thread. None of them seem to work. Any ideas? I don’t have any button related DTH in the graphical interface. Device list from command line is as follows:

─────────────────────────────────────────────────────────────────────────────────────────────────────

Label Name Type Device Id

─────────────────────────────────────────────────────────────────────────────────────────────────────
1 Bob’s iPhone iPhone MOBILE 197d0f5d-f657-47b9-9c0c-a0d8fd1bd1c5
2 BookCase basic-switch ZIGBEE 95cdfb9f-035d-4ff2-8b2d-32207f508835
3 Callum Callum DTH b32a5117-144d-4848-964b-fcc51ccac4bc
4 Callum’s Desk Lamp basic-switch ZIGBEE 560c731d-9ea8-4f61-b551-b50081b2c696
5 Coffee Plinth basic-switch ZIGBEE a582ace2-298c-4d0f-b8f4-39915a131bee
─────────────────────────────────────────────────────────────────────────────────────────────────────
6 Conservatory sensibo-airconditioner-1 VIPER a6455f96-19ee-40d5-acd9-9fe09e9f6c3d
7 Conservatory Door eWeLink Open/Closed Sensor DTH c7d2db5c-3c3e-480f-b15a-6034e13ea430
8 Conservatory Lamp SONOFF Outlet DTH 5a1382f7-805f-43a1-a8a0-0afb244fe89e
9 Cooker Hood basic-switch ZIGBEE aed93388-0444-498f-95ba-0c0b914b5a52
10 Dad Dad DTH f92ef25e-6a89-4ddc-a326-13d2024db143
─────────────────────────────────────────────────────────────────────────────────────────────────────
11 Danalock Door Lock lock-battery ZIGBEE 08a2498e-e6da-4955-8ab8-fb1363fbeca5
12 Doorbell Switch Doorbell Switch DTH 9b05d595-cc7a-4995-af3b-5293d2f84445
13 Exterior Temperature eWeLink Multipurpose Sensor ZIGBEE bded5d2b-0963-4377-a15d-206663a51b98
14 Front Door Sensor eWeLink Open/Closed Sensor DTH c4d3ee31-dd39-4fb4-afd2-a8c20fb81755
15 Front LEDs SONOFF Outlet DTH 63c21b79-aea4-48eb-8e9a-70ffeb0e5fd5
─────────────────────────────────────────────────────────────────────────────────────────────────────
16 Hall Lamp SONOFF Outlet DTH 2d081d71-6bc2-40b5-81fc-43cb087af9f8
17 Jamie Jamie DTH ba07a562-b195-4141-952b-6bc74ad9dde7
18 Kitchen Door Sensor eWeLink Open/Closed Sensor DTH 09a5cc97-d649-468d-9589-86987c58bf76
19 lounge door eWeLink Open/Closed Sensor DTH a036844b-b0be-4ae8-8300-93899ba8ca07
20 Lounge Lamp SONOFF Outlet DTH 680ce64b-d745-4c86-991a-909e8259a61b
─────────────────────────────────────────────────────────────────────────────────────────────────────
21 Lounge Lamp 3 SONOFF Outlet DTH c3e65e38-ee5f-4579-a6fd-2018daeb3847
22 Luke Luke DTH 4e230a98-f22d-4157-ba32-7591352b56a7
23 Main Bedroom sensibo-airconditioner-1 VIPER 80a1f51f-bedd-4f1a-b767-a58acdefc33c
24 Mum Mum DTH 40a268c4-cc76-4813-b3ec-ef57d07851e2
25 Office Ceiling Light SONOFF 01MINIZB DTH dbbae824-1ddd-4f4b-851c-28ad240788a7
─────────────────────────────────────────────────────────────────────────────────────────────────────
26 SmartThings Hub SmartThings v3 Hub HUB 32088b3d-260d-41a6-8dd4-e04a65186812
27 Temperature eWeLink Multipurpose Sensor ZIGBEE 512933d8-8c6a-4ac8-9bc2-5dc4e12af7de
28 Thing Thing DTH 75c4f8a8-aa55-4d31-b339-a4070813ca45
─────────────────────────────────────────────────────────────────────────────────────────────────────

54

Mine are all working fine with the Zigbee Button from the beta channel and the button seems to be in the fingerprints for the production channel.

Mine all identify with the manufacturer eWeLink and the model WB01 but they apparently can also identify with the same manufacturer and the model SNZB-01P, or at least that is what was in the DTH and is now in the Edge drivers.

Have you checked yours? You should be able to see the deviceManufacturerCode and deviceModel if you view the device in the CLI with the -j or -y option.

55

Thanks for the info, I’m a bit new to the whole Smartthings Edge thing, only got involved when things stopped working. My button identifies as a eWelink WB-01, but has a DTH entry as Thing. Complete output below:
deviceId: 75c4f8a8-aa55-4d31-b339-a4070813ca45
name: Thing
label: Thing
deviceManufacturerCode: eWeLink
manufacturerName: SmartThings
deviceModel: WB-01
presentationId: SmartThings-smartthings-Thing
locationId: a7921afa-3cb6-4150-b6bd-be6b65a2ba54
sharedLocations:
components:

  • id: main
    capabilities:
    categories:
    • name: Other
      categoryType: manufacturer
      createTime: ‘2022-10-21T15:24:48.965Z’
      parentDeviceId: 32088b3d-260d-41a6-8dd4-e04a65186812
      dth:
      completedSetup: true
      deviceNetworkType: ZIGBEE
      deviceTypeId: 0144b700-9df5-4f06-9bfe-7a5d056b8aac
      deviceTypeName: Thing
      executingLocally: false
      hubId: 32088b3d-260d-41a6-8dd4-e04a65186812
      networkSecurityLevel: UNKNOWN
      type: DTH
      vid: SmartThings-smartthings-Thing
      mnmn: SmartThings
      restrictionTier: 0
      allowed:

Not sure what’s going on. I’ve removed from the app, removed from the IDE, everytime it redetects the same.

56

If the deviceModel is indeed the same thing as the model used in the fingerprints then that would be the problem. The drivers are for the WB01, you have a WB-01 so there isn’t a match.

1 Like
57

@nayelyz Hi, is this something you can help with? Appears my button must be a different revision and has a hyphen in the model name (WB-01 as opposed to WB01). Can this be added to the fingerprints?

1 Like
58

Mine as well, IMO it will work fine if the WB-01 is added to the fingerprints.

59

Sorry for the delay, the fingerprints that appear in the driver belong to certified devices, so, if the manufacturer doesn’t put the device through this process it can’t be added to the official Driver.
Did this device worked correctly with a stock DTH?

60

Yes it did, although it had to be added twice for some reason. It seems an oversight, maybe with a firmware version, that this button has a hyphen in the name, while being materially the same as the WB01.