John Smith <[email protected]> writes: >> What if you had temperature measurements every second? > > I solved that problem already for the soil moisture sensors + > temperature/humidity sensors on my ZigBee network as the sensors send > bursts of readings but there can be 30+ minutes between bursts as well. > > Since the timestamps are unique, my script that copies the readings to the > DB filters the readings so that there is at least 15s between readings, > then later on I also prune the database so there is at least 5 minutes > between readings, although the script doing the insertion could track/check > when the last insertion was.
That seems like an approach that works for you. There are various transmission mechanisms, and various code running at receivers, and I believe that a significant number of people would benefit from reduction of communications, and ingest/db resources, especially in systems where it's less easy to inject code (because of the person, or the system). You seem to be suggesting that rate limits are not reasonable, because you have a personal scheme, in one system instantiation, where you don't need them. That's that I'm reacting to. I'm not claiming that what you're doing is wrong, just that it's not valid to extrapolate from that to a conclusion that all rate limits are unnecessary. -- 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/rmicxwwxcbz.fsf%40s1.lexort.com.
