[weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

Here the errors when debug=1 Jan 8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Finished loading service weewx.engine.StdConvert Jan 8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Loading service weewx.engine.StdCalibrate Jan 8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Finished loadi

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

Most likely, the patch is not running to completion. It will let you know when it is done. Don't be deceived by the message from the interceptor driver: it is running in another thread. I don't know what type of RPi you have, but the patch typically takes a couple minutes. Slowest we have seen is

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

Hi Tom, thanks for the answer. This is probably not my case, as I have a dedicated RPi 3B+ and it was running more than 30 minutes. Can we check somehow how the Daily summaries v2 -> v3 process is running? Thanks, Michal. miso pi 8. 1. 2021 o 14:54 Tom Keffer napísal(a): > Most likely, the p

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

We can look in the database. I don't know what install method you used, but assuming it was a package install (using apt-get): *sqlite3 /var/lib/weewx/weewx.sdb* sqlite> *select * from archive_day__metadata;* sqlite> *select * from archive_day_outTemp order by dateTime desc limit 10;* sqlite> *.qu

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

thanks, this is the result: 1610060400|30.7|1610090851|32.4|1610111352|3065.1|99|183906.0|5940 1609974000|32.7|1609981063|34.7|1610016711|21169.49|631|1270170.0|37860 1609887600|32.9|1609930871|36.3|1609940679|43137.68|1235|2588262.0|74100 1609801200|33.3|1609880806|39.6|1609803685

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

Btw, I have installed weewx through DEB package, I updated it through DEB package too. M Dátum: piatok 8. januára 2021, čas: 15:36:09 UTC+1, odosielateľ: miso k > thanks, > this is the result: > > 1610060400|30.7|1610090851|32.4|1610111352|3065.1|99|183906.0|5940 > > 1609974000|32.7|1609981063|3

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

You didn't show the results of the first sqlite command sqlite> *select * from archive_day__metadata;* On Fri, Jan 8, 2021 at 6:37 AM miso k wrote: > Btw, I have installed weewx through DEB package, I updated it through DEB > package too. > M > > Dátum: piatok 8. januára 2021, čas: 15:36:09 UTC

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

So what? after sudo apt-get upgrade I restarted RPi gain and! Its running :) You have golden hands, Tom! sqlite> select * from archive_day__metadata; Version|3.0 lastUpdate|1610117160 the only thing what is not running now is AQI index. https://jastrabie.online/weewx/ $aqi($current($data_bindin

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

Solved this issue too: in skin.conf for Seasons was missing in stanza: [CheetahGenerator] search_list_extensions = user.aqi.service.AqiSearchList Tom, many thanks for quick support from Slovakia! Michal Dátum: piatok 8. januára 2021, čas: 15:50:03 UTC+1, odosielateľ: miso k > So what? after s

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

Tom - for dpkg installations there might be some confusion regarding how to answer the question regarding keeping/not-keeping weewx.conf that was previously in place especially if you've added extensions, and what the user might need to do manually to upgrade a customized system. I've been runn

[weewx-user] Debug=1 not outputting debug info

This is a spin off of another thread I had with a Seasons skin issue. In working through that issue with Gary, we discovered that when debug=1, no debug output is appearing in /var/log/messages. -- You received this message because you are subscribed to the Google Groups "weewx-user" group

[weewx-user] Re: Debug=1 not outputting debug info

You're going to have to help us with 'which os' and 'configured how' to be able to debug at all. Are you on a physical system ? In a VM ? In Docker ? On Friday, January 8, 2021 at 9:59:07 AM UTC-8 blu...@gmail.com wrote: > This is a spin off of another thread I had with a Seasons skin issu

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

I've had the same experience. But, as I understand it, the script that runs the "keep your weewx.conf" file is supplied by Debian. It's not something that we can control. Matthew is the expert on this. On Fri, Jan 8, 2021 at 9:54 AM vince wrote: > Tom - for dpkg installations there might be some

[weewx-user] Update graphs

Hi all, This week I had a low-battery issue with my Davis station #1 (rain, pressure, temp, etc), which caused a N/A temp and a rainRate of 13.107mm(!), while it was a dry day with 0,0mm rain. I used an SQL-editor to change wrong values, generated new reports and executed a 'wee_database weewx.

Re: [weewx-user] Re: Debug=1 not outputting debug info

wee_debug --info produces: Using verbosity=1, displaying most info wee_debug output will be sent to stdout(console) Using configuration file /etc/weewx/weewx.conf Using database binding 'wx_binding', which is bound to database 'archive_sqlite' System info Platform: Linux-4.19.66-v7+-armv

Re: [weewx-user] Re: Debug=1 not outputting debug info

>From your /var/log/messages snippet it looks like it's logging to me. Jan 8 10:50:21 corbett weewx[1497] INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 5.42 seconds Jan 8 10:50:22 corbett weewx[1497] INFO weewx.imagegenerator: Generated 14 images for report Seasons

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

On Friday, January 8, 2021 at 10:48:50 AM UTC-8 Tom Keffer wrote: > I've had the same experience. But, as I understand it, the script that > runs the "keep your weewx.conf" file is supplied by Debian. It's not > something that we can control. Matthew is the expert on this. > Thanks. Just to cl

Re: [weewx-user] Latest WeeWX 4.3.0 SQL optimizations may return invalid results

