[weewx-user] Re: Data Issue

[Dave McCreath]

Gary

I'm afraid that you are right again, no, I didn't use sudo before issueing 
the 'dump' command, never mind too late now.

I hit Amazon this morning for a UPS, it should be here by the end of the 
coming week.  Maybe a bit of overkill but better to be safe (and angst 
free) rather than sorry.

Thank you again, very much appreciated.

Dave

On Saturday, 20 January 2018 14:07:27 UTC, gjr80 wrote:
>
> Dave,
>
> The lines similar to:
>
> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
> record 2018-01-18 17:45:00 GMT (1516297500) to database 'weewx.sdb': 
> attempt to write a readonly database
>
> indicate that data dumped from the logger by wee_device could not be 
> written to the database, that could be because the user account under which 
> wee_device was run did not have permission to write to the databse. Did 
> you use sudo in front of wee_device? If not that could be the reason. No 
> matter, that data was not written to database and the memory logger has 
> been cleared so it is no more.
>
> Everything else looks as it should. Corrupted station memory can occur as 
> a result of a power outage. If you are running hardware record generarion 
> (which most vantage users do) the symptoms you will see is that your web 
> pages will not be updating, ie data will stay as per a given date and time 
> (the last date-time in you archive which will probably be the record saved 
> immediately before the outage) and if you then look at the log you will see 
> very simialr to what you posted just now but the lines
>
> Jan 20 09:05:15 raspberrypi weewx[2517]: manager: Added record 2018-01-20 
> 09:05:00 GMT (1516439100) to database 'weewx.sdb'
> Jan 20 09:05:15 raspberrypi weewx[2517]: manager: Added record 2018-01-20 
> 09:05:00 GMT (1516439100) to daily summary in 'weewx.sdb'
>
>
> will be missing (they should occur every archive interval seconds). Of 
> course if you are using software record generation things will keep ticking 
> along and you will not notice the difference, the price you pay using 
> software record generation is that you loose the ability for the logger to 
> buffer your archive records and allow you to download historical 
> records/catchup in the event of an outage (well maybe not all outages given 
> your power outage experience :) )
>
>
> Gary
>
>
> On Saturday, 20 January 2018 19:24:35 UTC+10, Dave McCreath wrote:
>>
>> Gary
>>
>> Many, many thanks for getting back and pointing me in the right direction.
>>
>> Done as you suggested, stopped weeWx, changed config back to hardware, 
>> dumped (for clarity), then cleared the station memory and then restarted 
>> weeWx.
>>
>> All seems to now be OK but I've attached the log below just in case from 
>> just as the dump was finishing:
>>
>> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
>> record 2018-01-18 17:45:00 GMT (1516297500) to database 'weewx.sdb': 
>> attempt to write a readonly database
>>
>> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
>> record 2018-01-18 17:50:00 GMT (1516297800) to database 'weewx.sdb': 
>> attempt to write a readonly database
>>
>> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
>> record 2018-01-18 17:55:00 GMT (1516298100) to database 'weewx.sdb': 
>> attempt to write a readonly database
>>
>> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
>> record 2018-01-18 18:00:00 GMT (1516298400) to database 'weewx.sdb': 
>> attempt to write a readonly database
>>
>> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
>> record 2018-01-18 18:05:00 GMT (1516298700) to database 'weewx.sdb': 
>> attempt to write a readonly database
>>
>> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
>> record 2018-01-18 18:10:00 GMT (1516299000) to database 'weewx.sdb': 
>> attempt to write a readonly database
>>
>> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
>> record 2018-01-18 18:15:00 GMT (1516299300) to database 'weewx.sdb': 
>> attempt to write a readonly database
>>
>> Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add 
>> record 2018-01-18 18:20:00 GMT (1516299600) to database 'weewx.sdb': 
>> attempt to write a readonly database
>>
>> Jan 20 08:58:06 raspberrypi wee_device[2355]: vantage: Archive memory 
>> cleared.
>>
>> Jan 20 08:59:50 raspberrypi systemd[1]: Starting LSB: weewx weather 
>> system...
>>
>> Jan 20 08:59:50 raspberrypi weewx[2513]: engine: Initializing weewx 
>> version 

Re: [weewx-user] Re: Data Issue

[Dave McCreath]

Tom

About $90, but it'll also cover a Synology NAS plus the RPi and the Davis 
Vue console.

Dave

On Saturday, 20 January 2018 19:01:25 UTC, Tom Keffer wrote:
>
> I hit Amazon this morning for a UPS, it should be here by the end of the 
>> coming week.  Maybe a bit of overkill but better to be safe (and angst 
>> free) rather than sorry.
>>
>
> ​Not at all overkill. It's one of the keys to a stable system, 
> particularly with an RPi. 
>
> Because the Pi's don't draw much power​, the UPS does not have to be very 
> big or expensive. $50 should do it.
>
> -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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Data Issue

[Dave McCreath]

Gary

Many, many thanks for getting back and pointing me in the right direction.

Done as you suggested, stopped weeWx, changed config back to hardware, 
dumped (for clarity), then cleared the station memory and then restarted 
weeWx.

All seems to now be OK but I've attached the log below just in case from 
just as the dump was finishing:

Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add record 
2018-01-18 17:45:00 GMT (1516297500) to database 'weewx.sdb': attempt to 
write a readonly database

Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add record 
2018-01-18 17:50:00 GMT (1516297800) to database 'weewx.sdb': attempt to 
write a readonly database

Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add record 
2018-01-18 17:55:00 GMT (1516298100) to database 'weewx.sdb': attempt to 
write a readonly database

Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add record 
2018-01-18 18:00:00 GMT (1516298400) to database 'weewx.sdb': attempt to 
write a readonly database

Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add record 
2018-01-18 18:05:00 GMT (1516298700) to database 'weewx.sdb': attempt to 
write a readonly database

Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add record 
2018-01-18 18:10:00 GMT (1516299000) to database 'weewx.sdb': attempt to 
write a readonly database

Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add record 
2018-01-18 18:15:00 GMT (1516299300) to database 'weewx.sdb': attempt to 
write a readonly database

Jan 20 08:56:46 raspberrypi wee_device[2124]: manager: Unable to add record 
2018-01-18 18:20:00 GMT (1516299600) to database 'weewx.sdb': attempt to 
write a readonly database

Jan 20 08:58:06 raspberrypi wee_device[2355]: vantage: Archive memory 
cleared.

Jan 20 08:59:50 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...

Jan 20 08:59:50 raspberrypi weewx[2513]: engine: Initializing weewx version 
3.8.0

Jan 20 08:59:50 raspberrypi weewx[2513]: engine: Using Python 2.7.13 
(default, Nov 24 2017, 17:33:09) #012[GCC 6.3.0 20170516]

Jan 20 08:59:50 raspberrypi weewx[2513]: engine: Platform 
Linux-4.1.19-v7+-armv7l-with-debian-9.3

Jan 20 08:59:50 raspberrypi weewx[2513]: engine: Locale is 'en_GB.UTF-8'

Jan 20 08:59:50 raspberrypi weewx[2513]: engine: pid file is 
/var/run/weewx.pid

Jan 20 08:59:50 raspberrypi weewx[2517]: engine: Using configuration file 
/etc/weewx/weewx.conf

Jan 20 08:59:50 raspberrypi weewx[2517]: engine: debug is 1

Jan 20 08:59:50 raspberrypi weewx[2517]: engine: Initializing engine

Jan 20 08:59:50 raspberrypi weewx[2517]: engine: Loading station type 
Vantage (weewx.drivers.vantage)

Jan 20 08:59:50 raspberrypi weewx[2501]: Starting weewx weather system: 
weewx.

Jan 20 08:59:50 raspberrypi systemd[1]: Started LSB: weewx weather system.

Jan 20 08:59:50 raspberrypi weewx[2517]: vantage: Driver version is 3.0.10

Jan 20 08:59:51 raspberrypi weewx[2517]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 4.00

Jan 20 08:59:51 raspberrypi weewx[2517]: vantage: Gentle wake up of console 
successful

Jan 20 08:59:51 raspberrypi weewx[2517]: vantage: Hardware type is 17

Jan 20 08:59:51 raspberrypi weewx[2517]: vantage: Hardware name: Vantage Vue

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Loading service 
weewx.engine.StdTimeSynch

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Finished loading service 
weewx.engine.StdTimeSynch

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Loading service 
weewx.engine.StdConvert

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: StdConvert target unit is 
0x1

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Finished loading service 
weewx.engine.StdConvert

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Loading service 
weewx.engine.StdCalibrate

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Finished loading service 
weewx.engine.StdCalibrate

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Loading service 
weewx.engine.StdQC

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Finished loading service 
weewx.engine.StdQC

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Loading service 
weewx.wxservices.StdWXCalculate

Jan 20 08:59:51 raspberrypi weewx[2517]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware

Jan 20 08:59:51 raspberrypi weewx[2517]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS

Jan 20 08:59:51 raspberrypi weewx[2517]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate

Jan 20 08:59:51 

[weewx-user] Data Issue

[Dave McCreath]

Good Evening All, please excuse this Noob!

In a bit of a pickle, I've got a Vantage Vue that has been working fine 
over the past two years, data ported through to WU via a Rpi (using the 
Debian Stretch).  Weewx is up to date (v 3.8.0).

Had a power cut this evening for a couple of hours, when the power came 
back on weeWx pulled a record from the Vue and published it (the record 
data was erroneous), after this, nothing.

Having recently upgraded to Stretch from Jessie I then switched back to 
Jessie (changed SD card) and in the syslog I saw that weeWx pulled and 
published two day's worth of records from the Vue (switched to Stretch two 
days ago) up until the time of the erroneous record (that was generated 
just after the power came back up).

I tried resetting the Vue (logger issue?) to no avail, same issue occurred. 
So switched back to Stretch and the issue was still there.

Went into the weeWx.conf file and changed the record_generation from 
'hardware' to 'software' (archive service generation) and now all is 
working fine!

Does anyone have an idea of what's gone wrong and what are the implications 
of switching from hardware to software in the longer term?

Many thanks

Dave

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx and Wunderground - Recent Data Issue

[Dave McCreath]

Eqpt:

Vantage Vue on USB with datalogger.
Debian 9.4 on a Raspberry Pi (updated and upgraded as of two weeks ago).
weewx v.3.8.2.
Wunderfixer running as a cron task every 60 minutes (at the moment).
WunderGround ID ICAMBSLE2 (which has been running well for over three 
years).

Issue:  

weewx uploads data packets to Wundergound every five minutes but less than 
half appear to get through first time.  Those that do get through first 
time do not appear on the Wundergound GUI until 6/7 minutes after being 
uploaded.  Previously, they would appear within 2 minutes of uploading.  
However, with Wunderfixer (currently) running every hour, data records are 
eventually getting through to the server after about two and a half hours 
(sometimes three).  Local data is being saved to my personal weewx website 
without any issues. 

Background:  

The issue first appeared at roughly 1400hrs GMT on Mon 29 Oct (day after 
the clocks changed!).  I initially thought it might be a timing issue post 
the clocks changing, but checking the records for Sunday 28 Oct, all was 
fine.  Checked the epoch time on the RPi and Davis console, both OK.  
Strangely, If I turn on rapid-fire (via .conf), all works as it should do, 
no issues whatsoever.

Log Extract: (No issues as far as I can see)

Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
15:55:00 GMT (1542038100) to database 'weewx.sdb'
Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
15:55:00 GMT (1542038100) to daily summary in 'weewx.sdb'
Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running reports for latest 
time in the database.
Nov 12 15:55:15 weewx weewx[4781]: vantage: Requesting 200 LOOP packets.
Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running report 
StandardReport
Nov 12 15:55:15 weewx weewx[4781]: vantage: Gentle wake up of console 
successful
Nov 12 15:55:15 weewx weewx[4781]: reportengine: Found configuration file 
/etc/weewx/skins/Standard/skin.conf for report StandardReport
Nov 12 15:55:15 weewx weewx[4781]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Nov 12 15:55:15 weewx weewx[4781]: manager: Daily summary version is 2.0
Nov 12 15:55:16 weewx weewx[4781]: restx: Wunderground-PWS: Published 
record 2018-11-12 15:55:00 GMT (1542038100)
Nov 12 15:55:17 weewx weewx[4781]: cheetahgenerator: Generated 14 files for 
report StandardReport in 1.46 seconds
Nov 12 15:55:17 weewx weewx[4781]: manager: Daily summary version is 2.0
Nov 12 15:55:18 weewx weewx[4781]: imagegenerator: Generated 12 images for 
StandardReport in 0.90 seconds
Nov 12 15:55:18 weewx weewx[4781]: copygenerator: copied 0 files to 
/var/www/html/weewx
Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report FTP
Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file 
/etc/weewx/skins/Ftp/skin.conf for report FTP
Nov 12 15:55:18 weewx weewx[4781]: ftpgenerator: FTP upload not requested. 
Skipped.
Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report RSYNC
Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file 
/etc/weewx/skins/Rsync/skin.conf for report RSYNC
Nov 12 15:55:18 weewx weewx[4781]: rsyncgenerator: rsync upload not 
requested. Skipped.
Nov 12 15:59:01 weewx CRON[9215]: (pi) CMD (wunderfixer --log weewx)
Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using weewx configuration 
file /etc/weewx/weewx.conf.
Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using database binding 
'wx_binding', which is bound to database 'archive_sqlite'
Nov 12 15:59:02 weewx weewx[9216]: wunderfixer: 25 Weather Underground 
records missing.
Nov 12 15:59:13 weewx weewx[9216]: wunderfixer: 25 out of 25 missing 
records published to 'ICAMBSLE2' for date 2018-11-12. Wunderfixer exiting.

WunderGround Web Page:

[image: WeeWx Issue.jpg]
 Anyone any ideas?

Regards

Dave

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx and Wunderground, Recent Issue

[Dave McCreath]

Vantage Vue on USB with datalogger.
Debian 9.4 on a Raspberry Pi (updated and upgraded as of two weeks ago).
weewx v.3.8.2.
Wunderfixer running as a cron task every 60 minutes (at the moment).
WunderGround ID ICAMBSLE2 (which has been running well for over three 
years).

Issue:  weewx uploads data packets to Wundergound every five minutes but 
less than half appear to get through first time.  Those that do get through 
first time do not appear on the Wundergound GUI until 6/7 minutes after 
being uploaded.  Previously, they would appear within 2 minutes of 
uploading.  However, with Wunderfixer (currently) running every hour, data 
records are eventually getting through to the server after about two and a 
half hours (sometimes three).  Local data is being saved to my personal 
weewx website without any issues. 

Background:  Issue first appeared at roughly 1400hrs GMT on Mon 29 Oct (day 
after the clocks changed!).  I initially thought it might be a timing issue 
post the clocks changing, but checking the records for Sunday 28 Oct, all 
was fine.  Checked the time on the RPi and Davis console, both OK.  
Strangely, If I turn on rapid-fire (via .conf file), all works as it should 
do, no issues whatsoever.

Anyone any ideas?

[image: WeeWx Issue.jpg] 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] weewx and Wunderground - Recent Data Issue

[Dave McCreath]

Thomas

Many thanks for getting back to me, no surprize there then!

I'll leave the system on rapid-fire for another couple of weeks and try 
again, but I do like the way weewx aggregates data over a five minute 
period before uploading unlike rapid fire.

Kind regards

Dave

On Monday, 12 November 2018 21:54:12 UTC, Thomas Keffer wrote:
>
> Dave, unfortunately, the WU is full of many, many bugs. Looks like you 
> stumbled across another one. There's not much we can do about them from our 
> end.
>
> -tk
>
> On Mon, Nov 12, 2018 at 9:15 AM Dave McCreath  > wrote:
>
>> Eqpt:
>>
>> Vantage Vue on USB with datalogger.
>> Debian 9.4 on a Raspberry Pi (updated and upgraded as of two weeks ago).
>> weewx v.3.8.2.
>> Wunderfixer running as a cron task every 60 minutes (at the moment).
>> WunderGround ID ICAMBSLE2 (which has been running well for over three 
>> years).
>>
>> Issue:  
>>
>> weewx uploads data packets to Wundergound every five minutes but less 
>> than half appear to get through first time.  Those that do get through 
>> first time do not appear on the Wundergound GUI until 6/7 minutes after 
>> being uploaded.  Previously, they would appear within 2 minutes of 
>> uploading.  However, with Wunderfixer (currently) running every hour, data 
>> records are eventually getting through to the server after about two and a 
>> half hours (sometimes three).  Local data is being saved to my personal 
>> weewx website without any issues. 
>>
>> Background:  
>>
>> The issue first appeared at roughly 1400hrs GMT on Mon 29 Oct (day after 
>> the clocks changed!).  I initially thought it might be a timing issue post 
>> the clocks changing, but checking the records for Sunday 28 Oct, all was 
>> fine.  Checked the epoch time on the RPi and Davis console, both OK.  
>> Strangely, If I turn on rapid-fire (via .conf), all works as it should do, 
>> no issues whatsoever.
>>
>> Log Extract: (No issues as far as I can see)
>>
>> Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
>> 15:55:00 GMT (1542038100) to database 'weewx.sdb'
>> Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
>> 15:55:00 GMT (1542038100) to daily summary in 'weewx.sdb'
>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running reports for 
>> latest time in the database.
>> Nov 12 15:55:15 weewx weewx[4781]: vantage: Requesting 200 LOOP packets.
>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running report 
>> StandardReport
>> Nov 12 15:55:15 weewx weewx[4781]: vantage: Gentle wake up of console 
>> successful
>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Found configuration file 
>> /etc/weewx/skins/Standard/skin.conf for report StandardReport
>> Nov 12 15:55:15 weewx weewx[4781]: cheetahgenerator: using search list 
>> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
>> Nov 12 15:55:15 weewx weewx[4781]: manager: Daily summary version is 2.0
>> Nov 12 15:55:16 weewx weewx[4781]: restx: Wunderground-PWS: Published 
>> record 2018-11-12 15:55:00 GMT (1542038100)
>> Nov 12 15:55:17 weewx weewx[4781]: cheetahgenerator: Generated 14 files 
>> for report StandardReport in 1.46 seconds
>> Nov 12 15:55:17 weewx weewx[4781]: manager: Daily summary version is 2.0
>> Nov 12 15:55:18 weewx weewx[4781]: imagegenerator: Generated 12 images 
>> for StandardReport in 0.90 seconds
>> Nov 12 15:55:18 weewx weewx[4781]: copygenerator: copied 0 files to 
>> /var/www/html/weewx
>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report FTP
>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file 
>> /etc/weewx/skins/Ftp/skin.conf for report FTP
>> Nov 12 15:55:18 weewx weewx[4781]: ftpgenerator: FTP upload not 
>> requested. Skipped.
>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report RSYNC
>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file 
>> /etc/weewx/skins/Rsync/skin.conf for report RSYNC
>> Nov 12 15:55:18 weewx weewx[4781]: rsyncgenerator: rsync upload not 
>> requested. Skipped.
>> Nov 12 15:59:01 weewx CRON[9215]: (pi) CMD (wunderfixer --log weewx)
>> Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using weewx configuration 
>> file /etc/weewx/weewx.conf.
>> Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using database binding 
>> 'wx_binding', which is bound to database 'archive_sqlite'
>> Nov 12 15:59:02 weew

[weewx-user] Re: Installing WeatherCloud Extension - Error

[Dave McCreath]

Thanks you.

On Tuesday, 2 April 2019 17:48:54 UTC+1, mwall wrote:
>
> On Monday, April 1, 2019 at 5:29:31 AM UTC-4, Dave McCreath wrote:
>>
>> Thanks for getting back to me.  Looks like the link is down so unable to 
>> download it!
>>
>
> the server is back online now 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Installing WeatherCloud Extension - Error

[Dave McCreath]

Perfect, thanks.  It worked!

On Tuesday, 2 April 2019 04:03:58 UTC+1, Chotechai Piyavongsiri wrote:
>
> It is v.0.11 (know by peeking inside the tar file)
>
> On Tuesday, 2 April 2019 10:02:35 UTC+7, Chotechai Piyavongsiri wrote:
>>
>> Here it is. Not sure what version it is.
>>
>> On Monday, 1 April 2019 16:45:15 UTC+7, Dave McCreath wrote:
>>>
>>> Has anyone got a copy of the tarball?
>>>
>>> Just asking, you never know.
>>>
>>> Dave
>>>
>>> On Monday, 1 April 2019 10:29:31 UTC+1, Dave McCreath wrote:
>>>>
>>>> Thanks for getting back to me.  Looks like the link is down so unable 
>>>> to download it!
>>>>
>>>> Regards
>>>>
>>>> Dave
>>>>
>>>> On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> You need to replace x.y in the command you are using to install with 
>>>>> the version number in the install file you downloaded. The current 
>>>>> version 
>>>>> appears to be 0.11 so try:
>>>>>
>>>>> $ wee_extension --install weewx-wcloud-0.11.tgz
>>>>>
>>>>> Using x.y or x.y.z is a common shorthand used to indicate you need to 
>>>>> replace the letters with the version you are using. Saves a bit of work 
>>>>> continually updating (and may be getting them out of date) instructions.
>>>>>
>>>>> Gary
>>>>>
>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Installing WeatherCloud Extension - Error

[Dave McCreath]

Getting a tad fed up with Wunderground and trying to move over to 
WeatherCloud.

I have weeWX installed and running and updated on a Raspberry Pi currently 
uploading to Wunderground, no issues.

I followed the instructions on the WeatherCloud site to install alongside 
weeWX (here ) but after trying to 
install the file on my RPi I get the following error:

pi@weewx:~ $ wee_extension --install weewx-wcloud-x.y.tgz
Request to install 'weewx-wcloud-x.y.tgz'
Traceback (most recent call last):
  File "/usr/bin/wee_extension", line 83, in 
main()
  File "/usr/bin/wee_extension", line 75, in main
ext.install_extension(options.install)
  File "/usr/share/weewx/weecfg/extension.py", line 124, in 
install_extension
raise InstallError("Extension '%s' not found." % extension_path)
weecfg.extension.InstallError: Extension 'weewx-wcloud-x.y.tgz' not found.

Anyone got an idea of how to overcome the installation error, I am no 
expert on 'things' LINUX?

Dave

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Installing WeatherCloud Extension - Error

[Dave McCreath]

Thanks for getting back to me.  Looks like the link is down so unable to 
download it!

Regards

Dave

On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:
>
> Hi,
>
> You need to replace x.y in the command you are using to install with the 
> version number in the install file you downloaded. The current version 
> appears to be 0.11 so try:
>
> $ wee_extension --install weewx-wcloud-0.11.tgz
>
> Using x.y or x.y.z is a common shorthand used to indicate you need to 
> replace the letters with the version you are using. Saves a bit of work 
> continually updating (and may be getting them out of date) instructions.
>
> Gary
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Installing WeatherCloud Extension - Error

[Dave McCreath]

Has anyone got a copy of the tarball?

Just asking, you never know.

Dave

On Monday, 1 April 2019 10:29:31 UTC+1, Dave McCreath wrote:
>
> Thanks for getting back to me.  Looks like the link is down so unable to 
> download it!
>
> Regards
>
> Dave
>
> On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:
>>
>> Hi,
>>
>> You need to replace x.y in the command you are using to install with the 
>> version number in the install file you downloaded. The current version 
>> appears to be 0.11 so try:
>>
>> $ wee_extension --install weewx-wcloud-0.11.tgz
>>
>> Using x.y or x.y.z is a common shorthand used to indicate you need to 
>> replace the letters with the version you are using. Saves a bit of work 
>> continually updating (and may be getting them out of date) instructions.
>>
>> Gary
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Weewx Down?

[Dave McCreath]

Tom

Many thanks, all done now.

Dave

On Saturday, 17 August 2019 15:01:03 UTC+1, Thomas Keffer wrote:
>
> Back up.
>
> Problem was an unattended upgrade, which crashed the webserver.
>
> -tk
>
> On Sat, Aug 17, 2019 at 6:37 AM Dave McCreath  > wrote:
>
>> Just tried installing weeWx on a new RPI.  Looks like www,weewx.com is 
>> temporarily off-line.
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/a230d99f-2e2c-4330-9933-b892ffdec79f%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/a230d99f-2e2c-4330-9933-b892ffdec79f%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/bd6bc351-fb50-4639-8fd4-fcdb2ef30b6a%40googlegroups.com.

[weewx-user] Weewx Down?

[Dave McCreath]

Just tried installing weeWx on a new RPI.  Looks like www,weewx.com is 
temporarily off-line.

-- 
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/a230d99f-2e2c-4330-9933-b892ffdec79f%40googlegroups.com.

Re: [weewx-user] Re: rtupdate.wunderground.com certificate error

[Dave McCreath]

Leon

The text below was posted by Tim Roche (WU IT) on the WeatherUndergound 
FaceBook page 17 hours ago:

*Quick update: We have some answers for why many of the stations are not 
sending data. It appears that many of the embedded device controllers don't 
behave very well with host names, and are sending data to us in a way that 
is not expected.*

*We love that enthusiasts building cool stuff send data to Weather 
Underground, so while we asses how to fix these issues, we have temporarily 
rolled back to our legacy system.*

*We will be testing over the next week to see how to fix these problems, 
and will ask for help from some of you.*

*I would like to personally apologize for this issue, we felt our testing 
was robust, but obviously there were gaps. We're still working on a plan 
and I will try to keep you updated here.*


Tim is a regular poster on the site and it's a good source of what's going 
on.


I think the time coincides with everything correcting itself on your system


Regards


Dave

On Wednesday, 5 February 2020 16:42:53 UTC, Leon Shaner wrote:
>
> FWIW, I haven't seen any 404's since around these times from last night:
>
> Feb  4 20:43:52 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: 
> Not Found
> Feb  4 20:43:52 Wunderground-RF: Failed to publish record 2020-02-04 
> 20:43:53 EST (1580867033): Failed upload after 1 tries
> Feb  4 20:49:10 Wunderground-RF: Failed upload attempt 1:  _ssl.c:1039: The handshake operation timed out>
> Feb  4 20:49:10 Wunderground-RF: Failed to publish record 2020-02-04 
> 20:48:49 EST (1580867329): Failed upload after 1 tries
> Feb  4 20:49:45 Wunderground-RF: Failed upload attempt 1:  timed out>
> Feb  4 20:49:45 Wunderground-RF: Failed to publish record 2020-02-04 
> 20:49:15 EST (1580867355): Failed upload after 1 tries
> Feb  4 20:50:19 Wunderground-RF: Failed upload attempt 1:  timed out>
> Feb  4 20:50:19 Wunderground-RF: Failed to publish record 2020-02-04 
> 20:49:49 EST (1580867389): Failed upload after 1 tries
> Feb  4 21:04:41 Wunderground-RF: Failed upload attempt 1:  [Errno 104] Connection reset by peer>
> Feb  4 21:04:41 Wunderground-RF: Failed to publish record 2020-02-04 
> 21:04:41 EST (1580868281): Failed upload after 1 tries
> Feb  4 21:04:44 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: 
> Not Found
>
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
>
>>

-- 
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/77bd16db-0eed-4598-94ea-f7ca3a0dc945%40googlegroups.com.

[weewx-user] Re: rtupdate.wunderground.com certificate error

[Dave McCreath]

Snap! 

SSL Certificate issue resolved but data still not being accepted via https.

Webcam updates are getting through.

-- 
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/8de64d9b-b4f6-4080-b217-5f106f3d0dbc%40googlegroups.com.

[weewx-user] Re: rtupdate.wunderground.com certificate error

