Well… It’s ALWAYS changing, the question is whether the change is significant. That would need to be defined. At some point it then becomes an issue of whether there is less resource use and complexity to discriminate change than to just send it out and let the recipient decide. Sending out an asynchronous packet every 15 or thirty seconds is pretty low overhead.
I’d like to explore this more and get more feedback. Just thinking on my feet, I could see some form of generic Json (or other) output service. Possibly using something like printf formatting to generate a payload, or maybe there’s some generic Json generation syntax that you could point me at.
A service like that could deliver the payload using HTTP or MQTT, so it’s not either/or.