Skip to content

Commit d92a164

Browse files
authored
updating info.md for hacs (#320)
1 parent 485314a commit d92a164

File tree

1 file changed

+8
-24
lines changed

1 file changed

+8
-24
lines changed

info.md

Lines changed: 8 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,10 @@
1-
# Magic Areas custom_component for Home Assistant
2-
Tired of writing the same automations, over and over, for each of your rooms? Annoyed that some entities can't be tied to `Areas` in the `Area Registry`? Would like to have a single `motion` sensor that is grouped to all your other motion sensors in that area? What if all (most) of your `sensor` and `binary_sensor` entities had aggregates (grouping/average), PER AREA?
1+
# Magic Areas for Home Assistant
2+
![Magic Areas](https://raw.githubusercontent.com/home-assistant/brands/master/custom_integrations/magic_areas/icon.png)
33

4-
If you think all of the above features are freaking awesome, **Magic Areas** is here for you!
4+
![Build Status](https://github.com/jseidl/hass-magic_areas/actions/workflows/validation.yaml/badge.svg) [![Discord](https://img.shields.io/discord/928386239789400065.svg?color=768AD4&label=Discord)](https://discord.gg/8vxJpJ2vP4) [![Latest release](https://img.shields.io/github/v/release/jseidl/hass-magic_areas.svg)](https://github.com/jseidl/hass-magic_areas/releases) [![GitHub latest commit](https://badgen.net/github/last-commit/jseidl/hass-magic_areas)](https://GitHub.com/jseidl/hass-magic_areas/commit/) [![GitHub contributors](https://badgen.net/github/contributors/jseidl/hass-magic_areas)](https://GitHub.com/jseidl/hass-magic_areas/graphs/contributors/)
55

6-
## Features
7-
* Uses multiple type of sensors for determining presence on an area.
8-
* `media_player`, `binary_sensors` ([all listed types](https://www.home-assistant.io/integrations/binary_sensor/)) are supported
9-
* Loads areas from `Area Registry` -- _No need of handling them elsewhere!_.
10-
* Support exclusion of entities.
11-
* Support inclusion of entities not in the Area Registry (i.e. integrations that don't define an `unique_id`).
12-
* Automatic turn climates and lights on! (All or user-defined).
13-
* Specify a `disable_entity` for when lights *shouldn't* turn on (e.g. daytime, high luminance etc)
14-
* Specify a `sleep_entity` and `sleep_lights` to have only your accent lights turn on late in night
15-
* Automatic turn off lights, climate and media devices when a room is clear
16-
* Creates a `Health` sensor (triggered by `binary_sensors` with `problem`, `smoke`, `moisture`, `safety` and `gas` device classes) for each area
17-
* Creates a `Presence Hold` switch to manually override area presence
18-
* Creates aggregation sensors for your `binary_sensor` such as:
19-
* Motion sensors
20-
* Door sensors
21-
* Window sensors
22-
* Leak sensors
23-
* Creates average (and sums) sensors for all your `sensor` needs
24-
* Creates global (interior/exterior) aggregate and average sensors
25-
* Area-Aware Media Player: Forward `media_play` events to media player entities in occupied areas only!
26-
* Light Groups: Automatically creates light groups for all ligths in an area
6+
Tired of writing the same automations, over and over, for each of your rooms? You wish Home Assistant just figured out all entities you have in an area and **magically** started being smarter about them?
7+
8+
Magic Areas is the batteries that were missing! Would like to have a single `motion` sensor that is grouped to all your other motion sensors in that area? What if all (most) of your `sensor` and `binary_sensor` entities had aggregates (grouping/average), PER AREA? Would you like for lights and climate devices to turn on and off **MAGICALLY** whenever an area is occupied/clear?
9+
10+
If you think all of the above features are freaking awesome, **Magic Areas** is here for you!

0 commit comments

Comments
 (0)