[weewx-user] Re: Importing Weatherflow data

[David Prellwitz]

sorry, my touchpad has caused early posting!
To continue, 
5. Edit the import file to include the field names.
6. run wee-import --test only
7. evaluate results, make corrections
8. run final import
9. restart weewx

any way to verify success?


On Monday, February 22, 2021 at 10:27:44 PM UTC-8 David Prellwitz wrote:

> I'm trying to import (wee_import) two weeks of data from my tempest 
> repository held at Weatherflow. The API page example of my data shows no 
> header in the csv file. How should i handle this import? should i edit the 
> file by adding the first reacord and inserting the proper field names?
> i assume the normal approach is to:
> 1. create the import config file.
> 2. extract the WeatherFlow data use their API.
> 3. stop weewx, 
> 4. copy current db as backup, 
> 5. edit 
> 6. 
>
>

-- 
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/cf1c3360-2673-47d0-8ba0-14de86edfd07n%40googlegroups.com.

[weewx-user] Importing Weatherflow data

[David Prellwitz]

I'm trying to import (wee_import) two weeks of data from my tempest 
repository held at Weatherflow. The API page example of my data shows no 
header in the csv file. How should i handle this import? should i edit the 
file by adding the first reacord and inserting the proper field names?
i assume the normal approach is to:
1. create the import config file.
2. extract the WeatherFlow data use their API.
3. stop weewx, 
4. copy current db as backup, 
5. edit 
6. 

-- 
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/0b956915-bd15-45d3-806c-bb6c80ab1bfan%40googlegroups.com.

[weewx-user] Belchertown skin with local Australian forecast

[Neville Davis]

This is a link to my current weather site.
http://nevsweather.duckdns.org:8048/weather/belchertown/index.html
I have updated my link to this site on my weewx Wiki page entry (pi weather 
with i2C sensors).
The skin now has two extra pages, one for a colour history chart (code by 
Nick Dajda used in his Bootstrap skin) and one for the local forecast for 
SEQ Australia(code by Darryn Capes-Davis for his responsive skin).

I have been having problems posting this just wondering if it did not 
accept the Bitly link I had in it.hopefully this works.

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/632e04d0-4726-491f-9e23-323a97d9cafbn%40googlegroups.com.

[weewx-user] Re: test

[Neville Davis]

That seems to be it... not sure what happened.

On Tuesday, February 23, 2021 at 9:41:41 AM UTC+10 Neville Davis wrote:

> I seemed to be unable to post, found not linked to my google account.. 
> this is to see if this works.
>
> 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/529a1740-3fd2-468f-9a33-4b83f6a413b3n%40googlegroups.com.

[weewx-user] test

[Neville Davis]

I seemed to be unable to post, found not linked to my google account.. this 
is to see if this works.

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/2beb88f9-c845-44e8-8d7b-38079eeb59adn%40googlegroups.com.

Re: [weewx-user] Version 4.4.0

[Tom Keffer]

Here's the problem: when a browser renders a document, it needs to know
what encoding it is in. For HTML documents, this is specified by a meta tag



However, with a plain text document, there is no way to specify the
encoding, so, instead, browsers must use a default. From what I can tell,
most default to cp1252 (aka, Windows-1252), *not* UTF-8. Hence, if we
encode the NOAA documents in UTF-8, the browser will not know it and,
instead, will default to cp1252, giving odd results.

The good news is that the Danish characters can be encoded using cp1252, so
use that as the encoding. I.e.,

[[SummaryByMonth]]
# Reports that summarize "by month"
[[[NOAA_month]]]
encoding = cp1252
template = NOAA/NOAA-%Y-%m.txt.tmpl

This will only work with V4.4.1 and later (not released yet).

You can understand that we can't make this the default for the NOAA reports
because not all characters can be encoded in cp1252. If a character cannot
be encoded, then an exception is raised, terminating the report. So,
normalized_ascii was chosen for the default.

-tk




On Mon, Feb 22, 2021 at 1:03 PM gert.a...@gmail.com 
wrote:

