[SUGGESTION] Conventional usage of Description field

Use this forum to discuss possible implementation of a new feature before opening a ticket.
A developer shall edit the topic title with "[xxx]" where xxx is the id of the accompanying tracker id.
Duplicate posts about the same id. +1 posts are not allowed.

Moderators: leecollings, remb0

Post Reply
User avatar
emme
Posts: 909
Joined: Monday 27 June 2016 11:02
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Milano, Italy
Contact:

[SUGGESTION] Conventional usage of Description field

Post by emme »

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? :P
The most dangerous phrase in any language is:
"We always done this way"
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest