Trying to set up SONOFF SNZB-06P timeout - what's the format?

[fribse]

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

[johnrobertcobbold]

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

[Alfy1080]

Mine will work amazingly for a little while then go back to detected for hours at a time.

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.

[evelant]

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

[nanderson97651]

so it may be a firmware thing that it doesn't get illuminance updates until the radar controller sends it to the main board

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.

[yanhao666]

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.

Maybe, when the sensor is close to the chest, the detection of presence/breathing will be more effective.

[charlidog]

There is a useful update here on the sonoff website - the latest firmware 1.0.6 - seems to work well for me

[Alfy1080]

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.

[charlidog]

I did the update manually as per the OTA update ZHA section

Waiting for the firmware to update automatically may take a considerable amount of time. We recommend proceeding with a manual update. To begin, you’ll need to copy the device’s IEEE address.

[evelant]

There is no version 1.0.6 as far as I can tell? 1.0.5 is the latest

[hjpfourie]

No option to manually update through Z2M from what I can tell. Z2M also doesn't detect a new firmware update (yet).

[kennethpangky]

There is no version 1.0.6 as far as I can tell? 1.0.5 is the latest

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.

[Alfy1080]

There is no version 1.0.6 as far as I can tell? 1.0.5 is the latest

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.

[kennethpangky]

There is no version 1.0.6 as far as I can tell? 1.0.5 is the latest

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.

[Sr-psycho]

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. PS The Occupancy timeout parameter had no effect. FW 1.0.5 Zigbee2MQTT v. 1.35.3-1

[vcadieux]

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. PS The Occupancy timeout parameter had no effect. FW 1.0.5 Zigbee2MQTT v. 1.35.3-1

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.

[Sr-psycho]

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.

Unfortunately, I can’t tell you how to configure SONOFF SNZB-06P in ZHA.

[BroncoDJ]

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 Supervisor 2024.02.1 Operating System 12.0 Frontend 20240306.0

[Fannangir]

Same behavior. The sensor is actually stuck on occupied, set at Low. Unfortunately, didn't find a solution to reduce sensitivity :(.

[BroncoDJ]

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-m-d]

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 ? i know this it is for zigbee2mqtt.