Media Player Script Blueprint 2023-12-09 by SirGoodenough
This provides a way to play canned media files with the big
long list of YAML entries but keep the main script or automation clean.
All that is required there would be a simple line like:
'- service: script.media_player_doorbell_sound'
Community link for this blueprint
🗿Notice👮🏿♂️:
-
Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
-
I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
-
I & my license also require attribution as a link back to the original should you use this code in your own creation.
-
Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
Import to Home Assistant
Click to import this blueprint directly into your Home Assistant instance.
Configuration
Requires 3 inputs to configure
Source Code
View on GitHubDetails
Explore More
Related Blueprints
More device control automations you might like
Motion-activated Light
Example Automation Blueprint
On-Off schedule with state persistence
On-Off schedule with state persistence
A simple on-off schedule, with the addition of state persistence across disruptive events, making sure the target device is always in the expected state. 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. ℹ️ Version 2021.10.26Simple Safe Scheduler
Simple Safe Scheduler
Scheduling a periodic action in Home Assistant might be trickier than what it looks at first glance. Not only the available automation triggers are limited to only time-based schedules (requiring the user to either use template triggers or install additional integrations for more complex scheduling options), but they also do not guarantee that the automation is executed at the provided time. As an example, let's assume automation A is scheduled to run at 12:00. If the Home Assistant server goes down at 11:59 due to a disruptive event (e.g. power outage, planned maintenance, hardware failure etc.) and comes back up at 12:01, the A automation run scheduled for 12:00 would simply be skipped, without any warning to the user. The Simple Safe Scheduler blueprint tries to mitigate scheduling limitations in Home Assistant by providing an easy interface to configure periodic actions, with built-in safety checks to ensure the action actually runs even in case of a disruptive event. The configured automation acts as a simple scheduler, allowing to flexibly program any kind of action based on the following parameters:- Time of the day (dynamically provided as an
input_datetimeentity); - Day of the week (multiple days can be selected);
- Week frequency (allowing to schedule the action to run i.e. every 2 weeks).