> Hi Tom
> At #1 you wrote:
> NOAA reports now use a 'utf8' encoding instead of 'strict_ascii'. This
> will only
> affect new installations. Fixes issue #644.
>
> When I look at the skin.conf, utf8 has disappeared as a choice:
> # Possible encodings include 'html_entities', 'strict_ascii',
> 'normalized_ascii',
>
> normalized_ascii will not show danish characters correct(æåøÆÅØ)
>
> From the NOAA report:
> normalized_ascii:
> NAME: Vester Smarken, Bornholm
>
> With utf8:
> NAME: Vester Sømarken, Bornholm
>
> Rgds
> Gert
>
>
>
>
>
>
> On Saturday, February 6, 2021 at 10:48:39 PM UTC+1 tre...@gmail.com wrote:
>
>> My first upgrade of Wewwx (after years on wview). Upgraded from 4.1.1 to
>> 4.4.0 with Belchertown 1.2 on a Ubuntu 20.04 VM using the setup.py method.
>> Wow that was smooth... Great software and wonderful community.
>>
>> On Thursday, February 4, 2021 at 7:14:28 AM UTC-7 kk44...@gmail.com
>> wrote:
>>
>>> Meanwhile I would add, that the update was without problems in my case
>>> (Ubuntu apt-get upgrade). I use Belchertown skin and some additional
>>> uploaders.
>>>
>>> Vetti52 schrieb am Donnerstag, 4. Februar 2021 um 11:04:43 UTC+1:
>>>
 Hi,
 maybe a new thread would be helpful, because the issue is/was very
 special and might not be a problem with version 4.4.0:

 After I realized, that weewx could be run manually, I was inspecting,
 what was the difference. I had updated to version 4.4.0 and also had an
 update for my Zigbee device driver (deCONZ). Then I had to reboot the
 Raspberry Pi and after that the error occured. Finally I realized, that,
 the /etc/init.d/weewx start failed, with code=exited but no success. I
 misinterpreted this as that weewx was not running, since there were no
 syslog entries at all. Repeating to start weewx using the previous
 interceptor driver did not work either. So I decided to let it run with
 gw1000 driver, but started it manually with sudo weewxd
 /etc/weewx/weewx.conf >nul &.  This was successful, and went to
 sleep
 Today I decided to look at this issue again and, instead of killing the
 manually started weexd properly, I accidently used /etc/init.d/weewx
 stop, which indeed stopped weewx, but the manually started weewxd
 continued. After I stopped this too, I realized, that weewx had in fact
 been started autmatically after reboot, but got stuck, as you say, because
 of the gw1000 driver. What I did not expect, is, that weewx then did not
 exit. Any additional starting command therefore failed. I was cind of
 silly, not to look at that, sorry. After stopping the hanging weewx, I
 could start weewx as expected, and now it works without any issues. Maybe,
 it would be better not to start weewx with its init.d script, but with 
 systemctl
 using a separate weewx.service file which should contain a stanza like

 [Unit]
 After=network-online.target

 that would avoid to start weewx before network is up, which seems to be
 a crucial step for gw1000. But this should be another thread, I think.

 Thanks
 Peter
 gjr80 schrieb am Mittwoch, 3. Februar 2021 um 20:33:21 UTC+1:

> Ok, can you please set debug=1, restart WeeWX as a daemon and post in
> a new thread the log through until the failure occurs.
>
> Gary
>
> On Thursday, 4 February 2021 at 05:28:00 UTC+10 Vetti52 wrote:
>
>> just to narrow down my problem:
>>
>> When starting manually
>>  weewxd /etc/weewx/weewx.conf
>> it works. Starting with
>> systemctl start weewx,
>> it fails.
>> Maybe, I will find out, what makes the difference. But, just in case,
>> someone knows the trick, please tell!
>>
>> Thanks
>> -Peter
>>
>> 

Re: [weewx-user] Version 4.4.0

[gert.a...@gmail.com]

Hi Tom
At #1 you wrote:
NOAA reports now use a 'utf8' encoding instead of 'strict_ascii'. This will 
only
affect new installations. Fixes issue #644. 

When I look at the skin.conf, utf8 has disappeared as a choice: 
# Possible encodings include 'html_entities', 'strict_ascii', 
'normalized_ascii', 

normalized_ascii will not show danish characters correct(æåøÆÅØ)

>From the NOAA report:
normalized_ascii:
NAME: Vester Smarken, Bornholm

With utf8:
NAME: Vester Sømarken, Bornholm 

Rgds
Gert






On Saturday, February 6, 2021 at 10:48:39 PM UTC+1 tre...@gmail.com wrote:

