[SUGGESTION] Conventional usage of Description field
Posted: Sunday 25 August 2019 17:19
Ciao,
he device Description field has recently being used for external/other systems as a configuration field using a JSON format.
this is really cool! but I think there are now few systems using it and we risk to make mess on it.
I would suggest to create a conventional key structure in order to keep it clean and simple.
For instance:
i use it for interfacing KNX via nodeRed, so my description field would "keyed" under a "KNX" key
for Alexa via Alexicz could be keyed under "Alexicz"
for Alexa via NodeRed (and Alexa-Remote2 node), could be "AlexaRemote"
and so on....
So... if you have domoticz control a KNX system amd voice command via Alexicz you could have:รน
{"KNX":{"dstgad":"0/0/0"},"Alexicz":{"Alexa_Name":"MyLight"}}
would you like it?
he device Description field has recently being used for external/other systems as a configuration field using a JSON format.
this is really cool! but I think there are now few systems using it and we risk to make mess on it.
I would suggest to create a conventional key structure in order to keep it clean and simple.
For instance:
i use it for interfacing KNX via nodeRed, so my description field would "keyed" under a "KNX" key
for Alexa via Alexicz could be keyed under "Alexicz"
for Alexa via NodeRed (and Alexa-Remote2 node), could be "AlexaRemote"
and so on....
So... if you have domoticz control a KNX system amd voice command via Alexicz you could have:รน
{"KNX":{"dstgad":"0/0/0"},"Alexicz":{"Alexa_Name":"MyLight"}}
would you like it?