I had a tuya presence sensor working for months, then it stopped, so I removed it.
Now I've installed a Sonoff SNZB-06P
But I can't get it working. Only shows active.
Do I have the correct device type and device profile?
I've tried installing the original tuya zigbee sensor then tuya zigbee mmwave battery sensor and now the sonoff.... I am lost. Have no idea what happened.
Just noticed on "Compatible device list" source= user. Not sure what that means.
Hi Art,
You have the correct driver, and the correct 'DeviceProfile' selected automatically.
These Sonoff SNZB-06P sensors are known to be too much sensitive. Please see a similar case from the last days :
Where is your sensor installed? Anything around (not only in front, but also at back of the sensor) that may trigger it ?
It seems to be working now. I'll keep testing and add rules to dim cabinet lighting.
That's weird, just started working. I'll let you know how it goes...
And thanks, I'm sorry to keep bothering you.
No problem, Art!
These mmWave sensors are rather complex and difficult to configure devices, if compared to the traditional PIR sensors. I suppose they have some internal automatic calibration algorithm built in, and it takes some time to settle.
I just noticed this. I set Radar Sensitivity to 1 low. When I hit reset it goes back to 2 med.
Did you set it in the "Commands" section or "Preferences" section of the device page?
Setting it in the Preferences section is the only way to set a persistent setting. Setting it in Commands is just a one-time command -- it will reset back to the Preferences setting upon refresh.
I thought I did that, evendently I didn't.
Thanks
Hey KKossev, again thank you for all you do to support the community! I have a Sonoff SNZB-06P i just tried to install and test. I have your current 3.5.1 driver in use, configured with the Sonoff SNZB-06P device profile selected. I loaded the defaults and the device is responding to pings just fine. NMW the motion state never changes from inactive. Any advice would be appreciated! Joe
It appears to be reporting lumens properly, fyi jj
Correction, lumens is reporting 'null', j
Did you try pairing the device again close to your hub (without deleting it)?
If it still don’t work after re-pairing, enable the Debug logging, then remove the USB power for 30 seconds and power it back again. Anything in the live logs after the power on?
(This device does not report lumens, but only a binary ‘dark’/‘light’ state)
Bummer on the dark light state, FYI i have a TS0225_LINPTECH_RADAR and i ordered the Sonoff to replace it. It worked on both lumens and your driver, but just false reported motion all the time NMW how I adjusted the config.. is there a MM radar you like that does both? Thank you and I will go pull the data you asked for. jj
Paired again, unplugged waited 30 seconds, powered up and here is the debug log:
dev:84522025-06-14 11:56:45.968 AM
debug
Driveway Radar Sensor clearing the Status event
dev:84522025-06-14 11:56:44.436 AM
debug
Driveway Radar Sensor Unprocessed ZDO command: cluster=0002 command=00 attrId=null value=null data=[81, 00, 00]
dev:84522025-06-14 11:56:44.431 AM
debug
Driveway Radar Sensor parse: descMap = [raw:catchall: 0000 0002 00 00 0040 00 1F40 00 00 0000 00 00 810000, profileId:0000, clusterId:0002, clusterInt:2, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:1F40, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[81, 00, 00]] description=catchall: 0000 0002 00 00 0040 00 1F40 00 00 0000 00 00 810000
dev:84522025-06-14 11:56:36.966 AM
debug
Driveway Radar Sensor sendZigbeeCommands: sent cmd=[he raw 1F40 0 0 0x8006 {00 00 00 00 00} {0x0000}]
dev:84522025-06-14 11:56:36.962 AM
debug
Driveway Radar Sensor Received ZDO Match Descriptor Request (0x0006) status Success, data=[03, 00, 00, 04, 01, 00, 01, 57, FC] (Sequence Number:03, Input cluster count:00 Input cluster: 0x5701)
dev:84522025-06-14 11:56:36.958 AM
debug
Driveway Radar Sensor parse: descMap = [raw:catchall: 0000 0006 00 00 0040 00 1F40 00 00 0000 00 00 0300000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:1F40, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[03, 00, 00, 04, 01, 00, 01, 57, FC]] description=catchall: 0000 0006 00 00 0040 00 1F40 00 00 0000 00 00 0300000401000157FC
dev:84522025-06-14 11:56:34.971 AM
debug
Driveway Radar Sensor sendZigbeeCommands: sent cmd=[he raw 1F40 0 0 0x8006 {00 00 00 00 00} {0x0000}]
dev:84522025-06-14 11:56:34.966 AM
debug
Driveway Radar Sensor Received ZDO Match Descriptor Request (0x0006) status Success, data=[02, 00, 00, 04, 01, 00, 01, 57, FC] (Sequence Number:02, Input cluster count:00 Input cluster: 0x5701)
dev:84522025-06-14 11:56:34.961 AM
debug
Driveway Radar Sensor parse: descMap = [raw:catchall: 0000 0006 00 00 0040 00 1F40 00 00 0000 00 00 0200000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:1F40, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[02, 00, 00, 04, 01, 00, 01, 57, FC]] description=catchall: 0000 0006 00 00 0040 00 1F40 00 00 0000 00 00 0200000401000157FC
dev:84522025-06-14 11:56:30.557 AM
debug
Driveway Radar Sensor sendZigbeeCommands: sent cmd=[he raw 1F40 0 0 0x8006 {00 00 00 00 00} {0x0000}]
dev:84522025-06-14 11:56:30.552 AM
debug
Driveway Radar Sensor Received ZDO Match Descriptor Request (0x0006) status Success, data=[01, 00, 00, 04, 01, 00, 01, 57, FC] (Sequence Number:01, Input cluster count:00 Input cluster: 0x5701)
dev:84522025-06-14 11:56:30.546 AM
debug
Driveway Radar Sensor parse: descMap = [raw:catchall: 0000 0006 00 00 0040 00 1F40 00 00 0000 00 00 0100000401000157FC, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:1F40, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[01, 00, 00, 04, 01, 00, 01, 57, FC]] description=catchall: 0000 0006 00 00 0040 00 1F40 00 00 0000 00 00 0100000401000157FC
sys:12025-06-14 11:56:22.633 AM
info
Zigbee Discovery Stopped
These logs (the ZDO Match Descriptor Requests) show the typical SONOFF 'specifics' when paired to any Zigbee hub. The frequency of these ZDO messages should decrease after an hour or two.
Did you only power-cycle the device, or did you also start a Zigbee pairing process from your HE hub at this time?
Most of the problems with the Sonoff mmWave sensor are just the opposite - it is too sensitive and may stay in the active state for a long time... What happens if you increase the sensitivity? Keep it away from any other electronic devices that may produce interference.
KKossev, thank you. You are a good man. I bailed on MMwave and went back to an outdoor PIR zwave LR for this application. This was for a driveway sensor to detect bad guys at night, and the AC unit nearby was driving the MM sensors nuts. I sent back the Sonoff and had tested 3 others to the same end result. The PIR sensor in this case in combination with a beam sensor (the beam break is the trigger, the PIR then confirms motion - if both are true then sirens, floods, the actions kick in). This is the PIR sensor, new product by Zooz - multi sensor and runs on battery plus it accepts 12vdc so it was perfect and made for outdoor use. You are awesome for always helping us. Thank you and have a blessed day! jj
Download the Hubitat app
