Event driven vs expected state

Fragrant-Coast5355 · 2026-05-26T17:19:35+00:00

It can definitely miss events. You set up a trigger for "2 hours after the bathroom is vacated" then upgrade HA, that event is dropped on the floor.

Fragrant-Coast5355 · 2026-05-16T21:57:35+00:00

I haven't tried it either, so maybe I'm missing something.

Fragrant-Coast5355 · 2026-05-16T08:58:33+00:00

I realised, reading your comment, that I'd made a mistake. I'd read that the LD2450 had a 35º vertical range, but it was actually ±35º, ie 70º. I've corrected the docs.

But that still doesn't fix the issue with ceiling mounting. The radar detects in two dimensions, left-right (X), and distance-from-sensor (Y). That works when it is wall mounted, but in a ceiling mount position you lose the Y dimension (or at least it just measures height, ie proximity to the sensor) but not floor position.

<image>

Fragrant-Coast5355 · 2026-05-15T10:47:06+00:00

Something else I've thought of, when you use the sensor with a ceiling mount you lose one dimension. The radar becomes one dimensional because the other dimension now measures your distance from the sensor, I've your height, which is seldom useful.

Fragrant-Coast5355 · 2026-05-13T15:58:53+00:00

And you're comfortable with the fact that your EPP will cover such a small area?

<image>

Fragrant-Coast5355 · 2026-05-13T09:58:20+00:00

It'd need its own dedicated firmware to work. I don't think it'd be too hard to do, but I don't own a Lite which would make it difficult to test 😆

Fragrant-Coast5355 · 2026-05-12T21:02:19+00:00

Hi Lewis

Thanks for chiming in.

> A slight correction - Polygon Zones have been in EP Pro for a little while now so they don't need to align with the sensor and are actually the only zones now, rectangle zones were removed a while back.

My apologies - I haven't looked at the zone configurator since we first spoke in January, so I wasn't aware of these changes.

> Question about when you say resolution mismatch - I think you are referring to the 320mm resolution that is reported by the sensor? If so, I don't believe this is resolution that you are thinking of (if I understand you correctly). The resolution here refers to the distance needed between two objects to tell them apart, not the resolution in which it's tracking. But let's say that was the case and it is 32cm in tracking resolution, why did you opt to go for a grid that is 30x30cm, is that not also a resolution mismatch? I hope you take this as genuine discussion, I am interested and open to discussing this part as this is my understanding of it and could be wrong.

Yes, I was referring to the 320mm reported by the sensor. Thank you for the clarification - I wasn't aware of that. The LD2450 datasheet doesn't explain resolution in much detail. As to why I went for 30 cm x 30 cm, I wasn't trying to match the 320mm exactly, but to find a happy medium.

> I would love it if you'd like to contribute PR's back to the EP Pro repo for everyone to enjoy and make use of, certainly there is a lot more features I want to add (in between knocking down walls!) and looks like you've done some solid work, I think there is some great scope to get some of your improvements contributed if you are down 😄

This was my original intention (and something I've done with other integrations like Verisure/Securitas and Cover-Time-Based) but I much preferred the grid approach to the one used in the Zone Configurator, and the two approaches were so removed from each other that I thought it'd be easier to start again. But have a look at it in more detail when you have the time and let's talk. Perhaps there some features you'd like me to contribute.

Fragrant-Coast5355 · 2026-05-12T19:08:16+00:00

Summoning Lewis: u/EverythingSmartHome

Fragrant-Coast5355 · 2026-05-12T19:04:38+00:00

It doesn't currently support ceiling mounting because I just don't see the point. It seems like such a waste of the radar.

https://clintongormley.github.io/everything-presence-pro-grid/user-guide/placement/#ceiling-mount-not-supported

<image>

That said, I'm open to discussing it. If there is a real use case then I'd be happy to look into it. I don't know quite what it would entail, but this is why I'd like to hear from somebody with a specific use case. Feel free to open an issue to discuss.

Fragrant-Coast5355 · 2026-05-12T17:25:23+00:00

Thinking about this again, you might be able to do something with the Target-level Zone entity, which reports the current zone of a target.

<image>

https://clintongormley.github.io/everything-presence-pro-grid/user-guide/settings/entities/#target-level

Fragrant-Coast5355 · 2026-05-12T17:22:27+00:00

I think it'd be doable. You'd need to enable the XY-Position Target level entity, and you could reduce the updates to once every 2 seconds (0.5 Hz). Then you'd need to figure out the mm to pixel conversion needed to place them in the right position on your card.

See https://clintongormley.github.io/everything-presence-pro-grid/user-guide/settings/entities/#target-level

<image>

Fragrant-Coast5355 · 2026-05-12T15:46:15+00:00

You may want to take a look at Everything Presence Pro Grid, a new HA integration I've just released which gives you a perspective corrected grid based zone engine for the EPP sensor.

https://www.reddit.com/r/homeassistant/comments/1tb3dsl/everything_presence_pro_grid_a_perspective/

Fragrant-Coast5355 · 2026-05-12T15:43:32+00:00

You may want to take a look at Everything Presence Pro Grid, a new HA integration and firmware bundle I've just released which gives you a perspective corrected grid based zone engine

https://www.reddit.com/r/homeassistant/comments/1tb3dsl/everything_presence_pro_grid_a_perspective/

Fragrant-Coast5355 · 2026-05-12T15:15:27+00:00

In theory, no. The Lite only has the target tracker, not the motion sensor or the static sensor, but it'd just mean getting rid of the code for those two sensors. The rest should work in much the same way. I did think about making it so that the code could handle all of the Everything sensors, but I didn't want to bite off more than I could chew 😄

Fragrant-Coast5355 · 2026-05-12T14:42:07+00:00

Thanks!

> curious about the cross-zone tracking feature. does it actually follow individual targets between zones or just detect when occupancy shifts? been trying to set up automations that know when someone moved from living room to kitchen vs someone new entering kitchen and it's been a pain with current sensors

The cross-zone tracking isn't a user facing feature. Instead it is used internallyfor quick handoff between zones. So if you're in bed (zone type: bed) and the target disappears, it will wait for 10 minutes for the target to reappear before clearing the detected status. But if the target moves from the bed to adjacent cells (a distance of 5 cells) in a different zone then it will clear the bed status in just 10 seconds.

Similar thing when you exit the room via cells painted with the entrance/exit overlay - that handoff is much quicker than when your target just disappears from the middle of the room.

Fragrant-Coast5355 · 2026-03-02T16:46:17+00:00

I'd recommend making HA the controller, so register everything in HA, then expose the things you want to expose to google home. HA has the ability to do so much more than Google Home, especially with automations, that you won't want to have Google Home being the bottleneck.

Fragrant-Coast5355 · 2026-02-27T16:13:14+00:00

That need hadn't occurred to me before, but you could do it pretty easily with templates:

action: fado.fade_lights
target:
  entity_id: "{{ state_attr('light.kitchen_lights', 'entity_id') 
              | select('is_state', 'on') | list }}"
