SONOFF Zigbee Human Presence Sensor | SNZB-06P

Presence Detection】 SNZB-06P based on 5.8GHz microwave radar, it can detect movement or stationary person. It automatically turns on the lights when you approach and keeps the lights on until you leave.
【Light Sensing】 The built-in light detector ensures that the lights are only turned on when presence is detected in the dark, helping you save energy.
【Zigbee 3.0 Compatible】 Supports Zigbee hubs using the Zigbee 3.0 protocol, like [SONOFF NSPanel Pro]SNZB-06P), and Echo Plus 2nd…
【Local Smart Scene】 Scene linkage between Zigbee devices can be executed normally even if there is no internet connection.
【Support Multiple Platforms】 Supporting Alexa, Google Home, Smartthings, Alice, IFTTT, and Home Assistant.

1 Like

Is there a driver for Hubitat? Will it work on C7 and lower? Typically Sonoff works well with Hubitat, kind of the generic standard.

It may be working out of the box using the HE inbuilt Generic Zigbee Motion Sensor (no temp) driver.

Always on power? Still want one

This almost certainly works with HE's generic zigbee driver.

I am very curious to see how such a complex sensor will perform, without any possibilities to configure the radar sensitivity and the maximum detection distance.

1 Like

From the videos I have seen, the configuration is very simple and the sensor releases in 30 seconds when you leave the zone.

How is the radar sensitivity configured?

In the same e-welink app, I saw an idea where you configure it in home asssit and it does not have to configure the sensitivity. Compared to the Aqara one, this sensor is simpler, it only detects one object and the release takes 30 seconds.

3 Likes

If the radar sensitivity can be configured from the eWeLink app, it should be possible to do the same in Hubitat.

The aqara comparison is true, however the fp2 costs quite a lot more, and if you don't need multiple person detection and want just to trigger lights or whatnot, this one might be very worth it.

2 Likes

Enable the Debug logs, then pair the device once again.
Can you post the debug logs that follow the pairing process ?

Not currently working with the Zigbee motion (no temp) driver.

1 Like

Anything in the live logs?

Sorry, how do I enable debug logs?

From the preferences section:

dev:2832023-10-20 09:41:37.174 AMdebugdescMap:[raw:catchall: 0000 0006 00 00 0040 00 038C 00 00 0000 00 00 0500000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[05, 00, 00, 04, 01, 00, 01, 57, FC]]
dev:2832023-10-20 09:41:33.627 AMdebugdescMap:[raw:catchall: 0000 0006 00 00 0040 00 038C 00 00 0000 00 00 0400000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[04, 00, 00, 04, 01, 00, 01, 57, FC]]
dev:2832023-10-20 09:41:32.619 AMdebugskipped:[raw:catchall: 0104 0001 01 01 0040 00 038C 00 00 0000 01 01 200086, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[20, 00, 86]]
dev:2832023-10-20 09:41:32.616 AMdebugdescMap:[raw:catchall: 0104 0001 01 01 0040 00 038C 00 00 0000 01 01 200086, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[20, 00, 86]]
dev:2832023-10-20 09:41:32.213 AMdebugdescMap:[raw:catchall: 0104 0001 01 01 0040 00 038C 00 00 0000 0B 01 0681, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 81]]
dev:2832023-10-20 09:41:31.810 AMdebugdescMap:[raw:catchall: 0000 8021 00 00 0040 00 038C 00 00 0000 00 00 1C00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[1C, 00]]
dev:2832023-10-20 09:41:31.409 AMdebugdescMap:[raw:catchall: 0104 0001 01 01 0040 00 038C 00 00 0000 0B 01 0681, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 81]]
dev:2832023-10-20 09:41:31.007 AMdebugdescMap:[raw:catchall: 0000 8021 00 00 0040 00 038C 00 00 0000 00 00 1A00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[1A, 00]]
dev:2832023-10-20 09:41:28.955 AMdebugdescMap:[raw:catchall: 0000 0006 00 00 0040 00 038C 00 00 0000 00 00 0200000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[02, 00, 00, 04, 01, 00, 01, 57, FC]]
dev:2832023-10-20 09:41:26.978 AMdebugdescMap:[raw:catchall: 0104 0500 01 01 0040 00 038C 00 00 0000 04 01 00, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]
dev:2832023-10-20 09:41:26.849 AMdebugdescMap:[raw:catchall: 0000 0013 00 00 0040 00 038C 00 00 0000 00 00 818C03711CD2FEFF20BA848E, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:038C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[81, 8C, 03, 71, 1C, D2, FE, FF, 20, BA, 84, 8E]]
dev:2832023-10-20 09:41:26.600 AMwarnconfigure...
dev:2832023-10-20 09:40:57.947 AMdebugdescMap:[raw:catchall: 0000 0006 00 00 0040 00 968F 00 00 0000 00 00 060000FFFF01250000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:968F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[06, 00, 00, FF, FF, 01, 25, 00, 00]]
dev:2832023-10-20 09:40:45.809 AMwarndescription logging is: true
dev:2832023-10-20 09:40:45.807 AMwarndebug logging is: true
dev:2832023-10-20 09:40:45.805 AMinfoupdated...
dev:2832023-10-20 09:22:36.786 AMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0406,0500,FC57,FC11", outClusters:"0003,0019", model:"SNZB-06P", manufacturer:"SONOFF"
dev:2832023-10-20 09:22:36.674 AMtraceZCL version:03
dev:2832023-10-20 09:22:36.672 AMtraceSoftware Build Id:1.0.3
dev:2832023-10-20 09:22:36.669 AMtraceModel:SNZB-06P
dev:2832023-10-20 09:22:36.667 AMtraceManufacturer:SONOFF
dev:2832023-10-20 09:22:36.482 AMdebuggetting info for unknown Zigbee device...
dev:2832023-10-20 09:22:33.663 AMinfoZigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 968F 00 00 0000 00 00 0500000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:968F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[05, 00, 00, 04, 01, 00, 01, 57, FC]]
dev:2832023-10-20 09:22:30.505 AMinfoZigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 968F 00 00 0000 00 00 0200000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:968F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[02, 00, 00, 04, 01, 00, 01, 57, FC]]
dev:2832023-10-20 09:22:26.460 AMdebuggetting device info in 10 seconds...

EDIT:

Did you pair the device again to the hub, or just changed the driver?

Paired it again with the hub.

1 Like

Please check again if you have actually changed the driver manually :
image

The logs above look like being from the Device driver ... ?

1 Like