Vacation lights, ie replay from history

[tomk (Tom)]

Hi,
So there has been many things written about replay from history sensor, however all of those are touching on using “ON” state, and nothing more. There is a lot of kung-fu with node red etc … But can somebody please explain how to for example use history sensor with basic automation script firing every minute (or other interval), to set light to given state, brightness and colour ?

A ready script would be nice, but I think we all would like to learn more about history_stats and how to use it for other things and documentation is not very helpful here.

[tom_l]

@tomk

But can somebody please explain how to for example use history sensor with basic automation script firing every minute (or other interval), to set light to given state, brightness and colour ?

What is a “history sensor”?

You could use an SQL sensor to get the state of an entity x days ago (where x is less than your purge_keep_days, which is 10 days by default). You would need one of these sensors for every entity you want to control. Then the automation would look like this:

trigger:
  - platform: state
    entity_id: 
      - sensor.my_light_3_days_ago
      - sensor.my_switch_3_days_ago
      - etc...
    not_to:
      - unknown
      - unavailable
action:
  - service: "light.turn_{{ states('sensor.my_light_3_days_ago') }}"
    target:
      entity_id: light.my_light
  - service: "switch.turn_{{ states('sensor.my_switch_3_days_ago') }}"
    target:
      entity_id: switch.my_switch
  - service: etc...

[finity]

This is the closest thing I know of using HA configuration to accomplish it. I used it as a basis for what I’m currently using:

Vacation Lighting - Replay Historical Lighting

I’ve taken the concept others have suggested on this forum and created a blueprint to replay lighting behavior. Credit to this awesome community! Description: A blueprint to replay the same lighting behavior from the previous week. For each light that will be controlled as part of your vacation/away lighting, a ‘history_stats’ sensor should be created to track the historical behavior. The blueprint maps each ‘history_stats’ sensor to its corresponding light entity then replays the on/off beh…

or there’s an integration that I tried. I like the one I’m using better but it looks like it works OK too:

GitHub - slashback100/presence_simulation: Home Assistant Presence Simulation

you can install it via HACS.

[tomk (Tom)]

@tom_l

What is a “history sensor”?

yeah, I meant “history stats”. Sorry it was around 2 am.
Anyway. How to get a colour and brightness out of your SQL sensor ?

[tom_l]

I don’t know how to get the attribute value x time ago with SQL. I’m sure it can be done, I’m just not sure how.

Might be worthwhile starting a new topic with a more relevant title like “How do I use an SQL sensor to retrieve a past attribute value?”.

That should have more of a chance of attracting the SQL experts.

[tomk (Tom)]

@tom_l

Might be worthwhile starting a new topic with a more relevant title like “How do I use an SQL sensor to retrieve a past attribute value?”.

That should have more of a chance of attracting the SQL experts.

roger.

[tomk (Tom)]

as @tom_l suggested, let’s use a real world entity

light.parents_bathroom_main_light