Thanks for fixing the link.
But now the “concern” … oh… doc enhancement request?
If the attribute does not have any possible values (for example, “battery”), you would just use the attribute name.
This is inaccurate and unncessary, IMHO: The Attribute
capability.battery.battery most certain does have “possible values”. It has a value from
0 to 100 representing the percentage power level of the battery.
The syntax or semantic problem isn’t yours, it is the titles of the Capability Document:
I recommend “
[possible values]” column header be changed to “
[data type, valid enumerated values, or valid range]” or something similar.
The “no value” syntax of
subscribe() is valid for all Attributes, even if they don’t have an enumerated list of “possible values”. Without a value name, the subscription applies to (and fires upon) any change in the value of the Attribute. (Which you do describe in the next sub-section Subscribe to All Device Events.