WTH not include more Blueprints with Home Assistant core for common simple automations (and maybe even present them as automation suggestions)?

Month of "What the heck?!"
1

Why not have Home Assistant core include a larger set of curated/vetted set of automation Blueprints?

When a user today select “Create automation” under Automations & scenesthey are by default greeted by two Blueprints made by the Home Assistant’s core team:

I seen a lot of new users stating that it can be hard to know where to get started with basic automations after installation of Home Assistant OS, so wondering why not have Home Assistant core by default include a few more essential automation Blueprints made by the Home Assistant’s core team?

As such would it not be a good idea to have Home Assistant core include a few more easy and effective automation Blueprints that have been curated “By Home Assistant” (i.e. Home Assistant core team)

Suggest adding a few more default automations, and I would recommend for example:

  • Toggle lights ON or OFF at Sunset and Sunrise.

  • Turn ON or OFF a switch/fan when a temperature goes over a certain degree.

  • Lock doors and turn off devices when everybody has left the house using Home Assistant.

  • Real-Time Smoke Detection with instant Notifications to the Home Assistant Companion App.

  • Notification reminders which garbage bin will be collected (garbage collection notification).

  • Notification on weather forecast event like rain or snow (severe weather alerts).

  • Notification when dishing machine finished its job using an enery meter (power plug)

  • Notification when washing machine finished its job using an enery meter (power plug)

  • Notification when tumble dryer is finished its job using a vibration sensor.

  • Notification reminders when doors/garage are open for too long.

  • Notification reminders when some lights and an iron being turned on for too long.

  • Notification reminders for feeding pet (feeding scheule for fish/bird/lizard/snake, etc.).

I think it would also be a good idea to somehow guide or describe in the UI what scenes and group helpers does if can be used in any of those automations (as well as maybe stearing users to create scenes and group or other some other commonly used helpers first).

  • Turn ON or OFF a group of lights at a specific time using a scene.

  • Toggle ON/OFF light when press a button.

  • Run a good night rutine when press a button.

Alternativly add a bunch of vetted and cherry-picked community-made Blueprints from the Blueprint Exchange (which could be overwhelming), but have those made “By the community” listed at the bottom while listing the default ones “By Home Assistant” at the top above those.

If possible perhaps add some filtering to high-light any such automation Blueprint where can see that the user has already added some devices with the minimum required device types entities?

PS: Sligtly off-topic but as a partial workaround can use this custom AI Automation Suggester to get ideas on what to automate → https://github.com/ITSpecialist111/ai_automation_suggester

2

Slightly off topic: Re automation for clothes-dryer-done: I’ve not been very successful w vibration sensors on dryers. But REALLY good luck in using temperature on dryer exhaust vent.

But anyway, I fully support adding additional automation examples via blueprints.

3

Such a solution does not work on heat pump dryers as they do not have an exhaust vent. A heat pump dryer (which more or less been standard in Europe since about 10-years or so) works as a closed loop system by heating the air using it to remove moisture from the clothes and then reusing it once the moisture is removed.

1 Like
4

Another action that would I’d imagine catch people is playing media to a certain volume; e.g. play something at maximum volume and attempt to put it back after and wonder why this doesn’t work as expected:

  • Get media player volume and store in variable
  • Set media player to maximum volume
  • Play media
  • Set media player volume back to that in stored in variable

That you need to have a wait for trigger to work as expected:

  • Get media player volume and store in variable
  • Set media player to maximum volume
  • Play media
  • Wait for media player to return to idle
  • Set media player volume back to that in stored in variable

Having a standard blueprint visible like this “Play media at set volume” would reduce the frustration of why the setting volume doesn’t work as expected…

2 Likes