Hello Tom, I am using MySQL database. Arend Op vrijdag 8 januari 2021 om 20:18:20 UTC+1 schreef tke...@gmail.com: > Thanks. Not sure what is happening, but let's take a look at your > database. I'm assuming you are using SQLite, and that you used a package > installer. You may have to install

[weewx-user] Re: Version 4.3.0 released

Ok, so what is the difference between the unsupported WMR200-version and the last supported driver? As I have three WMR200 I'm quite interested in keeping it running and they are now at 4.2.0 I guess I need to remove Weewx from the source.list so that the newest version don't get installed duri

Re: [weewx-user] Re: Debug=1 not outputting debug info

Gary was under the impression I should be seeing [DEBUG] information related to the report generator process. > On Jan 8, 2021, at 11:29 AM, vince wrote: > > From your /var/log/messages snippet it looks like it's logging to me. > > Jan 8 10:50:21 corbett weewx[1497] INFO weewx.cheetahgener

Re: [weewx-user] Re: Debug=1 not outputting debug info

It would be worth checking whether the configuration of your logger allows DEBUG messages. Try entering this from a command line *logger -p user.debug "This is a debug message"* and see if that shows up in /var/log/syslog -tk On Fri, Jan 8, 2021 at 11:54 AM Kevin Davis wrote: > Gary was under

Re: [weewx-user] Latest WeeWX 4.3.0 SQL optimizations may return invalid results

Then adapt as necessary. Use from_unixtime() instead of datetime() in the select statement. On Fri, Jan 8, 2021 at 11:49 AM Arend wrote: > Hello Tom, > > I am using MySQL database. > > Arend > > Op vrijdag 8 januari 2021 om 20:18:20 UTC+1 schreef tke...@gmail.com: > >> Thanks. Not sure what is h

Re: [weewx-user] Re: Version 4.3.0 released

The wmr200 driver is no longer included in the regular distribution. It's now a separate extension . If you upgrade, there will be no wmr200 driver, so you would have to install the extension. Older versions have to be installed manually. -tk On Fri, Jan 8

Re: [weewx-user] Update graphs

The graphs are regenerated only as often as whatever aggregation interval you are using. So, if you use an aggregation interval of 1 hour for your week plots, it will take an hour before they are refreshed. Or, just delete the plots. They will be automatically regenerated during the next reporting

Re: [weewx-user] Re: Debug=1 not outputting debug info

Ahhh - that's itwhat's happening is that on a pi, user.debug messages go to /var/log/syslog but 'not' to /var/log/messages. I verified the behavior above on pi versions dating back 5 years (really). One model-B pi here has a os date of 2016-02-26 according to /boot/issue.txt which shows the

Re: [weewx-user] Latest WeeWX 4.3.0 SQL optimizations may return invalid results

SELECT mintime, from_unixtime(dateTime), min from archive_day_outTemp order by min asc, mintime asc limit 20; Database weewx mintime from_unixtime(dateTime) min NULL 2019-12-15 00:00:00 NULL NULL 2019-12-17 00:00:00 NULL 16067062352020-11-30

Re: [weewx-user] Re: Debug=1 not outputting debug info

DUH! Ok; yep. They are going to syslog. Mystery solved. Thanks gents. On Fri, Jan 8, 2021 at 12:48 PM vince wrote: > Ahhh - that's itwhat's happening is that on a pi, user.debug messages > go to /var/log/syslog but 'not' to /var/log/messages. > > I verified the behavior above on pi vers

Re: [weewx-user] Latest WeeWX 4.3.0 SQL optimizations may return invalid results

It appears that you have a null value for mintime in your database. Most likely the problem is that you have no data for 2019-12-15 and 2019-12-17. I suspect the older query worked because MIN(value) ignores values, while ordering by value does not. This is a bug: the query should check for non n

Re: [weewx-user] Latest WeeWX 4.3.0 SQL optimizations may return invalid results

Adding that extra testing for NOT NULL did the trick. All dates (as far as I can tell) are now correctly retreived. Op vrijdag 8 januari 2021 om 22:33:50 UTC+1 schreef tke...@gmail.com: > It appears that you have a null value for mintime in your database. Most > likely the problem is that you h

Re: [weewx-user] Re: Version 4.3.0 released

How do I install the extension? What is the difference between Python2 and Python3? Does it matter on Raspbian 10/Buster? Virus-free. www.avg.com

Re: [weewx-user] Re: Version 4.3.0 released

You should use python 3. It's the future. To install: 1. Download the tar file for the current release: https://github.com/weewx/weewx-wmr200/archive/v3.5.1.tar.gz 2. Then, install like any other extension using wee_extension with the --install option

Re: [weewx-user] Re: Version 4.3.0 released

Per: I just added some installation instructions to the weewx-wmr200 README . On Fri, Jan 8, 2021 at 4:30 PM Tom Keffer wrote: > You should use python 3. It's the future. > > To install: > > 1. Download the tar file for the current relea

Re: [weewx-user] 4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

I had this issue already before. As inexperienced user, I reinstalled the whole Raspberry again. What about making a python script to make the dpkg update work? miso pi 8. 1. 2021 o 20:41 vince napísal(a): > On Friday, January 8, 2021 at 10:48:50 AM UTC-8 Tom Keffer wrote: > >> I've had the sa

Re: [weewx-user] Re: Version 4.3.0 released

I'm one of the few that used ignore_zero_wind. The new update works great. On Friday, January 8, 2021 at 6:43:36 PM UTC-6 tke...@gmail.com wrote: > Per: I just added some installation instructions to the weewx-wmr200 > README . > > On Fr