[weewx-user] Re: Vantage Pro 2 : Weewx stops reading the data

[PC]

Well, looking in the group, I found the command to erase the vantage memory:
wee_device --clear-memory

Since then, error messages we disappeared, calm flat

Le lundi 14 février 2022 à 15:23:59 UTC+1, matthew wall a écrit :

> On Monday, February 14, 2022 at 8:35:30 AM UTC-5 blaise@gmail.com 
> wrote:
>
>> When I look at the log, it's horror. Where can this come from. Is this 
>> the cause?
>>
> ...
>>
> Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
>>  File "_etc_weewx_skins_Seasons_titlebar_inc.py", line 344, in respond
>> Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
>>  TypeError: float() argument must be a string or a number, not 'NoneType'
>>
>
> in your Seasons skin, something in titlebar.inc file is expecting a float, 
> but it is getting a None.
>
> hard to say much more than that without knowing which version of weewx you 
> are running, which version of Seasons skin you are running, what 
> modifications (if any) you have made to either, and how your system got 
> into the state that it is in (i.e., how did you install, and what changes 
> did you make that started this behavior).
>
> 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/5b6f1bd1-4f1c-428b-af9f-7eab59a4a79fn%40googlegroups.com.

Re: [weewx-user] Re: WeeWX V4.6.1 released

[vince]

So where are the extra leaf1+2 and soil1+2+3+4 (apologies for my earlier 
typos) sensors coming from ?

Are there references to any of them in your skin.conf or weewx.conf files ?

-- 
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/796d571b-3fee-4f1f-bec8-17247cd1dc81n%40googlegroups.com.

Re: [weewx-user] Re: WeeWX V4.6.1 released

[Rob Cranfill]

Well that 'splains it! :-) I'll set about removing those (and cleaning up 
the DB, right? As detailed elsewhere in this thread?)

As requested, 

pi@pi3b:/etc/weewx $ wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.2.3 (weewx.drivers.vantage)
Unable to wake up console... sleeping
Unable to wake up console... retrying
Querying...
Davis Vantage EEPROM settings:

CONSOLE TYPE:   Vantage Vue

CONSOLE FIRMWARE:
  Date: Feb  3 2015
  Version:  4.18

CONSOLE SETTINGS:
  Archive interval: 60 (seconds)
  Altitude: 150 (foot)
  Wind cup type:large
  Rain bucket type: 0.01 inches
  Rain year start:  1
  Onboard time: 2022-02-14 17:34:27

CONSOLE DISPLAY UNITS:
  Barometer:mbar
  Temperature:  degree_F
  Rain: inch
  Wind: mile_per_hour

CONSOLE STATION INFO:
  Latitude (onboard):   +47.6
  Longitude (onboard):  -122.3
  Use manual or auto DST?   AUTO
  DST setting:  N/A
  Use GMT offset or zone code?  ZONE_CODE
  Time zone code:   4
  GMT offset:   N/A
  Temperature logging:  LAST
  Retransmit channel:   OFF (0)

TRANSMITTERS:
  Channel   Receive   Repeater  Type
 1  active  noneiss
 2  active  none(N/A)
 3  active  none(N/A)
 4  active  none(N/A)
 5  active  none(N/A)
 6  active  none(N/A)
 7  active  none(N/A)
 8  active  none(N/A)

RECEPTION STATS:
  Total packets received:   24546
  Total packets missed: 143
  Number of resynchronizations: 0
  Longest good stretch: 677
  Number of CRC errors: 16

BAROMETER CALIBRATION DATA:
  Current barometer reading:29.980 inHg
  Altitude: 150 feet
  Dew point:42 F
  Virtual temperature:  48 F
  Humidity correction factor:   1.8
  Correction ratio: 1.006
  Correction constant:  +0.000 inHg
  Gain: 0.000
  Offset:   -33.000

OFFSETS:
  Wind direction:   +0 deg
  Inside Temperature:   +0.0 F
  Inside Humidity:  +0 %
  Outside Temperature:  +0.0 F
  Outside Humidity: +0 %

On Monday, February 14, 2022 at 3:28:09 PM UTC-8 tke...@gmail.com wrote:

> Rob,
>
> Before this version, weewx only reported on explicit tags. For example, if 
> you didn't put $current.soilTemp1 in the template, you were not going to 
> see it in the report.
>
> Now it basically reports on everything that's in the database. 
>
> To stop it, look in the skin.conf file for the Seasons skin. Near the top, 
> you will see a stanza labelled [DisplayOptions]. In this stanza are lists 
> of the various types. Just remove any type for which you do not want to be 
> included in the report.
>
> As for where these values are coming from, I have no idea. Either they are 
> being emitted by your Vantage Vue, or they are being introduced by one of 
> your extensions. It's also possible you are picking up sensors from a 
> neighbor. 
>
> In fact, now that I think about it, it would be worth seeing which sensors 
> your Vantage is aware of. Try running
>
> *wee_device --info*
>
>
> -tk
>
> On Mon, Feb 14, 2022 at 3:15 PM Rob Cranfill  wrote:
>
>> First, I guess I'm just confused as to why I'm getting all this good 
>> stuff when my previous (<4.6) installation was happy for so long.
>>
>> I just did a quick 'grep' looking around, and I do see that the standard 
>> Seasons skin *defines* a bunch of these unwanted values. Is that enough to 
>> cause them to be reported?
>>
>> On Monday, February 14, 2022 at 11:27:03 AM UTC-8 vince wrote:
>>
>>> You have to have something mapped to a lot of leaf and soil sensors.   
>>> We'd need to see all your skin.conf files and your weewx.conf file to know 
>>> for sure where they're coming from. If you can't find it, I'd suggest you 
>>> use StdQC to just filter out the extraneous things (link to User's 
>>> Guide) .
>>>
>>> All your bogus temperatures seem to read crazy low numbers.   Set the 
>>> min/max to a range you'll never see and weewx should ignore them even if 
>>> you can't find a way to turn them off.  Perhaps something like the 
>>> following (untested):
>>>
>>> [StdQC]
>>>[[MinMax]]
>>> leafTemp1 = 200, 201, deg_F
>>> leafTemp2 = 200, 201, deg_F
>>> soilTemp1 = 200, 201, deg_F
>>> soilTemp2 = 200, 

