How does every plan or map Thier automations

Configuration
1

I’m starting think about all the things I still manually do in HA. So it got me wondering how ppl design Thier automations.

I was going to start writing out the main daily automations, then start looking at what automations run during those specified times etc.

Any ideas on what others have done. I still think folder structure would help with automations etc…

2

I’ve split my automations off into several categories:
contacts - non-door contact sensors (I’ve got one on my mailbox)
doors - door contacts including warnings when doors are left open or opened when we’re gone
lighting - synchronizing sets of lights and switches
motion - motion detection warnings
presences - people movement and associated notifications
remotes - physical buttons for various lights, scenes, etc.
ring - doorbell and outside garage camera/light
timing - time of day, sun position, and timed switches (that turn off after a set time)
These are all separate .yaml files in my /config/automations/ folder.
There’s also a line in my /config/configuration.yaml file as follows:
automation yaml: !include_dir_merge_list automations/

3

I designed my config around several “categories” eg. Climate, Presence, Light, Fan, Alarm etc. All of my automations are named to reflect the category. All my scripts, automations, templates, helpers etc revolve around those categories. I’ve split my config and use packages to organize all the YAML stuff that isn’t automations or templates. Those are kept in subfolders named after the category. Keeps everything organized and easy to find.

Automations and scripts are always named to reflect the category.

- id: alarm_announcements
  alias: '[Alarm] Announcements'
  description: 'House alarm TTS announcements.'

That way they stay sorted in the UI and in selectors.

image

You can have a look at my config to see the complete file structure.

4

I did this as well.

But I’m hoping I can move them to packages maybe. But unsure (don’t think) they can be updated from the gui if I do that

5

And i do them based on area…

  • hallway
  • living
  • bedroom
  • kitchen
  • etc

and then a few ‘generic’ not really bound to a specific area

6

Thanks all, good food for thought

7

how do you remember what automations do what, especially when you are creating overlapping automations??

8

in my case, i name my automations starting with the area :wink:

9

I use comments in the automation to describe the specific action(s) and trigger(s), etc.
This is OK as long as you’re looking at the actual script for the automation.
I also try to name my automations so that the general concept is fairly clear from the name.
This can result in longer names, but it does aid in remembering what it was supposed to do when I’m looking at it 6 months later :slight_smile:

10

yeah ok thats what i what i was thinking as well. Thank you !