[weewx-user] Re: Belchertown AerisWeather link to PWS weather problem

[Neville Davis]

Fixed the second part of my issue by the following edit to weewx.conf

forecast_enabled = 1

forecast_provider = "darksky"

forecast_api_id = ""

forecast_api_secret = "##"
I still cannot link PWS and aerisweasther

Neville
On Thursday, January 7, 2021 at 11:41:04 AM UTC+10 Neville Davis wrote:

> I have data going to PWS weather from weewx and my station is recorded as 
> active on their website.
> For about a month I have been trying to link my PWS data to AerisWeather 
> to get forecast data but it keeps reporting "something is going wrong try 
> again".
> I am now on weewx 4.3 and Belchertown 1.2... 
> Has anybody else had this problem...I know at least one person had to wait 
> about a week of stable data..before the process would complete.
> Pat if you see this I have tried to get my darksky (valid API or was 
> earlier this morning) to work but its failing. 
> Configured in weewx.conf
> forecast_enabled = 1
> forecast_provider = "darksky"
> darksky_secret_key = 
>
>
> Neville
>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0c48b1d1-8307-4eff-b5a5-0036e44db0e2n%40googlegroups.com.

[weewx-user] Belchertown AerisWeather link to PWS weather problem

[Neville Davis]

I have data going to PWS weather from weewx and my station is recorded as 
active on their website.
For about a month I have been trying to link my PWS data to AerisWeather to 
get forecast data but it keeps reporting "something is going wrong try 
again".
I am now on weewx 4.3 and Belchertown 1.2... 
Has anybody else had this problem...I know at least one person had to wait 
about a week of stable data..before the process would complete.
Pat if you see this I have tried to get my darksky (valid API or was 
earlier this morning) to work but its failing. 
Configured in weewx.conf
forecast_enabled = 1
forecast_provider = "darksky"
darksky_secret_key = 


Neville


-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7bdb074a-534b-42b9-9b53-79d8a04f028bn%40googlegroups.com.

RE: [weewx-user] cant find start time

[orders]

I have 2 Vantage pro consoles 1 feeding a computer with VWS, Cumulus and 
Weather Display I upload to CWOP, WUNDERGROUND, PWS, PLAINS WEATHER NET and the 
other feeding meteobridge to get to AMBIENT WEATHER site for the last 15 years. 
Now I have a rasberyPi  that is new to me as all the others are windows that is 
going to just be there I guess till I figure more about it. It is making a web 
page for now on the Pi only but soon hope to have it on my website weather page 
with the rest of them

Bill. 

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Wednesday, January 6, 2021 3:11 PM
To: weewx-user 
Subject: Re: [weewx-user] cant find start time

 

Oh. You're going through Meteobridge? That's an important detail. 

 

WeeWX expects to be able to control the state of the Vantage station. I don't 
know if it can do that going through a Meteobridge. I'm not even sure what that 
means.

 

-tk

 

On Wed, Jan 6, 2021 at 1:15 PM mailto:ord...@billandcorena.com> > wrote:

I tried to go back to hardware, after using wee-device commands but it stopped 
again.  I am connecting to the Vantage Pro2 thru a meteobridge and have other 
software running on windows, was just trying to learn something new but I am 
not sure that rasberryPi  is not above my head so as long as it works with 
software generation will leave it that way. I have learned some form this I 
guess.

Bill

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of gjr80
Sent: Wednesday, January 6, 2021 12:50 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] cant find start time

 

...and then change back to hardware record generation.

 

Gary

On Thursday, 7 January 2021 at 05:45:59 UTC+10 tke...@gmail.com 
  wrote:

That's good, but you really should clear the logger memory. Otherwise, you 
won't be able to enjoy a key feature of weewx + Vantage: the ability to 
continue to log data, even if your computer crashes, your network goes down, or 
you experience a power outage.

 

 

On Wed, Jan 6, 2021 at 10:59 AM mailto:ord...@billandcorena.com> > wrote:

Seems to be working after I used the software records.

Bill

 

From: weewx...@googlegroups.com   
mailto:weewx...@googlegroups.com> > On Behalf Of 
Tom Keffer
Sent: Wednesday, January 6, 2021 11:36 AM
To: weewx-user mailto:weewx...@googlegroups.com> >
Subject: Re: [weewx-user] cant find start time

 

The error "cannot find start time" happens when there is nothing in the 
database. Is this the first time you've used the database?

 

Normally, there is something in the database before a report is generated, but, 
I suspect, you have a corrupted logger memory. So, weewxd is unable to retrieve 
anything from it.

 

To fix: 
https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory

 

-tk

 

 

On Wed, Jan 6, 2021 at 9:44 AM billandcorena ahrens mailto:ord...@billandcorena.com> > wrote:

$ sudo tail -f /var/log/syslog

Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'

Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.manager: Starting backfill 
of daily summaries

Jan  6 10:37:07 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Getting 
all archive packets

Jan  6 10:37:08 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retrieving 
263 page(s); starting index= 0

Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty 
record page 0; index 0

Jan  6 10:37:09 raspberrypi weewx[9872] INFO weewx.engine: Starting main packet 
loop.

Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.

Jan  6 10:37:11 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:38:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Getting 
all archive packets

Jan  6 10:38:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry #0 
failed

Jan  6 10:38:26 raspberrypi weewx[9872] ERROR weewx.drivers.vantage: ip-read 
error: timed out

Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry #1 
failed

Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:38:27 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retrieving 
263 page(s); starting index= 0

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty 
record page 0; index 0

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
reports for latest time in the database.

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weew

RE: [weewx-user] cant find start time

[orders]

I used the dump command and it finished no change  and the other one was the 
same. So I went back to software and am getting a good web page.

 

From: weewx-user@googlegroups.com  On Behalf Of 
gjr80
Sent: Wednesday, January 6, 2021 3:48 PM
To: weewx-user 
Subject: Re: [weewx-user] cant find start time

 

We haven't seen the exact wee_device commands issued and the exact response, 
perhaps seeing those might go some way towards answering that question?

 

Gary

 

On Thursday, 7 January 2021 at 08:12:00 UTC+10 tke...@gmail.com 
  wrote:

Oh. You're going through Meteobridge? That's an important detail. 

 

WeeWX expects to be able to control the state of the Vantage station. I don't 
know if it can do that going through a Meteobridge. I'm not even sure what that 
means.

 

-tk

 

-- 
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/_N1v-H0ipFY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bb348b0d-6585-4214-b3d5-98ade4590b9bn%40googlegroups.com
 

 .

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/01fa01d6e47f%248eca7220%24ac5f5660%24%40billandcorena.com.

Re: [weewx-user] cant find start time

[gjr80]

We haven't seen the exact wee_device commands issued and the exact 
response, perhaps seeing those might go some way towards answering that 
question?

Gary

On Thursday, 7 January 2021 at 08:12:00 UTC+10 tke...@gmail.com wrote:

> Oh. You're going through Meteobridge? That's an important detail. 
>
> WeeWX expects to be able to control the state of the Vantage station. I 
> don't know if it can do that going through a Meteobridge. I'm not even sure 
> what that means.
>
> -tk
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bb348b0d-6585-4214-b3d5-98ade4590b9bn%40googlegroups.com.

Re: [weewx-user] cant find start time

[Tom Keffer]

Oh. You're going through Meteobridge? That's an important detail.

WeeWX expects to be able to control the state of the Vantage station. I
don't know if it can do that going through a Meteobridge. I'm not even sure
what that means.

-tk

On Wed, Jan 6, 2021 at 1:15 PM  wrote:

> I tried to go back to hardware, after using wee-device commands but it
> stopped again.  I am connecting to the Vantage Pro2 thru a meteobridge and
> have other software running on windows, was just trying to learn something
> new but I am not sure that rasberryPi  is not above my head so as long as
> it works with software generation will leave it that way. I have learned
> some form this I guess.
>
> Bill
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *gjr80
> *Sent:* Wednesday, January 6, 2021 12:50 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] cant find start time
>
>
>
> ...and then change back to hardware record generation.
>
>
>
> Gary
>
> On Thursday, 7 January 2021 at 05:45:59 UTC+10 tke...@gmail.com wrote:
>
> That's good, but you really should clear the logger memory. Otherwise, you
> won't be able to enjoy a key feature of weewx + Vantage: the ability to
> continue to log data, even if your computer crashes, your network goes
> down, or you experience a power outage.
>
>
>
>
>
> On Wed, Jan 6, 2021 at 10:59 AM  wrote:
>
> Seems to be working after I used the software records.
>
> Bill
>
>
>
> *From:* weewx...@googlegroups.com  *On Behalf
> Of *Tom Keffer
> *Sent:* Wednesday, January 6, 2021 11:36 AM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] cant find start time
>
>
>
> The error "cannot find start time" happens when there is nothing in the
> database. Is this the first time you've used the database?
>
>
>
> Normally, there is something in the database before a report is generated,
> but, I suspect, you have a corrupted logger memory. So, weewxd is unable to
> retrieve anything from it.
>
>
>
> To fix:
> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory
>
>
>
> -tk
>
>
>
>
>
> On Wed, Jan 6, 2021 at 9:44 AM billandcorena ahrens <
> ord...@billandcorena.com> wrote:
>
> $ sudo tail -f /var/log/syslog
>
> Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.engine: Using binding
> 'wx_binding' to database 'weewx.sdb'
>
> Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.manager: Starting
> backfill of daily summaries
>
> Jan  6 10:37:07 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Getting all archive packets
>
> Jan  6 10:37:08 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Retrieving 263 page(s); starting index= 0
>
> Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty
> record page 0; index 0
>
> Jan  6 10:37:09 raspberrypi weewx[9872] INFO weewx.engine: Starting main
> packet loop.
>
> Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Requesting 200 LOOP packets.
>
> Jan  6 10:37:11 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jan  6 10:38:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Getting all archive packets
>
> Jan  6 10:38:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry
> #0 failed
>
> Jan  6 10:38:26 raspberrypi weewx[9872] ERROR weewx.drivers.vantage:
> ip-read error: timed out
>
> Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry
> #1 failed
>
> Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jan  6 10:38:27 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Retrieving 263 page(s); starting index= 0
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty
> record page 0; index 0
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running
> reports for latest time in the database.
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Requesting 200 LOOP packets.
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running
> report 'SeasonsReport'
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Found
> configuration file /etc/weewx/skins/Seasons/skin.conf for report
> 'SeasonsReport'
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.cheetahgenerator:
> Using search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
> 'weewx.cheetahgenerator.Extras']
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary
> version is 3.0
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template NOAA/NOAA-%Y-%m.txt.tmpl

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[John Kline]

> I'll restart weewx at midnight, so as to not foul the daily data 
> capture/reporting.

You don’t need to wait until midnight.  If it’s raining when you do it, you 
have the danger of missing a tip; but otherwise, there is no issue with 
restarting it.

> On Jan 6, 2021, at 1:24 PM, tim lambert  wrote:
> 
> 
> Yep! A rookie mistake, which after some reflection I realized the error in my 
> ways -- thus the reason why I'm an ERP Implementation Program/Project 
> Manager, that is very very dependent on the Technical Team (they've simply 
> taught me how to translate techie to customer execs and now I'm trying to be 
> hands-on in the tech world).
> 
> I'll restart weewx at midnight, so as to not foul the daily data 
> capture/reporting.
> 
> Again, many thanks for your assistance and patience.
> 
> Regards!
> 
> 
>> On Wednesday, January 6, 2021 at 1:18:42 PM UTC-8 jo...@johnkline.com wrote:
>> Yeah, I pieced together how you got that error message.  You were asking the 
>> python interpreter to execute a shell script.
>> 
>> jkline@judy:~/software/weewx $ python  util/scripts/wee_extension 
>>   File "util/scripts/wee_extension", line 6
>> WEEWX_BINDIR=/home/weewx/bin
>> 
 On Jan 6, 2021, at 12:59 PM, tim lambert  wrote:
 
>>> 
>> 
>>> Thanks John!
>>> 
>>> I first needed to get to the proper location to execute the wee_installer 
>>> -- that being /home/weewx/bin
>>> 
>>> Then I executed the command, but with a sudo python3 ...
>>> 
>>> This loaded the weewx-ip-100-master.zip I downloaded from github
>>> 
>>> I assume I'll need to restart weewx?
 On Wednesday, January 6, 2021 at 12:37:51 PM UTC-8 jo...@johnkline.com 
 wrote:
 The directions say:
 
 sudo wee_extension --install weewx-ip100-0.5.zip
 
 I just replaced the name of the zip.
 
 It looks like you typed python, rather than sudo.
 Please try again to install the 0.5 version, and tell me how that goes and 
 the exact command line you used to install 0.5.  Then, we can go from 
 there.
 
>> On Jan 6, 2021, at 12:33 PM, tim lambert  wrote:
>> 
> 
 
> Using the directions outlined in the readme with 0.5 version
> 
> 
>> On Wednesday, January 6, 2021 at 12:28:29 PM UTC-8 jo...@johnkline.com 
>> wrote:
>> How did you install the 0.5 version?
>> 
 On Jan 6, 2021, at 11:57 AM, tim lambert  wrote:
 
>>> 
>> 
>>> Thanks John!
>>> 
>>> Unfortunately, I'm getting an error when executing the install:
>>> 
>>> python  wee_extension --install /home/pi/FTP/weewx-ip100-master.zip
>>>   File "wee_extension", line 6
>>> WEEWX_BINDIR=/home/weewx/bin
>>>  ^
>>> SyntaxError: invalid syntax
>>> 
>>> 
>>> Any ideas?
>>> 
>>> On Wednesday, January 6, 2021 at 11:20:58 AM UTC-8 jo...@johnkline.com 
>>> wrote:
> where can I exactly find the inclusion of the station volts
 
 
 Download this file:
 https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip
 
 Then:
 
 sudo wee_extension --install master.zip
 
 
>> On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:
>> 
> 
 
> Hi John,
> 
> After leaving the server run uninterrupted, all of the data being 
> displayed on weewx is ticking to the ip-100 console.   
> 
> Apologies for my ignorance, where can I exactly find the inclusion of 
> the station volts you noted in your last comm (btw Thanks for 
> addressing).
> 
>> On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com 
>> wrote:
>> > Once I sort this possible discrepancy, I'd like to pick your brain 
>> > on adding the Station Volts.
>> 
>> I added it at head.  Station volts will now show up as supplyVoltage.
>> 
 On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
 
>>> 
>> 
>>> The IP100 resets the day’s rain total at midnight (according to 
>>> it’s clock).  It doesn’t really matter to the driver when that 
>>> happens.  The driver is simply looking for a positive increment in 
>>> day_rain_total.  On a negative increment (e.g., reset), the driver 
>>> just saves the last value and reports 0.0 for rain.
>>> 
> On Jan 4, 2021, at 7:40 PM, tim lambert  
> wrote:
> 
 
 Thanks for the guidance John!   I was anticipating to simply have 
 a day with a clean run, starting at midnight.  I should have this 
 info tomorrow.
 
 I assume the loop will recognize my local timezone to reset to 
 zero at midnight, recognizing the db is being recorded on GMT?
 
 Once I sort this possibl

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[tim lambert]

Yep! A rookie mistake, which after some reflection I realized the error in 
my ways -- thus the reason why I'm an ERP Implementation Program/Project 
Manager, that is very very dependent on the Technical Team (they've simply 
taught me how to translate techie to customer execs and now I'm trying to 
be hands-on in the tech world).

I'll restart weewx at midnight, so as to not foul the daily data 
capture/reporting.

Again, many thanks for your assistance and patience.

Regards!


On Wednesday, January 6, 2021 at 1:18:42 PM UTC-8 jo...@johnkline.com wrote:

> Yeah, I pieced together how you got that error message.  You were asking 
> the python interpreter to execute a shell script.
>
> jkline@judy:~/software/weewx $ python  util/scripts/wee_extension 
>   File "util/scripts/wee_extension", line 6
> WEEWX_BINDIR=/home/weewx/bin
>
> On Jan 6, 2021, at 12:59 PM, tim lambert  wrote:
>
> 
>
> Thanks John!
>
> I first needed to get to the proper location to execute the wee_installer 
> -- that being /home/weewx/bin
>
> Then I executed the command, but with a sudo python3 ...
>
> This loaded the weewx-ip-100-master.zip I downloaded from github
>
> I assume I'll need to restart weewx?
> On Wednesday, January 6, 2021 at 12:37:51 PM UTC-8 jo...@johnkline.com 
> wrote:
>
>> The directions say:
>>
>>
>> sudo wee_extension --install weewx-ip100-0.5.zip
>>
>>
>> I just replaced the name of the zip.
>>
>> It looks like you typed python, rather than sudo.
>> Please try again to install the 0.5 version, and tell me how that goes 
>> and the exact command line you used to install 0.5.  Then, we can go from 
>> there.
>>
>> On Jan 6, 2021, at 12:33 PM, tim lambert  wrote:
>>
>> 
>>
>> Using the directions outlined in the readme with 0.5 version
>>
>>
>> On Wednesday, January 6, 2021 at 12:28:29 PM UTC-8 jo...@johnkline.com 
>> wrote:
>>
>>> How did you install the 0.5 version?
>>>
>>> On Jan 6, 2021, at 11:57 AM, tim lambert  wrote:
>>>
>>> 
>>>
>>> Thanks John!
>>>
>>> Unfortunately, I'm getting an error when executing the install:
>>>
>>> python  wee_extension --install /home/pi/FTP/weewx-ip100-master.zip
>>>   File "wee_extension", line 6
>>> WEEWX_BINDIR=/home/weewx/bin
>>>  ^
>>> SyntaxError: invalid syntax
>>>
>>>
>>> Any ideas?
>>>
>>> On Wednesday, January 6, 2021 at 11:20:58 AM UTC-8 jo...@johnkline.com 
>>> wrote:
>>>
 where can I exactly find the inclusion of the station volts


 Download this file:
 https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip

 Then:


 sudo wee_extension --install master.zip



 On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:

 

 Hi John,

 After leaving the server run uninterrupted, all of the data being 
 displayed on weewx is ticking to the ip-100 console.   

 Apologies for my ignorance, where can I exactly find the inclusion of 
 the station volts you noted in your last comm (btw Thanks for addressing).

 On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com 
 wrote:

> > Once I sort this possible discrepancy, I'd like to pick your brain 
> on adding the Station Volts.
>
> I added it at head.  Station volts will now show up as supplyVoltage.
>
> On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
>
> 
>
> The IP100 resets the day’s rain total at midnight (according to it’s 
> clock).  It doesn’t really matter to the driver when that happens.  The 
> driver is simply looking for a positive increment in day_rain_total.  On 
> a 
> negative increment (e.g., reset), the driver just saves the last value 
> and 
> reports 0.0 for rain.
>
> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
>
> 
> Thanks for the guidance John!   I was anticipating to simply have a 
> day with a clean run, starting at midnight.  I should have this info 
> tomorrow.
>
> I assume the loop will recognize my local timezone to reset to zero at 
> midnight, recognizing the db is being recorded on GMT?
>
> Once I sort this possible discrepancy, I'd like to pick your brain on 
> adding the Station Volts.
>
> Regards,
>
> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com 
> wrote:
>
>> You don’t to delete records.  There isn’t really much to the rain 
>> calculation.  For all rain that occurred while WeeWX is up and running, 
>> the 
>> day_rain_total will increment, the driver will calculate the delta and 
>> add 
>> it to the loop record as ‘rain’.  For the discrepancy to occur, 0.09 
>> inches 
>> would have had to happen while WeeWX wasn’t running.
>>
>> Let’s try a day where WeeWX has been running, uninterrupted, since 
>> midnight.
>>
>> On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
>>
>> 
>>
>> Thanks for the quick response J

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[John Kline]

Yeah, I pieced together how you got that error message.  You were asking the 
python interpreter to execute a shell script.

jkline@judy:~/software/weewx $ python  util/scripts/wee_extension 
  File "util/scripts/wee_extension", line 6
WEEWX_BINDIR=/home/weewx/bin

> On Jan 6, 2021, at 12:59 PM, tim lambert  wrote:
> 
> 
> Thanks John!
> 
> I first needed to get to the proper location to execute the wee_installer -- 
> that being /home/weewx/bin
> 
> Then I executed the command, but with a sudo python3 ...
> 
> This loaded the weewx-ip-100-master.zip I downloaded from github
> 
> I assume I'll need to restart weewx?
>> On Wednesday, January 6, 2021 at 12:37:51 PM UTC-8 jo...@johnkline.com wrote:
>> The directions say:
>> 
>> sudo wee_extension --install weewx-ip100-0.5.zip
>> 
>> I just replaced the name of the zip.
>> 
>> It looks like you typed python, rather than sudo.
>> Please try again to install the 0.5 version, and tell me how that goes and 
>> the exact command line you used to install 0.5.  Then, we can go from there.
>> 
 On Jan 6, 2021, at 12:33 PM, tim lambert  wrote:
 
>>> 
>> 
>>> Using the directions outlined in the readme with 0.5 version
>>> 
>>> 
 On Wednesday, January 6, 2021 at 12:28:29 PM UTC-8 jo...@johnkline.com 
 wrote:
 How did you install the 0.5 version?
 
>> On Jan 6, 2021, at 11:57 AM, tim lambert  wrote:
>> 
> 
 
> Thanks John!
> 
> Unfortunately, I'm getting an error when executing the install:
> 
> python  wee_extension --install /home/pi/FTP/weewx-ip100-master.zip
>   File "wee_extension", line 6
> WEEWX_BINDIR=/home/weewx/bin
>  ^
> SyntaxError: invalid syntax
> 
> 
> Any ideas?
> 
> On Wednesday, January 6, 2021 at 11:20:58 AM UTC-8 jo...@johnkline.com 
> wrote:
>>> where can I exactly find the inclusion of the station volts
>> 
>> 
>> Download this file:
>> https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip
>> 
>> Then:
>> 
>> sudo wee_extension --install master.zip
>> 
>> 
 On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:
 
>>> 
>> 
>>> Hi John,
>>> 
>>> After leaving the server run uninterrupted, all of the data being 
>>> displayed on weewx is ticking to the ip-100 console.   
>>> 
>>> Apologies for my ignorance, where can I exactly find the inclusion of 
>>> the station volts you noted in your last comm (btw Thanks for 
>>> addressing).
>>> 
 On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com 
 wrote:
 > Once I sort this possible discrepancy, I'd like to pick your brain 
 > on adding the Station Volts.
 
 I added it at head.  Station volts will now show up as supplyVoltage.
 
>> On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
>> 
> 
 
> The IP100 resets the day’s rain total at midnight (according to it’s 
> clock).  It doesn’t really matter to the driver when that happens.  
> The driver is simply looking for a positive increment in 
> day_rain_total.  On a negative increment (e.g., reset), the driver 
> just saves the last value and reports 0.0 for rain.
> 
>>> On Jan 4, 2021, at 7:40 PM, tim lambert  
>>> wrote:
>>> 
>> 
>> Thanks for the guidance John!   I was anticipating to simply have a 
>> day with a clean run, starting at midnight.  I should have this info 
>> tomorrow.
>> 
>> I assume the loop will recognize my local timezone to reset to zero 
>> at midnight, recognizing the db is being recorded on GMT?
>> 
>> Once I sort this possible discrepancy, I'd like to pick your brain 
>> on adding the Station Volts.
>> 
>> Regards,
>> 
>>> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com 
>>> wrote:
>>> You don’t to delete records.  There isn’t really much to the rain 
>>> calculation.  For all rain that occurred while WeeWX is up and 
>>> running, the day_rain_total will increment, the driver will 
>>> calculate the delta and add it to the loop record as ‘rain’.  For 
>>> the discrepancy to occur, 0.09 inches would have had to happen 
>>> while WeeWX wasn’t running.
>>> 
>>> Let’s try a day where WeeWX has been running, uninterrupted, since 
>>> midnight.
>>> 
> On Jan 4, 2021, at 7:27 PM, tim lambert  
> wrote:
> 
 
>>> 
 Thanks for the quick response John!
 
 I am running your version of the IP100 for weewx 4 - version 0.5
 
 I did restart the weewx today -- had some network issues, 
 compliments of Comcas

RE: [weewx-user] cant find start time

[orders]

I tried to go back to hardware, after using wee-device commands but it stopped 
again.  I am connecting to the Vantage Pro2 thru a meteobridge and have other 
software running on windows, was just trying to learn something new but I am 
not sure that rasberryPi  is not above my head so as long as it works with 
software generation will leave it that way. I have learned some form this I 
guess.

Bill

 

From: weewx-user@googlegroups.com  On Behalf Of 
gjr80
Sent: Wednesday, January 6, 2021 12:50 PM
To: weewx-user 
Subject: Re: [weewx-user] cant find start time

 

...and then change back to hardware record generation.

 

Gary

On Thursday, 7 January 2021 at 05:45:59 UTC+10 tke...@gmail.com 
  wrote:

That's good, but you really should clear the logger memory. Otherwise, you 
won't be able to enjoy a key feature of weewx + Vantage: the ability to 
continue to log data, even if your computer crashes, your network goes down, or 
you experience a power outage.

 

 

On Wed, Jan 6, 2021 at 10:59 AM mailto:ord...@billandcorena.com> > wrote:

Seems to be working after I used the software records.

Bill

 

From: weewx...@googlegroups.com   
mailto:weewx...@googlegroups.com> > On Behalf Of 
Tom Keffer
Sent: Wednesday, January 6, 2021 11:36 AM
To: weewx-user mailto:weewx...@googlegroups.com> >
Subject: Re: [weewx-user] cant find start time

 

The error "cannot find start time" happens when there is nothing in the 
database. Is this the first time you've used the database?

 

Normally, there is something in the database before a report is generated, but, 
I suspect, you have a corrupted logger memory. So, weewxd is unable to retrieve 
anything from it.

 

To fix: 
https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory

 

-tk

 

 

On Wed, Jan 6, 2021 at 9:44 AM billandcorena ahrens mailto:ord...@billandcorena.com> > wrote:

$ sudo tail -f /var/log/syslog

Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'

Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.manager: Starting backfill 
of daily summaries

Jan  6 10:37:07 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Getting 
all archive packets

Jan  6 10:37:08 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retrieving 
263 page(s); starting index= 0

Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty 
record page 0; index 0

Jan  6 10:37:09 raspberrypi weewx[9872] INFO weewx.engine: Starting main packet 
loop.

Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.

Jan  6 10:37:11 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:38:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Getting 
all archive packets

Jan  6 10:38:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry #0 
failed

Jan  6 10:38:26 raspberrypi weewx[9872] ERROR weewx.drivers.vantage: ip-read 
error: timed out

Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry #1 
failed

Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:38:27 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retrieving 
263 page(s); starting index= 0

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty 
record page 0; index 0

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
reports for latest time in the database.

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary 
version is 3.0

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template NOAA/NOAA-%Y-%m.txt.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template NOAA/NOAA-%Y.txt.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template index.html.tmpl: cannot find start time

Jan  6 10:38:28 raspber

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[tim lambert]

Thanks John!

I first needed to get to the proper location to execute the wee_installer 
-- that being /home/weewx/bin

Then I executed the command, but with a sudo python3 ...

This loaded the weewx-ip-100-master.zip I downloaded from github

I assume I'll need to restart weewx?
On Wednesday, January 6, 2021 at 12:37:51 PM UTC-8 jo...@johnkline.com 
wrote:

> The directions say:
>
>
> sudo wee_extension --install weewx-ip100-0.5.zip
>
>
> I just replaced the name of the zip.
>
> It looks like you typed python, rather than sudo.
> Please try again to install the 0.5 version, and tell me how that goes and 
> the exact command line you used to install 0.5.  Then, we can go from there.
>
> On Jan 6, 2021, at 12:33 PM, tim lambert  wrote:
>
> 
>
> Using the directions outlined in the readme with 0.5 version
>
>
> On Wednesday, January 6, 2021 at 12:28:29 PM UTC-8 jo...@johnkline.com 
> wrote:
>
>> How did you install the 0.5 version?
>>
>> On Jan 6, 2021, at 11:57 AM, tim lambert  wrote:
>>
>> 
>>
>> Thanks John!
>>
>> Unfortunately, I'm getting an error when executing the install:
>>
>> python  wee_extension --install /home/pi/FTP/weewx-ip100-master.zip
>>   File "wee_extension", line 6
>> WEEWX_BINDIR=/home/weewx/bin
>>  ^
>> SyntaxError: invalid syntax
>>
>>
>> Any ideas?
>>
>> On Wednesday, January 6, 2021 at 11:20:58 AM UTC-8 jo...@johnkline.com 
>> wrote:
>>
>>> where can I exactly find the inclusion of the station volts
>>>
>>>
>>> Download this file:
>>> https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip
>>>
>>> Then:
>>>
>>>
>>> sudo wee_extension --install master.zip
>>>
>>>
>>>
>>> On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:
>>>
>>> 
>>>
>>> Hi John,
>>>
>>> After leaving the server run uninterrupted, all of the data being 
>>> displayed on weewx is ticking to the ip-100 console.   
>>>
>>> Apologies for my ignorance, where can I exactly find the inclusion of 
>>> the station volts you noted in your last comm (btw Thanks for addressing).
>>>
>>> On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com 
>>> wrote:
>>>
 > Once I sort this possible discrepancy, I'd like to pick your brain 
 on adding the Station Volts.

 I added it at head.  Station volts will now show up as supplyVoltage.

 On Jan 4, 2021, at 7:44 PM, John Kline  wrote:

 

 The IP100 resets the day’s rain total at midnight (according to it’s 
 clock).  It doesn’t really matter to the driver when that happens.  The 
 driver is simply looking for a positive increment in day_rain_total.  On a 
 negative increment (e.g., reset), the driver just saves the last value and 
 reports 0.0 for rain.

 On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:

 
 Thanks for the guidance John!   I was anticipating to simply have a day 
 with a clean run, starting at midnight.  I should have this info tomorrow.

 I assume the loop will recognize my local timezone to reset to zero at 
 midnight, recognizing the db is being recorded on GMT?

 Once I sort this possible discrepancy, I'd like to pick your brain on 
 adding the Station Volts.

 Regards,

 On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com 
 wrote:

> You don’t to delete records.  There isn’t really much to the rain 
> calculation.  For all rain that occurred while WeeWX is up and running, 
> the 
> day_rain_total will increment, the driver will calculate the delta and 
> add 
> it to the loop record as ‘rain’.  For the discrepancy to occur, 0.09 
> inches 
> would have had to happen while WeeWX wasn’t running.
>
> Let’s try a day where WeeWX has been running, uninterrupted, since 
> midnight.
>
> On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
>
> 
>
> Thanks for the quick response John!
>
> I am running your version of the IP100 for weewx 4 - version 0.5
>
> I did restart the weewx today -- had some network issues, compliments 
> of Comcast.   However, I've witnessed discrepancies between the IP100 
> Console and weewx for several days -- just finally had a chance to get 
> some 
> data captures.   I may need to capture data again tomorrow (knowing it 
> will 
> be raining buckets again).
>
> At this point in time:
>
>   
> IP100weewx
> Rainfall  
> 0.06   0.15
> Rain Rate  
> 0.00   0.00
>
> Can I truncate (delete all records) from the weewx.sdb (after backing 
> up of course) to start fresh, so that we have a solid baseline to 
> evaluate?
>
> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com 
> wrote:
>
>> Station volt

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[John Kline]

The directions say:

sudo wee_extension --install weewx-ip100-0.5.zip

I just replaced the name of the zip.

It looks like you typed python, rather than sudo.
Please try again to install the 0.5 version, and tell me how that goes and the 
exact command line you used to install 0.5.  Then, we can go from there.

> On Jan 6, 2021, at 12:33 PM, tim lambert  wrote:
> 
> 
> Using the directions outlined in the readme with 0.5 version
> 
> 
>> On Wednesday, January 6, 2021 at 12:28:29 PM UTC-8 jo...@johnkline.com wrote:
>> How did you install the 0.5 version?
>> 
 On Jan 6, 2021, at 11:57 AM, tim lambert  wrote:
 
>>> 
>> 
>>> Thanks John!
>>> 
>>> Unfortunately, I'm getting an error when executing the install:
>>> 
>>> python  wee_extension --install /home/pi/FTP/weewx-ip100-master.zip
>>>   File "wee_extension", line 6
>>> WEEWX_BINDIR=/home/weewx/bin
>>>  ^
>>> SyntaxError: invalid syntax
>>> 
>>> 
>>> Any ideas?
>>> 
>>> On Wednesday, January 6, 2021 at 11:20:58 AM UTC-8 jo...@johnkline.com 
>>> wrote:
> where can I exactly find the inclusion of the station volts
 
 
 Download this file:
 https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip
 
 Then:
 
 sudo wee_extension --install master.zip
 
 
>> On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:
>> 
> 
 
> Hi John,
> 
> After leaving the server run uninterrupted, all of the data being 
> displayed on weewx is ticking to the ip-100 console.   
> 
> Apologies for my ignorance, where can I exactly find the inclusion of the 
> station volts you noted in your last comm (btw Thanks for addressing).
> 
>> On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com wrote:
>> > Once I sort this possible discrepancy, I'd like to pick your brain on 
>> > adding the Station Volts.
>> 
>> I added it at head.  Station volts will now show up as supplyVoltage.
>> 
 On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
 
>>> 
>> 
>>> The IP100 resets the day’s rain total at midnight (according to it’s 
>>> clock).  It doesn’t really matter to the driver when that happens.  The 
>>> driver is simply looking for a positive increment in day_rain_total.  
>>> On a negative increment (e.g., reset), the driver just saves the last 
>>> value and reports 0.0 for rain.
>>> 
> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
> 
 
 Thanks for the guidance John!   I was anticipating to simply have a 
 day with a clean run, starting at midnight.  I should have this info 
 tomorrow.
 
 I assume the loop will recognize my local timezone to reset to zero at 
 midnight, recognizing the db is being recorded on GMT?
 
 Once I sort this possible discrepancy, I'd like to pick your brain on 
 adding the Station Volts.
 
 Regards,
 
> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com 
> wrote:
> You don’t to delete records.  There isn’t really much to the rain 
> calculation.  For all rain that occurred while WeeWX is up and 
> running, the day_rain_total will increment, the driver will calculate 
> the delta and add it to the loop record as ‘rain’.  For the 
> discrepancy to occur, 0.09 inches would have had to happen while 
> WeeWX wasn’t running.
> 
> Let’s try a day where WeeWX has been running, uninterrupted, since 
> midnight.
> 
>>> On Jan 4, 2021, at 7:27 PM, tim lambert  
>>> wrote:
>>> 
>> 
> 
>> Thanks for the quick response John!
>> 
>> I am running your version of the IP100 for weewx 4 - version 0.5
>> 
>> I did restart the weewx today -- had some network issues, 
>> compliments of Comcast.   However, I've witnessed discrepancies 
>> between the IP100 Console and weewx for several days -- just finally 
>> had a chance to get some data captures.   I may need to capture data 
>> again tomorrow (knowing it will be raining buckets again).
>> 
>> At this point in time:
>> 
>>   IP100  
>>   weewx
>> Rainfall  0.06   
>> 0.15
>> Rain Rate  0.00  
>>  0.00
>> 
>> Can I truncate (delete all records) from the weewx.sdb (after 
>> backing up of course) to start fresh, so that we have a solid 
>> baseline to evaluate?
>> 
>>> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com 
>>> wrote:
>>> Station volts is not in the d

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[tim lambert]

Using the directions outlined in the readme with 0.5 version


On Wednesday, January 6, 2021 at 12:28:29 PM UTC-8 jo...@johnkline.com 
wrote:

> How did you install the 0.5 version?
>
> On Jan 6, 2021, at 11:57 AM, tim lambert  wrote:
>
> 
>
> Thanks John!
>
> Unfortunately, I'm getting an error when executing the install:
>
> python  wee_extension --install /home/pi/FTP/weewx-ip100-master.zip
>   File "wee_extension", line 6
> WEEWX_BINDIR=/home/weewx/bin
>  ^
> SyntaxError: invalid syntax
>
>
> Any ideas?
>
> On Wednesday, January 6, 2021 at 11:20:58 AM UTC-8 jo...@johnkline.com 
> wrote:
>
>> where can I exactly find the inclusion of the station volts
>>
>>
>> Download this file:
>> https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip
>>
>> Then:
>>
>>
>> sudo wee_extension --install master.zip
>>
>>
>>
>> On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:
>>
>> 
>>
>> Hi John,
>>
>> After leaving the server run uninterrupted, all of the data being 
>> displayed on weewx is ticking to the ip-100 console.   
>>
>> Apologies for my ignorance, where can I exactly find the inclusion of the 
>> station volts you noted in your last comm (btw Thanks for addressing).
>>
>> On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com wrote:
>>
>>> > Once I sort this possible discrepancy, I'd like to pick your brain on 
>>> adding the Station Volts.
>>>
>>> I added it at head.  Station volts will now show up as supplyVoltage.
>>>
>>> On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
>>>
>>> 
>>>
>>> The IP100 resets the day’s rain total at midnight (according to it’s 
>>> clock).  It doesn’t really matter to the driver when that happens.  The 
>>> driver is simply looking for a positive increment in day_rain_total.  On a 
>>> negative increment (e.g., reset), the driver just saves the last value and 
>>> reports 0.0 for rain.
>>>
>>> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
>>>
>>> 
>>> Thanks for the guidance John!   I was anticipating to simply have a day 
>>> with a clean run, starting at midnight.  I should have this info tomorrow.
>>>
>>> I assume the loop will recognize my local timezone to reset to zero at 
>>> midnight, recognizing the db is being recorded on GMT?
>>>
>>> Once I sort this possible discrepancy, I'd like to pick your brain on 
>>> adding the Station Volts.
>>>
>>> Regards,
>>>
>>> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com 
>>> wrote:
>>>
 You don’t to delete records.  There isn’t really much to the rain 
 calculation.  For all rain that occurred while WeeWX is up and running, 
 the 
 day_rain_total will increment, the driver will calculate the delta and add 
 it to the loop record as ‘rain’.  For the discrepancy to occur, 0.09 
 inches 
 would have had to happen while WeeWX wasn’t running.

 Let’s try a day where WeeWX has been running, uninterrupted, since 
 midnight.

 On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:

 

 Thanks for the quick response John!

 I am running your version of the IP100 for weewx 4 - version 0.5

 I did restart the weewx today -- had some network issues, compliments 
 of Comcast.   However, I've witnessed discrepancies between the IP100 
 Console and weewx for several days -- just finally had a chance to get 
 some 
 data captures.   I may need to capture data again tomorrow (knowing it 
 will 
 be raining buckets again).

 At this point in time:

   
 IP100weewx
 Rainfall  
 0.06   0.15
 Rain Rate  
 0.00   0.00

 Can I truncate (delete all records) from the weewx.sdb (after backing 
 up of course) to start fresh, so that we have a solid baseline to evaluate?

 On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com 
 wrote:

> Station volts is not in the default map.  It wouldn’t be hard to add.
>
> I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and 
> bumped the version to 0.5 in my fork).  I’m presuming you are running it.
>
> Although I’m not currently running the driver, I did run it for almost 
> two years and rain values ALWAYS agreed with my WeeWX instances running 
> the 
> CC3000 driver and talking to the same RainWise weather station.
>
> day_rain_total is used to calculate rain.  It is not, in itself saved 
> to the database.
>
> I have not downloaded your files.  You’ll have to tell me if the ip100 
> console does not agree with the console for today’s rain and, if not, 
> what 
> two values you are seeing.  Please list them.
>
> If you do have a discrepancy for today’s rain, please state if you 
> restarted weewx today (or i

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[John Kline]

How did you install the 0.5 version?

> On Jan 6, 2021, at 11:57 AM, tim lambert  wrote:
> 
> 
> Thanks John!
> 
> Unfortunately, I'm getting an error when executing the install:
> 
> python  wee_extension --install /home/pi/FTP/weewx-ip100-master.zip
>   File "wee_extension", line 6
> WEEWX_BINDIR=/home/weewx/bin
>  ^
> SyntaxError: invalid syntax
> 
> 
> Any ideas?
> 
> On Wednesday, January 6, 2021 at 11:20:58 AM UTC-8 jo...@johnkline.com wrote:
>>> where can I exactly find the inclusion of the station volts
>> 
>> 
>> Download this file:
>> https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip
>> 
>> Then:
>> 
>> sudo wee_extension --install master.zip
>> 
>> 
>>> On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:
>>> 
>>> 
>> 
>>> Hi John,
>>> 
>>> After leaving the server run uninterrupted, all of the data being displayed 
>>> on weewx is ticking to the ip-100 console.   
>>> 
>>> Apologies for my ignorance, where can I exactly find the inclusion of the 
>>> station volts you noted in your last comm (btw Thanks for addressing).
>>> 
>>> On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com wrote:
 > Once I sort this possible discrepancy, I'd like to pick your brain on 
 > adding the Station Volts.
 
 I added it at head.  Station volts will now show up as supplyVoltage.
 
> On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
> 
> 
 
> The IP100 resets the day’s rain total at midnight (according to it’s 
> clock).  It doesn’t really matter to the driver when that happens.  The 
> driver is simply looking for a positive increment in day_rain_total.  On 
> a negative increment (e.g., reset), the driver just saves the last value 
> and reports 0.0 for rain.
> 
>> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
>> 
>> 
>> Thanks for the guidance John!   I was anticipating to simply have a day 
>> with a clean run, starting at midnight.  I should have this info 
>> tomorrow.
>> 
>> I assume the loop will recognize my local timezone to reset to zero at 
>> midnight, recognizing the db is being recorded on GMT?
>> 
>> Once I sort this possible discrepancy, I'd like to pick your brain on 
>> adding the Station Volts.
>> 
>> Regards,
>> 
>> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com wrote:
>>> You don’t to delete records.  There isn’t really much to the rain 
>>> calculation.  For all rain that occurred while WeeWX is up and running, 
>>> the day_rain_total will increment, the driver will calculate the delta 
>>> and add it to the loop record as ‘rain’.  For the discrepancy to occur, 
>>> 0.09 inches would have had to happen while WeeWX wasn’t running.
>>> 
>>> Let’s try a day where WeeWX has been running, uninterrupted, since 
>>> midnight.
>>> 
 On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
 
 
>>> 
 Thanks for the quick response John!
 
 I am running your version of the IP100 for weewx 4 - version 0.5
 
 I did restart the weewx today -- had some network issues, compliments 
 of Comcast.   However, I've witnessed discrepancies between the IP100 
 Console and weewx for several days -- just finally had a chance to get 
 some data captures.   I may need to capture data again tomorrow 
 (knowing it will be raining buckets again).
 
 At this point in time:
 
   IP100
 weewx
 Rainfall  0.06 
   0.15
 Rain Rate  0.00
0.00
 
 Can I truncate (delete all records) from the weewx.sdb (after backing 
 up of course) to start fresh, so that we have a solid baseline to 
 evaluate?
 
> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com 
> wrote:
>> Station volts is not in the default map.  It wouldn’t be hard to add.
>> 
>> I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and 
>> bumped the version to 0.5 in my fork).  I’m presuming you are 
>> running it.
>> 
>> Although I’m not currently running the driver, I did run it for 
>> almost two years and rain values ALWAYS agreed with my WeeWX 
>> instances running the CC3000 driver and talking to the same RainWise 
>> weather station.
>> 
>> day_rain_total is used to calculate rain.  It is not, in itself 
>> saved to the database.
>> 
>> I have not downloaded your files.  You’ll have to tell me if the 
>> ip100 console does not agree with the console for today’s rain and, 
>> if n

Re: [weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Michael Sanphillipo]

Tom, thanks for your help I'm up and running!!

On Wednesday, January 6, 2021 at 3:00:53 PM UTC-5 tke...@gmail.com wrote:

> Good heavens. That's a lot. I wonder where they all came from?
>
> No matter. Here's how to fix (and sorry for giving you the wrong path to 
> the database).
>
> # First stop weewx
> *sudo systemctl stop weewx*
>
> *cd /var/lib/weewx*
>
> # Make a backup:
> *sudo cp weewx.sdb weewx.sdb.backup*
>
> # Delete all records where interval equals zero:
> *sudo sqlite3 weewx.sdb*
> sqlite> *delete from archive where interval==0;*
> sqlite> *.quit*
>
> # Restart weewx
> *sudo systemctl start weewx*
>
> If you get this error again, there is something wrong with the 
> configuration of your system.
>
> -tk
>
>
> On Wed, Jan 6, 2021 at 11:17 AM Michael Sanphillipo  
> wrote:
>
>> Tom, here are my results. Please let me know what to do next. Thanks!
>>
>> /var/lib/weewx $ sqlite3 /var/lib/weewx/weewx.sdb
>> SQLite version 3.27.2 2019-02-25 16:06:06
>> Enter ".help" for usage hints.
>> sqlite> select dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
>> interval from archive where interval<=0;
>> 1527646827|2018-05-29 22:20:27|0
>> 1528167350|2018-06-04 22:55:50|0
>> 1528498208|2018-06-08 18:50:08|0
>> 1528514117|2018-06-08 23:15:17|0
>> 1529163904|2018-06-16 11:45:04|0
>> 1529250650|2018-06-17 11:50:50|0
>> 1529969403|2018-06-25 19:30:03|0
>> 1530019815|2018-06-26 09:30:15|0
>> 1530045606|2018-06-26 16:40:06|0
>> 1531475142|2018-07-13 05:45:42|0
>> 1531637727|2018-07-15 02:55:27|0
>> 1532338834|2018-07-23 05:40:34|0
>> 1532424936|2018-07-24 05:35:36|0
>> 1532451003|2018-07-24 12:50:03|0
>> 1532459736|2018-07-24 15:15:36|0
>> 1532470836|2018-07-24 18:20:36|0
>> 1532548520|2018-07-25 15:55:20|0
>> 1536048937|2018-09-04 04:15:37|0
>> 1536216049|2018-09-06 02:40:49|0
>> 1536282003|2018-09-06 21:00:03|0
>> 1536954915|2018-09-14 15:55:15|0
>> 1537301423|2018-09-18 16:10:23|0
>> 1537933226|2018-09-25 23:40:26|0
>> 153857|2018-10-03 09:10:22|0
>> 1538660412|2018-10-04 09:40:12|0
>> 1538750748|2018-10-05 10:45:48|0
>> 1538870425|2018-10-06 20:00:25|0
>> 1538878546|2018-10-06 22:15:46|0
>> 1538967014|2018-10-07 22:50:14|0
>> 1539012006|2018-10-08 11:20:06|0
>> 1539111014|2018-10-09 14:50:14|0
>> 1539128421|2018-10-09 19:40:21|0
>> 1539129900|2018-10-09 20:05:00|0
>> 1539179426|2018-10-10 09:50:26|0
>> 1539360622|2018-10-12 12:10:22|0
>> 1539397529|2018-10-12 22:25:29|0
>> 1539448534|2018-10-13 12:35:34|0
>> 1539869437|2018-10-18 09:30:37|0
>> 1540113330|2018-10-21 05:15:30|0
>> 1540530332|2018-10-26 01:05:32|0
>> 1541252127|2018-11-03 09:35:27|0
>> 1541906710|2018-11-10 22:25:10|0
>> 1542099614|2018-11-13 04:00:14|0
>> 1543282805|2018-11-26 20:40:05|0
>> 1543788916|2018-12-02 17:15:16|0
>> 1543792503|2018-12-02 18:15:03|0
>> 1543828523|2018-12-03 04:15:23|0
>> 1543838124|2018-12-03 06:55:24|0
>> 1544019616|2018-12-05 09:20:16|0
>> 1544168454|2018-12-07 02:40:54|0
>> 1544239551|2018-12-07 22:25:51|0
>> 1544372440|2018-12-09 11:20:40|0
>> 1544904031|2018-12-15 15:00:31|0
>> 1545071707|2018-12-17 13:35:07|0
>> 1545429933|2018-12-21 17:05:33|0
>> 1545432303|2018-12-21 17:45:03|0
>> 1546150235|2018-12-30 01:10:35|0
>> 1546475415|2019-01-02 19:30:15|0
>> 1546518003|2019-01-03 07:20:03|0
>> 1547684108|2019-01-16 19:15:08|0
>> 1547692525|2019-01-16 21:35:25|0
>> 1547745917|2019-01-17 12:25:17|0
>> 1547795720|2019-01-18 02:15:20|0
>> 1547847003|2019-01-18 16:30:03|0
>> 1547885706|2019-01-19 03:15:06|0
>> 1547921726|2019-01-19 13:15:26|0
>> 1548084634|2019-01-21 10:30:34|0
>> 1548111631|2019-01-21 18:00:31|0
>> 1548140733|2019-01-22 02:05:33|0
>> 1548149429|2019-01-22 04:30:29|0
>> 1548172814|2019-01-22 11:00:14|0
>> 1548200418|2019-01-22 18:40:18|0
>> 1548355828|2019-01-24 13:50:28|0
>> 1548435918|2019-01-25 12:05:18|0
>> 1548532233|2019-01-26 14:50:33|0
>> 1548746432|2019-01-29 02:20:32|0
>> 1548782434|2019-01-29 12:20:34|0
>> 1548838528|2019-01-30 03:55:28|0
>> 1548889502|2019-01-30 18:05:02|0
>> 1549086926|2019-02-02 00:55:26|0
>> 1549353629|2019-02-05 03:00:29|0
>> 1549419305|2019-02-05 21:15:05|0
>> 1549438213|2019-02-06 02:30:13|0
>> 1549454715|2019-02-06 07:05:15|0
>> 1549679405|2019-02-08 21:30:05|0
>> 1549784417|2019-02-10 02:40:17|0
>> 1549825526|2019-02-10 14:05:26|0
>> 1549830909|2019-02-10 15:35:09|0
>> 1549874404|2019-02-11 03:40:04|0
>> 1550099133|2019-02-13 18:05:33|0
>> 1550101539|2019-02-13 18:45:39|0
>> 1550187328|2019-02-14 18:35:28|0
>> 1550194210|2019-02-14 20:30:10|0
>> 1550291412|2019-02-15 23:30:12|0
>> 1550573420|2019-02-19 05:50:20|0
>> 1550820921|2019-02-22 02:35:21|0
>> 1550881824|2019-02-22 19:30:24|0
>> 1551015637|2019-02-24 08:40:37|0
>> 1552304140|2019-03-11 07:35:40|0
>> 1552354241|2019-03-11 21:30:41|0
>> 1552566905|2019-03-14 08:35:05|0
>> 1552827608|2019-03-17 09:00:08|0
>> 1552918802|2019-03-18 10:20:02|0
>> 1554167132|2019-04-01 21:05:32|0
>> 1554227428|2019-04-02 13:50:28|0
>> 1554549615|2019-04-06 07:20:15|0
>> 1554727516|2019-04-08 08:45:16|0
>> 1554934221|2019-04

Re: [weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Tom Keffer]

Good heavens. That's a lot. I wonder where they all came from?

No matter. Here's how to fix (and sorry for giving you the wrong path to
the database).

# First stop weewx
*sudo systemctl stop weewx*

*cd /var/lib/weewx*

# Make a backup:
*sudo cp weewx.sdb weewx.sdb.backup*

# Delete all records where interval equals zero:
*sudo sqlite3 weewx.sdb*
sqlite> *delete from archive where interval==0;*
sqlite> *.quit*

# Restart weewx
*sudo systemctl start weewx*

If you get this error again, there is something wrong with the
configuration of your system.

-tk


On Wed, Jan 6, 2021 at 11:17 AM Michael Sanphillipo 
wrote:

> Tom, here are my results. Please let me know what to do next. Thanks!
>
> /var/lib/weewx $ sqlite3 /var/lib/weewx/weewx.sdb
> SQLite version 3.27.2 2019-02-25 16:06:06
> Enter ".help" for usage hints.
> sqlite> select dateTime, datetime(dateTime, 'unixepoch', 'localtime'),
> interval from archive where interval<=0;
> 1527646827|2018-05-29 22:20:27|0
> 1528167350|2018-06-04 22:55:50|0
> 1528498208|2018-06-08 18:50:08|0
> 1528514117|2018-06-08 23:15:17|0
> 1529163904|2018-06-16 11:45:04|0
> 1529250650|2018-06-17 11:50:50|0
> 1529969403|2018-06-25 19:30:03|0
> 1530019815|2018-06-26 09:30:15|0
> 1530045606|2018-06-26 16:40:06|0
> 1531475142|2018-07-13 05:45:42|0
> 1531637727|2018-07-15 02:55:27|0
> 1532338834|2018-07-23 05:40:34|0
> 1532424936|2018-07-24 05:35:36|0
> 1532451003|2018-07-24 12:50:03|0
> 1532459736|2018-07-24 15:15:36|0
> 1532470836|2018-07-24 18:20:36|0
> 1532548520|2018-07-25 15:55:20|0
> 1536048937|2018-09-04 04:15:37|0
> 1536216049|2018-09-06 02:40:49|0
> 1536282003|2018-09-06 21:00:03|0
> 1536954915|2018-09-14 15:55:15|0
> 1537301423|2018-09-18 16:10:23|0
> 1537933226|2018-09-25 23:40:26|0
> 153857|2018-10-03 09:10:22|0
> 1538660412|2018-10-04 09:40:12|0
> 1538750748|2018-10-05 10:45:48|0
> 1538870425|2018-10-06 20:00:25|0
> 1538878546|2018-10-06 22:15:46|0
> 1538967014|2018-10-07 22:50:14|0
> 1539012006|2018-10-08 11:20:06|0
> 1539111014|2018-10-09 14:50:14|0
> 1539128421|2018-10-09 19:40:21|0
> 1539129900|2018-10-09 20:05:00|0
> 1539179426|2018-10-10 09:50:26|0
> 1539360622|2018-10-12 12:10:22|0
> 1539397529|2018-10-12 22:25:29|0
> 1539448534|2018-10-13 12:35:34|0
> 1539869437|2018-10-18 09:30:37|0
> 1540113330|2018-10-21 05:15:30|0
> 1540530332|2018-10-26 01:05:32|0
> 1541252127|2018-11-03 09:35:27|0
> 1541906710|2018-11-10 22:25:10|0
> 1542099614|2018-11-13 04:00:14|0
> 1543282805|2018-11-26 20:40:05|0
> 1543788916|2018-12-02 17:15:16|0
> 1543792503|2018-12-02 18:15:03|0
> 1543828523|2018-12-03 04:15:23|0
> 1543838124|2018-12-03 06:55:24|0
> 1544019616|2018-12-05 09:20:16|0
> 1544168454|2018-12-07 02:40:54|0
> 1544239551|2018-12-07 22:25:51|0
> 1544372440|2018-12-09 11:20:40|0
> 1544904031|2018-12-15 15:00:31|0
> 1545071707|2018-12-17 13:35:07|0
> 1545429933|2018-12-21 17:05:33|0
> 1545432303|2018-12-21 17:45:03|0
> 1546150235|2018-12-30 01:10:35|0
> 1546475415|2019-01-02 19:30:15|0
> 1546518003|2019-01-03 07:20:03|0
> 1547684108|2019-01-16 19:15:08|0
> 1547692525|2019-01-16 21:35:25|0
> 1547745917|2019-01-17 12:25:17|0
> 1547795720|2019-01-18 02:15:20|0
> 1547847003|2019-01-18 16:30:03|0
> 1547885706|2019-01-19 03:15:06|0
> 1547921726|2019-01-19 13:15:26|0
> 1548084634|2019-01-21 10:30:34|0
> 1548111631|2019-01-21 18:00:31|0
> 1548140733|2019-01-22 02:05:33|0
> 1548149429|2019-01-22 04:30:29|0
> 1548172814|2019-01-22 11:00:14|0
> 1548200418|2019-01-22 18:40:18|0
> 1548355828|2019-01-24 13:50:28|0
> 1548435918|2019-01-25 12:05:18|0
> 1548532233|2019-01-26 14:50:33|0
> 1548746432|2019-01-29 02:20:32|0
> 1548782434|2019-01-29 12:20:34|0
> 1548838528|2019-01-30 03:55:28|0
> 1548889502|2019-01-30 18:05:02|0
> 1549086926|2019-02-02 00:55:26|0
> 1549353629|2019-02-05 03:00:29|0
> 1549419305|2019-02-05 21:15:05|0
> 1549438213|2019-02-06 02:30:13|0
> 1549454715|2019-02-06 07:05:15|0
> 1549679405|2019-02-08 21:30:05|0
> 1549784417|2019-02-10 02:40:17|0
> 1549825526|2019-02-10 14:05:26|0
> 1549830909|2019-02-10 15:35:09|0
> 1549874404|2019-02-11 03:40:04|0
> 1550099133|2019-02-13 18:05:33|0
> 1550101539|2019-02-13 18:45:39|0
> 1550187328|2019-02-14 18:35:28|0
> 1550194210|2019-02-14 20:30:10|0
> 1550291412|2019-02-15 23:30:12|0
> 1550573420|2019-02-19 05:50:20|0
> 1550820921|2019-02-22 02:35:21|0
> 1550881824|2019-02-22 19:30:24|0
> 1551015637|2019-02-24 08:40:37|0
> 1552304140|2019-03-11 07:35:40|0
> 1552354241|2019-03-11 21:30:41|0
> 1552566905|2019-03-14 08:35:05|0
> 1552827608|2019-03-17 09:00:08|0
> 1552918802|2019-03-18 10:20:02|0
> 1554167132|2019-04-01 21:05:32|0
> 1554227428|2019-04-02 13:50:28|0
> 1554549615|2019-04-06 07:20:15|0
> 1554727516|2019-04-08 08:45:16|0
> 1554934221|2019-04-10 18:10:21|0
> 1560451800|2019-06-13 14:50:00|0
> 1560578137|2019-06-15 01:55:37|0
> 1560591346|2019-06-15 05:35:46|0
> 1560690940|2019-06-16 09:15:40|0
> 1560917091|2019-06-19 00:04:51|0
> 1560917146|2019-06-19 00:05:46|0
> 1561295409|2019-06-23 09:10:09|0
> 1561377604|2019-06-24 08:00:0

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[tim lambert]

