I use the raw part of mesowx just to create such a table of LOOP data which maintains a 7 day (for me) record of all LOOP data - should I ever have reason to look back over what happened. I modified the graphing part of mesowx to not provide the real time display, but to give me the graphing functionality still - switching between the loop data and the archive data depending on period graphed < 7 days or > 7 days.
gary had updated mesowx raw and sync services to work with latest weewx versions even if the original depository had not been updated. weewx wiki was however updated with the new locations for downloads - but I have just seen that the links to mesowx in the wiki appear to have been removed since I updated the wiki page, and only the original links retained under skins. On Sunday, 27 November 2016 03:26:51 UTC+2, vince wrote: > On Saturday, November 26, 2016 at 11:57:42 AM UTC-8, Tom Keffer wrote: >> >> Unfortunately, there is not. >> >> Your choices are to either use the Weather Underground's "Rapidfire" >> protocol, or to try the weewx extension, mesowx >> <https://bitbucket.org/lirpa/mesowx>. If you go with mesowx, you should >> be prepared for some technical challenges. >> >> >> > And a project with zero commits in 30 months might be something to > consider avoiding... > > Just for the purpose of discussion, wouldn't it be possible to write each > LOOP data point out to a custom-formatted file in tmpfs or the like, then > have a webpage that reads that data, as one way of doing what he's asking ? > When we run weewx in the foreground, we see that data, couldn't a custom > SLE or the like do something similar and format it differently for some web > page to consume ? > -- 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]. For more options, visit https://groups.google.com/d/optout.
