I just picked up a pair of these from Amazon and they paired as Device. However, they seem to fine using the Generic Zigbee Temperature/Humidity driver, on my C-7.
fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0020,0402,0405,FC57,FC11", outClusters:"0019", model:"SNZB-02D", manufacturer:"SONOFF"
ZCL version:08
@mike.maxwell anything else needed?
I'm curious, does it respond to any of the driver's reporting configurations?
Good Luck!
The left is just a dumb/cheap display.
The middle is the ThirdReality Zigbee sensor (that uses 2xAAA batteries; after 6 months it still reports 100%).
On the right is the SNZB-02D (which uses a CR2450 battery).
Same thing with my 3R temp/humidity sensor.
The only thing that works in that Generic Hubitat System Driver is the temp offset, which I'll probably have to use since it seems to be consistently low wrt my Ecobee thermostat in the same room.
Just got a few myself and discovered more or less the same! It's not clear that they respect the reporting configuration, but I haven't tired re-pairing them in place (with the right driver this time) to see if that changes anything. But the defaults seem good for me regardless. My main concern is battery life, still TBD. 
The SNZB-02 has the weird bug where if you set a reporting schedule min and max to the same value, it will ignore it and only send updates on the delta. @mike.maxwell implemented a workaround where it passes +1 (or -1, i can't remember) seconds to the min or max so they aren't the same value in the default driver. This device may need the same "fix".
The min and max reporting periods should not be the same.
SNZB-02 has an internal measurement cycle time of 10 seconds. So the min reporting period can safely be set to 10 seconds.
A value of 600 seconds for the max reporting period means “send the T/H readings every 10 minutes, even if the change is less than the delta”.
This way the sensor will report periodically the T/H every 10 minutes, but will send an update quickly if the temperature or the humidity changes AND the changed value is greater than the delta.
The default driver was setting min and max to the same value when using the "every XX minutes" options. This caused the SNZB-02 to not send any scheduled updates. For at least this device that behavior was tweaked to set the max value +1 over the min.
Other devices don't seem to mind if min and max is the same (ie min = 300, max = 300). the max takes precedence.
I always remember the min max delta reporting verbiage as "send an update every max seconds OR on delta change, but never more than min seconds".
I have both the SNZB-02 and SNZB-02D on a C8. The generic driver configuration seemed to only allow me to configure a delta, period was not honored. With the Tuya temperature humidity illuminance lcd driver, all parameters (delta, min/max period) are working. The 02 seems to trigger as precise as 0.1 °C, but the 02D seems to step by .2 even when asked for .1 . I also find that it has a slower response time.
The built in Sonoff Zigbee Temperature and Humidity Sensor driver supports time or delta but not both at the same time. Using it with the SN02.
@mike.maxwell Can this fingerprint be added? I just picked up another one of them, and it paired as a Device in 2.3.7.120.
Zigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 38AF 00 00 0000 00 00 0400000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:38AF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[04, 00, 00, 04, 01, 00, 01, 57, FC]]
fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0020,0402,0405,FC57,FC11", outClusters:"0019", model:"SNZB-02D", manufacturer:"SONOFF"
ZCL version:08
Software Build Id:1.0.9
Model:SNZB-02D
Manufacturer:SONOFF
getting info for unknown Zigbee device...
Zigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 38AF 00 00 0000 00 00 0200000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:38AF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[02, 00, 00, 04, 01, 00, 01, 57, FC]]
Zigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 38AF 00 00 0000 00 00 0100000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:38AF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[01, 00, 00, 04, 01, 00, 01, 57, FC]]
Anybody know if that got fixed. Having same problem. Switch the driver to Sonoff H/T and nothing gets reported.
what driver does this work with?
Generic Zigbee Temperature/Humidity
I’m using the built in Sonoff Zigbee Temperature/Humidity Sensor driver for 2 of these and it works fine, but I might have manually selected it, been using it for months now.
Temp, Humidity, and Battery reports fine as far as I know.
FWIW mine are on softwareBuild 1.0.9
Thanks, I'll get this added into the next platform version
I just added this sensor about 30 minutes ago. I had tried both the generic type and the Sonoff type but I was not seeing any data coming across in the logs.
I then learned about and applied the 2.3.8.117 update and set the type to Generic Zigbee Temperature/Humidity Sensor. I am seeing the display on the device update by multiple degrees F but I still don't see anything in the HE logs (both Debug and Description Text logging are Enabled).
Any ideas on how I go from here?
Download the Hubitat app