Thanks John!

Unfortunately, I'm getting an error when executing the install:

python  wee_extension --install /home/pi/FTP/weewx-ip100-master.zip
  File "wee_extension", line 6
WEEWX_BINDIR=/home/weewx/bin
 ^
SyntaxError: invalid syntax


Any ideas?

On Wednesday, January 6, 2021 at 11:20:58 AM UTC-8 jo...@johnkline.com 
wrote:

> where can I exactly find the inclusion of the station volts
>
>
> Download this file:
> https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip
>
> Then:
>
>
> sudo wee_extension --install master.zip
>
>
>
> On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:
>
> 
>
> Hi John,
>
> After leaving the server run uninterrupted, all of the data being 
> displayed on weewx is ticking to the ip-100 console.   
>
> Apologies for my ignorance, where can I exactly find the inclusion of the 
> station volts you noted in your last comm (btw Thanks for addressing).
>
> On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com wrote:
>
>> > Once I sort this possible discrepancy, I'd like to pick your brain on 
>> adding the Station Volts.
>>
>> I added it at head.  Station volts will now show up as supplyVoltage.
>>
>> On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
>>
>> 
>>
>> The IP100 resets the day’s rain total at midnight (according to it’s 
>> clock).  It doesn’t really matter to the driver when that happens.  The 
>> driver is simply looking for a positive increment in day_rain_total.  On a 
>> negative increment (e.g., reset), the driver just saves the last value and 
>> reports 0.0 for rain.
>>
>> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
>>
>> 
>> Thanks for the guidance John!   I was anticipating to simply have a day 
>> with a clean run, starting at midnight.  I should have this info tomorrow.
>>
>> I assume the loop will recognize my local timezone to reset to zero at 
>> midnight, recognizing the db is being recorded on GMT?
>>
>> Once I sort this possible discrepancy, I'd like to pick your brain on 
>> adding the Station Volts.
>>
>> Regards,
>>
>> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com wrote:
>>
>>> You don’t to delete records.  There isn’t really much to the rain 
>>> calculation.  For all rain that occurred while WeeWX is up and running, the 
>>> day_rain_total will increment, the driver will calculate the delta and add 
>>> it to the loop record as ‘rain’.  For the discrepancy to occur, 0.09 inches 
>>> would have had to happen while WeeWX wasn’t running.
>>>
>>> Let’s try a day where WeeWX has been running, uninterrupted, since 
>>> midnight.
>>>
>>> On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
>>>
>>> 
>>>
>>> Thanks for the quick response John!
>>>
>>> I am running your version of the IP100 for weewx 4 - version 0.5
>>>
>>> I did restart the weewx today -- had some network issues, compliments of 
>>> Comcast.   However, I've witnessed discrepancies between the IP100 Console 
>>> and weewx for several days -- just finally had a chance to get some data 
>>> captures.   I may need to capture data again tomorrow (knowing it will be 
>>> raining buckets again).
>>>
>>> At this point in time:
>>>
>>>   
>>> IP100weewx
>>> Rainfall  
>>> 0.06   0.15
>>> Rain Rate  
>>> 0.00   0.00
>>>
>>> Can I truncate (delete all records) from the weewx.sdb (after backing up 
>>> of course) to start fresh, so that we have a solid baseline to evaluate?
>>>
>>> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com 
>>> wrote:
>>>
 Station volts is not in the default map.  It wouldn’t be hard to add.

 I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and 
 bumped the version to 0.5 in my fork).  I’m presuming you are running it.

 Although I’m not currently running the driver, I did run it for almost 
 two years and rain values ALWAYS agreed with my WeeWX instances running 
 the 
 CC3000 driver and talking to the same RainWise weather station.

 day_rain_total is used to calculate rain.  It is not, in itself saved 
 to the database.

 I have not downloaded your files.  You’ll have to tell me if the ip100 
 console does not agree with the console for today’s rain and, if not, what 
 two values you are seeing.  Please list them.

 If you do have a discrepancy for today’s rain, please state if you 
 restarted weewx today (or if it restarted on its own today).  That would 
 be 
 a way to lose rainfall.


 On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:

 

 I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the 
 IP-100 v0.5 extension.  It appears the IP-100 Console data does not match 
 the data presented via weewx (using the out-of-box index.html, which is 
 using the SeasonsSk

Re: [weewx-user] cant find start time

[gjr80]

...and then change back to hardware record generation.

Gary

On Thursday, 7 January 2021 at 05:45:59 UTC+10 tke...@gmail.com wrote:

> That's good, but you really should clear the logger memory. Otherwise, you 
> won't be able to enjoy a key feature of weewx + Vantage: the ability to 
> continue to log data, even if your computer crashes, your network goes 
> down, or you experience a power outage.
>
>
> On Wed, Jan 6, 2021 at 10:59 AM  wrote:
>
>> Seems to be working after I used the software records.
>>
>> Bill
>>
>>  
>>
>> *From:* weewx...@googlegroups.com  *On Behalf 
>> Of *Tom Keffer
>> *Sent:* Wednesday, January 6, 2021 11:36 AM
>> *To:* weewx-user 
>> *Subject:* Re: [weewx-user] cant find start time
>>
>>  
>>
>> The error "cannot find start time" happens when there is nothing in the 
>> database. Is this the first time you've used the database?
>>
>>  
>>
>> Normally, there is something in the database before a report 
>> is generated, but, I suspect, you have a corrupted logger memory. So, 
>> weewxd is unable to retrieve anything from it.
>>
>>  
>>
>> To fix: 
>> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory
>>
>>  
>>
>> -tk
>>
>>  
>>
>>  
>>
>> On Wed, Jan 6, 2021 at 9:44 AM billandcorena ahrens <
>> ord...@billandcorena.com> wrote:
>>
>> $ sudo tail -f /var/log/syslog
>>
>> Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.engine: Using binding 
>> 'wx_binding' to database 'weewx.sdb'
>>
>> Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.manager: Starting 
>> backfill of daily summaries
>>
>> Jan  6 10:37:07 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Getting all archive packets
>>
>> Jan  6 10:37:08 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Gentle wake up of console successful
>>
>> Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Retrieving 263 page(s); starting index= 0
>>
>> Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Empty record page 0; index 0
>>
>> Jan  6 10:37:09 raspberrypi weewx[9872] INFO weewx.engine: Starting main 
>> packet loop.
>>
>> Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Gentle wake up of console successful
>>
>> Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Requesting 200 LOOP packets.
>>
>> Jan  6 10:37:11 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Gentle wake up of console successful
>>
>> Jan  6 10:38:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Getting all archive packets
>>
>> Jan  6 10:38:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Retry #0 failed
>>
>> Jan  6 10:38:26 raspberrypi weewx[9872] ERROR weewx.drivers.vantage: 
>> ip-read error: timed out
>>
>> Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Retry #1 failed
>>
>> Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Gentle wake up of console successful
>>
>> Jan  6 10:38:27 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Retrieving 263 page(s); starting index= 0
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Empty record page 0; index 0
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
>> reports for latest time in the database.
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
>> Requesting 200 LOOP packets.
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
>> report 'SeasonsReport'
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Found 
>> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
>> 'SeasonsReport'
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.cheetahgenerator: 
>> Using search list ['weewx.cheetahgenerator.Almanac', 
>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>> 'weewx.cheetahgenerator.Extras']
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily 
>> summary version is 3.0
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
>> Skipping template NOAA/NOAA-%Y-%m.txt.tmpl: cannot find start time
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
>> Skipping template NOAA/NOAA-%Y.txt.tmpl: cannot find start time
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
>> Skipping template index.html.tmpl: cannot find start time
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
>> Skipping template statistics.html.tmpl: cannot find start time
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
>> Skipping template telemetry.html.tmpl: cannot find start time
>>
>> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
>> Skipping template tabular.html.tmpl: cannot find start time
>>
>> Ja

Re: [weewx-user] cant find start time

[Tom Keffer]

That's good, but you really should clear the logger memory. Otherwise, you
won't be able to enjoy a key feature of weewx + Vantage: the ability to
continue to log data, even if your computer crashes, your network goes
down, or you experience a power outage.


On Wed, Jan 6, 2021 at 10:59 AM  wrote:

> Seems to be working after I used the software records.
>
> Bill
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Tom Keffer
> *Sent:* Wednesday, January 6, 2021 11:36 AM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] cant find start time
>
>
>
> The error "cannot find start time" happens when there is nothing in the
> database. Is this the first time you've used the database?
>
>
>
> Normally, there is something in the database before a report is generated,
> but, I suspect, you have a corrupted logger memory. So, weewxd is unable to
> retrieve anything from it.
>
>
>
> To fix:
> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory
>
>
>
> -tk
>
>
>
>
>
> On Wed, Jan 6, 2021 at 9:44 AM billandcorena ahrens <
> ord...@billandcorena.com> wrote:
>
> $ sudo tail -f /var/log/syslog
>
> Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.engine: Using binding
> 'wx_binding' to database 'weewx.sdb'
>
> Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.manager: Starting
> backfill of daily summaries
>
> Jan  6 10:37:07 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Getting all archive packets
>
> Jan  6 10:37:08 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Retrieving 263 page(s); starting index= 0
>
> Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty
> record page 0; index 0
>
> Jan  6 10:37:09 raspberrypi weewx[9872] INFO weewx.engine: Starting main
> packet loop.
>
> Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Requesting 200 LOOP packets.
>
> Jan  6 10:37:11 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jan  6 10:38:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Getting all archive packets
>
> Jan  6 10:38:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry
> #0 failed
>
> Jan  6 10:38:26 raspberrypi weewx[9872] ERROR weewx.drivers.vantage:
> ip-read error: timed out
>
> Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry
> #1 failed
>
> Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jan  6 10:38:27 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Retrieving 263 page(s); starting index= 0
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty
> record page 0; index 0
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running
> reports for latest time in the database.
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Requesting 200 LOOP packets.
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running
> report 'SeasonsReport'
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Found
> configuration file /etc/weewx/skins/Seasons/skin.conf for report
> 'SeasonsReport'
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.cheetahgenerator:
> Using search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
> 'weewx.cheetahgenerator.Extras']
>
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary
> version is 3.0
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template NOAA/NOAA-%Y-%m.txt.tmpl: cannot find start time
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template NOAA/NOAA-%Y.txt.tmpl: cannot find start time
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template index.html.tmpl: cannot find start time
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template statistics.html.tmpl: cannot find start time
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template telemetry.html.tmpl: cannot find start time
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template tabular.html.tmpl: cannot find start time
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template celestial.html.tmpl: cannot find start time
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template rss.xml.tmpl: cannot find start time
>
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:

Re: [weewx-user] Re: Wrong XTypes output after upgrading WeeWX 4.1.1 to 4.3.0

[Arend]

Found a solution to the problem, everything is back to normal now.

Added these lines to the end of  *lowest_temperature.py*:

# Tell the unit system what group our new observation type, 
'lowTemperature', belongs to:
weewx.units.obs_group_dict['lowTemperature'] = "group_temperature" 

Somehow this wasn't required in 4.1.1. Maybe more people will run into this 
issue when upgrading to 4.3.0.

Op woensdag 6 januari 2021 om 19:51:20 UTC+1 schreef Arend:

> The get_scalar function is still returning the correct values:
> [image: Current conditions.png]
> I have put Outside Temperature, Temperature1 and the calculated Lowest 
> Temperature in one chart. I really don't understand why the get_series 
> calculation is now outputting such high values. Any suggestions are welcome.
>
> [image: daytempdew (1).png]
>
> Op woensdag 6 januari 2021 om 19:24:22 UTC+1 schreef tke...@gmail.com:
>
>> I would guess that the problem is that you are always returning 
>> lowestTemperature in Fahrenheit, but your data records are in Celsius.
>>
>> That part of XTypes has not changed. I don't know why it worked before. 
>> Perhaps units were in Fahrenheit before?
>>
>> -tk
>>
>> On Wed, Jan 6, 2021 at 10:16 AM Arend  wrote:
>>
>>> Hello Tom,
>>>
>>> I get strange output as can be seen in the chart below. It apperas the 
>>> series isn't calculated/retrieved as it did before the upgrade. I hope this 
>>> helps to understand.
>>>
>>> [image: daytempdew.png]
>>>
>>> Regards, Arend
>>> Op woensdag 6 januari 2021 om 19:12:47 UTC+1 schreef tke...@gmail.com:
>>>
 It would help if we knew what the problem was. "No longer works" 
 doesn't tell us much.

 On Wed, Jan 6, 2021 at 10:00 AM Arend  wrote:

> In addition to the previous: the get_scalar function still seems to be 
> working but the get_series function no longer works.
>
> Op woensdag 6 januari 2021 om 18:33:12 UTC+1 schreef Arend:
>
>> Everything worked fine until I did the upgrade.
>>
>> I guess something has changed in the way XTypes are handled?
>>
>> *This is the code I use in extensions.py:*
>>
>> #
>> #Copyright (c) 2009-2015 Tom Keffer 
>> #
>> #See the file LICENSE.txt for your full rights.
>> #
>>
>> """User extensions module
>>
>> This module is imported from the main executable, so anything put 
>> here will be
>> executed before anything else happens. This makes it a good place to 
>> put user
>> extensions.
>> """
>>
>> import locale
>> # This will use the locale specified by the environment variable 
>> 'LANG'
>> # Other options are possible. See:
>> # http://docs.python.org/2/library/locale.html#locale.setlocale
>> locale.setlocale(locale.LC_ALL, '')
>>
>> import user.lowest_temperature
>> import weewx.xtypes
>>
>>
>> weewx.xtypes.xtypes.append(user.lowest_temperature.LowestTemperature())
>>
>>
>> *This is the code in lowest_temperature.py:*
>>
>> import weewx.units
>> import weewx.xtypes
>> from weewx.units import ValueTuple
>>
>> class LowestTemperature(weewx.xtypes.XType):
>>
>>   def get_scalar(self, obs_type, record, dbmanager):
>> """Determine which sensor has lowest temperature."""
>> if obs_type != 'lowTemperature':
>>   raise weewx.UnknownType
>> try:
>>   record_us = weewx.units.to_US(record)
>>   if record_us['outTemp'] == None or record_us['extraTemp1'] == 
>> None:
>>   # if record_us['outTemp'] < 100 or record_us['extraTemp1'] < 
>> 100:
>> raise TypeError("Temperature(s) equal to None")
>>   if record_us['outTemp'] <= record_us['extraTemp1']:
>> lowTemperature = record_us['outTemp']
>>   else:
>> lowTemperature = record_us['extraTemp1']
>>   return ValueTuple(lowTemperature, "degree_F", 
>> "group_temperature")
>> except KeyError:
>>   # Don't have everything we need. Raise an exception.
>>   raise weewx.CannotCalculate(obs_type)
>>   
>>   def get_series(self, obs_type, timespan, db_manager, 
>> aggregate_type=None, aggregate_interval=None):
>> if obs_type != 'lowTemperature':
>>   raise weewx.UnknownType
>> start_vec = list()
>> stop_vec = list()
>> data_vec = list()
>> if aggregate_type:
>>   raise weewx.UnknownAggregation(aggregate_type)
>> for record in db_manager.genSql("SELECT `dateTime`, `interval`, 
>> `usUnits`, `outTemp`, `extraTemp1` FROM `archive` WHERE `dateTime` > 
>> %(start)s AND `dateTime` <= %(stop)s;" % {'start': timespan[0], 'stop': 
>> timespan[1]}):
>>   if (record[2] != 1):
>> raise weewx.CannotCalculate("units are not US")
>>   if record[3] == None or record[4] == None:
>>   # if record[3] < 100 or record[4] < 100:
>> raise 

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[John Kline]

