The WUnderground stuff was purely via weewx, and I have never bothered with the rapidfire side. My console is a WMR300, which has no direct WUnderground access, and in fact no network at all (USB only). This also is the reason why initially the mysql and weewx hosts were separate. The mysql server that was already doing other things did not have usb access.
I have never bothered to implement anything fancier, because it seems that, being retired, I have no spare time. (perhaps it is really that, being old, everything takes so much longer). The kiss principle says that by the trivial process of increasing the number of rows by a factor of 5, while reducing number of columns by a factor of 3 and halving the number of bytes per column means that I have achieved a "good enough" situation without any significant effort. Allowing for a larger index means my system is probably close to the default size anyway. I did try Belchertown, perhaps 8 years ago, without much success, so perhaps the short interval was what upset it. On Wednesday, 19 November 2025 at 7:41:55 pm UTC+10 John Smith wrote: > On Wed, 19 Nov 2025 at 19:48, '[email protected]' via weewx-user < > [email protected]> wrote: > >> Depending on the hardware used, there might be some limitations that >> apply. With my setup, I query multiple >> > > I'm pretty sure I read an email on this list the other week that they were > having problems with weeWX attempting to access a console while the console > itself was trying to also do uploads to WUnderground at the same time, I > guess it will depend if Cameron has a similar console to what you're > using... > > I've had a little more time to think about Cameron's needs and wants and > I'd be more inclined to just use a single weeWX instance and log all loop > packets to a database and then scan past records afterwards that have > little or no changes between them and delete them. > > That way when something actually happens you have, depending on console > and sensors and all that, 10s of data readings per minute, rather than 1... > Just delete the uninteresting stuff... > > >> For each instance I could choose whatever interval I'd be happy with. >> Having Terabytes of storage on this devices, >> > > I'm using a 1TB USB SSD with my SBC running weeWX, but it only has 4GB of > RAM and it's a slow-ish arm CPU, so storage isn't the limiting factor, the > CPU would be the bigger issue out of the 3, so getting as many as possible > columns to have smaller number types (ie less bytes per value) should make > an improvement, not just on day to day use by weeWX, but on other important > things like daily backups of data... > > >> that would be running 24/7 anyway, I'd definitely go for this most >> straight forward approach, if I had the desire to persist my observations >> in an 1-minute-interval. I wouldn't use an 1-minute-interval with a >> skin(because the chart >> > > People using the Belchertown skin, maybe others too but I'm not aware of > them, use MQTT for sub-minute updates of their websites from loop packets, > but they don't try and store all that data for future use... > -- 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/9aa40e73-f636-4660-954e-bcf25ceb65cdn%40googlegroups.com.
