Thank you for the clarification tom. So I assume there are not going to be more tables added (e.g. for week, month etc) but only the daily hi/lows, right?
Regards, henry. On Friday, March 22, 2019 at 12:45:41 AM UTC+1, Tom Keffer wrote: > > The daily summaries hold one row per day. > > Each row is timestamped with the start of the day, *local time*. In your > time zone (CET +1, I presume), they are all in the same day, 3-March-2019. > > If you have only one row in your daily summaries and WeeWX has been > running for more than one day, then there is something wrong and we will > need to see the logs. > > -tk > > On Thu, Mar 21, 2019 at 4:06 PM Henry Denston <[email protected] > <javascript:>> wrote: > >> Sorry, in case I create too much spam, but I'm trying to dig deeper into >> WeeWx and while I was checking out the database structure I can not fully >> understand how the day tables are managed. >> I'm using mysql so I checked the weewx/manager.py (the DaySummaryManager >> classs) and all mysql.py files. >> >> The daily tables look like this (e.g for my temperature): >> >> [image: pic.png] >> >> >> >> >> >> >> I first assumed that every observation type (like radiation, temperature, >> rain etc.) gets it's own daily table (and that is right). >> Then every daily table contained one row for every day the station was up >> and running and every row will have a min and max value of that day (for >> the specific observation type). >> I could not test the station over a longer period of time so far but to >> me it seems that a daily table will always only hold one single row? >> I'm confused as as you can see in my picture posted above, the dateTime >> is from the day before (02.03.2019) and the min/max timestamps are from >> another day, the day after (03.03.2019). >> How will weewx get the hi/lo values for every single day in a month for >> example if the daily tables only hold one single row? >> >> It's been a long day so maybe I'm just being dumb right now but I'm >> confused and I don't like being confused ;). >> I hope someone will be so kind to clear this up for me. >> Thank you very much, henry. >> >> On Sunday, March 3, 2019 at 3:27:31 AM UTC+1, Henry Denston wrote: >>> >>> I'm using WeeWX on a RPi but there are also many other systems >>> running simultaneously. I'm using a single bash script used by rc.local >>> file and crontab that checks and manages all systems. Implementing WeeWx >>> into my system like that just is a convenient way for me to not 'break' my >>> system architecture and keeping things simple. >>> >>> So far I did not encounter issues, so I'm happy :) >>> >>> Again Tom, thank you very much for this great project and your efforts! >>> >>> On Saturday, March 2, 2019 at 10:01:45 PM UTC+1, Tom Keffer wrote: >>>> >>>> The init.d scripts files do more than just start weewx. They also make >>>> sure essential services are up and running before attempting the startup. >>>> >>>> So, let me flip the question around: is there any reason *not* to use >>>> the init.d script? Is there something you need to work around that >>>> attracts >>>> you to putting the start up in the rc.local file? >>>> >>>> -tk >>>> >>>> >>>> >>>> On Sat, Mar 2, 2019 at 11:40 AM <[email protected]> wrote: >>>> >>>>> On Sunday, February 24, 2019 at 11:42:22 AM UTC-8, Henry Denston wrote: >>>>>> >>>>>> Ok, thanks Tim, good advice! :) >>>>>> >>>>>> So basically there is no need to use the file from >>>>>> util/init.d/weewx.debian like the DOCs advice. >>>>>> So there is no downside by not using the instruction from the >>>>>> documentary and just execute the ./bin/weewxd weewx.conf file with >>>>>> the weewx.conf as first parameter from the /etc/rc.local file? >>>>>> >>>>> >>>>> >>>>> The downside is that if you start/stop weewx via some custom >>>>> mechanism, we will have a difficult time helping you for future >>>>> questions....and you will have a difficult time updating weewx to future >>>>> versions (maybe). >>>>> >>>>> >>>>> - If you are running a systemd-based operating system, start weewx >>>>> with a systemd-based startup file >>>>> - If you are running an init.d-based operating system, start weewx >>>>> with an init.d-based startup file >>>>> >>>>> >>>>> But 'technically' weewx does not care how you start it up. You can >>>>> do it any way you want. >>>>> >>>>> >>>>> >>>>
