Hi Thomas, I use it mainly for the NOAA Climatological monthly and yearly summaries, and also compile yearly and all time highs and lows from the database, and appreciate having the database available for any other kind of record manipulation or graphing. As i mentioned, I don't keep a full time connection to a computer, as I have never had a computer I had on for 24/7, or necessarily kept my console near the computer, and I still use an original VP (not VP2) which seems to sometimes cause interference problems if I do keep it near and attached to the computer, have never experimented with a website or a Raspberry Pi.
Anyway, weeWX has works great downloading my archive data from the logger to the weeWX database, other than the loss of granularity by not reading the available hi/lo data for the archive interval. If that extra bit of data could also be taken from the logged archive data, I would see no reason I would need to accumulate LOOP packet data as I'm not publishing in real time, just keeping old-fashioned (more or less) local data records. (Each month I also check the highs and lows as recorded on the console to adjust the weeWX reports if needed, and save them elsewhere.) It also seems to me that the ability to record the archive hi/lo s to the db would also be a plus for those who do rely on the LOOP data, but have unexpected computer downtime or dropped connections, and need to download the archived data from the logger to fill in the gaps. I used WeatherLink exactly the same way before I dumped Windows all together; for periodic downloads, reports, and graphing; except it would record the archive interval hi/lo s. I hope that makes sense, please let me know if I can clarify something, or if I'm just using weeWX wrong, or misunderstanding something, or if maybe there's something else I could be doing (I'm not going to pretend I'm an expert on weeWX or computers). Thanks for your work! WeeWX does most everything I want (and more), except just that one little thing. I also hope I didn't hijack the other Thomas' thread, but if I understand it it sounds similar to what I wanted. On Wednesday, September 5, 2018 at 7:02:23 PM UTC-6, Thomas Keffer wrote: > > Thanks for your comments, Jeff, but you've got me curious. If you don't > use WeeWX for its ability to accumulate LOOP packets and make records out > of them, and you don't publish to the web, what do you use it for? Internal > LAN publishing? Something else? > > -tk > > On Wed, Sep 5, 2018 at 9:08 AM Jeff A. D. <[email protected] > <javascript:>> wrote: > >> If I may chime in on the subject, but there are various reasons I don't >> have a full time connection to my wx station (Davis VP), and therefore rely >> on the archive records to download from the data logger periodically. Even >> using a fairly long archive interval of 30 minutes, the archive records are >> (would be) more than adequate for me as they do contain the highs and lows >> for that interval. However, for whatever reason, even though as I >> understand it, weewx, and I think wview, where originally started for the >> Davis stations, they neglected to record these values in the data base. >> >> So maybe in the view of some, I'm missing out on half the reason to use >> the program, as I use it *only* for archive purposes and not to publish >> to the web in real time; but in my view the program is lacking in an area >> where it could otherwise be complete. >> >> Please don't misunderstand, I do love weewx and am thankful for it, as it >> seems to be the best alternative for Linux. I just wish it didn't have >> this one shortcoming. >> >> On Wednesday, September 5, 2018 at 5:51:37 AM UTC-6, Thomas Keffer wrote: >>> >>> Andrew pretty much has the right idea. >>> >>> The whole value of weewx is in its archiving abilities. If your >>> driver(s) don't emit LOOP packets, then your missing out on half the reason >>> to use the program! >>> >>> -tk >>> >>> On Tue, Sep 4, 2018 at 9:46 PM Andrew Milner <[email protected]> >>> wrote: >>> >>>> If you bind your service to loop rather than record then >>>> weewx will build an archive record at the archive interval, with the >>>> value being the average value for the period >>>> >>>> if you specify use loop for hilo in weewx.conf then weewx will populate >>>> the max and min from the loop data and the archive record will contain the >>>> average value for the archive period >>>> >>>> if you do not specify to use loop hilo then min and max will be the >>>> highest archived value for the day or the lowest archived value for the day >>>> >>>> does this answer your question though?? >>>> >>>> oh yes, the min and max times will always be on archive boundaries >>>> unless use loop for hilow is specified since the source of the data is of >>>> course the archive record. >>>> >>>> so the way to specify the times of the max and min is for the data to >>>> be in loop packets rather than rec packets >>>> >>>> >>>> >>>> On Wednesday, 5 September 2018 07:30:35 UTC+3, Thomas Carlin wrote: >>>>> >>>>> Good evening! >>>>> >>>>> I have extended my weewx instance with several sensors build on the >>>>> ESP8266 platform with help from many in this community. I have built a >>>>> driver based on the custom service documentation provided by TK and crew. >>>>> >>>>> This has been working wonderfully, and I am really enjoying the extra >>>>> temperature sensors, as well as things like electricity monitors, >>>>> irrigation system monitors etc. The only issue that I have with this >>>>> system is that I am only adding a single piece of data into the archive >>>>> each time the archive interval is reached. I would like to know if there >>>>> is a way to as part of the additional service, add into the records the >>>>> minimum and maximum values recorded by the sensors, and the dates and >>>>> times. Obviously, the sensors will have to record and transmit this data >>>>> on the archive interval, and the driver will need to interpret this data. >>>>> >>>>> I just need to know how to insert the min and max data into the database. >>>>> >>>>> Is this possible with the current architecture? >>>>> >>>>> For Example, the contents of the an archive for outTemp and one of my >>>>> custom sensors. Notice the precision of the time of the outTemp, and the >>>>> general time of the l2_volt, all on the 5 minute archive interval of my >>>>> system. >>>>> >>>>> sqlite> select * from archive_day_outTemp order by dateTime desc limit 1; >>>>> dateTime |min |mintime |max |maxtime |sum >>>>> |count|wsum |sumtime >>>>> 1536040800|55.1999999999999|1536065400|87.5|1536097806|18741.1237726958|263 >>>>> |5622337.13180874|78900 >>>>> >>>>> >>>>> sqlite> select * from archive_day_l2_volt order by dateTime desc limit 10; >>>>> dateTime |min |mintime |max |maxtime |sum |count|wsum >>>>> |sumtime >>>>> 1536040800|115.15|1536117900|125.74|1536079200|32513.28|263 >>>>> |9753984.0|78900 >>>>> >>>>> >>>>> Hopefully this request makes sense, and thank you for your help! >>>>> >>>>> >>>>> http://carlincomputing.duckdns.org/weewx/index.html >>>>> >>>>> -- >>>> 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. >>>> >>> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