> My first upgrade of Wewwx (after years on wview). Upgraded from 4.1.1 to 
> 4.4.0 with Belchertown 1.2 on a Ubuntu 20.04 VM using the setup.py method. 
> Wow that was smooth... Great software and wonderful community.
>
> On Thursday, February 4, 2021 at 7:14:28 AM UTC-7 kk44...@gmail.com wrote:
>
>> Meanwhile I would add, that the update was without problems in my case 
>> (Ubuntu apt-get upgrade). I use Belchertown skin and some additional 
>> uploaders.
>>
>> Vetti52 schrieb am Donnerstag, 4. Februar 2021 um 11:04:43 UTC+1:
>>
>>> Hi,
>>> maybe a new thread would be helpful, because the issue is/was very 
>>> special and might not be a problem with version 4.4.0:
>>>
>>> After I realized, that weewx could be run manually, I was inspecting, 
>>> what was the difference. I had updated to version 4.4.0 and also had an 
>>> update for my Zigbee device driver (deCONZ). Then I had to reboot the 
>>> Raspberry Pi and after that the error occured. Finally I realized, that, 
>>> the /etc/init.d/weewx start failed, with code=exited but no success. I 
>>> misinterpreted this as that weewx was not running, since there were no 
>>> syslog entries at all. Repeating to start weewx using the previous 
>>> interceptor driver did not work either. So I decided to let it run with 
>>> gw1000 driver, but started it manually with sudo weewxd 
>>> /etc/weewx/weewx.conf >nul &.  This was successful, and went to 
>>> sleep
>>> Today I decided to look at this issue again and, instead of killing the 
>>> manually started weexd properly, I accidently used /etc/init.d/weewx 
>>> stop, which indeed stopped weewx, but the manually started weewxd 
>>> continued. After I stopped this too, I realized, that weewx had in fact 
>>> been started autmatically after reboot, but got stuck, as you say, because 
>>> of the gw1000 driver. What I did not expect, is, that weewx then did not 
>>> exit. Any additional starting command therefore failed. I was cind of 
>>> silly, not to look at that, sorry. After stopping the hanging weewx, I 
>>> could start weewx as expected, and now it works without any issues. Maybe, 
>>> it would be better not to start weewx with its init.d script, but with 
>>> systemctl 
>>> using a separate weewx.service file which should contain a stanza like
>>>
>>> [Unit]
>>> After=network-online.target
>>>
>>> that would avoid to start weewx before network is up, which seems to be 
>>> a crucial step for gw1000. But this should be another thread, I think.
>>>
>>> Thanks 
>>> Peter
>>> gjr80 schrieb am Mittwoch, 3. Februar 2021 um 20:33:21 UTC+1:
>>>
 Ok, can you please set debug=1, restart WeeWX as a daemon and post in a 
 new thread the log through until the failure occurs.

 Gary

 On Thursday, 4 February 2021 at 05:28:00 UTC+10 Vetti52 wrote:

> just to narrow down my problem:
>
> When starting manually 
>  weewxd /etc/weewx/weewx.conf
> it works. Starting with
> systemctl start weewx, 
> it fails.
> Maybe, I will find out, what makes the difference. But, just in case, 
> someone knows the trick, please tell!
>
> Thanks
> -Peter
>
> Vetti52 schrieb am Mittwoch, 3. Februar 2021 um 18:20:07 UTC+1:
>
>> Typo: Upgrade from 4.3.0 to 4.4.0.
>> Version 4.3.0 had no issues so far.
>>
>> Vetti52 schrieb am Mittwoch, 3. Februar 2021 um 18:17:46 UTC+1:
>>
>>> Just upgraded from 4.4.3 to 4.4.0, but it fails.
>>> got this in systemctl status weewx.service:
>>> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
>>> weewx.engine:   debug_wind=self.debug_wind)
>>> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
>>> weewx.engine: File "/usr/share/weewx/user/gw1000.py", line 
>>> 2166, in __init__
>>> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
>>> weewx.engine:   
>>> lost_contact_log_period=lost_contact_log_period)
>>> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
>>> weewx.engine: File "/usr/share/weewx/user/gw1000.py", line 
>>> 2915, in __init__
>>> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
>>> weewx.engine:   ip_port_list = self.discover()
>>> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
>>> weewx.engine: File 

