Please :star: this repo if you find it useful
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:
- light
- cover
- media_player
- All domains for which entities have status on
or off
than can be turned on/off with service homeassistant.turn_on
and homeassistant.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.
~/.homeassistant
for instance), create a directory custom_components/presence_simulation
and put the code in it.~/.homeassistant
for instance)git clone https://github.com/slashback100/presence_simulation.git
. It will create the directory custom_components/presence_simulation
NB: it can also be added as a custom repository if you have an issue with above procedure
homeassistant.turn_on
and homeassistant.turn_off
. You can also setup several entities, separated with ','You can edit these configurations afterwards by clicking on Options in the integration screen.
The component will create an entity called switch.presence_simulation
. This entity will be set to on
when the simulation is running. off
otherwise.
You have 2 ways of launching the simulation:
Toggling the switch.presence_simulation
will toggle the presence simulation.
Three services are available:
The service presence_simulation.start
will start the simulation and set the switch.presence_simulation
entity to on
.
Optionally, you can reference a list of entities, a delta or choose to restore the states if you want to override the component configuration:
entity_id:
- group.outside_lights
- light.living_room
- light.hall
delta: 5
restore_states: True
random: 300
The service presence_simulation.stop
will stop the simulation and set the switch.presence_simulation
entity to off
.
The service presence_simulation.toggle
will start or stop the simulation, depending on the current state of the switch.presence_simulation
entity.
Liked some of my work? Buy me a coffee (or more likely a beer)
This is a bit of an edge case, but...
Frequently we're away from home for an extended period when there is a public holiday during the vacation. It's a bit strange when e.g. on Xmas day which happens to be a Wednesday the lights follow a standard Wednesday schedule instead of a weekend one.
For this sort of thing I am using the binary sensors from the workday platform, where you can have a sensor saying that in your jurisdiction you have a holiday today or there will be one tomorrow.
It would be great if the presence simulator had an option to simulate particular days of the week depending on the status of whether today is a holiday or tomorrow is a holiday -- usually some combination of last week's Friday/Saturday/Sunday.
Hi, is it possible to add more details to the logbook when e.g. a light gets turned on by the simulation? Sometime I'm wondering why my light was on and nobody was at home and then I realize that the simulation was on ^^
Add possibility to configure several entities in the default configuration (#62) Add Polish translations
homeassistant-components homeassistant historic presence-simulation hacs home-assistant home-automation presence simulation