Trying to set up SONOFF SNZB-06P timeout - what's the format? #19771
Comments
|
Same issue. Tested 2 so far, it reports occupancy indefinitely even when placed in an empty box. occupancy is permanently on |
|
@Busta999 I got a couple delivered today. They do work ok at reporting occupancy - it's annoying that I can't adjust the timeout yet so they don't "clear" for 60 seconds. I did have to reset one a couple of times closer to a coordinator to get it to report something other than "N/A". Press and hold the button for ~5 seconds. |
|
Same here. |
|
same thing here , |
|
I have ordered a Sonoff Hub to test the sensors on. Identify if I have bad sensors or an issue in zigbee2MQTT. should have an answer by Wednesday this week. |
|
Right now the minimum timeout can be set to 30s. Setting below 30s will keep the device occupied. Both ZHA and Z2M can configure it. |
In fact, microwave radar can penetrate most non-metallic materials, including walls. Moreover, it has reflection capabilities, meaning that objects in motion behind the sensor or outside of the room may trigger it. |
Good point, I tested the device in a closed cardboard box with sensor pointing away from towards a wall and it continued to report occupancy. Overnight the sensor reset to clear, when the room was unoccupied. I have just returned to the room and the sensor did take 60+ seconds to report occupied. It went to clear very quickly after leaving the room, No occupancy is set to 1 second. I’ll have the sonoff hub hopefully today and will test further. But your point is valid and I suspect correct, the device was continuing to detect presence, even while sat in cardboard box. If it continues to function as this morning’s testing indicates then this device will perform as desired. Use a PIR sensor to detect entrance into the space to turn on lights, then use the Sonoff to detect ongoing presence to stop lights from going off. My main use case is in rooms where people may be still for longer periods than a PIR sensor time out period, for me Lounge, Kitchen, Office. At this stage I am not so sure either sensor of zigbee2MQTT is malfunctioning, I suspect the sensor is just slow identifying and reporting occupancy, which for its price, is ok and workable. Will perform further testing on zigbee2MQTT and sonoff hub. |
As I wrote, it was set up with that already, and it works, I can also see it showing clear now, so I guess it's working. And thankyou to all you other guys about how to interpret the explanation on the 'Time' in Settings Specific, seems like the text is simply wrong. |
|
Same issue here, the documentation is not very clear about how to configure the timeout format and, apart from that, it always emits a |
|
What's needed to allow zigbee2mqtt to configure the sensitivity of the sensor? The product page lists "Three levels of sensitivity (2.5m, 3.5m, 4m)" but there's no way to configure it yet in z2m |
In addition the marketing materials mention some sort of lux sensor but I don't see it exposed either. |
|
In the Sonoff Hub you can automate against Luminance High/Low with no configuration of thresholds. I’ll check the exact field names. |
I'm using Z2M with SkyConnect and Home Assistant so no Sonoff Hub anywhere in my system. I was hoping to still be able to automate based on ambient brightness. |
|
The hope is that the basic luminance along with presence sensitivity will be added to zigbee2MQTT, I am pretty new to zigbee2MQTT so not yet sure how that happens |
|
I'm also new to Z2M, switching from ZHA. Happy to help where I can to get these added but it's pretty new territory for me. |
The sensitivity can be configured here. "1" means 2.5m, "2" means 3.5m, "3" means 4m |
|
@yanhao666 thanks! How did you find this information? Or rather, where do you find the information about which clusters/attributes can be used to configure any particular device? |
Gold information, thankyou @yanhao666 ! |
|
Hmm it also seems like binding isn't working properly with this sensor. When I try to bind it to a group of lights it doesn't turn them on/off. There's seemingly no way to bind to the on/off cluster of the target. Trying to bind to an individual bulb (ikea tradfri in this case) only shows the "Identify" cluster.
|
Yes this worked for me. Thank you. |
|
Mine showing occupied permanently. |
I had to re-pair mine a few times to make them work. Then when they started working they were fine until I turned off power and rebooted them. I don't believe 1.0.5 is available yet. 1.0.3 is the current firmware I think |
I raised a ticket with Sonoff: Regards, |
Mine did that as well. It's very sensitive. I moved the position of mine on the wall and has worked well since. |
|
@linkedupbits lol thanks for trying, the product page says I guess they just meant that zigbee hubs continue to work even if the internet is down. |
|
Zigbee2MQTT update has enabled OTA for these. I've just updated mine to 1.0.5, hopefully there's some improvement. Does anyone know if/where Sonoff publish firmware changelogs? |
How did you update it? When I try to check for an update it says "Failed to check if update available for 'Office presence sensor' (Unexpected token � in JSON at position 0)". |
Strange, all three of my sensors updated without error. Sorry I don't have any suggestions as I haven't done many Z2M OTA upgrades |
It works 95% of the time, but sometime false recognition still occurs. |
|
This device is really disappointing. Is anyone else's sensor behaving like a motion sensor? It's about 2-3 ft away from me and if I sit still, it will stop showing presence (if it's not stuck showing presence for hours when no one is present). I have two of them, one on firmware 1.0.5 and one on 1.0.3. Both behave the same way. |
@metec22 It seems possible that the radar microwave has been interfered with. Are there metal objects blocking the middle? Or using another radar nearby at the same time? |
|
HA 2023.12.x seems to have issues with zigbee and/or mqtt, devices go "unavailable" in HA even though z2m is still communicating with them. Other than that when the network is working smoothly I don't have any of those issues with these sensors. They respond fast and state stays "occupied" when people are still. I set msOccupancySensing -> ultrasonicUToOThreshold to 3 on all of mine. If you have two or more of the sensors too close to each other or pointed toward each other they can interfere. Any other radar based devices might interfere as well (I think some security systems?). |
|
Weird. I don't have any metal objects anywhere near the sensor. I only used one sensor at a time in the same spot. It's also much slower than a motion sensor I was hoping to replace. When I walk into the room, it takes about 2-3 seconds for the light to come on. On the updated sensor, I set the time out to 30s and tried all three settings for threshold. On the one with the older firmware, I haven't changed anything. Maybe there is some interference in the room but nothing obvious. |
|
@metec22 , for me it sounds defective. I have three mw sensors on top of each other while testing, they all work perfectly, and with the released notes on how to adjust sensitivity / duration, and the firmware at 1.0.3 it works quite nicely. |
I received 6 of these sensors yesterday. I've set up one per room in z2m and upgraded the firmware to v1.0.5. One of them is in a 5 meter long hallway with no interference source whatsoever, but the detection time sometimes is instantaneous and sometimes it takes about 3 seconds to detect presence. Edit: after testing with different sensitivity settings and timeout periods, the presence sensor still behaves like a motion sensor. Overnight it constantly changes to detected and clear several times. Bonus: today, out of the blue, the presence sensor in the bathroom got stuck on detected state for 6 hours without anyone entering or exiting the bathroom for the entire time. No potential interference sources exist in the bathroom (fans, air conditioners, other radar based devices). |
It is not a good sensor, I`m having problems as well... Wish I had bought the normal Tuya mmwave sensor =( |
|
I have another update. The bedroom still behaves pretty much the same, but i realised that the behaviour is very much related to the positioning of the sensor. I got much better results when placing the sensors about 1.5 m high on the wall. The bedroom one still stops detecting me from time to time but the bathroom one is now working flawlessly since i repositioned it. I will keep playing with it and report back, but as far as i can tell this is a good sign not to lose faith in this sensor. ATM 5 out of 6 sensors work exactly as expected. |
|
Mine will work amazingly for a little while then go back to detected for hours at a time. |
|
I also had a few issues when I installed mine but everything has been flawless since I moved it to a slightly different place. It looks like objects / walls were initially bouncing back the waves. I now wish that the lux could be updated at regular intervals.. It now detects my presence but won't update the lux while I am there, effectively preventing any automation from switching on/off the lights if and when it later gets dark (sunset) / brighter (sunrise) and I am still in the room |
This happened to me with sensors that were placed very high on the wall and in the corners of the rooms or with the sensor pointing downwards. I found that the sweet spot for me is around 1.5m height, as far from the corners of the wall as possible and with the sensor pointing straight ahead. For the light intensity issues, i'm just using the data from other light sensors around my home until the ones in the presence sensor get better. The fact that the light intensity only updates upon presence detection is quite stupid especially for a mains powered device that could send updates to z2m as often as it needed without worrying about battery life. |
|
I ripped one open (for science!) and the photodiode is on the radar board not the mainboard so it may be a firmware thing that it doesn't get illuminance updates until the radar controller sends it to the main board. edit: this is in the reddit post, but may be useful here, the radar board appears to be a slightly modified AirLink AT58L4M32-2020 (which explains why this sensor doesn't have advanced capabilities like some other radar presense sensors) and the main board is based on a standard EFR32MG22 zigbee chip |
This is why I opened a support ticket with Sonoff directly asking if it can be changed in a future firmware update. It may be a long shot but they've already updated fw once to reduce the cooldown. I recommend more people submit a request here to decouple photodetector updates from radar updates. |
Maybe, when the sensor is close to the chest, the detection of presence/breathing will be more effective. |
|
There is a useful update here on the sonoff website - the latest firmware 1.0.6 - seems to work well for me |
I can't see any mention of v1.0.6 on that page. Also how did you update? I have v1.0.5 in Z2M and checking for new versions doesn't give me anything. |
|
I did the update manually as per the OTA update ZHA section
|
|
There is no version 1.0.6 as far as I can tell? 1.0.5 is the latest |
|
No option to manually update through Z2M from what I can tell. Z2M also doesn't detect a new firmware update (yet). |
Mine came ootb with 1.0.6. Also having the same issue of being stuck on motion detected. Also, it doesn't even expose the occupany entity. |
The motion entity is the occupancy entity. You just have to change the entity type in HA. |
I see. Because for those who have it connected to ZHA it shows both motion and occupancy. And apparently the occupancy entity works but the motion one doesn't, which is why I was looking for that entity. If it's a matter of just changing the entity type then it wouldn't work anyway. It's always stuck in detected state. |
|
Guys, whose sensor is stuck in the “detected” state should go to Settings (specific) and select the required time in minutes after which the sensor will report that the object is missing. The sensor with this parameter has been working for the second week without errors. HA rebooted many times during this time. All OK. |
What would be the setting in ZHA to change for this ? I have one Sonoff stuck in detected out of 4. I am not using Zigbee2MQTT. I installed V1.0.5 when I got them. |
Unfortunately, I can’t tell you how to configure SONOFF SNZB-06P in ZHA. |
|
Background: I received a few SNZB-06P sensors (Firmware: 0x00001006) yesterday and have already tested a couple on HAOS. They connect without problems and everything seems to be working fine. Issue: I suspect that many people are facing the same "problem". The sensor is so sensitive that it is sometimes impossible to block its detection even when placed in a metal box. It detects human presence even through the smallest crack in a slightly opened metal box. Recommendation: Before complaining about the permanent "Detected state", I recommend testing the sensor's operation by moving away from it. Even on "Low" detection sensitivity, it "sees" people through walls, reacts to nearby animals, etc. I tried to close it in a cabinet, and it still "sees" too much. Request: Realistically, there is a need for a lower sensitivity level than "Low". If anyone has managed to further reduce its sensitivity, please share your solution.. Conclusion: The SNZB-06P motion sensor is a great product, but its high sensitivity can be a problem in some cases. I hope Sonoff will consider adding a lower sensitivity level in future firmware updates. My current Home Assistant version: Core 2024.3.0 |
|
Same behavior. |
|
To achieve more precise sensor operation, I direct the sensors not directly at the monitored space, but at a 45-degree angle to the ceiling from the door. This makes the sensor sensitivity tolerable and reduces the number of excessive detections. |
|
I have two SNZB-06P, one with zigbee2mqtt+ha and other in other home with Amazon Alexa Studio (with zigbee hub), both are in the bath (in their respective homes) to swith on/off the light. With zigbee2mqtt+ha works rather well, may be delay 1 second to light up (perhaps moving orientation works better) and the 15 seconds delay i would prefer 10 or 5 seconds, the light keeps on to much for me. The problem is with Amazon Alexa Studio, the 80% percent of times do no detect anything so the light do not turn on, besides Alexa/hub APP do not permit anything and the delay is 60 seconds which for me is too much. Any help or tip ? |
and others
What happened?
I've set up the SONOFF SNZB-06P in Z2M, it is recognized nicely.
There is only one topic in 'Exposes', and that is occupancy
There is no Sensitivity Setting and there is no Timeout setting exposed.
Both of these are available in Sonoff's own Zigbee bridge.
There is some explanation in 'Settings (specific)' that explains
Sends a message after the last time no occupancy (occupancy: false) was detected.
So it looks like you can have it send multiple messages.
It also explains that it should be set to an object like [10,60] and it will then send a message after 10s and after 60s.
But the field shown does not accept objects, only numbers, and setting it to a number doesn't change anything.
What did you expect to happen?
That I could enter [10] and it would timeout after 10s, or [60] and it would time out after 60s.
When I saw the device was supported, I actually expted it to support the parameters exposed to eWeLink though Sonoff ZBBridge.
How to reproduce it (minimal and precise)
Just add it to Z2M
Zigbee2MQTT version
1.33.2
Adapter firmware version
20230507
Adapter
TubesZB CC2652P2 POE adapter
Debug log
No response
The text was updated successfully, but these errors were encountered: