Re: [weewx-user] No PFM found for MEZ025

[Greg from Oz]

 lid = MEZ025

should be 

 lid = MEZ024

as there is no MEZ025 just like the error messages says.just guessing.


On Monday, 2 November 2020 14:42:15 UTC+11, John Kline wrote:
>
> NWS: no PFM found for MEZ025 in forecast from GYX
>
>
> Seems like a good error message to me.  MEZ025 is not where to be found on 
> the page.
>
> Did you mean MEZ024?
>
> On Nov 1, 2020, at 7:15 PM, weather list > 
> wrote:
>
> I have fthe forecast extension installed, with NWS set up as:
>
> [[NWS]]
> lid = MEZ025
> foid = GYX
>
> WeeWx log reports:
>
>
> Nov  1 22:04:27 raspberry-NUC62 weewx[27447] ERROR user.forecast: 
> NWSThread: NWS: no PFM found for MEZ025 in forecast from GYX
> Nov  1 22:05:18 raspberry-NUC62 weewx[27447] ERROR user.forecast: 
> NWSThread: NWS: no PFM found for MEZ025 in forecast from GYX
>
> And yet, this URL 
>  
> seems 
> to return PFM data. Am I making an obvious (not to me) error here?
>
> Point Forecast Matrices 
> Issued by NWS Portland, ME
>
> Current Version | Previous Version | Text Only | Print | Product List | 
> Glossary On
> Versions: 1 2 3 4 5 6 7 8 9 10 11 12
> 000
> FOUS51 KGYX 020103
> PFMGYX
>
> Point Forecast Matrices
> National Weather Service Gray ME
> 802 PM EST Sun Nov 1 2020
>
> *MEZ024*-020900-
> Portland-Cumberland ME
> 43.65N  70.32W Elev. 75 ft
> 802 PM EST Sun Nov 1 2020
>
> Date   11/01/20  Mon 11/02/20Tue 11/03/20 
>Wed
> EST 3hrly 16 19 22 01 04 07 10 13 16 19 22 01 04 07 10 13 16 19 22 01 
> 04 07
> UTC 3hrly 21 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 
> 09 12
>
> Min/Max  39  41  29  42   
>26
> Temp50 48 42 39 40 40 35 32 31 31 30 30 37 41 39 33 31 30 
> 28 28
> Dewpt   47 45 39 34 29 25 21 18 20 21 22 23 21 18 18 18 18 17 
> 17 20
> RH  89 89 89 82 64 55 56 56 63 66 72 75 52 39 42 53 58 58 
> 63 71
> Wind dir S  W NW  W  W  W  W  W  W SW  W  W NW NW NW NW NW  N 
> NW  S
> Wind spd 8 10 10 12 20 27 26 19 12  9  6 10 14 14 12  6  5  2 
>  2  2
> Wind gust   35 40 44 32
> Clouds  OV OV B2 B1 B2 SC SC FW SC B2 B1 B1 SC SC FW FW FW FW 
> SC SC
> PoP 12hr 90  20  40  30   
> 5
> QPF 12hr   0.24   00.02   0   
> 0
> Snow 12hr 00-00   00-00   T
> Rain D  L
> Rain shwrs SS
> SnowshwrsS  C  C  C
> Wind chill   31 31 30 23 19 20 21 23 21 2831 27 25
> Min chill3130192021232725 
>26
> Wind Y  Y  Y
>
>
> Date   11/04  Thu 11/05/20  Fri 11/06/20  Sat 11/07/20  Sun 
> 11/08/20
> EST 6hrly 13 19   01 07 13 19   01 07 13 19   01 07 13 19   01 07 13 19
> UTC 6hrly 18 00   06 12 18 00   06 12 18 00   06 12 18 00   06 12 18 00
>
> Max/Min  48  3960  4562  4461  4462
> Temp  46 43   41 41 58 52   48 46 60 52   48 45 60 52   48 45 60 53
> Dewpt 27 34   36 38 44 45   44 44 46 46   44 42 45 45   43 43 46 47
> PWind dir S  SWSW  SWSW   W W   WSW
> Wind charLT  LTGN  LTLT  LTLT  LTLT
> Avg cloudsSC FW   FW FW FW SC   B1 B2 B1 SC   SC SC SC FW   SC SC SC SC
> PoP 12hr  0   0 0   0 0   0 0   0 5
>
> $$
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/20D9FD93-D7F6-4A14-9BD9-4228FC98EEE2%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/63e306cf-235f-4da4-ad34-32647b9326feo%40googlegroups.com.

Re: [weewx-user] Re: Sunshine Hours

[gjr80]

Kalli,

I've added an approximation for sunshine time to WeeWX-WD. The algorithm 
involves calculating the elapsed time in seconds for which the WeeWX field '
radiation' is above a set threshold level and storing this time in field '
sunshine' in the WeeWX-WD database weewxwd.sdb. The default threshold level 
is 120 W/m2, but can be adjusted using the sunshine_threshold config item 
under the [Weewx-WD] stanza in weewx.conf. So in an archive record if 
radiation is above the threshold value the sunshine field will be set to 
the interval (in seconds) covered by the archive record. So if your archive 
interval is set to 300, field sunshine in that archive record would contain 
300, if radiation was below the threshold value then field sunshine will be 
0. Field sunshine is not added to loop packets, only archive records. 

You can then use field sunshine in report tags just like other WeeWX 
fields, though you will need to set the binding for each tag. For example, 
the sunshine time for today would be:

$day($data_binding='wd_binding').sunshine.sum

I have also populated the sunshine hour tags in testtags.php, so any 
sites/apps that use sunshine hours from testtags.php should now display 
data. I am not sure what FreshWDL uses, let's get WeeWX-WD working properly 
with sunshine then we can come back to FreshWDL if necessary.

Unfortunately you are going to have to upgrade to WeeWX-WD v2.1.0, adding '
sunshine' to a WeeWX-WD v1.x version was more work than I was prepared to 
do. The upgrade process is straight forward and I have detailed the steps 
below.

To upgrade WeeWX-WD v1.x to v2.1.0 (the following steps are based on you 
having a package install rather than a setup.py install, if you have a 
setup.py install let me know and I will provide appropriate instructions):

1. download the v2.1.0 extension package:

$ wget -P /var/tmp 
https://github.com/gjr80/weewx-weewx-wd/releases/download/v2.1.0/weewxwd-2.1.0.tar.gz

2. stop WeeWX and backup your WeeWX and WeeWX-WD databases:

$ sudo cp /var/lib/weewx/weewx.sdb /var/lib/weewx/weewx_backup.sdb
$ sudo cp /var/lib/weewx/weewxwd.sdb /var/lib/weewx/weewxwd_backup.sdb

3. install v2.1.0:

$ sudo wee_extension --install=/var/tmp/weewxwd-2.1.0.tar.gz

4. remove some v1.x residue that the installer cannot remove:

$ sudo rm -R /etc/weewx/skins/SteelGauges
$ sudo rm /usr/share/weewx/user/imageStackedWindRose3.py*
$ sudo rm /usr/share/weewx/user/wd_database
$ sudo rm /usr/share/weewx/user/wdAstroSearchX3.py*
$ sudo rm /usr/share/weewx/user/wdSearchX3.py*
$ sudo rm /usr/share/weewx/user/wdTaggedStats3.py*
$ sudo rm /usr/share/weewx/user/weewxwd3.py*

5. edit weewx.conf and make the following changes:

- under [StdReport] delete the [[wdSteelGauges]] stanza in full
- under [DataBindings] [[wd_binding]] change:

schema = user.weewxwd3.schema

to

schema = user.wdschema.weewxwd_schema

- under [Engine] [[Services]] delete the user.weewxwd3.WdWXCalculate entry 
from process_services
- under [Engine] [[Services]] delete user.weewxwd3.WdArchive from 
archive_services

WeeWX-WD will now add a field 'sunshine' to each archive record but it will 
not be saved to database (whilst the WeeWX-WD database schema now includes 
field 'sunshine' your WeeWX-WD database will not include field 'sunshine' 
as the database was created using the old WeeWX-WD schema). To add field 
sunshine to the WeeWX-WD database: 

1. use the utility wee_database to create a new copy WeeWX-WD database with 
the new schema and populate it with data from the old WeeWX-WD database:

$ sudo wee_database /etc/weewx/weewx.conf --reconfigure --binding=wd_binding

2. you will now have a new WeeWX-WD database named weewxwd.sdb_new that 
includes field sunshine, you now need to swap your old WeeWX-WD database 
for this new database:

$ sudo mv /var/lib/weewx/weewxwd.sdb /var/lib/weewx/weewxwd_orig.sdb
$ sudo mv /var/lib/weewx/weewxwd.sdb_new /var/lib/weewx/weewxwd.sdb

3. the daily summaries in the new database should be rebuilt on the next 
WeeWX startup but let's do it manually to make sure:

$ sudo wee_database /etc/weewx/weewx.conf --binding=wd_binding 
--rebuild-daily

You should now be able to restart WeeWX and WeeWX-WD will populate field 
sunshine in the WeeWX-WD database and the sunshine hours fields in 
testtags.php should also be populated.

Gary
On Monday, 2 November 2020 at 08:26:42 UTC+10 gjr80 wrote:

> Hi Kalli,
>
> Have written the code but just sorting out a couple of unrelated issues 
> that are causing problems under WeeWX v3.8.0. Won't be long.
>
> Gary
>
> On Sunday, 1 November 2020 at 23:26:07 UTC+10 Kalli wrote:
>
>> Hello Gir80
>> I'm curious what you're doing great again.
>>
>> cu.Kalli
>>
>>
>>
>> Am Dienstag, 27. Oktober 2020 22:39:17 UTC+1 schrieb gjr80:
>>>
>>> Thanks Kalli, I will put something together and email you.
>>>
>>> Gary
>>>
>>> On Wednesday, 28 October 2020 at 01:52:30 UTC+10 Kalli wrote:
>>>
 Gir80 I have the weewx 3.8 weewx wd v1.3 

 

Re: [weewx-user] No PFM found for MEZ025

[John Kline]

> NWS: no PFM found for MEZ025 in forecast from GYX

Seems like a good error message to me.  MEZ025 is not where to be found on the 
page.

Did you mean MEZ024?

> On Nov 1, 2020, at 7:15 PM, weather list  wrote:
> 
> I have fthe forecast extension installed, with NWS set up as:
> 
> [[NWS]]
> lid = MEZ025
> foid = GYX
> 
> WeeWx log reports:
> 
> 
> Nov  1 22:04:27 raspberry-NUC62 weewx[27447] ERROR user.forecast: NWSThread: 
> NWS: no PFM found for MEZ025 in forecast from GYX
> Nov  1 22:05:18 raspberry-NUC62 weewx[27447] ERROR user.forecast: NWSThread: 
> NWS: no PFM found for MEZ025 in forecast from GYX
> 
> And yet, this URL seems to return PFM data. Am I making an obvious (not to 
> me) error here?
> 
> Point Forecast Matrices 
> Issued by NWS Portland, ME
> 
> Current Version | Previous Version | Text Only | Print | Product List | 
> Glossary On
> Versions: 1 2 3 4 5 6 7 8 9 10 11 12
> 000
> FOUS51 KGYX 020103
> PFMGYX
> 
> Point Forecast Matrices
> National Weather Service Gray ME
> 802 PM EST Sun Nov 1 2020
> 
> MEZ024-020900-
> Portland-Cumberland ME
> 43.65N  70.32W Elev. 75 ft
> 802 PM EST Sun Nov 1 2020
> 
> Date   11/01/20  Mon 11/02/20Tue 11/03/20
> Wed
> EST 3hrly 16 19 22 01 04 07 10 13 16 19 22 01 04 07 10 13 16 19 22 01 04 
> 07
> UTC 3hrly 21 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 09 
> 12
> 
> Min/Max  39  41  29  42  
> 26
> Temp50 48 42 39 40 40 35 32 31 31 30 30 37 41 39 33 31 30 28 
> 28
> Dewpt   47 45 39 34 29 25 21 18 20 21 22 23 21 18 18 18 18 17 17 
> 20
> RH  89 89 89 82 64 55 56 56 63 66 72 75 52 39 42 53 58 58 63 
> 71
> Wind dir S  W NW  W  W  W  W  W  W SW  W  W NW NW NW NW NW  N NW  
> S
> Wind spd 8 10 10 12 20 27 26 19 12  9  6 10 14 14 12  6  5  2  2  
> 2
> Wind gust   35 40 44 32
> Clouds  OV OV B2 B1 B2 SC SC FW SC B2 B1 B1 SC SC FW FW FW FW SC 
> SC
> PoP 12hr 90  20  40  30   
> 5
> QPF 12hr   0.24   00.02   0   > 0
> Snow 12hr 00-00   00-00   T
> Rain D  L
> Rain shwrs SS
> SnowshwrsS  C  C  C
> Wind chill   31 31 30 23 19 20 21 23 21 2831 27 25
> Min chill3130192021232725
> 26
> Wind Y  Y  Y
> 
> 
> Date   11/04  Thu 11/05/20  Fri 11/06/20  Sat 11/07/20  Sun 11/08/20
> EST 6hrly 13 19   01 07 13 19   01 07 13 19   01 07 13 19   01 07 13 19
> UTC 6hrly 18 00   06 12 18 00   06 12 18 00   06 12 18 00   06 12 18 00
> 
> Max/Min  48  3960  4562  4461  4462
> Temp  46 43   41 41 58 52   48 46 60 52   48 45 60 52   48 45 60 53
> Dewpt 27 34   36 38 44 45   44 44 46 46   44 42 45 45   43 43 46 47
> PWind dir S  SWSW  SWSW   W W   WSW
> Wind charLT  LTGN  LTLT  LTLT  LTLT
> Avg cloudsSC FW   FW FW FW SC   B1 B2 B1 SC   SC SC SC FW   SC SC SC SC
> PoP 12hr  0   0 0   0 0   0 0   0 5
> 
> $$
> -- 
> 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/20D9FD93-D7F6-4A14-9BD9-4228FC98EEE2%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/768B45FB-0BB9-4B2B-934C-E9DE8E330DF2%40johnkline.com.

[weewx-user] No PFM found for MEZ025

[weather list]

I have fthe forecast extension installed, with NWS set up as:

[[NWS]]
lid = MEZ025
foid = GYX

WeeWx log reports:


Nov  1 22:04:27 raspberry-NUC62 weewx[27447] ERROR user.forecast: NWSThread: 
NWS: no PFM found for MEZ025 in forecast from GYX
Nov  1 22:05:18 raspberry-NUC62 weewx[27447] ERROR user.forecast: NWSThread: 
NWS: no PFM found for MEZ025 in forecast from GYX

And yet, this URL 
 
seems to return PFM data. Am I making an obvious (not to me) error here?

Point Forecast Matrices 
Issued by NWS Portland, ME

Current Version | Previous Version | Text Only | Print | Product List | 
Glossary On
Versions: 1 2 3 4 5 6 7 8 9 10 11 12
000
FOUS51 KGYX 020103
PFMGYX

Point Forecast Matrices
National Weather Service Gray ME
802 PM EST Sun Nov 1 2020

MEZ024-020900-
Portland-Cumberland ME
43.65N  70.32W Elev. 75 ft
802 PM EST Sun Nov 1 2020

Date   11/01/20  Mon 11/02/20Tue 11/03/20Wed
EST 3hrly 16 19 22 01 04 07 10 13 16 19 22 01 04 07 10 13 16 19 22 01 04 07
UTC 3hrly 21 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 09 12

Min/Max  39  41  29  42  26
Temp50 48 42 39 40 40 35 32 31 31 30 30 37 41 39 33 31 30 28 28
Dewpt   47 45 39 34 29 25 21 18 20 21 22 23 21 18 18 18 18 17 17 20
RH  89 89 89 82 64 55 56 56 63 66 72 75 52 39 42 53 58 58 63 71
Wind dir S  W NW  W  W  W  W  W  W SW  W  W NW NW NW NW NW  N NW  S
Wind spd 8 10 10 12 20 27 26 19 12  9  6 10 14 14 12  6  5  2  2  2
Wind gust   35 40 44 32
Clouds  OV OV B2 B1 B2 SC SC FW SC B2 B1 B1 SC SC FW FW FW FW SC SC
PoP 12hr 90  20  40  30   5
QPF 12hr   0.24   00.02   0   0
Snow 12hr 00-00   00-00   T
Rain D  L
Rain shwrs SS
SnowshwrsS  C  C  C
Wind chill   31 31 30 23 19 20 21 23 21 2831 27 25
Min chill313019202123272526
Wind Y  Y  Y


Date   11/04  Thu 11/05/20  Fri 11/06/20  Sat 11/07/20  Sun 11/08/20
EST 6hrly 13 19   01 07 13 19   01 07 13 19   01 07 13 19   01 07 13 19
UTC 6hrly 18 00   06 12 18 00   06 12 18 00   06 12 18 00   06 12 18 00

Max/Min  48  3960  4562  4461  4462
Temp  46 43   41 41 58 52   48 46 60 52   48 45 60 52   48 45 60 53
Dewpt 27 34   36 38 44 45   44 44 46 46   44 42 45 45   43 43 46 47
PWind dir S  SWSW  SWSW   W W   WSW
Wind charLT  LTGN  LTLT  LTLT  LTLT
Avg cloudsSC FW   FW FW FW SC   B1 B2 B1 SC   SC SC SC FW   SC SC SC SC
PoP 12hr  0   0 0   0 0   0 0   0 5

$$

-- 
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/20D9FD93-D7F6-4A14-9BD9-4228FC98EEE2%40gmail.com.

[weewx-user] Re: weewx-multi and sdr.conf

[Rob Wolff]

I had the same issue. Resolved it by adding

[SDR]
driver = user.sdr
path = /usr/local/bin
ld_library_path = /usr/local/lib

to my weewx.conf
Hope this helps.
On Sunday, May 31, 2020 at 3:39:26 PM UTC-4 weatherl...@gmail.com wrote:

