Closed eigenein closed 4 years ago
Potentially this could also help to get rid of the special "one-off" message type, leaving only read and write ones. Whether it's persistent or not could be put into metadata
Trying to evolve this idea I decided that it's better to add strongly typed fields, either on message or reading level, depending on whether they should be stored per sensor or per reading
Currently all the values are primitives. And for example a reading cannot be:
Also, I still have to implement sensor titles somehow (#10).
A draft idea is to replace the primitive
value: Value
with a HTTP-headers-like set of values. For example, an annotated image could look like:And then renderer picks up everything it's able to render. Automation has to be adjusted too. Perhaps relates to reading transformations (#30).
Open questions: