Re: [weewx-user] Crash reading from Vantage Pro 2 since v5

[Julian Edwards]

Hi Tom

1. Yes, it's the Weatherlink IP.
2. The log entries immediately before the ones I pasted are below. I've 
always seen IP connectivity issues, which I put down to the Weatherlink IP 
module's idiosyncrasies. When I see these happening I sometimes check to 
see if I can ping the IP address of the Weatherlink and it always responds, 
so I don't think there's any underlying network problem (it's all wired as 
well, there's no Wifi in the way).

Jan 28 09:07:07 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-read error: timed out 
Jan 28 09:07:07 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: LOOP 
batch try #1; error: timed out 
Jan 28 09:07:08 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:07:12 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR 
weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe] 
Jan 28 09:07:13 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console 
Jan 28 09:07:13 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: LOOP 
batch try #2; error: Unable to wake up Vantage console 
Jan 28 09:07:13 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:07:16 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR 
weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe] 
Jan 28 09:07:18 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console 
Jan 28 09:07:18 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: LOOP 
batch try #3; error: Unable to wake up Vantage console 
Jan 28 09:07:18 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: LOOP 
max batch errors (3) exceeded. 
Jan 28 09:07:18 jeeves weewxd[3350596]: INFO weewx.engine: Main loop 
exiting. Shutting engine down. 
Jan 28 09:07:18 jeeves weewxd[3350596]: INFO weewx.engine: Shutting down 
StdReport thread 
Jan 28 09:07:18 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:07:18 jeeves weewxd[3350596]: CRITICAL __main__: Caught 
WeeWxIOError: LOOP max batch errors (3) exceeded. 
Jan 28 09:07:18 jeeves weewxd[3350596]: CRITICAL __main__:  
 Waiting 60.0 seconds then retrying... 
Jan 28 09:08:18 jeeves weewxd[3350596]: INFO __main__: retrying...

The config I am using looks like this:

[Vantage] 
   driver = weewx.drivers.vantage 
   type = ethernet 
   host = 
   tcp_port = 2
   loop_request = 2

I've added in a systemd config to restart the weexwd if it crashes, but it 
would be nice to find out what's wrong and perhaps it should just keep 
retrying forever anyway?

Weirdly it has not crashed out today at all, however.

Thanks
Julian

On Sunday 28 January 2024 at 10:15:26 UTC+10 Tom Keffer wrote:

Julian, a couple of questions:

1. These are ip-read and -write errors. What kind of logger are you using? 
A WeatherLink IP?

2. The log snippet shows code from when the driver is initially loaded, so 
it is unlikely to run 30 minutes in, unless this is actually a restart. 
Look farther back in the log and see what triggered the restart.

Most likely this is a network connectivity issue. The only substantive 
changes in the Vantage driver have been in reading and setting its 
configuration, particularly retransmitters. 

-tk

On Sat, Jan 27, 2024 at 3:53 PM Julian Edwards  wrote:

v4 was flawless for me, but since upgrading to v5 (Debian package) the 
daemon runs for maybe 30 minutes before crashing with this in the log:

Jan 28 09:08:18 jeeves weewxd[3350596]: INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage) 
Jan 28 09:08:25 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-read error: timed out 
Jan 28 09:08:26 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:08:29 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR 
weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe] 
Jan 28 09:08:30 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console 
Jan 28 09:08:30 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:08:34 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR 
weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe] 
Jan 28 09:08:35 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console 
Jan 28 09:08:35 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe 
Jan 28 09:08:39 jeeves weewxd[3350596]: message repeated 3 times: [ ERROR 
weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe] 
Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console 
Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.drivers.vantage: While 
getting EEPROM data value at address 0x29 
Jan 28 09:08:40 jeeves weewxd[3350596]: ERROR weewx.engine: Import of 

[weewx-user] Re: Aeris forcast with belchertown

[bchap...@gmail.com]

Are you using the aeris maps?  That's where I found my issue.  The maps 
rack up hundreds of requests per hour and max you out real quick.  I turned 
off aeris maps and now I have less than 300 hits per day.

On Sunday, January 28, 2024 at 1:25:38 PM UTC-5 Dan Roman wrote:

> I had this problem back in October but it cleared itself up.  Never 
> determined if it was an Aeris or Blechertown problem.  Didn't need to 
> change my password, delete my account, or anything.  It was just a glitch 
> in the matrix I guess that went on for a couple of days and then fixed 
> itself.
>
>
> On Friday, January 26, 2024 at 11:32:57 AM UTC-5 bchap...@gmail.com wrote:
>
>> So, I've solved my problem.  If you're using the aeris free account on 
>> their contributor plan, do not turn on aeris maps in the belchertown 
>> settings.  I don't know what has changed on their end because I have had 
>> the same configuration for many years, but now the map will make thousands 
>> of hits per hour and they will shut you down when you exceed your allowed 
>> 5,000 hits.  I turned off the aeris maps and all looks well so far.
>>
>> On Wednesday, January 24, 2024 at 11:08:16 PM UTC-5 bchap...@gmail.com 
>> wrote:
>>
>>> I've done that.  Should have mentioned in original post.  I've changed 
>>> my password, deleted and created a new app.  My hit count reset at 1900EST 
>>> and within an hour I was at ~600 hits, and that's with forcasting turned 
>>> off in the conf file.  Aeris tech support has not been able to solve this.  
>>> I'm thinking I may need to delete my account with them and re-create a new 
>>> one.  
>>>
>>> On Wednesday, January 24, 2024 at 7:38:45 PM UTC-5 bchap...@gmail.com 
>>> wrote:
>>>
 Is anyone else having problems with aeris forcasting?  For the past few 
 weeks my access credits have been running out resulting in my webpage not 
 being updated.  I've turned off forcasting in weewx.conf and when I watch 
 my activity on aeris the hits keep coming.  I don't know who is making 
 these requests.  My aeris credits are racking up at an average of a few 
 hundred an hour, even with forcasting turned off.  I've contacted aeris 
 tech support which has not been helpful.

>>>

-- 
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/414aa36a-725a-4c51-ad15-ed4241f12505n%40googlegroups.com.

[weewx-user] Re: Help with installing weewx-gw1000 driver

[Phil Bilboe]

Its an old Pentium dual core laptop, 2 x 2Ghz that I have lying around. I 
thought I would try getting Weewx setup on it for a learning experience and 
if successful use a raspberry pi for long term use. I guess I could try to 
find an up to date OS lite that will run on it or just buy a raspberry pi. 
Thanks for your input it is very much appreciated.

On Sunday 28 January 2024 at 18:56:45 UTC vince wrote:

> I might add that you mentioned you're on Ubuntu 18.04.2 LTS which is many 
> months past end of standard support. You really should be on Ubuntu 22.04.3 
> LTS which has standard support until June 2027.  If this is a standalone 
> system or a throwaway test system, I'd recommend flattening it to a current 
> os before you get too invested in other things running on it which would 
> make a flatten+reload more involved.
>
> On Sunday, January 28, 2024 at 10:48:03 AM UTC-8 vince wrote:
>
>> I would extract the .tar.gz file and tell wee_extension to install the 
>> directory of contents therein...
>>
>> cd /var/tmp
>> tar zxvf gw1000-0.6.0b3.tar.gz
>> wee_extension --install gw1000
>>
>>
>> On Sunday, January 28, 2024 at 9:36:48 AM UTC-8 Phil Bilboe wrote:
>>
>>> I'm new to linux and trying to install weewx to read my gw1100 gateway. 
>>>
>>> I'm running Ubuntu 18.04.2 LTS and have completed the debian install and 
>>> the simulator works and generates a webpage.
>>>
>>> When I try to install the gw1000 driver I get the following:
>>>
>>> phil@phil-Inspiron-1545:~$ wee_extension 
>>> --install=/var/tmp/gw1000-0.6.0b3.tar.gz
>>> Request to install '/var/tmp/gw1000-0.6.0b3.tar.gz'
>>> Extracting from tar archive /var/tmp/gw1000-0.6.0b3.tar.gz
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_extension", line 92, in 
>>> main()
>>>   File "/usr/share/weewx/wee_extension", line 84, in main
>>> ext.install_extension(options.install)
>>>   File "/usr/share/weewx/weecfg/extension.py", line 130, in 
>>> install_extension
>>> self.install_from_dir(extension_dir)
>>>   File "/usr/share/weewx/weecfg/extension.py", line 150, in 
>>> install_from_dir
>>> installer_path, installer = 
>>> weecfg.get_extension_installer(extension_dir)
>>>   File "/usr/share/weewx/weecfg/__init__.py", line 1904, in 
>>> get_extension_installer
>>> installer = loader()
>>>   File "/var/tmp/gw1000/install.py", line 396, in loader
>>>   File "/var/tmp/gw1000/install.py", line 401, in __init__
>>>   File "/var/tmp/gw1000/install.py", line 386, in version_compare
>>> AttributeError: 'module' object has no attribute 'zip_longest'
>>>
>>> When I try to go to the next step and test the driver I get the 
>>> following:
>>>
>>> PYTHONPATH=/home/weewx/bin python -m user.gw1000 --test-driver
>>> /usr/bin/python: No module named user.gw1000
>>>
>>> or I get:
>>> PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver
>>> /usr/bin/python: No module named user.gw1000
>>>
>>> I'm kind of lost as to what to do next. Any suggestions would be 
>>> appreciated.
>>>
>>>

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

[weewx-user] Re: Help with installing weewx-gw1000 driver

[vince]

I might add that you mentioned you're on Ubuntu 18.04.2 LTS which is many 
months past end of standard support. You really should be on Ubuntu 22.04.3 
LTS which has standard support until June 2027.  If this is a standalone 
system or a throwaway test system, I'd recommend flattening it to a current 
os before you get too invested in other things running on it which would 
make a flatten+reload more involved.

On Sunday, January 28, 2024 at 10:48:03 AM UTC-8 vince wrote:

> I would extract the .tar.gz file and tell wee_extension to install the 
> directory of contents therein...
>
> cd /var/tmp
> tar zxvf gw1000-0.6.0b3.tar.gz
> wee_extension --install gw1000
>
>
> On Sunday, January 28, 2024 at 9:36:48 AM UTC-8 Phil Bilboe wrote:
>
>> I'm new to linux and trying to install weewx to read my gw1100 gateway. 
>>
>> I'm running Ubuntu 18.04.2 LTS and have completed the debian install and 
>> the simulator works and generates a webpage.
>>
>> When I try to install the gw1000 driver I get the following:
>>
>> phil@phil-Inspiron-1545:~$ wee_extension 
>> --install=/var/tmp/gw1000-0.6.0b3.tar.gz
>> Request to install '/var/tmp/gw1000-0.6.0b3.tar.gz'
>> Extracting from tar archive /var/tmp/gw1000-0.6.0b3.tar.gz
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_extension", line 92, in 
>> main()
>>   File "/usr/share/weewx/wee_extension", line 84, in main
>> ext.install_extension(options.install)
>>   File "/usr/share/weewx/weecfg/extension.py", line 130, in 
>> install_extension
>> self.install_from_dir(extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 150, in 
>> install_from_dir
>> installer_path, installer = 
>> weecfg.get_extension_installer(extension_dir)
>>   File "/usr/share/weewx/weecfg/__init__.py", line 1904, in 
>> get_extension_installer
>> installer = loader()
>>   File "/var/tmp/gw1000/install.py", line 396, in loader
>>   File "/var/tmp/gw1000/install.py", line 401, in __init__
>>   File "/var/tmp/gw1000/install.py", line 386, in version_compare
>> AttributeError: 'module' object has no attribute 'zip_longest'
>>
>> When I try to go to the next step and test the driver I get the following:
>>
>> PYTHONPATH=/home/weewx/bin python -m user.gw1000 --test-driver
>> /usr/bin/python: No module named user.gw1000
>>
>> or I get:
>> PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver
>> /usr/bin/python: No module named user.gw1000
>>
>> I'm kind of lost as to what to do next. Any suggestions would be 
>> appreciated.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/04e2568a-3869-4b8b-8ed1-58244fe63b24n%40googlegroups.com.

[weewx-user] Re: Help with installing weewx-gw1000 driver

[vince]

I would extract the .tar.gz file and tell wee_extension to install the 
directory of contents therein...

cd /var/tmp
tar zxvf gw1000-0.6.0b3.tar.gz
wee_extension --install gw1000


On Sunday, January 28, 2024 at 9:36:48 AM UTC-8 Phil Bilboe wrote:

> I'm new to linux and trying to install weewx to read my gw1100 gateway. 
>
> I'm running Ubuntu 18.04.2 LTS and have completed the debian install and 
> the simulator works and generates a webpage.
>
> When I try to install the gw1000 driver I get the following:
>
> phil@phil-Inspiron-1545:~$ wee_extension 
> --install=/var/tmp/gw1000-0.6.0b3.tar.gz
> Request to install '/var/tmp/gw1000-0.6.0b3.tar.gz'
> Extracting from tar archive /var/tmp/gw1000-0.6.0b3.tar.gz
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_extension", line 92, in 
> main()
>   File "/usr/share/weewx/wee_extension", line 84, in main
> ext.install_extension(options.install)
>   File "/usr/share/weewx/weecfg/extension.py", line 130, in 
> install_extension
> self.install_from_dir(extension_dir)
>   File "/usr/share/weewx/weecfg/extension.py", line 150, in 
> install_from_dir
> installer_path, installer = 
> weecfg.get_extension_installer(extension_dir)
>   File "/usr/share/weewx/weecfg/__init__.py", line 1904, in 
> get_extension_installer
> installer = loader()
>   File "/var/tmp/gw1000/install.py", line 396, in loader
>   File "/var/tmp/gw1000/install.py", line 401, in __init__
>   File "/var/tmp/gw1000/install.py", line 386, in version_compare
> AttributeError: 'module' object has no attribute 'zip_longest'
>
> When I try to go to the next step and test the driver I get the following:
>
> PYTHONPATH=/home/weewx/bin python -m user.gw1000 --test-driver
> /usr/bin/python: No module named user.gw1000
>
> or I get:
> PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver
> /usr/bin/python: No module named user.gw1000
>
> I'm kind of lost as to what to do next. Any suggestions would be 
> appreciated.
>
>

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

[weewx-user] Re: Aeris forcast with belchertown

[Dan Roman]

I had this problem back in October but it cleared itself up.  Never 
determined if it was an Aeris or Blechertown problem.  Didn't need to 
change my password, delete my account, or anything.  It was just a glitch 
in the matrix I guess that went on for a couple of days and then fixed 
itself.


On Friday, January 26, 2024 at 11:32:57 AM UTC-5 bchap...@gmail.com wrote:

> So, I've solved my problem.  If you're using the aeris free account on 
> their contributor plan, do not turn on aeris maps in the belchertown 
> settings.  I don't know what has changed on their end because I have had 
> the same configuration for many years, but now the map will make thousands 
> of hits per hour and they will shut you down when you exceed your allowed 
> 5,000 hits.  I turned off the aeris maps and all looks well so far.
>
> On Wednesday, January 24, 2024 at 11:08:16 PM UTC-5 bchap...@gmail.com 
> wrote:
>
>> I've done that.  Should have mentioned in original post.  I've changed my 
>> password, deleted and created a new app.  My hit count reset at 1900EST and 
>> within an hour I was at ~600 hits, and that's with forcasting turned off in 
>> the conf file.  Aeris tech support has not been able to solve this.  I'm 
>> thinking I may need to delete my account with them and re-create a new 
>> one.  
>>
>> On Wednesday, January 24, 2024 at 7:38:45 PM UTC-5 bchap...@gmail.com 
>> wrote:
>>
>>> Is anyone else having problems with aeris forcasting?  For the past few 
>>> weeks my access credits have been running out resulting in my webpage not 
>>> being updated.  I've turned off forcasting in weewx.conf and when I watch 
>>> my activity on aeris the hits keep coming.  I don't know who is making 
>>> these requests.  My aeris credits are racking up at an average of a few 
>>> hundred an hour, even with forcasting turned off.  I've contacted aeris 
>>> tech support which has not been helpful.
>>>
>>

-- 
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/52afdb7c-adf9-48d6-ac09-efa5536494dfn%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

English version below.

Es gibt zu diesem Thema noch etwas Neues: eine 
Kurzfrist-Niederschlagsvorhersage. Da kann man  für die nächsten 2 Stunden 
im 5-Minuten-Abstand erfahren, ob man einen Platzregen zu gewärtigen hat. 
Die Radardaten des Deutschen Wetterdienstes enthalten eine solche 
Vorhersage (siehe die animierte GIF-Datei weiter oben). Hier kann man sie 
nun für einen beliebigen Ort herausziehen und als Tabelle oder sonst 
irgendwie darstellen, was die Kreativität beim Schreiben von Skin-Templates 
hergibt. Eine bloße Tabelle ist recht einfach:



#*set* $forecast = $day.radarRVRainRateForecast.series

#for $i *in* $forecast



$i[0]$i[1]$i[2]



#end for



Der Zeitraum (hier $day) ist dabei egal. Es wird immer die ganze Vorhersage 
zurückgeliefert. Man kann auch ein Template schreiben, das eine JSON-Datei 
daraus erzeugt, die dann von HighCharts in eine Graphik verwandelt wird. 
Voraussetzung, daß die Vorhersage abgerufen werden kann, ist, daß für den 
betreffenden Ort eine Abfrage des aktuellen Wertes konfiguriert ist. d.h. 
um radarRVRainRateForecast zu haben, muß es radarRVRainRate geben. Im 
Moment eignet sich das Wetter leider nur wenig zum Testen dieser 
Funktionalität, aber warten wir auf das nächste Tiefdruckgebiet.

Abgedeckt werden Deutschland, Luxemburg, die österreichischen Bundesländer 
Tirol (teilweise) und Vorarlberg sowie Nordwesttschechien. Die Genauigkeit 
wird durch das Raster von 1 km begrenzt.



Included in their radar data products the German Weather Service DWD 
provides a short time forecast of precipitation intensity with 5 minutes 
interval. This extension extracts those forecasts for locations specified 
by the user in the weewx.conf configuration file. So you can see if you may 
face a rain of cats and dogs at your station within the next 2 hours or 
something. The service covers Germany, Lëtzebuerg, Austrian states Tirol 
(parts of) and Vorarlberg as well as the north west of Czechia including 
Praha. The accuracy is limited by the 1 km grid.

It is simple to display the forecast as a table:



#*set* $forecast = $day.radarRVRainRateForecast.series

#for $i *in* $forecast



$i[0]$i[1]$i[2]



#end for



The timespan (here: $day) is irrelevant. You always get the whole forecast.

Unfortunately there is no chance to test this functionality now. You will 
have to wait for the next cyclone.

-- 
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/832fb8cb-1e1d-42d0-97f9-975f7190ff39n%40googlegroups.com.

Re: [weewx-user] Integrate rain24 with Packetsloop

[Tom Keffer]

Oh, it was the first thing I did after realizing my omission! Commit 9455fa1

.

On Sun, Jan 28, 2024 at 7:30 AM Remy Lavabre  wrote:

> thanks Tom,
>
> I had thought about putting rain = prefer_software but as this type of
> rain configuration is not documented in the Weewx documentation (or at
> least I didn't find it!) I didn't take the initiative. .. stupid I am ! :-(
>
> little suggestion Tom, perhaps it would be good to document this point in
> the [[Delta]] rain class?
> Well, not everyone is ignorant like me!! :-))
> Many thanks to you for your help Tom
>
> Le dimanche 28 janvier 2024 à 00:21:43 UTC+1, Tom Keffer a écrit :
>
>> My apologies. I forgot one important detail. The "[Delta]" section tells
>> WeeWX how to calculate rain, but you also have to include "rain" under
>> [StdWXCalculations] / [[Calculations]] in order to get it to do the actual
>> calculation. It looks like
>>
>> [StdWXCalculate]
>> [[Calculations]]
>> ...
>> rain = prefer_hardware
>>
>> ...
>> [[Delta]]
>> [[[rain]]]
>> input = dayRain
>>
>> On Sat, Jan 27, 2024 at 9:17 AM Remy Lavabre  wrote:
>>
>>> Hello Tom,
>>>
>>> I followed your instructions:
>>>
>>> 1/“rain” field present in the database
>>> 2/ “dayRain” field not present in the database
>>> 3/ My driver returns “dayRain” values and not “rain” values in the
>>> packetsloop
>>> 4/ [[Delta]] [[ [rain]]] input = dayRain added in weewx.conf (under
>>> [StdWXCalculate]).
>>>
>>> I did some tests : my driver returns 0.0 for dayRain but unfortunately
>>> the "rain" field in my database always remains NULL, even after several
>>> recordings in weewx.conf.
>>> Shouldn't "rain" field go to 0.0?
>>>
>>> THANKS
>>>
>>> Le vendredi 26 janvier 2024 à 22:48:03 UTC+1, Tom Keffer a écrit :
>>>
 If an observation type never gets reset to zero, you have two choices.
 1. Save the value. If you want to know daily use, take the difference
 of the value.
 2. Save the difference. That is, the change in the value over an
 archive period. If you want to know daily use, you would sum all the small
 deltas. This is like rain

 See the discussion *Accumulated vs delta energy
 *
  in
 the README of the Brultech driver for the pros and cons of the two
 approaches.

 It is not necessary to save "dayRain". WeeWX mostly uses "rain".
 Besides, as you note, it can always be calculated.



 On Fri, Jan 26, 2024 at 7:06 AM Remy Lavabre 
 wrote:

> And one more question
> Is it absolutely necessary to create a "dayRain" field in addition to
> the "rain" field in the weewx.sdb database?
> If the database only contains the [rain] field but the Weewx driver
> returns a "dayRain" field (cumulative rain over 24 hours since midnight)
> with a real value in each packetloop, the class [[Delta]] [[ [rain]]] 
> input
> = dayRain will it work??
> (the accumulation of rain since midnight is useless to me in a
> database field since it is easily calculated)
> Sorry for all the questions...and thanks again! ;-)
>
> Le vendredi 26 janvier 2024 à 15:46:04 UTC+1, Remy Lavabre a écrit :
>
>> Hello Tom and thank you for your response.
>>
>>  [StdWXCalculate]
>>  [[Calculations]]
>>  ...
>>  [[Delta]]
>>  [[[rain]]]
>>  input = dayRain
>>
>> This will calculate the rain difference between two records in weewx
>> sql based on the principle that the counter is reset to zero at midnight 
>> ->
>> PERFECT FOR THE RAIN 24H !
>>
>> Small additional question: if we wish to constantly calculate the
>> difference between two records values of a meter which *never*
>> resets to zero (such as an electricity or water meter), how should we
>> proceed?
>>
>> THANKS
>>
>> Le jeudi 18 janvier 2024 à 14:05:10 UTC+1, Tom Keffer a écrit :
>>
>>> Unfortunately (for you), WeeWX mostly uses observation type "rain",
>>> the amount of rain that fell since the last loop packet (what you are
>>> calling "instantaneous rain").
>>>
>>> You should assign the rain since midnight to type "dayRain".
>>>
>>> Then calculate "rain" as the difference between successive
>>> "dayRain" values. While this is a pretty simple calculation, there is an
>>> xtype that can do it for you.  See class Delta in weewx.wxxtypes
>>> .
>>> To use it, add this to weewx.conf:
>>>
>>> [StdWXCalculate]
>>> [[Calculations]]
>>> ...
>>> [[Delta]]
>>> [[[rain]]]
>>> input = 

[weewx-user] Help installing GW1000 driver.

[Phil Bilboe]

I have installed weewx onto my old laptop running Ubuntu 18.04.2 LTS and it 
is working in simulator mode and generating a webpage. When I try to 
install the GW1000 driver is get the following message.

sudo wee_extension --install=/var/tmp/gw1000-0.6.0b3.tar.gz
[sudo] password for phil: 
Request to install '/var/tmp/gw1000-0.6.0b3.tar.gz'
Extracting from tar archive /var/tmp/gw1000-0.6.0b3.tar.gz
Traceback (most recent call last):
  File "/usr/share/weewx/wee_extension", line 92, in 
main()
  File "/usr/share/weewx/wee_extension", line 84, in main
ext.install_extension(options.install)
  File "/usr/share/weewx/weecfg/extension.py", line 130, in 
install_extension
self.install_from_dir(extension_dir)
  File "/usr/share/weewx/weecfg/extension.py", line 150, in install_from_dir
installer_path, installer = 
weecfg.get_extension_installer(extension_dir)

  File "/usr/share/weewx/weecfg/__init__.py", line 1904, in 
get_extension_installer
installer = loader()
  File "/var/tmp/gw1000/install.py", line 396, in loader
  File "/var/tmp/gw1000/install.py", line 401, in __init__
  File "/var/tmp/gw1000/install.py", line 386, in version_compare
