Sonoff supply a driver for the presence sensor
The SNZB-03P motion sensor uses Zigbee Motion Sensor Mc from @Mariano_Colmenarejo
Thanks for your answer, the ZigBee motion sensor doesnβt show up in my drivers. I just reinstalled it but it doesnβt show up.
According to the video you published, you have to enroll your hub in the official Sonoff channel and install its driver on your Hub.
Look in the device manual and a link to the channel invitation will come
Afterwards you can install the device and it will pair with the Sonoff driver.
My driver does not have support for the SNZB-06P
My driver has support for Sonoff SNZB-03, not SNZB-03P. If you pair it with zigbee Thing Mc, then I could see if it is compatible with the driver
hello
I use the sonoff official pilote SNZB-06P.
it works but the pilote is very poor and show no information graph and no parameters such:
- extension detection duration (0 to x minutes)
- device sensibility (low = 2.5m, medium=3,5m, high=4m)
is someone could have a good idea to improve it it would be nice!
thank you
hello @Mariano_Colmenarejo
I use also the sonoff SNZB-03 with you pilote driver βZigbee Motion Sensor Mcβ.
It works but I canβt have any informations on the battery and the receive Signal Metrics
see my screensshots:
can you help ?
thankβs in advance
Hi,
Battery reports are received every 6 hours, please wait for the next one to be received.
Did you pair it directly with the driver or did you change the driver from a different one?
@Mariano_Colmenarejo Any chance of you adding support?
I could try it, I found a Sonoff document for sensitivity and timeout settings.
What firmware version does the app show for this device?
in zigbee thing it shows 0x01. For versions 1.05 and higher, the timeout can be up to 15 seconds minimum and in previous versions 30 seconds.
Ok, it seems that it is the composition of App version and zcl version that gives the firmware version.
I would have to make 2 different profiles for the lower limit of the timeout in preferences or find another way to do it
The device could emit motion and occupancy.
Motion would be required to use it in STHM.
Do I also add occupancy in case you want to use it for routines?
Yes, please. That could be useful.
Hi @nrasmussen @jean-louis_rocchisan
Added SONOFF, SNZB-06P to this driver version.
Profile has capabilities Motion and Occupancy
Added two preferences for Sensitivity and Timeout.
They are treated as if they were firmware <1.05 (minimum timeout 30sec)
- name: "motionSensitivitySonoff"
title: "Select Sensor Sensitivity Level"
description: "Select Motion Sensitivity Level (Low, Midium, High). Default : High"
required: false
preferenceType: enumeration
definition:
options:
1 : "Low: Detection distance 2.5m"
2 : "Medium: Detection distance 3.5m"
3 : "High: Detection distance of 4m"
default: 3
- name: "unoccupiedDelaySonoff"
title: "Delay to emity Unoccupied event"
description: "Select Delay to emity Unoccupied event after Occupied detection (30 sec to 65535 sec). Default : 30"
required: false
preferenceType: integer
definition:
minimum: 30
maximum: 65535
default: 30
There are no signal metrics capability, because they are obtained with battery messages and this device does not have a battery.
If you send me some logs of the preference values changes, I could see if they are accepted correctly by the device and I can check the firmware version.
It is necessary that you uninstall the device and reinstall it directly with the Zigbee Motion Sensor Mc driver to device configure, it may be necessary to delete the sonoff driver.
βββββββββββββββββββββββββββββββββββββββββββββββββββ
Name Zigbee Motion Sensor Mc
Version 2024-02-19T19:52:44.853232749
βββββββββββββββββββββββββββββββββββββββββββββββββββ
- id: "SONOFF/SNZB-06P"
deviceLabel: SONOFF SNZB-06P Sensor
manufacturer: SONOFF
model: SNZB-06P
deviceProfileName: sonoff-motion-occupancy
Thanks a lot! Iβll do some tests and report back.
Did you uninstall your device and pair it again with this driver?
If you made a driver change from the sonoff driver then it is possible that the cluster and occupancy attribute were not configured.
I have already deleted the signal metrics capability from the profile in this driver version
βββββββββββββββββββββββββββββββββββββββββββββββββββ
Name Zigbee Motion Sensor Mc
Version 2024-02-20T12:00:15.106471691
βββββββββββββββββββββββββββββββββββββββββββββββββββ
@Mariano_Colmenarejo Screenshot from your latest driver update.
From the initial tests Iβve made so far it seems like motion detection works fine. Iβm not sure how the occupancy reporting is supposed to work; status does eventually change between Inside and Away, but with huge delays (up to several hours).
Hi @nrasmussen
As I mentioned, it would be necessary to see the deviceβs cli logs to see if the device accepts the preference configuration and the cluster reports and occupancy attributes.
It is the problem of making a driver without having the device, I need the userβs collaboration to debug it.
Iβm not sure how the occupancy reporting is supposed to work; status does eventually change between Inside and Away, but with huge delays (up to several hours).
If you read the other comments in this thread, as well as reviews and comments on other sites, you will see that this is a common complaint about this particular model. Nothing to do with SmartThings, it happens with other hubs as well. It is a very inexpensive model, and just doesnβt have the same precision as some of the more expensive devices of the same type.
Yes, of course. I fully understand. Iβll try to get the logs you need.
Hello
Yes I uninstall twice.
it works
I have 2 measures 
- detection movements
- status occupancy (not sure to understand how it works but will test it on a day or two)
improvement idea: on occupancy would be nice to have a graph widget like temperature
signal metrics have disappear
thanks a lot for the job done