Device database attributes (Device Properties)

[evarsanyi]

It would be nice if there were a seperate name/attribute for the controlled load vs the device itself; in my installation the actual switch is frequently not related obviously (location wise) with the load its controlling.

 

Example: there's a 4 wide j-box with 3 switchlincs and a keypad linc at a central location. At other exits from the area are 2 wide boxes. The immediate area has 4 loads and the the switches in the 4wide box control all of them as well as some outliers that are visible (outside landscaping). When I set up the database for this area I end up with 11 insteon devices, 5 of which have loads that are related to the convenience of wiring rather than the locations.

 

I'm using a convention of of 'Location - Load' in naming devices but it might be cleaner if one could specify the 'load' as a seperate attribute and talk about it in scenes rather than talking about the switch. A comment field might be nice too to include wiring notes/etc. For keypadlincs an attribute describing what's written on each controller button distinct from the name.

 

Just an idea, this can all be done by overloading the device name with some discipline.

[Michel Kohanim]

evarsanyi,

 

Very good idea ... will review it in our next requirements meeting.

 

At the moment, the only issue I see with this is the increase in size of our nodes (in ISY). Of course, we could alleviate this by having a "parallel" database with extra/descriptive information; the main question is how long it would take us.

 

Thanks so very much for your continued feedback,

With kind regards,

Michel

It would be nice if there were a seperate name/attribute for the controlled load vs the device itself; in my installation the actual switch is frequently not related obviously (location wise) with the load its controlling.

 

Example: there's a 4 wide j-box with 3 switchlincs and a keypad linc at a central location. At other exits from the area are 2 wide boxes. The immediate area has 4 loads and the the switches in the 4wide box control all of them as well as some outliers that are visible (outside landscaping). When I set up the database for this area I end up with 11 insteon devices, 5 of which have loads that are related to the convenience of wiring rather than the locations.

 

I'm using a convention of of 'Location - Load' in naming devices but it might be cleaner if one could specify the 'load' as a seperate attribute and talk about it in scenes rather than talking about the switch. A comment field might be nice too to include wiring notes/etc. For keypadlincs an attribute describing what's written on each controller button distinct from the name.

 

Just an idea, this can all be done by overloading the device name with some discipline.

[Michel Kohanim]

evarsanyi,

 

I just wanted to let you know that we added a rudimentary properties object to capture:

1. Location

2. Is Load

3. Notes

 

for each and every node in the tree (except groups). I hope this makes it easier for you to capture the desired information. This will be available in 2.4 (Monday 08.06.2007).

 

Thanks so very much for the suggestion,

With kind regards,

Michel

 

 

It would be nice if there were a seperate name/attribute for the controlled load vs the device itself; in my installation the actual switch is frequently not related obviously (location wise) with the load its controlling.

 

Example: there's a 4 wide j-box with 3 switchlincs and a keypad linc at a central location. At other exits from the area are 2 wide boxes. The immediate area has 4 loads and the the switches in the 4wide box control all of them as well as some outliers that are visible (outside landscaping). When I set up the database for this area I end up with 11 insteon devices, 5 of which have loads that are related to the convenience of wiring rather than the locations.

 

I'm using a convention of of 'Location - Load' in naming devices but it might be cleaner if one could specify the 'load' as a seperate attribute and talk about it in scenes rather than talking about the switch. A comment field might be nice too to include wiring notes/etc. For keypadlincs an attribute describing what's written on each controller button distinct from the name.

 

Just an idea, this can all be done by overloading the device name with some discipline.

[evarsanyi]

That's great! Is 'is load' a string attribute (that I can store the load location in) or a boolean?

 

Thanks,

-Eric

[Michel Kohanim]

Eric,

 

Hi. IsLoad is boolean but you also get to have Location and Notes which are both free form strings.

 

With regards,

 

That's great! Is 'is load' a string attribute (that I can store the load location in) or a boolean?

 

Thanks,

-Eric