Requests for version 5

[MWareman]

With network resources gaining the ability to incorporate variable values - I have a small request that we include an additional field for each scene and device. Currently - devices (and scenes) have an ID. They also have a name - and most of us give them a name that is appropriate for the display in the admin console. This may be less than appropriate when used in a network resource.

 

Is it possible to have an additional (optional) 'Alias' field for each device and scene in ISY? This would be accessible thru the REST API as well as via a variable reference for notifications and network resources?

 

Finally - is it possible to consider dropping the ID on export and replacing them with GUIDs - and then dynamically assigning IDs to the incoming GUIDs on import?  This will allow *much* easier copying of resources between ISY devices and thru forums - we won't have to deal with ID conflicts etc. Maybe even store the GUID with the resource - and even add a version counter (incremented each time the resource is changed). 

 

Possible?

 

Michael.

[Michel Kohanim]

Hi Michael,

 

Everything is possible. The only questions are:

1. What's the priority

2. Do we have enough resources

3. Does ISY have enough resources to do this without impacting core functionality

 

The 3rd one is of major concern for me: we keep all node data in memory (that's why you can backup / restore ISY without impacting run time). Adding aliases and GUIDs will have to also be stored in memory which is premium.

 

With kind regards,

Michel