AttributeError: 'module' object has no attribute 'zip_longest'

Any suggestions as to why it won't install?

-- 
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/e95027eb-5db7-45be-9de8-f07ffafbf2c6n%40googlegroups.com.

[weewx-user] Help with installing weewx-gw1000 driver

[Phil Bilboe]

I'm new to linux and trying to install weewx to read my gw1100 gateway. 

I'm running Ubuntu 18.04.2 LTS and have completed the debian install and 
the simulator works and generates a webpage.

When I try to install the gw1000 driver I get the following:

phil@phil-Inspiron-1545:~$ wee_extension 
--install=/var/tmp/gw1000-0.6.0b3.tar.gz
Request to install '/var/tmp/gw1000-0.6.0b3.tar.gz'
Extracting from tar archive /var/tmp/gw1000-0.6.0b3.tar.gz
Traceback (most recent call last):
  File "/usr/share/weewx/wee_extension", line 92, in 
main()
  File "/usr/share/weewx/wee_extension", line 84, in main
ext.install_extension(options.install)
  File "/usr/share/weewx/weecfg/extension.py", line 130, in 
install_extension
self.install_from_dir(extension_dir)
  File "/usr/share/weewx/weecfg/extension.py", line 150, in install_from_dir
installer_path, installer = 
weecfg.get_extension_installer(extension_dir)
  File "/usr/share/weewx/weecfg/__init__.py", line 1904, in 
get_extension_installer
installer = loader()
  File "/var/tmp/gw1000/install.py", line 396, in loader
  File "/var/tmp/gw1000/install.py", line 401, in __init__
  File "/var/tmp/gw1000/install.py", line 386, in version_compare
AttributeError: 'module' object has no attribute 'zip_longest'

When I try to go to the next step and test the driver I get the following:

PYTHONPATH=/home/weewx/bin python -m user.gw1000 --test-driver
/usr/bin/python: No module named user.gw1000

or I get:
PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver
/usr/bin/python: No module named user.gw1000

I'm kind of lost as to what to do next. Any suggestions would be 
appreciated.

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

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

['michael.k...@gmx.at' via weewx-user]

Ich muss da jetzt endlich mal angehen. Die Radardaten in Kombination mit 
der Temperatur müssten sich ja auch gut eignen, um die Heizung für den 
Regenbecher anzusteuern, ohne sinnlos Energie zu verschwenden.

Karen K schrieb am Dienstag, 16. Januar 2024 um 21:04:01 UTC+1:

