John Smith <[email protected]> writes: >> In essence MQTTPublish would be creating its own ‘archive record’. > > I'm struggling to figure out the benefit of this, would this be to reduce > the publishing rate? or?
Yes, because depending on your system, that might matter. A system with limited network capacity, or battery power to send transmissions, or whatever, might be better sending less data, if that less data is not meaningfully less useful. The receiving system also requires resources. In the case of Home Assistant, the normal practice is that each incoming update results in a state database entry. While you can configure the MQTT receiver not to cause that, the idea that you know the value of the observable during a period with no data points is iffy. Using a reasonable interval helps lot, where reasonable is a blend of short enough to capture the signal of the underlying feature, short enough for automations to run based on real changes, and long enough that unnecesary and unhelpful procesing and database usage is avoided. What if you had temperature measurements every second? Every 10 ms? Certainly there are both people whose concerns don't lead to wanting to avoid high-rate transmissions and people whose concerns do lead to wanting limits. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/rmiqzlcxghc.fsf%40s1.lexort.com.
