I suspect the idea was that if I set 60 seconds between alerts, for example after 60 seconds the initial door open alert is triggered and I close the door immediately after the alert, the last alert waits for a 60 second timeout and is not immediate.
That is possible as well.
Does HA pop the indication that the door is closed again right away. Not the alarm system itself, but the binary sensor that is the trigger itself.
As you can maybe tell, I got this blueprint, my first, by adapting a google_translate version someone else had and I donāt actually use this myself. I just spool one to test it when needed. sounds like this is needed.
I should be able to change it to die when the sensor dies, that would be cleaner.
Yes, it would be good for him to react immediately after closing. Itās an otherwise good plan. Thank you
Edit Blueprint because the home of my blueprints have moved from GISTS to a Github repo. Please use the new links now in the original post.
Seems this blueprint is the same as your keypad? Did a copy paste mishap when moving repo?
I would like to use this script https://community.home-assistant.io/t/script-to-resume-radio-tunein-and-spotify-after-tts-on-google-home-speakers/326634 when I leave open the door, so the music resumes after the TTS. Any idea how to do that?
1 Like
oops
. Just moved everything from GISTs to a REPO, I must have missed that.
With 8 blueprints it was an all day endeavor.
Iām on it.
Thanks for letting me know.
ā¦A Few Moments Laterā¦
All fixed.
1 Like
Letās just say there is no way in heck that Iām going to try to convert a 400 line script with about 50 variables, some that are lists, to a blueprint and merge it with the 150 line blueprint I have now. Mostly because it is something I would not use. I donāt use Tune-in or Spotify at allā¦
Sorry.
But if you want to take it on or convince that guy to take it on, I would advise where I can.
@rudy12767
Hi, here is that guy 
The way Iāve set up my variables is also why Iām not sure if I can create a blueprint out of my script. I basically also donāt see the need, because, as I see it, a blueprint is to make it easy to setup difficult things multiple times.
I do see other advantages of a bleuprint, the way they can be shared, imported and updated through the community forum are very nice.
I think @rudy12767 can import your blueprint and change the tts part to a script call to my script, however that will be overwritten when the blueprint is updated.
I also donāt feel like forking your blueprint and adapting it to my needs since I donāt use it myself, and then will have to maintain it and check for changes and everything.
@rudy12767
You can import the blueprint and replace this part
- service: tts.cloud_say
data:
entity_id: !input 'speaker_target'
message: !input 'announcement_message'
options:
gender: !input 'speaker_gender'
language: !input 'speaker_language'
with
- service: script.google_home_say
data:
tts_target: !input 'speaker_target'
tts_message: !input 'announcement_message'
That will probably work, but as I said, that will be overwritten when you import the blueprint again.
And it will not use the language and gender settings, you will have to set those in my script (or leave default for the settings of your tts service)
Dear Sir_Goodenough and āthat guyā, thanks for the imput both.
If you want to put this together like he suggested, I have no problem with you posting it back in to the exchange as long as you add links back to the originals in your descriptionā¦
- 2022-2-15 - added link to new blueprint.
- 2022-3-10 - added link to new blueprint.
- 2022-4-17 - added new blueprint link to family
- 2022-04-11: Add multiple to Speaker Selection and changed minimum HA to 2022.4.0
New Version today.
I did this a couple of days ago but released it today because of the problems with 2033.5.0 and 2022.5.1 releases not allowing Blueprint Imports.
Please Click the 
at the end of the Top Post if you find this Useful
- 2022-05-05: Updated for 2022.5.0 HA. Added Markdown to !input Descriptions.
Updated the āother blueprintsā links.
How do I set it up to let it know which window or door is open (entity/device)?
You use the blueprint to make an automation that uses the code in the blueprint.
Simply add a new automation in the automation editor and use this blueprint. It will ask you for the entities.
I have a problem with the automation.
When i set it to remind me that a door/window is open after 120 seconds. It keeps repeating this every 2 minutes.
At night i keep doors open, verry irritating @ night.
Mayby ad a timespan when this may happen, or a option to not repeat the announcement would be a nice addition to the automation
That is how it was designed. Kind of meant for doors that are normally closed, and it will keep nagging until you close it again.
If something else is desired, the Blueprint would need modification. Perhaps I can take that on as a winter project, but I do not have the ability to do this at this time.
If you want to test and suggest modifications, I could add them in for others and I will give you credit.
It would also be VERY easy to stop and disable the automation during certain hours with a separate automation.
November 30, 2022 > Update. Added ZHA Cube Controller version to library.
December 11, 2022 > Update. Added Device Tracker Blueprint to the list.
- 2022-12-12: Add Update Method Note, minor code change.
-
- Name of Blueprint may have changed meaing you have to re-download with a new link.
-
- If name changed, it is similar. Variables have not changed.
2023-01-26 Added new Bluprint
Zigbee2MQTT Aqara Magic Cube T1-Pro CTP-R01 Xiaomi Lumi cagl02
This Blueprint gives you literally hundreds of actions available on the new Magic Cube.
New Version:
Changelog
- 2023-03-01: Add Author Tag. Bump HA required Version to 2023-3-0
Hello! Is it possible to make him speak only if the door is open? Now heās constantly talking when the door opens and closes. Thanks
Change the closing messageā¦
final_message:
name: Final message
description: 'What to say when door is closed.
This can be set to "" if you do not want a message after the sensor is reset.'
default: Thank you for closing the barn door.
1 Like
strong text
I didnāt understand how a little.
Did I correct it correctly?
alias: open door
description: ""
use_blueprint:
path: SirGoodenough/door_open_tts_cloud_say_announcer_nabu_casa_required.yaml
input:
door_entity:
- binary_sensor.datchik_dveri_v_dom_contact
speaker_target:
- media_player.googlehome2753
speaker_gender: female
speaker_language: ru-RU
announcement_message: Open door?
final_message:
name: Final message
description: Thank you for closing the barn door.
default: Thank you for closing the barn door.
start_time: "09:00:00"
end_time: "22:00:00"
cooldown: 40
You should not have had to edit any yaml at all. The blueprint needs to be in the original config to work.
You need to have an original version of the blueprint again (delete it and download a new copy if you need to.)
When you have that back where it was, go into the automation that you created while initializing the BluePrint actions. That is where you can edit what it says an open and at close properly.
Then delete the old calling automation.
You can open the old one in the automation UI editor if you like as well, but I suggest it may be better to delete the old and build a new one.
I explained it wrong. Automation works correctly!
I would like to receive messages only if the door is opened more than the set time.
Now it works like this:
Opened and closed the door = message ā1 came
Opened the door, time passed = received message ā2. After I closed the door, I received message ā 1.