Re: [weewx-user] Running Klimalogg and Fine Offset in one weewx session?

[Rainer Lang]

the Klimalogg Pro database consists of two databases (default names: 
weewx.sdb and weewx-kl.sdb) - they will have of course be located in a 
different directory from your standard weewx installation if you keep 
the database names.
The installation will not run with the weewx-kl.sdb only - even though 
the archived data will be in weewx-kl.sdb.
I found that out the hard way thinking for a restore only the 
weewx-kl.sdb was necessary. Luckily the KLP has a 50,000 record internal 
storage which could be reloaded when starting from scratch again.


You will have to run two separate instances of weewx and for each your 
SQLITE_ROOT should be different - (if for you session = instance, then 
not one session).


As they are/will be located in different directories fed by two separate 
weewx instances (with their own weewx.conf - e.g. fineoffset.conf and 
klp.conf), you don't need to rename the databases - but you can.
maybe for a better recognition you should do this. (The weewx multi 
description uses the rename approach, see below)


If in your wording session = one weewx installation on one server, then 
you are correct.


By the way - I'm running both myself (weewx with GW1000 and weewx with 
Klimalogg Pro) - so far still on two separate RPi4s, but one of my next 
activities will be to move them onto one RPi4.


There is a setup description on GitHub for running two stations and two 
weewx instances on one server - recently updated.


https://github.com/weewx/weewx/wiki/weewx-multi


On 22.02.2021 17:17, Maarten Weerman wrote:

Hi all,

I have weewx 4.4.0 already running with a Fine Offset Station and it 
works fine. I also have a TFA Klimalogg station with two external 
sensors. I've read out that it is possible to get data with a weewx 
Klimalogg driver and that it is also possible two run two stations in 
one weewx session.


I have some questions: I've read that the table structure of the 
klimalogg database is different from the "normal" weewx.sdb database. 
Does that have any effect when running two stations in one weewx?


And regarding the existing weewx.sdb table, do i have to rename it in 
e.g. "fineoffset.sdb" or can i keep the current name weewx.sdb? I 
still want to use my existing weewx.sdb database table for data from 
my Fine Offset Station and just add the "Klimalogg.sdb" database for 
the Klimalogg Pro.


Best regards

Georg






--
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/CAKEu0RNRcUiT%2B-bNQbsPnaMtZEisjuXDcHm9T0eju1L%2BnTDXcA%40mail.gmail.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/24a63a77-b826-1784-513c-0e3d775bb720%40gmail.com.

[weewx-user] Running Klimalogg and Fine Offset in one weewx session?

[Maarten Weerman]

Hi all,

I have weewx 4.4.0 already running with a Fine Offset Station and it works
fine. I also have a TFA Klimalogg station with two external sensors. I've
read out that it is possible to get data with a weewx Klimalogg driver and
that it is also possible two run two stations in one weewx session.

I have some questions: I've read that the table structure of the klimalogg
database is different from the "normal" weewx.sdb database. Does that have
any effect when running two stations in one weewx?

And regarding the existing weewx.sdb table, do i have to rename it in e.g.
"fineoffset.sdb" or can i keep the current name weewx.sdb? I still want to
use my existing weewx.sdb database table for data from my Fine Offset
Station and just add the "Klimalogg.sdb" database for the Klimalogg Pro.

Best regards

Georg

-- 
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/CAKEu0RNRcUiT%2B-bNQbsPnaMtZEisjuXDcHm9T0eju1L%2BnTDXcA%40mail.gmail.com.

Re: [weewx-user] Bootstrap skin update preview

[moth...@gmail.com]

Then I just wait until the latest version of python 3.7
Ton

Op zondag 21 februari 2021 om 22:26:20 UTC+1 schreef gjr80:

> The following error strongly suggests a python 2 only extension being run 
> under python 3:
>
> File "/var/tmp/fuzzy-archer-2.26/install.py", line 84
> print ""
>^
> SyntaxError: Missing parentheses in call to 'print'. Did you mean 
> print("")?
>
> You have two options; install/run WeeWX under python 2 and install the 
> extension or approach the author to upgrade the extension to python 3. 
> There is a third option, don’t install the extension, but that does not 
> really help.
>
> Gary
>
> On Monday, 22 February 2021 at 05:58:56 UTC+10 michael.k...@gmx.at wrote:
>
>>
>> Hi,
>> did you download a "Release"? This seems to be broken. If you want to 
>> download the latest "liveCharts" version, please got to 
>> https://github.com/brewster76/fuzzy-archer/tree/liveCharts and choose 
>> "Download Zip" after clicking the green "Code" button ind install this 
>> version.
>>
>> If you want wo download the latest non-live chart version, go to 
>> https://github.com/brewster76/fuzzy-archer and do the same. 
>>
>> The latest release doesn't seem to work with python3.
>> moth...@gmail.com schrieb am Sonntag, 21. Februar 2021 um 19:54:27 UTC+1:
>>
>>> Have also done an installation. Got these error messages. Use the latest 
>>> version of Weewx and Pyhthon. The original script does not work.
>>> Can't get it working on my system.
>>> This is a copy of the system log.
>>> pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@raspberrypi:~ $ sudo wee_extension 
>>> --install=/home/pi/Downloads/fuzzy-archer-2.26.tar.gz   
>>>
>>> Request to install '/home/pi/Downloads/fuzzy-archer-2.26.tar.gz'
>>> Extracting from tar archive /home/pi/Downloads/fuzzy-archer-2.26.tar.gz
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_extension", line 88, in 
>>> main()
>>>   File "/usr/share/weewx/wee_extension", line 80, in main
>>> ext.install_extension(options.install)
>>>   File "/usr/share/weewx/weecfg/extension.py", line 125, in 
>>> install_extension
>>> self.install_from_dir(extension_dir)
>>>   File "/usr/share/weewx/weecfg/extension.py", line 147, in 
>>> install_from_dir
>>> extension_dir)
>>>   File "/usr/share/weewx/weecfg/__init__.py", line 1866, in 
>>> get_extension_installer
>>> __import__('install')
>>>   File "/var/tmp/fuzzy-archer-2.26/install.py", line 84
>>> print ""
>>>^
>>> SyntaxError: Missing parentheses in call to 'print'. Did you mean 
>>> print("")?
>>> pi@raspberrypi:~ $ sudo wee_extension 
>>> --install=/home/pi/Downloads/fuzzy-archer-liveCharts.zip
>>> Request to install '/home/pi/Downloads/fuzzy-archer-liveCharts.zip'
>>> Extracting from zip archive 
>>> /home/pi/Downloads/fuzzy-archer-liveCharts.zip
>>>
>>> The following alternative languages are available:
>>>catala
>>>dutch
>>>espanol
>>>finnish
>>>francais
>>>german
>>>italian
>>>korean
>>>norwegian
>>>
>>> Language changes can be made in skins/Bootstrap/skin.conf
>>>
>>> Default location for HTML and image files is public_html/Bootstrap
>>> *** POINT YOUR BROWSER TO: public_html/Bootstrap/index.html ***
>>>
>>> Saving installer file to /usr/share/weewx/user/installer/bootstrap
>>> Saved configuration dictionary. Backup copy at 
>>> /etc/weewx/weewx.conf.20210221194236
>>> Finished installing extension 
>>> '/home/pi/Downloads/fuzzy-archer-liveCharts.zip'
>>> pi@raspberrypi:~ $ sudo /etc/init.d/weewx start
>>> [ ok ] Starting weewx (via systemctl): weewx.service.
>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Feb 21 19:43:27 raspberrypi weewx[23186] DEBUG weewx.drivers.vantage: 
>>> Gentle wake up of console successful
>>> Feb 21 19:43:27 raspberrypi weewx[23186] DEBUG weewx.drivers.vantage: 
>>> Retrieving 1 page(s); starting index= 3
>>> Feb 21 19:43:27 raspberrypi weewx[23186] INFO weewx.manager: Added 
>>> record 2021-02-21 19:40:00 CET (1613932800)   to 
>>> database 'weewx.sdb'
>>> Feb 21 19:43:27 raspberrypi weewx[23186] INFO weewx.manager: Added 
>>> record 2021-02-21 19:40:00 CET (1613932800)   to 
>>> daily summary in 'weewx.sdb'
>>> Feb 21 19:43:28 raspberrypi weewx[23186] DEBUG weewx.drivers.vantage: 
>>> DMPAFT complete: page timestamp 2021-02-1  2 
>>> 22:20:00 CET (1613164800) less than final timestamp 2021-02-21 19:40:00 CET 
>>> (1613932800)
>>> Feb 21 19:43:28 raspberrypi weewx[23186] DEBUG weewx.drivers.vantage: 
>>> Catch up complete.
>>> Feb 21 19:43:28 raspberrypi weewx[23186] INFO weewx.engine: Starting 
>>> main packet loop.
>>> Feb 21 19:43:28 raspberrypi weewx[23186] DEBUG weewx.drivers.vantage: 
>>> Gentle wake up of console successful
>>> Feb 21 19:43:28 raspberrypi weewx[23186] DEBUG weewx.drivers.vantage: 

