I had the same problem, my solution was a Xiaomi temp/humidity sensor above the shower, when it detects a rise in humidity, the timeout for the lights is set to be longer.
1 Like
You can actually change this behaviour in the device configuration through zigbee2mqtt:
https://koenkk.github.io/zigbee2mqtt/configuration/device_specific_configuration.html
Hi all,
Did anyone tried to see is the timout can be changed using zigbee2mqtt?
Thank you in advance
No it can’t as it is by sensor design. Read the many threads on this topic.
I have two of these sensors deployed in hallways. They turn on lights when I stumble to the bathroom or kitchen in the middle of the night. The 2 minute timeout is fine with me.
Sorry. I didn’t find what you mentioned when I searched in the topic.
Yes, it can.
You modify the configuration.yaml file under /share/zigbee2mqtt/ and add the following under the occupancy/motion device:
occupancy_timeout: 10
See here:
https://koenkk.github.io/zigbee2mqtt/configuration/device_specific_configuration.html
Don’t forget to restart the addon after making the change.
1 Like
It’s not the same, you can’t change the timeout of the sensor itself.
No, but it does tighten up the delay.
I’m using a 5sec timeout and it’s very apparent.
This is what is written:
Timeout (in seconds) after the
occupancy: falsemessage is sent
The total timeout isn’t 5 seconds. It’s the response time of the gateway to the no motion message from the sensor. Please provide full information, otherwise people get wrong expectations.
Ahh my mistake, I wasn’t aware this was how it was altering the behaviour. Thanks for the info!
I am using occupancy_timeout setting. I believe the wording in the documentation is probably not exactly correct. This setting specifies a timeout after which the
occupancy: false
mqtt message is sent. So the timer starts at the moment a sensor signals presence and then after the specified time the mqtt message is sent. If on the other hand zigbee2mqtt gets a new occupancy message from the sensor during the timeout then the timer is restarted.
Xiaomi sensors have 60 seconds hardware timeout and I set zigbee2mqtt occupancy_timeout to 61 seconds. This prevents getting occupancy: false and another occupancy: true immediately afterwards.
1 Like
I’ve (hardware) modified one of my motion sensors. The 5 seconds timeout is awesome. The HA assistant component needs some improvements because the sensor reports “motion” via MCAST very often now. “no_motion” isn’t reported (whenever). I’ve implemented/hardcoded a timeout of 5 seconds now.
1 Like
Please share how you’ve accomplished this! 
Are there JTAG headers you connect to on the device or something?
edit: just found this actually:
http://livebywant.tistory.com/13?category=703455 (translation required).
This code change is needed to use the modded motion sensor:
For example by downloading this file and copy it to config/custom_components/binary_sensnor/xiaomi_aqara.py. Restart HA and give it a try!
2 Likes
What impact could this modified code have if I have mixed sensors (modified and unmodified)?
Has any one tested the mod with deconz?
How can I easily open the motion sensor?
The sensor can be opened easily. The bottom is a screw cap. Remove the battery and pull gently the grey holder. It’s clipped.