Presence detection

Configuration > Devices & Services > Presence detection lets any entity from any integration - not just a device that's inherently presence-capable - count as an extra occupancy signal for an Area. Any entity reporting true/on counts as presence, not just a "presence"/ "occupancy" binary sensor - a motion sensor, a door/window contact, or even a media player's own "playing" state all work equally well.

Adding a source

"+ Add source" (the header's three-dot menu) opens a modal that picks Location, Area, Source, Device, and Entity - the same generic device/entity picker Automations already uses, so any entity in the system is reachable, not a fixed list of "supported" devices. Like every other integration on Devices & Services, this tile only shows up once at least one source is configured - a fresh install starts with it hidden.

The source list

A flat, searchable table - Source, Device, Entity, Location, Area, and Status - with a search row and Enabled/Disabled status-filter checkboxes underneath the header, the same convention the ESPHome device list already uses. Each row has a Disable/Enable toggle (pauses the source without deleting it - the occupancy sweep simply skips a disabled row) and a Remove action.

Built-in presence sources still apply

This integration is additive, not a replacement: Bluetooth, LD2410 BLE, Zigbee, Aqara, and Z-Wave devices already feed Area occupancy automatically through their own built-in presence-capable entities, exactly as before. Presence detection is for everything else - most commonly an ESPHome device running the native ld2410/ld2411/ld2412 component, which isn't one of the five built-in sources but reports presence just as reliably.