--- title: "Magic Areas" description: "Magic Areas is a Marketplace integration for Home Assistant. It has 915 installs sharing analytics, works locally and was last updated October 19, 2026." canonical: "https://vulpo.app/integrations/marketplace/jseidl-magic-areas" url: "https://vulpo.app/integrations/marketplace/jseidl-magic-areas.md" last-updated: "2026-10-22" version: "1.4" --- # Magic Areas > Magic Areas is a Marketplace integration for Home Assistant. It has 915 installs sharing analytics, works locally and was last updated October 19, 2026. Magic Areas is a Home Assistant integration that turns areas into presence-aware zones which control lights, fans, climate and media. It tracks whether an area is occupied from sources such as motion sensors, media players, device trackers and Bluetooth beacons, with a configurable timeout for clearing presence. Secondary states like dark, sleep and extended refine the area state, and meta-areas such as interior, exterior and floors group several areas together. Lights are grouped by purpose (overhead, task, accent and sleep), and each group can be tied to chosen area states. Further options cover fan groups driven by aggregated sensor values, climate preset switching, an area-aware media player for notifications, sensor aggregates, health sensors and a presence hold switch. It works locally and is set up in the UI. Automatic summary of the README and code of jseidl/magic-areas. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=jseidl&repository=magic-areas&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=jseidl&repository=magic-areas&category=integration) ## Supports - **Works locally**: Talks to your devices on your own network. No vendor cloud in between. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Create a Magic Area - **Area** ### After setup - **Create fan groups** - **Create climate controller** - **Create media player groups** - **Create light groups** - **Create cover groups** - **Area-aware media player** - **Create aggregate sensors** - **Create health sensors** - **Create presence hold switch** - **Monitor Bluetooth tracker sensors** - **Create a Wasp in a Box sensor** - **Device classes to track** - **Overhead lights** - **States which overhead lights are turned on**: Configure which area states will trigger this light group. Light groups will be turned on while area is on this state and off if the area loses these states. For example, if you want the light to stay on after an extended period of time, you need to select the extended state too. - **When should overhead lights be controlled?**: Select if this light group should be controlled only when an area first gets occupied, only on area state changes or both. - **Sleep lights** - **States which sleep lights are turned on**: Configure which area states will trigger this light group. Light groups will be turned on while area is on this state and off if the area loses these states. For example, if you want the light to stay on after an extended period of time, you need to select the extended state too. - **When should sleep lights be controlled?**: Select if this light group should be controlled only when an area first gets occupied, only on area state changes or both. - **Accent lights** - **States which accent lights are turned on**: Configure which area states will trigger this light group. Light groups will be turned on while area is on this state and off if the area loses these states. For example, if you want the light to stay on after an extended period of time, you need to select the extended state too. - **When should accent lights be controlled?**: Select if this light group should be controlled only when an area first gets occupied, only on area state changes or both. - **Task lights** - **States which task lights are turned on**: Configure which area states will trigger this light group. Light groups will be turned on while area is on this state and off if the area loses these states. For example, if you want the light to stay on after an extended period of time, you need to select the extended state too. - **When should task lights be controlled?**: Select if this light group should be controlled only when an area first gets occupied, only on area state changes or both. - **Time after the switch will be automatically turned off. (0 = timeout disabled).** - **Media Player devices used for broadcasting** - **Play notifications devices only when on these states**: Notifications will only be played when an area is on this state. Using extended will ensure you don't get notified in rooms you just passed by and not selecting sleep will prevent notifications while on this mode. - **Minimum number of entities of the same device class required to create aggregates.** - **Binary sensor device classes to be aggregated.** - **Sensor device classes to be aggregated.** - **Illuminance threshold for this area**: Magic Areas will create a light binary sensor that will track when the area's aggregate illuminance goes over this threshold. Requires the device class illuminance to be selected for aggregation. Set to 0 to disable. - **Hysteresis for Illuminance threshold sensor**: Hysteresis defines how sensitive the sensor is to changes on its value. A value of zero will flip the sensor state whenever the illuminance crosses the threshold above. Positive values means that the sensor will only change state if the threshold is surpassed by a given amount, expressed in percentage of the threshold set above. Ramping up this value might be useful if you're trying to use this sensor as its own area's light sensor. - **Required state.**: State the area has to have in order to consider turning on the fan group. - **Tracked device class.**: Select which aggregate device class to track for value changes. - **Setpoint.**: Number which the tracked aggregate sensor must be equal or greater in order to turn on the fan group. - **Climate entity**: Climate entity to be controlled. Texts from the code of [jseidl/magic-areas](https://github.com/jseidl/magic-areas). ## Entities - **Binary sensors**: Area State, BLE Tracker Occupancy, Area Health, Light (Calculated), Wasp in a Box - **Covers**: Awnings, Blinds, Curtains, Dampers, Doors, Garage doors, Gates, Shades, Shutters, Windows, Covers - **Fans**: Fans - **Lights**: All Lights, Overhead Lights, Task Lights, Accent Lights, Sleep Lights - **Media**: Media Players, Area-aware media player - **Switches**: Presence Hold, Light Control, Media Player Control, Climate Control, Fan Control ## From the README > Magic Areas is a Home Assistant custom integration that makes your smart home think for itself through rock-solid presence tracking — the foundation for a truly smart home. > > Magic Areas knows when a room is occupied (and when it’s not) and reacts automatically. It turns Home Assistant’s Areas into dependable, presence-aware zones so your home feels alive without you lifting a finger. Instead of building dozens of manual automations, let Magic Areas control your lights, climate, and other devices so that they do just right thing, at the right time. > > - 🕰️ Smart Presence Timeouts: Each area has a configurable timeout for clearing presence after the last motion. If motion is detected again within the timeout, it resets — no abrupt shutoffs. > - ✋ Presence Hold: Creates a switch to manually override presence in an area. Useful if sensors aren’t fully reliable yet or for guests. > - 🕯️ Secondary States: Define subtle room states for more nuanced automations: > - dark / bright: Based on light sensors or sun > - sleep: Tracked by any entity > - extended: When a room has been occupied beyond a set time > - accented: Track presence based on entertainment like media players > - 🏠 Meta-Areas and Hierarchies: Set areas as interior, exterior and assign them to floors. Magic Areas will create meta-areas to track grouped presence (e.g., upstairs occupied). Presence logic and… From the README of [jseidl/magic-areas](https://github.com/jseidl/magic-areas#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Climate](https://vulpo.app/integrations/category/climate.md) - Number: 915 installs sharing analytics; 523 GitHub stars - Connection: Works locally - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: 4.4.2, last updated October 19, 2026 - Domain: `magic_areas` - Source: - Issues: In Vulpo: Light card, Cover card, Fan card, Apple Watch, Control Center Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/jseidl-magic-areas --- - HTML version of this page: https://vulpo.app/integrations/marketplace/jseidl-magic-areas - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml