Naming Devices and Scenes

[jrini]

I have been looking through the UDI WIKI and Forum and have not been able to find any specific set of rules for naming Scenes and/or Devices. Do any rules exist? Where do I find them?

[oberkc]

No rules that I am aware of, other than those you impose upon yourself. I suspect, however, that there is a total character limit, and may be some off-limit characters, but such limits will become self-evident should you ever violate them (I don't know what they are, off-hand).

 

I have developed my own naming convention: "RRR DD Description", where RRR is the three-character designation for room, the DD is a two-character designation for device type.

[wswartz]

I too looked for some suggestions on naming conventions when I first started and couldn't find any either.

 

For devices, I came up with was this:

Room.XX.Description

where:

Room = is just that

XX = device type - SD: Switchlinc Dimmer, SR: Switchlinc Relay, KP: Keypadlinc etc.

Description = describes the fixture or function

Examples:

Bedroom.SD.Accents

Basement.SR.Pantry

Office.KP.Overheads

 

For scenes, I use:

Scene.Location.Description

Examples:

Scene.Basement.StairsOnOff

Scene.GameRm.WallLights

Scene.Chickens.CoopLight (yes, our chicken coop is Insteon enabled!)

 

Would be interested in what others use for naming conventions.

 

Bill

[jrini]

I worked with many real time systems before I retired. I am just wondering if the UDI system has a name and documented rules.

[arw01]

For devices I tend to just use the name with underscores for spaces and put oh on overhead lights at the end. With the Isy using numbers internally, you are free to rename anytime and not have to repair your programs.

 

Scenes tend to be the same as the device with _sc on the end. Programs also share the name of what they control with _pr appended.

 

For variables I have I for integer and s for state. Helps me keep it straight.