> I have three instances running in multi (weewx, sdr, wflow) but the 
> sdr.instance throws this error:
>
>>
>> May 31 15:29:38 NUC2498 weewx-sdr[4919]: import of driver failed: failed 
> to start process 'rtl_433 -M utc -F json -G': [Errno 2] No such file or 
> directory ()
>
> which rtl_433
> /usr/local/bin/rtl_433
>
> Running sdr.conf manually works fine: sudo bin/weewxd sdr.conf
>
> Can someone point me to what is causing this?
>
> May 31 15:29:38 NUC2498 weewx-sdr[4915]: engine: Initializing weewx 
> version 3.9.1
> May 31 15:29:38 NUC2498 weewx-sdr[4915]: engine: Using Python 2.7.13 (
> default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
> May 31 15:29:38 NUC2498 weewx-sdr[4915]: engine: Platform Linux-4.9.0-12-
> amd64-x86_64-with-debian-9.12
> May 31 15:29:38 NUC2498 weewx-sdr[4915]: engine: Locale is 'en_US.UTF-8'
> May 31 15:29:38 NUC2498 weewx-sdr[4915]: engine: pid file is /var/run/
> weewx-sdr.pid
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: engine: Using configuration file 
> /home/weewx/sdr.conf
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: engine: Debug is 1
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: engine: Initializing engine
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: engine: Loading station type SDR 
> (user.sdr)
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: sdr: MainThread: driver version 
> is 0.64
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: sdr: MainThread: sensor map is {
> 'extraTemp2': 'temperature.*.AmbientF007THPacket', 'extraTemp3': 
> 'temperature.001A.AcuriteLightningPacket', 'soilTemp1': 
> 'strikes_total.001A.AcuriteLightningPacket', 'soilTemp2': 
> 'distance.001A.AcuriteLightningPacket', 'leafTemp2': 
> 'depth.*.TSFT002Packet'}
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: sdr: MainThread: deltas is {
> 'strikes': 'strikes_total', 'rain': 'rain_total'}
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: sdr: MainThread: startup process 
> 'rtl_433 
> -M utc -F json -G'
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: import of driver failed: failed 
> to start process 'rtl_433 -M utc -F json -G': [Errno 2] No such file or 
> directory ()
> May 31 15:29:38 NUC2498 weewx-sdr[4919]: engine: Unable to load driver: 
> failed to start process 'rtl_433 -M utc -F json -G': [Errno 2] No such 
> file or directory
> May 31 15:29:38 NUC2498 weewx-sdr[4919]:   Waiting 60 seconds then 
> retrying...
> May 31 15:29:40 NUC2498 weewx[4249]: sdr: MainThread: lines=[]
> May 31 15:29:46 NUC2498 weewx[4249]: sdr: MainThread: lines=['{"time" : 
> "2020-05-31 19:29:42", "model" : "Ambient Weather F007TH 
> Thermo-Hygrometer", "device" : 97, "channel" : 1, "battery" : "OK", 
> "temperature_F" : 89.900, "humidity" : 41, "mic" : "CRC"}\n']
> May 31 15:29:46 NUC2498 weewx[4249]: sdr: MainThread: packet={'extraTemp2'
> : 89.9, 'usUnits': 1, 'dateTime': 1590953382}
> May 31 15:29:49 NUC2498 weewx[4249]: sdr: MainThread: lines=[]
> May 31 15:29:53 NUC2498 weewx[4249]: sdr: MainThread: lines=['{"time" : 
> "2020-05-31 19:29:49", "model" : "TS-FT002", "id" : 127, "depth_cm" : 216, 
> "temperature_C" : 39.000, "transmit_s" : 180, "flags" : 8, "mic" : 
> "CHECKSUM"}\n', '{"time" : "2020-05-31 19:29:50", "model" : "TS-FT002", 
> "id" : 127, "depth_cm" : 216, "temperature_C" : 39.000, "transmit_s" : 180, 
> "flags" : 8, "mic" : "CHECKSUM"}\n']
> May 31 15:29:53 NUC2498 weewx[4249]: sdr: MainThread: parse_json: unknown 
> model TS-FT002
> May 31 15:29:53 NUC2498 weewx[4249]: sdr: MainThread: punt unrecognized 
> line '{"time" : "2020-05-31 19:29:49", "model" : "TS-FT002", "id" : 127, 
> "depth_cm" : 216, "temperature_C" : 39.000, "transmit_s" : 180, "flags" : 
> 8, "mic" : "CHECKSUM"}#012'
> May 31 15:29:53 NUC2498 weewx[4249]: sdr: MainThread: parse_json: unknown 
> model TS-FT002
> May 31 15:29:53 NUC2498 weewx[4249]: sdr: MainThread: punt unrecognized 
> line '{"time" : "2020-05-31 19:29:50", "model" : "TS-FT002", "id" : 127, 
> "depth_cm" : 216, "temperature_C" : 39.000, "transmit_s" : 180, "flags" : 
> 8, "mic" : "CHECKSUM"}#012'
>
>
>
> NUC running Debian 9
> WeeWx 3.9.1
>

-- 
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/4b435cd0-d208-4239-847d-d14b7f76f31en%40googlegroups.com.

Re: [weewx-user] Re: Sunshine Hours

[gjr80]

Hi Kalli,

Have written the code but just sorting out a couple of unrelated issues 
that are causing problems under WeeWX v3.8.0. Won't be long.

Gary

On Sunday, 1 November 2020 at 23:26:07 UTC+10 Kalli wrote:

> Hello Gir80
> I'm curious what you're doing great again.
>
> cu.Kalli
>
>
>
> Am Dienstag, 27. Oktober 2020 22:39:17 UTC+1 schrieb gjr80:
>>
>> Thanks Kalli, I will put something together and email you.
>>
>> Gary
>>
>> On Wednesday, 28 October 2020 at 01:52:30 UTC+10 Kalli wrote:
>>
>>> Gir80 I have the weewx 3.8 weewx wd v1.3 
>>>
>>> tke...@gmail.com schrieb am Dienstag, 27. Oktober 2020 um 13:40:39 
>>> UTC+1:
>>>
 Never mind!

 On Tue, Oct 27, 2020 at 5:39 AM gjr80  wrote:

> Tom,
>
> I suspect that in this case FreshWDL is displaying sunshine hours as 
> measured by a sunshine recorder 
> . Some PWS software 
> approximates sunshine hours by calculating the cumulative time for a day 
> where the solar irradiance is above a given level. From memory the 
> measurement of sunshine hours has come up a couple of times here or in 
> weewx-development.
>
> Gary
> On Tuesday, 27 October 2020 at 22:25:34 UTC+10 tke...@gmail.com wrote:
>
>> The Seasons skin has something you can use. Look in the file 
>> celestial.inc. 
>>
>> If you just want amount of daylight, try something like (NOT TESTED):
>>
>> #set $sunrise_ts = $almanac.sun.rise.raw
>> #set $sunset_ts = $almanac.sun.set.raw
>> #if $sunrise_ts and $sunset_ts
>>
>> #set $today_daylight = $sunset_ts -  $sunrise_ts
>> #set $seconds = $today_daylight
>> #set $hours = $seconds //3600
>> #set $seconds %= 3600
>> #set $minutes = $seconds//60
>> #set $seconds %= 60
>> #set $daylight_str = "%d hours, %d minutes, %d seconds" % 
>> ($hours, $minutes, $seconds)
>>
>> Total daylight: $daylight_str
>>
>> #end if
>>
>> -tk
>>
>> On Mon, Oct 26, 2020 at 7:55 PM gjr80  wrote:
>>
>>> Hallo Kalli,
>>>
>>> The short answer is at the moment sunshine hours is not provided by 
>>> WeeWX or WeeWX-WD. Looking at the WeeWX-WD code it appears to be 
>>> something 
>>> I started working on but never fully implemented. Can you let me know 
>>> hat 
>>> version of WeeWX and WeeWX-WD you are running. It should be a simple 
>>> function to implement.
>>>
>>> Gary
>>>
>>> On Tuesday, 27 October 2020 at 03:16:23 UTC+10 Kalli wrote:
>>>

 Hello i have weewx-wd. in FreshWDL the sun is displayed. 
 unfortunately i can't find any settings for it at weewx. Can anybody 
 help 
 me further. 
>>>
>>> -- 
>>> 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/884f712b-74c8-4bd4-8655-74610e4f94dcn%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/3ad7fb34-745e-40bd-8e65-454da4c0c701n%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/a33866a0-bd20-4416-a016-137a3fbf12f5n%40googlegroups.com.

[weewx-user] Basic weather station (temp/humidity) with a large display

[Dan Bunyard]

I have what seems to be a dumb question but I keep coming up empty. I want 
a screen with a USB interface for WeeWX that simply needs indoor/outdoor 
temp and humidity. I don't need a full-blown weather station with all the 
bells and whistles, just temperature and humidity. Does anyone have a good 
suggestion? TIA!

-- 
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/b8cbccb8-00f1-4025-b670-f3e0943d54e9n%40googlegroups.com.

Re: [weewx-user] MQTT lagging

