This Home Assistant component aim to provide a presence simulation in your home while you are away. It will turn on & off lights, switches, covers... based on your history.
It will look in the DB for the states history of all the entities configured in the component for a period corresponding to a delta variable defined in the component.
It will apply to the entites the same state (and some attributes like brightness and rgb_color) as it was delta days ago, in order to simulate your presence.
If the service is running longer than the number of days defined as the delta, the component will simply be reset and start over, until the stop service is called.
Supported entities domains:
lightcover- All domains for which entities have status
onoroffthan can be turned on/off with servicehomeassistant.turn_onandhomeassistant.turn_off(automation,switch,group...).
The history integration must be activated - which it is by default. The period kept in the DB should be bigger than the delta used in the simulation. The default number of days kept is 10 and this can be configured with the recorder integration.
Although having your lights take_over_control is enabled
This integration is both fully configurable through YAML and the frontend. (Configuration -> Integrations -> Presence Simulator, Presence Simulato -> Options) Here, the options in the frontend and in YAML have the same names.
# Example configuration.yaml entry
presence_simulator:
lights:
- light.living_room_lights| option | description | required | default | type |
|---|---|---|---|---|
name |
The name to display on the automation switch. | False | "default" | string |
lights |
List of light entities for Presence Simulator to automate (may be empty). | False | [] | list |
Full example:
# Example configuration.yaml entry
adaptive_lighting:
- name: "default"
lights: []
automations: []
automations_filter: mqtt
playback_days: 7
interval: 90