Improvements for Homie (V3.1)

[timpur]

Anyone have ideas for homie V3.1?
Some Outstanding Discussions:

• Stats implemented as a Node
• property attribute $interval #53
• Bits that didn't get addressed from Some thoughts beyond v3.0 #62
• Implementation guideline for client/controller developer #51 and What is defined as an announcement? #65
• new Datatype map? (Or use different formats for enum)?  #72

[timpur]

@marvinroger @zephyrr @ThomDietrich @euphi @nerdfirefighter @ingoogni @lorenwest @tripflex

[nicola-lunghi]

#76

[nicola-lunghi]

see the other issues that I've created

#77
#78
#79
#80
#81
#82
#83
#84

[timpur]

Arrays

homie/super-car/$nodes → "lights[]"

homie/super-car/lights/$name → "Lights"
homie/super-car/lights/$properties → "intensity"
homie/super-car/lights/$array → "0-1"

homie/super-car/lights/intensity/$name → "Intensity"
homie/super-car/lights/intensity/$settable → "true"
homie/super-car/lights/intensity/$unit → "%"
homie/super-car/lights/intensity/$datatype → "integer"
homie/super-car/lights/intensity/$format → "0:100"

homie/super-car/lights_0/$name → "Back lights"
homie/super-car/lights_0/intensity → "0"
homie/super-car/lights_1/$name → "Front lights"
homie/super-car/lights_1/intensity → "100"

I was looking at this example and thought to my self, that actually looks complex to subscribe to via mqtt. Wouldnt it be nicer to do this:

homie/super-car/lights/0/$name → "Back lights"
homie/super-car/lights/0/intensity → "0"
homie/super-car/lights/1/$name → "Front lights"
homie/super-car/lights/1/intensity → "100"

Thus you onlt have to sub to homie/super-car/lights/# to get all the node topics, since there all hirarical now.

Maybe also:

homie/super-car/lights/elements/0/$name → "Back lights"
homie/super-car/lights/elements/0/intensity → "0"
homie/super-car/lights/elements/1/$name → "Front lights"
homie/super-car/lights/elements/1/intensity → "100"

Just ideas, tell me your thoughts?

[marvinroger]

homie/super-car/lights/0/$name looks like a $name attribute of the 0 property of the lights node.

[ThomDietrich]

My thought exactly.

Remember that the underscore character is reserved for arrays in topic ids. You could benefit from that.

I'd suggest to discuss this in a specific issue.

[ThomDietrich]

Also could you create an issue to start discussion of the stats improvement?

[nerdfirefighter]

why is lights an array? is it because now at the nodes layer its by node type?

My usage of a range/array is when i have a light strip where i refer to strip[] which is an array of led 0- length of strip. each led in the strip does not have a name they only have a value (which most of the time is a Red:Green:Blue string). i dont think having an name value for each array element is appropriate. if you need a name is should be its own node not a range.

[ThomDietrich]

@nerdfirefighter $name just as most other attributes is not mandatory.

[timpur]

sorry moved to #90

[nicola-lunghi]

Can we create a "development" or testing branch and start putting the "approved" modification in it to see if this is coherent?
for example the "optional" arguments

[timpur]

Have you guys seen https://iot.mozilla.org/wot/, @ThomDietrich

[davidgraeff]

Closing this umbrella issue. See #62.