> Noch kommt hier relativ schnell etwas hinzu. Kartenausschnitte zeigten die 
> Ortsnamen ziemlich pixelig. Das hat sich jetzt verbessert. Es werden auch 
> mehr Orte angezeigt, wenn der Ausschnitt kleiner ist. Damit man die Grenzen 
> nicht so mühsam in Pixeln heraussuchen muß, kann man jetzt beim Schlüssel "
> map" anstelle der vier Zahlen auch ein Bundesland im ISO3166-2-Code 
> angeben, z.B. "DE-MV" für Mecklenburg-Vorpommern. Bis jetzt funktioniert 
> das allerdings nur für die ostdeutschen Bundesländer sowie die 
> österreichischen Bundesländer Vorarlberg (AT-8) und Tirol (AT-7). 
> Außerdem geht es für das Gebirge Harz ("Harz"), Deutschland im Ganzen ("DE") 
> und - für Tests der Skalierung - die ostdeutschen Bundesländer zusammen ("
> DE-Ost").

-- 
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/edf22d84-46e9-4d8b-b6ea-91b1e487d00dn%40googlegroups.com.

[weewx-user] Re: Aucrite sensor stopped working - does it need re-registration?

[ken.r...@gmail.com]

Hi Matt,

When I point the web browser at the hub, I only see 4 sensors, but I've 
always only seen 4 sensors even when all 6 were working.

Wireshark shows traffic from 5 of the 6 sensors, there's nothing from this 
6th sensor and nothing from an unknown sensor ID.

I don't have a 433MHz transceiver so I can't tell what the sensor is 
sending to the hub. The 433MHz repeater flickers when it transmits (and the 
other 5 sensors are switched off) so I know it's transmitting something to 
the hub, but the hub isn't sending anything on to Weeex from it.

Regards,
Ken.
On Sunday 28 January 2024 at 02:34:38 UTC+1 matthew wall wrote:

> ken,
>
> what do you see when you point a web browser at the hub?  are all of your 
> sensors listed?
>
> check everything.  watch the http requests from the hub to the machine 
> running weewx (use tcpdump, or wireshark, or turn up the verbosity in the 
> interceptor).  see which sensors are in the requests, see which ones are 
> not.  find out if the missing sensor is being reported by the hub but not 
> received by weewx.  or not even being reported by the hub.
>
> m
>  
>

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

[weewx-user] Re: Needed software for APRS

[Tom Hogland]

Maybe you can clarify something. Do you have a cabled VP2 with the serial 
connection, or a wireless VP2 and a serial datalogger in the console? 

You can use the aprs extension or weewx to write a report in aprs format, 
then use packages like aprsdigi, aprx, direwolf, or xastir to send the data 
to a connected radio. All have their own special configs, etc. to set up, 
and you'll need the correct cable to connect your specific radio to your 
soundcard interface. 

I have had a serial datalogger for about 15 years and no connection issues.

On Sunday, January 28, 2024 at 5:19:15 AM UTC-9 Massimiliano Buldrini wrote:

> I'm fine with any software solutions.
>
> I read that there are problems with datalogger serial and usb.
> Is better a datalogger  WeatherLinkIP interfaces ?
>
> Regards
> Massimiliano
> IZ4SJB
>
> Il giorno domenica 28 gennaio 2024 alle 15:13:38 UTC+1 Massimiliano 
> Buldrini ha scritto:
>
>> Yes
>>
>> Il giorno sabato 27 gennaio 2024 alle 23:47:23 UTC+1 Devonian ha scritto:
>>
>>> Direwolf ?
>>>
>>> Nigel
>>> G4ZAL
>>>
>>> On Saturday 27 January 2024 at 15:19:46 UTC Massimiliano Buldrini wrote:
>>>
 I have a Davis Vantage Pro 2 with Serial".

 I have a Raspberry P4, a serial card to connect directly to the GPIO, a 
 CM108 with audio and PTT that I want to connect to a portable radio that 
 acts as a DIGIPEATER

 What software are needed besides weewx to transmit data via radio and 
 via igate?

 Can someone give me some advice?

 Regards
 Massimiliano
 IZ4SJB[image: hardware.jpg]

>>>

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

Re: [weewx-user] Integrate rain24 with Packetsloop

[Remy Lavabre]

thanks Tom,

I had thought about putting rain = prefer_software but as this type of rain 
configuration is not documented in the Weewx documentation (or at least I 
didn't find it!) I didn't take the initiative. .. stupid I am ! :-(

little suggestion Tom, perhaps it would be good to document this point in 
the [[Delta]] rain class? 
Well, not everyone is ignorant like me!! :-))
Many thanks to you for your help Tom

Le dimanche 28 janvier 2024 à 00:21:43 UTC+1, Tom Keffer a écrit :

> My apologies. I forgot one important detail. The "[Delta]" section tells 
> WeeWX how to calculate rain, but you also have to include "rain" under 
> [StdWXCalculations] / [[Calculations]] in order to get it to do the actual 
> calculation. It looks like
>
> [StdWXCalculate]
> [[Calculations]]
> ...
> rain = prefer_hardware
>
> ...
> [[Delta]]
> [[[rain]]]
> input = dayRain
>
> On Sat, Jan 27, 2024 at 9:17 AM Remy Lavabre  wrote:
>
>> Hello Tom,
>>
>> I followed your instructions:
>>
>> 1/“rain” field present in the database
>> 2/ “dayRain” field not present in the database
>> 3/ My driver returns “dayRain” values and not “rain” values in the 
>> packetsloop
>> 4/ [[Delta]] [[ [rain]]] input = dayRain added in weewx.conf (under 
>> [StdWXCalculate]).
>>
>> I did some tests : my driver returns 0.0 for dayRain but unfortunately 
>> the "rain" field in my database always remains NULL, even after several 
>> recordings in weewx.conf.
>> Shouldn't "rain" field go to 0.0?
>>
>> THANKS
>>
>> Le vendredi 26 janvier 2024 à 22:48:03 UTC+1, Tom Keffer a écrit :
>>
>>> If an observation type never gets reset to zero, you have two choices.
>>> 1. Save the value. If you want to know daily use, take the difference of 
>>> the value.
>>> 2. Save the difference. That is, the change in the value over an archive 
>>> period. If you want to know daily use, you would sum all the small deltas. 
>>> This is like rain
>>>
>>> See the discussion *Accumulated vs delta energy 
>>> *
>>>  in 
>>> the README of the Brultech driver for the pros and cons of the two 
>>> approaches.
>>>
>>> It is not necessary to save "dayRain". WeeWX mostly uses "rain". 
>>> Besides, as you note, it can always be calculated.
>>>
>>>
>>>
>>> On Fri, Jan 26, 2024 at 7:06 AM Remy Lavabre  
>>> wrote:
>>>
 And one more question
 Is it absolutely necessary to create a "dayRain" field in addition to 
 the "rain" field in the weewx.sdb database?
 If the database only contains the [rain] field but the Weewx driver 
 returns a "dayRain" field (cumulative rain over 24 hours since midnight) 
 with a real value in each packetloop, the class [[Delta]] [[ [rain]]] 
 input 
 = dayRain will it work??
 (the accumulation of rain since midnight is useless to me in a database 
 field since it is easily calculated)
 Sorry for all the questions...and thanks again! ;-)

 Le vendredi 26 janvier 2024 à 15:46:04 UTC+1, Remy Lavabre a écrit :

