[weewx-user] Re: Ghost values in logger archive records

[Rob Cranfill]

1) No Weatherlink
2) Manufacturing code: MJ150429081

And thanks again!
On Friday, February 25, 2022 at 2:52:08 PM UTC-8 tke...@gmail.com wrote:

> The discussion of bogus archive records was intertwined with other, 
> unrelated, topics in another thread 
>  titled "WeeWX 
> V4.6.1 released", so I'm moving it here, to its own, dedicated, thread.
>
> The issue is that we have seen 3 different stations that emit bogus values 
> for fields such as "soilMoist1", "soilTemp1," etc., despite the requisite 
> sensor not being present. Here's the summary. Please correct me if I'm 
> wrong.
>
> Rob: Vantage Vue; firmware 3-Feb-2015 (V4.18)
> Gentil: Vantage Vue; firmware 3-Feb-2015 (V4.18)
>
> Gary: Vantage Vue; firmware 16-Apr-2018 (V4.33)
>
>
> I've been in contact with Davis and they have asked two questions:
>
> 1. Are you pushing to WeatherLink.com? If so, please provide your Device 
> ID. That will allow them to monitor remotely what your logger is emitting.
>
> 2. Please provide the manufacturer's code for your console. You can find 
> it on the back of your console on a barcode strip. This is to check for a 
> console / firmware mismatch. 
>
> Thanks all!
>
> -tk
>

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

[weewx-user] Re: Ghost values in logger archive records

[Gary Strand]

Thanks for the diligent digging!

1. I am not pushing to Weatherlink.

2. My Manufacturing Code is MS201022095

Your efforts are much appreciated!

On Friday, February 25, 2022 at 3:52:08 PM UTC-7 tke...@gmail.com wrote:

> The discussion of bogus archive records was intertwined with other, 
> unrelated, topics in another thread 
>  titled "WeeWX 
> V4.6.1 released", so I'm moving it here, to its own, dedicated, thread.
>
> The issue is that we have seen 3 different stations that emit bogus values 
> for fields such as "soilMoist1", "soilTemp1," etc., despite the requisite 
> sensor not being present. Here's the summary. Please correct me if I'm 
> wrong.
>
> Rob: Vantage Vue; firmware 3-Feb-2015 (V4.18)
> Gentil: Vantage Vue; firmware 3-Feb-2015 (V4.18)
>
> Gary: Vantage Vue; firmware 16-Apr-2018 (V4.33)
>
>
> I've been in contact with Davis and they have asked two questions:
>
> 1. Are you pushing to WeatherLink.com? If so, please provide your Device 
> ID. That will allow them to monitor remotely what your logger is emitting.
>
> 2. Please provide the manufacturer's code for your console. You can find 
> it on the back of your console on a barcode strip. This is to check for a 
> console / firmware mismatch. 
>
> Thanks all!
>
> -tk
>

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

[weewx-user] Ghost values in logger archive records

[Tom Keffer]

The discussion of bogus archive records was intertwined with other,
unrelated, topics in another thread
 titled "WeeWX V4.6.1
released", so I'm moving it here, to its own, dedicated, thread.

The issue is that we have seen 3 different stations that emit bogus values
for fields such as "soilMoist1", "soilTemp1," etc., despite the requisite
sensor not being present. Here's the summary. Please correct me if I'm
wrong.

Rob: Vantage Vue; firmware 3-Feb-2015 (V4.18)
Gentil: Vantage Vue; firmware 3-Feb-2015 (V4.18)

Gary: Vantage Vue; firmware 16-Apr-2018 (V4.33)


I've been in contact with Davis and they have asked two questions:

1. Are you pushing to WeatherLink.com? If so, please provide your Device
ID. That will allow them to monitor remotely what your logger is emitting.

2. Please provide the manufacturer's code for your console. You can find it
on the back of your console on a barcode strip. This is to check for a
console / firmware mismatch.

Thanks all!

-tk

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

Re: [weewx-user] Vantage barometric reduction in _loop_map

[Tom Keffer]

Right you are! Thanks.

Fixed in commit 70a947c

.

Nice to know someone is using type 2 packets.

On Fri, Feb 25, 2022 at 8:54 AM Paul G  wrote:

> I'm trying to understand how pressure is processed in weewx v4 and I see
> this line in the loop mapping dictionary:
>
>  'bar_reduction'   : lambda p, k: float(p[k]) / 1000.0 if p[k] else None,
>
> Since Barometric Reduction Method has a value in 0..2 shouldn't it be
> mapped with an identity function? E.g. lambda p, k: p[k]
>
> --
> 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/f9a8beec-04c9-4cc5-9ba8-ab6d3fb2afd6n%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/CAPq0zEBt7UX%3Dpt%3Di9mjuVB1%3DREdC8aCCRCjLCRMip0Y7afz0pw%40mail.gmail.com.

[weewx-user] Vantage barometric reduction in _loop_map

[Paul G]

I'm trying to understand how pressure is processed in weewx v4 and I see 
this line in the loop mapping dictionary:

 'bar_reduction'   : lambda p, k: float(p[k]) / 1000.0 if p[k] else None,

Since Barometric Reduction Method has a value in 0..2 shouldn't it be 
mapped with an identity function? E.g. lambda p, k: p[k] 

-- 
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/f9a8beec-04c9-4cc5-9ba8-ab6d3fb2afd6n%40googlegroups.com.

Re: [weewx-user] Re: Upgrade debian 11 bullseye

[Didier Decoodt]

I agree with you, I will try to disable brotli, it's a good idea
I have also opened a discussion on brotli google group, but no news...

Le ven. 25 févr. 2022 à 10:53, vhel...@gmail.com  a
écrit :

> That error does not have anythink to do with Weewx, you should google with
> error or try to disable that brotli compression and then upgrade.
>
> torstai 24. helmikuuta 2022 klo 12.21.07 UTC+2 didier@gmail.com
> kirjoitti:
>
>> Hi
>>
>> During the first upgrade (10.4 to 10.10), I have an error:
>>
>> invoke-rc.d: initscript apache2, action "restart" failed.
>> ● apache2.service - The Apache HTTP Server
>>Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor
>> preset: enabled)
>>Active: failed (Result: exit-code) since Wed 2022-02-23 18:55:55 CET;
>> 12ms ago
>>  Docs: https://httpd.apache.org/docs/2.4/
>>   Process: 17929 ExecStart=/usr/sbin/apachectl start (code=exited,
>> status=1/FAILURE)
>>
>> févr. 23 18:55:55 meteo systemd[1]: Starting The Apache HTTP Server...
>> févr. 23 18:55:55 meteo apachectl[17929]: AH00526: Syntax error on line 4
>> of /etc/apache2/mods-enabled/brotli.conf:
>> févr. 23 18:55:55 meteo apachectl[17929]: Invalid command
>> 'BrotliCompressionLevel', perhaps misspelled or defined by a module not
>> included in the server configuration
>> févr. 23 18:55:55 meteo apachectl[17929]: Action 'start' failed.
>> févr. 23 18:55:55 meteo apachectl[17929]: The Apache error log may have
>> more information.
>> févr. 23 18:55:55 meteo systemd[1]: apache2.service: Control process
>> exited, code=exited, status=1/FAILURE
>> févr. 23 18:55:55 meteo systemd[1]: apache2.service: Failed with result
>> 'exit-code'.
>> févr. 23 18:55:55 meteo systemd[1]: Failed to start The Apache HTTP
>> Server.
>>
>> May be due to brotli, I check brotli.conf (but I think it's correct...)
>>
>> 
>>   # Compression
>>   ## BrotliCompressionLevel: 0-11 (default: 11)
>>   BrotliCompressionLevel 10
>>   ## BrotliWindowSize: 10-24 (default: 22)
>>   BrotliWindowSize 22
>>   # Logging
>>   # Filter note
>>   BrotliFilterNote Input  brotli_in
>>   BrotliFilterNote Output brotli_out
>>   BrotliFilterNote Ratio  brotli_ratio
>>   #LogFormat '"%r" %{brotli_out}n/%{brotli_in}n (%{brotli_ratio}n)' brotli
>>   #CustomLog ${APACHE_LOG_DIR}/brotli_access.log brotli
>>   # Output filter
>>   AddOutputFilterByType BROTLI text/html text/plain text/css text/xml
>>   AddOutputFilterByType BROTLI text/css
>>   AddOutputFilterByType BROTLI application/x-javascript
>> application/javascript
>>   AddOutputFilterByType BROTLI application/rss+xml
>>   AddOutputFilterByType BROTLI application/xml
>>   AddOutputFilterByType BROTLI application/json
>>   # Global output filer if necessary.
>>   # SetOutputFilter BROTLI
>>   # SetEnvIfNoCase Request_URI \.txt$ no-br
>> 
>>
>> Le jeu. 24 févr. 2022 à 10:29, vhel...@gmail.com  a
>> écrit :
>>
>>> Hi,
>>>
>>> You can upgrade to Debian 11. Here's one howto:
>>> https://www.linuxtechi.com/how-to-upgrade-debian-10-to-debian-11/
>>> Since you are using VMware, take a snapshot before upgrade, and maybe
>>> also copy important weewx files to somewhere safe too.
>>> It should be flawless, but you newer know... :)
>>>
>>>
>>>
>>> keskiviikko 23. helmikuuta 2022 klo 18.21.14 UTC+2 didier@gmail.com
>>> kirjoitti:
>>>
 Thanks for your answer
 I have not a raspberry, this is a virtual machine 64bits on a
 vmware server, but I think that the upgrade is similar.

 Le mer. 23 févr. 2022 à 16:21, Aslak Vaa  a écrit :

> It is possible to make an upgrade from Raspbian OS Buster to Bullseye
> as long as you do not change from 32 bits to 64 bits version or vice 
> versa.
> You will find instructions on how to make an upgrade by searching the
> net with keywords "Raspbian OS Buster to Bullseye Raspberry Pi".
> The only issue is that you will have to keep buster in the
> file /etc/apt/sources.list.d/weewx.list. It will not work when you replace
> buster with bullseye in that file.
>
> I have a Raspberry Pi 4 Model B with 4 GB of RAM. I previously ran
> Buster in 32 bits version, and I wanted Bullseye in 64 bits version,.
> I started with a fresh installation of Bullseye 64 bits, and I made a
> full installation of weewx with extensions and all prerequisits. After
> transferring configuration,  database and other changed files from old
> Buster setup and starting up weewx, everything worked just fine.
> If you have 4 GB RAM or more in your Raspberry Pi, I will recommend
> that you go for the 64 bits version.
> With older RPis 32 bits Bullseye will be the only option even if RPi 3
> is able to run the 64 bits version of OS.
>
> On Wednesday, February 23, 2022 at 2:08:21 PM UTC+1
> didier@gmail.com wrote:
>
>> Hi
>>
>> Today I have a debian 10, weewx 4.6.2 and Belchertown skin 1.3b1
>> (working perfectly)
>> Is it possible to upgarde debian to next 

Re: [weewx-user] Re: Upgrade debian 11 bullseye

[vhel...@gmail.com]

That error does not have anythink to do with Weewx, you should google with 
error or try to disable that brotli compression and then upgrade.

torstai 24. helmikuuta 2022 klo 12.21.07 UTC+2 didier@gmail.com 
kirjoitti:

> Hi
>
> During the first upgrade (10.4 to 10.10), I have an error:
>
> invoke-rc.d: initscript apache2, action "restart" failed.
> ● apache2.service - The Apache HTTP Server
>Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor 
> preset: enabled)
>Active: failed (Result: exit-code) since Wed 2022-02-23 18:55:55 CET; 
> 12ms ago
>  Docs: https://httpd.apache.org/docs/2.4/
>   Process: 17929 ExecStart=/usr/sbin/apachectl start (code=exited, 
> status=1/FAILURE)
>
> févr. 23 18:55:55 meteo systemd[1]: Starting The Apache HTTP Server...
> févr. 23 18:55:55 meteo apachectl[17929]: AH00526: Syntax error on line 4 
> of /etc/apache2/mods-enabled/brotli.conf:
> févr. 23 18:55:55 meteo apachectl[17929]: Invalid command 
> 'BrotliCompressionLevel', perhaps misspelled or defined by a module not 
> included in the server configuration
> févr. 23 18:55:55 meteo apachectl[17929]: Action 'start' failed.
> févr. 23 18:55:55 meteo apachectl[17929]: The Apache error log may have 
> more information.
> févr. 23 18:55:55 meteo systemd[1]: apache2.service: Control process 
> exited, code=exited, status=1/FAILURE
> févr. 23 18:55:55 meteo systemd[1]: apache2.service: Failed with result 
> 'exit-code'.
> févr. 23 18:55:55 meteo systemd[1]: Failed to start The Apache HTTP Server.
>
> May be due to brotli, I check brotli.conf (but I think it's correct...)
>
> 
>   # Compression
>   ## BrotliCompressionLevel: 0-11 (default: 11)
>   BrotliCompressionLevel 10
>   ## BrotliWindowSize: 10-24 (default: 22)
>   BrotliWindowSize 22
>   # Logging
>   # Filter note
>   BrotliFilterNote Input  brotli_in
>   BrotliFilterNote Output brotli_out
>   BrotliFilterNote Ratio  brotli_ratio
>   #LogFormat '"%r" %{brotli_out}n/%{brotli_in}n (%{brotli_ratio}n)' brotli
>   #CustomLog ${APACHE_LOG_DIR}/brotli_access.log brotli
>   # Output filter
>   AddOutputFilterByType BROTLI text/html text/plain text/css text/xml
>   AddOutputFilterByType BROTLI text/css
>   AddOutputFilterByType BROTLI application/x-javascript 
> application/javascript
>   AddOutputFilterByType BROTLI application/rss+xml
>   AddOutputFilterByType BROTLI application/xml
>   AddOutputFilterByType BROTLI application/json
>   # Global output filer if necessary.
>   # SetOutputFilter BROTLI
>   # SetEnvIfNoCase Request_URI \.txt$ no-br
> 
>
> Le jeu. 24 févr. 2022 à 10:29, vhel...@gmail.com  a 
> écrit :
>
>> Hi,
>>
>> You can upgrade to Debian 11. Here's one howto: 
>> https://www.linuxtechi.com/how-to-upgrade-debian-10-to-debian-11/
>> Since you are using VMware, take a snapshot before upgrade, and maybe 
>> also copy important weewx files to somewhere safe too.
>> It should be flawless, but you newer know... :) 
>>
>>
>>
>> keskiviikko 23. helmikuuta 2022 klo 18.21.14 UTC+2 didier@gmail.com 
>> kirjoitti:
>>
>>> Thanks for your answer
>>> I have not a raspberry, this is a virtual machine 64bits on a 
>>> vmware server, but I think that the upgrade is similar.
>>>
>>> Le mer. 23 févr. 2022 à 16:21, Aslak Vaa  a écrit :
>>>
 It is possible to make an upgrade from Raspbian OS Buster to Bullseye 
 as long as you do not change from 32 bits to 64 bits version or vice versa.
 You will find instructions on how to make an upgrade by searching the 
 net with keywords "Raspbian OS Buster to Bullseye Raspberry Pi". 
 The only issue is that you will have to keep buster in the 
 file /etc/apt/sources.list.d/weewx.list. It will not work when you replace 
 buster with bullseye in that file.

 I have a Raspberry Pi 4 Model B with 4 GB of RAM. I previously ran 
 Buster in 32 bits version, and I wanted Bullseye in 64 bits version,.
 I started with a fresh installation of Bullseye 64 bits, and I made a 
 full installation of weewx with extensions and all prerequisits. After 
 transferring configuration,  database and other changed files from old 
 Buster setup and starting up weewx, everything worked just fine.
 If you have 4 GB RAM or more in your Raspberry Pi, I will recommend 
 that you go for the 64 bits version. 
 With older RPis 32 bits Bullseye will be the only option even if RPi 3 
 is able to run the 64 bits version of OS. 

 On Wednesday, February 23, 2022 at 2:08:21 PM UTC+1 
 didier@gmail.com wrote:

> Hi
>
> Today I have a debian 10, weewx 4.6.2 and Belchertown skin 1.3b1 
> (working perfectly)
> Is it possible to upgarde debian to next release 11 bullseye ?
>
> If yes, what is the procedure?
>
> Many thanks
>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an