Re: [weewx-user] ERROR weewx.drivers.vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead

[Tom Keffer]

You did not restart weewx, so the log does not show the startup sequence.

There could be another problem, but, at the minimum, it appears that the
memory in your logger is corrupt. See the section *WeeWX generates HTML
pages, but it does not update them
*
in
the wiki on how to clear the logger.

However, the symptoms are not quite classic. The timestamps in your logger
are quite old: over a year old. Usually, corrupt memory shows more recent
timestamps than that.

It's also still possible there is something else wrong. If clearing the
logger does not help, then post the log again, but this time make sure to
restart weewx and make sure the log includes that startup sequence.

-tk

On Mon, Feb 22, 2021 at 1:02 AM G400  wrote:

> Hi,
> About 30 min log is attached
>
> I see a lot of these errors:
>
> Feb 22 09:06:04 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage:
> LOOP try #1; error: Expected to read 99 chars; got 0 instead
> Feb 22 09:06:08 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage:
> LOOP try #2; error: Expected to read 99 chars; got 0 instead
> Feb 22 09:06:12 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage:
> LOOP try #3; error: Expected to read 99 chars; got 0 instead
> Feb 22 09:06:16 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage:
> LOOP try #4; error: Expected to read 99 chars; got 0 instead
> Feb 22 09:06:16 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage:
> LOOP max tries (4) exceeded.
> Feb 22 09:06:16 aad-raspberry-01 weewx[1286] INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Feb 22 09:06:16 aad-raspberry-01 weewx[1286] INFO weewx.engine: Shutting
> down StdReport thread
> Feb 22 09:06:16 aad-raspberry-01 weewx[1286] DEBUG weewx.engine: StdReport
> thread has been terminated
> Feb 22 09:06:16 aad-raspberry-01 weewx[1286] CRITICAL __main__: Caught
> WeeWxIOError: Max tries exceeded while getting LOOP data.
> Feb 22 09:06:16 aad-raspberry-01 weewx[1286] CRITICAL __main__: 
> Waiting 60 seconds then retrying...
> Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: retrying...
> Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: Using
> configuration file /etc/weewx/weewx.conf
> Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: Debug is 1
> Feb 22 09:07:16 aad
>
> --
> 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/ffc858e0-1827-44a2-8f17-6859d29064b4n%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/CAPq0zEBVt2x3DktBvTgW7F3UEnEq7frHv0QtrO3Q_-cYntEQXg%40mail.gmail.com.

