The description assumes you’re using the recorder component. Any value above 7 is just fine!
The code for the automation is actually a “Blueprint”. It is its own thing so you will add a blue print using the code above then as another step create the automation from the blueprint. That’s when you’ll be prompted to fill in all the variables with the entities described above. After that then the automation will show up under “automations”
If you want to be able to “see” the on/off switch you would add the input boolean to your Lovelace dashboard
So, with point 2 I did exactly as you described and that’s where I have a problem I think, I created the automation using the blueprint, I see the additional config added to my automation.yaml but no new automations on the ‘automations’ page. Is that expected?
yeah, I did. perhaps I didn’t do it properly.
I’ve now added the dummy sensor instead and can see the Automation in my automations tab.
I’m now going to leave the vacation mode toggle on and wait for the lights to start freeking out my wife. I’ll know its all working when she start complaining.
Hi @timgiwo, love your idea, it was just what I was looking for. I’ve managed to put in the Blueprint and the sensors, and created an automation. Now my two questions:
where can I tweak the recorder time or check it is bigger then 7 days?
is this directly running when I switch on vacation mode? Or does it start after 0:00 or something? Is there a possibility to check its really running?
hello all.
strange one here!
I’ve set this up recently - 1st time I went away for the weekend this worked a treat.
I used used the mode this weekend and unfortunately none of my lights were triggered (looking at the light history over the weekend confirms this)
how can I debug this? I’ve tried looking at the logs but I couldn’t seen anything of interest.
Ah you’re right! Thank you for raising. “count” of the history stats sensor now appears to reset at the end of the configured duration, so doesn’t keep high values the way it is currently written
Feel free to add to it. I think what they’ve done has value as a seperate history_stats sensor, but trying to get them to revert to old style. You all probably have more experience with it so may be able to add weight to the conversation there.
Since HA has stepped up its game with media players, would those entities also work with replay? Have the radio or TV play in a natural way when you are present?
I am just getting in to Home Assistant and this looks awesome, thanks for the blueprint going to set this up so it works during the holidays.
Quick question, since all states is already recorded in the logs, why do we need separate sensors for this. Can’t the state be pulled from the regular logs for the specific lights?
Unfortunately the states are buried in the HA DB and aren’t easily accessible by blueprints.
The intents of this implementation was to make use of blueprints and common well-supported HA building blocks.
There was another user that was also interested in querying the DB for state changes and has an alternate post here!
The thing that I’m not 100% clear on is the history states. I’ve set up the sensors properly, but when I go into the history page and choose one of the sensors as the entity, it doesn’t necessarily have the correct status. And when I change the state of the light, the status doesn’t change in that history. When I pull one of the sensors up in the history, am I actually looking at the history of it one week ago? What is going on?