> where can I exactly find the inclusion of the station volts


Download this file:
https://github.com/chaunceygardiner/weewx-ip100/archive/master.zip

Then:

sudo wee_extension --install master.zip


> On Jan 6, 2021, at 8:54 AM, tim lambert  wrote:
> 
> 
> Hi John,
> 
> After leaving the server run uninterrupted, all of the data being displayed 
> on weewx is ticking to the ip-100 console.   
> 
> Apologies for my ignorance, where can I exactly find the inclusion of the 
> station volts you noted in your last comm (btw Thanks for addressing).
> 
>> On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com wrote:
>> > Once I sort this possible discrepancy, I'd like to pick your brain on 
>> > adding the Station Volts.
>> 
>> I added it at head.  Station volts will now show up as supplyVoltage.
>> 
 On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
 
>>> 
>> 
>>> The IP100 resets the day’s rain total at midnight (according to it’s 
>>> clock).  It doesn’t really matter to the driver when that happens.  The 
>>> driver is simply looking for a positive increment in day_rain_total.  On a 
>>> negative increment (e.g., reset), the driver just saves the last value and 
>>> reports 0.0 for rain.
>>> 
> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
> 
 
 Thanks for the guidance John!   I was anticipating to simply have a day 
 with a clean run, starting at midnight.  I should have this info tomorrow.
 
 I assume the loop will recognize my local timezone to reset to zero at 
 midnight, recognizing the db is being recorded on GMT?
 
 Once I sort this possible discrepancy, I'd like to pick your brain on 
 adding the Station Volts.
 
 Regards,
 
> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com wrote:
> You don’t to delete records.  There isn’t really much to the rain 
> calculation.  For all rain that occurred while WeeWX is up and running, 
> the day_rain_total will increment, the driver will calculate the delta 
> and add it to the loop record as ‘rain’.  For the discrepancy to occur, 
> 0.09 inches would have had to happen while WeeWX wasn’t running.
> 
> Let’s try a day where WeeWX has been running, uninterrupted, since 
> midnight.
> 
>>> On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
>>> 
>> 
> 
>> Thanks for the quick response John!
>> 
>> I am running your version of the IP100 for weewx 4 - version 0.5
>> 
>> I did restart the weewx today -- had some network issues, compliments of 
>> Comcast.   However, I've witnessed discrepancies between the IP100 
>> Console and weewx for several days -- just finally had a chance to get 
>> some data captures.   I may need to capture data again tomorrow (knowing 
>> it will be raining buckets again).
>> 
>> At this point in time:
>> 
>>   IP100  
>>   weewx
>> Rainfall  0.06   
>> 0.15
>> Rain Rate  0.00  
>>  0.00
>> 
>> Can I truncate (delete all records) from the weewx.sdb (after backing up 
>> of course) to start fresh, so that we have a solid baseline to evaluate?
>> 
>>> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com 
>>> wrote:
>>> Station volts is not in the default map.  It wouldn’t be hard to add.
>>> 
>>> I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and 
>>> bumped the version to 0.5 in my fork).  I’m presuming you are running 
>>> it.
>>> 
>>> Although I’m not currently running the driver, I did run it for almost 
>>> two years and rain values ALWAYS agreed with my WeeWX instances running 
>>> the CC3000 driver and talking to the same RainWise weather station.
>>> 
>>> day_rain_total is used to calculate rain.  It is not, in itself saved 
>>> to the database.
>>> 
>>> I have not downloaded your files.  You’ll have to tell me if the ip100 
>>> console does not agree with the console for today’s rain and, if not, 
>>> what two values you are seeing.  Please list them.
>>> 
>>> If you do have a discrepancy for today’s rain, please state if you 
>>> restarted weewx today (or if it restarted on its own today).  That 
>>> would be a way to lose rainfall.
>>> 
>>> 
> On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:
> 
 
>>> 
 I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the 
 IP-100 v0.5 extension.  It appears the IP-100 Console data does not 
 match the data presented via weewx (using the out-of-box index.html, 
 which is using the SeasonsSkin) -- particularly, the Rain and Rain 
 Rate.   I've shared screen shots of both the IP-100 Co

Re: [weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Michael Sanphillipo]

Tom, here are my results. Please let me know what to do next. Thanks!

/var/lib/weewx $ sqlite3 /var/lib/weewx/weewx.sdb
SQLite version 3.27.2 2019-02-25 16:06:06
Enter ".help" for usage hints.
sqlite> select dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
interval from archive where interval<=0;
1527646827|2018-05-29 22:20:27|0
1528167350|2018-06-04 22:55:50|0
1528498208|2018-06-08 18:50:08|0
1528514117|2018-06-08 23:15:17|0
1529163904|2018-06-16 11:45:04|0
1529250650|2018-06-17 11:50:50|0
1529969403|2018-06-25 19:30:03|0
1530019815|2018-06-26 09:30:15|0
1530045606|2018-06-26 16:40:06|0
1531475142|2018-07-13 05:45:42|0
1531637727|2018-07-15 02:55:27|0
1532338834|2018-07-23 05:40:34|0
1532424936|2018-07-24 05:35:36|0
1532451003|2018-07-24 12:50:03|0
1532459736|2018-07-24 15:15:36|0
1532470836|2018-07-24 18:20:36|0
1532548520|2018-07-25 15:55:20|0
1536048937|2018-09-04 04:15:37|0
1536216049|2018-09-06 02:40:49|0
1536282003|2018-09-06 21:00:03|0
1536954915|2018-09-14 15:55:15|0
1537301423|2018-09-18 16:10:23|0
1537933226|2018-09-25 23:40:26|0
153857|2018-10-03 09:10:22|0
1538660412|2018-10-04 09:40:12|0
1538750748|2018-10-05 10:45:48|0
1538870425|2018-10-06 20:00:25|0
1538878546|2018-10-06 22:15:46|0
1538967014|2018-10-07 22:50:14|0
1539012006|2018-10-08 11:20:06|0
1539111014|2018-10-09 14:50:14|0
1539128421|2018-10-09 19:40:21|0
1539129900|2018-10-09 20:05:00|0
1539179426|2018-10-10 09:50:26|0
1539360622|2018-10-12 12:10:22|0
1539397529|2018-10-12 22:25:29|0
1539448534|2018-10-13 12:35:34|0
1539869437|2018-10-18 09:30:37|0
1540113330|2018-10-21 05:15:30|0
1540530332|2018-10-26 01:05:32|0
1541252127|2018-11-03 09:35:27|0
1541906710|2018-11-10 22:25:10|0
1542099614|2018-11-13 04:00:14|0
1543282805|2018-11-26 20:40:05|0
1543788916|2018-12-02 17:15:16|0
1543792503|2018-12-02 18:15:03|0
1543828523|2018-12-03 04:15:23|0
1543838124|2018-12-03 06:55:24|0
1544019616|2018-12-05 09:20:16|0
1544168454|2018-12-07 02:40:54|0
1544239551|2018-12-07 22:25:51|0
1544372440|2018-12-09 11:20:40|0
1544904031|2018-12-15 15:00:31|0
1545071707|2018-12-17 13:35:07|0
1545429933|2018-12-21 17:05:33|0
1545432303|2018-12-21 17:45:03|0
1546150235|2018-12-30 01:10:35|0
1546475415|2019-01-02 19:30:15|0
1546518003|2019-01-03 07:20:03|0
1547684108|2019-01-16 19:15:08|0
1547692525|2019-01-16 21:35:25|0
1547745917|2019-01-17 12:25:17|0
1547795720|2019-01-18 02:15:20|0
1547847003|2019-01-18 16:30:03|0
1547885706|2019-01-19 03:15:06|0
1547921726|2019-01-19 13:15:26|0
1548084634|2019-01-21 10:30:34|0
1548111631|2019-01-21 18:00:31|0
1548140733|2019-01-22 02:05:33|0
1548149429|2019-01-22 04:30:29|0
1548172814|2019-01-22 11:00:14|0
1548200418|2019-01-22 18:40:18|0
1548355828|2019-01-24 13:50:28|0
1548435918|2019-01-25 12:05:18|0
1548532233|2019-01-26 14:50:33|0
1548746432|2019-01-29 02:20:32|0
1548782434|2019-01-29 12:20:34|0
1548838528|2019-01-30 03:55:28|0
1548889502|2019-01-30 18:05:02|0
1549086926|2019-02-02 00:55:26|0
1549353629|2019-02-05 03:00:29|0
1549419305|2019-02-05 21:15:05|0
1549438213|2019-02-06 02:30:13|0
1549454715|2019-02-06 07:05:15|0
1549679405|2019-02-08 21:30:05|0
1549784417|2019-02-10 02:40:17|0
1549825526|2019-02-10 14:05:26|0
1549830909|2019-02-10 15:35:09|0
1549874404|2019-02-11 03:40:04|0
1550099133|2019-02-13 18:05:33|0
1550101539|2019-02-13 18:45:39|0
1550187328|2019-02-14 18:35:28|0
1550194210|2019-02-14 20:30:10|0
1550291412|2019-02-15 23:30:12|0
1550573420|2019-02-19 05:50:20|0
1550820921|2019-02-22 02:35:21|0
1550881824|2019-02-22 19:30:24|0
1551015637|2019-02-24 08:40:37|0
1552304140|2019-03-11 07:35:40|0
1552354241|2019-03-11 21:30:41|0
1552566905|2019-03-14 08:35:05|0
1552827608|2019-03-17 09:00:08|0
1552918802|2019-03-18 10:20:02|0
1554167132|2019-04-01 21:05:32|0
1554227428|2019-04-02 13:50:28|0
1554549615|2019-04-06 07:20:15|0
1554727516|2019-04-08 08:45:16|0
1554934221|2019-04-10 18:10:21|0
1560451800|2019-06-13 14:50:00|0
1560578137|2019-06-15 01:55:37|0
1560591346|2019-06-15 05:35:46|0
1560690940|2019-06-16 09:15:40|0
1560917091|2019-06-19 00:04:51|0
1560917146|2019-06-19 00:05:46|0
1561295409|2019-06-23 09:10:09|0
1561377604|2019-06-24 08:00:04|0
1561721120|2019-06-28 07:25:20|0
1561729203|2019-06-28 09:40:03|0
1561848012|2019-06-29 18:40:12|0
1561851305|2019-06-29 19:35:05|0
1563068443|2019-07-13 21:40:43|0
1563411933|2019-07-17 21:05:33|0
1591577408|2020-06-07 20:50:08|0
1591585234|2020-06-07 23:00:34|0


On Wednesday, January 6, 2021 at 1:37:35 PM UTC-5 tke...@gmail.com wrote:

> Do it from a terminal.
>
> For now, just do the very first select statement so we can see where we 
> stand:
>
> *sqlite3 /var/weewx/weedwx.sdb*
> sqlite> *select dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
> interval from archive where interval<=0;*
> sqlite> *.quit*
>
>
>
> On Wed, Jan 6, 2021 at 10:33 AM Michael Sanphillipo  
> wrote:
>
>> Tom, do I do this in terminal and do I enter it exactly as you have it 
>> listed above?
>>
>> On Wed, Jan 6, 2021 at 1:19 PM Tom Keffer  wrote:
>>
>>> The softwar

RE: [weewx-user] cant find start time

[orders]

Seems to be working after I used the software records.

Bill

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Wednesday, January 6, 2021 11:36 AM
To: weewx-user 
Subject: Re: [weewx-user] cant find start time

 

The error "cannot find start time" happens when there is nothing in the 
database. Is this the first time you've used the database?

 

Normally, there is something in the database before a report is generated, but, 
I suspect, you have a corrupted logger memory. So, weewxd is unable to retrieve 
anything from it.

 

To fix: 
https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory

 

-tk

 

 

On Wed, Jan 6, 2021 at 9:44 AM billandcorena ahrens mailto:ord...@billandcorena.com> > wrote:

$ sudo tail -f /var/log/syslog

Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'

Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.manager: Starting backfill 
of daily summaries

Jan  6 10:37:07 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Getting 
all archive packets

Jan  6 10:37:08 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retrieving 
263 page(s); starting index= 0

Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty 
record page 0; index 0

Jan  6 10:37:09 raspberrypi weewx[9872] INFO weewx.engine: Starting main packet 
loop.

Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.

Jan  6 10:37:11 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:38:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Getting 
all archive packets

Jan  6 10:38:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry #0 
failed

Jan  6 10:38:26 raspberrypi weewx[9872] ERROR weewx.drivers.vantage: ip-read 
error: timed out

Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry #1 
failed

Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:38:27 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retrieving 
263 page(s); starting index= 0

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty 
record page 0; index 0

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
reports for latest time in the database.

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary 
version is 3.0

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template NOAA/NOAA-%Y-%m.txt.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template NOAA/NOAA-%Y.txt.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template index.html.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template statistics.html.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template telemetry.html.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template tabular.html.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template celestial.html.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Skipping 
template rss.xml.tmpl: cannot find start time

Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: Generated 
0 files for report SeasonsReport in 0.02 seconds

Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary 
version is 3.0

Jan  6 10:38:29 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful

Jan  6 10:38:30 raspberrypi weewx[9872] INFO weewx.imagegenerator: Generated 30 
images for report SeasonsReport in 2.05 seconds

Jan  6 10:38:30 raspberrypi weewx[9872] INFO weewx.reportengine: Copied 5 files 
to /var/w

Re: [weewx-user] Re: Wrong XTypes output after upgrading WeeWX 4.1.1 to 4.3.0

[Arend]

The get_scalar function is still returning the correct values:
[image: Current conditions.png]
I have put Outside Temperature, Temperature1 and the calculated Lowest 
Temperature in one chart. I really don't understand why the get_series 
calculation is now outputting such high values. Any suggestions are welcome.

[image: daytempdew (1).png]

Op woensdag 6 januari 2021 om 19:24:22 UTC+1 schreef tke...@gmail.com:

> I would guess that the problem is that you are always returning 
> lowestTemperature in Fahrenheit, but your data records are in Celsius.
>
> That part of XTypes has not changed. I don't know why it worked before. 
> Perhaps units were in Fahrenheit before?
>
> -tk
>
> On Wed, Jan 6, 2021 at 10:16 AM Arend  wrote:
>
>> Hello Tom,
>>
>> I get strange output as can be seen in the chart below. It apperas the 
>> series isn't calculated/retrieved as it did before the upgrade. I hope this 
>> helps to understand.
>>
>> [image: daytempdew.png]
>>
>> Regards, Arend
>> Op woensdag 6 januari 2021 om 19:12:47 UTC+1 schreef tke...@gmail.com:
>>
>>> It would help if we knew what the problem was. "No longer works" doesn't 
>>> tell us much.
>>>
>>> On Wed, Jan 6, 2021 at 10:00 AM Arend  wrote:
>>>
 In addition to the previous: the get_scalar function still seems to be 
 working but the get_series function no longer works.

 Op woensdag 6 januari 2021 om 18:33:12 UTC+1 schreef Arend:

> Everything worked fine until I did the upgrade.
>
> I guess something has changed in the way XTypes are handled?
>
> *This is the code I use in extensions.py:*
>
> #
> #Copyright (c) 2009-2015 Tom Keffer 
> #
> #See the file LICENSE.txt for your full rights.
> #
>
> """User extensions module
>
> This module is imported from the main executable, so anything put here 
> will be
> executed before anything else happens. This makes it a good place to 
> put user
> extensions.
> """
>
> import locale
> # This will use the locale specified by the environment variable 'LANG'
> # Other options are possible. See:
> # http://docs.python.org/2/library/locale.html#locale.setlocale
> locale.setlocale(locale.LC_ALL, '')
>
> import user.lowest_temperature
> import weewx.xtypes
>
> weewx.xtypes.xtypes.append(user.lowest_temperature.LowestTemperature())
>
>
> *This is the code in lowest_temperature.py:*
>
> import weewx.units
> import weewx.xtypes
> from weewx.units import ValueTuple
>
> class LowestTemperature(weewx.xtypes.XType):
>
>   def get_scalar(self, obs_type, record, dbmanager):
> """Determine which sensor has lowest temperature."""
> if obs_type != 'lowTemperature':
>   raise weewx.UnknownType
> try:
>   record_us = weewx.units.to_US(record)
>   if record_us['outTemp'] == None or record_us['extraTemp1'] == 
> None:
>   # if record_us['outTemp'] < 100 or record_us['extraTemp1'] < 100:
> raise TypeError("Temperature(s) equal to None")
>   if record_us['outTemp'] <= record_us['extraTemp1']:
> lowTemperature = record_us['outTemp']
>   else:
> lowTemperature = record_us['extraTemp1']
>   return ValueTuple(lowTemperature, "degree_F", 
> "group_temperature")
> except KeyError:
>   # Don't have everything we need. Raise an exception.
>   raise weewx.CannotCalculate(obs_type)
>   
>   def get_series(self, obs_type, timespan, db_manager, 
> aggregate_type=None, aggregate_interval=None):
> if obs_type != 'lowTemperature':
>   raise weewx.UnknownType
> start_vec = list()
> stop_vec = list()
> data_vec = list()
> if aggregate_type:
>   raise weewx.UnknownAggregation(aggregate_type)
> for record in db_manager.genSql("SELECT `dateTime`, `interval`, 
> `usUnits`, `outTemp`, `extraTemp1` FROM `archive` WHERE `dateTime` > 
> %(start)s AND `dateTime` <= %(stop)s;" % {'start': timespan[0], 'stop': 
> timespan[1]}):
>   if (record[2] != 1):
> raise weewx.CannotCalculate("units are not US")
>   if record[3] == None or record[4] == None:
>   # if record[3] < 100 or record[4] < 100:
> raise TypeError("Temperature(s) equal to None") 
>   start_vec.append(record[0] - record[1] * 60)
>   stop_vec.append(record[0])
>   if record[3] <= record[4]:
> data_vec.append(record[3])
>   else:
> data_vec.append(record[4])
> return (ValueTuple(start_vec, 'unix_epoch', 'group_time'), 
> ValueTuple(stop_vec, 'unix_epoch', 'group_time'), ValueTuple(data_vec, 
> "degree_F", "group_temperature"))
>
> Do I need to rewrite all code?
>
> -- 
 You received this message because you are subscribed to the Google 
 Grou