> Hello Tom and thank you for your response.
>
>  [StdWXCalculate]
>  [[Calculations]]
>  ...
>  [[Delta]]
>  [[[rain]]]
>  input = dayRain
>
> This will calculate the rain difference between two records in weewx 
> sql based on the principle that the counter is reset to zero at midnight 
> -> 
> PERFECT FOR THE RAIN 24H !
>
> Small additional question: if we wish to constantly calculate the 
> difference between two records values of a meter which *never* resets 
> to zero (such as an electricity or water meter), how should we proceed?
>
> THANKS
>
> Le jeudi 18 janvier 2024 à 14:05:10 UTC+1, Tom Keffer a écrit :
>
>> Unfortunately (for you), WeeWX mostly uses observation type "rain", 
>> the amount of rain that fell since the last loop packet (what you are 
>> calling "instantaneous rain").
>>
>> You should assign the rain since midnight to type "dayRain".
>>
>> Then calculate "rain" as the difference between successive 
>> "dayRain" values. While this is a pretty simple calculation, there is an 
>> xtype that can do it for you.  See class Delta in weewx.wxxtypes 
>> . 
>> To use it, add this to weewx.conf:
>>
>> [StdWXCalculate]
>> [[Calculations]]
>> ...
>> [[Delta]]
>> [[[rain]]]
>> input = dayRain
>>
>>
>>
>>
>> On Wed, Jan 17, 2024 at 11:47 PM Remy Lavabre  
>> wrote:
>>
>>> Good morning,
>>>
>>> I created a [driver] for weewx to retrieve data from the Awekas API 
>>> (my Bresser weather station does not have a USB port).
>>>
>>> This works but regarding the 

[weewx-user] Re: Needed software for APRS

[Massimiliano Buldrini]

I'm fine with any software solutions.

I read that there are problems with datalogger serial and usb.
Is better a datalogger  WeatherLinkIP interfaces ?

Regards
Massimiliano
IZ4SJB

Il giorno domenica 28 gennaio 2024 alle 15:13:38 UTC+1 Massimiliano 
Buldrini ha scritto:

> Yes
>
> Il giorno sabato 27 gennaio 2024 alle 23:47:23 UTC+1 Devonian ha scritto:
>
>> Direwolf ?
>>
>> Nigel
>> G4ZAL
>>
>> On Saturday 27 January 2024 at 15:19:46 UTC Massimiliano Buldrini wrote:
>>
>>> I have a Davis Vantage Pro 2 with Serial".
>>>
>>> I have a Raspberry P4, a serial card to connect directly to the GPIO, a 
>>> CM108 with audio and PTT that I want to connect to a portable radio that 
>>> acts as a DIGIPEATER
>>>
>>> What software are needed besides weewx to transmit data via radio and 
>>> via igate?
>>>
>>> Can someone give me some advice?
>>>
>>> Regards
>>> Massimiliano
>>> IZ4SJB[image: hardware.jpg]
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/95703d59-5e4f-43bf-9d8f-d380cf841b24n%40googlegroups.com.

[weewx-user] Re: Needed software for APRS

[Massimiliano Buldrini]

Yes

Il giorno sabato 27 gennaio 2024 alle 23:47:23 UTC+1 Devonian ha scritto:

> Direwolf ?
>
> Nigel
> G4ZAL
>
> On Saturday 27 January 2024 at 15:19:46 UTC Massimiliano Buldrini wrote:
>
>> I have a Davis Vantage Pro 2 with Serial".
>>
>> I have a Raspberry P4, a serial card to connect directly to the GPIO, a 
>> CM108 with audio and PTT that I want to connect to a portable radio that 
>> acts as a DIGIPEATER
>>
>> What software are needed besides weewx to transmit data via radio and via 
>> igate?
>>
>> Can someone give me some advice?
>>
>> Regards
>> Massimiliano
>> IZ4SJB[image: hardware.jpg]
>>
>

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

[weewx-user] Re: weewx.drivers.vantage: Socket error while opening port 22222

[jterr...@gmail.com]

I am coming back to your first message of this discussion since  it seems 
that you are trying to use the weewx Vantage driver to connect to a 
Weatherlink Live.
The communication protocol of the Weatherlink Live is completely different 
of the one used by VP2 or Vantage Vue + datalogger., and the built-in 
Vantage driver will not work with a Weatherlink Live.

If you want weewx to capture data from the Weatherlink Live, you will have 
to use one of the available third-party weewx driver specifically written 
for the Weatherlink Live . See https://github.com/weewx/weewx/wiki/#drivers
Le dimanche 21 janvier 2024 à 22:13:44 UTC+1, Ed Surowiec a écrit :

> I am having trouble getting weewx to connect to my WeatherLink Live 
> ethernet box.  I am able to connect to the WeatherLink Live using a browser 
> and also using netcat to port 2 from the raspberry pi I have weewx 
> installed on.  Here is the error.  Any help would be appreciated.
>
>
>
> Jan 21 13:51:26 rpi-blue weewxd[12964]: INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
>
> Jan 21 13:51:26 rpi-blue weewxd[12964]: ERROR weewx.drivers.vantage: 
> Socket error while opening port 2 to ethernet host 10.0.1.180.
>
> Jan 21 13:51:26 rpi-blue weewxd[12964]: ERROR weewx.engine: Import of 
> driver failed: [Errno 111] Connection refused ()
>
>
> I am able to connect to weatherlink live box using the link 
> http://10.0.1.180:80/v1/current_conditions
>
> and see data in my browser.
>
>
> I can also connect to the weatherlink live with netcat from the raspberry 
> pi that I have weewx installed on.
>
> *pi@rpi-blue*:*~ $* nc -nvulp 2
>
> Bound on 0.0.0.0 2
>
> Connection received on 10.0.1.180 43539
>
>
> {"did":"001D0A712868","ts":1705869635,"conditions":[{"lsid":326721,"data_structure_type":1,"txid":1,"wind_speed_last":4.00,"wind_dir_last":207,"rain_size":1,"rain_rate_last":0,"rain_15_min":0,"rain_60_min":0,"rain_24_hr":28,"rain_storm":28,"rain_storm_start_at":1705832820,"rainfall_daily":28,"rainfall_monthly":54,"rainfall_year":54,"wind_speed_hi_last_10_min":10.00,"wind_dir_at_hi_speed_last_10_min":244}]}^C
>
>
> My weewx.config contains the following:
>
>
> ##
>
> [Vantage]
> # This section is for the Davis Vantage series of weather stations.
> 
> # Connection type: serial or ethernet 
> #  serial (the classic VantagePro)
> #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
>type = ethernet
> 
> # If the connection type is serial, a port must be specified:
> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
> # /dev/ttyUSB0 is a common USB port name
> # /dev/ttyS0   is a common serial port name
> #   BSD:
> # /dev/cuaU0   is a common serial port name
> port = /dev/ttyUSB0
> 
> # If the connection type is ethernet, an IP Address/hostname is 
> required:
>host = 10.0.1.180
> 
> ##
> # The rest of this section rarely needs any attention. 
> # You can safely leave it "as is."
> ##
> 
> # Serial baud rate (usually 19200)
> baudrate = 19200
> 
> # TCP port (when using the WeatherLinkIP)
> tcp_port = 2
> 
> # TCP send delay (when using the WeatherLinkIP):
> tcp_send_delay = 0.5
> 
> # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
> loop_request = 1
> 
> # The id of your ISS station (usually 1). If you use a wind meter 
> connected
> # to a anemometer transmitter kit, use its id
> iss_id = 1
> 
> # How long to wait for a response from the station before giving up (in
> # seconds; must be greater than 2)
> timeout = 4
> 
> # How long to wait before trying again (in seconds)
> wait_before_retry = 1.2
> 
> # How many times to try before giving up:
> max_tries = 4
> 
> # Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
> model_type = 2
> 
> # The driver to use:
> driver = weewx.drivers.vantage
>
>
> ##
>
>
>

