User changeable device GUID.

[ivx 3]

Hi,

 

Currently any API calls or even historic energy data related to device ID.

All is good as long as you don't need to replace device.

If you need to replace old device, you need to rewrite all scenes, quick apps which are related to it.

If there were user settable GUID id, no code rewrites needed, also energy data continues to work ok when device replaced.

 

For example:

 

Scene condition now

   conditions = { {

      id = 83,

With proposed GUID   

 conditions = { {

      guid= 'e71d1a45-cee8-4846-bcb8-5dadf2ba6665',

 

Some calls 

fibaro.call(88,'turnOn')        ----> fibaro.call('e71d1a45-cee8-4846-bcb8-5dadf2ba6665','turnOn')

fibaro.getValue(83,"value") ---->fibaro.getValue('e71d1a45-cee8-4846-bcb8-5dadf2ba6665',"value")

....

Offcourse there may be totally new methods for calling GUID values, if to hard to accept same time old ID and GUID for old methods:

fibaro.callGuid(

fibaro.getValueGuid(

or new method deviceIdFromGuid()

fibaro.call(deviceIdFromGuid( 'e71d1a45-cee8-4846-bcb8-5dadf2ba6665'),'turnOn')

 

 

Adding new device just generates random guid, but later user cand change it as needed(replaced device to uses old device guid).

 

 

Edited October 30, 2023 by ivx