[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

Vince,

First step was straightforward, simple use of this instruction (considering 
that the target machine is Raspberry with Raspian Buster (latest):
http://weewx.com/docs/debian.htm
Response from the installation process (directly translated from the dutch 
text):
python-configobj (>= 4.5) but cannot be installed
python-cheetah (>= 2.0) but cannot be installed
python-usb (>= 0.4) but cannot be installed 

After this error report, then I tried this instruction for individual 
installation of the files:
http://weewx.com/docs/setup.htm
Response for each of the files  was that the file could not be found.

Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:

> Please post the exact transcript of everything you did and what the 
> computer returned.
>
> It's fine if you would like to google translate the transcript into 
> English.
>
>
>

-- 
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/03a58c1b-156c-471c-a685-da9e3f2083bdn%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

*Example command-line & response *(with basic translation manually added 
behind each line).
Had to use sudo, because otherwise remark that no admission and question 
whether I have administrator rights.
Python3, because (although Python2.7 is on the machine as part of Domoticz) 
generally I try to apply Python3.x

sudo apt-get install python3-configobj
Pakketlijsten worden ingelezen... Klaar=> 
Packagelist read ... Ready
Boom van vereisten wordt opgebouwd=> Tree 
of Requisites being built
De statusinformatie wordt gelezen... Klaar  => 
Status info being read ... Ready
E: Kan pakket python3-configobj niet vinden   => 
Package python3-configobj cannot be found


Op woensdag 16 december 2020 om 09:24:36 UTC+1 schreef Ton vanN:

> Vince,
>
> First step was straightforward, simple use of this instruction 
> (considering that the target machine is Raspberry with Raspian Buster 
> (latest):
> http://weewx.com/docs/debian.htm
> Response from the installation process (directly translated from the dutch 
> text):
> python-configobj (>= 4.5) but cannot be installed
> python-cheetah (>= 2.0) but cannot be installed
> python-usb (>= 0.4) but cannot be installed 
>
> After this error report, then I tried this instruction for individual 
> installation of the files:
> http://weewx.com/docs/setup.htm
> Response for each of the files  was that the file could not be found.
>
> Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:
>
>> Please post the exact transcript of everything you did and what the 
>> computer returned.
>>
>> It's fine if you would like to google translate the transcript into 
>> English.
>>
>>
>>

-- 
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/4c945063-4f31-4f73-8575-0f15d2cd705cn%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

This morning tried a few more variations as described in the 
setup-instruction, but no luck with modules configobj and usb.
Intending to apply WeeWx, the module for usb is not really required 
(instead a UDP-sniffer to be applied), but configobj seems critical.

Op woensdag 16 december 2020 om 09:36:19 UTC+1 schreef Ton vanN:

> *Example command-line & response *(with basic translation manually added 
> behind each line).
> Had to use sudo, because otherwise remark that no admission and question 
> whether I have administrator rights.
> Python3, because (although Python2.7 is on the machine as part of 
> Domoticz) generally I try to apply Python3.x
>
> sudo apt-get install python3-configobj
> Pakketlijsten worden ingelezen... Klaar=> 
> Packagelist read ... Ready
> Boom van vereisten wordt opgebouwd=> Tree 
> of Requisites being built
> De statusinformatie wordt gelezen... Klaar  => 
> Status info being read ... Ready
> E: Kan pakket python3-configobj niet vinden   => 
> Package python3-configobj cannot be found
>
>
> Op woensdag 16 december 2020 om 09:24:36 UTC+1 schreef Ton vanN:
>
>> Vince,
>>
>> First step was straightforward, simple use of this instruction 
>> (considering that the target machine is Raspberry with Raspian Buster 
>> (latest):
>> http://weewx.com/docs/debian.htm
>> Response from the installation process (directly translated from the 
>> dutch text):
>> python-configobj (>= 4.5) but cannot be installed
>> python-cheetah (>= 2.0) but cannot be installed
>> python-usb (>= 0.4) but cannot be installed 
>>
>> After this error report, then I tried this instruction for individual 
>> installation of the files:
>> http://weewx.com/docs/setup.htm
>> Response for each of the files  was that the file could not be found.
>>
>> Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:
>>
>>> Please post the exact transcript of everything you did and what the 
>>> computer returned.
>>>
>>> It's fine if you would like to google translate the transcript into 
>>> English.
>>>
>>>
>>>

-- 
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/092e3b35-c6aa-4a30-98d6-c54184a91d9bn%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

*Another test from CLI:*
 sudo pip3 install python3-configobj
*Response:*
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting python3-configobj
Could not install packages due to an EnvironmentError: 404 Client Error: 
Not Found for url: https://pypi.org/simple/python3-configobj/

*But latest variation finally was OK!*
sudo pip3 install configobj
*Response:*
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting configobj
  Downloading 
https://www.piwheels.org/simple/configobj/configobj-5.0.6-py3-none-any.whl
Requirement already satisfied: six in /usr/lib/python3/dist-packages (from 
configobj) (1.12.0)
Installing collected packages: configobj
Successfully installed configobj-5.0.6


Op woensdag 16 december 2020 om 09:45:31 UTC+1 schreef Ton vanN:

> This morning tried a few more variations as described in the 
> setup-instruction, but no luck with modules configobj and usb.
> Intending to apply WeeWx, the module for usb is not really required 
> (instead a UDP-sniffer to be applied), but configobj seems critical.
>
> Op woensdag 16 december 2020 om 09:36:19 UTC+1 schreef Ton vanN:
>
>> *Example command-line & response *(with basic translation manually added 
>> behind each line).
>> Had to use sudo, because otherwise remark that no admission and question 
>> whether I have administrator rights.
>> Python3, because (although Python2.7 is on the machine as part of 
>> Domoticz) generally I try to apply Python3.x
>>
>> sudo apt-get install python3-configobj
>> Pakketlijsten worden ingelezen... Klaar=> 
>> Packagelist read ... Ready
>> Boom van vereisten wordt opgebouwd=> Tree 
>> of Requisites being built
>> De statusinformatie wordt gelezen... Klaar  => 
>> Status info being read ... Ready
>> E: Kan pakket python3-configobj niet vinden   => 
>> Package python3-configobj cannot be found
>>
>>
>> Op woensdag 16 december 2020 om 09:24:36 UTC+1 schreef Ton vanN:
>>
>>> Vince,
>>>
>>> First step was straightforward, simple use of this instruction 
>>> (considering that the target machine is Raspberry with Raspian Buster 
>>> (latest):
>>> http://weewx.com/docs/debian.htm
>>> Response from the installation process (directly translated from the 
>>> dutch text):
>>> python-configobj (>= 4.5) but cannot be installed
>>> python-cheetah (>= 2.0) but cannot be installed
>>> python-usb (>= 0.4) but cannot be installed 
>>>
>>> After this error report, then I tried this instruction for individual 
>>> installation of the files:
>>> http://weewx.com/docs/setup.htm
>>> Response for each of the files  was that the file could not be found.
>>>
>>> Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:
>>>
 Please post the exact transcript of everything you did and what the 
 computer returned.

 It's fine if you would like to google translate the transcript into 
 English.




-- 
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/d75d1ea5-a85d-4491-ae8b-876bfa055600n%40googlegroups.com.

[weewx-user] Weewx stops reporting on fixed interval

[Mauro De Lauretis]

Hello,

I have been experiencing an issue for the last two weeks, and so far have 
not been able to determine the cause. I was hoping someone may have some 
ideas.

I am running the Weather34 Skin (
https://github.com/steepleian/weewx-Weather34)
Weewx 4.2.0.
MySQL Database
OS Rasbian on Raspberry

At fixed intervals (7-8 hours, more and less) the system stops entering 
data into the database and upload files into my web server, but I cannot 
see any suitable information or error from the syslog. If I restart Weewx, 
everything turns to work great. Then, after this "famous" 7-8 hours, Weewx 
stops again to report and doesn't work before I make a manually restart.

If anyone has any ideas it would be very much appreciated.

Thanks
Mauro

-- 
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/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

Making progress: 
now weewx up & running with simulator

Next is  linking to a webserver.
Apache already running on all my Raspberries due to Domoticz.
It's folder (within the Domoticz-installation) is /home/pi/domoticz/www
No folder /var/www present
Therefore references in the WeeWx-setup instructions not immediately 
applicable.
Trying to install Apache at another level results in failure, with response 
as described below.

*CLI-input:*
sudo apt-get install apache2 -y   [also tried with apt 
and pip3, without success]
*Response:*
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
Pakket apache2 is niet beschikbaar, hoewel er naar verwezen wordt door
een ander pakket. Mogelijk betekent dit dat het pakket ontbreekt,
verouderd is, of enkel beschikbaar is van een andere bron
E: Pakket 'apache2' heeft geen kandidaat voor installatie

*Google-translated:*
Package lists are being read ... Done 
Tree of requirements is built The status information is being read ... Done 
Package apache2 is not available, although it is referenced by another 
package. This may mean that the package is missing, obsolete, or only 
available from another source 
E: Package 'apache2' has no candidate for installation

Must be people with previous, comparable experience for this configuration:
*what is a practical solution (regardless whether Apache or other 
webserver, but Apache/nginx for Domoticz must remain operational!)?*
Op woensdag 16 december 2020 om 09:57:52 UTC+1 schreef Ton vanN:

> *Another test from CLI:*
>  sudo pip3 install python3-configobj
> *Response:*
> Looking in indexes: https://pypi.org/simple, 
> https://www.piwheels.org/simple
> Collecting python3-configobj
> Could not install packages due to an EnvironmentError: 404 Client Error: 
> Not Found for url: https://pypi.org/simple/python3-configobj/
>
> *But latest variation finally was OK!*
> sudo pip3 install configobj
> *Response:*
> Looking in indexes: https://pypi.org/simple, 
> https://www.piwheels.org/simple
> Collecting configobj
>   Downloading 
> https://www.piwheels.org/simple/configobj/configobj-5.0.6-py3-none-any.whl
> Requirement already satisfied: six in /usr/lib/python3/dist-packages (from 
> configobj) (1.12.0)
> Installing collected packages: configobj
> Successfully installed configobj-5.0.6
>
>
> Op woensdag 16 december 2020 om 09:45:31 UTC+1 schreef Ton vanN:
>
>> This morning tried a few more variations as described in the 
>> setup-instruction, but no luck with modules configobj and usb.
>> Intending to apply WeeWx, the module for usb is not really required 
>> (instead a UDP-sniffer to be applied), but configobj seems critical.
>>
>> Op woensdag 16 december 2020 om 09:36:19 UTC+1 schreef Ton vanN:
>>
>>> *Example command-line & response *(with basic translation manually 
>>> added behind each line).
>>> Had to use sudo, because otherwise remark that no admission and question 
>>> whether I have administrator rights.
>>> Python3, because (although Python2.7 is on the machine as part of 
>>> Domoticz) generally I try to apply Python3.x
>>>
>>> sudo apt-get install python3-configobj
>>> Pakketlijsten worden ingelezen... Klaar
>>> => Packagelist read ... Ready
>>> Boom van vereisten wordt opgebouwd=> 
>>> Tree of Requisites being built
>>> De statusinformatie wordt gelezen... Klaar  => 
>>> Status info being read ... Ready
>>> E: Kan pakket python3-configobj niet vinden   => 
>>> Package python3-configobj cannot be found
>>>
>>>
>>> Op woensdag 16 december 2020 om 09:24:36 UTC+1 schreef Ton vanN:
>>>
 Vince,

 First step was straightforward, simple use of this instruction 
 (considering that the target machine is Raspberry with Raspian Buster 
 (latest):
 http://weewx.com/docs/debian.htm
 Response from the installation process (directly translated from the 
 dutch text):
 python-configobj (>= 4.5) but cannot be installed
 python-cheetah (>= 2.0) but cannot be installed
 python-usb (>= 0.4) but cannot be installed 

 After this error report, then I tried this instruction for individual 
 installation of the files:
 http://weewx.com/docs/setup.htm
 Response for each of the files  was that the file could not be found.

 Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:

> Please post the exact transcript of everything you did and what the 
> computer returned.
>
> It's fine if you would like to google translate the transcript into 
> English.
>
>
>

-- 
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/ms

Re: [weewx-user] Weewx stops reporting on fixed interval

[Tom Keffer]

I know you think the log is uninteresting, but to more experienced eyes, it
may contain some clues. Be sure to set debug=1.

Also, what kind of hardware?

On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis <
mauro.delaure...@gmail.com> wrote:

> Hello,
>
> I have been experiencing an issue for the last two weeks, and so far have
> not been able to determine the cause. I was hoping someone may have some
> ideas.
>
> I am running the Weather34 Skin (
> https://github.com/steepleian/weewx-Weather34)
> Weewx 4.2.0.
> MySQL Database
> OS Rasbian on Raspberry
>
> At fixed intervals (7-8 hours, more and less) the system stops entering
> data into the database and upload files into my web server, but I cannot
> see any suitable information or error from the syslog. If I restart Weewx,
> everything turns to work great. Then, after this "famous" 7-8 hours, Weewx
> stops again to report and doesn't work before I make a manually restart.
>
> If anyone has any ideas it would be very much appreciated.
>
> Thanks
> Mauro
>
> --
> 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/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBi-Kdhb76W2fYTem15DFCaM053kKm%2BezO8XBW-gYAiaA%40mail.gmail.com.

[weewx-user] Re: yet another question to GW1000 api driver mapping

[Vetti52]

Thanks, Gary, for your polite explanations. 
Since I have read some of your comments with equal advices in other 
threads, I proceeded already to sucessfully map the fields. Otherwise I did 
not even had an idea about field_map in GW1000. Sorry, that you need to 
explain again and again the comparison of --live-data and mapped loop data. 
But at that point, I feel better, not to miss any point. Thanks for your 
patience.
Well, data are mapped, weewx running directly gives this output:

$ sudo weewxd /etc/weewx/weewx.conf
LOOP:   2020-12-16 13:29:56 CET (1608121796) altimeter: 30.09246486970751, 
appTemp: 46.07291271146897, barometer: 30.092169667712717, cloudbase: 
944.6426189788297, dateTime: 1608121796, daymaxwind: 3.6, dayRain: 0.0, 
dewpoint: 45.0455158818643, heatindex: 47.4030006, humidex: 
48.934644083871206, inDewpoint: 50.88299985988465, inHumidity: 60, inTemp: 
65.12, luminosity: 8184.0, maxSolarRad: 86.02828823732644, monthRain: 
0.6653543307086613, outHumidity: 87, outTemp: 48.74, pressure: 
29.97589031125, radiation: 64.59352801894238, rain: None, rainEvent: 
0.4015748031496063, rainRate: 0.0, relbarometer: 1019.2, usUnits: 1, UV: 0, 
uvradiation: 6.5, weekRain: 10.9, wh65_battery: 0, windchill: 48.74, 
windDir: 187, windGust: 3.3554127779089566, windGustDir: None, windSpeed: 
2.6843302223271652, yearRain: 29.17716535433071
LOOP:   2020-12-16 13:30:56 CET (1608121856) altimeter: 30.09542729292998, 
appTemp: 45.69491271146897, barometer: 30.095134121428384, cloudbase: 
944.6426189788297, dateTime: 1608121856, daymaxwind: 3.6, dayRain: 0.0, 
dewpoint: 45.0455158818643, heatindex: 47.4030006, humidex: 
48.934644083871206, inDewpoint: 50.88299985988465, inHumidity: 60, inTemp: 
65.12, luminosity: 8075.0, maxSolarRad: 85.3176898825967, monthRain: 
0.6653543307086613, outHumidity: 87, outTemp: 48.74, pressure: 
29.97884331002, radiation: 63.73322809786898, rain: 0.0, rainEvent: 
0.4015748031496063, rainRate: 0.0, relbarometer: 1019.3, usUnits: 1, UV: 0, 
uvradiation: 6.4, weekRain: 10.9, wh65_battery: 0, windchill: 
47.93087953525257, windDir: 162, windGust: 5.816048815042191, windGustDir: 
None, windSpeed: 3.3554127779089566, yearRain: 29.17716535433071
REC:2020-12-16 13:30:00 CET (1608121800) altimeter: 30.09246486970751, 
appTemp: 46.07291271146897, barometer: 30.092169667712717, cloudbase: 
944.6426189788297, dateTime: 1608121800, daymaxwind: 3.6, dayRain: 0.0, 
dewpoint: 45.0455158818643, ET: 0.00012174671890853505, extraTemp1: 
124.894399, heatindex: 47.4030006, humidex: 
48.934644083871206, inDewpoint: 50.88299985988465, inHumidity: 60.0, 
inTemp: 65.12, interval: 5.0, luminosity: 8184.0, maxSolarRad: 
86.02828823732644, monthRain: 0.6653543307086613, outHumidity: 87.0, 
outTemp: 48.74, pressure: 29.97589031125, radiation: 64.59352801894238, 
rain: 0.0, rainEvent: 0.4015748031496063, rainRate: 0.0, relbarometer: 
1019.2, usUnits: 1, UV: 0.0, uvradiation: 6.5, weekRain: 10.9, wh65_battery: 
0.0, windchill: 48.74, windDir: 187.0, windGust: 3.3554127779089566, 
windGustDir: 187, windrun: 0.22369418519393044, windSpeed: 
2.6843302223271652, yearRain: 29.17716535433071

So I am glad to see, that the StdArchive service is ok. Right?

Your last question needs some explanation and preparation: I am no longer 
bothering with rainEvent, as this works now as expected. Thus, my approach 
focussing wh65_battery data, was, that I looked at the output the value of $x 
in sensors.inc. So, when interpreting your question, I should not print $x, 
but $current.rainEvent.raw instead at the same place? Sorry for the dumb 
question, but I do not clearly understand the difference between $current 
and $current.raw. To me the format of the recorded battery value is a 
decimal number. When using interceptor's Ecowitt-client, $x returns this 
value as a decimal number 0.0 as well. So, do you expect, that in case of 
GW1000 the recorded number is converted into a string and thus not 
evaluated in #if $x == 0 ? Said that, should I simply compare the output of 
$current.wh65_batt and $current.wh65_batt.raw instead of $x at the same 
place I depicted above?

Peter
gjr80 schrieb am Dienstag, 15. Dezember 2020 um 23:51:10 UTC+1:

> Some comments below. Hopefully it gives you a process to work through to 
> identify your problem.
>
> Gary
>
> On Wednesday, 16 December 2020 at 06:37:40 UTC+10 Vetti52 wrote:
>
>> Well, I started this conversation already at another thread (
>> https://groups.google.com/g/weewx-user/c/ua0JjTp1DW8/m/AFGZf7AyAgAJ), 
>> concerning wind.gust.dir in version 4.2.0. As TK managed to solve the main 
>> problem, there is still the other part unsolved. So, I want to move this 
>> topic into a new thread, knowing, that there were similar questions during 
>> the last months, whicht could help only partially.
>>
>> I am not able to change from interceptor's ecowitt-client to GW1000 
>> without loss of some data. Gary provided the crucial hints in the thread 
>> menti

Re: [weewx-user] Wind Rose empty in Steel Series

[Tom Keffer]

You have the correct configuration, but remember, it only applies *when the
database is created*. Thereafter, the schema is read from the database.

You can try rebuilding the daily summaries using wee_database:

*sudo wee_database --drop-daily*
*sudo wee_database --rebuild-daily*


The rebuild will use the configuration in weewx.conf.

-tk

On Tue, Dec 15, 2020 at 9:58 PM fpb  wrote:

> @Tom,
>
> I'm having a similar issue but I'm trying to figure out what the correct
> schema (assuming that is the issue)  but I can't find a combination.
>
> This is what I have;
>
> [DataBindings]
>
> [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.manager.DaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview_extended.schema
> [[forecast_binding]]
> database = forecast_sqlite
>
> and below my log errors;
>
> ec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator:
> Generate failed with exception ''
>
> Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
> Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl
>
> Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
> Reason: cannot find 'raw' while searching for 'day.wind.count.raw'
>
> Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
> Traceback (most recent call last):
>
> Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in generate
>
> Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
> unicode_string = compiled_template.respond()
>
> Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
>   File "_etc_weewx_skins_Seasons_NOAA_NOAA__Y__m_txt_tmpl.py", line 430, in
> respond
>
> Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
> NotFound: cannot find 'raw' while searching for 'day.wind.count.raw'
> Any help will be appreciate.
>
> On Thursday, June 4, 2020 at 6:01:51 PM UTC-4 tke...@gmail.com wrote:
>
>> That's probably what happened.
>>
>> You're not the first to get tripped up by this. Obviously, I need to
>> rethink how to manage the transition to the new way of specifying schemas.
>>
>> On Thu, Jun 4, 2020 at 11:20 AM Jacques Terrettaz 
>> wrote:
>>
>>> Forget my last message :  I used a new Raspberry PI to install weewx V4,
>>> and then I transferred my "old" mysql database  to the new installation...
>>>
>>>
>>> Le 4 juin 2020 à 20:01, Jacques Terrettaz  a écrit :
>>>
>>> Tom,
>>>
>>> One comment about the old and new database schema :  I didn't change
>>> anything by myself in the [DataBinding] section of weewx.conf after  the
>>> upgrade to V4.0, so I suspect that the  manager = weewx.manager.
>>> DaySummaryManager  line  was automatically modified during the upgrade
>>> process.
>>> Is it right ?
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/ACB63400-3370-43DF-A186-A96D3BC23AA3%40gmail.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/d4d9e47e-ca30-4729-a81b-9d1cfd8dde76n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBpdUpek-t%3DKF7LNX41BB%3DyaJsei8CQGMmuPOS5HYGT2Q%40mail.gmail.com.

Re: [weewx-user] Weewx stops reporting on fixed interval

[Mauro De Lauretis]

Hi Tom,
I've never thought that the log is interesting, simply I was not able to 
see where the error is. :-)

Station Hardware is a Davis Vantage Pro2, while the debug is already set to 
debug = 1.

Regards
Mauro

Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1 tke...@gmail.com 
ha scritto:

> I know you think the log is uninteresting, but to more experienced eyes, 
> it may contain some clues. Be sure to set debug=1.
>
> Also, what kind of hardware?
>
> On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis  
> wrote:
>
>> Hello,
>>
>> I have been experiencing an issue for the last two weeks, and so far have 
>> not been able to determine the cause. I was hoping someone may have some 
>> ideas.
>>
>> I am running the Weather34 Skin (
>> https://github.com/steepleian/weewx-Weather34)
>> Weewx 4.2.0.
>> MySQL Database
>> OS Rasbian on Raspberry
>>
>> At fixed intervals (7-8 hours, more and less) the system stops entering 
>> data into the database and upload files into my web server, but I cannot 
>> see any suitable information or error from the syslog. If I restart Weewx, 
>> everything turns to work great. Then, after this "famous" 7-8 hours, Weewx 
>> stops again to report and doesn't work before I make a manually restart.
>>
>> If anyone has any ideas it would be very much appreciated.
>>
>> Thanks
>> Mauro
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com.

Re: [weewx-user] Weewx stops reporting on fixed interval

[Tom Keffer]

Sorry, but it does not look like you attached the log.

On Wed, Dec 16, 2020 at 5:32 AM Mauro De Lauretis <
mauro.delaure...@gmail.com> wrote:

> Hi Tom,
> I've never thought that the log is interesting, simply I was not able to
> see where the error is. :-)
>
> Station Hardware is a Davis Vantage Pro2, while the debug is already set
> to debug = 1.
>
> Regards
> Mauro
>
> Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1 tke...@gmail.com
> ha scritto:
>
>> I know you think the log is uninteresting, but to more experienced eyes,
>> it may contain some clues. Be sure to set debug=1.
>>
>> Also, what kind of hardware?
>>
>> On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis 
>> wrote:
>>
>>> Hello,
>>>
>>> I have been experiencing an issue for the last two weeks, and so far
>>> have not been able to determine the cause. I was hoping someone may have
>>> some ideas.
>>>
>>> I am running the Weather34 Skin (
>>> https://github.com/steepleian/weewx-Weather34)
>>> Weewx 4.2.0.
>>> MySQL Database
>>> OS Rasbian on Raspberry
>>>
>>> At fixed intervals (7-8 hours, more and less) the system stops entering
>>> data into the database and upload files into my web server, but I cannot
>>> see any suitable information or error from the syslog. If I restart Weewx,
>>> everything turns to work great. Then, after this "famous" 7-8 hours, Weewx
>>> stops again to report and doesn't work before I make a manually restart.
>>>
>>> If anyone has any ideas it would be very much appreciated.
>>>
>>> Thanks
>>> Mauro
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDiZhdseb3a%3D0TWNz6xJY7-ptn6jhwe4TJLEF7LA4uX3Q%40mail.gmail.com.

Re: [weewx-user] Weewx stops reporting on fixed interval

[Mauro De Lauretis]

You're right, Tom.
If not attached the log because I should copy and paste you the exactly 
moment when Weewx stops reporting, but how can I do it when I'm not logged 
on my Raspberry when it happens? Are there other possibilities?





Il giorno mercoledì 16 dicembre 2020 alle 14:41:45 UTC+1 tke...@gmail.com 
ha scritto:

> Sorry, but it does not look like you attached the log.
>
> On Wed, Dec 16, 2020 at 5:32 AM Mauro De Lauretis  
> wrote:
>
>> Hi Tom,
>> I've never thought that the log is interesting, simply I was not able to 
>> see where the error is. :-)
>>
>> Station Hardware is a Davis Vantage Pro2, while the debug is already set 
>> to debug = 1.
>>
>> Regards
>> Mauro
>>
>> Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1 tke...@gmail.com 
>> ha scritto:
>>
>>> I know you think the log is uninteresting, but to more experienced eyes, 
>>> it may contain some clues. Be sure to set debug=1.
>>>
>>> Also, what kind of hardware?
>>>
>>> On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis  
>>> wrote:
>>>
 Hello,

 I have been experiencing an issue for the last two weeks, and so far 
 have not been able to determine the cause. I was hoping someone may have 
 some ideas.

 I am running the Weather34 Skin (
 https://github.com/steepleian/weewx-Weather34)
 Weewx 4.2.0.
 MySQL Database
 OS Rasbian on Raspberry

 At fixed intervals (7-8 hours, more and less) the system stops entering 
 data into the database and upload files into my web server, but I cannot 
 see any suitable information or error from the syslog. If I restart Weewx, 
 everything turns to work great. Then, after this "famous" 7-8 hours, Weewx 
 stops again to report and doesn't work before I make a manually restart.

 If anyone has any ideas it would be very much appreciated.

 Thanks
 Mauro

 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fe500236-0b9c-4db4-a555-57c78ec08e06n%40googlegroups.com.

Re: [weewx-user] Weewx stops reporting on fixed interval

[Tom Keffer]

If you can ssh into your RPi, you could scp the log to
somewhere convenient. Then upload it to a cloud service such as pastebin.com
.

Alternatively, you can use a text editor to trim it down to the essentials,
then post it here. But, please don't post anything too big here.

-tk

On Wed, Dec 16, 2020 at 6:04 AM Mauro De Lauretis <
mauro.delaure...@gmail.com> wrote:

> You're right, Tom.
> If not attached the log because I should copy and paste you the exactly
> moment when Weewx stops reporting, but how can I do it when I'm not logged
> on my Raspberry when it happens? Are there other possibilities?
>
>
>
>
>
> Il giorno mercoledì 16 dicembre 2020 alle 14:41:45 UTC+1 tke...@gmail.com
> ha scritto:
>
>> Sorry, but it does not look like you attached the log.
>>
>> On Wed, Dec 16, 2020 at 5:32 AM Mauro De Lauretis 
>> wrote:
>>
>>> Hi Tom,
>>> I've never thought that the log is interesting, simply I was not able to
>>> see where the error is. :-)
>>>
>>> Station Hardware is a Davis Vantage Pro2, while the debug is already set
>>> to debug = 1.
>>>
>>> Regards
>>> Mauro
>>>
>>> Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1
>>> tke...@gmail.com ha scritto:
>>>
 I know you think the log is uninteresting, but to more experienced
 eyes, it may contain some clues. Be sure to set debug=1.

 Also, what kind of hardware?

 On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis <
 mauro.de...@gmail.com> wrote:

> Hello,
>
> I have been experiencing an issue for the last two weeks, and so far
> have not been able to determine the cause. I was hoping someone may have
> some ideas.
>
> I am running the Weather34 Skin (
> https://github.com/steepleian/weewx-Weather34)
> Weewx 4.2.0.
> MySQL Database
> OS Rasbian on Raspberry
>
> At fixed intervals (7-8 hours, more and less) the system stops
> entering data into the database and upload files into my web server, but I
> cannot see any suitable information or error from the syslog. If I restart
> Weewx, everything turns to work great. Then, after this "famous" 7-8 
> hours,
> Weewx stops again to report and doesn't work before I make a manually
> restart.
>
> If anyone has any ideas it would be very much appreciated.
>
> Thanks
> Mauro
>
> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
> 
> .
>
 --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/fe500236-0b9c-4db4-a555-57c78ec08e06n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECM0Z7AUsvJ%3DDYycXRf4hJc-3zzF8zPobkdo84JcYPppA%40mail.gmail.com.

Re: [weewx-user] Weewx stops reporting on fixed interval

[Mauro De Lauretis]

Yes, I can ssh into my RPi, but I don't know how to scp the log.

Il giorno mercoledì 16 dicembre 2020 alle 15:28:09 UTC+1 tke...@gmail.com 
ha scritto:

> If you can ssh into your RPi, you could scp the log to 
> somewhere convenient. Then upload it to a cloud service such as 
> pastebin.com. 
>
> Alternatively, you can use a text editor to trim it down to the 
> essentials, then post it here. But, please don't post anything too big here.
>
> -tk
>
> On Wed, Dec 16, 2020 at 6:04 AM Mauro De Lauretis  
> wrote:
>
>> You're right, Tom.
>> If not attached the log because I should copy and paste you the exactly 
>> moment when Weewx stops reporting, but how can I do it when I'm not logged 
>> on my Raspberry when it happens? Are there other possibilities?
>>
>>
>>
>>
>>
>> Il giorno mercoledì 16 dicembre 2020 alle 14:41:45 UTC+1 tke...@gmail.com 
>> ha scritto:
>>
>>> Sorry, but it does not look like you attached the log.
>>>
>>> On Wed, Dec 16, 2020 at 5:32 AM Mauro De Lauretis  
>>> wrote:
>>>
 Hi Tom,
 I've never thought that the log is interesting, simply I was not able 
 to see where the error is. :-)

 Station Hardware is a Davis Vantage Pro2, while the debug is already 
 set to debug = 1.

 Regards
 Mauro

 Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1 
 tke...@gmail.com ha scritto:

> I know you think the log is uninteresting, but to more experienced 
> eyes, it may contain some clues. Be sure to set debug=1.
>
> Also, what kind of hardware?
>
> On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis <
> mauro.de...@gmail.com> wrote:
>
>> Hello,
>>
>> I have been experiencing an issue for the last two weeks, and so far 
>> have not been able to determine the cause. I was hoping someone may have 
>> some ideas.
>>
>> I am running the Weather34 Skin (
>> https://github.com/steepleian/weewx-Weather34)
>> Weewx 4.2.0.
>> MySQL Database
>> OS Rasbian on Raspberry
>>
>> At fixed intervals (7-8 hours, more and less) the system stops 
>> entering data into the database and upload files into my web server, but 
>> I 
>> cannot see any suitable information or error from the syslog. If I 
>> restart 
>> Weewx, everything turns to work great. Then, after this "famous" 7-8 
>> hours, 
>> Weewx stops again to report and doesn't work before I make a manually 
>> restart.
>>
>> If anyone has any ideas it would be very much appreciated.
>>
>> Thanks
>> Mauro
>>
>> -- 
>> You received this message because you are subscribed to the Google 
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/fe500236-0b9c-4db4-a555-57c78ec08e06n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ad557cfe-18ca-4cdd-b628-186faa63d1a9n%40googlegroups.com.

Re: [weewx-user] Weewx stops reporting on fixed interval

[Karen K]

on the computer where you run ssh:
scp root@rpi/var/log/syslog .

Please, note the dot at the end. Replace "rpi" by the IP address or name of 
your RPi. May be, you need to replace "root" by "pi" or "user" to get it 
work.

After that you will find a file named "syslog" in the current directory. 
You can open it with any text editor.

Mauro De Lauretis schrieb am Mittwoch, 16. Dezember 2020 um 16:03:17 UTC+1:

> Yes, I can ssh into my RPi, but I don't know how to scp the log.
>
> Il giorno mercoledì 16 dicembre 2020 alle 15:28:09 UTC+1 tke...@gmail.com 
> ha scritto:
>
>> If you can ssh into your RPi, you could scp the log to 
>> somewhere convenient. Then upload it to a cloud service such as 
>> pastebin.com. 
>>
>> Alternatively, you can use a text editor to trim it down to the 
>> essentials, then post it here. But, please don't post anything too big here.
>>
>> -tk
>>
>> On Wed, Dec 16, 2020 at 6:04 AM Mauro De Lauretis  
>> wrote:
>>
>>> You're right, Tom.
>>> If not attached the log because I should copy and paste you the exactly 
>>> moment when Weewx stops reporting, but how can I do it when I'm not logged 
>>> on my Raspberry when it happens? Are there other possibilities?
>>>
>>>
>>>
>>>
>>>
>>> Il giorno mercoledì 16 dicembre 2020 alle 14:41:45 UTC+1 
>>> tke...@gmail.com ha scritto:
>>>
 Sorry, but it does not look like you attached the log.

 On Wed, Dec 16, 2020 at 5:32 AM Mauro De Lauretis <
 mauro.de...@gmail.com> wrote:

> Hi Tom,
> I've never thought that the log is interesting, simply I was not able 
> to see where the error is. :-)
>
> Station Hardware is a Davis Vantage Pro2, while the debug is already 
> set to debug = 1.
>
> Regards
> Mauro
>
> Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1 
> tke...@gmail.com ha scritto:
>
>> I know you think the log is uninteresting, but to more experienced 
>> eyes, it may contain some clues. Be sure to set debug=1.
>>
>> Also, what kind of hardware?
>>
>> On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis <
>> mauro.de...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I have been experiencing an issue for the last two weeks, and so far 
>>> have not been able to determine the cause. I was hoping someone may 
>>> have 
>>> some ideas.
>>>
>>> I am running the Weather34 Skin (
>>> https://github.com/steepleian/weewx-Weather34)
>>> Weewx 4.2.0.
>>> MySQL Database
>>> OS Rasbian on Raspberry
>>>
>>> At fixed intervals (7-8 hours, more and less) the system stops 
>>> entering data into the database and upload files into my web server, 
>>> but I 
>>> cannot see any suitable information or error from the syslog. If I 
>>> restart 
>>> Weewx, everything turns to work great. Then, after this "famous" 7-8 
>>> hours, 
>>> Weewx stops again to report and doesn't work before I make a manually 
>>> restart.
>>>
>>> If anyone has any ideas it would be very much appreciated.
>>>
>>> Thanks
>>> Mauro
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, 
>>> send an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
> You received this message because you are subscribed to the Google 
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to weewx-user+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/fe500236-0b9c-4db4-a555-57c78ec08e06n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails fr

Re: [weewx-user] Weewx stops reporting on fixed interval

[Karen K]

on the computer where you run ssh:
scp root@rpi:/var/log/syslog .

Please, note the dot at the end. Replace "rpi" by the IP address or name of 
your RPi. May be, you need to replace "root" by "pi" or "user" to get it 
work.

After that you will find a file named "syslog" in the current directory. 
You can open it with any text editor.


Mauro De Lauretis schrieb am Mittwoch, 16. Dezember 2020 um 16:03:17 UTC+1:

> Yes, I can ssh into my RPi, but I don't know how to scp the log.
>
> Il giorno mercoledì 16 dicembre 2020 alle 15:28:09 UTC+1 tke...@gmail.com 
> ha scritto:
>
>> If you can ssh into your RPi, you could scp the log to 
>> somewhere convenient. Then upload it to a cloud service such as 
>> pastebin.com. 
>>
>> Alternatively, you can use a text editor to trim it down to the 
>> essentials, then post it here. But, please don't post anything too big here.
>>
>> -tk
>>
>> On Wed, Dec 16, 2020 at 6:04 AM Mauro De Lauretis  
>> wrote:
>>
>>> You're right, Tom.
>>> If not attached the log because I should copy and paste you the exactly 
>>> moment when Weewx stops reporting, but how can I do it when I'm not logged 
>>> on my Raspberry when it happens? Are there other possibilities?
>>>
>>>
>>>
>>>
>>>
>>> Il giorno mercoledì 16 dicembre 2020 alle 14:41:45 UTC+1 
>>> tke...@gmail.com ha scritto:
>>>
 Sorry, but it does not look like you attached the log.

 On Wed, Dec 16, 2020 at 5:32 AM Mauro De Lauretis <
 mauro.de...@gmail.com> wrote:

> Hi Tom,
> I've never thought that the log is interesting, simply I was not able 
> to see where the error is. :-)
>
> Station Hardware is a Davis Vantage Pro2, while the debug is already 
> set to debug = 1.
>
> Regards
> Mauro
>
> Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1 
> tke...@gmail.com ha scritto:
>
>> I know you think the log is uninteresting, but to more experienced 
>> eyes, it may contain some clues. Be sure to set debug=1.
>>
>> Also, what kind of hardware?
>>
>> On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis <
>> mauro.de...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I have been experiencing an issue for the last two weeks, and so far 
>>> have not been able to determine the cause. I was hoping someone may 
>>> have 
>>> some ideas.
>>>
>>> I am running the Weather34 Skin (
>>> https://github.com/steepleian/weewx-Weather34)
>>> Weewx 4.2.0.
>>> MySQL Database
>>> OS Rasbian on Raspberry
>>>
>>> At fixed intervals (7-8 hours, more and less) the system stops 
>>> entering data into the database and upload files into my web server, 
>>> but I 
>>> cannot see any suitable information or error from the syslog. If I 
>>> restart 
>>> Weewx, everything turns to work great. Then, after this "famous" 7-8 
>>> hours, 
>>> Weewx stops again to report and doesn't work before I make a manually 
>>> restart.
>>>
>>> If anyone has any ideas it would be very much appreciated.
>>>
>>> Thanks
>>> Mauro
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, 
>>> send an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
> You received this message because you are subscribed to the Google 
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to weewx-user+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/fe500236-0b9c-4db4-a555-57c78ec08e06n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails 

[weewx-user] Re: yet another question to GW1000 api driver mapping

[Vetti52]

As I could not wait for an answer, I tried to replace $x in the example 
mentioned above (marked in yellow) by any of the supposed expressions. But 
in any case I get this type of error:
 ERROR weewx.cheetahgenerator: Generate failed with exception ''
 ERROR weewx.cheetahgenerator:  Ignoring template 
/etc/weewx/skins/alltimeSeasons/index.html.tmpl
 ERROR weewx.cheetahgenerator:  Reason: 'UnknownType' object is not 
subscriptable

neither $get_battery_status($current.wh65_batt.raw) nor $current.wh65_batt or 
$current.wh65_battery or any other combination works. I must admit, that I 
do not understand, what I am doing. This python coils. 
Vetti52 schrieb am Mittwoch, 16. Dezember 2020 um 14:18:26 UTC+1:

> Thanks, Gary, for your polite explanations. 
> Since I have read some of your comments with equal advices in other 
> threads, I proceeded already to sucessfully map the fields. Otherwise I did 
> not even had an idea about field_map in GW1000. Sorry, that you need to 
> explain again and again the comparison of --live-data and mapped loop data. 
> But at that point, I feel better, not to miss any point. Thanks for your 
> patience.
> Well, data are mapped, weewx running directly gives this output:
>
> $ sudo weewxd /etc/weewx/weewx.conf
> LOOP:   2020-12-16 13:29:56 CET (1608121796) altimeter: 30.09246486970751, 
> appTemp: 46.07291271146897, barometer: 30.092169667712717, cloudbase: 
> 944.6426189788297, dateTime: 1608121796, daymaxwind: 3.6, dayRain: 0.0, 
> dewpoint: 45.0455158818643, heatindex: 47.4030006, humidex: 
> 48.934644083871206, inDewpoint: 50.88299985988465, inHumidity: 60, inTemp: 
> 65.12, luminosity: 8184.0, maxSolarRad: 86.02828823732644, monthRain: 
> 0.6653543307086613, outHumidity: 87, outTemp: 48.74, pressure: 
> 29.97589031125, radiation: 64.59352801894238, rain: None, rainEvent: 
> 0.4015748031496063, rainRate: 0.0, relbarometer: 1019.2, usUnits: 1, UV: 
> 0, uvradiation: 6.5, weekRain: 10.9, wh65_battery: 0, windchill: 48.74, 
> windDir: 187, windGust: 3.3554127779089566, windGustDir: None, windSpeed: 
> 2.6843302223271652, yearRain: 29.17716535433071
> LOOP:   2020-12-16 13:30:56 CET (1608121856) altimeter: 30.09542729292998, 
> appTemp: 45.69491271146897, barometer: 30.095134121428384, cloudbase: 
> 944.6426189788297, dateTime: 1608121856, daymaxwind: 3.6, dayRain: 0.0, 
> dewpoint: 45.0455158818643, heatindex: 47.4030006, humidex: 
> 48.934644083871206, inDewpoint: 50.88299985988465, inHumidity: 60, inTemp: 
> 65.12, luminosity: 8075.0, maxSolarRad: 85.3176898825967, monthRain: 
> 0.6653543307086613, outHumidity: 87, outTemp: 48.74, pressure: 
> 29.97884331002, radiation: 63.73322809786898, rain: 0.0, rainEvent: 
> 0.4015748031496063, rainRate: 0.0, relbarometer: 1019.3, usUnits: 1, UV: 
> 0, uvradiation: 6.4, weekRain: 10.9, wh65_battery: 0, windchill: 
> 47.93087953525257, windDir: 162, windGust: 5.816048815042191, windGustDir: 
> None, windSpeed: 3.3554127779089566, yearRain: 29.17716535433071
> REC:2020-12-16 13:30:00 CET (1608121800) altimeter: 
> 30.09246486970751, appTemp: 46.07291271146897, barometer: 
> 30.092169667712717, cloudbase: 944.6426189788297, dateTime: 1608121800, 
> daymaxwind: 3.6, dayRain: 0.0, dewpoint: 45.0455158818643, ET: 
> 0.00012174671890853505, extraTemp1: 124.894399, heatindex: 
> 47.4030006, humidex: 48.934644083871206, inDewpoint: 
> 50.88299985988465, inHumidity: 60.0, inTemp: 65.12, interval: 5.0, 
> luminosity: 8184.0, maxSolarRad: 86.02828823732644, monthRain: 
> 0.6653543307086613, outHumidity: 87.0, outTemp: 48.74, pressure: 
> 29.97589031125, radiation: 64.59352801894238, rain: 0.0, rainEvent: 
> 0.4015748031496063, rainRate: 0.0, relbarometer: 1019.2, usUnits: 1, UV: 
> 0.0, uvradiation: 6.5, weekRain: 10.9, wh65_battery: 0.0, windchill: 
> 48.74, windDir: 187.0, windGust: 3.3554127779089566, windGustDir: 187, 
> windrun: 0.22369418519393044, windSpeed: 2.6843302223271652, yearRain: 
> 29.17716535433071
>
> So I am glad to see, that the StdArchive service is ok. Right?
>
> Your last question needs some explanation and preparation: I am no longer 
> bothering with rainEvent, as this works now as expected. Thus, my approach 
> focussing wh65_battery data, was, that I looked at the output the value 
> of $x in sensors.inc. So, when interpreting your question, I should not 
> print $x, but $current.rainEvent.raw instead at the same place? Sorry for 
> the dumb question, but I do not clearly understand the difference between 
> $current and $current.raw. To me the format of the recorded battery value 
> is a decimal number. When using interceptor's Ecowitt-client, $x returns 
> this value as a decimal number 0.0 as well. So, do you expect, that in case 
> of GW1000 the recorded number is converted into a string and thus not 
> evaluated in #if $x == 0 ? Said that, should I simply compare the output 
> of $current.wh65_batt and $current.wh65_batt.raw instead of $x at the 
> same place I depicted

[weewx-user] Re: Installation of version 4.2.0

[vince]

I would simply symlink 'from' the existing tree 'to' the weewx directory:
   ln -s /home/weewx/public_html /home/pi/domoticz/www/weewx

Then you should see the web pages from weewx in your web if you use 
http://hostname/weewx 



-- 
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/2c13187b-ddd3-4692-879d-7d2e440f8427n%40googlegroups.com.

Re: [weewx-user] Weewx stops reporting on fixed interval

[Mauro De Lauretis]

Thank you! 

Il giorno mercoledì 16 dicembre 2020 alle 16:24:54 UTC+1 kk44...@gmail.com 
ha scritto:

> on the computer where you run ssh:
> scp root@rpi:/var/log/syslog .
>
> Please, note the dot at the end. Replace "rpi" by the IP address or name 
> of your RPi. May be, you need to replace "root" by "pi" or "user" to get it 
> work.
>
> After that you will find a file named "syslog" in the current directory. 
> You can open it with any text editor.
>
>
> Mauro De Lauretis schrieb am Mittwoch, 16. Dezember 2020 um 16:03:17 UTC+1:
>
>> Yes, I can ssh into my RPi, but I don't know how to scp the log.
>>
>> Il giorno mercoledì 16 dicembre 2020 alle 15:28:09 UTC+1 tke...@gmail.com 
>> ha scritto:
>>
>>> If you can ssh into your RPi, you could scp the log to 
>>> somewhere convenient. Then upload it to a cloud service such as 
>>> pastebin.com. 
>>>
>>> Alternatively, you can use a text editor to trim it down to the 
>>> essentials, then post it here. But, please don't post anything too big here.
>>>
>>> -tk
>>>
>>> On Wed, Dec 16, 2020 at 6:04 AM Mauro De Lauretis  
>>> wrote:
>>>
 You're right, Tom.
 If not attached the log because I should copy and paste you the exactly 
 moment when Weewx stops reporting, but how can I do it when I'm not logged 
 on my Raspberry when it happens? Are there other possibilities?





 Il giorno mercoledì 16 dicembre 2020 alle 14:41:45 UTC+1 
 tke...@gmail.com ha scritto:

> Sorry, but it does not look like you attached the log.
>
> On Wed, Dec 16, 2020 at 5:32 AM Mauro De Lauretis <
> mauro.de...@gmail.com> wrote:
>
>> Hi Tom,
>> I've never thought that the log is interesting, simply I was not able 
>> to see where the error is. :-)
>>
>> Station Hardware is a Davis Vantage Pro2, while the debug is already 
>> set to debug = 1.
>>
>> Regards
>> Mauro
>>
>> Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1 
>> tke...@gmail.com ha scritto:
>>
>>> I know you think the log is uninteresting, but to more experienced 
>>> eyes, it may contain some clues. Be sure to set debug=1.
>>>
>>> Also, what kind of hardware?
>>>
>>> On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis <
>>> mauro.de...@gmail.com> wrote:
>>>
 Hello,

 I have been experiencing an issue for the last two weeks, and so 
 far have not been able to determine the cause. I was hoping someone 
 may 
 have some ideas.

 I am running the Weather34 Skin (
 https://github.com/steepleian/weewx-Weather34)
 Weewx 4.2.0.
 MySQL Database
 OS Rasbian on Raspberry

 At fixed intervals (7-8 hours, more and less) the system stops 
 entering data into the database and upload files into my web server, 
 but I 
 cannot see any suitable information or error from the syslog. If I 
 restart 
 Weewx, everything turns to work great. Then, after this "famous" 7-8 
 hours, 
 Weewx stops again to report and doesn't work before I make a manually 
 restart.

 If anyone has any ideas it would be very much appreciated.

 Thanks
 Mauro

 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google 
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/fe500236-0b9c-4db4-a555-57c78ec08e06n%40googlegroups.com
  
 

[weewx-user] weewx installation failure on Raspberry Pi

[John Mora]

Hello, I am attempting to install weewx on my Raspberry Pi 4 8G. I follow 
the instructions in the manual: http://weewx.com/docs/debian.htm
I log in to the system using the same user/credentials as when I installed 
PiHole and Unbound which installed and ran without any issues.
When the weewx installation completes, the service fails to start and there 
appears to be folders/files missing.

Here is the console output from the installation process, the output of 
"systemctl status weewx.service" and "journalctl -u weewx"

pi@raspberrypi1:~ $ cat /etc/issue
Raspbian GNU/Linux 10 \n \l

pi@raspberrypi1:~ $ python --version
Python 2.7.16

pi@raspberrypi1:~ $ sudo wget -qO - http://weewx.com/keys.html | sudo 
apt-key add -
OK

pi@raspberrypi1:~ $ sudo wget -qO - http://weewx.com/apt/weewx-python2.list 
| sudo tee /etc/apt/sources.list.d/weewx.list
deb [arch=all] http://weewx.com/apt/python2 squeeze main

pi@raspberrypi1:~ $ sudo apt-get update
Hit:1 http://weewx.com/apt/python2 squeeze InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Get:3 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Fetched 15.0 kB in 1s (11.5 kB/s)
Reading package lists... Done
pi@raspberrypi1:~ $ sudo apt-get install weewx
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  lxplug-volume
Use 'sudo apt autoremove' to remove it.
Suggested packages:
  sqlite ftp
The following NEW packages will be installed:
  weewx
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,207 kB of archives.
After this operation, 5,327 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package weewx.
(Reading database ... 100745 files and directories currently installed.)
Preparing to unpack .../archives/weewx_4.2.0-1_all.deb ...
Unpacking weewx (4.2.0-1) ...
Setting up weewx (4.2.0-1) ...
Job for weewx.service failed because the control process exited with error 
code.
See "systemctl status weewx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript weewx, action "start" failed.
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: failed (Result: exit-code) since Wed 2020-12-16 13:48:44 EST; 
22ms ago
 Docs: man:systemd-sysv-generator(8)
  Process: 10601 ExecStart=/etc/init.d/weewx start (code=exited, 
status=1/FAILURE)

Dec 16 13:48:43 raspberrypi1 systemd[1]: Starting LSB: weewx weather 
system...
Dec 16 13:48:44 raspberrypi1 weewx[10601]: Starting weewx weather system: 
weewxTraceback (most recent call last):
Dec 16 13:48:44 raspberrypi1 weewx[10601]:   File 
"/usr/share/weewx/weewxd", line 28, in 
Dec 16 13:48:44 raspberrypi1 weewx[10601]: import user.extensions
Dec 16 13:48:44 raspberrypi1 weewx[10601]: ImportError: No module named 
extensions
Dec 16 13:48:44 raspberrypi1 weewx[10601]:  failed!
Dec 16 13:48:44 raspberrypi1 systemd[1]: weewx.service: Control process 
exited, code=exited, status=1/FAILURE
Dec 16 13:48:44 raspberrypi1 systemd[1]: weewx.service: Failed with result 
'exit-code'.
Dec 16 13:48:44 raspberrypi1 systemd[1]: Failed to start LSB: weewx weather 
system.
dpkg: error processing package weewx (--configure):
 installed weewx package post-installation script subprocess returned error 
exit status 1
Processing triggers for systemd (241-7~deb10u5+rpi1) ...
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (1)

pi@raspberrypi1:~ $ sudo systemctl status weewx.service
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: failed (Result: exit-code) since Wed 2020-12-16 13:48:44 EST; 
8min ag
 Docs: man:systemd-sysv-generator(8)

Dec 16 13:48:43 raspberrypi1 systemd[1]: Starting LSB: weewx weather 
system...
Dec 16 13:48:44 raspberrypi1 weewx[10601]: Starting weewx weather system: 
weewxT
Dec 16 13:48:44 raspberrypi1 weewx[10601]:   File 
"/usr/share/weewx/weewxd", lin
Dec 16 13:48:44 raspberrypi1 weewx[10601]: import user.extensions
Dec 16 13:48:44 raspberrypi1 weewx[10601]: ImportError: No module named 
extensio
Dec 16 13:48:44 raspberrypi1 weewx[10601]:  failed!
Dec 16 13:48:44 raspberrypi1 systemd[1]: weewx.service: Control process 
exited, 
Dec 16 13:48:44 raspberrypi1 systemd[1]: weewx.service: Failed with result 
'exit
Dec 16 13:48:44 raspberrypi1 systemd[1]: Failed to start LSB: weewx weather 
syst
lines 1-14/14 (END)


pi@raspberrypi1:~ $ journalctl -u weewx
-- Logs begin at Wed 2020-12-16 08:39:43 EST, end at Wed 2020-12-16 
14:11:41 EST. --
Dec 16 13:48:43 raspberrypi1 systemd[1]: Starting LSB: weewx weather 
system...
Dec 16 13:48:44 raspberrypi1 weewx[10601]: Starting weewx weather system: 
weewxTraceback (most recent call last):
Dec 16 13:48:44 raspberrypi1 weewx[10601]:   File 
"/usr/share/weewx/weewxd", line 28, in 

Re: [weewx-user] weewx installation failure on Raspberry Pi

[Tom Keffer]

1. Any particular reason why you're trying to use Python 2 on a Debian 10
system? Normally, the expectation is that Deb 10 (buster) users would be
using Python 3.

2. What is the results of

*ls -l /usr/share/weewx*

3. What is the results of

*ls -l /usr/share/weewx/user*


On Wed, Dec 16, 2020 at 11:27 AM John Mora  wrote:

> Hello, I am attempting to install weewx on my Raspberry Pi 4 8G. I follow
> the instructions in the manual: http://weewx.com/docs/debian.htm
> I log in to the system using the same user/credentials as when I installed
> PiHole and Unbound which installed and ran without any issues.
> When the weewx installation completes, the service fails to start and
> there appears to be folders/files missing.
>
> Here is the console output from the installation process, the output of
> "systemctl status weewx.service" and "journalctl -u weewx"
>
> pi@raspberrypi1:~ $ cat /etc/issue
> Raspbian GNU/Linux 10 \n \l
>
> pi@raspberrypi1:~ $ python --version
> Python 2.7.16
>
> pi@raspberrypi1:~ $ sudo wget -qO - http://weewx.com/keys.html | sudo
> apt-key add -
> OK
>
> pi@raspberrypi1:~ $ sudo wget -qO -
> http://weewx.com/apt/weewx-python2.list | sudo tee
> /etc/apt/sources.list.d/weewx.list
> deb [arch=all] http://weewx.com/apt/python2 squeeze main
>
> pi@raspberrypi1:~ $ sudo apt-get update
> Hit:1 http://weewx.com/apt/python2 squeeze InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Get:3 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
> Fetched 15.0 kB in 1s (11.5 kB/s)
> Reading package lists... Done
> pi@raspberrypi1:~ $ sudo apt-get install weewx
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following package was automatically installed and is no longer
> required:
>   lxplug-volume
> Use 'sudo apt autoremove' to remove it.
> Suggested packages:
>   sqlite ftp
> The following NEW packages will be installed:
>   weewx
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/1,207 kB of archives.
> After this operation, 5,327 kB of additional disk space will be used.
> Preconfiguring packages ...
> Selecting previously unselected package weewx.
> (Reading database ... 100745 files and directories currently installed.)
> Preparing to unpack .../archives/weewx_4.2.0-1_all.deb ...
> Unpacking weewx (4.2.0-1) ...
> Setting up weewx (4.2.0-1) ...
> Job for weewx.service failed because the control process exited with error
> code.
> See "systemctl status weewx.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript weewx, action "start" failed.
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated)
>Active: failed (Result: exit-code) since Wed 2020-12-16 13:48:44 EST;
> 22ms ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 10601 ExecStart=/etc/init.d/weewx start (code=exited,
> status=1/FAILURE)
>
> Dec 16 13:48:43 raspberrypi1 systemd[1]: Starting LSB: weewx weather
> system...
> Dec 16 13:48:44 raspberrypi1 weewx[10601]: Starting weewx weather system:
> weewxTraceback (most recent call last):
> Dec 16 13:48:44 raspberrypi1 weewx[10601]:   File
> "/usr/share/weewx/weewxd", line 28, in 
> Dec 16 13:48:44 raspberrypi1 weewx[10601]: import user.extensions
> Dec 16 13:48:44 raspberrypi1 weewx[10601]: ImportError: No module named
> extensions
> Dec 16 13:48:44 raspberrypi1 weewx[10601]:  failed!
> Dec 16 13:48:44 raspberrypi1 systemd[1]: weewx.service: Control process
> exited, code=exited, status=1/FAILURE
> Dec 16 13:48:44 raspberrypi1 systemd[1]: weewx.service: Failed with result
> 'exit-code'.
> Dec 16 13:48:44 raspberrypi1 systemd[1]: Failed to start LSB: weewx
> weather system.
> dpkg: error processing package weewx (--configure):
>  installed weewx package post-installation script subprocess returned
> error exit status 1
> Processing triggers for systemd (241-7~deb10u5+rpi1) ...
> Errors were encountered while processing:
>  weewx
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> pi@raspberrypi1:~ $ sudo systemctl status weewx.service
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated)
>Active: failed (Result: exit-code) since Wed 2020-12-16 13:48:44 EST;
> 8min ag
>  Docs: man:systemd-sysv-generator(8)
>
> Dec 16 13:48:43 raspberrypi1 systemd[1]: Starting LSB: weewx weather
> system...
> Dec 16 13:48:44 raspberrypi1 weewx[10601]: Starting weewx weather system:
> weewxT
> Dec 16 13:48:44 raspberrypi1 weewx[10601]:   File
> "/usr/share/weewx/weewxd", lin
> Dec 16 13:48:44 raspberrypi1 weewx[10601]: import user.extensions
> Dec 16 13:48:44 raspberrypi1 weewx[10601]: ImportError: No module named
> extensio
> Dec 16 13:48:44 raspberrypi1 weewx[10601]:  failed!
> Dec 16 13:48:44 raspberrypi1 systemd[1]: weewx.service: Control process
> exited,
> Dec 16 13:48:44 raspberrypi1 systemd[1]: weewx.service: Failed with result
> 'exit
> Dec 16 1

Re: [weewx-user] Weewx stops reporting on fixed interval

[Mauro De Lauretis]

Tom, maybe I've found the problem of the stopping:

Dec 16 00:13:45 raspberrypi weewx[2295]: Stopping weewx weather system: 
weewx not running

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Succeeded.

Dec 16 00:13:45 raspberrypi systemd[1]: Stopped LSB: weewx weather system.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25134 (sh) in control group while starting unit. Ignoring.

Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25135 (wget) in control group while starting unit. Ignoring.

Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25137 (sh) in control group while starting unit. Ignoring.

Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25138 (wget) in control group while starting unit. Ignoring.

Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25139 (sh) in control group while starting unit. Ignoring.

Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25140 (wget) in control group while starting unit. Ignoring.

Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25160 (sh) in control group while starting unit. Ignoring.

Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25161 (wget) in control group while starting unit. Ignoring.

Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25163 (sh) in control group while starting unit. Ignoring.

Dec 16 00:13:46 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:46 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25165 (wget) in control group while starting unit. Ignoring.

Dec 16 00:13:46 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:46 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25168 (sh) in control group while starting unit. Ignoring.

Dec 16 00:13:46 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:46 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25170 (wget) in control group while starting unit. Ignoring.

Dec 16 00:13:46 raspberrypi systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

Dec 16 00:13:46 raspberrypi systemd[1]: weewx.service: Found left-over 
process 25177 (sh) in control group while starting unit. Ignoring.

Il giorno mercoledì 16 dicembre 2020 alle 17:35:59 UTC+1 Mauro De Lauretis 
ha scritto:

> Thank you! 
>
> Il giorno mercoledì 16 dicembre 2020 alle 16:24:54 UTC+1 kk44...@gmail.com 
> ha scritto:
>
>> on the computer where you run ssh:
>> scp root@rpi:/var/log/syslog .
>>
>> Please, note the dot at the end. Replace "rpi" by the IP address or name 
>> of your RPi. May be, you need to replace "root" by "pi" or "user" to get it 
>> work.
>>
>> After that you will find a file named "syslog" in the current directory. 
>> You can open it with any text editor.
>>
>>
>> Mauro De Lauretis schrieb am Mittwoch, 16. Dezember 2020 um 16:03:17 
>> UTC+1:
>>
>>> Yes, I can ssh into my RPi, but I don't know how to scp the log.
>>>
>>> Il giorno mercoledì 16 dicembre 2020 alle 15:28:09 UTC+1 
>>> tke...@gmail.com ha scritto:
>>>
 If you can ssh into your RPi, you could scp the log to 
 somewhere convenient. Then upload it to a cloud service such as 
 pastebin.com. 

 Alternatively, you can use a text editor to trim it down to the 
 essentials, then post it here. But, please don't post anything too big 
 here.

Re: [weewx-user] weewx installation failure on Raspberry Pi

[vince]

h - he used the python2 instructions, not the python3 instructions.
Might be easier to just delete the package and follow the python3 
instructions which will get him the python3 package.

-- 
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/3cae8484-237b-4b23-a371-c337d601e01bn%40googlegroups.com.

Re: [weewx-user] weewx installation failure on Raspberry Pi

[John Mora]

Thanks for the response. The reason I used the python 2 directions was pure 
user error.

I retried using the python 3 instructions and was much more successful, 
although am still getting an error, but it appears that the it can't open a 
port to connect to the weatherlink live device.

Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 344, in 
openPort
Dec 16 15:55:52 raspberrypi1 weewx[19469]: Starting weewx weather system: 
weewx.
Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
  raise weewx.WeeWxIOError(ex)
Dec 16 15:55:52 raspberrypi1 systemd[1]: Started LSB: weewx weather system.
Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine:   
weewx.WeeWxIOError: [Errno 111] Connection refused
Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__: Unable to load 
driver: [Errno 111] Connection refused
Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__:   
Exiting...

vantage.py relevant snippet:

def openPort(self):
import socket
try:
self.socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
self.socket.settimeout(self.timeout)
self.socket.connect((self.host, self.port))
except (socket.error, socket.timeout, socket.herror) as ex:
log.error("Socket error while opening port %d to ethernet host 
%s.", self.port, self.host)
# Reraise as a weewx I/O error:
raise weewx.WeeWxIOError(ex)
except:
log.error("Unable to connect to ethernet host %s on port %d.", 
self.host, self.port)
raise
log.debug("Opened up ethernet host %s on port %d. timeout=%s, 
tcp_send_delay=%s",
  self.host, self.port, self.timeout, self.tcp_send_delay)

Any direction as to why?

Thanks!

On Wednesday, December 16, 2020 at 4:13:32 PM UTC-5 vince wrote:

> h - he used the python2 instructions, not the python3 instructions.
> Might be easier to just delete the package and follow the python3 
> instructions which will get him the python3 package.
>
>

-- 
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/63473755-a844-4834-958d-035b0e5ea23bn%40googlegroups.com.

Re: [weewx-user] weewx installation failure on Raspberry Pi

[Tom Keffer]

It appears that you are trying to use the WeatherLink iP logger.

Are you sure that's what you want? Most people have serial or USB loggers.
The WLIP logger is not made any longer.

-tk


On Wed, Dec 16, 2020 at 1:20 PM John Mora  wrote:

> Thanks for the response. The reason I used the python 2 directions was
> pure user error.
>
> I retried using the python 3 instructions and was much more successful,
> although am still getting an error, but it appears that the it can't open a
> port to connect to the weatherlink live device.
>
> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 344, in
> openPort
> Dec 16 15:55:52 raspberrypi1 weewx[19469]: Starting weewx weather system:
> weewx.
> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine:
>   raise weewx.WeeWxIOError(ex)
> Dec 16 15:55:52 raspberrypi1 systemd[1]: Started LSB: weewx weather system.
> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
> weewx.WeeWxIOError: [Errno 111] Connection refused
> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__: Unable to
> load driver: [Errno 111] Connection refused
> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__: 
> Exiting...
>
> vantage.py relevant snippet:
>
> def openPort(self):
> import socket
> try:
> self.socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
> self.socket.settimeout(self.timeout)
> self.socket.connect((self.host, self.port))
> except (socket.error, socket.timeout, socket.herror) as ex:
> log.error("Socket error while opening port %d to ethernet host
> %s.", self.port, self.host)
> # Reraise as a weewx I/O error:
> raise weewx.WeeWxIOError(ex)
> except:
> log.error("Unable to connect to ethernet host %s on port %d.",
> self.host, self.port)
> raise
> log.debug("Opened up ethernet host %s on port %d. timeout=%s,
> tcp_send_delay=%s",
>   self.host, self.port, self.timeout, self.tcp_send_delay)
>
> Any direction as to why?
>
> Thanks!
>
> On Wednesday, December 16, 2020 at 4:13:32 PM UTC-5 vince wrote:
>
>> h - he used the python2 instructions, not the python3 instructions.
>> Might be easier to just delete the package and follow the python3
>> instructions which will get him the python3 package.
>>
>> --
> 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/63473755-a844-4834-958d-035b0e5ea23bn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAv5SdEyEiT52Ku2oC-JP-nQ851OT%2BEU%3D6yhGYpUz6pZg%40mail.gmail.com.

Re: [weewx-user] weewx installation failure on Raspberry Pi

[John Mora]

Thank you for the response and your patience. 

I am using the new WeatherLink Live connected via Ethernet cable directly 
to my router. I am able to ping the device from the Raspberry Pi and even 
use the browser to show current conditions via JSON.

It is currently configured and working as expected. It is sending 
information to weatherlink.com.

On Wednesday, December 16, 2020 at 4:29:30 PM UTC-5 tke...@gmail.com wrote:

> It appears that you are trying to use the WeatherLink iP logger.
>
> Are you sure that's what you want? Most people have serial or USB loggers. 
> The WLIP logger is not made any longer.
>
> -tk
>
>
> On Wed, Dec 16, 2020 at 1:20 PM John Mora  wrote:
>
>> Thanks for the response. The reason I used the python 2 directions was 
>> pure user error.
>>
>> I retried using the python 3 instructions and was much more successful, 
>> although am still getting an error, but it appears that the it can't open a 
>> port to connect to the weatherlink live device.
>>
>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 344, in 
>> openPort
>> Dec 16 15:55:52 raspberrypi1 weewx[19469]: Starting weewx weather system: 
>> weewx.
>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
>>   raise weewx.WeeWxIOError(ex)
>> Dec 16 15:55:52 raspberrypi1 systemd[1]: Started LSB: weewx weather 
>> system.
>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
>>   weewx.WeeWxIOError: [Errno 111] Connection refused
>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__: Unable to 
>> load driver: [Errno 111] Connection refused
>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__:   
>> Exiting...
>>
>> vantage.py relevant snippet:
>>
>> def openPort(self):
>> import socket
>> try:
>> self.socket = socket.socket(socket.AF_INET, 
>> socket.SOCK_STREAM)
>> self.socket.settimeout(self.timeout)
>> self.socket.connect((self.host, self.port))
>> except (socket.error, socket.timeout, socket.herror) as ex:
>> log.error("Socket error while opening port %d to ethernet 
>> host %s.", self.port, self.host)
>> # Reraise as a weewx I/O error:
>> raise weewx.WeeWxIOError(ex)
>> except:
>> log.error("Unable to connect to ethernet host %s on port 
>> %d.", self.host, self.port)
>> raise
>> log.debug("Opened up ethernet host %s on port %d. timeout=%s, 
>> tcp_send_delay=%s",
>>   self.host, self.port, self.timeout, self.tcp_send_delay)
>>
>> Any direction as to why?
>>
>> Thanks!
>>
>> On Wednesday, December 16, 2020 at 4:13:32 PM UTC-5 vince wrote:
>>
>>> h - he used the python2 instructions, not the python3 instructions.
>>> Might be easier to just delete the package and follow the python3 
>>> instructions which will get him the python3 package.
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/63473755-a844-4834-958d-035b0e5ea23bn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/09ea5664-10c7-4d01-8c38-665240b4b25en%40googlegroups.com.

Re: [weewx-user] weewx installation failure on Raspberry Pi

[Tom Keffer]

I see. The WLL logger is not a supported logger, so you'll have to install
an extension for it. There are several listed on the Wiki
.

-tk

On Wed, Dec 16, 2020 at 1:35 PM John Mora  wrote:

> Thank you for the response and your patience.
>
> I am using the new WeatherLink Live connected via Ethernet cable directly
> to my router. I am able to ping the device from the Raspberry Pi and even
> use the browser to show current conditions via JSON.
>
> It is currently configured and working as expected. It is sending
> information to weatherlink.com.
>
> On Wednesday, December 16, 2020 at 4:29:30 PM UTC-5 tke...@gmail.com
> wrote:
>
>> It appears that you are trying to use the WeatherLink iP logger.
>>
>> Are you sure that's what you want? Most people have serial or USB
>> loggers. The WLIP logger is not made any longer.
>>
>> -tk
>>
>>
>> On Wed, Dec 16, 2020 at 1:20 PM John Mora  wrote:
>>
>>> Thanks for the response. The reason I used the python 2 directions was
>>> pure user error.
>>>
>>> I retried using the python 3 instructions and was much more successful,
>>> although am still getting an error, but it appears that the it can't open a
>>> port to connect to the weatherlink live device.
>>>
>>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine:
>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 344, in
>>> openPort
>>> Dec 16 15:55:52 raspberrypi1 weewx[19469]: Starting weewx weather
>>> system: weewx.
>>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine:
>>>   raise weewx.WeeWxIOError(ex)
>>> Dec 16 15:55:52 raspberrypi1 systemd[1]: Started LSB: weewx weather
>>> system.
>>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine:
>>>   weewx.WeeWxIOError: [Errno 111] Connection refused
>>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__: Unable to
>>> load driver: [Errno 111] Connection refused
>>> Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__: 
>>> Exiting...
>>>
>>> vantage.py relevant snippet:
>>>
>>> def openPort(self):
>>> import socket
>>> try:
>>> self.socket = socket.socket(socket.AF_INET,
>>> socket.SOCK_STREAM)
>>> self.socket.settimeout(self.timeout)
>>> self.socket.connect((self.host, self.port))
>>> except (socket.error, socket.timeout, socket.herror) as ex:
>>> log.error("Socket error while opening port %d to ethernet
>>> host %s.", self.port, self.host)
>>> # Reraise as a weewx I/O error:
>>> raise weewx.WeeWxIOError(ex)
>>> except:
>>> log.error("Unable to connect to ethernet host %s on port
>>> %d.", self.host, self.port)
>>> raise
>>> log.debug("Opened up ethernet host %s on port %d. timeout=%s,
>>> tcp_send_delay=%s",
>>>   self.host, self.port, self.timeout,
>>> self.tcp_send_delay)
>>>
>>> Any direction as to why?
>>>
>>> Thanks!
>>>
>>> On Wednesday, December 16, 2020 at 4:13:32 PM UTC-5 vince wrote:
>>>
 h - he used the python2 instructions, not the python3 instructions.
 Might be easier to just delete the package and follow the python3
 instructions which will get him the python3 package.

 --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/63473755-a844-4834-958d-035b0e5ea23bn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/09ea5664-10c7-4d01-8c38-665240b4b25en%40googlegroups.com
> 
> .
>

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

Re: [weewx-user] weewx installation failure on Raspberry Pi

[John Mora]

AHA! Yes, I understand. I just read into the extension for it. I will 
install the appropriate extension and move forward.
Thank you for your time, it is highly appreciated.
If I run into an issue with the extension and getting it to work, I will 
start a new thread.

Cheers!
John
On Wednesday, December 16, 2020 at 4:59:25 PM UTC-5 tke...@gmail.com wrote:

> I see. The WLL logger is not a supported logger, so you'll have to install 
> an extension for it. There are several listed on the Wiki 
> .
>
> -tk
>
> On Wed, Dec 16, 2020 at 1:35 PM John Mora  wrote:
>
>> Thank you for the response and your patience. 
>>
>> I am using the new WeatherLink Live connected via Ethernet cable directly 
>> to my router. I am able to ping the device from the Raspberry Pi and even 
>> use the browser to show current conditions via JSON.
>>
>> It is currently configured and working as expected. It is sending 
>> information to weatherlink.com.
>>
>> On Wednesday, December 16, 2020 at 4:29:30 PM UTC-5 tke...@gmail.com 
>> wrote:
>>
>>> It appears that you are trying to use the WeatherLink iP logger.
>>>
>>> Are you sure that's what you want? Most people have serial or USB 
>>> loggers. The WLIP logger is not made any longer.
>>>
>>> -tk
>>>
>>>
>>> On Wed, Dec 16, 2020 at 1:20 PM John Mora  wrote:
>>>
 Thanks for the response. The reason I used the python 2 directions was 
 pure user error.

 I retried using the python 3 instructions and was much more successful, 
 although am still getting an error, but it appears that the it can't open 
 a 
 port to connect to the weatherlink live device.

 Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 344, in 
 openPort
 Dec 16 15:55:52 raspberrypi1 weewx[19469]: Starting weewx weather 
 system: weewx.
 Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
   raise weewx.WeeWxIOError(ex)
 Dec 16 15:55:52 raspberrypi1 systemd[1]: Started LSB: weewx weather 
 system.
 Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL weewx.engine: 
   weewx.WeeWxIOError: [Errno 111] Connection refused
 Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__: Unable to 
 load driver: [Errno 111] Connection refused
 Dec 16 15:55:52 raspberrypi1 weewx[19487] CRITICAL __main__:   
 Exiting...

 vantage.py relevant snippet:

 def openPort(self):
 import socket
 try:
 self.socket = socket.socket(socket.AF_INET, 
 socket.SOCK_STREAM)
 self.socket.settimeout(self.timeout)
 self.socket.connect((self.host, self.port))
 except (socket.error, socket.timeout, socket.herror) as ex:
 log.error("Socket error while opening port %d to ethernet 
 host %s.", self.port, self.host)
 # Reraise as a weewx I/O error:
 raise weewx.WeeWxIOError(ex)
 except:
 log.error("Unable to connect to ethernet host %s on port 
 %d.", self.host, self.port)
 raise
 log.debug("Opened up ethernet host %s on port %d. timeout=%s, 
 tcp_send_delay=%s",
   self.host, self.port, self.timeout, 
 self.tcp_send_delay)

 Any direction as to why?

 Thanks!

 On Wednesday, December 16, 2020 at 4:13:32 PM UTC-5 vince wrote:

> h - he used the python2 instructions, not the python3 instructions.
> Might be easier to just delete the package and follow the python3 
> instructions which will get him the python3 package.
>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/63473755-a844-4834-958d-035b0e5ea23bn%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/09ea5664-10c7-4d01-8c38-665240b4b25en%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe fr

Re: [weewx-user] GW1000 - solar radiation data lost while switching from Interceptor to API driver

[Graham Eddy]

syslog shows you have mapped 'UV’ from ‘uv’ and ‘radiation’ from 
‘solar_radiation’.
my working config has ‘UV’ mapped from ‘uvi’ and ‘radiation’ from ‘uv'

> On 17 Dec 2020, at 10:41 am, 'Rainer Lang' via weewx-user 
>  wrote:
> 
> I was running Weewx with the GW1000 interceptor and everything ran smoothly. 
> After downloading and installing the GW1000 API driver v. 0.1.012b and 
> meticulously following the readme instructions, I got the system running - 
> with ONE issue - the solar radiation data had disappeared and would no longer 
> be displayed. 
> 
> (they are there and sent to Ecowitt.net, WU etc. and are captured by 
> CumulusMX and Meteobridge => it's not a GW1000 console issue, it's obviously 
> a weewx (configuration ?) issue. I have 4 GW1000 type consoles and switched 
> between them to make sure it's not due to the console [with weewxd]. 
> 
> Since midnight the solar radiation picture/graph has completely disappeared.
> So I'm wondering what went wrong here ...
> Anyone can advise ?
> attached the syslog of the driver switch time window and some debug=1 output 
> at the end, the weewx.conf, a screencopy of the missing or mutilated graph 
> and the output of weexd as screencopy and text.
> 
> -- 
> 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/712d3a95-4fd7-4bbc-9b07-62477f1b2774n%40googlegroups.com
>  
> .
> 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/979F765D-AA53-4533-BEF7-245A3D4A714D%40gmail.com.

[weewx-user] Re: yet another question to GW1000 api driver mapping

[gjr80]

Peter,

Comments below.

Gary
On Wednesday, 16 December 2020 at 23:18:26 UTC+10 Vetti52 wrote:

> Thanks, Gary, for your polite explanations. 
> Since I have read some of your comments with equal advices in other 
> threads, I proceeded already to sucessfully map the fields. Otherwise I did 
> not even had an idea about field_map in GW1000. Sorry, that you need to 
> explain again and again the comparison of --live-data and mapped loop data. 
> But at that point, I feel better, not to miss any point. Thanks for your 
> patience.
>

I noted you had worked through the mappings, I wanted to outline the entire 
process, mainly for the next person that comes along.
 

> Well, data are mapped, weewx running directly gives this output:
>
> $ sudo weewxd /etc/weewx/weewx.conf
> LOOP:   2020-12-16 13:29:56 CET (1608121796) altimeter: 30.09246486970751, 
> appTemp: 46.07291271146897, barometer: 30.092169667712717, cloudbase: 
> 944.6426189788297, dateTime: 1608121796, daymaxwind: 3.6, dayRain: 0.0, 
> dewpoint: 45.0455158818643, heatindex: 47.4030006, humidex: 
> 48.934644083871206, inDewpoint: 50.88299985988465, inHumidity: 60, inTemp: 
> 65.12, luminosity: 8184.0, maxSolarRad: 86.02828823732644, monthRain: 
> 0.6653543307086613, outHumidity: 87, outTemp: 48.74, pressure: 
> 29.97589031125, radiation: 64.59352801894238, rain: None, rainEvent: 
> 0.4015748031496063, rainRate: 0.0, relbarometer: 1019.2, usUnits: 1, UV: 
> 0, uvradiation: 6.5, weekRain: 10.9, wh65_battery: 0, windchill: 48.74, 
> windDir: 187, windGust: 3.3554127779089566, windGustDir: None, windSpeed: 
> 2.6843302223271652, yearRain: 29.17716535433071
> LOOP:   2020-12-16 13:30:56 CET (1608121856) altimeter: 30.09542729292998, 
> appTemp: 45.69491271146897, barometer: 30.095134121428384, cloudbase: 
> 944.6426189788297, dateTime: 1608121856, daymaxwind: 3.6, dayRain: 0.0, 
> dewpoint: 45.0455158818643, heatindex: 47.4030006, humidex: 
> 48.934644083871206, inDewpoint: 50.88299985988465, inHumidity: 60, inTemp: 
> 65.12, luminosity: 8075.0, maxSolarRad: 85.3176898825967, monthRain: 
> 0.6653543307086613, outHumidity: 87, outTemp: 48.74, pressure: 
> 29.97884331002, radiation: 63.73322809786898, rain: 0.0, rainEvent: 
> 0.4015748031496063, rainRate: 0.0, relbarometer: 1019.3, usUnits: 1, UV: 
> 0, uvradiation: 6.4, weekRain: 10.9, wh65_battery: 0, windchill: 
> 47.93087953525257, windDir: 162, windGust: 5.816048815042191, windGustDir: 
> None, windSpeed: 3.3554127779089566, yearRain: 29.17716535433071
> REC:2020-12-16 13:30:00 CET (1608121800) altimeter: 
> 30.09246486970751, appTemp: 46.07291271146897, barometer: 
> 30.092169667712717, cloudbase: 944.6426189788297, dateTime: 1608121800, 
> daymaxwind: 3.6, dayRain: 0.0, dewpoint: 45.0455158818643, ET: 
> 0.00012174671890853505, extraTemp1: 124.894399, heatindex: 
> 47.4030006, humidex: 48.934644083871206, inDewpoint: 
> 50.88299985988465, inHumidity: 60.0, inTemp: 65.12, interval: 5.0, 
> luminosity: 8184.0, maxSolarRad: 86.02828823732644, monthRain: 
> 0.6653543307086613, outHumidity: 87.0, outTemp: 48.74, pressure: 
> 29.97589031125, radiation: 64.59352801894238, rain: 0.0, rainEvent: 
> 0.4015748031496063, rainRate: 0.0, relbarometer: 1019.2, usUnits: 1, UV: 
> 0.0, uvradiation: 6.5, weekRain: 10.9, wh65_battery: 0.0, windchill: 
> 48.74, windDir: 187.0, windGust: 3.3554127779089566, windGustDir: 187, 
> windrun: 0.22369418519393044, windSpeed: 2.6843302223271652, yearRain: 
> 29.17716535433071
>
> So I am glad to see, that the StdArchive service is ok. Right?
>
 
Yes. One small thing though that I did not highlight is the accumulator 
extractor functions. By default when WeeWX synthesises an archive record 
from the accumulated loop data WeeWX takes the average of the accumulated 
values for each field. In essence you get the average value of the filed in 
the archive period. For something like temperature this is appropriate, but 
for something like WeeWX field rain (the amount of rainfall seen in the 
archive period) we want the sum not the average. For something like 
rainEvent which is a cumulative value we likely want the last value seen 
rather than the average (and certainly not the sum). Similarly for 
wh65_battery, if we had two loop packets arrive in the archive period and 
the first one had wh65_battery = 0 and the last had had wh65_battery = 1 do 
we want the resulting archive record to have wh65_battery = 0.5? No, we ant 
it to have the last value seen ie 1. 

The way we tell WeeWX how to extract a given archive record field from the 
accumulated loop data is by specifying the extractor function to use in 
weewx.conf. In your case you will need to add something like the following 
to weewx.conf:

[Accumulator]
[[rainEvent]]
extractor = last
[[wh65_battery]]
extractor = last

If you have a look in weewx.conf you will likely find an [Accumulator] 
stanza towards the bottom of weewx.conf already. You will likely find it 
alr

[weewx-user] Re: GW1000 - solar radiation data lost while switching from Interceptor to API driver

[gjr80]

Hi,

The short answer is that radiation (aka solar insulation) or an equivalent 
is not available via the GW1000 API so the GW1000 driver does not emit it. 
The reason you see it on Ecowitt pages and WU is that the GW1000 takes what 
the GW1000 API refers to as 'light' in lux and approximates solar 
insolation by dividing by 126.7. The GW1000 then uploads this derived value 
to Ecowitt and WU (and to anywhere else the GW1000 is configured to 
upload). A similar result can be achieved with WeeWX by having the WeeWX 
StdCalculate service calculate WeeWX field radiation. This is done by 
adding an entry for radiation under [StdCalculate] [[Corrections]] in 
weewx.conf:

[StdCalibrate]
 
[[Corrections]]

radiation = luminosity/126.7 if luminosity is not None else None 

The reason the interceptor driver picked up radiation is that the 
interceptor driver intercepts the the same data the GW1000 uploads to 
Ecowitt or WU, so the interceptor driver sees the radiation field that was 
calculated by the GW1000. WeeWX drivers do not calculate/derive 
observations; rather they decode/unit translate data provided buy the 
station/sensors only. Calculation of derived observations is taken care of 
by other WeeWX services, typically the StdCalculate service.

I can't speak for what Cumulus does but I know Cumulus obtains the exact 
same data from the API that the GW1000 driver does. Cumulus must be set to 
automatically derive solar insolation from luminosity.

As further background, the GW1000 API emits three 'radiation' related 
observations; what the API refers to as 'light' in lux, 'UV' in 
microwatts/square metre and 'UVI' an index from 0-15. Of these observations 
'light' corresponds to the WeeWX extended schema field luminosity and 'UVI' 
corresponds to WeeWX field UV. Consequently, (and by default) these 
observations are mapped to the equivalent WeeWX field. There is no 
equivalent to the GW1000 API field 'UV' so the GW1000 driver passes this 
field through as uvradiation (uvradiation was chosen to distinguish it from 
WeeWX field UV). Note that uvradiation is not equivalent to WeeWX field 
radiation.

I am in the process of producing a wiki page for the driver repo to explain 
this.

Gary
On Thursday, 17 December 2020 at 09:41:03 UTC+10 lang@googlemail.com 
wrote:

> I was running Weewx with the GW1000 interceptor and everything ran 
> smoothly. After downloading and installing the GW1000 API driver v. 
> 0.1.012b and meticulously following the readme instructions, I got the 
> system running - with ONE issue - the solar radiation data had disappeared 
> and would no longer be displayed. 
>
> (they are there and sent to Ecowitt.net, WU etc. and are captured by 
> CumulusMX and Meteobridge => it's not a GW1000 console issue, it's 
> obviously a weewx (configuration ?) issue. I have 4 GW1000 type consoles 
> and switched between them to make sure it's not due to the console [with 
> weewxd]. 
>
> Since midnight the solar radiation picture/graph has completely 
> disappeared.
> So I'm wondering what went wrong here ...
> Anyone can advise ?
> attached the syslog of the driver switch time window and some debug=1 
> output at the end, the weewx.conf, a screencopy of the missing or mutilated 
> graph and the output of weexd as screencopy and text.
>

-- 
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/d085a7f5-f83a-445b-82dc-6cd826f25456n%40googlegroups.com.

[weewx-user] FTP Upload Problems

['buck...@googlemail.com' via weewx-user]

Hello, since some days i ve problems to upload my ftp files to my webserver
i use weewx 4.2.0
system is uptodate

here a part of my syslog:

Dec 17 08:35:27 raspberrypi weewx[652] INFO weewx.cheetahgenerator: 
Generated 15 files for report Belchertown in 10.59 seconds
Dec 17 08:35:27 raspberrypi weewx[652] INFO weewx.reportengine: Copied 31 
files to /var/www/html
Dec 17 08:35:46 raspberrypi weewx[652] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 4.71 seconds
Dec 17 08:35:47 raspberrypi weewx[652] INFO weewx.imagegenerator: Generated 
15 images for report SeasonsReport in 1.16 seconds
Dec 17 08:35:47 raspberrypi weewx[652] INFO weewx.reportengine: Copied 87 
files to /var/www/html/weewx
Dec 17 08:35:47 raspberrypi weewxd: translategenerator.pyc: Language is 
german
Dec 17 08:35:48 raspberrypi weewxd: historygenerator.pyc: Generated 8 
tables in 0.42 seconds
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator: 
Generate failed with exception ''
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/niculskin/forecast.html.tmpl
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:  
Reason: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/etc/weewx/skins/niculskin/forecast_iconic.inc'
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in generate
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
  File "_etc_weewx_skins_niculskin_forecast_html_tmpl.py", line 96, in 
respond
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
  File "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1685, 
in _handleCheetahInclude
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
file=file)
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
  File "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 738, in 
compile
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
fileHash += str(os.path.getmtime(file))
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
  File "/usr/lib/python2.7/genericpath.py", line 62, in getmtime
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
return os.stat(filename).st_mtime
Dec 17 08:35:52 raspberrypi weewx[652] ERROR weewx.cheetahgenerator:   
OSError: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/etc/weewx/skins/niculskin/forecast_iconic.inc'
Dec 17 08:35:52 raspberrypi weewx[652] INFO weewx.cheetahgenerator: 
Generated 13 files for report StandardReport in 4.78 seconds
Dec 17 08:35:53 raspberrypi weewx[652] INFO weewx.imagegenerator: Generated 
13 images for report StandardReport in 1.18 seconds
Dec 17 08:35:53 raspberrypi weewx[652] INFO weewx.reportengine: Copied 11 
files to /var/www/html/weewx
Dec 17 08:35:53 raspberrypi weewx[652] INFO user.sftp: sftpgenerator: 
upload not possible: missing parameter 'server'
Dec 17 08:35:53 raspberrypi weewx[652] INFO user.sftp: sftpgenerator: 
upload not possible: No module named pysftp
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weeutil.ftpupload: Failed 
uploading /var/www/html/weewx/daytempchill.png to server 213.160.xx.xx. 
Reason: '451-Error during write to file#012451 Transfer aborted'
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine: 
ftpgenerator: (0): caught exception '': 
451-Error during write to file#012451 Transfer aborted
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
   Traceback (most recent call last):
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
   n = ftp_data.run()
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
 File "/usr/share/weewx/weeutil/ftpupload.py", line 163, in run
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
   ftp_server.storbinary(stor_cmd, fd)
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
 File "/usr/lib/python2.7/ftplib.py", line 488, in storbinary
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
   return self.voidresp()
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
 File "/usr/lib/python2.7/ftplib.py", line 231, in voidresp
Dec 17 08:35:54 raspberrypi weewx[652] ERROR weewx.reportengine:
   resp = self.getresp()
Dec 17 08:35:54 raspberrypi weewx[652] ERROR wee