Re: [weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Michael Sanphillipo]

Tom, my weewx.sdb is in /var/lib/weewx/. 

When I run squlite3 I get this.

pi@raspberrypi:/var/lib/weewx $ sqlite3 /var/lib/weewx/weedwx.sdb
SQLite version 3.27.2 2019-02-25 16:06:06
Enter ".help" for usage hints.
sqlite> select dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
interval from archive where interval<=0;
Error: no such table: archive
sqlite> 


On Wednesday, January 6, 2021 at 1:37:35 PM UTC-5 tke...@gmail.com wrote:

> Do it from a terminal.
>
> For now, just do the very first select statement so we can see where we 
> stand:
>
> *sqlite3 /var/weewx/weedwx.sdb*
> sqlite> *select dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
> interval from archive where interval<=0;*
> sqlite> *.quit*
>
>
>
> On Wed, Jan 6, 2021 at 10:33 AM Michael Sanphillipo  
> wrote:
>
>> Tom, do I do this in terminal and do I enter it exactly as you have it 
>> listed above?
>>
>> On Wed, Jan 6, 2021 at 1:19 PM Tom Keffer  wrote:
>>
>>> The software is a little more hard-nosed about demanding valid values 
>>> for the field 'interval'. Somewhere in your database, you have a value of 
>>> zero for the archive interval length. To find them:
>>>
>>> *sqlite3 /var/weewx/weedwx.sdb*
>>> sqlite> *select dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
>>> interval from archive where interval<=0;*
>>>
>>> To delete them:
>>>
>>> sqlite> *delete from archive where interval<=0;*
>>>
>>> Alternatively, if you're confident you know what the correct value 
>>> should be (let's say it's 5 minutes);
>>>
>>> sqlite> *update archive set interval=5 where interval<=0;*
>>>
>>> -tk
>>>
>>> On Wed, Jan 6, 2021 at 9:49 AM Michael Sanphillipo  
>>> wrote:
>>>
 I upgraded today and received the following errors in my Syslog. Any 
 help would be greatly appreciated.

 Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Initializing 
 weewx version 4.3.0
 Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Using Python 
 3.7.3 (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
 Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Platform 
 Linux-5.4.79-v7+-armv7l-with-debian-10.7
 Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Locale is 
 'en_US.UTF-8'
 Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: PID file is 
 /var/run/weewx.pid
 Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Debug is 0
 Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: Loading 
 station type AcuRite (weewx.drivers.acurite)
 Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.drivers.acurite: 
 driver version is 0.4
 Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: StdConvert 
 target unit is 0x1
 Jan  6 12:44:46 raspberrypi weewx[1051]: Starting weewx weather system: 
 weewx.
 Jan  6 12:44:46 raspberrypi systemd[1]: Started LSB: weewx weather 
 system.
 Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: Daily 
 summaries at V2.0. Patching to V3.0
 Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: 
 recalculate_weights: Using database 'weewx.sdb'
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: Caught 
 unrecoverable exception:
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
 Non-positive value for record field 'interval': 0
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
 Traceback (most recent call last):
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
 File "/usr/share/weewx/weewxd", line 148, in main
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
   engine = weewx.engine.StdEngine(config_dict)
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
 File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
   self.loadServices(config_dict)
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
 File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
   obj = weeutil.weeutil.get_object(svc)(self, config_dict)
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
 File "/usr/share/weewx/weewx/wxservices.py", line 38, in __init__
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
   self.db_manager = 
 engine.db_binder.get_manager(data_binding=data_binding, 
 initialize=True)
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
 File "/usr/share/weewx/weewx/manager.py", line 534, in get_manager
 Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
   self.manager_cache[data

Re: [weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Tom Keffer]

Do it from a terminal.

For now, just do the very first select statement so we can see where we
stand:

*sqlite3 /var/weewx/weedwx.sdb*
sqlite> *select dateTime, datetime(dateTime, 'unixepoch', 'localtime'),
interval from archive where interval<=0;*
sqlite> *.quit*



On Wed, Jan 6, 2021 at 10:33 AM Michael Sanphillipo 
wrote:

> Tom, do I do this in terminal and do I enter it exactly as you have it
> listed above?
>
> On Wed, Jan 6, 2021 at 1:19 PM Tom Keffer  wrote:
>
>> The software is a little more hard-nosed about demanding valid values for
>> the field 'interval'. Somewhere in your database, you have a value of zero
>> for the archive interval length. To find them:
>>
>> *sqlite3 /var/weewx/weedwx.sdb*
>> sqlite> *select dateTime, datetime(dateTime, 'unixepoch', 'localtime'),
>> interval from archive where interval<=0;*
>>
>> To delete them:
>>
>> sqlite> *delete from archive where interval<=0;*
>>
>> Alternatively, if you're confident you know what the correct value should
>> be (let's say it's 5 minutes);
>>
>> sqlite> *update archive set interval=5 where interval<=0;*
>>
>> -tk
>>
>> On Wed, Jan 6, 2021 at 9:49 AM Michael Sanphillipo 
>> wrote:
>>
>>> I upgraded today and received the following errors in my Syslog. Any
>>> help would be greatly appreciated.
>>>
>>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Initializing
>>> weewx version 4.3.0
>>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Using Python
>>> 3.7.3 (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
>>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Platform
>>> Linux-5.4.79-v7+-armv7l-with-debian-10.7
>>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Locale is
>>> 'en_US.UTF-8'
>>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: PID file is
>>> /var/run/weewx.pid
>>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Using
>>> configuration file /etc/weewx/weewx.conf
>>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Debug is 0
>>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: Loading
>>> station type AcuRite (weewx.drivers.acurite)
>>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.drivers.acurite:
>>> driver version is 0.4
>>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: StdConvert
>>> target unit is 0x1
>>> Jan  6 12:44:46 raspberrypi weewx[1051]: Starting weewx weather system:
>>> weewx.
>>> Jan  6 12:44:46 raspberrypi systemd[1]: Started LSB: weewx weather
>>> system.
>>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: Daily
>>> summaries at V2.0. Patching to V3.0
>>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager:
>>> recalculate_weights: Using database 'weewx.sdb'
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: Caught
>>> unrecoverable exception:
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> Non-positive value for record field 'interval': 0
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> Traceback (most recent call last):
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> File "/usr/share/weewx/weewxd", line 148, in main
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> engine = weewx.engine.StdEngine(config_dict)
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> self.loadServices(config_dict)
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> File "/usr/share/weewx/weewx/wxservices.py", line 38, in __init__
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> self.db_manager = engine.db_binder.get_manager(data_binding=data_binding,
>>> initialize=True)
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> File "/usr/share/weewx/weewx/manager.py", line 534, in get_manager
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> self.manager_cache[data_binding] = open_manager(manager_dict, initialize)
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> File "/usr/share/weewx/weewx/manager.py", line 684, in open_manager
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> manager_dict['schema'])
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> File "/usr/share/weewx/weewx/manager.py", line 164, in open_with_create
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>>> dbmanager = cls(connection, table_name=table_name, schema=schema)
>>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL

Re: [weewx-user] cant find start time

[Tom Keffer]

The error "cannot find start time" happens when there is nothing in the
database. Is this the first time you've used the database?

Normally, there is something in the database before a report is generated,
but, I suspect, you have a corrupted logger memory. So, weewxd is unable to
retrieve anything from it.

To fix:
https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory

-tk


On Wed, Jan 6, 2021 at 9:44 AM billandcorena ahrens <
ord...@billandcorena.com> wrote:

> $ sudo tail -f /var/log/syslog
> Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.engine: Using binding
> 'wx_binding' to database 'weewx.sdb'
> Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.manager: Starting
> backfill of daily summaries
> Jan  6 10:37:07 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Getting all archive packets
> Jan  6 10:37:08 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
> Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Retrieving 263 page(s); starting index= 0
> Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty
> record page 0; index 0
> Jan  6 10:37:09 raspberrypi weewx[9872] INFO weewx.engine: Starting main
> packet loop.
> Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
> Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Requesting 200 LOOP packets.
> Jan  6 10:37:11 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
> Jan  6 10:38:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Getting all archive packets
> Jan  6 10:38:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry
> #0 failed
> Jan  6 10:38:26 raspberrypi weewx[9872] ERROR weewx.drivers.vantage:
> ip-read error: timed out
> Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry
> #1 failed
> Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
> Jan  6 10:38:27 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Retrieving 263 page(s); starting index= 0
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty
> record page 0; index 0
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running
> reports for latest time in the database.
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Requesting 200 LOOP packets.
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running
> report 'SeasonsReport'
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Found
> configuration file /etc/weewx/skins/Seasons/skin.conf for report
> 'SeasonsReport'
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.cheetahgenerator:
> Using search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
> 'weewx.cheetahgenerator.Extras']
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary
> version is 3.0
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template NOAA/NOAA-%Y-%m.txt.tmpl: cannot find start time
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template NOAA/NOAA-%Y.txt.tmpl: cannot find start time
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template index.html.tmpl: cannot find start time
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template statistics.html.tmpl: cannot find start time
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template telemetry.html.tmpl: cannot find start time
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template tabular.html.tmpl: cannot find start time
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template celestial.html.tmpl: cannot find start time
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Skipping template rss.xml.tmpl: cannot find start time
> Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator:
> Generated 0 files for report SeasonsReport in 0.02 seconds
> Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary
> version is 3.0
> Jan  6 10:38:29 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
> Jan  6 10:38:30 raspberrypi weewx[9872] INFO weewx.imagegenerator:
> Generated 30 images for report SeasonsReport in 2.05 seconds
> Jan  6 10:38:30 raspberrypi weewx[9872] INFO weewx.reportengine: Copied 5
> files to /var/www/html/weewx
> Jan  6 10:38:30 raspberrypi weewx[9872] DEBUG weewx.reportengine: Report
> 'SmartphoneReport' not enabled. Skipping.
> Jan  6 10:38:30 raspberrypi weewx[9872] DEBUG

Re: [weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Michael Sanphillipo]

Tom, do I do this in terminal and do I enter it exactly as you have it 
listed above?


On Wednesday, January 6, 2021 at 1:19:12 PM UTC-5 tke...@gmail.com wrote:

> The software is a little more hard-nosed about demanding valid values for 
> the field 'interval'. Somewhere in your database, you have a value of zero 
> for the archive interval length. To find them:
>
> *sqlite3 /var/weewx/weedwx.sdb*
> sqlite> *select dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
> interval from archive where interval<=0;*
>
> To delete them:
>
> sqlite> *delete from archive where interval<=0;*
>
> Alternatively, if you're confident you know what the correct value should 
> be (let's say it's 5 minutes);
>
> sqlite> *update archive set interval=5 where interval<=0;*
>
> -tk
>
> On Wed, Jan 6, 2021 at 9:49 AM Michael Sanphillipo  
> wrote:
>
>> I upgraded today and received the following errors in my Syslog. Any help 
>> would be greatly appreciated.
>>
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Initializing weewx 
>> version 4.3.0
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Using Python 3.7.3 
>> (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Platform 
>> Linux-5.4.79-v7+-armv7l-with-debian-10.7
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Locale is 
>> 'en_US.UTF-8'
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Debug is 0
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: Loading 
>> station type AcuRite (weewx.drivers.acurite)
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.drivers.acurite: 
>> driver version is 0.4
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> Jan  6 12:44:46 raspberrypi weewx[1051]: Starting weewx weather system: 
>> weewx.
>> Jan  6 12:44:46 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: Daily 
>> summaries at V2.0. Patching to V3.0
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: 
>> recalculate_weights: Using database 'weewx.sdb'
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: Caught 
>> unrecoverable exception:
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> Non-positive value for record field 'interval': 0
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> Traceback (most recent call last):
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewxd", line 148, in main
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> engine = weewx.engine.StdEngine(config_dict)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> self.loadServices(config_dict)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/wxservices.py", line 38, in __init__
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> self.db_manager = engine.db_binder.get_manager(data_binding=data_binding, 
>> initialize=True)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 534, in get_manager
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> self.manager_cache[data_binding] = open_manager(manager_dict, initialize)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 684, in open_manager
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> manager_dict['schema'])
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 164, in open_with_create
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> dbmanager = cls(connection, table_name=table_name, schema=schema)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 831, in __init__
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
>> self.patch_sums()
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", 

Re: [weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Michael Sanphillipo]

Tom, do I do this in terminal and do I enter it exactly as you have it
listed above?

On Wed, Jan 6, 2021 at 1:19 PM Tom Keffer  wrote:

> The software is a little more hard-nosed about demanding valid values for
> the field 'interval'. Somewhere in your database, you have a value of zero
> for the archive interval length. To find them:
>
> *sqlite3 /var/weewx/weedwx.sdb*
> sqlite> *select dateTime, datetime(dateTime, 'unixepoch', 'localtime'),
> interval from archive where interval<=0;*
>
> To delete them:
>
> sqlite> *delete from archive where interval<=0;*
>
> Alternatively, if you're confident you know what the correct value should
> be (let's say it's 5 minutes);
>
> sqlite> *update archive set interval=5 where interval<=0;*
>
> -tk
>
> On Wed, Jan 6, 2021 at 9:49 AM Michael Sanphillipo 
> wrote:
>
>> I upgraded today and received the following errors in my Syslog. Any help
>> would be greatly appreciated.
>>
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Initializing weewx
>> version 4.3.0
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Using Python 3.7.3
>> (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Platform
>> Linux-5.4.79-v7+-armv7l-with-debian-10.7
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Locale is
>> 'en_US.UTF-8'
>> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: PID file is
>> /var/run/weewx.pid
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Using
>> configuration file /etc/weewx/weewx.conf
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Debug is 0
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: Loading
>> station type AcuRite (weewx.drivers.acurite)
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.drivers.acurite:
>> driver version is 0.4
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: StdConvert
>> target unit is 0x1
>> Jan  6 12:44:46 raspberrypi weewx[1051]: Starting weewx weather system:
>> weewx.
>> Jan  6 12:44:46 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: Daily
>> summaries at V2.0. Patching to V3.0
>> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager:
>> recalculate_weights: Using database 'weewx.sdb'
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: Caught
>> unrecoverable exception:
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> Non-positive value for record field 'interval': 0
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> Traceback (most recent call last):
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewxd", line 148, in main
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> engine = weewx.engine.StdEngine(config_dict)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> self.loadServices(config_dict)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/wxservices.py", line 38, in __init__
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> self.db_manager = engine.db_binder.get_manager(data_binding=data_binding,
>> initialize=True)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 534, in get_manager
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> self.manager_cache[data_binding] = open_manager(manager_dict, initialize)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 684, in open_manager
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> manager_dict['schema'])
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 164, in open_with_create
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> dbmanager = cls(connection, table_name=table_name, schema=schema)
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 831, in __init__
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> self.patch_sums()
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> File "/usr/share/weewx/weewx/manager.py", line 1255, in patch_sums
>> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
>> self.recalculate_weights(start_d=da

Re: [weewx-user] Re: Wrong XTypes output after upgrading WeeWX 4.1.1 to 4.3.0

[Tom Keffer]

I would guess that the problem is that you are always returning
lowestTemperature in Fahrenheit, but your data records are in Celsius.

That part of XTypes has not changed. I don't know why it worked before.
Perhaps units were in Fahrenheit before?

-tk

On Wed, Jan 6, 2021 at 10:16 AM Arend  wrote:

> Hello Tom,
>
> I get strange output as can be seen in the chart below. It apperas the
> series isn't calculated/retrieved as it did before the upgrade. I hope this
> helps to understand.
>
> [image: daytempdew.png]
>
> Regards, Arend
> Op woensdag 6 januari 2021 om 19:12:47 UTC+1 schreef tke...@gmail.com:
>
>> It would help if we knew what the problem was. "No longer works" doesn't
>> tell us much.
>>
>> On Wed, Jan 6, 2021 at 10:00 AM Arend  wrote:
>>
>>> In addition to the previous: the get_scalar function still seems to be
>>> working but the get_series function no longer works.
>>>
>>> Op woensdag 6 januari 2021 om 18:33:12 UTC+1 schreef Arend:
>>>
 Everything worked fine until I did the upgrade.

 I guess something has changed in the way XTypes are handled?

 *This is the code I use in extensions.py:*

 #
 #Copyright (c) 2009-2015 Tom Keffer 
 #
 #See the file LICENSE.txt for your full rights.
 #

 """User extensions module

 This module is imported from the main executable, so anything put here
 will be
 executed before anything else happens. This makes it a good place to
 put user
 extensions.
 """

 import locale
 # This will use the locale specified by the environment variable 'LANG'
 # Other options are possible. See:
 # http://docs.python.org/2/library/locale.html#locale.setlocale
 locale.setlocale(locale.LC_ALL, '')

 import user.lowest_temperature
 import weewx.xtypes

 weewx.xtypes.xtypes.append(user.lowest_temperature.LowestTemperature())


 *This is the code in lowest_temperature.py:*

 import weewx.units
 import weewx.xtypes
 from weewx.units import ValueTuple

 class LowestTemperature(weewx.xtypes.XType):

   def get_scalar(self, obs_type, record, dbmanager):
 """Determine which sensor has lowest temperature."""
 if obs_type != 'lowTemperature':
   raise weewx.UnknownType
 try:
   record_us = weewx.units.to_US(record)
   if record_us['outTemp'] == None or record_us['extraTemp1'] ==
 None:
   # if record_us['outTemp'] < 100 or record_us['extraTemp1'] < 100:
 raise TypeError("Temperature(s) equal to None")
   if record_us['outTemp'] <= record_us['extraTemp1']:
 lowTemperature = record_us['outTemp']
   else:
 lowTemperature = record_us['extraTemp1']
   return ValueTuple(lowTemperature, "degree_F", "group_temperature")
 except KeyError:
   # Don't have everything we need. Raise an exception.
   raise weewx.CannotCalculate(obs_type)

   def get_series(self, obs_type, timespan, db_manager,
 aggregate_type=None, aggregate_interval=None):
 if obs_type != 'lowTemperature':
   raise weewx.UnknownType
 start_vec = list()
 stop_vec = list()
 data_vec = list()
 if aggregate_type:
   raise weewx.UnknownAggregation(aggregate_type)
 for record in db_manager.genSql("SELECT `dateTime`, `interval`,
 `usUnits`, `outTemp`, `extraTemp1` FROM `archive` WHERE `dateTime` >
 %(start)s AND `dateTime` <= %(stop)s;" % {'start': timespan[0], 'stop':
 timespan[1]}):
   if (record[2] != 1):
 raise weewx.CannotCalculate("units are not US")
   if record[3] == None or record[4] == None:
   # if record[3] < 100 or record[4] < 100:
 raise TypeError("Temperature(s) equal to None")
   start_vec.append(record[0] - record[1] * 60)
   stop_vec.append(record[0])
   if record[3] <= record[4]:
 data_vec.append(record[3])
   else:
 data_vec.append(record[4])
 return (ValueTuple(start_vec, 'unix_epoch', 'group_time'),
 ValueTuple(stop_vec, 'unix_epoch', 'group_time'), ValueTuple(data_vec,
 "degree_F", "group_temperature"))

 Do I need to rewrite all code?

 --
>>> 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 weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/5ac947ed-240d-428b-8a69-c0186359d97cn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from

Re: [weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Tom Keffer]

The software is a little more hard-nosed about demanding valid values for
the field 'interval'. Somewhere in your database, you have a value of zero
for the archive interval length. To find them:

*sqlite3 /var/weewx/weedwx.sdb*
sqlite> *select dateTime, datetime(dateTime, 'unixepoch', 'localtime'),
interval from archive where interval<=0;*

To delete them:

sqlite> *delete from archive where interval<=0;*

Alternatively, if you're confident you know what the correct value should
be (let's say it's 5 minutes);

sqlite> *update archive set interval=5 where interval<=0;*

-tk

On Wed, Jan 6, 2021 at 9:49 AM Michael Sanphillipo 
wrote:

> I upgraded today and received the following errors in my Syslog. Any help
> would be greatly appreciated.
>
> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Initializing weewx
> version 4.3.0
> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Using Python 3.7.3
> (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Platform
> Linux-5.4.79-v7+-armv7l-with-debian-10.7
> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Locale is
> 'en_US.UTF-8'
> Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: PID file is
> /var/run/weewx.pid
> Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Using configuration
> file /etc/weewx/weewx.conf
> Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Debug is 0
> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: Loading station
> type AcuRite (weewx.drivers.acurite)
> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.drivers.acurite: driver
> version is 0.4
> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: StdConvert
> target unit is 0x1
> Jan  6 12:44:46 raspberrypi weewx[1051]: Starting weewx weather system:
> weewx.
> Jan  6 12:44:46 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: Daily
> summaries at V2.0. Patching to V3.0
> Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager:
> recalculate_weights: Using database 'weewx.sdb'
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: Caught
> unrecoverable exception:
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> Non-positive value for record field 'interval': 0
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> Traceback (most recent call last):
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewxd", line 148, in main
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> engine = weewx.engine.StdEngine(config_dict)
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> self.loadServices(config_dict)
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/wxservices.py", line 38, in __init__
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> self.db_manager = engine.db_binder.get_manager(data_binding=data_binding,
> initialize=True)
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 534, in get_manager
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> self.manager_cache[data_binding] = open_manager(manager_dict, initialize)
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 684, in open_manager
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> manager_dict['schema'])
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 164, in open_with_create
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> dbmanager = cls(connection, table_name=table_name, schema=schema)
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 831, in __init__
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> self.patch_sums()
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 1255, in patch_sums
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> self.recalculate_weights(start_d=datetime.date(2020,6,1))
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/manager.py", line 1182, in recalculate_weights
> Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: 
> se

Re: [weewx-user] Re: Wrong XTypes output after upgrading WeeWX 4.1.1 to 4.3.0

[Arend]

Hello Tom,

I get strange output as can be seen in the chart below. It apperas the 
series isn't calculated/retrieved as it did before the upgrade. I hope this 
helps to understand.

[image: daytempdew.png]

Regards, Arend
Op woensdag 6 januari 2021 om 19:12:47 UTC+1 schreef tke...@gmail.com:

> It would help if we knew what the problem was. "No longer works" doesn't 
> tell us much.
>
> On Wed, Jan 6, 2021 at 10:00 AM Arend  wrote:
>
>> In addition to the previous: the get_scalar function still seems to be 
>> working but the get_series function no longer works.
>>
>> Op woensdag 6 januari 2021 om 18:33:12 UTC+1 schreef Arend:
>>
>>> Everything worked fine until I did the upgrade.
>>>
>>> I guess something has changed in the way XTypes are handled?
>>>
>>> *This is the code I use in extensions.py:*
>>>
>>> #
>>> #Copyright (c) 2009-2015 Tom Keffer 
>>> #
>>> #See the file LICENSE.txt for your full rights.
>>> #
>>>
>>> """User extensions module
>>>
>>> This module is imported from the main executable, so anything put here 
>>> will be
>>> executed before anything else happens. This makes it a good place to put 
>>> user
>>> extensions.
>>> """
>>>
>>> import locale
>>> # This will use the locale specified by the environment variable 'LANG'
>>> # Other options are possible. See:
>>> # http://docs.python.org/2/library/locale.html#locale.setlocale
>>> locale.setlocale(locale.LC_ALL, '')
>>>
>>> import user.lowest_temperature
>>> import weewx.xtypes
>>>
>>> weewx.xtypes.xtypes.append(user.lowest_temperature.LowestTemperature())
>>>
>>>
>>> *This is the code in lowest_temperature.py:*
>>>
>>> import weewx.units
>>> import weewx.xtypes
>>> from weewx.units import ValueTuple
>>>
>>> class LowestTemperature(weewx.xtypes.XType):
>>>
>>>   def get_scalar(self, obs_type, record, dbmanager):
>>> """Determine which sensor has lowest temperature."""
>>> if obs_type != 'lowTemperature':
>>>   raise weewx.UnknownType
>>> try:
>>>   record_us = weewx.units.to_US(record)
>>>   if record_us['outTemp'] == None or record_us['extraTemp1'] == None:
>>>   # if record_us['outTemp'] < 100 or record_us['extraTemp1'] < 100:
>>> raise TypeError("Temperature(s) equal to None")
>>>   if record_us['outTemp'] <= record_us['extraTemp1']:
>>> lowTemperature = record_us['outTemp']
>>>   else:
>>> lowTemperature = record_us['extraTemp1']
>>>   return ValueTuple(lowTemperature, "degree_F", "group_temperature")
>>> except KeyError:
>>>   # Don't have everything we need. Raise an exception.
>>>   raise weewx.CannotCalculate(obs_type)
>>>   
>>>   def get_series(self, obs_type, timespan, db_manager, 
>>> aggregate_type=None, aggregate_interval=None):
>>> if obs_type != 'lowTemperature':
>>>   raise weewx.UnknownType
>>> start_vec = list()
>>> stop_vec = list()
>>> data_vec = list()
>>> if aggregate_type:
>>>   raise weewx.UnknownAggregation(aggregate_type)
>>> for record in db_manager.genSql("SELECT `dateTime`, `interval`, 
>>> `usUnits`, `outTemp`, `extraTemp1` FROM `archive` WHERE `dateTime` > 
>>> %(start)s AND `dateTime` <= %(stop)s;" % {'start': timespan[0], 'stop': 
>>> timespan[1]}):
>>>   if (record[2] != 1):
>>> raise weewx.CannotCalculate("units are not US")
>>>   if record[3] == None or record[4] == None:
>>>   # if record[3] < 100 or record[4] < 100:
>>> raise TypeError("Temperature(s) equal to None") 
>>>   start_vec.append(record[0] - record[1] * 60)
>>>   stop_vec.append(record[0])
>>>   if record[3] <= record[4]:
>>> data_vec.append(record[3])
>>>   else:
>>> data_vec.append(record[4])
>>> return (ValueTuple(start_vec, 'unix_epoch', 'group_time'), 
>>> ValueTuple(stop_vec, 'unix_epoch', 'group_time'), ValueTuple(data_vec, 
>>> "degree_F", "group_temperature"))
>>>
>>> Do I need to rewrite all code?
>>>
>>> -- 
>> 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 weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/5ac947ed-240d-428b-8a69-c0186359d97cn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1b588685-d1ba-4940-99d7-b830a6b0b700n%40googlegroups.com.

