There are a couple of skins with live weather feed, see https://github.com/weewx/weewx/wiki#skins for a (probably incomplete) list. Anyway, I'm not committed in persisting anything in another interval than the default. What I do emphasize is min/max values and their closest-to-exact time of occurrence to be recorded correctly. But that available out-of-the-box, on database level (to get at least a little bit back to topic)
John Smith schrieb am Mittwoch, 19. November 2025 um 10:41:55 UTC+1: > 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/ac9169e3-b10c-4444-8237-936c5e29e749n%40googlegroups.com.