[vince]

On Sunday, November 1, 2020 at 11:09:53 AM UTC-8, T Reid wrote:
>
> I am running weewx and Belchertown on an older rpi 3 model B version 1.2.  
> Cheetah takes around 20 seconds to generate the Belchertown reports.  Time 
> for new hardware?
>
>
"*I'm good. My computer is too fast already*", said nobody ever...

I'm running on far wimpier hardware than even a model-B pi, and it takes 42 
seconds for me, but I do have my MQTT broker on a pi3 that has a wired.

Still think you should do a quick test with Belchertown disabled to see if 
that breaks looks your MQTT issue.  That would be a good data point to have.

-- 
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/89906c5c-68c6-4b55-9c93-69f330f8e7c2o%40googlegroups.com.

[weewx-user] Re: Belchertown 1.2 and Danish Charaters

[Arend]

I get the impression that most of the code that was responsible for 
handling 'useHTML' has been removed.
Contrary the comment in the belchertown.js.tmpl file, 'useHTML' is still 
present and functional in the latest Highcharts API.
Putting all the required code back in would be quite a job I guess. And 
those changes should be added to the master in the repo, otherwise you 
would face the same problems again with the next update.
I don't know why it has been removed, only Pat can answer that.


Op zondag 1 november 2020 om 21:42:40 UTC+1 schreef gert.a...@gmail.com:

> Hi Arend
>
> As far as I remember, the problem was not in version 1.1. Also the 
> previous problem was not in version 1.1. I still wonder, why the line was 
> commented.
>
> Gert
>
> On Sunday, November 1, 2020 at 3:56:27 PM UTC+1 Arend wrote:
>
>> Hi Gert,
>>
>> This issue showed up after upgrading from 1.1 to 1.2? And you had no 
>> problems in 1.1?
>>
>> Arend
>>
>> Op zaterdag 31 oktober 2020 om 07:00:13 UTC+1 schreef gert.a...@gmail.com
>> :
>>
>>> Hi Arend. All
>>>
>>> Do you also know where to fix this? It should say "Ø" Have looked in 
>>> belchertown.js.tmpl, but I don't think I can find anything here
>>>
>>> Gert
>>>
>>> On Wednesday, October 21, 2020 at 9:51:58 PM UTC+2 gert.a...@gmail.com 
>>> wrote:
>>>
 Hi Arend

 Thanks a lot, that solved the problem. I wonder how you found this, 
 good work.

 Rgds
 Gert

 On Wednesday, October 21, 2020 at 2:32:30 PM UTC+2 Arend wrote:

> Hi Gert,
>
> Getting those Danish characters back: try to find and uncomment this 
> line in belchertown.js.tmpl.
>
> //options.xAxis.labels = { useHTML: true } // Option 
> disabled in highcharts 8
>
> Kind regards, Arend 
>
> Op dinsdag 20 oktober 2020 om 06:15:18 UTC+2 schreef 
> gert.a...@gmail.com:
>
>> Hi
>>
>> I got my icons back. Did a new installation of Belchertown.
>>
>> But, I'm still missing the Danish characters in the Windrose.
>> http://gertandersen.de
>>
>> Rgds
>> Gert
>>
>> On Monday, October 19, 2020 at 2:40:02 PM UTC+2 gert.a...@gmail.com 
>> wrote:
>>
>>> Hi
>>>
>>> I'm running Ubuntu 20.04, Weewx 4.1.1, Phyton 3 and Belchertown 1.2. 
>>> I have upgraded from Belchertown 1.1 and I have some issues with the 
>>> Aeris 
>>> and the Windrose.
>>>
>>> With Aeris I'm missing the  current weather icon, but I have the 
>>> text. Screenshot attached.
>>>
>>> Using the Windrose I have some funny characters instead of the 
>>> Danish characters. See screenshot.
>>>
>>> My ordinals in weewx.conf is:
>>> directions = N, NNØ, NØ, ØNØ, Ø, ØSØ, SØ, SSØ, S, SSV, SV, VSV, V, 
>>> VNV, NV, NNV, N/A
>>>
>>> Correct display Belchertown 1.1(using Darksky):
>>> http://sjostauan.dk
>>>
>>> Missing icon and correct characters Belchertown 1.2(using Aeris):
>>> http://gertandersen.de
>>>
>>> I had a similar problem with the development to version 1.1:
>>> Link 
>>> 
>>> but Pat fixed it. I don't know if the issue is related to the bug in 
>>> the 1.1 development version.
>>>
>>> Any ideas where to look?
>>>
>>> Rgds
>>> Gert
>>>
>>>

-- 
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/a3528634-3c8d-441a-8cda-339538fb9dc5n%40googlegroups.com.

[weewx-user] Re: Belchertown 1.2 and Danish Charaters

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

Hi Arend

As far as I remember, the problem was not in version 1.1. Also the previous 
problem was not in version 1.1. I still wonder, why the line was commented.

Gert

On Sunday, November 1, 2020 at 3:56:27 PM UTC+1 Arend wrote:

> Hi Gert,
>
> This issue showed up after upgrading from 1.1 to 1.2? And you had no 
> problems in 1.1?
>
> Arend
>
> Op zaterdag 31 oktober 2020 om 07:00:13 UTC+1 schreef gert.a...@gmail.com:
>
>> Hi Arend. All
>>
>> Do you also know where to fix this? It should say "Ø" Have looked in 
>> belchertown.js.tmpl, but I don't think I can find anything here
>>
>> Gert
>>
>> On Wednesday, October 21, 2020 at 9:51:58 PM UTC+2 gert.a...@gmail.com 
>> wrote:
>>
>>> Hi Arend
>>>
>>> Thanks a lot, that solved the problem. I wonder how you found this, good 
>>> work.
>>>
>>> Rgds
>>> Gert
>>>
>>> On Wednesday, October 21, 2020 at 2:32:30 PM UTC+2 Arend wrote:
>>>
 Hi Gert,

 Getting those Danish characters back: try to find and uncomment this 
 line in belchertown.js.tmpl.

 //options.xAxis.labels = { useHTML: true } // Option 
 disabled in highcharts 8

 Kind regards, Arend 

 Op dinsdag 20 oktober 2020 om 06:15:18 UTC+2 schreef 
 gert.a...@gmail.com:

> Hi
>
> I got my icons back. Did a new installation of Belchertown.
>
> But, I'm still missing the Danish characters in the Windrose.
> http://gertandersen.de
>
> Rgds
> Gert
>
> On Monday, October 19, 2020 at 2:40:02 PM UTC+2 gert.a...@gmail.com 
> wrote:
>
>> Hi
>>
>> I'm running Ubuntu 20.04, Weewx 4.1.1, Phyton 3 and Belchertown 1.2. 
>> I have upgraded from Belchertown 1.1 and I have some issues with the 
>> Aeris 
>> and the Windrose.
>>
>> With Aeris I'm missing the  current weather icon, but I have the 
>> text. Screenshot attached.
>>
>> Using the Windrose I have some funny characters instead of the Danish 
>> characters. See screenshot.
>>
>> My ordinals in weewx.conf is:
>> directions = N, NNØ, NØ, ØNØ, Ø, ØSØ, SØ, SSØ, S, SSV, SV, VSV, V, 
>> VNV, NV, NNV, N/A
>>
>> Correct display Belchertown 1.1(using Darksky):
>> http://sjostauan.dk
>>
>> Missing icon and correct characters Belchertown 1.2(using Aeris):
>> http://gertandersen.de
>>
>> I had a similar problem with the development to version 1.1:
>> Link 
>> 
>> but Pat fixed it. I don't know if the issue is related to the bug in 
>> the 1.1 development version.
>>
>> Any ideas where to look?
>>
>> Rgds
>> Gert
>>
>>

-- 
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/cc882c6d-a9d3-4e21-9275-414be738d466n%40googlegroups.com.

Re: [weewx-user] MQTT lagging

[T Reid]

I am running weewx and Belchertown on an older rpi 3 model B version 1.2.  
Cheetah takes around 20 seconds to generate the Belchertown reports.  Time 
for new hardware?

On Sunday, November 1, 2020 at 10:32:27 AM UTC-8 vince wrote:

> On Sunday, November 1, 2020 at 9:52:51 AM UTC-8, T Reid wrote:
>>
>> >  My guess is that your weewx instance is CPU bound and really is 
>> running behind.  
>>
>> You may be on to something.  I watched top for a while.  CPU load on the 
>> python2 process runs under 10% when MQTT is posting loop records.  But 
>> every five minutes, when the archive records and web pages are being 
>> generated, the CPU load of the python2 process jumps up over 100%.  
>>
>
>
> I might have missed it, but what kind of box are you running on ?   An old 
> model-B pi with a slow SD card, a 4GB pi4 with a SSD, etc. ???
>
> My experience is that Belchertown is pretty heavyweight.  Look at the time 
> it takes the archive interval skins to run.   Disable all except the 
> standard or seasons skin and do a test to baseline your system.  Then flip 
> back to Belchertown and see if things bog down again.
>
>

-- 
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/02cc932b-838f-40c2-8a71-914bcef91fc6n%40googlegroups.com.

Re: [weewx-user] MQTT lagging

[vince]

On Sunday, November 1, 2020 at 9:52:51 AM UTC-8, T Reid wrote:
>
> >  My guess is that your weewx instance is CPU bound and really is running 
> behind.  
>
> You may be on to something.  I watched top for a while.  CPU load on the 
> python2 process runs under 10% when MQTT is posting loop records.  But 
> every five minutes, when the archive records and web pages are being 
> generated, the CPU load of the python2 process jumps up over 100%.  
>


I might have missed it, but what kind of box are you running on ?   An old 
model-B pi with a slow SD card, a 4GB pi4 with a SSD, etc. ???

My experience is that Belchertown is pretty heavyweight.  Look at the time 
it takes the archive interval skins to run.   Disable all except the 
standard or seasons skin and do a test to baseline your system.  Then flip 
back to Belchertown and see if things bog down again.

-- 
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/51919aeb-d358-403a-bfcc-ee865472d378o%40googlegroups.com.

Re: [weewx-user] MQTT lagging

[T Reid]

>  My guess is that your weewx instance is CPU bound and really is running 
behind.  

You may be on to something.  I watched top for a while.  CPU load on the 
python2 process runs under 10% when MQTT is posting loop records.  But 
every five minutes, when the archive records and web pages are being 
generated, the CPU load of the python2 process jumps up over 100%.  In 
/var/log/messages, the MQTT records are posting on time, but fall behind by 
10 seconds or more when the archive records and web pages are generated.  
The MQTT records then catch up again almost immediately after the archive 
activity dies down.  I may have to dig around in the log files a bit more 
to find lags that it did not recover from.

On Saturday, October 31, 2020 at 6:47:04 AM UTC-7 Greg Troxel wrote:

>
> T Reid  writes:
>
> > As I feared, the problem is not fixed. The lag between the posting of 
> MQTT 
> > records by weewx and the current time has wandered all over the place 
> over 
> > the past two days. It has gone from dead on time to 1.5 hours behind, 
> and 
> > everything in between. Last night it was doing okay, this morning it was 
> > 80 minutes behind, and now it is 20 minutes behind. There is no rhyme or 
> > reason to it. The only constant is that weewx can't seem to post MQTT 
> > records on time on a consistent basis.
>
> My guess is that your weewx instance is CPU bound and really is running
> behind.
>
> Is your archive interval 5 minutes, or something longer? If it's
> shorter than 5 minutes, then don't do that!
>
>
> I suggested restarting the broker because if the problem was in the
> network going to the broker, then the reconnect would start fresh. But
> you see old records newly appearing after the broker restart, which more
> or less proves that weewx is newly posting them after the restart.
>
> So look with ps, top, and so on about CPU usage. Check if your html
> skins are being generated on time, and transferred to your web server
> etc., or if those also are slow.
>
> Try to simplify your setup in terms of skins and generating things, and
> see if that helps. If it does, that supports the "not enough CPU time"
> theory.
>
> Back off from loop to archive in mqtt, and see if that is reliably
> timely. I'm not saying you should run that way, or have to, but it's an
> interesting data point.
>
> I am running weewx on a Raspberry Pi 3 (NetBSD 9) with a VP2, and every
> 5-minute archive interval:
>
> generate 2 skins
> rsync them
> post aggregate data to mqtt
>
> and I do not publish loop data. I just looked and the weewx python
> process has used 17 hours of CPU time in 16 days.
>
> > - I looked at the traffic with mosquitto_sub, and the incoming
> > weather data right now is from 45 minutes ago.
>
> It would be interesting to know if the inter-message arrival rate is the
> same as the intended transmit rate, or if it catches up some between
> archive intervals and then has a bigger lag over them.
>

-- 
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/63939b20-1f02-42bb-8aff-0b60048dda4en%40googlegroups.com.

Re: [weewx-user] Belchertown: Running a new index.htm.temp template

[weather list]

Is there then no way to include a PHP file which has POST arguments in it?

I guess this is the offending code:

Forecast for 
Casco Bay (ANZ153)\n";
$zone_image = "\n";
}

> On 31 Oct, 2020, at 23:04, Graham Eddy  wrote:
> 
> presumably invalid _POST reference is in include file. but: ‘main’ is invalid 
> html
> 
>> On 1 Nov 2020, at 1:44 pm, weather list > > wrote:
>> 
>> Quite right, might be:
>> 
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>> Generate failed with exception ''
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>>  Ignoring template /home/weewx/skins/Belchertown/forecast/index.html.tmpl
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>>  Reason: cannot find '_POST'
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>>   Traceback (most recent call last):
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>> File "/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in 
>> generate
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>>   unicode_string = compiled_template.respond()
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>> File "_home_weewx_skins_Belchertown_forecast_index_html_tmpl.py", 
>> line 103, in respond
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
>> 1707, in _handleCheetahInclude
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>>   self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>> File "_home_weewx_skins_forecast_noaacoastalforecastsmaine_php.py", 
>> line 131, in respond
>> Oct 31 22:35:31 raspberry-NUC62 weewx[17083] ERROR weewx.cheetahgenerator: 
>>   NameMapper.NotFound: cannot find '_POST'
>> 
>> 
>> Here is the index.html.tmpl page in question.
>> 
>> #errorCatcher Echo
>> #encoding UTF-8
>> #set global $page = "forecast"
>> 
>> #include "header.html.tmpl"
>> 
>> 
>>
>> #include "page-header.inc"
>> #include "/home/weewx/skins/forecast/noaacoastalforecastsmaine.php"
>> 
>> 
>> 
>> #include "footer.html.tmpl"
>> 
>> 
>>> On 31 Oct, 2020, at 21:30, Graham Eddy >> > wrote:
>>> 
>>> ‘no effect’ very unlikely. same outcome possible if more errors. post log 
>>> around template generation
>>> 
 On 1 Nov 2020, at 12:18 pm, weather list >>> > wrote:
 
 Fixed but it appears to have no effect so far.
 
> On 31 Oct, 2020, at 19:55, Graham Eddy  > wrote:
> 
> ‘Belchertown’ has too few brackets
> 
>> On 1 Nov 2020, at 10:50 am, weather list > > wrote:
>> 
>>[[[weewx_data]]]
>>template = json/weewx_data.json.tmpl
>> 
>>[[Belchertown]]
>>template = js/belchertown.js.tmpl
> 
> 
> -- 
> 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/B86E6B8F-CA9E-4E4E-9E71-15847E7074A0%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/0B7B2307-101E-4060-9FC1-17FB88C40A14%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/8F69F569-7E95-45EA-BFE0-317BCB6910FF%40gmail.com
>>>  
>>> 

[weewx-user] Re: Belchertown 1.2 and Danish Charaters

[Arend]

Hi Gert,

This issue showed up after upgrading from 1.1 to 1.2? And you had no 
problems in 1.1?

Arend

Op zaterdag 31 oktober 2020 om 07:00:13 UTC+1 schreef gert.a...@gmail.com:

> Hi Arend. All
>
> Do you also know where to fix this? It should say "Ø" Have looked in 
> belchertown.js.tmpl, but I don't think I can find anything here
>
> Gert
>
> On Wednesday, October 21, 2020 at 9:51:58 PM UTC+2 gert.a...@gmail.com 
> wrote:
>
>> Hi Arend
>>
>> Thanks a lot, that solved the problem. I wonder how you found this, good 
>> work.
>>
>> Rgds
>> Gert
>>
>> On Wednesday, October 21, 2020 at 2:32:30 PM UTC+2 Arend wrote:
>>
>>> Hi Gert,
>>>
>>> Getting those Danish characters back: try to find and uncomment this 
>>> line in belchertown.js.tmpl.
>>>
>>> //options.xAxis.labels = { useHTML: true } // Option 
>>> disabled in highcharts 8
>>>
>>> Kind regards, Arend 
>>>
>>> Op dinsdag 20 oktober 2020 om 06:15:18 UTC+2 schreef gert.a...@gmail.com
>>> :
>>>
 Hi

 I got my icons back. Did a new installation of Belchertown.

 But, I'm still missing the Danish characters in the Windrose.
 http://gertandersen.de

 Rgds
 Gert

 On Monday, October 19, 2020 at 2:40:02 PM UTC+2 gert.a...@gmail.com 
 wrote:

> Hi
>
> I'm running Ubuntu 20.04, Weewx 4.1.1, Phyton 3 and Belchertown 1.2. I 
> have upgraded from Belchertown 1.1 and I have some issues with the Aeris 
> and the Windrose.
>
> With Aeris I'm missing the  current weather icon, but I have the text. 
> Screenshot attached.
>
> Using the Windrose I have some funny characters instead of the Danish 
> characters. See screenshot.
>
> My ordinals in weewx.conf is:
> directions = N, NNØ, NØ, ØNØ, Ø, ØSØ, SØ, SSØ, S, SSV, SV, VSV, V, 
> VNV, NV, NNV, N/A
>
> Correct display Belchertown 1.1(using Darksky):
> http://sjostauan.dk
>
> Missing icon and correct characters Belchertown 1.2(using Aeris):
> http://gertandersen.de
>
> I had a similar problem with the development to version 1.1:
> Link 
> 
> but Pat fixed it. I don't know if the issue is related to the bug in 
> the 1.1 development version.
>
> Any ideas where to look?
>
> Rgds
> Gert
>
>

