I have now. I needed to install sqlite3. All is right with the world!
A huge thank you to everyone who helped me! On Tuesday, September 5, 2017 at 5:31:11 PM UTC-7, gjr80 wrote: > > Where was the SQL issue? Did you get into SQLite by running > > $ sqlite3 /home/weewx/archive/weewx.sdb > > Did you substitute the relevant timestamps for xxxxxxxxxxx and > yyyyyyyyyyyy? The latter can be the trick/catch, you need to find the > timestamp for the start and end date-time you are interested in. Using an > epoch calculator such as https://www.epochconverter.com/ can be helpful. > > Gary > > On Wednesday, 6 September 2017 10:26:08 UTC+10, TheChoctlab wrote: >> >> Hi Gary, >> >> Thank you. I have done as you suggested and now have the, "curiosity >> factor" data that I was looking for. >> >> Now, I am eagerly awaiting Andrew's response as to how to query the >> database directly. >> >> >> >> >> On Tuesday, September 5, 2017 at 5:09:09 PM UTC-7, gjr80 wrote: >>> >>> Hi, >>> >>> That will certainly take care of WU from the date you implement these >>> cron entries onwards but by itself it won't fix anything historical. You >>> will need to do historical updates manually from the command line using the >>> --date option. Something like: >>> >>> $ /home/weewx/bin/wunderfixer --date=2017-08-21 >>> >>> should do the trick. Of course you can add the --test command line >>> option to make sure you have it right before you actually send data to WU. >>> Remember with WU once you upload data you cannot change it other than a one >>> time 'delete'. Wunderfixer details are in the Utilities Guide >>> <http://weewx.com/docs/utilities.htm#wunderfixer_utility>, but if you >>> have the cron entries set as you do I expect you have already found that. >>> >>> Gary >>> >>> On Wednesday, 6 September 2017 09:39:11 UTC+10, TheChoctlab wrote: >>>> >>>> As for a cron job, I think I have that figured out. >>>> >>>> I am doing it like this: >>>> >>>> # Run wunderfixer at 1258pm daily >>>> 58 12 * * * /home/weewx/bin/wunderfixer --log weewx > /dev/null 2>&1 >>>> # Run wunderfixer at 1158pm daily >>>> 58 23 * * * /home/weewx/bin/wunderfixer --log weewx > /dev/null 2>&1 >>>> >>>> >>>> >>>> On Monday, September 4, 2017 at 7:52:44 PM UTC-7, Andrew Milner wrote: >>>>> >>>>> alternatively have you tried running wunderfixer to add in the missing >>>>> values to WU?? I run wunderfixer twice a day using a cron task and now >>>>> it >>>>> never misses any data!! >>>>> >>>>> >>>>> >>>>> On Tuesday, 5 September 2017 05:48:07 UTC+3, Andrew Milner wrote: >>>>> >>>>>> If you are just wanting to see the drop out of curiosity then why not >>>>>> just directly access the database using sqlite3 eg >>>>>> SELECT datetime, outTemp FROM archive WHERE datetime > xxxxxxxxxxxxx >>>>>> and datetime < yyyyyyyyyyyyyy; >>>>>> >>>>>> >>>>>> >>>>>> On 5 September 2017 at 05:41, TheChoctlab <[email protected]> wrote: >>>>>> >>>>>>> Nuts. >>>>>>> >>>>>>> What I was after was to see the temperature drop as the solar >>>>>>> eclipse took place. >>>>>>> >>>>>>> Looking at my WU data I know that it dropped at least six (6) >>>>>>> degrees Fahrenheit. However, WU is missing data for three ten minute >>>>>>> records right at the maximum period of occlusion. >>>>>>> >>>>>>> I guess I should have thought about this prior t the eclipse. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Monday, September 4, 2017 at 7:31:27 PM UTC-7, Tom Keffer wrote: >>>>>>>> >>>>>>>> Querying for specific times is not available. Perhaps it should be. >>>>>>>> What is your application that you need to do this? >>>>>>>> >>>>>>>> -tk >>>>>>>> >>>>>>>> On Mon, Sep 4, 2017 at 6:53 PM, TheChoctlab <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Eureka! Thank you Tom. >>>>>>>>> >>>>>>>>> Now then, how would I query for a specific date? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Monday, September 4, 2017 at 6:00:17 AM UTC-7, Tom Keffer wrote: >>>>>>>>>> >>>>>>>>>> Almost. You need to iterate over a time period. Also, because the >>>>>>>>>> results of the iteration will be individual records, there will not >>>>>>>>>> be a >>>>>>>>>> minimum and maximum temperature. Just temperature. Something like >>>>>>>>>> (NOT >>>>>>>>>> TESTED): >>>>>>>>>> >>>>>>>>>> #for $record in $day.records >>>>>>>>>> $record.dateTime.format("%B"): $record.outTemp >>>>>>>>>> #end for >>>>>>>>>> >>>>>>>>>> -tk >>>>>>>>>> >>>>>>>>>> On Sun, Sep 3, 2017 at 9:36 PM, TheChoctlab <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> On your suggestion, I reviewed the information regarding >>>>>>>>>>> Iteration. I think that will get me where I want to go. >>>>>>>>>>> >>>>>>>>>>> I am more of a hardware guy rather than a software guy. So, >>>>>>>>>>> please forgive my feeble attempt at the following: >>>>>>>>>>> >>>>>>>>>>> Min, max temperatures by record#for $record in $record.days >>>>>>>>>>> $record.dateTime.format("%B"): Min, max temperatures: >>>>>>>>>>> $record.outTemp.min $record.outTemp.max#end for >>>>>>>>>>> >>>>>>>>>>> Am I, sort of, on the right track? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sunday, September 3, 2017 at 8:44:30 PM UTC-7, Tom Keffer >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> See the Customizing Guide, section Iteration >>>>>>>>>>>> <http://weewx.com/docs/customizing.htm#Iteration>. >>>>>>>>>>>> Specifically, you want suffix .records. >>>>>>>>>>>> >>>>>>>>>>>> -tk >>>>>>>>>>>> >>>>>>>>>>>> On Sun, Sep 3, 2017 at 4:53 PM, TheChoctlab <[email protected]> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I have searched the Group but, must not have used the correct >>>>>>>>>>>>> search terms as I could not find what I am after. >>>>>>>>>>>>> >>>>>>>>>>>>> My interest is producing a report similar to the "Monthly >>>>>>>>>>>>> Summary" but, that displays daily data from each archive record >>>>>>>>>>>>> (every ten >>>>>>>>>>>>> minutes). Wview does this but, I much prefer weewx. >>>>>>>>>>>>> >>>>>>>>>>>>> Any guidance will be greatly appreciated. >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> 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]. >>>>>>>>>>> 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. >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> You received this message because you are subscribed to a topic in >>>>>>> the Google Groups "weewx-user" group. >>>>>>> To unsubscribe from this topic, visit >>>>>>> https://groups.google.com/d/topic/weewx-user/NcjHMUgGsYs/unsubscribe >>>>>>> . >>>>>>> To unsubscribe from this group and all its topics, 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]. For more options, visit https://groups.google.com/d/optout.