[Dave McCreath]

Spoke too soon.

SSL Certificate error went away last night, still failed to upload (on 
third error), now back to SSL Certificate error again!

Jan 31 10:50:27 raspberrypi weewx[545]: restx: Wunderground-PWS: Thread 
exiting. Reason: hostname 'weatherstation.wunderground.com' doesn't match 
either of 
'*.prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud',
 
'prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud',
 
'prod-pws-ng-546567.us-south.containers.appdomain.cloud'

Bummer.

-- 
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/730af4c4-6fea-446f-ac0a-3ef112d65739%40googlegroups.com.

[weewx-user] Re: rtupdate.wunderground.com certificate error

[Dave McCreath]

JB

Many thanks for pointing me in the direction of the fix, applied (at line 
61) and it appears to be working fine after a reboot. 

A quick query on Verion 4.xx of weewx for those Linux savvy bodies amongst 
us, how easy is it to install on an RPi and is an undated version of 
Wunderfixer included (that works)?

Regards

Dave


On Monday, 3 February 2020 05:18:22 UTC, J B wrote:
>
> I should mention that I'm assuming that this workaround doesn't turn off 
> certificate validation system-wide but I'm not well-versed enough in how 
> this works to know for sure. Since the daemons are managed by root I guess 
> it's possible.
>
> On Sunday, February 2, 2020 at 9:14:24 PM UTC-8, J B wrote:
>>
>> Like some of you I'm still getting intermittent errors that stop weewx 
>> 3.9.2 from uploading until I restart. Someone over at 
>> https://apicommunity.wunderground.com/ posted this creative 
>> workaround that seems to be working so far. It lowers the security of 
>> python but it's better than sending everything over http.
>>
>> tmarschner 
>> 
>>
>>- 2 Posts 
>>-  0 Reply Likes
>>
>> Hi there,
>>
>> Here's an alternative workaround that doesn't require you to send your 
>> Wunderground credentials in clear text. It turns off certificate validation 
>> for python. I've tested this on weewx 3.9.2 on a Raspberry Pi (v. 9 
>> Stretch) running python 2.7.13.
>>
>> Modify the weewx startup script /etc/init.d/weewx.
>>
>> Find the start-stop-daemon line that starts up weewx (the do_start 
>> routine) and insert "/usr/bin/env PYTHONHTTPSVERIFY=0" into the --exec 
>> parameter as shown below:
>>
>> start-stop-daemon --start --chuid $WEEWX_USER --pidfile $PIDFILE --exec 
>> /usr/bin/env PYTHONHTTPSVERIFY=0 $DAEMON -- $DAEMON_ARGS || return 2
>>
>> Cheers,
>> Tom
>>
>

-- 
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/6c5defed-ad97-44ed-aac7-9ad27bea8058%40googlegroups.com.

[weewx-user] Re: rtupdate.wunderground.com certificate error

[Dave McCreath]

Looks like WU are onto this, see attached from 
apicommunity.wunderground.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/5629582a-dfe1-4f7a-9e36-500b600498c7%40googlegroups.com.

[weewx-user] Wunderfixer - Crontask

[Dave McCreath]

Hi All

Bit of advice please for a noob.

Running Weewx on an RPi 4, Raspian 10 (Buster) and recently upgraded to v4 
from v3.

I was aware that Wunderfixer stopped working some time ago in v3 (unless 
you were a Linux guru, which I'm not) due to api issues.

Now that I have upgraded to v4, all is working fine and using Wunderfixer 
now works direct from the command line as it should having inserted my api 
into the config file. 

However, I now wish to go back to running Wunderfixer as a Crontask twice a 
day as recommended in the Wunderfixer instructionsat 1158hrs and 2358hrs.

I have inserted the Crontask (via crontab -e) instructions as per those 
shown in the Wunderfixer instructions but with log options enabled:

16 13 * * * /home/weewx/bin/wunderfixer -v


>From the log I get the following message:

>From pi@raspberrypi  Mon Jul 20 13:16:01 2020
Return-Path: 
X-Original-To: pi
Delivered-To: pi@raspberrypi
Received: by raspberrypi (Postfix, from userid 1000)
id ABD598021A; Mon, 20 Jul 2020 13:16:01 +0100 (BST)
From: root@raspberrypi (Cron Daemon)
To: pi@raspberrypi
Subject: Cron  /home/weewx/bin/wunderfixer -v
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Cron-Env: 
X-Cron-Env: 
X-Cron-Env: 
X-Cron-Env: 
Message-Id: <20200720121601.ABD598021A@raspberrypi>
Date: Mon, 20 Jul 2020 13:16:01 +0100 (BST)

/bin/sh: 1: /home/weewx/bin/wunderfixer: not found

Not sure that I'm pointing the crontask to the correct location, weewx for 
me is installed in /etc/weewx, not /home/weewx, and my weewx directory does 
not have a /bin sub directory, in fact I've no idea where wunderfixer is 
actually running from!

Can anyone point me in the right direction as to where I should direct the 
crontask to or have an example to hand that I can use.

Thank you

Dave

-- 
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/41e20a45-1645-44d3-9a1b-76fbe1edf3f3o%40googlegroups.com.

RE: [weewx-user] Re: RPi WeeWx Python 3.7 Issue

[Dave McCreath]

Tom

 

Hi.

 

Yep, mine is the same as yours:

 

[ 4689.183852] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0

[ 4689.183939] cp210x 1-1.4:1.0: device disconnected

[ 4689.633565] usb 1-1.4: new full-speed USB device number 5 using xhci_hcd

[ 4692.803586] usb 1-1.4: new full-speed USB device number 6 using xhci_hcd

[ 4692.938998] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00

[ 4692.939011] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[ 4692.939021] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller

[ 4692.939031] usb 1-1.4: Manufacturer: Silicon Labs

[ 4692.939040] usb 1-1.4: SerialNumber: 0001

[ 4692.946665] cp210x 1-1.4:1.0: cp210x converter detected

[ 4692.952907] usb 1-1.4: cp210x converter now attached to ttyUSB0

[ 4693.217302] usb 1-1.4: USB disconnect, device number 6

[ 4693.217689] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0

[ 4693.217742] cp210x 1-1.4:1.0: device disconnected

[ 4693.513548] usb 1-1.4: new full-speed USB device number 7 using xhci_hcd

[ 4693.648964] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00

[ 4693.648972] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[ 4693.648979] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller

[ 4693.648986] usb 1-1.4: Manufacturer: Silicon Labs

[ 4693.648992] usb 1-1.4: SerialNumber: 0001

[ 4693.652553] cp210x 1-1.4:1.0: cp210x converter detected

[ 4693.657075] usb 1-1.4: cp210x converter now attached to ttyUSB0

pi@raspberrypi:~ $

 

Regards

 

Dave

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: 22 April 2021 01:07
To: weewx-user 
Subject: Re: [weewx-user] Re: RPi WeeWx Python 3.7 Issue

 

Do you have a device /dev/ttyUSB0? That's normally where a Vantage shows up in 
the device directory, but not always. 

 

The most reliable way to find out where the Vantage ended up is to unplug it, 
plug it in again, then type 'dmesg'. This will look something like:

 

dmesg

[14818.699217] usb 2-2.1: USB disconnect, device number 4
[14818.699660] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[14818.699710] pl2303 2-2.1:1.0: device disconnected
[14820.731608] usb 2-2.1: new full-speed USB device number 10 using xhci_hcd
[14820.844750] usb 2-2.1: New USB device found, idVendor=05ad, idProduct=0fba, 
bcdDevice= 3.00
[14820.844756] usb 2-2.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[14820.844759] usb 2-2.1: Product: USB-Serial Controller
[14820.844761] usb 2-2.1: Manufacturer: Prolific Technology Inc.
[14820.852720] pl2303 2-2.1:1.0: pl2303 converter detected
[14820.856368] usb 2-2.1: pl2303 converter now attached to ttyUSB0

 

In my case, the serial-to-usb converter showed up at /dev/ttyUSB0, but your 
results may differ.

 

-tk

 

On Wed, Apr 21, 2021 at 4:34 PM Dave McCreath mailto:dave.mccre...@gmail.com> > wrote:

Forgot to add.

 

Now running 4.5.1 from a backup SD card and all is currently well but does not 
look like I'll be able to update/upgrade the RPi until I figure out what's 
wrong.

 

Regards

 

Dave

On Thursday, 22 April 2021 at 00:08:18 UTC+1 Dave McCreath wrote:

Good Evening Venerable Experts

 

Earlier on today I updated my RPi (sudu apt-get update && sudo apt-get 
upgrade).  On rebooting WeeWx failed to start, this was post an upgrade from 
4.2 to 4.5.1. (I have WeeWx added to the sources list)

 

So, being savvy, rebooted from a backup sd card to bring the system back to 
where it was prior to the update/upgrade and WeeWx version 4.2.

 

I then went about updating/upgrading WeeWx from 4.2 to 4.5 (sudo apt-get 
install weewx), that went fine, rebooted and WeeWx ran without any issues post 
the upgrade.

 

Next I then tried sudu apt-get update && sudo apt-get upgrade again.  Post a 
reboot, exactly the same issue as before, WeeWx would not start:

 

pi@raspberrypi:~ $ service weewx status

● weewx.service - LSB: weewx weather system

   Loaded: loaded (/etc/init.d/weewx; generated)

   Active: active (exited) since Wed 2021-04-21 23:48:06 BST; 2min 28s ago

 Docs: man:systemd-sysv-generator(8)

  Process: 338 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS)

 

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine: 
  self.port.openPort()

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 308, in openPort

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine: 
  self.serial_port = serial.Serial(self.port, self.baudrate, 
timeout=self.timeout)

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine: 
File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, 
in __init__

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITI

[weewx-user] Re: RPi WeeWx Python 3.7 Issue

[Dave McCreath]

Forgot to add.

Now running 4.5.1 from a backup SD card and all is currently well but does 
not look like I'll be able to update/upgrade the RPi until I figure out 
what's wrong.

Regards

Dave

On Thursday, 22 April 2021 at 00:08:18 UTC+1 Dave McCreath wrote:

> Good Evening Venerable Experts
>
> Earlier on today I updated my RPi (sudu apt-get update && sudo apt-get 
> upgrade).  On rebooting WeeWx failed to start, this was post an upgrade 
> from 4.2 to 4.5.1. (I have WeeWx added to the sources list)
>
> So, being savvy, rebooted from a backup sd card to bring the system back 
> to where it was prior to the update/upgrade and WeeWx version 4.2.
>
> I then went about updating/upgrading WeeWx from 4.2 to 4.5 (sudo apt-get 
> install weewx), that went fine, rebooted and WeeWx ran without any issues 
> post the upgrade.
>
> Next I then tried sudu apt-get update && sudo apt-get upgrade again.  Post 
> a reboot, exactly the same issue as before, WeeWx would not start:
>
> pi@raspberrypi:~ $ service weewx status
>
> ● weewx.service - LSB: weewx weather system
>
>Loaded: loaded (/etc/init.d/weewx; generated)
>
>Active: active (exited) since Wed 2021-04-21 23:48:06 BST; 2min 28s ago
>
>  Docs: man:systemd-sysv-generator(8)
>
>   Process: 338 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS)
>
>  
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> weewx.engine:   self.port.openPort()
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py", 
> line 308, in openPort
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> weewx.engine:   self.serial_port = serial.Serial(self.port, 
> self.baudrate, timeout=self.timeout)
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> weewx.engine: File 
> "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in __init__
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> weewx.engine:   self.open()
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> weewx.engine: File 
> "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in open
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> weewx.engine:   raise SerialException(msg.errno, "could not 
> open port {}: {}".format(self._port, msg))
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> weewx.engine:   serial.serialutil.SerialException: [Errno 2] could 
> not open port /dev/ttyUSB0: [Errno 2] No such file or directory: 
> '/dev/ttyUSB0'
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL __main__: 
> Unable to load driver: [Errno 2] could not open port /dev/ttyUSB0: [Errno 
> 2] No such file or directory: '/dev/ttyUSB0'
>
> Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
> __main__:   Exiting...
>
>
> Any ideas?
>

-- 
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/27e48fc1-8ea2-44c7-bdaa-73cfb1c15dcen%40googlegroups.com.

Re: [weewx-user] Re: RPi WeeWx Python 3.7 Issue

[Dave McCreath]

Tom

Please be aware that my answer is for the current working system, not the 
one that was broken.

I can try the RPi upgrade again and see if the file is located within the 
devices directory?

Dave

On Thursday, 22 April 2021 at 01:14:53 UTC+1 Dave McCreath wrote:

> Tom
>
>  
>
> Hi.
>
>  
>
> Yep, mine is the same as yours:
>
>  
>
> [ 4689.183852] cp210x ttyUSB0: cp210x converter now disconnected from 
> ttyUSB0
>
> [ 4689.183939] cp210x 1-1.4:1.0: device disconnected
>
> [ 4689.633565] usb 1-1.4: new full-speed USB device number 5 using xhci_hcd
>
> [ 4692.803586] usb 1-1.4: new full-speed USB device number 6 using xhci_hcd
>
> [ 4692.938998] usb 1-1.4: New USB device found, idVendor=10c4, 
> idProduct=ea60, bcdDevice= 1.00
>
> [ 4692.939011] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
>
> [ 4692.939021] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller
>
> [ 4692.939031] usb 1-1.4: Manufacturer: Silicon Labs
>
> [ 4692.939040] usb 1-1.4: SerialNumber: 0001
>
> [ 4692.946665] cp210x 1-1.4:1.0: cp210x converter detected
>
> [ 4692.952907] usb 1-1.4: cp210x converter now attached to ttyUSB0
>
> [ 4693.217302] usb 1-1.4: USB disconnect, device number 6
>
> [ 4693.217689] cp210x ttyUSB0: cp210x converter now disconnected from 
> ttyUSB0
>
> [ 4693.217742] cp210x 1-1.4:1.0: device disconnected
>
> [ 4693.513548] usb 1-1.4: new full-speed USB device number 7 using xhci_hcd
>
> [ 4693.648964] usb 1-1.4: New USB device found, idVendor=10c4, 
> idProduct=ea60, bcdDevice= 1.00
>
> [ 4693.648972] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
>
> [ 4693.648979] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller
>
> [ 4693.648986] usb 1-1.4: Manufacturer: Silicon Labs
>
> [ 4693.648992] usb 1-1.4: SerialNumber: 0001
>
> [ 4693.652553] cp210x 1-1.4:1.0: cp210x converter detected
>
> [ 4693.657075] usb 1-1.4: cp210x converter now attached to ttyUSB0
>
> pi@raspberrypi:~ $
>
>  
>
> Regards
>
>  
>
> Dave
>
>  
>
> *From:* weewx...@googlegroups.com  *On Behalf 
> Of *Tom Keffer
> *Sent:* 22 April 2021 01:07
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: RPi WeeWx Python 3.7 Issue
>
>  
>
> Do you have a device /dev/ttyUSB0? That's normally where a Vantage shows 
> up in the device directory, but not always. 
>
>  
>
> The most reliable way to find out where the Vantage ended up is to unplug 
> it, plug it in again, then type 'dmesg'. This will look something like:
>
>  
>
> *dmesg*
>
> [14818.699217] usb 2-2.1: USB disconnect, device number 4
> [14818.699660] pl2303 ttyUSB0: pl2303 converter now disconnected from 
> ttyUSB0
> [14818.699710] pl2303 2-2.1:1.0: device disconnected
> [14820.731608] usb 2-2.1: new full-speed USB device number 10 using 
> xhci_hcd
> [14820.844750] usb 2-2.1: New USB device found, idVendor=05ad, 
> idProduct=0fba, bcdDevice= 3.00
> [14820.844756] usb 2-2.1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=0
> [14820.844759] usb 2-2.1: Product: USB-Serial Controller
> [14820.844761] usb 2-2.1: Manufacturer: Prolific Technology Inc.
> [14820.852720] pl2303 2-2.1:1.0: pl2303 converter detected
> [14820.856368] usb 2-2.1: pl2303 converter now attached to ttyUSB0
>
>  
>
> In my case, the serial-to-usb converter showed up at /dev/ttyUSB0, but 
> your results may differ.
>
>  
>
> -tk
>
>  
>
> On Wed, Apr 21, 2021 at 4:34 PM Dave McCreath  wrote:
>
> Forgot to add.
>
>  
>
> Now running 4.5.1 from a backup SD card and all is currently well but does 
> not look like I'll be able to update/upgrade the RPi until I figure out 
> what's wrong.
>
>  
>
> Regards
>
>  
>
> Dave
>
> On Thursday, 22 April 2021 at 00:08:18 UTC+1 Dave McCreath wrote:
>
> Good Evening Venerable Experts
>
>  
>
> Earlier on today I updated my RPi (sudu apt-get update && sudo apt-get 
> upgrade).  On rebooting WeeWx failed to start, this was post an upgrade 
> from 4.2 to 4.5.1. (I have WeeWx added to the sources list)
>
>  
>
> So, being savvy, rebooted from a backup sd card to bring the system back 
> to where it was prior to the update/upgrade and WeeWx version 4.2.
>
>  
>
> I then went about updating/upgrading WeeWx from 4.2 to 4.5 (sudo apt-get 
> install weewx), that went fine, rebooted and WeeWx ran without any issues 
> post the upgrade.
>
>  
>
> Next I then tried sudu apt-get update && sudo apt-get upgrade again.  Post 
> a reboot, exactly the same issue as before, WeeWx would not start:
>
>  
>
> pi@raspberrypi:~ $ servic

[weewx-user] RPi WeeWx Python 3.7 Issue

[Dave McCreath]

Good Evening Venerable Experts

Earlier on today I updated my RPi (sudu apt-get update && sudo apt-get 
upgrade).  On rebooting WeeWx failed to start, this was post an upgrade 
from 4.2 to 4.5.1. (I have WeeWx added to the sources list)

So, being savvy, rebooted from a backup sd card to bring the system back to 
where it was prior to the update/upgrade and WeeWx version 4.2.

I then went about updating/upgrading WeeWx from 4.2 to 4.5 (sudo apt-get 
install weewx), that went fine, rebooted and WeeWx ran without any issues 
post the upgrade.

Next I then tried sudu apt-get update && sudo apt-get upgrade again.  Post 
a reboot, exactly the same issue as before, WeeWx would not start:

pi@raspberrypi:~ $ service weewx status

● weewx.service - LSB: weewx weather system

   Loaded: loaded (/etc/init.d/weewx; generated)

   Active: active (exited) since Wed 2021-04-21 23:48:06 BST; 2min 28s ago

 Docs: man:systemd-sysv-generator(8)

  Process: 338 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)

 

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
weewx.engine:   self.port.openPort()

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py", 
line 308, in openPort

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
weewx.engine:   self.serial_port = serial.Serial(self.port, 
self.baudrate, timeout=self.timeout)

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
weewx.engine: File 
"/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in __init__

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
weewx.engine:   self.open()

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
weewx.engine: File 
"/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in open

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
weewx.engine:   raise SerialException(msg.errno, "could not 
open port {}: {}".format(self._port, msg))

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL 
weewx.engine:   serial.serialutil.SerialException: [Errno 2] could 
not open port /dev/ttyUSB0: [Errno 2] No such file or directory: 
'/dev/ttyUSB0'

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL __main__: 
Unable to load driver: [Errno 2] could not open port /dev/ttyUSB0: [Errno 
2] No such file or directory: '/dev/ttyUSB0'

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL __main__: 
  Exiting...


Any ideas?

-- 
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/a492c213-9deb-412f-947c-028097938b00n%40googlegroups.com.

RE: [weewx-user] Re: RPi WeeWx Python 3.7 Issue

[Dave McCreath]

Wait 15 minutes and I’ll do the upgrade again.

 

From: weewx-user@googlegroups.com  On Behalf Of 
Dave McCreath
Sent: 22 April 2021 01:21
To: weewx-user 
Subject: Re: [weewx-user] Re: RPi WeeWx Python 3.7 Issue

 

Tom

 

Please be aware that my answer is for the current working system, not the one 
that was broken.

 

I can try the RPi upgrade again and see if the file is located within the 
devices directory?

 

Dave

 

On Thursday, 22 April 2021 at 01:14:53 UTC+1 Dave McCreath wrote:

Tom

 

Hi.

 

Yep, mine is the same as yours:

 

[ 4689.183852] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0

[ 4689.183939] cp210x 1-1.4:1.0: device disconnected

[ 4689.633565] usb 1-1.4: new full-speed USB device number 5 using xhci_hcd

[ 4692.803586] usb 1-1.4: new full-speed USB device number 6 using xhci_hcd

[ 4692.938998] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00

[ 4692.939011] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[ 4692.939021] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller

[ 4692.939031] usb 1-1.4: Manufacturer: Silicon Labs

[ 4692.939040] usb 1-1.4: SerialNumber: 0001

[ 4692.946665] cp210x 1-1.4:1.0: cp210x converter detected

[ 4692.952907] usb 1-1.4: cp210x converter now attached to ttyUSB0

[ 4693.217302] usb 1-1.4: USB disconnect, device number 6

[ 4693.217689] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0

[ 4693.217742] cp210x 1-1.4:1.0: device disconnected

[ 4693.513548] usb 1-1.4: new full-speed USB device number 7 using xhci_hcd

[ 4693.648964] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00

[ 4693.648972] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[ 4693.648979] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller

[ 4693.648986] usb 1-1.4: Manufacturer: Silicon Labs

[ 4693.648992] usb 1-1.4: SerialNumber: 0001

[ 4693.652553] cp210x 1-1.4:1.0: cp210x converter detected

[ 4693.657075] usb 1-1.4: cp210x converter now attached to ttyUSB0

pi@raspberrypi:~ $

 

Regards

 

Dave

 

From: weewx...@googlegroups.com <mailto:weewx...@googlegroups.com>  
mailto:weewx...@googlegroups.com> > On Behalf Of 
Tom Keffer
Sent: 22 April 2021 01:07
To: weewx-user mailto:weewx...@googlegroups.com> >
Subject: Re: [weewx-user] Re: RPi WeeWx Python 3.7 Issue

 

Do you have a device /dev/ttyUSB0? That's normally where a Vantage shows up in 
the device directory, but not always. 

 

The most reliable way to find out where the Vantage ended up is to unplug it, 
plug it in again, then type 'dmesg'. This will look something like:

 

dmesg

[14818.699217] usb 2-2.1: USB disconnect, device number 4
[14818.699660] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[14818.699710] pl2303 2-2.1:1.0: device disconnected
[14820.731608] usb 2-2.1: new full-speed USB device number 10 using xhci_hcd
[14820.844750] usb 2-2.1: New USB device found, idVendor=05ad, idProduct=0fba, 
bcdDevice= 3.00
[14820.844756] usb 2-2.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[14820.844759] usb 2-2.1: Product: USB-Serial Controller
[14820.844761] usb 2-2.1: Manufacturer: Prolific Technology Inc.
[14820.852720] pl2303 2-2.1:1.0: pl2303 converter detected
[14820.856368] usb 2-2.1: pl2303 converter now attached to ttyUSB0

 

In my case, the serial-to-usb converter showed up at /dev/ttyUSB0, but your 
results may differ.

 

-tk

 

On Wed, Apr 21, 2021 at 4:34 PM Dave McCreath mailto:dave.m...@gmail.com> > wrote:

Forgot to add.

 

Now running 4.5.1 from a backup SD card and all is currently well but does not 
look like I'll be able to update/upgrade the RPi until I figure out what's 
wrong.

 

Regards

 

Dave

On Thursday, 22 April 2021 at 00:08:18 UTC+1 Dave McCreath wrote:

Good Evening Venerable Experts

 

Earlier on today I updated my RPi (sudu apt-get update && sudo apt-get 
upgrade).  On rebooting WeeWx failed to start, this was post an upgrade from 
4.2 to 4.5.1. (I have WeeWx added to the sources list)

 

So, being savvy, rebooted from a backup sd card to bring the system back to 
where it was prior to the update/upgrade and WeeWx version 4.2.

 

I then went about updating/upgrading WeeWx from 4.2 to 4.5 (sudo apt-get 
install weewx), that went fine, rebooted and WeeWx ran without any issues post 
the upgrade.

 

Next I then tried sudu apt-get update && sudo apt-get upgrade again.  Post a 
reboot, exactly the same issue as before, WeeWx would not start:

 

pi@raspberrypi:~ $ service weewx status

● weewx.service - LSB: weewx weather system

   Loaded: loaded (/etc/init.d/weewx; generated)

   Active: active (exited) since Wed 2021-04-21 23:48:06 BST; 2min 28s ago

 Docs: man:systemd-sysv-generator(8)

  Process: 338 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS)

 

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine: 
*

Re: [weewx-user] Re: RPi WeeWx Python 3.7 Issue

[Dave McCreath]

Tom

Apologies, it's 0140 in the morning here and it's been a long day!

Completed the upgrade but this time removed the plug and then re-inserted 
it post the reboot, all is now well.

pi@raspberrypi:~ $ service weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (running) since Thu 2021-04-22 01:36:39 BST; 1min 21s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 437 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
Tasks: 4 (limit: 4915)
   CGroup: /system.slice/weewx.service
   └─595 python3 /usr/share/weewx/weewxd --daemon 
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.restx: 
CWOP: Posting not enabled.
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.restx: WOW: 
Posting not enabled.
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.restx: 
AWEKAS: Data will be uploaded for user DMacWx
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO __main__: 
Starting up weewx version 4.5.1
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.engine: 
Clock error is 18.35 seconds (positive is fast)
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO 
weewx.drivers.vantage: Clock set to 2021-04-22 01:36:40 BST (1619051800)
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.engine: 
Using binding 'wx_binding' to database 'weewx.sdb'
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.manager: 
Starting backfill of daily summaries
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.manager: 
Daily summaries up to date
Apr 22 01:36:40 raspberrypi python3[595]: weewx[595] INFO weewx.engine: 
Starting main packet loop.
pi@raspberrypi:~ $ 

Thanks for the suggestion Peter, appears to have fixed it.

Regards

Dave

On Thursday, 22 April 2021 at 01:28:21 UTC+1 tke...@gmail.com wrote:

> Well, geez, we're not trying to fix the working system. Try it on the 
> broken system.
>
> On Wed, Apr 21, 2021 at 5:21 PM Dave McCreath  wrote:
>
>> Tom
>>
>> Please be aware that my answer is for the current working system, not the 
>> one that was broken.
>>
>> I can try the RPi upgrade again and see if the file is located within the 
>> devices directory?
>>
>> Dave
>>
>> On Thursday, 22 April 2021 at 01:14:53 UTC+1 Dave McCreath wrote:
>>
>>> Tom
>>>
>>>  
>>>
>>> Hi.
>>>
>>>  
>>>
>>> Yep, mine is the same as yours:
>>>
>>>  
>>>
>>> [ 4689.183852] cp210x ttyUSB0: cp210x converter now disconnected from 
>>> ttyUSB0
>>>
>>> [ 4689.183939] cp210x 1-1.4:1.0: device disconnected
>>>
>>> [ 4689.633565] usb 1-1.4: new full-speed USB device number 5 using 
>>> xhci_hcd
>>>
>>> [ 4692.803586] usb 1-1.4: new full-speed USB device number 6 using 
>>> xhci_hcd
>>>
>>> [ 4692.938998] usb 1-1.4: New USB device found, idVendor=10c4, 
>>> idProduct=ea60, bcdDevice= 1.00
>>>
>>> [ 4692.939011] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
>>> SerialNumber=3
>>>
>>> [ 4692.939021] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller
>>>
>>> [ 4692.939031] usb 1-1.4: Manufacturer: Silicon Labs
>>>
>>> [ 4692.939040] usb 1-1.4: SerialNumber: 0001
>>>
>>> [ 4692.946665] cp210x 1-1.4:1.0: cp210x converter detected
>>>
>>> [ 4692.952907] usb 1-1.4: cp210x converter now attached to ttyUSB0
>>>
>>> [ 4693.217302] usb 1-1.4: USB disconnect, device number 6
>>>
>>> [ 4693.217689] cp210x ttyUSB0: cp210x converter now disconnected from 
>>> ttyUSB0
>>>
>>> [ 4693.217742] cp210x 1-1.4:1.0: device disconnected
>>>
>>> [ 4693.513548] usb 1-1.4: new full-speed USB device number 7 using 
>>> xhci_hcd
>>>
>>> [ 4693.648964] usb 1-1.4: New USB device found, idVendor=10c4, 
>>> idProduct=ea60, bcdDevice= 1.00
>>>
>>> [ 4693.648972] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
>>> SerialNumber=3
>>>
>>> [ 4693.648979] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller
>>>
>>> [ 4693.648986] usb 1-1.4: Manufacturer: Silicon Labs
>>>
>>> [ 4693.648992] usb 1-1.4: SerialNumber: 0001
>>>
>>> [ 4693.652553] cp210x 1-1.4:1.0: cp210x converter detected
>>>
>>> [ 4693.657075] usb 1-1.4: cp210x converter now attached to ttyUSB0
>>>
>>> pi@raspberrypi:~ $
>>>
>>>  
>>>
>>> Regards

[weewx-user] Upgrade from 4.5.1 to 4.8.0 Critical Error

[Dave McCreath]

Good Morning.

My system runs on a Mk4 RPI using Debian Buster.

I'll start by saying that I'm not confident using Linux at all, but I try 
my best.

I upgraded my system to 4.5.1 a month after it came out and I had a similar 
issue to this one so rolled back using a back up.  Tried again a couple of 
weeks later and all went well using the repopulated 4.5.1 .conf file.

Last night I tried to upgrade the whole RPI system again which included the 
upgrade to WeeWX  4.8.0.  I used sudo apt update, followed by sudo apt 
upgrade.  I was asked as part of the process to either accept or decline 
the new .conf file.  I accepted, repopulated the new .conf file with the 
correct data and then rebooted the system.  WeeWX failed to start properly 
(see below).  I then tried again, this time opting to retain the 4.5.1 
.conf file, this also failed.  I'm now back up and running on a backup of 
the system prior to upgrading and all is well.

Here is a snapshot of the syslog during the upgrade (this mornings attempt 
that also failed), appears to be OK?:

Apr 25 11:08:17 raspberrypi systemd[1]: Stopping LSB: weewx weather 
system...

Apr 25 11:08:17 raspberrypi weewx[1578] INFO __main__: Received signal TERM 
(15).

Apr 25 11:08:17 raspberrypi weewx[1578] INFO weewx.engine: Main loop 
exiting. Shutting engine down.

Apr 25 11:08:17 raspberrypi weewx[1578] INFO weewx.engine: Shutting down 
StdReport thread

Apr 25 11:08:17 raspberrypi weewx[1578] INFO __main__: Terminating weewx 
version 4.5.1

Apr 25 11:08:17 raspberrypi weewx[26729]: Stopping weewx weather system: 
weewx.

Apr 25 11:08:17 raspberrypi systemd[1]: weewx.service: Succeeded.

Apr 25 11:08:17 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
And this is a snapshot of the syslog after the upgrade, I get the same 
error with either the 4.5.1 or 4.8.0 .conf file:

Apr 25 11:22:06 raspberrypi weewx[30659] INFO __main__: Received signal 
TERM (15).

Apr 25 11:22:06 raspberrypi weewx[30659] INFO weewx.engine: Main loop 
exiting. Shutting engine down.

Apr 25 11:22:06 raspberrypi weewx[30659] INFO weewx.engine: Shutting down 
StdReport thread

Apr 25 11:22:06 raspberrypi weewx[30659] INFO __main__: Terminating weewx 
version 4.8.0

Apr 25 11:22:06 raspberrypi weewx[2733]: Stopping weewx weather system: 
weewx.

Apr 25 11:22:06 raspberrypi systemd[1]: weewx.service: Succeeded.

Apr 25 11:22:06 raspberrypi systemd[1]: Stopped LSB: weewx weather system.

Apr 25 11:22:18 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...

Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Initializing weewx 
version 4.8.0

Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Using Python 3.7.3 
(default, Jan 22 2021, 20:04:44) #012[GCC 8.3.0]

Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Platform 
Linux-5.10.63-v7l+-armv7l-with-debian-10.12

Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Locale is 
'en_GB.UTF-8'

Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf

Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Debug is 0

Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: PID file is 
/var/run/weewx.pid

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__: Caught 
unrecoverable exception:

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__:   
'unspecified'

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__:   
Traceback (most recent call last):

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 147, in main

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__:   
engine = weewx.engine.StdEngine(config_dict)

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 81, in __init__

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__:   
self.setupStation(config_dict)

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 103, in setupStation

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__:   
driver = config_dict[station_type]['driver']

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__: File 
"/usr/lib/python3/dist-packages/configobj.py", line 554, in __getitem__

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__:   
val = dict.__getitem__(self, key)

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__:   
KeyError: 'unspecified'

Apr 25 11:22:18 raspberrypi weewx[2845] CRITICAL __main__:   
Exiting.

Apr 25 11:22:18 raspberrypi weewx[2830]: Starting weewx weather system: 
weewx.

Apr 25 11:22:18 raspberrypi systemd[1]: Started LSB: weewx weather system.

Can anyone with more knowledge than I give me an idea of what I'm dong 
wrong?


Many, many thanks.


Dave

-- 
You received this message because you are subscribed to the Google Groups 

Re: [weewx-user] Upgrade from 4.5.1 to 4.8.0 Critical Error

[Dave McCreath]

Tom

Many thanks for getting back to me with the suggestion.  I've just done a 
full system upgrade (again), and it worked first time.  I've no idea what 
happened.  To the best of my knowledge I've done nothing different to the 
other occasions I tried to upgrade, however, the SD card used this 
afternoon was a new one.  That may have been the issue.

Thank you

Dave

On Monday, 25 April 2022 at 12:00:45 UTC+1 tke...@gmail.com wrote:

> For some reason, your configuration file is not getting set up for the 
> specific weather station and driver you are using. 
>
> Perhaps you can give us some details about what you mean by, "repopulated 
> the new .conf file with the correct data"? Did you do this by hand?
>
> If it happens again, you can try to reconfigure by using the utility 
> wee_config <http://www.weewx.com/docs/utilities.htm#Action_--reconfigure>:
>
> *wee_config --reconfigure*
>
> It will prompt you for information about your station, including which 
> driver to use.
>
> -tk
>
> On Mon, Apr 25, 2022 at 3:45 AM Dave McCreath  wrote:
>
>> Good Morning.
>>
>> My system runs on a Mk4 RPI using Debian Buster.
>>
>> I'll start by saying that I'm not confident using Linux at all, but I try 
>> my best.
>>
>> I upgraded my system to 4.5.1 a month after it came out and I had a 
>> similar issue to this one so rolled back using a back up.  Tried again a 
>> couple of weeks later and all went well using the repopulated 4.5.1 .conf 
>> file.
>>
>> Last night I tried to upgrade the whole RPI system again which included 
>> the upgrade to WeeWX  4.8.0.  I used sudo apt update, followed by sudo apt 
>> upgrade.  I was asked as part of the process to either accept or decline 
>> the new .conf file.  I accepted, repopulated the new .conf file with the 
>> correct data and then rebooted the system.  WeeWX failed to start properly 
>> (see below).  I then tried again, this time opting to retain the 4.5.1 
>> .conf file, this also failed.  I'm now back up and running on a backup of 
>> the system prior to upgrading and all is well.
>>
>> Here is a snapshot of the syslog during the upgrade (this mornings 
>> attempt that also failed), appears to be OK?:
>>
>> Apr 25 11:08:17 raspberrypi systemd[1]: Stopping LSB: weewx weather 
>> system...
>>
>> Apr 25 11:08:17 raspberrypi weewx[1578] INFO __main__: Received signal 
>> TERM (15).
>>
>> Apr 25 11:08:17 raspberrypi weewx[1578] INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>>
>> Apr 25 11:08:17 raspberrypi weewx[1578] INFO weewx.engine: Shutting down 
>> StdReport thread
>>
>> Apr 25 11:08:17 raspberrypi weewx[1578] INFO __main__: Terminating weewx 
>> version 4.5.1
>>
>> Apr 25 11:08:17 raspberrypi weewx[26729]: Stopping weewx weather system: 
>> weewx.
>>
>> Apr 25 11:08:17 raspberrypi systemd[1]: weewx.service: Succeeded.
>>
>> Apr 25 11:08:17 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
>> And this is a snapshot of the syslog after the upgrade, I get the same 
>> error with either the 4.5.1 or 4.8.0 .conf file:
>>
>> Apr 25 11:22:06 raspberrypi weewx[30659] INFO __main__: Received signal 
>> TERM (15).
>>
>> Apr 25 11:22:06 raspberrypi weewx[30659] INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>>
>> Apr 25 11:22:06 raspberrypi weewx[30659] INFO weewx.engine: Shutting down 
>> StdReport thread
>>
>> Apr 25 11:22:06 raspberrypi weewx[30659] INFO __main__: Terminating weewx 
>> version 4.8.0
>>
>> Apr 25 11:22:06 raspberrypi weewx[2733]: Stopping weewx weather system: 
>> weewx.
>>
>> Apr 25 11:22:06 raspberrypi systemd[1]: weewx.service: Succeeded.
>>
>> Apr 25 11:22:06 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
>>
>> Apr 25 11:22:18 raspberrypi systemd[1]: Starting LSB: weewx weather 
>> system...
>>
>> Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Initializing weewx 
>> version 4.8.0
>>
>> Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Using Python 3.7.3 
>> (default, Jan 22 2021, 20:04:44) #012[GCC 8.3.0]
>>
>> Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Platform 
>> Linux-5.10.63-v7l+-armv7l-with-debian-10.12
>>
>> Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Locale is 
>> 'en_GB.UTF-8'
>>
>> Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>>
>> Apr 25 11:22:18 raspberrypi weewx[2841] INFO __main__: Debug is 0
>>
>

Re: [weewx-user] Re: Davis Data Logger - Issue

[Dave McCreath]

Tom

It's a USB Data Logger (old type of USB). AC powered with battery backup, 
no taught wires and the logger is housed securely.

Just over an hour has gone by with no more errors, as you say, it may just 
be the reset/catch up that caused the second issue.  I'll have a look again 
on the morrow to see if the error crops up again.  

When I first saw the issue, having recently upgraded to 4.8, I reverted to 
my 4.5.1 back up  As the issue was still present I then re-seated the data 
logger.  I'll do the upgrade back to 4.8 once I'm happy the system is 
stable again.

Many thanks.

Dave


On Sunday, 8 May 2022 at 21:53:45 UTC+1 tke...@gmail.com wrote:

> The "Expected 99, got 0" error is pretty common, especially after the 
> logger has done a catch up. I have not noticed any correlation with the age 
> of the logger. 
>
> What kind of connection are you using? USB? Serial? Serial through a USB 
> converter? The last (converters) are notoriously flaky.
>
> -tk
>
> On Sun, May 8, 2022 at 1:03 PM Dave McCreath  wrote:
>
>> Spoke too soon.  The error appears to back back up, is this a data logger 
>> issue?:
>>
>> May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: AWEKAS: 
>> Published record 2022-05-08 20:55:00 BST (1652039700)
>> May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: PWSWeather: 
>> Published record 2022-05-08 20:55:00 BST (1652039700)
>> May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: 
>> Wunderground-PWS: Published record 2022-05-08 20:55:00 BST (1652039700)
>> May  8 20:55:19 raspberrypi weewx[8172] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 1.07 seconds
>> May  8 20:55:21 raspberrypi weewx[8172] INFO weewx.imagegenerator: 
>> Generated 30 images for report SeasonsReport in 2.44 seconds
>> May  8 20:55:21 raspberrypi weewx[8172] INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> May  8 20:55:28 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> try #1; error: Expected to read 99 chars; got 0 instead
>> May  8 20:55:32 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> try #2; error: Expected to read 99 chars; got 0 instead
>> May  8 20:55:36 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> try #3; error: Expected to read 99 chars; got 0 instead
>> May  8 20:55:40 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> try #4; error: Expected to read 99 chars; got 0 instead
>> May  8 20:55:40 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> max tries (4) exceeded.
>> May  8 20:55:40 raspberrypi weewx[8172] INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>> May  8 20:55:40 raspberrypi weewx[8172] INFO weewx.engine: Shutting down 
>> StdReport thread
>> May  8 20:55:40 raspberrypi weewx[8172] CRITICAL __main__: Caught 
>> WeeWxIOError: Max tries exceeded while getting LOOP data.
>> May  8 20:55:40 raspberrypi weewx[8172] CRITICAL __main__:  
>>  Waiting 60 seconds then retrying...
>> May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: retrying...
>> May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: Debug is 0
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Archive will 
>> use data binding wx_binding
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Record 
>> generation will be attempted in 'software'
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Using archive 
>> interval of 300 seconds (software record generation)
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: 
>> StationRegistry: Station will not be registered: no station_url specified.
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: 
>> Wunderground-PWS: Data for station ICAMBSLE2 will be posted
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: PWSWeather: 
>> Data for station WISBECH will be posted
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: CWOP: Posting 
>> not enabled.
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: WOW: Posting 
>> not enabled.
>> May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: AWEKAS: Data 
>> will be uploaded for user DMacWx
>> May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: Starting up weewx 
>> version

[weewx-user] Davis Data Logger - Issue

[Dave McCreath]

Just noticed a couple of errors thrown up by WeeWX:

ERROR weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; 
got 0 instead.

Having then read through this forum I then reset the data logger in the 
Vantage console (removed all power, pulled the data logger out for 20 
seconds, replaced and then powered back up) and all appears to be back up 
and running OK.

My first data logger lasted about 5 years before giving up on me, this one 
is about 3 years old, is this a sign that it's on its way out as well?

They're not cheap!


Thanks


Dave


-- 
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/92183bdc-2b70-42de-a04a-5f3bc1c741e4n%40googlegroups.com.

[weewx-user] Re: Davis Data Logger - Issue

[Dave McCreath]

Spoke too soon.  The error appears to back back up, is this a data logger 
issue?:

May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: AWEKAS: Published 
record 2022-05-08 20:55:00 BST (1652039700)
May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: PWSWeather: 
Published record 2022-05-08 20:55:00 BST (1652039700)
May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: Wunderground-PWS: 
Published record 2022-05-08 20:55:00 BST (1652039700)
May  8 20:55:19 raspberrypi weewx[8172] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 1.07 seconds
May  8 20:55:21 raspberrypi weewx[8172] INFO weewx.imagegenerator: 
Generated 30 images for report SeasonsReport in 2.44 seconds
May  8 20:55:21 raspberrypi weewx[8172] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
May  8 20:55:28 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
try #1; error: Expected to read 99 chars; got 0 instead
May  8 20:55:32 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
try #2; error: Expected to read 99 chars; got 0 instead
May  8 20:55:36 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
try #3; error: Expected to read 99 chars; got 0 instead
May  8 20:55:40 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
try #4; error: Expected to read 99 chars; got 0 instead
May  8 20:55:40 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
max tries (4) exceeded.
May  8 20:55:40 raspberrypi weewx[8172] INFO weewx.engine: Main loop 
exiting. Shutting engine down.
May  8 20:55:40 raspberrypi weewx[8172] INFO weewx.engine: Shutting down 
StdReport thread
May  8 20:55:40 raspberrypi weewx[8172] CRITICAL __main__: Caught 
WeeWxIOError: Max tries exceeded while getting LOOP data.
May  8 20:55:40 raspberrypi weewx[8172] CRITICAL __main__:  
 Waiting 60 seconds then retrying...
May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: retrying...
May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: Debug is 0
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: StdConvert 
target unit is 0x1
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Archive will use 
data binding wx_binding
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Record 
generation will be attempted in 'software'
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Using archive 
interval of 300 seconds (software record generation)
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: StationRegistry: 
Station will not be registered: no station_url specified.
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: Wunderground-PWS: 
Data for station ICAMBSLE2 will be posted
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: PWSWeather: Data 
for station WISBECH will be posted
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: CWOP: Posting not 
enabled.
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: WOW: Posting not 
enabled.
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.restx: AWEKAS: Data will 
be uploaded for user DMacWx
May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: Starting up weewx 
version 4.5.1
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Clock error is 
0.55 seconds (positive is fast)
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.manager: Starting 
backfill of daily summaries
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.manager: Daily summaries 
up to date
May  8 20:56:40 raspberrypi weewx[8172] INFO weewx.engine: Starting main 
packet loop.
May  8 21:00:16 raspberrypi weewx[8172] INFO weewx.manager: Added record 
2022-05-08 21:00:00 BST (165204) to database 'weewx.sdb'
May  8 21:00:16 raspberrypi weewx[8172] INFO weewx.manager: Added record 
2022-05-08 21:00:00 BST (165204) to daily summary in 'weewx.sdb'
May  8 21:00:16 raspberrypi weewx[8172] INFO weewx.restx: AWEKAS: Published 
record 2022-05-08 21:00:00 BST (165204)
May  8 21:00:16 raspberrypi weewx[8172] INFO weewx.restx: PWSWeather: 
Published record 2022-05-08 21:00:00 BST (165204)
May  8 21:00:16 raspberrypi weewx[8172] INFO weewx.restx: Wunderground-PWS: 
Published record 2022-05-08 21:00:00 BST (165204)
May  8 21:00:17 raspberrypi weewx[8172] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 1.02 seconds
May  8 21:00:21 raspberrypi weewx[8172] INFO weewx.imagegenerator: 
Generated 45 images for report SeasonsReport in 4.30 seconds
May  8 21:00:21 raspberrypi weewx[8172] INFO weewx.reportengine: Copied 5 
files to /var/www/html/weewx

Any suggestions welcome.

Dave

On Sunday, 8 May 2022 at 20:20:45 UTC+1 Dave McCreath wrote:

> Just noti

Re: [weewx-user] Data Retrieval - Vantage Data Logger

[Dave McCreath]

RTC arrived, installed and all is working as it should be.

Turned the RPi off for 40 minutes, rebooted, and all missing records 
retrieved and uploaded.

Thank you.

Dave

On Friday, 14 April 2023 at 12:30:11 UTC+1 Dave McCreath wrote:

> Just by chance we had another power cut today, 1hr 10minutes.  Whilst the 
> power was off I disconnected the USB interface from the Vantage Vue to the 
> RPi.  When the power was restored I stopped the weeWx service on the RPi, 
> plugged the USB interface back in and then restarted weeWx.  All good and 
> every record retrieved and uploaded.  
>
> Still awaiting the arrival of the RTC.
>
> Dave
>
> On Thursday, 13 April 2023 at 21:43:15 UTC+1 Dave McCreath wrote:
>
>> Vince.  RTC inbound, I'll keep you posted.
>>
>> On Wednesday, 12 April 2023 at 21:01:01 UTC+1 vince wrote:
>>
>>> On Wednesday, April 12, 2023 at 12:50:57 PM UTC-7 Dave McCreath wrote:
>>>
>>> Any ideas?
>>>
>>>
>>> Not without debug > 0 logs for the second case where it failed.   Given 
>>> your description, my 'guess' is you do not have a RTC installed and you 
>>> haven't disabled that lame fake_hwclock thing that is enabled in the os as 
>>> a default.   Leave the box powered down for an hour if you can just so we 
>>> can see the clock jump after you power it back up.
>>>
>>>
>>>

-- 
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/df26aa0b-6ff9-458d-aefa-0ca916778e59n%40googlegroups.com.

Re: [weewx-user] Data Retrieval - Vantage Data Logger

[Dave McCreath]

I've managed to replicate the error.

As above, leave the RPi on but stop the weeWx service for ten minutes, then 
re-start it, the two records held on the data logger are found and uploaded.

However, if I power down the RPi for ten minutes and then boot it back up 
again, weeWx fails to pull the two missing records.

Any ideas?

Dave

On Wednesday, 12 April 2023 at 14:47:52 UTC+1 Dave McCreath wrote:

> Tom, Greg
>
> Many thanks to both of you for getting back to me.
>
> The console is mains powered with battery backup, batteries are good, less 
> than 2 weeks old.
>
> Using the Vantage driver, 5 minute interval, time is updated on each new 
> boot of the Rpi.
>
> As Greg suggested, I turned debugging on, powered down the Rpi for 10 
> minutes and then rebooted, missing two records.  On checking the log, the 
> two missing data files were found and uploaded!  However, that did not 
> happen earlier on today between 1040-1120hrs (see below).  Not sure what 
> has changed?
>
> It appears to have corrected itself, but just in case, I've appended the 
> log:
>
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG weewx.restx: Shut down 
> PWSWeather thread.
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG weewx.restx: Shut down 
> Wunderground-PWS thread.
> Apr 12 14:08:10 raspberrypi weewx[4785] INFO __main__: Terminating weewx 
> version 4.9.1
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:  
>  Traceback (most recent call last):
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__: File 
> "/usr/share/weewx/weewxd", line 154, in main
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:  
>  engine.run()
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 208, in run
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:   for 
> packet in self.console.genLoopPackets():
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__: File 
> "/usr/share/weewx/weewx/drivers/vantage.py", line 539, in genLoopPackets
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:   for 
> _loop_packet in self.genDavisLoopPackets(self.loop_batch):
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__: File 
> "/usr/share/weewx/weewx/drivers/vantage.py", line 566, in 
> genDavisLoopPackets
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:  
>  loop_packet = self._get_packet()
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__: File 
> "/usr/share/weewx/weewx/drivers/vantage.py", line 580, in _get_packet
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:  
>  _buffer = self.port.read(99)
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__: File 
> "/usr/share/weewx/weewx/drivers/vantage.py", line 277, in read
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:  
>  _buffer = self.serial_port.read(chars)
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__: File 
> "/usr/lib/python3/dist-packages/serial/serialposix.py", line 483, in read
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:  
>  ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], 
> timeout.time_left())
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__: File 
> "/usr/share/weewx/weewxd", line 245, in sigTERMhandler
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:  
>  raise Terminate
> Apr 12 14:08:10 raspberrypi weewx[4785] DEBUG __main__:   Terminate
> Apr 12 14:08:10 raspberrypi weewx[11059]: Stopping weewx weather system: 
> weewx.
> Apr 12 14:08:10 raspberrypi systemd[1]: weewx.service: Succeeded.
> Apr 12 14:08:10 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
>
> Apr 12 14:19:44 raspberrypi systemd[1]: Starting LSB: weewx weather 
> system...
> Apr 12 14:19:44 raspberrypi weewx[13942] INFO __main__: Initializing weewx 
> version 4.9.1
> Apr 12 14:19:44 raspberrypi weewx[13942] INFO __main__: Using Python 3.7.3 
> (default, Oct 31 2022, 14:04:00) #012[GCC 8.3.0]
> Apr 12 14:19:44 raspberrypi weewx[13942] INFO __main__: Located at 
> /usr/bin/python3
> Apr 12 14:19:44 raspberrypi weewx[13942] INFO __main__: Platform 
> Linux-5.10.103-v7l+-armv7l-with-debian-10.13
> Apr 12 14:19:44 raspberrypi weewx[13942] INFO __main__: Locale is 
> 'en_GB.UTF-8'
> Apr 12 14:19:44 raspberrypi weewx[13942] INFO __main__: Using 
> configuration file /etc/weewx/weewx.conf
> Apr 12 14:19:44 raspberrypi weewx[13942] INFO __main__: Debug is 1
> Apr 12 14:19:44 raspberrypi weewx[13942] I

Re: [weewx-user] Data Retrieval - Vantage Data Logger

[Dave McCreath]

Just by chance we had another power cut today, 1hr 10minutes.  Whilst the 
power was off I disconnected the USB interface from the Vantage Vue to the 
RPi.  When the power was restored I stopped the weeWx service on the RPi, 
plugged the USB interface back in and then restarted weeWx.  All good and 
every record retrieved and uploaded.  

Still awaiting the arrival of the RTC.

Dave

On Thursday, 13 April 2023 at 21:43:15 UTC+1 Dave McCreath wrote:

> Vince.  RTC inbound, I'll keep you posted.
>
> On Wednesday, 12 April 2023 at 21:01:01 UTC+1 vince wrote:
>
>> On Wednesday, April 12, 2023 at 12:50:57 PM UTC-7 Dave McCreath wrote:
>>
>> Any ideas?
>>
>>
>> Not without debug > 0 logs for the second case where it failed.   Given 
>> your description, my 'guess' is you do not have a RTC installed and you 
>> haven't disabled that lame fake_hwclock thing that is enabled in the os as 
>> a default.   Leave the box powered down for an hour if you can just so we 
>> can see the clock jump after you power it back up.
>>
>>
>>

-- 
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/a9bedcb1-97a7-4fd3-ac89-b023e926d4f8n%40googlegroups.com.

[weewx-user] Data Retrieval - Vantage Data Logger

[Dave McCreath]

Good afternoon all.

Minor issue but nagging me.

System: Vantage Vue with USB datalogger, RPi 4, weeWx 4.9.1.

In the past, post a power outage, the system would power up and pull all 
the missing records from the data logger generated during a power outage 
and then upload those missing from whichever site they were destined for.

For me, over time, this has stopped.  Post a power outage now, weeWx does 
not find any missing records at all, even though I presume, they must 
exist.  All records generated post the power cut are uploaded as normal.

The complexities of databases are (almost) beyond me.  Weewx appears to be 
pulling records from the weather station as they are produced, but not 
those that should be logged on the data logger.

Any ideas what I have wrong?

Dave

-- 
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/a53ce525-89e2-438b-b940-115d555d4cfen%40googlegroups.com.

Re: [weewx-user] Data Retrieval - Vantage Data Logger

[Dave McCreath]

Vince.  RTC inbound, I'll keep you posted.

On Wednesday, 12 April 2023 at 21:01:01 UTC+1 vince wrote:

> On Wednesday, April 12, 2023 at 12:50:57 PM UTC-7 Dave McCreath wrote:
>
> Any ideas?
>
>
> Not without debug > 0 logs for the second case where it failed.   Given 
> your description, my 'guess' is you do not have a RTC installed and you 
> haven't disabled that lame fake_hwclock thing that is enabled in the os as 
> a default.   Leave the box powered down for an hour if you can just so we 
> can see the clock jump after you power it back up.
>
>
>

-- 
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/375ecbb0-9621-4ac7-9a63-f697f47db018n%40googlegroups.com.

[weewx-user] Repository Error

[Dave McCreath]

Hi

Weewx installed on a RPI 4 (Debian - Bullseye), version 5.0.1, working 
fine, no issues.

Just tried to update to version 5.0.2 via sudo apt update && sudo apt 
full-upgrade and received the following error:

$ sudo apt update && sudo apt full-upgrade
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease 
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease 
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease 
Hit:5 http://repository.picockpit.com/raspbian bullseye InRelease  
Get:6 http://weewx.com/apt/python3 buster InRelease [4,252 B]   
  
Err:6 http://weewx.com/apt/python3 buster InRelease
  The following signatures couldn't be verified because the public key is 
not available: NO_PUBKEY E788768B9CB16E10
Fetched 4,252 B in 2s (1,789 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
http://weewx.com/apt/python3 buster InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
E788768B9CB16E10
W: Failed to fetch http://weewx.com/apt/python3/dists/buster/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY E788768B9CB16E10
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I've read through the WeeWX 5 help guide and, even though I'm on Bullseye, 
it does state that the repository should point to Buster (which it does).

Any help for noob much appreciated.

Many thanks.

-- 
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/2e0c6862-ce47-4be1-b465-55208f8e0bc5n%40googlegroups.com.

[weewx-user] Re: Repository Error

[Dave McCreath]

Mario

I owe you a beer (or two).

/dev/ttyUSB0 is the USB-to-serial adapter.

Followed your instructions to the letter and I now have a fully functioning 
WeeWX v5.0.2.

Many, many thanks.

Regards

Dave

On Thursday 15 February 2024 at 22:03:02 UTC matthew wall wrote:

> On Thursday, February 15, 2024 at 4:43:37 PM UTC-5 dave.m...@gmail.com 
> wrote:
>
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
>  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 325, in 
> open
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
>  raise SerialException(msg.errno, "could not open port {}: 
> {}".format(self._port, msg))
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
>  serial.serialutil.SerialException: [Errno 13] could not open port 
> /dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL __main__: Unable to load 
> driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Permission 
> denied: '/dev/ttyUSB0'
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL __main__:  
>  Exiting...
> Feb 15 21:37:15 weewx systemd[1]: weewx.service: Main process exited, 
> code=exited, status=4/NOPERMISSION
> Feb 15 21:37:15 weewx systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
>
> Now unable to restart WeeWX and have rolled back to the previous version.
>
> Any idea what the issue is?
>
>
> the error indicates that the weewxd process does not have permission to 
> read/write the USB-to-serial device.  make sure that the user running 
> weewxd has read/write permission to /dev/ttyUSB0 (which is probably a 
> USB-to-serial adapter).
>
> for example, if user 'weewx' is running weewxd, then put the weewx user 
> into the dialout group then restart weewxd:
>
> sudo usermod -aG dialout weewx
> sudo systemctl restart weewx
>
> see the section about reading/writing to devices in the wiki article "what 
> you need to know about permissions":
>
>
> https://github.com/weewx/weewx/wiki/Understanding-permissions#readingwriting-data-to-a-device
>
> please let us know what works for you.  there are *so* many variations 
> when it comes to permissions, and many different ways to make things work.  
> we're still trying to simplify the documentation to make permissions easier 
> to understand and deal with.
>
> m
>

-- 
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/5b750db4-17ef-4414-93fe-389c1da8aa60n%40googlegroups.com.

[weewx-user] Re: Repository Error

[Dave McCreath]

Mathew

I owe you a beer (or two)!

Your are correct  /dev/ttyUSB0  is indeed the USB to serial adaptor to the 
Vantage Vue.

I followed your instructions to the letter and I now have a fully 
functioning v5.0.2 or WeeWX.

Thank you, your help and patience is very, very much appreciated.

Dave

On Thursday 15 February 2024 at 22:03:02 UTC matthew wall wrote:

> On Thursday, February 15, 2024 at 4:43:37 PM UTC-5 dave.m...@gmail.com 
> wrote:
>
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
>  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 325, in 
> open
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
>  raise SerialException(msg.errno, "could not open port {}: 
> {}".format(self._port, msg))
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
>  serial.serialutil.SerialException: [Errno 13] could not open port 
> /dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL __main__: Unable to load 
> driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Permission 
> denied: '/dev/ttyUSB0'
> Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL __main__:  
>  Exiting...
> Feb 15 21:37:15 weewx systemd[1]: weewx.service: Main process exited, 
> code=exited, status=4/NOPERMISSION
> Feb 15 21:37:15 weewx systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
>
> Now unable to restart WeeWX and have rolled back to the previous version.
>
> Any idea what the issue is?
>
>
> the error indicates that the weewxd process does not have permission to 
> read/write the USB-to-serial device.  make sure that the user running 
> weewxd has read/write permission to /dev/ttyUSB0 (which is probably a 
> USB-to-serial adapter).
>
> for example, if user 'weewx' is running weewxd, then put the weewx user 
> into the dialout group then restart weewxd:
>
> sudo usermod -aG dialout weewx
> sudo systemctl restart weewx
>
> see the section about reading/writing to devices in the wiki article "what 
> you need to know about permissions":
>
>
> https://github.com/weewx/weewx/wiki/Understanding-permissions#readingwriting-data-to-a-device
>
> please let us know what works for you.  there are *so* many variations 
> when it comes to permissions, and many different ways to make things work.  
> we're still trying to simplify the documentation to make permissions easier 
> to understand and deal with.
>
> m
>

-- 
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/2c89f6bb-fc7e-45ac-95cc-cadb76eff884n%40googlegroups.com.

[weewx-user] Re: Repository Error

[Dave McCreath]

: CRITICAL weewx.engine:   
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 Traceback (most recent call last):
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self)
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 return VantageService(engine, config_dict)
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in __init__
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in __init__
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 self.port.openPort()
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in openPort
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 self.serial_port = serial.Serial(self.port, self.baudrate, 
timeout=self.timeout)
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
 File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 244, in 
__init__
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 self.open()
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:    
 File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 325, in 
open
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 raise SerialException(msg.errno, "could not open port {}: 
{}".format(self._port, msg))
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL weewx.engine:  
 serial.serialutil.SerialException: [Errno 13] could not open port 
/dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL __main__: Unable to load 
driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Permission 
denied: '/dev/ttyUSB0'
Feb 15 21:37:15 weewx weewxd[103822]: CRITICAL __main__:  
 Exiting...
Feb 15 21:37:15 weewx systemd[1]: weewx.service: Main process exited, 
code=exited, status=4/NOPERMISSION
Feb 15 21:37:15 weewx systemd[1]: weewx.service: Failed with result 
'exit-code'.

Now unable to restart WeeWX and have rolled back to the previous version.

Any idea what the issue is?

Regards



On Thursday 15 February 2024 at 21:21:37 UTC Mario Wesolek wrote:

> https://weewx.com/docs/4.10/debian.htm
>
> Reimport the Key 
> Dave McCreath schrieb am Donnerstag, 15. Februar 2024 um 22:16:53 UTC+1:
>
>> Hi
>>
>> Weewx installed on a RPI 4 (Debian - Bullseye), version 5.0.1, working 
>> fine, no issues.
>>
>> Just tried to update to version 5.0.2 via sudo apt update && sudo apt 
>> full-upgrade and received the following error:
>>
>> $ sudo apt update && sudo apt full-upgrade
>> Hit:1 http://security.debian.org/debian-security bullseye-security 
>> InRelease
>> Hit:2 http://deb.debian.org/debian bullseye InRelease 
>> Hit:3 http://deb.debian.org/debian bullseye-updates InRelease 
>> Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease 
>> Hit:5 http://repository.picockpit.com/raspbian bullseye InRelease  
>> Get:6 http://weewx.com/apt/python3 buster InRelease [4,252 B]   
>>   
>> Err:6 http://weewx.com/apt/python3 buster InRelease
>>   The following signatures couldn't be verified because the public key is 
>> not available: NO_PUBKEY E788768B9CB16E10
>> Fetched 4,252 B in 2s (1,789 B/s)
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> All packages are up to date.
>> W: An error occurred during the signature verification. The repository is 
>> not updated and the previous index files will be used. GPG error: 
>> http://weewx.com/apt/python3 buster InRelease: The following signatures 
>> couldn't be verified because the public key is not available: NO_PUBKEY 
>> E788768B9CB16E10
>> W: Failed to fetch http://weewx.com/apt/python3/dists/buster/InRelease 
>>  The following signatures couldn't be verified because the public key is 
>> not available: NO_PUBKEY E788768B9CB16E10
>> W: Some index files failed to download. They have been ignored, or old

[weewx-user] Re: Install of WeeWX 5.0.2 on RPI 5 Failed

[Dave McCreath]

Ville

Many thanks for your support.  As requested output of ls /dev/

is here:

DMac@WeeWX:~ $ ls /dev/
autofs   loop1 ram6tty24  tty58  vcsu1
blockloop2 ram7tty25  tty59  vcsu2
bsg  loop3 ram8tty26  tty6   vcsu3
btrfs-controlloop4 ram9tty27  tty60  vcsu4
bus  loop5 random  tty28  tty61  vcsu5
cachefiles   loop6 rfkill  tty29  tty62  vcsu6
cec0 loop7 rtc tty3   tty63  vcsu7
cec1 loop-control  rtc0tty30  tty7   vga_arbiter
char mappersda tty31  tty8   vhci
console  media0sda1tty32  tty9   vhost-net
cpu_dma_latency  media1serial  tty33  ttyAMA10   vhost-vsock
cuse media2serial0 tty34  ttyprintk  video19
disk mem   sg0 tty35  ttyUSB0video20
dma_heap mmcblk0   shm tty36  uhid   video21
dri  mmcblk0p1 snd tty37  uinput video22
fd   mmcblk0p2 spidev10.0  tty38  urandomvideo23
full mqueuestderr  tty39  v4lvideo24
fuse net   stdin   tty4   vantagevideo25
gpiochip0null  stdout  tty40  vcio   video26
gpiochip1port  tty tty41  vc-mem video27
gpiochip2ppp   tty0tty42  vcsvideo28
gpiochip3pps0  tty1tty43  vcs1   video29
gpiochip4ptmx  tty10   tty44  vcs2   video30
gpiomem0 ptp0  tty11   tty45  vcs3   video31
gpiomem1 pts   tty12   tty46  vcs4   video32
gpiomem2 ram0  tty13   tty47  vcs5   video33
gpiomem3 ram1  tty14   tty48  vcs6   video34
gpiomem4 ram10 tty15   tty49  vcs7   video35
hwrngram11 tty16   tty5   vcsa   video36
i2c-11   ram12 tty17   tty50  vcsa1  video37
i2c-12   ram13 tty18   tty51  vcsa2  watchdog
initctl  ram14 tty19   tty52  vcsa3  watchdog0
inputram15 tty2tty53  vcsa4  zero
kmsg ram2  tty20   tty54  vcsa5
kvm  ram3  tty21   tty55  vcsa6
log  ram4  tty22   tty56  vcsa7
loop0ram5  tty23   tty57  vcsu

Regards

Dave


On Wednesday 21 February 2024 at 12:49:42 UTC vhel...@gmail.com wrote:

> Hi,
>
> Plug the USB serial converter with weatherstation plugged to your RPI5.
> Check from linux terminal command: ls /dev/ to see is your logger there.
> Paste the results of: ls /dev/ here.
>
> -Ville-
>
>
> keskiviikko 21. helmikuuta 2024 klo 14.38.36 UTC+2 Dave McCreath kirjoitti:
>
>> Recently acquired an RPi 5 and decided this morning to migrate WeeWX over 
>> to it from an up to date RPi 4.
>>
>> Three attempts, all failed with the same errors.  I have tried with both 
>> the USB serial connector inserted and without.  I'm running the RPi 
>> headless over VNC and nothing else plugged into it at all apart from the 
>> power lead.
>>
>> *Log:*
>>
>>  2024-02-21T12:15:44.944885+00:00 WeeWX weectl[2869]: INFO weectllib: 
>> Initializing weectl version 5.0.2
>> 2024-02-21T12:15:44.945066+00:00 WeeWX weectl[2869]: INFO weectllib: 
>> Command line: /usr/share/weewx/weectl.py station reconfigure 
>> --config=/etc/weewx/weewx.conf --driver=weewx.drivers.vantage 
>> --units=metric --location=Leverington --latitude=52.693 --longitude=0.147 
>> --altitude=3,meter --register=y --station-url=
>> https://www.wunderground.com/dashboard/pws/ICAMBSLE2 --no-prompt 
>> --no-backup
>> 2024-02-21T12:15:44.945101+00:00 WeeWX weectl[2869]: ERROR 
>> weeutil.startup: Cannot load user extensions: No module named 'user'
>> 2024-02-21T12:15:44.974672+00:00 WeeWX weectl[2869]: INFO weectl-station: 
>> Using Vantage version 3.6.2 (weewx.drivers.vantage)
>> 2024-02-21T12:15:45.030191+00:00 WeeWX systemd[1]: Reloading.
>> 2024-02-21T12:15:45.848292+00:00 WeeWX systemd[1]: Reloading.
>> 2024-02-21T12:15:46.281844+00:00 WeeWX systemd[1]: Started weewx.service 
>> - WeeWX.
>> 2024-02-21T12:15:46.362945+00:00 WeeWX weewxd[3153]: INFO __main__: 
>> Initializing weewxd version 5.0.2
>> 2024-02-21T12:15:46.363060+00:00 WeeWX weewxd[3153]: INFO __main__: 
>> Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> 2024-02-21T12:15:46.371965+00:00 WeeWX weewxd[3153]: INFO __main__: Using 
>> Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
>> 2024-0

[weewx-user] Install of WeeWX 5.0.2 on RPI 5 Failed

[Dave McCreath]

Recently acquired an RPi 5 and decided this morning to migrate WeeWX over 
to it from an up to date RPi 4.

Three attempts, all failed with the same errors.  I have tried with both 
the USB serial connector inserted and without.  I'm running the RPi 
headless over VNC and nothing else plugged into it at all apart from the 
power lead.

*Log:*

 2024-02-21T12:15:44.944885+00:00 WeeWX weectl[2869]: INFO weectllib: 
Initializing weectl version 5.0.2
2024-02-21T12:15:44.945066+00:00 WeeWX weectl[2869]: INFO weectllib: 
Command line: /usr/share/weewx/weectl.py station reconfigure 
--config=/etc/weewx/weewx.conf --driver=weewx.drivers.vantage 
--units=metric --location=Leverington --latitude=52.693 --longitude=0.147 
--altitude=3,meter --register=y 
--station-url=https://www.wunderground.com/dashboard/pws/ICAMBSLE2 
--no-prompt --no-backup
2024-02-21T12:15:44.945101+00:00 WeeWX weectl[2869]: ERROR weeutil.startup: 
Cannot load user extensions: No module named 'user'
2024-02-21T12:15:44.974672+00:00 WeeWX weectl[2869]: INFO weectl-station: 
Using Vantage version 3.6.2 (weewx.drivers.vantage)
2024-02-21T12:15:45.030191+00:00 WeeWX systemd[1]: Reloading.
2024-02-21T12:15:45.848292+00:00 WeeWX systemd[1]: Reloading.
2024-02-21T12:15:46.281844+00:00 WeeWX systemd[1]: Started weewx.service - 
WeeWX.
2024-02-21T12:15:46.362945+00:00 WeeWX weewxd[3153]: INFO __main__: 
Initializing weewxd version 5.0.2
2024-02-21T12:15:46.363060+00:00 WeeWX weewxd[3153]: INFO __main__: Command 
line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
2024-02-21T12:15:46.371965+00:00 WeeWX weewxd[3153]: INFO __main__: Using 
Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
2024-02-21T12:15:46.372032+00:00 WeeWX weewxd[3153]: INFO __main__: Located 
at /usr/bin/python3
2024-02-21T12:15:46.374175+00:00 WeeWX weewxd[3153]: INFO __main__: 
Platform Linux-6.1.0-rpi8-rpi-2712-aarch64-with-glibc2.36
2024-02-21T12:15:46.374268+00:00 WeeWX weewxd[3153]: INFO __main__: Locale: 
'en_GB.UTF-8'
2024-02-21T12:15:46.374299+00:00 WeeWX weewxd[3153]: INFO __main__: Entry 
path: /usr/share/weewx/weewxd.py
2024-02-21T12:15:46.374324+00:00 WeeWX weewxd[3153]: INFO __main__: 
WEEWX_ROOT: /etc/weewx
2024-02-21T12:15:46.374352+00:00 WeeWX weewxd[3153]: INFO __main__: 
Configuration file: /etc/weewx/weewx.conf
2024-02-21T12:15:46.374376+00:00 WeeWX weewxd[3153]: INFO __main__: User 
module: /etc/weewx/bin/user
2024-02-21T12:15:46.374401+00:00 WeeWX weewxd[3153]: INFO __main__: Debug: 0
2024-02-21T12:15:46.374584+00:00 WeeWX weewxd[3153]: INFO weewx.engine: 
Loading station type Vantage (weewx.drivers.vantage)
2024-02-21T12:15:46.379577+00:00 WeeWX weewxd[3153]: ERROR weewx.engine: 
Import of driver failed: [Errno 2] could not open port /dev/ttyUSB0: [Errno 
2] No such file or directory: '/dev/ttyUSB0' ()
2024-02-21T12:15:46.382885+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  Traceback (most recent call last):
2024-02-21T12:15:46.384033+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
File "/usr/lib/python3/dist-packages/serial/serialposix.py", 
line 322, in open
2024-02-21T12:15:46.384085+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | 
os.O_NONBLOCK)
2024-02-21T12:15:46.384112+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
   
 ^^
2024-02-21T12:15:46.384136+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/ttyUSB0'
2024-02-21T12:15:46.384173+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  
2024-02-21T12:15:46.384196+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  During handling of the above exception, another exception 
occurred:
2024-02-21T12:15:46.384219+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  
2024-02-21T12:15:46.384240+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  Traceback (most recent call last):
2024-02-21T12:15:46.384261+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/engine.py", line 115, in 
setupStation
2024-02-21T12:15:46.384285+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  self.console = loader_function(config_dict, self)
2024-02-21T12:15:46.384311+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
 ^^
2024-02-21T12:15:46.384339+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in 
loader
2024-02-21T12:15:46.384367+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
  return VantageService(engine, config_dict)
2024-02-21T12:15:46.384391+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 
 ^^^
2024-02-21T12:15:46.384417+00:00 WeeWX weewxd[3153]: CRITICAL weewx.engine: 

[weewx-user] Re: Install of WeeWX 5.0.2 on RPI 5 Failed

[Dave McCreath]

Tom

Many thanks, solved!

sudo usermod -aG dialout weewx.

All up and working fine on the new RPi 5 having followed your magnificent 
guide here:  Moving Weewx to new PC (google.com) 
<https://groups.google.com/g/weewx-user/c/OsQXX2lAtdk>

Regards

Dave

On Wednesday 21 February 2024 at 16:00:54 UTC Dave McCreath wrote:

> I also ran dmesg with the serial adaptor inserted and the following are 
> the last six lines of output: 
>
> [ 1596.869545] usb 3-1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 1596.869548] usb 3-1: Product: CP2102 USB to UART Bridge Controller
> [ 1596.869551] usb 3-1: Manufacturer: Silicon Labs
> [ 1596.869553] usb 3-1: SerialNumber: 0001
> [ 1596.870446] cp210x 3-1:1.0: cp210x converter detected
> [ 1596.873368] usb 3-1: cp210x converter now attached to ttyUSB0
> On Wednesday 21 February 2024 at 13:18:38 UTC Dave McCreath wrote:
>
>> Ville
>>
>> Many thanks for your support.  As requested output of ls /dev/
>>
>> is here:
>>
>> DMac@WeeWX:~ $ ls /dev/
>> autofs   loop1 ram6tty24  tty58  vcsu1
>> blockloop2 ram7tty25  tty59  vcsu2
>> bsg  loop3 ram8tty26  tty6   vcsu3
>> btrfs-controlloop4 ram9tty27  tty60  vcsu4
>> bus  loop5 random  tty28  tty61  vcsu5
>> cachefiles   loop6 rfkill  tty29  tty62  vcsu6
>> cec0 loop7 rtc tty3   tty63  vcsu7
>> cec1 loop-control  rtc0tty30  tty7   vga_arbiter
>> char mappersda tty31  tty8   vhci
>> console  media0sda1tty32  tty9   vhost-net
>> cpu_dma_latency  media1serial  tty33  ttyAMA10   vhost-vsock
>> cuse media2serial0 tty34  ttyprintk  video19
>> disk mem   sg0 tty35  ttyUSB0video20
>> dma_heap mmcblk0   shm tty36  uhid   video21
>> dri  mmcblk0p1 snd tty37  uinput video22
>> fd   mmcblk0p2 spidev10.0  tty38  urandomvideo23
>> full mqueuestderr  tty39  v4lvideo24
>> fuse net   stdin   tty4   vantagevideo25
>> gpiochip0null  stdout  tty40  vcio   video26
>> gpiochip1port  tty tty41  vc-mem video27
>> gpiochip2ppp   tty0tty42  vcsvideo28
>> gpiochip3pps0  tty1tty43  vcs1   video29
>> gpiochip4ptmx  tty10   tty44  vcs2   video30
>> gpiomem0 ptp0  tty11   tty45  vcs3   video31
>> gpiomem1 pts   tty12   tty46  vcs4   video32
>> gpiomem2 ram0  tty13   tty47  vcs5   video33
>> gpiomem3 ram1  tty14   tty48  vcs6   video34
>> gpiomem4 ram10 tty15   tty49  vcs7   video35
>> hwrngram11 tty16   tty5   vcsa   video36
>> i2c-11   ram12 tty17   tty50  vcsa1  video37
>> i2c-12   ram13 tty18   tty51  vcsa2  watchdog
>> initctl  ram14 tty19   tty52  vcsa3  watchdog0
>> inputram15 tty2tty53  vcsa4  zero
>> kmsg ram2  tty20   tty54  vcsa5
>> kvm  ram3  tty21   tty55  vcsa6
>> log  ram4  tty22   tty56  vcsa7
>> loop0ram5  tty23   tty57  vcsu
>>
>> Regards
>>
>> Dave
>>
>>
>> On Wednesday 21 February 2024 at 12:49:42 UTC vhel...@gmail.com wrote:
>>
>>> Hi,
>>>
>>> Plug the USB serial converter with weatherstation plugged to your RPI5.
>>> Check from linux terminal command: ls /dev/ to see is your logger there.
>>> Paste the results of: ls /dev/ here.
>>>
>>> -Ville-
>>>
>>>
>>> keskiviikko 21. helmikuuta 2024 klo 14.38.36 UTC+2 Dave McCreath 
>>> kirjoitti:
>>>
>>>> Recently acquired an RPi 5 and decided this morning to migrate WeeWX 
>>>> over to it from an up to date RPi 4.
>>>>
>>>> Three attempts, all failed with the same errors.  I have tried with 
>>>> both the USB serial connector inserted and without.  I'm running the RPi 
>>>> headless over VNC and nothing else plugged into it at all apart from the 
>>>> power lead.
>>>>
>>>> *Log:

[weewx-user] Re: Install of WeeWX 5.0.2 on RPI 5 Failed

[Dave McCreath]

I also ran dmesg with the serial adaptor inserted and the following are the 
last six lines of output: 

[ 1596.869545] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 1596.869548] usb 3-1: Product: CP2102 USB to UART Bridge Controller
[ 1596.869551] usb 3-1: Manufacturer: Silicon Labs
[ 1596.869553] usb 3-1: SerialNumber: 0001
[ 1596.870446] cp210x 3-1:1.0: cp210x converter detected
[ 1596.873368] usb 3-1: cp210x converter now attached to ttyUSB0
On Wednesday 21 February 2024 at 13:18:38 UTC Dave McCreath wrote:

> Ville
>
> Many thanks for your support.  As requested output of ls /dev/
>
> is here:
>
> DMac@WeeWX:~ $ ls /dev/
> autofs   loop1 ram6tty24  tty58  vcsu1
> blockloop2 ram7tty25  tty59  vcsu2
> bsg  loop3 ram8tty26  tty6   vcsu3
> btrfs-controlloop4 ram9tty27  tty60  vcsu4
> bus  loop5 random  tty28  tty61  vcsu5
> cachefiles   loop6 rfkill  tty29  tty62  vcsu6
> cec0 loop7 rtc tty3   tty63  vcsu7
> cec1 loop-control  rtc0tty30  tty7   vga_arbiter
> char mappersda tty31  tty8   vhci
> console  media0sda1tty32  tty9   vhost-net
> cpu_dma_latency  media1serial  tty33  ttyAMA10   vhost-vsock
> cuse media2serial0 tty34  ttyprintk  video19
> disk mem   sg0 tty35  ttyUSB0video20
> dma_heap mmcblk0   shm tty36  uhid   video21
> dri  mmcblk0p1 snd tty37  uinput video22
> fd   mmcblk0p2 spidev10.0  tty38  urandomvideo23
> full mqueuestderr  tty39  v4lvideo24
> fuse net   stdin   tty4   vantagevideo25
> gpiochip0null  stdout  tty40  vcio   video26
> gpiochip1port  tty tty41  vc-mem video27
> gpiochip2ppp   tty0tty42  vcsvideo28
> gpiochip3pps0  tty1tty43  vcs1   video29
> gpiochip4ptmx  tty10   tty44  vcs2   video30
> gpiomem0 ptp0  tty11   tty45  vcs3   video31
> gpiomem1 pts   tty12   tty46  vcs4   video32
> gpiomem2 ram0  tty13   tty47  vcs5   video33
> gpiomem3 ram1  tty14   tty48  vcs6   video34
> gpiomem4 ram10 tty15   tty49  vcs7   video35
> hwrngram11 tty16   tty5   vcsa   video36
> i2c-11   ram12 tty17   tty50  vcsa1  video37
> i2c-12   ram13 tty18   tty51  vcsa2  watchdog
> initctl  ram14 tty19   tty52  vcsa3  watchdog0
> inputram15 tty2tty53  vcsa4  zero
> kmsg ram2  tty20   tty54  vcsa5
> kvm  ram3  tty21   tty55  vcsa6
> log  ram4  tty22   tty56  vcsa7
> loop0ram5  tty23   tty57  vcsu
>
> Regards
>
> Dave
>
>
> On Wednesday 21 February 2024 at 12:49:42 UTC vhel...@gmail.com wrote:
>
>> Hi,
>>
>> Plug the USB serial converter with weatherstation plugged to your RPI5.
>> Check from linux terminal command: ls /dev/ to see is your logger there.
>> Paste the results of: ls /dev/ here.
>>
>> -Ville-
>>
>>
>> keskiviikko 21. helmikuuta 2024 klo 14.38.36 UTC+2 Dave McCreath 
>> kirjoitti:
>>
>>> Recently acquired an RPi 5 and decided this morning to migrate WeeWX 
>>> over to it from an up to date RPi 4.
>>>
>>> Three attempts, all failed with the same errors.  I have tried with both 
>>> the USB serial connector inserted and without.  I'm running the RPi 
>>> headless over VNC and nothing else plugged into it at all apart from the 
>>> power lead.
>>>
>>> *Log:*
>>>
>>>  2024-02-21T12:15:44.944885+00:00 WeeWX weectl[2869]: INFO weectllib: 
>>> Initializing weectl version 5.0.2
>>> 2024-02-21T12:15:44.945066+00:00 WeeWX weectl[2869]: INFO weectllib: 
>>> Command line: /usr/share/weewx/weectl.py station reconfigure 
>>> --config=/etc/weewx/weewx.conf --driver=weewx.drivers.vantage 
>>> --units=metric --location=Leverington --latitude=52.693 --longitude=0.147 
>>> --altitude=3,meter --register=y --station-url=
>>> https://www.wunderground.com/dashboard/pws/ICAMBSLE2 --no-prompt 
>>> --no-backup
>>> 2024-02-21T12:15:44.945101+00:00 W