-- 
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/497201cb-44e6-4635-adb4-e36e7578920fn%40googlegroups.com.

[weewx-user] Can't get RTL-SDR running on Rpi3+ (868 Mhz EU)

[Co van der lee]

Hi, 

I’m struggeling a few weeks to get RTL-SDR running on my Rpi 3+ with a 
NooElec nano v2 https://www.nooelec.com/store/nesdr-nano2.html

I wanted to minimize the possible misconfigurations so i didn’t install 
Weewx, this should bet he next step but before that i want be sure RTL-SDR 
is functioning OK.

I installed Debian 10 (Buster), and installed thet pre-requisites form 
http://weewx.com/docs/setup.htm

 

After this is followed the folowing steps:

https://github.com/lheijst/rtldavis/blob/master/README.md

 

*The test after installation looks like this:.*

 

pi@wsb-meteo:~/work/src/github.com/lheijst/rtldavis $ $GOPATH/bin/rtldavis 
-ex 200

14:30:11.389438 rtldavis.go VERSION=0.15

14:30:11.390879 tr=1 fc=0 ppm=0 gain=0 maxmissed=51 ex=200 
receiveWindow=300 actChan=[0] maxChan=1

14:30:11.391160 undefined=false verbose=false disableAfc=false 
deviceString=0

14:30:11.392226 BitRate: 19200

14:30:11.392380 SymbolLength: 14

14:30:11.392476 SampleRate: 268800

14:30:11.392573 Preamble: 1100101110001001

14:30:11.392668 PreambleSymbols: 16

14:30:11.392763 PreambleLength: 224

14:30:11.392859 PacketSymbols: 80

14:30:11.392954 PacketLength: 1120

14:30:11.393048 BlockSize: 512

14:30:11.393143 BufferLength: 2048

Found Rafael Micro R820T tuner

14:30:11.843016 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0 
Transmitter:0}

Exact sample rate is: 268800.001367 Hz

14:30:12.018160 GetTunerGain: 0 Db

14:30:12.018311 SetFreqCorrection 0 ppm Successful

Allocating 1 zero-copy buffers

14:30:12.021978 Init channels: wait max 17 seconds for a message of each 
transmitter

14:30:29.961383 Init channels: wait max 17 seconds for a message of each 
transmitter

14:30:29.961516 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0 
Transmitter:0}

14:30:47.900464 Init channels: wait max 17 seconds for a message of each 
transmitter

14:30:47.900594 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0 
Transmitter:0}

14:31:05.839529 Init channels: wait max 17 seconds for a message of each 
transmitter

14:31:05.839662 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0 
Transmitter:0}

 

*After that i tested the following:*

 

pi@wsb-meteo:~/work/src/github.com/lheijst/rtldavis $ $GOPATH/bin/rtldavis 
-tr 1 -startfreq 868315000 -endfreq 86832100 -stepfreq 500

 

13:43:04.106356 rtldavis.go VERSION=0.15

13:43:04.107193 tr=1 fc=0 ppm=0 gain=0 maxmissed=51 ex=0 receiveWindow=300 
actChan=[0] maxChan=1

13:43:04.107295 undefined=false verbose=false disableAfc=false 
deviceString=0

13:43:04.107345 TEST: startFreq=868315000 endFreq=86832100 stepFreq=500

13:43:04.108215 BitRate: 19200

13:43:04.108286 SymbolLength: 14

13:43:04.108328 SampleRate: 268800

13:43:04.108367 Preamble: 1100101110001001

13:43:04.108406 PreambleSymbols: 16

13:43:04.108446 PreambleLength: 224

13:43:04.108484 PacketSymbols: 80

13:43:04.108526 PacketLength: 1120

13:43:04.108566 BlockSize: 512

13:43:04.108604 BufferLength: 2048

Found Rafael Micro R820T tuner

13:43:04.569158 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0 
Transmitter:0}

Exact sample rate is: 268800.001367 Hz

13:43:04.744014 GetTunerGain: 0 Db

13:43:04.744066 SetFreqCorrection 0 ppm Successful

Allocating 1 zero-copy buffers

13:43:04.748731 Init channels: wait max 17 seconds for a message of each 
transmitter

13:43:22.686845 Test reached endfreq; test ended

pi@wsb-meteo:~/work/src/github.com/lheijst/rtldavis $

 

*i searched internet and found this:*

https://www.wxforum.net/index.php?topic=36267.0

 

if i compare the result (see below which give results) to my version it 
looks like something went wrong??. Does anyone have some suggestions?

 

Thanks!

 

$GOPATH/bin/rtldavis -tr 1 -startfreq 868315000 -endfreq 868321000 
-stepfreq 500

12:31:03.070259 TESTFREQ 1: Frequency 868315000 (freqError=-523): OK, 
msg.data: 80330D003E89
12:31:15.883647 TESTFREQ 2: Frequency 868315500 (freqError=2514): OK, 
msg.data: E0080500DD6C
12:31:28.694940 TESTFREQ 3: Frequency 868316000 (freqError=2540): OK, 
msg.data: 5021650035BD
12:31:41.508008 TESTFREQ 4: Frequency 868316500 (freqError=1646): OK, 
msg.data: A07A3D008D28
12:31:54.320391 TESTFREQ 5: Frequency 868317000 (freqError=1261): OK, 
msg.data: 80330D003E89
12:32:09.696444 TESTFREQ 6: Frequency 868317500: NOK
12:32:19.944829 TESTFREQ 7: Frequency 868318000 (freqError=460): OK, 
msg.data: 50396500DF7F
12:32:32.758386 TESTFREQ 8: Frequency 868318500 (freqError=-110): OK, 
msg.data: A07B3D00BA18   <== pick this frequency for the p.channels 
list in protocol.go
12:32:45.569193 TESTFREQ 9: Frequency 868319000 (freqError=-1030): OK, 
msg.data: 80330D003E89
12:32:58.382205 TESTFREQ 10: Frequency 868319500 (freqError=-1063): OK, 
msg.data: E0090500EA5C
12:33:11.193817 TESTFREQ 11: Frequency 86832 (freqError=-1940): OK, 
msg.data: 50396500DF7F
12:33:24.007724 TESTFREQ 12: Frequency 868320500 (freqError=-2365): OK, 
msg.data: A07A3D008D28
12:33:36.818709 

Re: [weewx-user] Re: Sunshine Hours

[Kalli]

Hello Gir80
I'm curious what you're doing great again.

cu.Kalli



Am Dienstag, 27. Oktober 2020 22:39:17 UTC+1 schrieb gjr80:
>
> Thanks Kalli, I will put something together and email you.
>
> Gary
>
> On Wednesday, 28 October 2020 at 01:52:30 UTC+10 Kalli wrote:
>
>> Gir80 I have the weewx 3.8 weewx wd v1.3 
>>
>> tke...@gmail.com schrieb am Dienstag, 27. Oktober 2020 um 13:40:39 UTC+1:
>>
>>> Never mind!
>>>
>>> On Tue, Oct 27, 2020 at 5:39 AM gjr80  wrote:
>>>
 Tom,

 I suspect that in this case FreshWDL is displaying sunshine hours as 
 measured by a sunshine recorder 
 . Some PWS software 
 approximates sunshine hours by calculating the cumulative time for a day 
 where the solar irradiance is above a given level. From memory the 
 measurement of sunshine hours has come up a couple of times here or in 
 weewx-development.

 Gary
 On Tuesday, 27 October 2020 at 22:25:34 UTC+10 tke...@gmail.com wrote:

> The Seasons skin has something you can use. Look in the file 
> celestial.inc. 
>
> If you just want amount of daylight, try something like (NOT TESTED):
>
> #set $sunrise_ts = $almanac.sun.rise.raw
> #set $sunset_ts = $almanac.sun.set.raw
> #if $sunrise_ts and $sunset_ts
>
> #set $today_daylight = $sunset_ts -  $sunrise_ts
> #set $seconds = $today_daylight
> #set $hours = $seconds //3600
> #set $seconds %= 3600
> #set $minutes = $seconds//60
> #set $seconds %= 60
> #set $daylight_str = "%d hours, %d minutes, %d seconds" % ($hours, 
> $minutes, $seconds)
>
> Total daylight: $daylight_str
>
> #end if
>
> -tk
>
> On Mon, Oct 26, 2020 at 7:55 PM gjr80  wrote:
>
>> Hallo Kalli,
>>
>> The short answer is at the moment sunshine hours is not provided by 
>> WeeWX or WeeWX-WD. Looking at the WeeWX-WD code it appears to be 
>> something 
>> I started working on but never fully implemented. Can you let me know 
>> hat 
>> version of WeeWX and WeeWX-WD you are running. It should be a simple 
>> function to implement.
>>
>> Gary
>>
>> On Tuesday, 27 October 2020 at 03:16:23 UTC+10 Kalli wrote:
>>
>>>
>>> Hello i have weewx-wd. in FreshWDL the sun is displayed. 
>>> unfortunately i can't find any settings for it at weewx. Can anybody 
>>> help 
>>> me further. 
>>
>> -- 
>> 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/884f712b-74c8-4bd4-8655-74610e4f94dcn%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/3ad7fb34-745e-40bd-8e65-454da4c0c701n%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/c9df13d7-dbc9-4d87-9bff-789a3259e376o%40googlegroups.com.

