Modify decay rate during sleep

[fctruter]

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

Bed occupancy is slightly different from other presence sensors, because the interpretation is different based on the time of the day.

Describe the solution you'd like

Split out bed sensors from other presence sensors with a time of day config

Describe alternatives you've considered

Can implement this in the downstream automation that makes use of the occupancy output.

Additional context

When I am laying/sitting in the bed during to day when either reading or working on my laptop I want the lights to stay on. When I am sleeping at night I don't want the lights to go on even if movement is detected in the room.

[wylie102]

This doesn't sound like an issue with this integration, more that your sensor stops detecting you at different points in the night. Or you have the automation not quite set up for what you want.

Your issue is that one of your automations is set to turn your light on if your motion sensor detects movement. At night this is more likely because it has stopped detecting movement and then detected you again again.

Either you set something to cancel this overnight, or if your bed occupancy sensor consistently detects you then you combine that with the motion sensor for room occupancy. Either as a helper (then plug that into this integration) or just add it as a secondary sensor within the integration.

So then you walk into your room, the motion sensor detects you, the lights turn on. You sit in your bed the motion and bed sensor detect you. At night you turn off the light, at some point the motion sensor will lose you but the bed sensor will still have you so the output of the combined sensor stays at occupied so no light change is triggered. This is all doable regardless of what this integration is doing.

You just need to change your automations, upstream not downstream.

[wylie102]

@Hankanman One thing that would be useful for bedrooms would be a different decay rate between night and day. If I'm in bed at night and both my bed sensor and motion sensor lose me for 5 minutes I want the light to stay in the state they are in (off).

But during the day if I leave the room for 5 minutes I want the light to turn off, even if historically I might be in the room during that time of day. Really we want it basing the room occupancy based on the probability that the sensor is wrong rather than the likelihood of the room being occupied at that particular point in the day. So it should use patterns of relative duration of occupancy vs absence I.e if the sensor stops detecting me what is the probability that I have left the room vs the probability that the sensor is wrong based on how long I am usually gone before staying gone (actually gone) vs how long I am gone when I am likely to re-appear (either sensor loss or short absence).

I wasn't able to tell quite how it works at the moment, I've only just set things up but it seems more like pattern of time of day rather than duration (I'm happy to be corrected on that and learn a bit more about how the integration works under the hood). Also it seems like it might be double counting in bedrooms since the rooms will have a strong record of being occupied during sleep hours, so will have a high prior probability so no need for a very slow decay rate, especially one that carries over during the day.

I think a helpful move would be for bedrooms to be able to set a long decay rate at night, and then a shorter one during the day.

[wylie102]

Also maybe down the road you need an option for what the presence detection is being used to control. For example for lights, if we are using a reliable presence sensor like mmwave, then you don't need it predicting when you might be in the room and turning the lights on while the motion sensor is clear (which mine did today despite me being out of the room for 2+hours). What we want it to be doing for lights is accurately identifying presence/absence once the motion sensor is clear and ignoring false clear signals, but turning off when the room is actually empty for an appropriate time. (And probably need to be ignoring any illuminance sensor since these are tied to the lights which we are controlling so it's a bit of a loop).

But if being used for heating then you maybe do want to have a two tiered trigger and have it heating the room slightly ahead of when you are most likely to be using it, then more once presence is detected. And it doesn't need to turn off and on if you leave the room for just 10min. And you then want the prediction ignoring temp/humidity.

I guess this could be achieved with automating off different threshold levels. Or creating different entities for heating and lights, using different inputs and decay values. But it would be awesome if it could be done natively within the integration itself.

[Hankanman]

Some features now available in release 2025.12.0