When implementing drivers for devices that have fixed functionality (energy meters, standalone thermostats, etc) there should be a way for these devices to publish tags for their standard points, in other words for a thermostat, it should be able to publish its room temperature with all the appropriate Haystack tags for that info.
In my opinion, whatever mechanism is put in place should support arbitrary metadata publishing, but we should determine a standard for enabling Haystack tagging information to pass cleanly through the platform.
Possible solutions to discuss include allowing arbitrary metadata to be published with each scrape, and/or to enable the master driver to only publish the extended metadata once upon startup.
Look forward to discussing this and finding a solution that supports a variety of use cases.
zfsamzfsam
commented
4 years ago
When implementing drivers for devices that have fixed functionality (energy meters, standalone thermostats, etc) there should be a way for these devices to publish tags for their standard points, in other words for a thermostat, it should be able to publish its room temperature with all the appropriate Haystack tags for that info.
In my opinion, whatever mechanism is put in place should support arbitrary metadata publishing, but we should determine a standard for enabling Haystack tagging information to pass cleanly through the platform.
Possible solutions to discuss include allowing arbitrary metadata to be published with each scrape, and/or to enable the master driver to only publish the extended metadata once upon startup.
Look forward to discussing this and finding a solution that supports a variety of use cases.