Re: [weewx-user] Davis WeatherLink Live: Which driver is best?

[Didier Decoodt]

it's a fork of https://github.com/vinceskahan/weewx-weatherlinklive-json

Le dim. 1 nov. 2020 à 12:21, Karen K  a écrit :

> didier@gmail.com schrieb am Sonntag, 1. November 2020 um 11:36:36
> UTC+1:
>
>> I'm using this one :
>> https://github.com/Drealine/weatherlinklive-driver-weewx
>>
>
> Oh, I think, this one is not listed at https://github.com/weewx/weewx/wiki
>  .
>
> --
> 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/64cfc036-5576-46bf-8b31-9b4ce55da912n%40googlegroups.com
> 
> .
>


-- 
Quel temps fait-il à Auffargis  ?

-- 
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/CAAvt3%3DQW2j%3D9ndOyQnfwznPiR%2B52GPfhAaBTU%2B23ZRg%2B-bFU_Q%40mail.gmail.com.

Re: [weewx-user] Davis WeatherLink Live: Which driver is best?

[Karen K]

didier@gmail.com schrieb am Sonntag, 1. November 2020 um 11:36:36 UTC+1:

> I'm using this one : 
> https://github.com/Drealine/weatherlinklive-driver-weewx
>

Oh, I think, this one is not listed at https://github.com/weewx/weewx/wiki .

-- 
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/64cfc036-5576-46bf-8b31-9b4ce55da912n%40googlegroups.com.

Re: [weewx-user] Davis WeatherLink Live: Which driver is best?

[Didier Decoodt]

I'm using this one :
https://github.com/Drealine/weatherlinklive-driver-weewx

Le dim. 1 nov. 2020 à 11:22, Karen K  a écrit :

> Within the last days I did a some testing, and I read the threads
> regarding the Davis WeatherLink Live device for Davis Vantage Pro 2, and I
> wonder, which driver is best to use.
>
> Let me summarize, what I found out about the drivers.
>
> Just to avoid confusion:
>
>- "WeatherLink IP": a discontinued adaptor to insert into the Davis
>console
>- "WeatherLink Live": a separate device to receive data from a
>wireless Davis Vantage Pro 2 station
>
> Both of them use a different protocol to communicate with the PC.
>
> As I bought the station recently, I got the WeatherLink Live device. Then
> I looked for the appropriate driver, and I found a lot of them:
>
> *Vantage (weewx.drivers.vantage)*
>
> Although it is not mentioned in the documentation, I assume, that that
> driver is for the old, discontinued adaptors, only. I had a look at the
> code of the driver, and it seems so.
>
> Could someone confirm or deny?
>
> *WLL (users.wll)*
>
> I tried that driver, and it works. There were 2 little problems.
>
> First, I use a separate anemometer transmitter kit. Unfortunately, the
> driver reads the values from the transmitter kit and shows the wind, only.
> I changed the code a little bit, and now it reads the values from the
> station including the wind. I reported the changes to the author of the
> driver.
>
> Second, if you stop Weewx, the driver reports an exception to the logs,
> but does not finish. I have to kill the process by "kill -KILL".
>
> Nevertheless, this is the driver I still use.
>
> *WeatherLink Live* (recommended by Weewx)
>
> That driver seems attractive, because it announces to use both the
> broadcast messages and the HTTP requests.
>
> Remark for setup: Not as he documentation says, I had to set up the wind
> for ID 1 instead of 2 to get data.
>
> Unfortunately, in my case, every now and then the log shows an error
> message, and Weewx pauses for 60 seconds. The error message reads:
>
> Oct 31 18:39:27 LokalWiki weewx[147658] ERROR
> user.weatherlink_live.scheduler: Error caught in scheduler tick. Not
> rescheduling
> Oct 31 18:39:27 LokalWiki weewx[147658] INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Oct 31 18:39:27 LokalWiki weewx[147658] INFO weewx.engine: Shutting down
> StdReport thread
> Oct 31 18:39:27 LokalWiki weewx[147658] CRITICAL __main__: Caught
> WeeWxIOError: Error while receiving or processing packets:
> HTTPConnectionPool(host='192.168.XX.XX', port=80): Max retries exceeded
> with url: /v1/real_time?duration=1500 (Caused by
> NewConnectionError(' 0x7f6b45b15340>: Failed to establish a new connection: [Errno 111]
> Verbindungsaufbau abgelehnt'))
> Oct 31 18:39:27 LokalWiki weewx[147658] CRITICAL __main__:  Waiting 60
> seconds then retrying...
>
> As the driver uses 2 different data sources, the author may want to change
> the error handling and simply queries the device by HTTP request if the
> real time broadcast cannot be activated for some reason. I think that would
> make the driver more robust.
>
> (Remark: I don't think, the error message is really a problem of the
> driver but rather one of the network.)
>
> *WeatherLinkLiveJSON*
>
> I did not test this one.
>
> *Weatherlinkliveudp *(recommended by Weewx)
>
> I did not test this one, because I thought, "WeatherLink Live" will be
> more than that, as it uses both ways to communicate with the device.
>
> I can be wrong but I think I read somewhere the broadcast messages and the
> HTML request do not deliver the same set of information. Correct me, if I
> am wrong.
>
> And in one thread I read, someone decoded the V2 API of Davis, but that
> thread gave no further information, an I see no driver that implements that.
>
> What would you recommend a new user to use?
>
> --
> 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/2dbac754-84a7-43a4-a080-a99e228d7043n%40googlegroups.com
> 
> .
>


-- 
Quel temps fait-il à Auffargis  ?

-- 
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/CAAvt3%3DQ%3DWDHMfXkNuLzdkRsbWCq6i539tHRM8okN61xHwr9fMA%40mail.gmail.com.

[weewx-user] Davis WeatherLink Live: Which driver is best?

[Karen K]

Within the last days I did a some testing, and I read the threads regarding 
the Davis WeatherLink Live device for Davis Vantage Pro 2, and I wonder, 
which driver is best to use.

Let me summarize, what I found out about the drivers.

Just to avoid confusion:

   - "WeatherLink IP": a discontinued adaptor to insert into the Davis 
   console
   - "WeatherLink Live": a separate device to receive data from a wireless 
   Davis Vantage Pro 2 station
   
Both of them use a different protocol to communicate with the PC.

As I bought the station recently, I got the WeatherLink Live device. Then I 
looked for the appropriate driver, and I found a lot of them:

*Vantage (weewx.drivers.vantage)*

Although it is not mentioned in the documentation, I assume, that that 
driver is for the old, discontinued adaptors, only. I had a look at the 
code of the driver, and it seems so.

Could someone confirm or deny?

*WLL (users.wll)*

I tried that driver, and it works. There were 2 little problems.

First, I use a separate anemometer transmitter kit. Unfortunately, the 
driver reads the values from the transmitter kit and shows the wind, only. 
I changed the code a little bit, and now it reads the values from the 
station including the wind. I reported the changes to the author of the 
driver.

Second, if you stop Weewx, the driver reports an exception to the logs, but 
does not finish. I have to kill the process by "kill -KILL". 

Nevertheless, this is the driver I still use.

*WeatherLink Live* (recommended by Weewx)

That driver seems attractive, because it announces to use both the 
broadcast messages and the HTTP requests.

Remark for setup: Not as he documentation says, I had to set up the wind 
for ID 1 instead of 2 to get data.

Unfortunately, in my case, every now and then the log shows an error 
message, and Weewx pauses for 60 seconds. The error message reads:

Oct 31 18:39:27 LokalWiki weewx[147658] ERROR 
user.weatherlink_live.scheduler: Error caught in scheduler tick. Not 
rescheduling 
Oct 31 18:39:27 LokalWiki weewx[147658] INFO weewx.engine: Main loop 
exiting. Shutting engine down. 
Oct 31 18:39:27 LokalWiki weewx[147658] INFO weewx.engine: Shutting down 
StdReport thread 
Oct 31 18:39:27 LokalWiki weewx[147658] CRITICAL __main__: Caught 
WeeWxIOError: Error while receiving or processing packets: 
HTTPConnectionPool(host='192.168.XX.XX', port=80): Max retries exceeded 
with url: /v1/real_time?duration=1500 (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Verbindungsaufbau abgelehnt')) 
Oct 31 18:39:27 LokalWiki weewx[147658] CRITICAL __main__:  Waiting 60 
seconds then retrying... 

As the driver uses 2 different data sources, the author may want to change 
the error handling and simply queries the device by HTTP request if the 
real time broadcast cannot be activated for some reason. I think that would 
make the driver more robust. 

(Remark: I don't think, the error message is really a problem of the driver 
but rather one of the network.)

*WeatherLinkLiveJSON*

I did not test this one.

*Weatherlinkliveudp *(recommended by Weewx)

I did not test this one, because I thought, "WeatherLink Live" will be more 
than that, as it uses both ways to communicate with the device.

I can be wrong but I think I read somewhere the broadcast messages and the 
HTML request do not deliver the same set of information. Correct me, if I 
am wrong.

And in one thread I read, someone decoded the V2 API of Davis, but that 
thread gave no further information, an I see no driver that implements that.

What would you recommend a new user to use?

-- 
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/2dbac754-84a7-43a4-a080-a99e228d7043n%40googlegroups.com.

Re: [weewx-user] Weewx upgrade from 2.0.2 -> 4.2.0

[Fraser Stuart]

upgrade successful
http://weather.yarrawonga.org/

only real issue I noticed was discrepancies in the summary records due to 
the news ones being based on the 5 minute archive records whereas the 
originals used the 5 minute readings and LOOP data. Not a huge concern and 
correctable if I could be bothered updating the daily summaries from the 
old DB.

now for the fun stuff - getting the website customised :)

On Saturday, 31 October 2020 at 00:31:17 UTC+11 Fraser Stuart wrote:

> 1. no the only customisations I have done are to the generated web pages, 
> a report and one of the graphs. happy to recreate them so not stressed at 
> all about them. 
>
> 2. thanks thats good advice - and being able to A|B the two versions will 
> help a lot. 
>
> cheers,
> F
>
>
>
> On Friday, 30 October 2020 at 23:08:28 UTC+11 tke...@gmail.com wrote:
>
>> Two things to think about:
>>
>> 1. Do you have any custom WeeWX services, or search list extensions? 
>> Their APIs have changed since V2.0.
>>
>> 2. There have been some changes in the structure of weewx.conf. I've 
>> never tested the upgrade process on such a large jump, so I'm not sure it 
>> will correctly upgrade weewx.conf. I would suggest installing WeeWX on your 
>> new machine first. It will install a fresh copy of weewx.conf. Edit it. 
>> Temporarily move your console over and test it. When you're satisfied it 
>> will run without problems, then do your migration.
>>
>> -tk
>>
>>
>>
>> On Thu, Oct 29, 2020 at 11:14 PM Fraser Stuart  
>> wrote:
>>
>>> I have had weewx running since 2013 and its time to upgrade the 
>>> hardware. 
>>>
>>> I've got a PC Engines APU2 unit ready to go and its time to migrate 
>>> nearly 8 years of data over. I've got a few questions and was wondering if 
>>> anyone can set me straight
>>>
>>> 1) I'm using the Vantage Vue so as it caches 2 weeks work of data I 
>>> assume I can switch the Davis console between hosts and each will catch up 
>>> from where it last read? ie so I can fall back into the old host, and it'll 
>>> sort itself out.
>>>
>>> 2) Database changes. I'm running a mysql backend. 
>>> I can see from http://weewx.com/docs/upgrading.htm that there is just a 
>>> single database now. 
>>>
>>> also I note: *On startup, WeeWX will automatically backfill the new 
>>> internal daily summaries from the archive data *
>>>
>>> I cant see much about the data schema - Am i correct in assuming 
>>> *wee_database 
>>> --transfer* will take of any schema changes for me?
>>>
>>>
>>> 3) overall process is like this then:
>>>
>>>- Stop weewx on the old host and disconnect console
>>>- Migrate the data [wee_database --transfer]
>>>- attach console to new host & start weewx. 
>>>- watch it populate 8 years of daily summaries?
>>>
>>>
>>>
>>> any other gotchas I should be aware of for such a large jump in versions?
>>>
>>> -- 
>>> 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/fa5438d9-6249-429d-bd7c-9367681ddf32n%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/d6be7f7b-9859-41eb-b805-63713b338203n%40googlegroups.com.