[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am 
told they behave just like a console. First thing I would do is test 
connectivity from your RPi to the Envoy. Any chance the Envoy is now on a 
different USB port? Not sure if you remember the Establishing connectivity 
 
testing Tom got you to work through a couple of years back, but that is a 
good place to start. The instructions are now in the wiki rather than the 
User Guide but the link I have provided should work.

Gary
On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:

> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather system...
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx 
> version 4.4.0
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 2.7.13 
> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
> 'en_NZ.UTF-8'
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
> /var/run/weewx.pid
> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: 
> weewx.
> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system.
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing engine
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Driver 
> version is 3.2.1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Option 
> loop_request=1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Opened 
> up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
> #0 failed
> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
> #1 failed
> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
> #2 failed
> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
> #3 failed
> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: Unable 
> to wake up console
> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of 
> driver failed: Unable to wake up Vantage console ( 'weewx.WakeupError'>)
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
> Traceback (most recent call last):
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   self.console = loader_function(config_dict, self)
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   return VantageService(engine, config_dict)
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   self._setup()
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   self.port.wakeup_console(max_tries=self.max_tries)
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in 
> wakeup_console
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   raise weewx.WakeupError("Unable to wake up Vantage console")
> 

[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather system...
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx 
version 4.4.0
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 2.7.13 
(default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
Linux-4.19.66-v7+-armv7l-with-debian-9.13
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
'en_NZ.UTF-8'
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
/var/run/weewx.pid
Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: 
weewx.
Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system.
Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing engine
Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Driver 
version is 3.2.1
Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Option 
loop_request=1
Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Opened 
up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
#0 failed
Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
#1 failed
Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
#2 failed
Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
#3 failed
Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: Unable 
to wake up console
Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of driver 
failed: Unable to wake up Vantage console ()
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
Traceback (most recent call last):
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
return VantageService(engine, config_dict)
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
self._setup()
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
self.port.wakeup_console(max_tries=self.max_tries)
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in 
wakeup_console
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
raise weewx.WakeupError("Unable to wake up Vantage console")
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
WakeupError: Unable to wake up Vantage console
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL __main__: Unable to load 
driver: Unable to wake up Vantage console
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL __main__:   
Exiting...
Feb 22 22:39:20 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:20 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:27 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:27 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:35 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:35 WeatherPi dhcpcd[372]: wlan0: soliciting a 

Re: [weewx-user] ERROR weewx.drivers.vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead

[G400]

Hi,
About 30 min log is attached

I see a lot of these errors:

Feb 22 09:06:04 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: 
LOOP try #1; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:08 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: 
LOOP try #2; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:12 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: 
LOOP try #3; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: 
LOOP try #4; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: 
LOOP max tries (4) exceeded.
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] INFO weewx.engine: Main loop 
exiting. Shutting engine down.
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] INFO weewx.engine: Shutting 
down StdReport thread
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] DEBUG weewx.engine: StdReport 
thread has been terminated
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] CRITICAL __main__: Caught 
WeeWxIOError: Max tries exceeded while getting LOOP data.
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] CRITICAL __main__:   
Waiting 60 seconds then retrying...
Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: retrying...
Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: Using 
configuration file /etc/weewx/weewx.conf
Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: Debug is 1
Feb 22 09:07:16 aad

-- 
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/ffc858e0-1827-44a2-8f17-6859d29064b4n%40googlegroups.com.
<>

[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Hi,

We need to see the log from when you try starting WeeWX. Restart WeeWX and 
let it run for an archive period or two, then goto the log and take an 
extract from when WeeWX was restarted through until the two archive periods 
have passed. Post the log back here without alteration. It’s important you 
capture the full WeeWX startup.

Gary

On Monday, 22 February 2021 at 18:28:14 UTC+10 monmul wrote:

> My Davis system has been running really well for the last 2 years. Needed 
> no maintenance from me etc. Then the Envoy started tripping the circuit 
> fuse (I think it was the Envoy rather than the power chord as I replaced 
> with new Envoy and tripping stopped). I directly changed out the Envoy and 
> rebooted the system expecting that all would be back to normal. Nope!
>
> No data appears to be coming through:
>
> Here are my diagnostic so far:
>
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo weewxd
> pi@WeatherPi:~ $ ps -a
>   PID TTY  TIME CMD
> 15482 pts/100:00:00 ps
> pi@WeatherPi:~ $ kill -HUP 15482
> bash: kill: (15482) - No such process
> pi@WeatherPi:~ $ tail -f /var/log/syslog
> Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 21:17:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
>
> Any guidance would be much appreciated.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/66bf4f8c-7dc4-4b58-9702-299799f16eadn%40googlegroups.com.

[weewx-user] Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

My Davis system has been running really well for the last 2 years. Needed 
no maintenance from me etc. Then the Envoy started tripping the circuit 
fuse (I think it was the Envoy rather than the power chord as I replaced 
with new Envoy and tripping stopped). I directly changed out the Envoy and 
rebooted the system expecting that all would be back to normal. Nope!

No data appears to be coming through:

Here are my diagnostic so far:

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ sudo weewxd
pi@WeatherPi:~ $ ps -a
  PID TTY  TIME CMD
15482 pts/100:00:00 ps
pi@WeatherPi:~ $ kill -HUP 15482
bash: kill: (15482) - No such process
pi@WeatherPi:~ $ tail -f /var/log/syslog
Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 21:17:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1

Any guidance would be much appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/acc70090-16ae-4423-80e9-e992d6bc1910n%40googlegroups.com.