Re: [weewx-user] Re: WeeWX V4.6.1 released

[Tom Keffer]

Rob,

Before this version, weewx only reported on explicit tags. For example, if
you didn't put $current.soilTemp1 in the template, you were not going to
see it in the report.

Now it basically reports on everything that's in the database.

To stop it, look in the skin.conf file for the Seasons skin. Near the top,
you will see a stanza labelled [DisplayOptions]. In this stanza are lists
of the various types. Just remove any type for which you do not want to be
included in the report.

As for where these values are coming from, I have no idea. Either they are
being emitted by your Vantage Vue, or they are being introduced by one of
your extensions. It's also possible you are picking up sensors from a
neighbor.

In fact, now that I think about it, it would be worth seeing which sensors
your Vantage is aware of. Try running

*wee_device --info*


-tk

On Mon, Feb 14, 2022 at 3:15 PM Rob Cranfill  wrote:

> First, I guess I'm just confused as to why I'm getting all this good stuff
> when my previous (<4.6) installation was happy for so long.
>
> I just did a quick 'grep' looking around, and I do see that the standard
> Seasons skin *defines* a bunch of these unwanted values. Is that enough to
> cause them to be reported?
>
> On Monday, February 14, 2022 at 11:27:03 AM UTC-8 vince wrote:
>
>> You have to have something mapped to a lot of leaf and soil sensors.
>> We'd need to see all your skin.conf files and your weewx.conf file to know
>> for sure where they're coming from. If you can't find it, I'd suggest you
>> use StdQC to just filter out the extraneous things (link to User's Guide)
>> .
>>
>> All your bogus temperatures seem to read crazy low numbers.   Set the
>> min/max to a range you'll never see and weewx should ignore them even if
>> you can't find a way to turn them off.  Perhaps something like the
>> following (untested):
>>
>> [StdQC]
>>[[MinMax]]
>> leafTemp1 = 200, 201, deg_F
>> leafTemp2 = 200, 201, deg_F
>> soilTemp1 = 200, 201, deg_F
>> soilTemp2 = 200, 201, deg_F
>> soilTemp2 = 200, 201, deg_F
>> soilTemp2 = 200, 201, deg_F
>>
>>
>>
>> --
> 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/46b0c5ae-a3ed-40df-947c-cb4a0a46471fn%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/CAPq0zEAnQO%3Db%2BcxriNKPaeCCxHJx58wAi4P4GJnoRekRMwkmEQ%40mail.gmail.com.

Re: [weewx-user] Re: WeeWX V4.6.1 released

[Rob Cranfill]

First, I guess I'm just confused as to why I'm getting all this good stuff 
when my previous (<4.6) installation was happy for so long.

I just did a quick 'grep' looking around, and I do see that the standard 
Seasons skin *defines* a bunch of these unwanted values. Is that enough to 
cause them to be reported?

On Monday, February 14, 2022 at 11:27:03 AM UTC-8 vince wrote:

> You have to have something mapped to a lot of leaf and soil sensors.   
> We'd need to see all your skin.conf files and your weewx.conf file to know 
> for sure where they're coming from. If you can't find it, I'd suggest you 
> use StdQC to just filter out the extraneous things (link to User's Guide) 
> .
>
> All your bogus temperatures seem to read crazy low numbers.   Set the 
> min/max to a range you'll never see and weewx should ignore them even if 
> you can't find a way to turn them off.  Perhaps something like the 
> following (untested):
>
> [StdQC]
>[[MinMax]]
> leafTemp1 = 200, 201, deg_F
> leafTemp2 = 200, 201, deg_F
> soilTemp1 = 200, 201, deg_F
> soilTemp2 = 200, 201, deg_F
> soilTemp2 = 200, 201, deg_F
> soilTemp2 = 200, 201, deg_F
>
>
>
>

-- 
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/46b0c5ae-a3ed-40df-947c-cb4a0a46471fn%40googlegroups.com.

Re: [weewx-user] Re: Upgrade Raspberry Pi 2 to Raspberry Pi 4

[p q]

Unless you're dealing with a hardware failure of your old Raspi, I'd set up
the new one from scratch as suggested, but I'd do it before taking down the
old one.

On Mon, Feb 14, 2022 at 2:01 PM vince  wrote:

> Experimentation will tell you.
> The worst that happens is it doesn't work.
>
> But personally I'd upgrade to the current os and take this as an
> opportunity to start cleanly and document how you (re)installed everything.
>
> On Monday, February 14, 2022 at 1:34:31 PM UTC-8 bchap...@gmail.com wrote:
>
>> Can I just swap out the card?
>
> --
> 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/2d9eaf54-81e8-4758-96c1-9a7987382740n%40googlegroups.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM23oF%2B5R%2B2AXKf7sz%2BwCcv%3DU6i524Oskea6WaTub2N12Ag%40mail.gmail.com.

Re: [weewx-user] Upgrade Raspberry Pi 2 to Raspberry Pi 4

[Bruce Chapman]

> On Feb 14, 2022, at 16:53, Doug Jenkins  wrote:
> 
> Well that depends:
> 
> 1. What version of Raspbian is the RPi2 using?

Buster 10.11

> 2. Do you have any device-specific items on i2c or via GPIO?

No

> 
> If it is a RPI4 and the RAM is over 4GB (eg 8gb version), then you should 
> consider setting up the new Raspberry Pi OS 64bit release. 

2GB Ram

I was hoping for just a swap out but if there is an advantage to a fresh 
install, that’s what I’ll do

Thanks for your advise.


> 
> Another consideration is to update the micro-sd card to another newer card or 
> use a USB drive. The new RPI4s (newer than Sept 2020) support boot from USB 
> Device.
> 
> Just my $0.02
> 
> DDJ
> 
> On Monday, February 14, 2022 at 4:34:31 PM UTC-5 bchap...@gmail.com wrote:
> Can I just swap out the card?
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/wPrwvf0iZe4/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/14ce56e6-7597-46e6-867d-85873ad36d3dn%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/5B56D53A-5B7D-46F1-94D5-F750FFFBC067%40gmail.com.

[weewx-user] Re: Upgrade Raspberry Pi 2 to Raspberry Pi 4

[vince]

Experimentation will tell you.
The worst that happens is it doesn't work.

But personally I'd upgrade to the current os and take this as an 
opportunity to start cleanly and document how you (re)installed everything.

On Monday, February 14, 2022 at 1:34:31 PM UTC-8 bchap...@gmail.com wrote:

> Can I just swap out the card?

-- 
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/2d9eaf54-81e8-4758-96c1-9a7987382740n%40googlegroups.com.

[weewx-user] Re: Upgrade Raspberry Pi 2 to Raspberry Pi 4

[Doug Jenkins]

Well that depends:

1. What version of Raspbian is the RPi2 using?
2. Do you have any device-specific items on i2c or via GPIO?

If it is a RPI4 and the RAM is over 4GB (eg 8gb version), then you should 
consider setting up the new Raspberry Pi OS 64bit release. 

Another consideration is to update the micro-sd card to another newer card 
or use a USB drive. The new RPI4s (newer than Sept 2020) support boot from 
USB Device.

Just my $0.02

DDJ

On Monday, February 14, 2022 at 4:34:31 PM UTC-5 bchap...@gmail.com wrote:

> Can I just swap out the card?

-- 
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/14ce56e6-7597-46e6-867d-85873ad36d3dn%40googlegroups.com.

[weewx-user] Upgrade Raspberry Pi 2 to Raspberry Pi 4

[bchap...@gmail.com]

Can I just swap out the card?

-- 
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/c7b165f1-3dcc-4cce-9579-c7745603fd5dn%40googlegroups.com.

[weewx-user] Re: Problem with units

[gjr80]

I see now there have been some changes have been introduced in WeeWX v4.6.x 
to how default labelling and formatting of observation types is determined 
and it appears that group_energy/watt_hour may have fallen through the 
cracks. I think we can work around the issue in your case by adding some 
additional lines to user/extensions.py:

weewx.units.default_unit_format_dict['watt_hour'] = '%.1f'
weewx.units.default_unit_label_dict['watt_hour'] = u' Wh' 

Again you will need to restart WeeWX for the changes to take effect and 
hopefully the first report cycle should add you missing units/formatting.

Gary

On Tuesday, 15 February 2022 at 04:18:53 UTC+10 udo.kl...@gmail.com wrote:

> Hi Gary, unfortunately your tip did not work. "signal1" still has no unit. 
> Before the update it still did. 
>
> gjr80 schrieb am Montag, 14. Februar 2022 um 01:58:29 UTC+1:
>
>> Making changes to units.py  is a poor approach to dealing with problems 
>> and should be avoided, at best your changes will not survive a WeeWX 
>> upgrade; at worst your changes could unknowingly cause problems elsewhere 
>> with WeeWX.
>>
>> If you wish to assign an observation type to a unit group this is best 
>> done through the user/extensions.py file. user/extensions.py is intended 
>> for users to add code that is to be run during the WeeWX startup and allows 
>> user changes to the WeeWX environment to be made in a safe manner. Files in 
>> the user directory are protected during a WeeWX upgrade and will not be 
>> overwritten. I suggest you revert your changes to units.py and try 
>> adding the following to user/extensions.py (untested):
>>
>> import weewx.units
>> weewx.units.obs_group_dict['signal1'] = 'group_energy'
>>
>> Save extensions.py and restart WeeWX. Does that fix your problem?
>>
>> Gary
>> On Monday, 14 February 2022 at 01:14:14 UTC+10 udo.kl...@gmail.com wrote:
>>
>>> Hello all,
>>>
>>> I have updated this weekend to WeeWX version 4.6.2. Actually everything 
>>> works as usual, but in my photovoltaic data no units are displayed anymore. 
>>> I have changed the assignment in the units.py as follows "signal1" : 
>>> "group_energy", but without success.
>>>
>>> Who knows advice?
>>>
>>

-- 
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/dcb7360c-543c-4ace-98d5-2a68c3f316den%40googlegroups.com.

Re: [weewx-user] Re: WeeWX V4.6.1 released

[vince]

(oops - degree_F there)

On Monday, February 14, 2022 at 11:27:03 AM UTC-8 vince wrote:

> You have to have something mapped to a lot of leaf and soil sensors.   
> We'd need to see all your skin.conf files and your weewx.conf file to know 
> for sure where they're coming from. If you can't find it, I'd suggest you 
> use StdQC to just filter out the extraneous things (link to User's Guide) 
> .
>
> All your bogus temperatures seem to read crazy low numbers.   Set the 
> min/max to a range you'll never see and weewx should ignore them even if 
> you can't find a way to turn them off.  Perhaps something like the 
> following (untested):
>
> [StdQC]
>[[MinMax]]
> leafTemp1 = 200, 201, deg_F
> leafTemp2 = 200, 201, deg_F
> soilTemp1 = 200, 201, deg_F
> soilTemp2 = 200, 201, deg_F
> soilTemp2 = 200, 201, deg_F
> soilTemp2 = 200, 201, deg_F
>
>
>
>

-- 
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/d8a5f7ae-31e2-4c67-be63-e64967e735f1n%40googlegroups.com.

Re: [weewx-user] Re: WeeWX V4.6.1 released

[vince]

You have to have something mapped to a lot of leaf and soil sensors.   We'd 
need to see all your skin.conf files and your weewx.conf file to know for 
sure where they're coming from. If you can't find it, I'd suggest you use 
StdQC to just filter out the extraneous things (link to User's Guide) 
.

All your bogus temperatures seem to read crazy low numbers.   Set the 
min/max to a range you'll never see and weewx should ignore them even if 
you can't find a way to turn them off.  Perhaps something like the 
following (untested):

[StdQC]
   [[MinMax]]
leafTemp1 = 200, 201, deg_F
leafTemp2 = 200, 201, deg_F
soilTemp1 = 200, 201, deg_F
soilTemp2 = 200, 201, deg_F
soilTemp2 = 200, 201, deg_F
soilTemp2 = 200, 201, deg_F



-- 
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/9e973806-560e-4e3a-bea5-be9f07031921n%40googlegroups.com.

[weewx-user] Re: Problem with units

[kludo]

Hi Gary, unfortunately your tip did not work. "signal1" still has no unit. 
Before the update it still did. 

gjr80 schrieb am Montag, 14. Februar 2022 um 01:58:29 UTC+1:

> Making changes to units.py  is a poor approach to dealing with problems 
> and should be avoided, at best your changes will not survive a WeeWX 
> upgrade; at worst your changes could unknowingly cause problems elsewhere 
> with WeeWX.
>
> If you wish to assign an observation type to a unit group this is best 
> done through the user/extensions.py file. user/extensions.py is intended 
> for users to add code that is to be run during the WeeWX startup and allows 
> user changes to the WeeWX environment to be made in a safe manner. Files in 
> the user directory are protected during a WeeWX upgrade and will not be 
> overwritten. I suggest you revert your changes to units.py and try adding 
> the following to user/extensions.py (untested):
>
> import weewx.units
> weewx.units.obs_group_dict['signal1'] = 'group_energy'
>
> Save extensions.py and restart WeeWX. Does that fix your problem?
>
> Gary
> On Monday, 14 February 2022 at 01:14:14 UTC+10 udo.kl...@gmail.com wrote:
>
>> Hello all,
>>
>> I have updated this weekend to WeeWX version 4.6.2. Actually everything 
>> works as usual, but in my photovoltaic data no units are displayed anymore. 
>> I have changed the assignment in the units.py as follows "signal1" : 
>> "group_energy", but without success.
>>
>> Who knows advice?
>>
>

-- 
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/124154c5-6111-4f77-b1e5-136f572e1c94n%40googlegroups.com.

Re: [weewx-user] Re: WeeWX V4.6.1 released

[Rob Cranfill]

Here is my user dir:

pi@pi3b:~ $ ls -l /usr/share/weewx/user/
total 232K
-rw-rw-r-- 1 root root 140K Jul  1  2021 belchertown.py
-rw-r--r-- 1 root root  31K May  9  2020 cmon.orig
-rw-r--r-- 1 root root  32K May  9  2020 cmon.py
-rw-r--r-- 1 root root  541 Jul 14  2019 extensions.py
-rw-r--r-- 1 root root  306 Feb 10 19:15 __init__.py
drwxr-xr-x 4 root root 4.0K Oct 26  2020 installer
-rw-r--r-- 1 root root 8.8K Jun  9  2021 lowBattery.py
drwxr-xr-x 2 root root 4.0K Feb 11 17:17 __pycache__

Attached is a short output from running directly.

Thanks!

On Sunday, February 13, 2022 at 9:12:31 PM UTC-8 matthew wall wrote:

> On Saturday, February 12, 2022 at 3:47:09 PM UTC-5 robcr...@gmail.com 
> wrote:
>
>> Matthew,
>>
>> pi@pi3b:/etc/weewx $ wee_extension --list
>>
>> Extension NameVersion   Description
>> Belchertown   1.2   A clean modern skin with real time streaming 
>> updates and interactive charts. Modeled after BelchertownWeather.com
>> cmon  0.20  Collect and display computer health 
>> indicators.
>>
>> So I have Belchertown as does Roger. The culprit?
>>
>
> rob,  
> could you run weewx directly so that we can see what values are in your 
> LOOP and REC?
> also, could you provide a directory listing of your 'user' directory?  do 
> this:  'ls /usr/share/weewx/user'
> 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/40a26ca0-9168-4036-bb96-f165892b8f33n%40googlegroups.com.
REC:2022-02-14 10:09:00 PST (1644862140) 'altimeter': '29.85914220177629', 
'appTemp': '43.569079119655434', 'barometer': '29.859', 'cloudbase': 
'979.0067036271072', 'consBatteryVoltage': 'None', 'dateTime': '1644862140', 
'dewpoint': '42.25237050404073', 'ET': '0.0', 'forecastRule': '45', 
'heatindex': '44.279', 'highOutTemp': '45.9', 'humidex': '45.9', 'inDewpoint': 
'43.778625198290946', 'inHumidity': '61.0', 'inTemp': '57.1', 'interval': '1', 
'leafTemp1': '-82.0', 'leafTemp2': '-82.0', 'leafWet1': '8.0', 'leafWet2': 
'8.0', 'lowOutTemp': '45.9', 'maxSolarRad': 'None', 'outHumidity': '87.0', 
'outTemp': '45.9', 'pressure': '29.694906620501794', 'rain': '0.0', 'rainRate': 
'0.0', 'rxCheckPercent': '100.0', 'soilMoist1': '8.0', 'soilMoist2': '8.0', 
'soilMoist3': '8.0', 'soilMoist4': '32.0', 'soilTemp1': '-82.0', 'soilTemp2': 
'-90.0', 'soilTemp3': '-82.0', 'soilTemp4': '-90.0', 'txBatteryStatus': 'None', 
'usUnits': '1', 'wind_samples': '24.0', 'windchill': '45.9', 'windDir': 
'202.5', 'windGust': '2.0', 'windGustDir': '135.0', 'windrun': 
'0.01', 'windSpeed': '1.0'
REC:2022-02-14 10:10:00 PST (1644862200) 'altimeter': '29.860139027692338', 
'appTemp': '44.011813576895015', 'barometer': '29.86', 'cloudbase': 
'978.6329749752173', 'consBatteryVoltage': 'None', 'dateTime': '1644862200', 
'dewpoint': '42.15401491010904', 'ET': '0.0', 'forecastRule': '45', 
'heatindex': '44.169', 'highOutTemp': '45.9', 'humidex': '45.8', 'inDewpoint': 
'43.778625198290946', 'inHumidity': '61.0', 'inTemp': '57.1', 'interval': '1', 
'leafTemp1': '-82.0', 'leafTemp2': '-82.0', 'leafWet1': '8.0', 'leafWet2': 
'8.0', 'lowOutTemp': '45.8', 'maxSolarRad': 'None', 'outHumidity': '87.0', 
'outTemp': '45.8', 'pressure': '29.695898961315308', 'rain': '0.0', 'rainRate': 
'0.0', 'rxCheckPercent': '98.229167', 'soilMoist1': '8.0', 
'soilMoist2': '8.0', 'soilMoist3': '8.0', 'soilMoist4': '32.0', 'soilTemp1': 
'-82.0', 'soilTemp2': '-90.0', 'soilTemp3': '-82.0', 'soilTemp4': '-90.0', 
'txBatteryStatus': 'None', 'usUnits': '1', 'wind_samples': '23.0', 'windchill': 
'45.8', 'windDir': 'None', 'windGust': '2.0', 'windGustDir': '247.5', 
'windrun': '0.0', 'windSpeed': '0.0'
LOOP:   2022-02-14 10:10:05 PST (1644862205) 'altimeter': '29.85914002849249', 
'appTemp': '43.44854457689501', 'barometer': '29.859', 'cloudbase': 
'978.6329749752173', 'consBatteryVoltage': '0.83', 'dateTime': '1644862205', 
'dayET': '0.0', 'dayRain': '0.05', 'dewpoint': '42.15401491010904', 'ET': 
'None', 'extraAlarm1': '0', 'extraAlarm2': '0', 'extraAlarm3': '0', 
'extraAlarm4': '0', 'extraAlarm5': '0', 'extraAlarm6': '0', 'extraAlarm7': '0', 
'extraAlarm8': '0', 'forecastIcon': '6', 'forecastRule': '45', 'heatindex': 
'44.169', 'humidex': '45.8', 'inDewpoint': '43.778625198290946', 'inHumidity': 
'61.0', 'insideAlarm': '0', 'inTemp': '57.1', 'leafWet4': '0.0', 'maxSolarRad': 
'None', 'monthET': '0.0', 'monthRain': '0.24', 'outHumidity': '87.0', 
'outsideAlarm1': '0', 'outsideAlarm2': '0', 'outTemp': '45.8', 'pressure': 
'29.694904456996444', 'rain': 'None', 'rainAlarm': '0', 'rainRate': '0.0', 
'soilLeafAlarm1': '0', 'soilLeafAlarm2': '0', 'soilLeafAlarm3': '0', 
'soilLeafAlarm4': '0', 'stormRain': '0.05', 'stormStart': '1644825600', 
'sunrise': '1644851760', 'sunset'

Re: [weewx-user] Trying to install docker and need yml assistance

[Adam Morgan]

Thank you again Doug!  Ok, part of my issue was that I had not fully read 
through the docs.  I haven't done a ton with Docker and all of the other 
containers that I had created were for apps that had their own web server 
where  I would do the configuration.  I spent a few minutes with the 
documentation right now - I see that the config is done in the 
configuration file and not in a UI.  I may tackle the web server down the 
line - I really appreciate you including that.  I am coming from Virtual 
Weather Station and my main goal is uploading to WU so that I can access 
via Alex by using some code that I wrote in AWS.  For some reason my 
uploads to WU stopped working last year and their support refused to answer 
me.  


On Monday, February 14, 2022 at 10:53:00 AM UTC-5 do...@dougjenkins.com 
wrote:

> Adam:
>
> By Default, each stack in Docker will have its own internal network. These 
> will show up as 172.16.x.x. That is ok as docker will route traffic from 
> the host to the container as long as you have the ports mapped correctly.
>
> The next thing we need to check is to see if you have a http server inside 
> the container that you are running with WeeWx. Looking at felddy's 
> weewx-docker Dockerfile (weewx-docker/Dockerfile at develop · 
> felddy/weewx-docker · GitHub 
> ) I did 
> not see a http server serving the pages. So the html will not be viewable 
> without a http server.
>
> The best course of action here is to spin up a http server as a container. 
> I actually do this for my setup (www.largoweather.com) using a nginx 
> container. What i do is configure weewx to write to a directory that is 
> shared with the container. Then I add both containers to the same yaml file 
> and have them share the same network. 
>
> Here is a copy of my yaml file. In it I am running Tom Mitchell's weewx 
> container (GitHub - tomdotorg/docker-weewx: Docker image for weewx 
> weather software ) with 
> Belchertown skin using a MQTT broker with a ngnix web server. You can 
> modify this to your liking. If you have any questions on the configs, just 
> let me know.
>
> # == WEEWX STACK START ==
> version: "2.1"
> services:
>   web:
> image: nginx
> container_name: weewx_web
> networks:
>   - wxnet
> ports:
>   - 91:80
> depends_on:
>   - mqtt-broker
>   - weewx-engine
> environment:
>   - TZ=America/New_York
>   - NGINX_HOST=<>.com
>   - NGINX_PORT=80
> volumes:
>   - /media/docker/volumes/weewx/html:/usr/share/nginx/html:ro
>   - /media/docker/volumes/ngnix/templates:/etc/nginx/templates
> restart: unless-stopped 
>   
>   mqtt-broker:
> image: eclipse-mosquitto:latest
> container_name: weewx_mqtt
> networks:
>   - wxnet
> environment:
>   - TZ=America/New_York
> volumes:
>   - /media/docker/volumes/weewx/mosquitto/config:/mosquitto/config
>   - /media/docker/volumes/weewx/mosquitto/data:/mosquitto/data
>   - /media/docker/volumes/weewx/mosquitto/log:/mosquitto/log
> ports:
>   - 1883:1883
>   - 9001:9001
> depends_on:
>   - weewx-engine
> restart: unless-stopped
>   
>   weewx-engine:
> image:  mitct02/weewx:4.5.1
> container_name: weewx_engine
> environment:
>   - TZ=America/New_York
> networks:
>   - wxnet
> privileged: true
> volumes:
>   - /media/docker/volumes/weewx/config/:/home/weewx/conf/
>   - 
> /media/docker/volumes/weewx/skins/Belchertown/:/home/weewx/skins/Belchertown/
>   - /media/docker/volumes/weewx/html/:/home/weewx/public_html/
> restart: unless-stopped
>  
> networks:
>   wxnet:
> driver: bridge
>
>
> # == WEEWX STACK STOP ===[
>
>
>
> On Sunday, February 13, 2022 at 6:36:49 PM UTC-5 muchgoo...@gmail.com 
> wrote:
>
>> Sorry, still struggling with this one.  I don't want a new network 
>> created.  Instead, I just want to bind to the host.  Any help would be 
>> greatly appreciated.  Thank you again!
>>
>> On Sunday, February 13, 2022 at 1:54:28 PM UTC-5 Adam Morgan wrote:
>>
>>> Thank you, that's a good thought.  I did verify that nothing else is 
>>> using that port (I only have 10ish containers).
>>>
>>> I did notice that this created a new network.  Could that be the issue?  
>>> In my limited experience I have only ever used "host".  This is a device 
>>> running on my network and not local host - would that mean that I can't use 
>>> the IP of the host to access it through the browser?  
>>>
>>> On Sunday, February 13, 2022 at 1:05:29 PM UTC-5 vince wrote:
>>>
 I'd run "docker ps -a" and look at which containers are forwarding 
 which ports.

>


-- 
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...@goog

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

Adam:

By Default, each stack in Docker will have its own internal network. These 
will show up as 172.16.x.x. That is ok as docker will route traffic from 
the host to the container as long as you have the ports mapped correctly.

The next thing we need to check is to see if you have a http server inside 
the container that you are running with WeeWx. Looking at felddy's 
weewx-docker Dockerfile (weewx-docker/Dockerfile at develop · 
felddy/weewx-docker · GitHub 
) I did not 
see a http server serving the pages. So the html will not be viewable 
without a http server.

The best course of action here is to spin up a http server as a container. 
I actually do this for my setup (www.largoweather.com) using a nginx 
container. What i do is configure weewx to write to a directory that is 
shared with the container. Then I add both containers to the same yaml file 
and have them share the same network. 

Here is a copy of my yaml file. In it I am running Tom Mitchell's weewx 
container (GitHub - tomdotorg/docker-weewx: Docker image for weewx weather 
software ) with Belchertown skin 
using a MQTT broker with a ngnix web server. You can modify this to your 
liking. If you have any questions on the configs, just let me know.

# == WEEWX STACK START ==
version: "2.1"
services:
  web:
image: nginx
container_name: weewx_web
networks:
  - wxnet
ports:
  - 91:80
depends_on:
  - mqtt-broker
  - weewx-engine
environment:
  - TZ=America/New_York
  - NGINX_HOST=<>.com
  - NGINX_PORT=80
volumes:
  - /media/docker/volumes/weewx/html:/usr/share/nginx/html:ro
  - /media/docker/volumes/ngnix/templates:/etc/nginx/templates
restart: unless-stopped 
  
  mqtt-broker:
image: eclipse-mosquitto:latest
container_name: weewx_mqtt
networks:
  - wxnet
environment:
  - TZ=America/New_York
volumes:
  - /media/docker/volumes/weewx/mosquitto/config:/mosquitto/config
  - /media/docker/volumes/weewx/mosquitto/data:/mosquitto/data
  - /media/docker/volumes/weewx/mosquitto/log:/mosquitto/log
ports:
  - 1883:1883
  - 9001:9001
depends_on:
  - weewx-engine
restart: unless-stopped
  
  weewx-engine:
image:  mitct02/weewx:4.5.1
container_name: weewx_engine
environment:
  - TZ=America/New_York
networks:
  - wxnet
privileged: true
volumes:
  - /media/docker/volumes/weewx/config/:/home/weewx/conf/
  - 
/media/docker/volumes/weewx/skins/Belchertown/:/home/weewx/skins/Belchertown/
  - /media/docker/volumes/weewx/html/:/home/weewx/public_html/
restart: unless-stopped
 
networks:
  wxnet:
driver: bridge


# == WEEWX STACK STOP ===[



On Sunday, February 13, 2022 at 6:36:49 PM UTC-5 muchgoo...@gmail.com wrote:

> Sorry, still struggling with this one.  I don't want a new network 
> created.  Instead, I just want to bind to the host.  Any help would be 
> greatly appreciated.  Thank you again!
>
> On Sunday, February 13, 2022 at 1:54:28 PM UTC-5 Adam Morgan wrote:
>
>> Thank you, that's a good thought.  I did verify that nothing else is 
>> using that port (I only have 10ish containers).
>>
>> I did notice that this created a new network.  Could that be the issue?  
>> In my limited experience I have only ever used "host".  This is a device 
>> running on my network and not local host - would that mean that I can't use 
>> the IP of the host to access it through the browser?  
>>
>> On Sunday, February 13, 2022 at 1:05:29 PM UTC-5 vince wrote:
>>
>>> I'd run "docker ps -a" and look at which containers are forwarding 
>>> which ports.
>>>

>>>

-- 
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/1d94b41b-62f8-43c6-9799-8a53289415e9n%40googlegroups.com.

[weewx-user] Re: Vantage Pro 2 : Weewx stops reading the data

[matthew wall]

On Monday, February 14, 2022 at 8:35:30 AM UTC-5 blaise@gmail.com wrote:

> When I look at the log, it's horror. Where can this come from. Is this the 
> cause?
> ...
> Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
>  File "_etc_weewx_skins_Seasons_titlebar_inc.py", line 344, in respond
> Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
>  TypeError: float() argument must be a string or a number, not 'NoneType'
>

in your Seasons skin, something in titlebar.inc file is expecting a float, 
but it is getting a None.

hard to say much more than that without knowing which version of weewx you 
are running, which version of Seasons skin you are running, what 
modifications (if any) you have made to either, and how your system got 
into the state that it is in (i.e., how did you install, and what changes 
did you make that started this behavior).

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/f5dcb34e-f7cd-4045-a337-0309a7cb09cfn%40googlegroups.com.

[weewx-user] Re: Vantage Pro 2 : Weewx stops reading the data

[PC]

When I look at the log, it's horror. Where can this come from. Is this the 
cause?

Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/index.html.tmpl
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
Reason: float() argument must be a string or a number, not 'NoneType'
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 326, in generate
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 unicode_string = compiled_template.respond()
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_Seasons_index_html_tmpl.py", line 203, in respond
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1707, in 
_handleCheetahInclude
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_Seasons_titlebar_inc.py", line 344, in respond
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 TypeError: float() argument must be a string or a number, not 'NoneType'
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator: Generate 
failed with exception ''
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/statistics.html.tmpl
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
Reason: float() argument must be a string or a number, not 'NoneType'
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 326, in generate
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 unicode_string = compiled_template.respond()
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_Seasons_statistics_html_tmpl.py", line 137, in 
respond
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1707, in 
_handleCheetahInclude
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_Seasons_titlebar_inc.py", line 344, in respond
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 TypeError: float() argument must be a string or a number, not 'NoneType'
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator: Generate 
failed with exception ''
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/telemetry.html.tmpl
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
Reason: float() argument must be a string or a number, not 'NoneType'
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 326, in generate
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 unicode_string = compiled_template.respond()
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_Seasons_telemetry_html_tmpl.py", line 188, in 
respond
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1707, in 
_handleCheetahInclude
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_Seasons_titlebar_inc.py", line 344, in respond
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 TypeError: float() argument must be a string or a number, not 'NoneType'
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator: Generate 
failed with exception ''
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/tabular.html.tmpl
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
Reason: float() argument must be a string or a number, not 'NoneType'
Feb 14 14:05:19 PiMeteo weewx[7206] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Feb 14 14:05:19 PiMet

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Remy Lavabre]

A *water year* (also called *hydrological year*, *discharge year* or *flow 
year*) is a term commonly used in hydrology 
 to describe a time period of 12 
months for which precipitation 
 totals are measured. Its 
beginning differs from the calendar year 
 because part of the 
precipitation that falls in late autumn and winter accumulates as snow 
 and does not drain until the 
following spring or summer's snowmelt 
.

Due to meteorological and geographical factors, the definition of the water 
years varies; the United States Geological Survey 
 defines 
it as the period between October 1 of one year and September 30th of the 
next. The water year is designated by the calendar year in which it ends, 
so the 2010 water year (USGS) started on October 1, 2009 and ended on 
September 30, 2010.

One way to identify a water-year is to find that successive 12-month period 
that most consistently, year after year, gives the highest correlation 
between precipitation and streamflow and negligible changes in storage 
(i.e., soil water and snow).
Thank’s Wikipedia...
Le lundi 14 février 2022 à 12:45:58 UTC+1, paul...@gmail.com a écrit :

> Checked this morning and pleased to say Max Wind direction is now 
> reporting and updating in the Day tab of the Statistics section. Still N/A 
> in Week but I'm guessing it will update in due course.
> Just out of interest I've noticed in the Statistics section the Year tab 
> is blue and if you click on it you get the option of Year or Rain Year. 
> What actually is the difference between these two? In my case the values 
> reported are identical.
> Paul
>
> On Sunday, 13 February 2022 at 20:01:25 UTC remy.l...@gmail.com wrote:
>
>> Yes, it’s the good python file, same as me  (if standard installation...)
>> The Tom’s update/patch solves perfectly the problem and also min/max 
>> windGustDir data base.
>> Try stop and start weewx (logicaly same thing as restart... !?)
>> Try to look for all wxxtype.py on your system to see if there is another 
>> file ? Logicaly no...
>>
>>
>> Le dimanche 13 février 2022 à 20:23:07 UTC+1, paul...@gmail.com a écrit :
>>
>>> Hi Remy
>>> Yes I did sudo /etc/init.d/weewx restart. Just in case I've done it 
>>> again but no change.
>>> Can I just check I swapped the correct wxxtypes.py file. I swapped the 
>>> one in /usr/share/weewx/weewx
>>> Paul
>>>
>>> On Sunday, 13 February 2022 at 18:08:44 UTC remy.l...@gmail.com wrote:
>>>
 Hi Paul.
 Have you triedto stop weewx and restart it ?
 You must do that if you modify python file.
 Cordialy 


 Le dimanche 13 février 2022 à 18:32:38 UTC+1, paul...@gmail.com a 
 écrit :

> I don't report wind gust values/direction in the Current Conditions 
> section of my Seasons skin (version 4.6.2) but in the Statistics 
> (previously High/Low) section I've always had a Max Wind entry with both 
> speed and direction reported. Since 4.6.2 the direction is reported as 
> N/A 
> so I've followed this thread and replaced the wxxtypes.py file with the 
> new 
> one from Tom but it doesn't seem to have made any difference to my Max 
> Wind 
> entry. If you look at the Statistics report below it still shows N/A for 
> Max Wind degrees for Day and Week but for Month and Year (presumably data 
> from 4.5.1) a degree value is reported.
>
> [image: Max Wind.jpg]
> Any suggestions?
>
> Paul
> On Sunday, 13 February 2022 at 15:04:26 UTC asla...@gmail.com wrote:
>
>> Brilliant, now it work just fine.
>> Thanks a lot.
>>
>> On Sunday, February 13, 2022 at 3:28:45 PM UTC+1 remy.l...@gmail.com 
>> wrote:
>>
>>> Yes !! Thank-you Tom it works great now :
>>>
>>> [image: Capture d’écran de 2022-02-13 15-26-27.png]
>>> Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a 
>>> écrit :
>>>
 I was able to replicate the problem. Pre V4.6, if windGustDir was 
 missing, windDir was substituted. That behavior went away with v4.6. 
 This 
 patch restores it.

 Index: bin/weewx/wxxtypes.py
 ===
 diff --git a/bin/weewx/wxxtypes.py b/bin/weewx/wxxtypes.py
 --- a/bin/weewx/wxxtypes.py (revision 
 279bb450ab801c80a12b8ceadd0144e16c473bea)
 +++ b/bin/weewx/wxxtypes.py (date 1644758479921)
 @@ -98,11 +98,18 @@
  return ValueTuple(val, 'degree_compass', 'group_direction')
  
  def calc_windGustDir(self, key, data, db_manager):
 -# Return the current gust direction if windGust is 
 non-zero

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[paul...@gmail.com]

Checked this morning and pleased to say Max Wind direction is now reporting 
and updating in the Day tab of the Statistics section. Still N/A in Week 
but I'm guessing it will update in due course.
Just out of interest I've noticed in the Statistics section the Year tab is 
blue and if you click on it you get the option of Year or Rain Year. What 
actually is the difference between these two? In my case the values 
reported are identical.
Paul

On Sunday, 13 February 2022 at 20:01:25 UTC remy.l...@gmail.com wrote:

> Yes, it’s the good python file, same as me  (if standard installation...)
> The Tom’s update/patch solves perfectly the problem and also min/max 
> windGustDir data base.
> Try stop and start weewx (logicaly same thing as restart... !?)
> Try to look for all wxxtype.py on your system to see if there is another 
> file ? Logicaly no...
>
>
> Le dimanche 13 février 2022 à 20:23:07 UTC+1, paul...@gmail.com a écrit :
>
>> Hi Remy
>> Yes I did sudo /etc/init.d/weewx restart. Just in case I've done it again 
>> but no change.
>> Can I just check I swapped the correct wxxtypes.py file. I swapped the 
>> one in /usr/share/weewx/weewx
>> Paul
>>
>> On Sunday, 13 February 2022 at 18:08:44 UTC remy.l...@gmail.com wrote:
>>
>>> Hi Paul.
>>> Have you triedto stop weewx and restart it ?
>>> You must do that if you modify python file.
>>> Cordialy 
>>>
>>>
>>> Le dimanche 13 février 2022 à 18:32:38 UTC+1, paul...@gmail.com a 
>>> écrit :
>>>
 I don't report wind gust values/direction in the Current Conditions 
 section of my Seasons skin (version 4.6.2) but in the Statistics 
 (previously High/Low) section I've always had a Max Wind entry with both 
 speed and direction reported. Since 4.6.2 the direction is reported as N/A 
 so I've followed this thread and replaced the wxxtypes.py file with the 
 new 
 one from Tom but it doesn't seem to have made any difference to my Max 
 Wind 
 entry. If you look at the Statistics report below it still shows N/A for 
 Max Wind degrees for Day and Week but for Month and Year (presumably data 
 from 4.5.1) a degree value is reported.

 [image: Max Wind.jpg]
 Any suggestions?

 Paul
 On Sunday, 13 February 2022 at 15:04:26 UTC asla...@gmail.com wrote:

> Brilliant, now it work just fine.
> Thanks a lot.
>
> On Sunday, February 13, 2022 at 3:28:45 PM UTC+1 remy.l...@gmail.com 
> wrote:
>
>> Yes !! Thank-you Tom it works great now :
>>
>> [image: Capture d’écran de 2022-02-13 15-26-27.png]
>> Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a 
>> écrit :
>>
>>> I was able to replicate the problem. Pre V4.6, if windGustDir was 
>>> missing, windDir was substituted. That behavior went away with v4.6. 
>>> This 
>>> patch restores it.
>>>
>>> Index: bin/weewx/wxxtypes.py
>>> ===
>>> diff --git a/bin/weewx/wxxtypes.py b/bin/weewx/wxxtypes.py
>>> --- a/bin/weewx/wxxtypes.py (revision 
>>> 279bb450ab801c80a12b8ceadd0144e16c473bea)
>>> +++ b/bin/weewx/wxxtypes.py (date 1644758479921)
>>> @@ -98,11 +98,18 @@
>>>  return ValueTuple(val, 'degree_compass', 'group_direction')
>>>  
>>>  def calc_windGustDir(self, key, data, db_manager):
>>> -# Return the current gust direction if windGust is 
>>> non-zero, otherwise, None
>>> -if 'windGust' not in data or 'windGustDir' not in data:
>>> +"""If windGustDir is missing, substitute windDir.
>>> +Set windGustDir to None if windGust is zero."""
>>> +if 'windGust' not in data:
>>>  raise weewx.CannotCalculate
>>>  if self.force_null and data['windGust'] == 0:
>>> +# windGust is zero. Force windGustDir to None
>>>  val = None
>>> +elif 'windGustDir' not in data:
>>> +# windGustDir is missing. If available, substitute 
>>> windDir.
>>> +if 'windDir' not in data:
>>> +raise weewx.CannotCalculate
>>> +val = data['windDir']
>>>  else:
>>>  val = data['windGustDir']
>>>  return ValueTuple(val, 'degree_compass', 'group_direction')
>>>
>>> Commit 9dc4da8 
>>> 
>>> . 
>>>
>>> If you want this right away, you can replace weewx/wxxtypes.py with 
>>> this 
>>> version 
>>> 
>>> .
>>>
>>>
>>>
>>> On Sun, Feb 13, 2022 at 1:38 AM Remy Lavabre  
>>> wrote:
>>>

 [image: Capture d’écran de 2022-02-13 10-14-16.png]

 Same problem for me !
 Since weewx 4.6.x windGustDir is always N/A but the value is

[weewx-user] Re: Historic data graphs and "Current Conditions" missing in Seasons

[Olle Bertilsson]

No modifications. Had to re-clone the SD-card and start from the beginning 
again. This time I skipped updating to 4.6.2. Now running on 4.5.1 as 
before and every works perfectly.
Compared current.inc, in Seasons, from 4.6.2 with 4.5.1 and found that most 
tables were missing in the one from 4.6.2. It seems like current.inc was 
corrupted during updating.
Is that a known issue?
Now I don't dare to update again...

söndag 13 februari 2022 kl. 01:45:15 UTC+1 skrev matthew wall:

> On Saturday, February 12, 2022 at 12:21:49 PM UTC-5 ollebert...@gmail.com 
> wrote:
>
>> Later I updated to version 4.6.2.
>> Seasons are now only presenting Temperature and Barometer in Current 
>> Conditions. Historical graphs only showing Temperature, Wind and Rain. 
>> Missing: Barometer, Wind chill/Heat index, Humidity, Wind directions and 
>> Wind Vector.
>> Also missing Hi/Lo table.
>>
>
> have you made any modifications to the Seasons skin before updating to 
> 4.6.2?
>
>

-- 
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/99e33b30-92cc-4b3b-bf47-df7275498706n%40googlegroups.com.

[weewx-user] Re: Vantage Pro 2 : Weewx stops reading the data

[PC]

In the same line, is the USB datalogger more reliable than the IP, or it 
has nothing to do?

Le lundi 14 février 2022 à 09:09:07 UTC+1, PC a écrit :

> Hello, 
> Vantage Pro2 and Datalogger IP. Weewx stops reading the data yesterday at 
> 16:45. You gave the solution (I think I erase memory), but I forgot to note 
> it.
> Thank you !

-- 
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/c9ebb947-25af-42de-8f30-ffd3d75f0854n%40googlegroups.com.

[weewx-user] Vantage Pro 2 : Weewx stops reading the data

[PC]

Hello, 
Vantage Pro2 and Datalogger IP. Weewx stops reading the data yesterday at 
16:45. You gave the solution (I think I erase memory), but I forgot to note 
it.
Thank you !

-- 
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/97768499-a1d2-4805-988c-713d4ba4cc8bn%40googlegroups.com.