Magic Areas is a Home Assistant custom integration distributed through HACS that turns the HA Area Registry into presence-aware zones. Each configured area gets its own config entry and a set of platform entities (binary sensor, sensor, switch, light, fan, cover, media player) that provide presence tracking, secondary states (dark, bright, sleep, extended, accented), and grouped controls for lights, fans, covers, and media players. It also implements meta-areas (Interior, Exterior, Global, Floors) that aggregate child area states with any/all/majority modes, climate control, Wasp-in-a-Box presence validation, BLE tracker monitoring, sensor aggregation with threshold/hysteresis, and an area-aware media player for TTS routing to occupied rooms. The architecture follows standard Home Assistant component conventions: setup, unload, and config migration live in __init__.py, UI configuration in config_flow.py, a large central const.py defines the configuration contract, base/magic.py holds the MagicArea and MagicMetaArea domain objects, and platform modules implement entity types. Presence is computed from device trackers and binary sensors with keep-only whitelists and clear timeouts; registry listeners reload areas when areas, devices, or entities change. The project is actively maintained, pinned to HA 2026.8.1+, and ships an extensive pytest suite plus GitHub Actions CI running against HA stable and beta with HACS and hassfest validation. Drift is moderate: the manifest lists zigbee2mqtt under after_dependencies even though it is not a standard HA integration domain, several translations are empty or missing newer feature keys, docs and translations still reference legacy feature names, broad exception handling hides failures, and many pylint checks are disabled. The most self-contained, reusable pieces are the ReusableTimer helper, the threshold/hysteresis validator, and the entity-registry cleanup utility.