Home automation organization

Hello!

Curious as to how people organize automations (if they do)

I have (tentatively, this is very subject to change) created a numbering system: 0 is temporary (only really used now as I wait for more sensors to arrive so I can get everything set up fully), 1 is location based, 2 is time of day based, 3 is motion sensor based, 4 is door and window sensor based, 5 is triggered by another device, 6 is NFC tags, and 7 is "other"

1 Like

I just name my rules based on the device or subject.

For example, I have basic rules named Laundry Outlet and Office Light.

Rule Machine rules Named Holiday On and Holiday Off (these are automations that run once every 14 days and affects the Office Light basic rule)

1 Like

I have my rules prefixed with numbers,
00-is modes of the hubitat and whole system rules
01 -is daylight time of day rules
04-is security
10's - are first floor rooms
20's - are second floor rooms
30's- are common areas hallways, foyer, garage, basement
50's - are outdoor

3 Likes

I like that idea

I name my rules with clearly what they do. I have to deal with a lot of hubs so this type of organization is important to me. I like your suggestion and I may try that in the future. The more organized you are the better.

2 Likes

Which is exactly why I’m asking lol. As I’m still setting up, it’s easy for me to adapt to a different organization scheme so I’m looking for ideas now, not when I have 50+ that I have to change

1 Like

I start my organization with my Devices. Every device name is a single character indicating the type of device (Lutron, Zigbee, group, virtual, etc.), followed by the location of the device ("Living Room", "Basement", etc.), followed by the specific device description.

As an example, when I look at "β•š Master Bathroom lights", I instantly know it's a Lutron device, in the Master Bathroom, controlling the lights. Similarly, with "~ Office cabinet lights button", I instantly know it's a Zigbee device, in the Office, and it's the button that controls the cabinet lights.

Moving to Apps, I also use a first-letter code for certain types of app: "#" for apps that will send a notification, "∞" for apps with time-based triggers. The rule name then starts with the main device(s) affected, and (when space allows) also spells out the function of the rule.

Example: a Basic Rule named "β•š Pantry light, ~ Basement tool chest light OFF when β•š Basement main lights turns OFF" rather clearly indicates the two devices under control, what will be done to them ("OFF"), and the condition that will trigger that action. Similarly, an RM rule called "~ Living Room W button PUSHED or ~ Living Room E button DOUBLETAPPED" shows the buttons being monitored.

Labelled this way, the devices and apps all sort themselves neatly by type.

What's organization?

1 Like

Most of my device names start with the device type.

For rules, I use emojis to arrange them in logical (to me) groups and try to make the rule names something that reminds me what they do. Temp rules have no emoji so they all end up sorted at the top.

So if you label a rule with this emoji what does it do? :scream:

1 Like

That would be a good one for certain relatives coming for a visit...

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.