[weewx-user] Re: Version 4.2.0 ready

[Greg from Oz]

My weewx.conf was changed as well. It had been changed back to Santa Clause 
and the location was changed but the rest of the file still had my original 
changes in it.
I have mentioned that earlier in these posts. Good to know I am not the 
only one that this happened to.
I upgraded from the beta version to the latest stable version and used the 
dpkg -i method.

On Sunday, 1 November 2020 11:39:10 UTC+11, Alessandro Del Prete wrote:
>
> From the log of my upgrade below, you can clearly see that it says " *merging 
> previous and distribution into /etc/weewx/weewx.conf*".
> If I answer NO to replace my weewx.conf I expect the previous version's 
> weewx.conf to be used, *untouched*. Instead, I found the station_type 
> changed to simulator, all the rest was exactly the same.
>
> Configuration file '/etc/weewx/weewx.conf'
>  ==> Modified (by you or by a script) since installation.
>  ==> Package distributor has shipped an updated version.
>What would you like to do about it ?  Your options are:
> Y or I  : install the package maintainer's version
> N or O  : keep your currently-installed version
>   D : show the differences between the versions
>   Z : start a shell to examine the situation
>  The default action is to keep your current version.
> *** weewx.conf (Y/I/N/O/D/Z) [default=N] ? N
> Installing new version of config file /etc/weewx/weewx.conf.dist ...
> saving previous config file as /etc/weewx/weewx.conf-4.1.1
> saving distribution config file as /etc/weewx/weewx.conf-4.2.0
> *merging previous and distribution into /etc/weewx/weewx.conf*
> Using configuration file /etc/weewx/weewx.conf-4.1.1
>
> On Sunday, November 1, 2020 at 1:28:54 AM UTC+1 Cameron D wrote:
>
>> There may be a bit of confusion in this thread about "merging".  My 
>> understanding and experience is that  with .DEB upgrades  there is no 
>> automatic merging of config file changes.
>> You run either with your old config or the new one.
>>
>> Every upgrade I do a manual check for changes and merge anything myself.
>> One case is weewx.conf, which contains a version number, with the comment 
>> "*do not modify this*".
>> So I modify it - such that my old config file matches the new version 
>> number.
>>
>> Cameron.
>>
>> On Saturday, 31 October 2020 at 11:49:44 am UTC+10 alessandr...@gmail.com 
>> wrote:
>>
>>> Hi Tom,
>>>
>>> I use ubuntu on an Intel NUC, with systemd, weewx 4.1 was installed as 
>>> package.
>>> I followed the upgrade guide, here was the result:
>>>
>>> The following packages will be upgraded:
>>>   weewx
>>> 1 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
>>> Need to get 1.207 kB of archives.
>>> After this operation, 47,1 kB of additional disk space will be used.
>>> Get:1 http://weewx.com/apt/python3 buster/main all weewx all 4.2.0-1 
>>> [1.207 kB]
>>> Fetched 1.207 kB in 6s (195 kB/s)
>>> Requesting to save current system state
>>> Successfully saved as "autozsys_sgety6"
>>> Preconfiguring packages ...
>>> (Reading database ... 245196 files and directories currently installed.)
>>> Preparing to unpack .../archives/weewx_4.2.0-1_all.deb ...
>>> Unpacking weewx (4.2.0-1) over (4.1.1-1) ...
>>> Setting up weewx (4.2.0-1) ...
>>> Installing new version of config file 
>>> /etc/weewx/skins/Seasons/current.inc ...
>>> Installing new version of config file 
>>> /etc/weewx/skins/Seasons/rss.xml.tmpl ...
>>> Installing new version of config file 
>>> /etc/weewx/skins/Seasons/seasons.js ...
>>> Installing new version of config file 
>>> /etc/weewx/skins/Standard/index.html.tmpl ...
>>>
>>> Configuration file '/etc/weewx/weewx.conf'
>>>  ==> Modified (by you or by a script) since installation.
>>>  ==> Package distributor has shipped an updated version.
>>>What would you like to do about it ?  Your options are:
>>> Y or I  : install the package maintainer's version
>>> N or O  : keep your currently-installed version
>>>   D : show the differences between the versions
>>>   Z : start a shell to examine the situation
>>>  The default action is to keep your current version.
>>>  weewx.conf (Y/I/N/O/D/Z) [default=N] ? N*
>>> Installing new version of config file /etc/weewx/weewx.conf.dist ...
>>> saving previous config file as /etc/weewx/weewx.conf-4.1.1
>>> saving distribution config file as /etc/weewx/weewx.conf-4.2.0
>>> merging previous and distribution into /etc/weewx/weewx.conf
>>> Using configuration file /etc/weewx/weewx.conf-4.1.1
>>> *update-rc.d: error: unable to read /etc/init.d/weewx*
>>> *dpkg: error processing package weewx (--configure):*
>>> * installed weewx package post-installation script subprocess returned 
>>> error exit status 1*
>>> Processing triggers for systemd (245.4-4ubuntu3.2) ...
>>> Errors were encountered while processing:
>>>  weewx
>>> ZSys is adding automatic system snapshot to GRUB menu
>>> *E: Sub-process /usr/bin/dpkg returned an error code (1)*
>>>
>>> No big issue regarding the missing /etc/init.d/weewx I