-- 
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/47d0abd3-86a9-4738-bd4f-da816b37f6afn%40googlegroups.com.

[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

['michael.k...@gmx.at' via weewx-user]

0.6.0b6 still contains the wrong case for  
self.latest_sensor_data['datetime']
https://github.com/gjr80/weewx-gw1000/blob/fcd562c2dc7b33015f8a29683d0e1cf35d385470/bin/user/gw1000.py#L1614
gjr80 schrieb am Sonntag, 28. Januar 2024 um 01:55:20 UTC+1:

> Thank you, yes, self.latest_sensor_data['dateTime'] should be 
> self.latest_sensor_data['datetime']. Fixed in 0.6.0b6.
>
> Gary
> On Sunday 28 January 2024 at 04:59:19 UTC+10 michael.k...@gmx.at wrote:
>
>> Seems like, changed it to
>> if self.latest_sensor_data is None or sensor_data['datetime'] > 
>> self.latest_sensor_data['datetime']:
>> and it didn't crash again so far.
>>
>> michael.k...@gmx.at schrieb am Samstag, 27. Januar 2024 um 14:31:43 
>> UTC+1:
>>
>>> Case typo?
>>>
>>> if self.latest_sensor_data is None or sensor_data['datetime'] > 
>>> self.latest_sensor_data['dateTime']:
>>> michael.k...@gmx.at schrieb am Samstag, 27. Januar 2024 um 14:24:58 
>>> UTC+1:
>>>
 That part worked. You can tell by the weewx.restx: MQTT: Published 
 record entries in the log, there is only one Loop packet every 10s 
 (the poll interval).
 But after a few archive_intervals it crashed:

 2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Main loop 
 exiting. Shutting engine down.
 2024-01-27 14:17:25 weewxd[657388] INFO weewx.engine: Shutting down 
 StdReport thread
 2024-01-27 14:17:26 weewxd[657388] INFO user.gw1000: GatewayCollector 
 thread has been terminated
 2024-01-27 14:17:27 weewxd[657388] INFO user.gw1000: GatewayCollector 
 thread has been terminated
 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: Caught 
 unrecoverable exception:
 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
  'dateTime'
 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
  Traceback (most recent call last):

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
 "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 166, in 
 main

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
  engine.run()

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
 "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
 206, in run

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
  self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
 "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
 241, in dispatchEvent

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
  callback(event)

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
 "/home/pi/weewx-data/bin/user/gw1000.py", line 1504, in new_loop_packet

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
  self.process_queued_sensor_data(queue_data, event.packet['dateTime'])

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__: File 
 "/home/pi/weewx-data/bin/user/gw1000.py", line 1611, in 
 process_queued_sensor_data

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   if 
 self.latest_sensor_data is None or sensor_data['datetime'] > 
 self.latest_sensor_data['dateTime']:

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:  
  KeyError: 'dateTime'

 2024-01-27 14:17:27 weewxd[657388] CRITICAL __main__:   Exiting.


 michael.k...@gmx.at schrieb am Donnerstag, 25. Januar 2024 um 10:48:00 
 UTC+1:

> OK, I need to sort this out a little. I think I messed up with 0.6.0bx 
> and 0.5.0bx. Currently I've got too many things on my plate, and wasn't 
> as 
> focused on this topic, as I should have been, sorry for that. I'll do my 
> homework and check everything again.
>
> gjr80 schrieb am Mittwoch, 24. Januar 2024 um 22:24:13 UTC+1:
>
>> On Thursday 25 January 2024 at 06:56:42 UTC+10 michael.k...@gmx.at 
>> wrote:
>>
>> The log is from latest logs I posted are from b5. Sorry, I forgot to 
>> mention that I didn't use the file in your link above, I downloaded from 
>> the releases, and for b4 it says: removed, go for b5. b5 is producing 
>> two 
>> independent LOOP packets after a few on my RPi4.
>>
>>
>> Sorry, but I don't understand this. The latest log you posted 
>> yesterday is very clearly from b4:
>>
>> 2024-01-23 19:46:51 weewxd[232660] INFO weewx.engine: Loading station 
>> type GW1000 (user.gw1000) 
>> 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: GatewayDriver: 
>> version is 0.6.0b4 
>> 2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: device address 
>> is 10.0.1.85:45000
>>
>> b4 and b5 have not been