Re: [weewx-user] Re: Wrong XTypes output after upgrading WeeWX 4.1.1 to 4.3.0

[Tom Keffer]

It would help if we knew what the problem was. "No longer works" doesn't
tell us much.

On Wed, Jan 6, 2021 at 10:00 AM Arend  wrote:

> In addition to the previous: the get_scalar function still seems to be
> working but the get_series function no longer works.
>
> Op woensdag 6 januari 2021 om 18:33:12 UTC+1 schreef Arend:
>
>> Everything worked fine until I did the upgrade.
>>
>> I guess something has changed in the way XTypes are handled?
>>
>> *This is the code I use in extensions.py:*
>>
>> #
>> #Copyright (c) 2009-2015 Tom Keffer 
>> #
>> #See the file LICENSE.txt for your full rights.
>> #
>>
>> """User extensions module
>>
>> This module is imported from the main executable, so anything put here
>> will be
>> executed before anything else happens. This makes it a good place to put
>> user
>> extensions.
>> """
>>
>> import locale
>> # This will use the locale specified by the environment variable 'LANG'
>> # Other options are possible. See:
>> # http://docs.python.org/2/library/locale.html#locale.setlocale
>> locale.setlocale(locale.LC_ALL, '')
>>
>> import user.lowest_temperature
>> import weewx.xtypes
>>
>> weewx.xtypes.xtypes.append(user.lowest_temperature.LowestTemperature())
>>
>>
>> *This is the code in lowest_temperature.py:*
>>
>> import weewx.units
>> import weewx.xtypes
>> from weewx.units import ValueTuple
>>
>> class LowestTemperature(weewx.xtypes.XType):
>>
>>   def get_scalar(self, obs_type, record, dbmanager):
>> """Determine which sensor has lowest temperature."""
>> if obs_type != 'lowTemperature':
>>   raise weewx.UnknownType
>> try:
>>   record_us = weewx.units.to_US(record)
>>   if record_us['outTemp'] == None or record_us['extraTemp1'] == None:
>>   # if record_us['outTemp'] < 100 or record_us['extraTemp1'] < 100:
>> raise TypeError("Temperature(s) equal to None")
>>   if record_us['outTemp'] <= record_us['extraTemp1']:
>> lowTemperature = record_us['outTemp']
>>   else:
>> lowTemperature = record_us['extraTemp1']
>>   return ValueTuple(lowTemperature, "degree_F", "group_temperature")
>> except KeyError:
>>   # Don't have everything we need. Raise an exception.
>>   raise weewx.CannotCalculate(obs_type)
>>
>>   def get_series(self, obs_type, timespan, db_manager,
>> aggregate_type=None, aggregate_interval=None):
>> if obs_type != 'lowTemperature':
>>   raise weewx.UnknownType
>> start_vec = list()
>> stop_vec = list()
>> data_vec = list()
>> if aggregate_type:
>>   raise weewx.UnknownAggregation(aggregate_type)
>> for record in db_manager.genSql("SELECT `dateTime`, `interval`,
>> `usUnits`, `outTemp`, `extraTemp1` FROM `archive` WHERE `dateTime` >
>> %(start)s AND `dateTime` <= %(stop)s;" % {'start': timespan[0], 'stop':
>> timespan[1]}):
>>   if (record[2] != 1):
>> raise weewx.CannotCalculate("units are not US")
>>   if record[3] == None or record[4] == None:
>>   # if record[3] < 100 or record[4] < 100:
>> raise TypeError("Temperature(s) equal to None")
>>   start_vec.append(record[0] - record[1] * 60)
>>   stop_vec.append(record[0])
>>   if record[3] <= record[4]:
>> data_vec.append(record[3])
>>   else:
>> data_vec.append(record[4])
>> return (ValueTuple(start_vec, 'unix_epoch', 'group_time'),
>> ValueTuple(stop_vec, 'unix_epoch', 'group_time'), ValueTuple(data_vec,
>> "degree_F", "group_temperature"))
>>
>> Do I need to rewrite all code?
>>
>> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/5ac947ed-240d-428b-8a69-c0186359d97cn%40googlegroups.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDKVqxjVdizyOr5nMvYPFxY5SGUq0T9vN26WkLa0zaUaA%40mail.gmail.com.

[weewx-user] Re: Wrong XTypes output after upgrading WeeWX 4.1.1 to 4.3.0

[Arend]

In addition to the previous: the get_scalar function still seems to be 
working but the get_series function no longer works.

Op woensdag 6 januari 2021 om 18:33:12 UTC+1 schreef Arend:

> Everything worked fine until I did the upgrade.
>
> I guess something has changed in the way XTypes are handled?
>
> *This is the code I use in extensions.py:*
>
> #
> #Copyright (c) 2009-2015 Tom Keffer 
> #
> #See the file LICENSE.txt for your full rights.
> #
>
> """User extensions module
>
> This module is imported from the main executable, so anything put here 
> will be
> executed before anything else happens. This makes it a good place to put 
> user
> extensions.
> """
>
> import locale
> # This will use the locale specified by the environment variable 'LANG'
> # Other options are possible. See:
> # http://docs.python.org/2/library/locale.html#locale.setlocale
> locale.setlocale(locale.LC_ALL, '')
>
> import user.lowest_temperature
> import weewx.xtypes
>
> weewx.xtypes.xtypes.append(user.lowest_temperature.LowestTemperature())
>
>
> *This is the code in lowest_temperature.py:*
>
> import weewx.units
> import weewx.xtypes
> from weewx.units import ValueTuple
>
> class LowestTemperature(weewx.xtypes.XType):
>
>   def get_scalar(self, obs_type, record, dbmanager):
> """Determine which sensor has lowest temperature."""
> if obs_type != 'lowTemperature':
>   raise weewx.UnknownType
> try:
>   record_us = weewx.units.to_US(record)
>   if record_us['outTemp'] == None or record_us['extraTemp1'] == None:
>   # if record_us['outTemp'] < 100 or record_us['extraTemp1'] < 100:
> raise TypeError("Temperature(s) equal to None")
>   if record_us['outTemp'] <= record_us['extraTemp1']:
> lowTemperature = record_us['outTemp']
>   else:
> lowTemperature = record_us['extraTemp1']
>   return ValueTuple(lowTemperature, "degree_F", "group_temperature")
> except KeyError:
>   # Don't have everything we need. Raise an exception.
>   raise weewx.CannotCalculate(obs_type)
>   
>   def get_series(self, obs_type, timespan, db_manager, 
> aggregate_type=None, aggregate_interval=None):
> if obs_type != 'lowTemperature':
>   raise weewx.UnknownType
> start_vec = list()
> stop_vec = list()
> data_vec = list()
> if aggregate_type:
>   raise weewx.UnknownAggregation(aggregate_type)
> for record in db_manager.genSql("SELECT `dateTime`, `interval`, 
> `usUnits`, `outTemp`, `extraTemp1` FROM `archive` WHERE `dateTime` > 
> %(start)s AND `dateTime` <= %(stop)s;" % {'start': timespan[0], 'stop': 
> timespan[1]}):
>   if (record[2] != 1):
> raise weewx.CannotCalculate("units are not US")
>   if record[3] == None or record[4] == None:
>   # if record[3] < 100 or record[4] < 100:
> raise TypeError("Temperature(s) equal to None") 
>   start_vec.append(record[0] - record[1] * 60)
>   stop_vec.append(record[0])
>   if record[3] <= record[4]:
> data_vec.append(record[3])
>   else:
> data_vec.append(record[4])
> return (ValueTuple(start_vec, 'unix_epoch', 'group_time'), 
> ValueTuple(stop_vec, 'unix_epoch', 'group_time'), ValueTuple(data_vec, 
> "degree_F", "group_temperature"))
>
> Do I need to rewrite all code?
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5ac947ed-240d-428b-8a69-c0186359d97cn%40googlegroups.com.

[weewx-user] Upgrading from 4.2 to 4.3 Python3 errors

[Michael Sanphillipo]

I upgraded today and received the following errors in my Syslog. Any help 
would be greatly appreciated.

Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Initializing weewx 
version 4.3.0
Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Using Python 3.7.3 
(default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Platform 
Linux-5.4.79-v7+-armv7l-with-debian-10.7
Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: Locale is 
'en_US.UTF-8'
Jan  6 12:44:46 raspberrypi weewx[1063] INFO __main__: PID file is 
/var/run/weewx.pid
Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Jan  6 12:44:46 raspberrypi weewx[1067] INFO __main__: Debug is 0
Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: Loading station 
type AcuRite (weewx.drivers.acurite)
Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.drivers.acurite: driver 
version is 0.4
Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.engine: StdConvert 
target unit is 0x1
Jan  6 12:44:46 raspberrypi weewx[1051]: Starting weewx weather system: 
weewx.
Jan  6 12:44:46 raspberrypi systemd[1]: Started LSB: weewx weather system.
Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: Daily summaries 
at V2.0. Patching to V3.0
Jan  6 12:44:46 raspberrypi weewx[1067] INFO weewx.manager: 
recalculate_weights: Using database 'weewx.sdb'
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: Caught 
unrecoverable exception:
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
Non-positive value for record field 'interval': 0
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
Traceback (most recent call last):
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 148, in main
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
engine = weewx.engine.StdEngine(config_dict)
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 93, in __init__
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
self.loadServices(config_dict)
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 161, in loadServices
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
obj = weeutil.weeutil.get_object(svc)(self, config_dict)
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/wxservices.py", line 38, in __init__
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
self.db_manager = engine.db_binder.get_manager(data_binding=data_binding, 
initialize=True)
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 534, in get_manager
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
self.manager_cache[data_binding] = open_manager(manager_dict, initialize)
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 684, in open_manager
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
manager_dict['schema'])
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 164, in open_with_create
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
dbmanager = cls(connection, table_name=table_name, schema=schema)
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 831, in __init__
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
self.patch_sums()
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 1255, in patch_sums
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
self.recalculate_weights(start_d=datetime.date(2020,6,1))
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 1182, in recalculate_weights
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
self._do_tranche(mark_d, end_of_tranche_d, weight_fn, progress_fn)
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 1215, in _do_tranche
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
weight = weight_fn(self, rec)
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 1366, in _calc_weight
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
"Non-positive value for record field 'interval': %s" % 
(record['interval'],))
Jan  6 12:44:52 raspberrypi weewx[1067] CRITICAL __main__:   
w

[weewx-user] cant find start time

[billandcorena ahrens]