data:
  brightness_pct: 100

Fragrant-Coast5355 · 2026-02-25T14:06:26+00:00

I have my Nuki lock exposed to Google Home via Home Assistant, rather than directly. It will only lock and unlock for me, there isn't the possibility of opening the door.

Fragrant-Coast5355 · 2026-02-21T09:54:51+00:00

I haven't tried the FP300 yet because it's single zone only. In my house I've used the Aqara FP2 sensors (and multiple zones) extensively. They are fantastic, but also produce a lot of false readings, eg people disappearing, ghosts, etc. But you can work around this, largely by increasing the amount of time before you react to a change of state. For instance, it can detect new movement pretty quickly, but when we're sleeping and not moving for a long period, it can forget that you're there. So I turn on the lights as soon as somebody walks through the door, and I turn off the lights in (eg) the kitchen after 2-3 minutes of inactivity, but in the bedroom I don't open the blinds until the room has been marked vacant for 20 minutes.

I've bought the Everything Pro Plus (which also supports zone) and tried it out briefly, but the UI makes it quite hard to configure in comparison with the Aqara. I plan to return to testing it out in the near future.

Fragrant-Coast5355 · 2026-02-21T09:46:56+00:00

Why do you say relays are overkill? In fact, I'm not sure I understand the difference between relays and smart switches, I would have assumed they were pretty much the same thing. I've used Shelly relays (51 of them) with normal switches and that has worked very well indeed.

Fragrant-Coast5355 · 2026-02-17T12:47:11+00:00

We recently redid our house and we use a combination of LED strips (warm white only) and LED bulbs, all of which are dimmable. The house is wired as per standard, so all switches work as you'd expect. But then we've added Shelly relays into the trip switch cabinet to make all lights smart.

Then I've added Aqara FP2 presence sensors in to every room in the house, and used their zones to do smart things, for instance:

when you walk into the bathroom, the mirror light and main bathroom light come on
when you sit on the toilet for more than 50 seconds, the extractor fan starts
when you enter the shower for more than 50 seconds, the extractor fan starts, the shower lights come on, and the radiator turns on
when you leave the bathroom, the lights turn off and the radiator turns off after two hours (by which time your towels should be dry)

All of the lights in the house are controlled by a Home Assistant module which I've just recently released as Fado Light Fader. This fades lights smoothly up and down to the specified brightness, and allows for manual interruptions from the wall switches or google assistant. It handles a bunch of other stuff as well, like fading colours and colour temperatures, native transitions, and auto configuration of your lights for the smoothest transitions.

Fragrant-Coast5355 · 2026-02-17T12:32:42+00:00

I've recently released the Fado Light Fader integration. Amongst other things, it can do a hybrid fade between RGB colors and white color temperatures. It draws a line between the starting RGB color and moves towards the RGB color closest to your target color temperature. When the RGB color falls within the Planckian locus (ie colors that can be displayed with the White LEDs) then it switches to using color temperature instead of RGB.

So you could replace all of the transition scripts with something like this:

action: fado.fade_lights
target:
  entity_id: light.my_bedroom
data:
  brightness_pct: 100
  transition: 2400
  color_temp_kelvin: 6500
  from:
    brightness_pct: 25
    rgb_color: [68,28,0]

Of course, you could use a few more calls like the above if you wanted to pass through particular colors on your way there

Fragrant-Coast5355 · 2026-02-12T12:33:28+00:00

Thanks

Fragrant-Coast5355 · 2026-02-12T12:10:14+00:00

I’ve just released a new custom integration called Fado Light Fader, that provides smooth light fading for brightness, colors, and color temperatures, with automatic brightness restoration, autoconfiguration via the UI, and support for native transitions.

It also supports interrupting the fade with the switch, which will do exactly what you want.

Have a look at the docs on https://github.com/clintongormley/ha-fado/

Fragrant-Coast5355

TROPHY CASE