What is “best” driver for:
| Application | 01 |
|---|---|
| Endpoint Id | 01 |
| Firmware MT | 1286-080C-00001006 |
| In Clusters | 0000,0003,0406,0500,FC57,FC11 |
| Manufacturer | SONOFF |
| Model | SNZB-06P |
| Out Clusters | 0003,0019 |
| Software Build | 1.0.6 |
I am spinning around in circles trying to find a configurable driver.
@kkossev
Sonoff SNZB-06P is supported in this driver :
Is the device online / responding to ping() commands? (The screenshot is cut, and not everything is visible.)
Anything in the live logs?
Yes, ping try <100
Logs of debug logging
Anything that you want to see?
What is in the logs when you move away from the sensor for one minute and when you activate the sensor back...
Did you install the driver for the first time now (because of the Sonoff sensor), or did you have a previous version installed before?
Make sure you have clicked on this button at least once:
The standard device profiles (used by all mmWave sensors) should have loaded automatically, but…
Please check the other mmWave devices - are they working OK after the update?
Checking others now.
TS0225_LINPTECH works OK
Are warnings in log significant?
Aren’t 0x0406 and 0xfc11 the reporting clusters?
These warnings shouln't be there ...
Try to load the defaults from the Configure drop-down menu :
It’s possible that something may have been broken in the latest version — I’ll check tomorrow morning and let you know.
Ok thanks, my cable dropped. Switched to hotspot. Will await you response. Thanks.
Temporarily moving back to Sunricher MW Motion Sensor.
Is the HE inbuilt driver for Sunricher MW Motion Sensor working OK with the SONOFF SNZB-06P ?
I've found and fixed the issue :
2, Click on the Refresh button
Good morning from North Carolina. First, your fix appears to work well, but I’ll have to play with it a bit to make it fit my use case.
Thank you.
[… and NO, the Sunricher MW Motion Sensor driver doesn’t work well. Get stuck in active.]
@kkossev Just to let you know that I have had mixed results with this device and driver.
I tested it in a location where there should not be anything to trip it other than someone sitting in a chair about 1 meter in front of it.
That test worked for several days with Sensitivity set to 1. It tripped quickly when someone sat and reset about 60 seconds after they left.
Then it started to get “stuck” active. Just looked now and:
Motion Started
2025-12-30 17:12:10.626
Not quite sure what to do with it.
Download the Hubitat app
