Naming Conventions for

[gReatAutomation]

Any recommendation for naming conventions for User specific Scheduled and Triggered items?

[kblagron]

Any recommendation for naming conventions for User specific Scheduled and Triggered items?

I probably should have some, but just looked - For the most part, they are named by the device scheduled/triggered, and then what the action is, but I am definitely not consistent.  I don't have a ton of events- about 15 scheduled, and about 20 triggered.  I am usually a bit wordy with them (15 - 25 characters) since usually you set them up and don't mess with them much after that.  I do that so I will remember what they do a year or so later.

[Dean Roddey]

Keep in mind that they have the descriptive text inside them that you can provide more info with. At some point I'd like to get hover support in the browser, and you could hover over them and see that info.

[gReatAutomation]

I wanted to loop back on this. After much back and forth, I decided to derive a naming/organization system modeled after the Microsoft Group Policy Editor:



I derived a similar structure. Rather than organize Schedules or Triggers by "room" I found it easier to associate them with the things that were impacted: Comfort, Lighting, Messaging, etc.

[Dean Roddey]

I would tend to make them a bit less wordy and keep the longer description inside the event. But, as long as the names are unique that will work. Just keep in mind that what you see in the browser isn't just a description, it's the actual unique id of the event, and if you change that you break any references you might to the event elsewhere.