$ sudo tail -f /var/log/syslog
Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jan  6 10:37:07 raspberrypi weewx[9872] INFO weewx.manager: Starting 
backfill of daily summaries
Jan  6 10:37:07 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
Getting all archive packets
Jan  6 10:37:08 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
Retrieving 263 page(s); starting index= 0
Jan  6 10:37:09 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty 
record page 0; index 0
Jan  6 10:37:09 raspberrypi weewx[9872] INFO weewx.engine: Starting main 
packet loop.
Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan  6 10:37:10 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
Requesting 200 LOOP packets.
Jan  6 10:37:11 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan  6 10:38:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
Getting all archive packets
Jan  6 10:38:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry 
#0 failed
Jan  6 10:38:26 raspberrypi weewx[9872] ERROR weewx.drivers.vantage: 
ip-read error: timed out
Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry 
#1 failed
Jan  6 10:38:26 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan  6 10:38:27 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
Retrieving 263 page(s); starting index= 0
Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Empty 
record page 0; index 0
Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
Requesting 200 LOOP packets.
Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'
Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary 
version is 3.0
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Skipping template NOAA/NOAA-%Y-%m.txt.tmpl: cannot find start time
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Skipping template NOAA/NOAA-%Y.txt.tmpl: cannot find start time
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Skipping template index.html.tmpl: cannot find start time
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Skipping template statistics.html.tmpl: cannot find start time
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Skipping template telemetry.html.tmpl: cannot find start time
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Skipping template tabular.html.tmpl: cannot find start time
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Skipping template celestial.html.tmpl: cannot find start time
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Skipping template rss.xml.tmpl: cannot find start time
Jan  6 10:38:28 raspberrypi weewx[9872] INFO weewx.cheetahgenerator: 
Generated 0 files for report SeasonsReport in 0.02 seconds
Jan  6 10:38:28 raspberrypi weewx[9872] DEBUG weewx.manager: Daily summary 
version is 3.0
Jan  6 10:38:29 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan  6 10:38:30 raspberrypi weewx[9872] INFO weewx.imagegenerator: 
Generated 30 images for report SeasonsReport in 2.05 seconds
Jan  6 10:38:30 raspberrypi weewx[9872] INFO weewx.reportengine: Copied 5 
files to /var/www/html/weewx
Jan  6 10:38:30 raspberrypi weewx[9872] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Jan  6 10:38:30 raspberrypi weewx[9872] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Jan  6 10:38:30 raspberrypi weewx[9872] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Jan  6 10:38:30 raspberrypi weewx[9872] DEBUG weewx.reportengine: Report 
'FTP' not enabled. Skipping.
Jan  6 10:38:30 raspberrypi weewx[9872] DEBUG weewx.reportengine: Report 
'RSYNC' not enabled. Skipping.
Jan  6 10:39:15 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: 
Getting all archive packets
Jan  6 10:39:19 raspberrypi weewx[9872] DEBUG weewx.drivers.vantage: Retry 
#0 failed
Jan  6 10:39:26 raspberrypi weewx[9872] ERROR weewx.drivers.v

[weewx-user] Wrong XTypes output after upgrading WeeWX 4.1.1 to 4.3.0

[Arend]

Everything worked fine until I did the upgrade.

I guess something has changed in the way XTypes are handled?

*This is the code I use in extensions.py:*

#
#Copyright (c) 2009-2015 Tom Keffer 
#
#See the file LICENSE.txt for your full rights.
#

"""User extensions module

This module is imported from the main executable, so anything put here will 
be
executed before anything else happens. This makes it a good place to put 
user
extensions.
"""

import locale
# This will use the locale specified by the environment variable 'LANG'
# Other options are possible. See:
# http://docs.python.org/2/library/locale.html#locale.setlocale
locale.setlocale(locale.LC_ALL, '')

import user.lowest_temperature
import weewx.xtypes

weewx.xtypes.xtypes.append(user.lowest_temperature.LowestTemperature())


*This is the code in lowest_temperature.py:*

import weewx.units
import weewx.xtypes
from weewx.units import ValueTuple

class LowestTemperature(weewx.xtypes.XType):

  def get_scalar(self, obs_type, record, dbmanager):
"""Determine which sensor has lowest temperature."""
if obs_type != 'lowTemperature':
  raise weewx.UnknownType
try:
  record_us = weewx.units.to_US(record)
  if record_us['outTemp'] == None or record_us['extraTemp1'] == None:
  # if record_us['outTemp'] < 100 or record_us['extraTemp1'] < 100:
raise TypeError("Temperature(s) equal to None")
  if record_us['outTemp'] <= record_us['extraTemp1']:
lowTemperature = record_us['outTemp']
  else:
lowTemperature = record_us['extraTemp1']
  return ValueTuple(lowTemperature, "degree_F", "group_temperature")
except KeyError:
  # Don't have everything we need. Raise an exception.
  raise weewx.CannotCalculate(obs_type)
  
  def get_series(self, obs_type, timespan, db_manager, aggregate_type=None, 
aggregate_interval=None):
if obs_type != 'lowTemperature':
  raise weewx.UnknownType
start_vec = list()
stop_vec = list()
data_vec = list()
if aggregate_type:
  raise weewx.UnknownAggregation(aggregate_type)
for record in db_manager.genSql("SELECT `dateTime`, `interval`, 
`usUnits`, `outTemp`, `extraTemp1` FROM `archive` WHERE `dateTime` > 
%(start)s AND `dateTime` <= %(stop)s;" % {'start': timespan[0], 'stop': 
timespan[1]}):
  if (record[2] != 1):
raise weewx.CannotCalculate("units are not US")
  if record[3] == None or record[4] == None:
  # if record[3] < 100 or record[4] < 100:
raise TypeError("Temperature(s) equal to None") 
  start_vec.append(record[0] - record[1] * 60)
  stop_vec.append(record[0])
  if record[3] <= record[4]:
data_vec.append(record[3])
  else:
data_vec.append(record[4])
return (ValueTuple(start_vec, 'unix_epoch', 'group_time'), 
ValueTuple(stop_vec, 'unix_epoch', 'group_time'), ValueTuple(data_vec, 
"degree_F", "group_temperature"))

Do I need to rewrite all code?

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/abb03705-953a-4626-a1ef-7d43a7cf688en%40googlegroups.com.

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

[tim lambert]

Hi John,

After leaving the server run uninterrupted, all of the data being displayed 
on weewx is ticking to the ip-100 console.   

Apologies for my ignorance, where can I exactly find the inclusion of the 
station volts you noted in your last comm (btw Thanks for addressing).

On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com wrote:

> > Once I sort this possible discrepancy, I'd like to pick your brain on 
> adding the Station Volts.
>
> I added it at head.  Station volts will now show up as supplyVoltage.
>
> On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
>
> 
>
> The IP100 resets the day’s rain total at midnight (according to it’s 
> clock).  It doesn’t really matter to the driver when that happens.  The 
> driver is simply looking for a positive increment in day_rain_total.  On a 
> negative increment (e.g., reset), the driver just saves the last value and 
> reports 0.0 for rain.
>
> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
>
> 
> Thanks for the guidance John!   I was anticipating to simply have a day 
> with a clean run, starting at midnight.  I should have this info tomorrow.
>
> I assume the loop will recognize my local timezone to reset to zero at 
> midnight, recognizing the db is being recorded on GMT?
>
> Once I sort this possible discrepancy, I'd like to pick your brain on 
> adding the Station Volts.
>
> Regards,
>
> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com wrote:
>
>> You don’t to delete records.  There isn’t really much to the rain 
>> calculation.  For all rain that occurred while WeeWX is up and running, the 
>> day_rain_total will increment, the driver will calculate the delta and add 
>> it to the loop record as ‘rain’.  For the discrepancy to occur, 0.09 inches 
>> would have had to happen while WeeWX wasn’t running.
>>
>> Let’s try a day where WeeWX has been running, uninterrupted, since 
>> midnight.
>>
>> On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
>>
>> 
>>
>> Thanks for the quick response John!
>>
>> I am running your version of the IP100 for weewx 4 - version 0.5
>>
>> I did restart the weewx today -- had some network issues, compliments of 
>> Comcast.   However, I've witnessed discrepancies between the IP100 Console 
>> and weewx for several days -- just finally had a chance to get some data 
>> captures.   I may need to capture data again tomorrow (knowing it will be 
>> raining buckets again).
>>
>> At this point in time:
>>
>>   
>> IP100weewx
>> Rainfall  
>> 0.06   0.15
>> Rain Rate  0.00   
>> 0.00
>>
>> Can I truncate (delete all records) from the weewx.sdb (after backing up 
>> of course) to start fresh, so that we have a solid baseline to evaluate?
>>
>> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com wrote:
>>
>>> Station volts is not in the default map.  It wouldn’t be hard to add.
>>>
>>> I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and bumped 
>>> the version to 0.5 in my fork).  I’m presuming you are running it.
>>>
>>> Although I’m not currently running the driver, I did run it for almost 
>>> two years and rain values ALWAYS agreed with my WeeWX instances running the 
>>> CC3000 driver and talking to the same RainWise weather station.
>>>
>>> day_rain_total is used to calculate rain.  It is not, in itself saved to 
>>> the database.
>>>
>>> I have not downloaded your files.  You’ll have to tell me if the ip100 
>>> console does not agree with the console for today’s rain and, if not, what 
>>> two values you are seeing.  Please list them.
>>>
>>> If you do have a discrepancy for today’s rain, please state if you 
>>> restarted weewx today (or if it restarted on its own today).  That would be 
>>> a way to lose rainfall.
>>>
>>>
>>> On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:
>>>
>>> 
>>>
>>> I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the 
>>> IP-100 v0.5 extension.  It appears the IP-100 Console data does not match 
>>> the data presented via weewx (using the out-of-box index.html, which is 
>>> using the SeasonsSkin) -- particularly, the Rain and Rain Rate.   I've 
>>> shared screen shots of both the IP-100 Console and the weewx html
>>>
>>> Based on some investigation, the log file (attached) indicates the data 
>>> which is showing on the IP-100 Console is being captured correctly,   
>>> However, looking at the archive table (attached) in the weewx.sdb, it does 
>>> not appear the data elements are being posted to the archive table 
>>> correctly - specifically day_rain_total (log) vs rain (archive table) and 
>>> rain (log) vs rainRate (archive table).
>>>
>>> Additionally, the station_volts (log file) are not being posted to the 
>>> archive table.
>>>
>>> I'm new to this world, but do have some technical bones -- any guidance 
>>> on what actions need 

Re: [weewx-user] Belchertown - suppressing graph=homepage >

[David Levine]

Using https://belchertownweather.com/graphs/ as a reference, none of the 
links are to graph=homepage, There are links to graph=all, graph=day, 
graph=week, ... No graph=homepage.  If I remove the [homepage] section in 
graphs.conf,  an error is generated to syslog and when I go to .../graphs/ 
I get no graphs displayed on that landing page. 

Not to complicate things further but if leave [homepage] and change the 
button to say Today, I get an acceptable approach, but then I'd like to 
remove the [day] section as it seems to be a duplicate. If I remove [day] I 
also seem to get no graphs generated on the .../graphs/ page. 

If it helps, this is where the generated pages are getting FTP'ed to from 
my local Raspberry pi - http://www.levinecentral.com/weather/graphs/ 

If I comment out [day] in graphs.conf, 
http://www.levinecentral.com/weather/graphs/ won't show any graphs between 
the buttons and footer. 

David

On Tuesday, January 5, 2021 at 11:12:54 PM UTC-5 colin@gmail.com wrote:

> Why do you wish to remove it, what are you trying to achieve? I'm a little 
> confused sorry
>
> Colin
>
> On Wed, 6 Jan 2021 at 16:25, David  wrote:
>
>> Thanks but that does not seem to be the situation I’m encountering.  
>>
>> I can’t seem to remove/rename [homepage] in graphs.conf
>>
>>
>>
>> On Tue, Jan 5, 2021 at 10:07 PM Timothy L  wrote:
>>
>>> Is this thread what you are asking?
>>> https://groups.google.com/g/weewx-user/c/qUt0XdqREqk/m/gGh5Of8cAgAJ
>>>
>>>
>>> On January 5, 2021, at 7:34 PM, David Levine  wrote:
>>>
>>>
>>> When I look at https://belchertownweather.com/graphs/ there is no 
>>> ?graph=homepage present.  When I comment out, rename or remove the 
>>> [homepage] section in graphs.conf, an error is generated to syslog and 
>>> there's nothing displayed on my site at /graphs/ . 
>>>
>>> I can add other sections such as [yesterday] but I've not found the 
>>> magic to remove.rename homepage. 
>>>
>>> What am I missing? Running the new 4.3 version of weewx and latest 
>>> Belchertown skin.
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>> Generate failed with exception ''
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>>  Ignoring template /etc/weewx/skins/Belchertown/index.html.tmpl
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>>  Reason: 'homepage'
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>>   Traceback (most recent call last):
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in 
>>> generate
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>>   unicode_string = compiled_template.respond()
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>> File "_etc_weewx_skins_Belchertown_index_html_tmpl.py", line 1508, 
>>> in respond
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>> File "_etc_weewx_skins_Belchertown_index_html_tmpl.py", line 631, 
>>> in __errorCatcher81
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>> File "", line 1, in 
>>>
>>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator: 
>>>   KeyError: 'homepage'
>>>
>>> David
>>>
>>> -- 
>>> 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 weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/b08a5bed-c75b-4148-a586-9e8ed16f0c05n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> -- 
>>> 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/Zmli8blPTIM/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/c4dgvo32pceu9rro6rkqv5s9.1609902439052%40email.android.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> 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 weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAGu77J8UuuJocDp%2

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[Joe]

I upgraded to the most recent release, and it is reporting, generating new 
graphs on schedule.  

Not sure why that had any bearing on it, but it's working 100% now.



On Tuesday, January 5, 2021 at 5:34:42 PM UTC-6 Joe wrote:

> Log give any clues ?
>
> On Monday, January 4, 2021 at 1:36:42 PM UTC-6 sali...@gmail.com wrote:
>
>> hi
>>
>> happy new year at all
>>
>> I had already this issue, now I used a disk ssd for my RPi3b.
>>
>> bye
>>
>> Patrick
>> Le 04/01/2021 à 20:18, Xant a écrit :
>>
>>
>> I recently also had a corrupted SD card. Tried many alternatives to 
>> recover data, including trying to mount at a Linux machine (at no prevail).
>>
>> The only (Windows) solution that actually worked was, where I was able to 
>> read and retrieve data, was the freeware "DiskInternals Linux Reader":
>>
>> https://www.diskinternals.com/linux-reader/
>>
>>
>> Xant
>>
>> On Monday, January 4, 2021 at 6:19:41 AM UTC-5 Joe wrote:
>>
>>>   GNU nano 3.2  
>>>   syslog
>>> 
>>>   
>>>
>>>
>>> Here is the log
>>>
>>>
>>> Jan  4 00:25:33 raspberrypi weewx[677] INFO weewx.restx: 
>>> Wunderground-RF: Published record 2021-01-04 00:25:33 CST (1609741533)
>>> Jan  4 00:25:35 raspberrypi weewx[677] INFO weewx.restx: 
>>> Wunderground-RF: Published record 2021-01-04 00:25:35 CST (1609741535)
>>> Jan  4 00:25:36 raspberrypi weewx[677] INFO weewx.imagegenerator: 
>>> Generated 13 images for report StandardReport in 8.04 seconds
>>> Jan  4 00:25:36 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
>>> files to /var/www/weewx
>>> Jan  4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
>>> report 'SeasonsReport'
>>> Jan  4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
>>> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
>>> 'SeasonsReport'
>>> Jan  4 00:25:37 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: 
>>> Using search list ['weewx.cheetahgenerator.Almanac', 
>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
>>> Jan  4 00:25:37 raspberrypi weewx[677] DEBUG weewx.manager: Daily 
>>> summary version is 2
>>> Jan  4 00:25:49 raspberrypi weewx[677] INFO weewx.restx: 
>>> Wunderground-RF: Published record 2021-01-04 00:25:49 CST (1609741549)
>>> Jan  4 00:25:49 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
>>> Generated 8 files for report SeasonsReport in 12.96 seconds
>>> Jan  4 00:25:49 raspberrypi weewx[677] DEBUG weewx.manager: Daily 
>>> summary version is 2
>>> Jan  4 00:25:57 raspberrypi weewx[677] INFO weewx.imagegenerator: 
>>> Generated 14 images for report SeasonsReport in 7.65 seconds
>>> Jan  4 00:25:57 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
>>> files to /var/www/weewx
>>> Jan  4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
>>> report 'SmartphoneReport'
>>> Jan  4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
>>> configuration file /etc/weewx/skins/Smartphone/skin.conf for report 
>>> 'SmartphoneReport'
>>> Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: 
>>> Using search list ['weewx.cheetahgenerator.Almanac', 
>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
>>> Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily 
>>> summary version is 2
>>> Jan  4 00:25:58 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
>>> Generated 6 files for report SmartphoneReport in 0.75 seconds
>>> Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily 
>>> summary version is 2Jan  4 00:26:01 raspberrypi weewx[677] INFO 
>>> weewx.restx: Wunderground-RF: Published record 2021-01-04 00:26:01 CST 
>>> (1609741561)
>>> Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.imagegenerator: 
>>> Generated 6 images for report SmartphoneReport in 3.04 seconds
>>> Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
>>> files to /smartphone
>>> Jan  4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
>>> report 'MobileReport'
>>> Jan  4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
>>> configuration file /etc/weewx/skins/Mobile/skin.conf for report 
>>> 'MobileReport'
>>> Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: 
>>> Using search list ['weewx.cheetahgenerator.Almanac', 
>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
>>> Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.manager: Daily 
>>> summary version is 2
>>> Jan  4 00:26:02 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
>>> Generated 1 files for report MobileReport in 0.29 seconds
>>> Ja

[weewx-user] Re: Version 4.3.0 released

[paul.ba...@gmail.com]

Updated and works fine, no single problem.
Use Debian 10.3  and 10.4,  
IROX Pro X1 and Weatherflow Tempest stations (two independent computers).
Thanks a  lot, Paul

Le Tuesday, January 5, 2021 à 8:51:18 PM UTC+1, vince a écrit :

> A quick FYI for folks running old ubuntu-1804 versions (bionic).   If you 
> install weewx via packages, there is no python3-cheetah package available 
> to install, so the normal python3 dpkg installation fails.   A workaround 
> is to use the python2 package instructions which work fine.
>
> (tested in vagrant/virtualbox)
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3988232b-9587-4599-b040-40aed88867f0n%40googlegroups.com.