[weewx-user] Help with Raspberrypi V5.4.51

2020-09-27 Thread Chris Neville
Hi
My SDcard had an issue and died, so I am rebuilding

I have a Pi V3b+ and was running Raspbian, however this is now Raspberrypi.

When I try to get WeeWx, it will recognise  'http://weewx.com/apt/python3 
buster main' however when I run "sudo apt-get update" 
I get an error that "http://weewx.com/apt/python3 buster InRelease" and 
that there is no public key, so is blocked as it can't be downloaded safely.

Anyone get this?
Is it an issue with my Pi or weewx.com?

Thanks

Chris

-- 
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/5c1072b5-8a7b-4f51-b95a-131e486e1054n%40googlegroups.com.


Re: [weewx-user] Re: Davis AirLink and PurpleAir

2020-09-27 Thread Graham Eddy
yes, john has already done the hard work. it’s just a case of wrapping the AQI 
part differently (called from WXCalculate rather than ‘airlink’ PMx.x 
collector) and positioning it as a process_service not data_service - that’s 
what i meant by “pinching his code"

> On 28 Sep 2020, at 10:56 am, John Kline  wrote:
> 
>> Oh. So you already have a way to calculate AQI from the PM data?
> 
> Yep.  It’s there.
> 
>> On Sep 27, 2020, at 5:48 PM, Tom Keffer > > wrote:
>> 
>> 
>> Oh. So you already have a way to calculate AQI from the PM data?
> 

-- 
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/DA3EBB64-5D54-48BF-A244-B0C7A43B2328%40gmail.com.


Re: [weewx-user] Re: PI update Weewx

2020-09-27 Thread Michael Sanphillipo
CRT is working and I'm using WEEwx in python3. It's only when I update the 
apt that it' wants to install weewx again that's when CRT fails. It's all 
working fine at this point I just won't update weewx  since I'm already 
using the latest version.


On Sunday, September 27, 2020 at 8:24:49 PM UTC-4 steep...@gmail.com wrote:

> Did you update weewx-crt? The version you have may not be Python3 
> compliant.
> IM
>
> On Sun, 27 Sep 2020 at 23:45, Michael Sanphillipo  
> wrote:
>
>> I tried that yesterday and when I ran update it updated Weewx even though 
>> I was already on the latest version then I had errors with crt.py. So I had 
>> to do a restore from an image I did before I made the change. 
>>
>> On Sunday, September 27, 2020 at 6:24:26 PM UTC-4 vince wrote:
>>
>>> On Sunday, September 27, 2020 at 2:26:48 PM UTC-7, Michael Sanphillipo 
>>> wrote:

 I recently switched Weewx to Python3, but I notice when I run Updates 
 on my PI I see the following.

 sudo apt update
 Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
 Hit:2 http://weewx.com/apt/python2 squeeze InRelease   

 Will this cause an issue if I'm using Python 3? If so what should I 
 change?

>>>
>>> I would try the python3 version of the  'configure apt' instructions in 
>>> http://www.weewx.com/docs/debian.htm and see if that repoints your 
>>> weewx repo at the python3 version.
>>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -- 
>>
>>
>> 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/293b4fa3-4e4e-4137-827b-53b400fd5361n%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/ee82f034-3b93-4619-a2c5-6f71f86aca17n%40googlegroups.com.


Re: [weewx-user] Re: Davis AirLink and PurpleAir

2020-09-27 Thread John Kline
> Oh. So you already have a way to calculate AQI from the PM data?

Yep.  It’s there.

> On Sep 27, 2020, at 5:48 PM, Tom Keffer  wrote:
> 
> 
> Oh. So you already have a way to calculate AQI from the PM data?
> 
>> On Sun, Sep 27, 2020 at 5:46 PM John Kline  wrote:
>> It’s already using XTypes for everything derived; so, not much to figure out 
>> there.
>> 
 On Sep 27, 2020, at 5:42 PM, Tom Keffer  wrote:
 
>>> 
>>> Here's the wiki on XTypes. I believe John has written an XTypes extension. 
>>> Between the two of you, I'm sure you can figure it out!
>>> 
>>> -tk
>>> 
>>> 
 On Sun, Sep 27, 2020 at 8:47 AM Graham Eddy  wrote:
 i had not thought to put the collection of AQI calculations into an 
 extension to StdWXCalculate
 
 i amend my suggested split of weewx-airlink to an ‘airlink’ data 
 acquisition service providing PMx.x values, plus an ‘aqi’ extension to 
 StdWXCalculate to convert PMx.x values to AQI-related values
 
 and yes, i’d be happy to code this extension (mainly by pinching john’s 
 code) if john wanted to head that direction - i’ll have to code something 
 similar/simpler for myself anyway if john doesn't want to go that way 
 (i.e. separate ‘aqi’ (sub-)service)
 
> On 27 Sep 2020, at 10:28 pm, Tom Keffer  wrote:
> 
> The "WeeWX way" is to emit what the hardware offers, then let 
> StdWXCalculate determine whether to keep it or calculate a new value in 
> software.
> 
> Right now, it's fairly easy to extend StdWXCalculate to calculate new 
> types via the XTypes facility. Gary and I are working on a version that 
> will make it even easier.
> 
>> On Sat, Sep 26, 2020 at 10:30 PM Graham Eddy  
>> wrote:
>> i was about to pinch john’s code for the AQI side of things - i get 
>> PM2.5 values via gw1000 - when i see this new driver announced. (i have 
>> found ecowitt’s purported 24 hour average values very unreliable - 
>> drifting, random resets, etc - but the actual pm2.5 values seem fine → 
>> derive the averaged values myself)
>> 
>> can i suggest that acquiring PMx.x values and deriving AQI values be 
>> kept as separate services? the AQI service would provide AQI xtype 
>> (mainly for cheetah) and convert PMx.x values in weewx packets to 
>> equivalent AQI values inserted into weewx packet (this is what i was 
>> going to implement). design-wise this would also allow support of AQI 
>> values derived from multiple pollution types (NO, etc) as well as 
>> abstracting the pollutant monitors
>> 
>>> On 27 Sep 2020, at 1:43 pm, John Kline  wrote:
>>> 
>>> Hi Rich,
>>> 
>>> I’ve created the github project here:
>>> https://github.com/chaunceygardiner/weewx-airlink
>>> 
>>> I haven’t had any issues with the extension, but it’s not a priority 
>>> for me until more is known about the AirLink.
>>> 
>>> Cheers,
>>> John
>>> 
>> 
>> 
>> -- 
>> 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/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%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/CAPq0zEATLW%2BWMaguZvAN0VULz%3DbyZWHUO8CHq6V%3DmVhG7nE-Sg%40mail.gmail.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/5A2D0839-5245-4DC3-9642-09F80D65BF71%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/CAPq0zED545gSC6m9OtdheVy%2Becjm%3DecTuB%3DM%3DXAeLiwBSj%2B28w%40mail.gmail.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 
>> 

Re: [weewx-user] Re: Davis AirLink and PurpleAir

2020-09-27 Thread Tom Keffer
Oh. So you already have a way to calculate AQI from the PM data?

On Sun, Sep 27, 2020 at 5:46 PM John Kline  wrote:

> It’s already using XTypes for everything derived; so, not much to figure
> out there.
>
> On Sep 27, 2020, at 5:42 PM, Tom Keffer  wrote:
>
> 
> Here's the wiki on XTypes
> . I
> believe John has written an XTypes extension. Between the two of you, I'm
> sure you can figure it out!
>
> -tk
>
>
> On Sun, Sep 27, 2020 at 8:47 AM Graham Eddy  wrote:
>
>> i had not thought to put the collection of AQI calculations into an
>> extension to StdWXCalculate
>>
>> i amend my suggested split of weewx-airlink to an ‘airlink’ data
>> acquisition service providing PMx.x values, plus an ‘aqi’ extension to
>> StdWXCalculate to convert PMx.x values to AQI-related values
>>
>> and yes, i’d be happy to code this extension (mainly by pinching john’s
>> code) if john wanted to head that direction - i’ll have to code something
>> similar/simpler for myself anyway if john doesn't want to go that way (i.e.
>> separate ‘aqi’ (sub-)service)
>>
>> On 27 Sep 2020, at 10:28 pm, Tom Keffer  wrote:
>>
>> The "WeeWX way" is to emit what the hardware offers, then let
>> StdWXCalculate determine whether to keep it or calculate a new value in
>> software.
>>
>> Right now, it's fairly easy to extend StdWXCalculate to calculate new
>> types via the XTypes facility. Gary and I are working on a version that
>> will make it even easier.
>>
>> On Sat, Sep 26, 2020 at 10:30 PM Graham Eddy 
>> wrote:
>>
>>> i was about to pinch john’s code for the AQI side of things - i get
>>> PM2.5 values via gw1000 - when i see this new driver announced. (i have
>>> found ecowitt’s purported 24 hour average values very unreliable -
>>> drifting, random resets, etc - but the actual pm2.5 values seem fine →
>>> derive the averaged values myself)
>>>
>>> can i suggest that acquiring PMx.x values and deriving AQI values be
>>> kept as separate services? the AQI service would provide AQI xtype (mainly
>>> for cheetah) and convert PMx.x values in weewx packets to equivalent AQI
>>> values inserted into weewx packet (this is what i was going to implement).
>>> design-wise this would also allow support of AQI values derived from
>>> multiple pollution types (NO, etc) as well as abstracting the pollutant
>>> monitors
>>>
>>> On 27 Sep 2020, at 1:43 pm, John Kline  wrote:
>>>
>>> Hi Rich,
>>>
>>> I’ve created the github project here:
>>> https://github.com/chaunceygardiner/weewx-airlink
>>>
>>> I haven’t had any issues with the extension, but it’s not a priority for
>>> me until more is known about the AirLink.
>>>
>>> Cheers,
>>> John
>>>
>>>
>>>
>>> --
>>> 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/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%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/CAPq0zEATLW%2BWMaguZvAN0VULz%3DbyZWHUO8CHq6V%3DmVhG7nE-Sg%40mail.gmail.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/5A2D0839-5245-4DC3-9642-09F80D65BF71%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/CAPq0zED545gSC6m9OtdheVy%2Becjm%3DecTuB%3DM%3DXAeLiwBSj%2B28w%40mail.gmail.com
> 
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To 

Re: [weewx-user] Re: Davis AirLink and PurpleAir

2020-09-27 Thread John Kline
It’s already using XTypes for everything derived; so, not much to figure out 
there.

> On Sep 27, 2020, at 5:42 PM, Tom Keffer  wrote:
> 
> 
> Here's the wiki on XTypes. I believe John has written an XTypes extension. 
> Between the two of you, I'm sure you can figure it out!
> 
> -tk
> 
> 
>> On Sun, Sep 27, 2020 at 8:47 AM Graham Eddy  wrote:
>> i had not thought to put the collection of AQI calculations into an 
>> extension to StdWXCalculate
>> 
>> i amend my suggested split of weewx-airlink to an ‘airlink’ data acquisition 
>> service providing PMx.x values, plus an ‘aqi’ extension to StdWXCalculate to 
>> convert PMx.x values to AQI-related values
>> 
>> and yes, i’d be happy to code this extension (mainly by pinching john’s 
>> code) if john wanted to head that direction - i’ll have to code something 
>> similar/simpler for myself anyway if john doesn't want to go that way (i.e. 
>> separate ‘aqi’ (sub-)service)
>> 
>>> On 27 Sep 2020, at 10:28 pm, Tom Keffer  wrote:
>>> 
>>> The "WeeWX way" is to emit what the hardware offers, then let 
>>> StdWXCalculate determine whether to keep it or calculate a new value in 
>>> software.
>>> 
>>> Right now, it's fairly easy to extend StdWXCalculate to calculate new types 
>>> via the XTypes facility. Gary and I are working on a version that will make 
>>> it even easier.
>>> 
 On Sat, Sep 26, 2020 at 10:30 PM Graham Eddy  wrote:
 i was about to pinch john’s code for the AQI side of things - i get PM2.5 
 values via gw1000 - when i see this new driver announced. (i have found 
 ecowitt’s purported 24 hour average values very unreliable - drifting, 
 random resets, etc - but the actual pm2.5 values seem fine → derive the 
 averaged values myself)
 
 can i suggest that acquiring PMx.x values and deriving AQI values be kept 
 as separate services? the AQI service would provide AQI xtype (mainly for 
 cheetah) and convert PMx.x values in weewx packets to equivalent AQI 
 values inserted into weewx packet (this is what i was going to implement). 
 design-wise this would also allow support of AQI values derived from 
 multiple pollution types (NO, etc) as well as abstracting the pollutant 
 monitors
 
> On 27 Sep 2020, at 1:43 pm, John Kline  wrote:
> 
> Hi Rich,
> 
> I’ve created the github project here:
> https://github.com/chaunceygardiner/weewx-airlink
> 
> I haven’t had any issues with the extension, but it’s not a priority for 
> me until more is known about the AirLink.
> 
> Cheers,
> John
> 
 
 
 -- 
 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/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%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/CAPq0zEATLW%2BWMaguZvAN0VULz%3DbyZWHUO8CHq6V%3DmVhG7nE-Sg%40mail.gmail.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/5A2D0839-5245-4DC3-9642-09F80D65BF71%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/CAPq0zED545gSC6m9OtdheVy%2Becjm%3DecTuB%3DM%3DXAeLiwBSj%2B28w%40mail.gmail.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/996EEDED-C846-4D73-B45B-60643A176FCA%40johnkline.com.


Re: [weewx-user] Re: Davis AirLink and PurpleAir

2020-09-27 Thread Tom Keffer
Here's the wiki on XTypes
. I
believe John has written an XTypes extension. Between the two of you, I'm
sure you can figure it out!

-tk


On Sun, Sep 27, 2020 at 8:47 AM Graham Eddy  wrote:

> i had not thought to put the collection of AQI calculations into an
> extension to StdWXCalculate
>
> i amend my suggested split of weewx-airlink to an ‘airlink’ data
> acquisition service providing PMx.x values, plus an ‘aqi’ extension to
> StdWXCalculate to convert PMx.x values to AQI-related values
>
> and yes, i’d be happy to code this extension (mainly by pinching john’s
> code) if john wanted to head that direction - i’ll have to code something
> similar/simpler for myself anyway if john doesn't want to go that way (i.e.
> separate ‘aqi’ (sub-)service)
>
> On 27 Sep 2020, at 10:28 pm, Tom Keffer  wrote:
>
> The "WeeWX way" is to emit what the hardware offers, then let
> StdWXCalculate determine whether to keep it or calculate a new value in
> software.
>
> Right now, it's fairly easy to extend StdWXCalculate to calculate new
> types via the XTypes facility. Gary and I are working on a version that
> will make it even easier.
>
> On Sat, Sep 26, 2020 at 10:30 PM Graham Eddy 
> wrote:
>
>> i was about to pinch john’s code for the AQI side of things - i get PM2.5
>> values via gw1000 - when i see this new driver announced. (i have found
>> ecowitt’s purported 24 hour average values very unreliable - drifting,
>> random resets, etc - but the actual pm2.5 values seem fine → derive the
>> averaged values myself)
>>
>> can i suggest that acquiring PMx.x values and deriving AQI values be kept
>> as separate services? the AQI service would provide AQI xtype (mainly for
>> cheetah) and convert PMx.x values in weewx packets to equivalent AQI values
>> inserted into weewx packet (this is what i was going to implement).
>> design-wise this would also allow support of AQI values derived from
>> multiple pollution types (NO, etc) as well as abstracting the pollutant
>> monitors
>>
>> On 27 Sep 2020, at 1:43 pm, John Kline  wrote:
>>
>> Hi Rich,
>>
>> I’ve created the github project here:
>> https://github.com/chaunceygardiner/weewx-airlink
>>
>> I haven’t had any issues with the extension, but it’s not a priority for
>> me until more is known about the AirLink.
>>
>> Cheers,
>> John
>>
>>
>>
>> --
>> 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/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%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/CAPq0zEATLW%2BWMaguZvAN0VULz%3DbyZWHUO8CHq6V%3DmVhG7nE-Sg%40mail.gmail.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/5A2D0839-5245-4DC3-9642-09F80D65BF71%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/CAPq0zED545gSC6m9OtdheVy%2Becjm%3DecTuB%3DM%3DXAeLiwBSj%2B28w%40mail.gmail.com.


Re: [weewx-user] Re: Belchertown hook1 not refreshing

2020-09-27 Thread Tim Tuck

Hi Manfred,

Thanks for that, I'll have to give that a try,

cheers

Tim

On 25/9/20 5:50 am, Manfred Maier wrote:

So, this is my approach.

In the index.html.tmpl I've included the following script:

    
setInterval("reload_hook();", 1);
        function reload_hook () {
$.get('./hooks/hook_after_station_info.html', function(data) {
\$('#target_after_station_info').html(data);
                })
        }
    

This script replaces later in the index.html a certain content by the 
content of the file hook_after_station_info.html in the subfolder 
'hooks'. The replacement is done every 1 milliseconds.


In the same index.html.tmpl file I've replaced the code, that manages 
the content of the "index_hook_after-station_info" by the following:


                #if os.path.exists("index_hook_after_station_info.inc")
                
                

                    
                    #include "index_hook_after_station_info.inc"
                    
                
                
                #end if

 In the index_hook_after_station_info.inc I've put the HTML code that 
should be displayed on the page. In my case the file contains a couple 
of custom calculations of variables and then the following html code:




$suntext $raintext

https://www.brezentrager.de/wetter-zorneding/; 
target="_blank">Hier geht's zur aktuellen Vorhersage für Zorneding




The last missing part is the file that is used to update the index hook.
As mentioned above, this file is stored in the subfolder 'hooks'. So 
create this subfolder in your Belchertown folder and create a file 
called 'hook_after_station_info.html.tmpl'. The content of this file 
is identical to the content of the index_hook_after_station_info.inc


Finally you have to tell Belchertown, that this file has to be 
produced every time the skin is produced. This can be done in the 
skin.conf file.

Under [CheetahGenerator] add:

        [[[hooks]]]
            template = hooks/hook_after_station_info.html.tmpl

This approach leads to the desired behavior (i.e. the index hook 
updates automatically). But I'm definitely not an experienced 
web-programmer. I'm pretty sure there is a more elegant way of doing 
it. There's for example no reason for having two separate file with 
the code for the index_hook. This easily could be done with just one file.


Hope this works for you. In case you have any questions, please let me 
know.


Best,
Manfred

Manfred Maier schrieb am Donnerstag, 24. September 2020 um 13:46:16 UTC+2:

Hi Tim,
the only thing you've missed is that the refresh of the image
hooks only works for images.

There is a workaround available (using some custom script). I
hopefully find some time later in the evening to post the solution
here.

I'm using this workaround on my page: wetter-zorneding.de

The text below the station observations updates automatically
(showing the sunshine hours and amount of rain).

Best,
Manfred

ti...@skybase.net schrieb am Donnerstag, 24. September 2020 um
09:39:28 UTC+2:

Hi all,

I have this in my index_hook_after_station_info.inc


      The 24hr AQI for South Penrith is
$current($data_binding='aqi_binding').aqi_pm2_5 which is

$aqi($current($data_binding='aqi_binding').aqi_pm2_5_category).category.




and in /etc/weewx/weewx.conf I have ..

    reload_hook_images = 1
    reload_images_hook_asi = 300

But hook1 never refreshes.

Have I missed something ?

thanks

Tim


--
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/ec9f86d9-7a8f-4df7-aa39-9dab82d9df52n%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/cd8b9fa4-c6b2-7109-1495-056aac20392d%40skybase.net.


[weewx-user] Getting ObserverIp working with python3

2020-09-27 Thread Bill Eaton
I'm upgrading my desktop/server to Ubuntu 20.04/Python3. My old 
installation of WeeWx was running on Python2.7. On Python 2.7, I was able 
to get Matt Walls ObserverIp driver working. 

I hacked up the ObserverIp driver fixing all of the things that wouldn't 
work in Python 3 until all of the errors went away. I gave up when I got 
the driver running on it's own, but WeeWx was logging some kind of dict 
rain gauge error.

Now I'm working on the Interceptor driver in listen mode. It runs in 
Python3 with no errors. But I don't seem to be getting any data either. I'm 
not 100% clear how it's supposed to work. I telnetted into the bridge and 
configured it to point to the static address on my desktop/server 
computer(setdsthn ). By default the bridge wants to talk 
to port 5000, so I put port 5000 in the weewx.conf file.

The interceptor.py driver runs by itself without errors. And WeeWx starts 
without errors, but there are a bunch of messages 

DEBUG user.interceptor: empty queue

Has anyone had any success with Interceptor in Python3? 

Sep 27 17:00:31 locutus weewx[56069] INFO __main__: Using Python 3.8.2 
(default, Jul 16 2020, 14:00:26) #012[GCC 9.3.0]
Sep 27 17:00:31 locutus weewx[56069] INFO __main__: Platform 
Linux-5.4.0-48-generic-x86_64-with-glibc2.29
Sep 27 17:00:31 locutus weewx[56069] INFO __main__: Locale is 'en_US.UTF-8'
Sep 27 17:00:31 locutus weewx[56069] INFO __main__: PID file is 
/var/run/weewx.pid
Sep 27 17:00:31 locutus weewx[56072] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Sep 27 17:00:31 locutus weewx[56072] INFO __main__: Debug is 1
Sep 27 17:00:31 locutus weewx[56072] DEBUG __main__: Initializing engine
Sep 27 17:00:31 locutus weewx[56072] INFO weewx.engine: Loading station 
type Interceptor (user.interceptor)
Sep 27 17:00:31 locutus weewx[56040]:...done.
Sep 27 17:00:31 locutus systemd[1]: Started LSB: weewx weather system.
Sep 27 17:00:31 locutus weewx[56072] INFO user.interceptor: driver version 
is 0.53
Sep 27 17:00:31 locutus weewx[56072] INFO user.interceptor: device type: 
acurite-bridge
Sep 27 17:00:31 locutus weewx[56072] INFO user.interceptor: mode is listen
Sep 27 17:00:31 locutus weewx[56072] INFO user.interceptor: listen on :5000
Sep 27 17:00:31 locutus weewx[56072] INFO user.interceptor: sensor map: 
{'pressure': 'pressure.*.*', 'inTemp': 'temperature_in.*.*', 'inHumidity': 
'humidity_in.*.*', 'outTemp': 'temperature.?*.*', 'outHumidity': 
'humidity.?*.*', 'windSpeed': 'windspeed.?*.*', 'windDir': 'winddir.?*.*', 
'rain': 'rainfall.?*.*', 'txBatteryStatus': 'battery.?*.*', 
'rxCheckPercent': 'rssi.?*.*'}
Sep 27 17:00:31 locutus weewx[56072] DEBUG user.interceptor: start tcp 
server
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Sep 27 17:00:31 locutus weewx[56072] INFO weewx.engine: StdConvert target 
unit is 0x1
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.manager: Daily summary 
version is 1.0
Sep 27 17:00:31 locutus weewx[56072] INFO weewx.wxservices: The following 
values will be calculated: pressure=prefer_hardware, 
altimeter=prefer_hardware, appTemp=prefer_hardware, 
barometer=prefer_hardware, beaufort=prefer_hardware, 
cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
heatindex=prefer_hardware, humidex=prefer_hardware, 
inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
Sep 27 17:00:31 locutus weewx[56072] INFO weewx.wxservices: The following 
algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Sep 27 17:00:31 locutus weewx[56072] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Sep 27 17:00:31 locutus weewx[56072] INFO weewx.engine: Archive will use 
data binding wx_binding
Sep 27 17:00:31 locutus weewx[56072] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Sep 27 17:00:31 locutus weewx[56072] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Sep 27 

Re: [weewx-user] Re: PI update Weewx

2020-09-27 Thread steeple ian
Did you update weewx-crt? The version you have may not be Python3 compliant.
IM

On Sun, 27 Sep 2020 at 23:45, Michael Sanphillipo 
wrote:

> I tried that yesterday and when I ran update it updated Weewx even though
> I was already on the latest version then I had errors with crt.py. So I had
> to do a restore from an image I did before I made the change.
>
> On Sunday, September 27, 2020 at 6:24:26 PM UTC-4 vince wrote:
>
>> On Sunday, September 27, 2020 at 2:26:48 PM UTC-7, Michael Sanphillipo
>> wrote:
>>>
>>> I recently switched Weewx to Python3, but I notice when I run Updates on
>>> my PI I see the following.
>>>
>>> sudo apt update
>>> Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
>>> Hit:2 http://weewx.com/apt/python2 squeeze InRelease
>>>
>>> Will this cause an issue if I'm using Python 3? If so what should I
>>> change?
>>>
>>
>> I would try the python3 version of the  'configure apt' instructions in
>> http://www.weewx.com/docs/debian.htm and see if that repoints your weewx
>> repo at the python3 version.
>>
>
>
>
>
>
>
>
>
> --
>
>
> 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/293b4fa3-4e4e-4137-827b-53b400fd5361n%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/CADASSaTfaFCi_k6J-XZG_6z%2Boo93PoTN%3DO4UBrj2qrgJmQAviw%40mail.gmail.com.


[weewx-user] Re: PI update Weewx

2020-09-27 Thread Michael Sanphillipo
I tried that yesterday and when I ran update it updated Weewx even though I 
was already on the latest version then I had errors with crt.py. So I had 
to do a restore from an image I did before I made the change. 

On Sunday, September 27, 2020 at 6:24:26 PM UTC-4 vince wrote:

> On Sunday, September 27, 2020 at 2:26:48 PM UTC-7, Michael Sanphillipo 
> wrote:
>>
>> I recently switched Weewx to Python3, but I notice when I run Updates on 
>> my PI I see the following.
>>
>> sudo apt update
>> Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
>> Hit:2 http://weewx.com/apt/python2 squeeze InRelease   
>>
>> Will this cause an issue if I'm using Python 3? If so what should I 
>> change?
>>
>
> I would try the python3 version of the  'configure apt' instructions in 
> http://www.weewx.com/docs/debian.htm and see if that repoints your weewx 
> repo at the python3 version.
>

-- 
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/293b4fa3-4e4e-4137-827b-53b400fd5361n%40googlegroups.com.


[weewx-user] Re: PI update Weewx

2020-09-27 Thread vince
On Sunday, September 27, 2020 at 2:26:48 PM UTC-7, Michael Sanphillipo 
wrote:
>
> I recently switched Weewx to Python3, but I notice when I run Updates on 
> my PI I see the following.
>
> sudo apt update
> Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
> Hit:2 http://weewx.com/apt/python2 squeeze InRelease   
>
> Will this cause an issue if I'm using Python 3? If so what should I change?
>

I would try the python3 version of the  'configure apt' instructions 
in http://www.weewx.com/docs/debian.htm and see if that repoints your weewx 
repo at the python3 version.

-- 
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/0549116a-9ac7-4a63-bb9c-5eb938454bdco%40googlegroups.com.


[weewx-user] PI update Weewx

2020-09-27 Thread Michael Sanphillipo
I recently switched Weewx to Python3, but I notice when I run Updates on my 
PI I see the following.

sudo apt update
Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
Hit:2 http://weewx.com/apt/python2 squeeze InRelease   

Will this cause an issue if I'm using Python 3? If so what should I change?

-- 
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/8512cca0-a1fa-4f22-9cf4-768524b1a28cn%40googlegroups.com.


Re: [weewx-user] Re: Can't get LOOP packets from WiFi logger

2020-09-27 Thread 'loonsailor' via weewx-user
Thanks for the suggestion.  I just made the change.  I'll watch for the 
next few hours and report back on results.

On Saturday, September 26, 2020 at 7:16:55 AM UTC-7 bgra...@umw.edu wrote:

> Hello,
> I have had this problem and solved it for my VPro2 by modifying the 
> vantage.py driver. It was suggested to me several years ago because I'm 
> using the RS232 interface which is designed for APRS (ham radio) reporting. 
> Not sure I understand why it works but it does for me and I need to modify 
> each new driver file (vantage.py) when I update weewx.
> I made the following modification:
>
> In vantage.py:
>
> def genLoopPackets(self):
> """Generator function that returns loop packets"""
>
> while True:
> # Get LOOP packets in big batches This is necessary because 
> there is
> # an undocumented limit to how many LOOP records you can 
> request
> # on the VP (somewhere around 220).
> for _loop_packet in self.genDavisLoopPackets(2): #[this is set 
> to 200 in vantage.py original]
> yield _loop_packet
>
> My archive time is set to 15 minutes, if this is important.
> Good luck.
> Bob
> On Friday, September 25, 2020 at 3:14:51 PM UTC-4 loonsailor wrote:
>
>> I wanted to provide a status update, and see if anybody else has any 
>> experience with the WiFiLogger that's similar to this, or has any ideas.
>>
>> Ryan, I'm having problems with the WiFiLogger2.  I'm reading it with 
>> weeWx.  There is no email address on wifilogger.net, so I don't know how 
>> to reach out the the developer directly.
>>
>> It took a while to get the parameters on the WFL right, but I got it 
>> working, mostly.  However, I still get lots of errors.  Here is the weeWx 
>> error log for the last few hours:
>>
>> Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: ip-read error: [Errno 104] Connection reset by peer
>>
>> Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #1; error: [Errno 104] Connection reset by 
>> peer
>>
>> Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #2; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #3; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 05:17:56 ubu-mini-weather weewx[198474] 
>> ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded.
>>
>> Sep 25 05:17:56 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe
>>
>> Sep 25 05:17:56 ubu-mini-weather weewx[198474] CRITICAL __main__: Caught 
>> WeeWxIOError: Max tries exceeded while getting LOOP data.
>>
>> Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: ip-read error: [Errno 104] Connection reset by peer
>>
>> Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #1; error: [Errno 104] Connection reset by 
>> peer
>>
>> Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #2; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #3; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 08:05:40 ubu-mini-weather weewx[198474] 
>> ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded.
>>
>> Sep 25 08:05:40 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe
>>
>> Sep 25 08:05:40 ubu-mini-weather weewx[198474] CRITICAL __main__: Caught 
>> WeeWxIOError: Max tries exceeded while getting LOOP data.
>>
>> Sep 25 08:06:50 ubu-mini-weather weewx[198474] INFO weewx.engine: Clock 
>> error is 0.97 seconds (positive is fast)
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: ip-read error: [Errno 104] Connection reset by peer
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #1; error: [Errno 104] Connection reset by 
>> peer
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #2; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #3; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] 
>> ERROR weewx.drivers.vantage: LOOP max tries (4) 

Re: [weewx-user] Re: Davis AirLink and PurpleAir

2020-09-27 Thread Graham Eddy
i had not thought to put the collection of AQI calculations into an extension 
to StdWXCalculate

i amend my suggested split of weewx-airlink to an ‘airlink’ data acquisition 
service providing PMx.x values, plus an ‘aqi’ extension to StdWXCalculate to 
convert PMx.x values to AQI-related values

and yes, i’d be happy to code this extension (mainly by pinching john’s code) 
if john wanted to head that direction - i’ll have to code something 
similar/simpler for myself anyway if john doesn't want to go that way (i.e. 
separate ‘aqi’ (sub-)service)

> On 27 Sep 2020, at 10:28 pm, Tom Keffer  wrote:
> 
> The "WeeWX way" is to emit what the hardware offers, then let StdWXCalculate 
> determine whether to keep it or calculate a new value in software.
> 
> Right now, it's fairly easy to extend StdWXCalculate to calculate new types 
> via the XTypes facility. Gary and I are working on a version that will make 
> it even easier.
> 
> On Sat, Sep 26, 2020 at 10:30 PM Graham Eddy  > wrote:
> i was about to pinch john’s code for the AQI side of things - i get PM2.5 
> values via gw1000 - when i see this new driver announced. (i have found 
> ecowitt’s purported 24 hour average values very unreliable - drifting, random 
> resets, etc - but the actual pm2.5 values seem fine → derive the averaged 
> values myself)
> 
> can i suggest that acquiring PMx.x values and deriving AQI values be kept as 
> separate services? the AQI service would provide AQI xtype (mainly for 
> cheetah) and convert PMx.x values in weewx packets to equivalent AQI values 
> inserted into weewx packet (this is what i was going to implement). 
> design-wise this would also allow support of AQI values derived from multiple 
> pollution types (NO, etc) as well as abstracting the pollutant monitors
> 
>> On 27 Sep 2020, at 1:43 pm, John Kline > > wrote:
>> 
>> Hi Rich,
>> 
>> I’ve created the github project here:
>> https://github.com/chaunceygardiner/weewx-airlink 
>> 
>> 
>> I haven’t had any issues with the extension, but it’s not a priority for me 
>> until more is known about the AirLink.
>> 
>> Cheers,
>> John
>> 
> 
> 
> -- 
> 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/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%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/CAPq0zEATLW%2BWMaguZvAN0VULz%3DbyZWHUO8CHq6V%3DmVhG7nE-Sg%40mail.gmail.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/5A2D0839-5245-4DC3-9642-09F80D65BF71%40gmail.com.


[weewx-user] Re: how can I correct mistakes in the database in past? how to get year.json?

2020-09-27 Thread Astrid
Sorry, I found the mistake.
It was something wrong in weewx.conf at

[[[CheetahGenerator]]] 
HTML_ROOT = public_html/json

Now it works. :)

Regards, Astrid

-- 
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/63d2a658-55d0-42de-8368-ab41514452d5o%40googlegroups.com.


[weewx-user] Re: how can I correct mistakes in the database in past? how to get year.json?

2020-09-27 Thread Astrid
The last time year.json was created was on 09.09.2020. At this time I 
started to switch to weewx 4.1.1 and integrated new highcharts skin 0.3.0 
as it has been released.

Regards, Astrid

-- 
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/e4466b10-c02b-4331-868d-67c32a75659co%40googlegroups.com.


Re: [weewx-user] Feature request for forecast extension

2020-09-27 Thread Michael Bruski
Thanks for that hint John.  It does the trick.  I guess I should have taken
a second look at the docs.

Mike

On Sat, Sep 26, 2020, 23:24 John Kline  wrote:

> 
> I don’t mind adding it; but have you tried specifying the URL in
> weewx.conf:
>
> lid=XX
> foid=XXX
> url =
> http://forecast.weather.gov/product.php?site=NWS=AFM=txt
> 
>
> If you only changed PFM to AFM, the above should work.
>
> Let me know.
>
> Cheers,
> John
>
> On Sep 26, 2020, at 4:40 PM, Michael Bruski 
> wrote:
>
> 
> Hi John,
>
> I'm trying to run my remote on a RPi4B near Galena, MD 21635.   The MDZ012
> LID covers Kent county, MD where Galena is located.
>
> I'm running WeeWX v4.1.1 and weewx-forecast-3.4.0b10.zip (after
> discovering that 3.4.0B1 wouldn't work).
>
> As a work around, I tweaked the default URLs for NWS in
> /usr/share/weewx/user/forecast.py to substitute 'AFM' for 'PFM' to get the
> Area Forecast Matrix and that is working fine.  My LID is found
> and I get the local forecast I'm looking for.   However, I may do a couple
> more deploys and it would be nice to have the ability to make this
> selection via the weewx.conf file instead of tweaking the source code.
>
> I'm considering doing the same for my home location in Carroll county MD
> because I sometimes see some not so insignificant differences between the
> MDZ005 Area Forecast Matrix and the MDZ013 Point Forecast Matrix possibly
> due to 850 ft difference in elevation.  In Maryland it seems the Area
> Forecast Matrix provides a better granularity (and better forecast) than
> the Point Forecast Matrix which has fewer locations and covers larger areas.
>
> Mike/AJ9X
>
> On Saturday, September 26, 2020 at 5:48:36 PM UTC-4 jo...@johnkline.com
> wrote:
>
>> What town are you in?  Zip code?
>>
>> From where did you get the forecast extension?
>>
>> What version of WeeWX are you running?
>>
>> On Sep 26, 2020, at 8:34 AM, Michael Bruski  wrote:
>>
>> 
>>
>> I'm a newbie to weewx and have recently added the forecast extension to
>> two weewx systems I am operating at two different locations.   The initial
>> setup and test was done at my home location.   I changed the LID/FOID for
>> location 2 after deploying it.  While checking the syslog for the remote
>> system, I found the following messages from the forecast extension:
>>
>> Sep 26 11:10:18 wstn weewx[18561] INFO user.forecast: NWSThread: NWS:
>> downloading forecast from '
>> http://forecast.weather.gov/product.php?site=NWS=PFM=txt=PHI
>> '
>> Sep 26 11:11:58 wstn weewx[18561] ERROR user.forecast: NWSThread: NWS: no
>> PFM found for MDZ012 in forecast from PHI
>>
>> I did some checking through the NWS EMWIN messages on GOES16 to see what
>> was what and see that MDZ012 is not included in the Holy Springs PFM, but,
>> it is provided in the AFM.  Would it be possible to add a key/tag to
>> weewx.conf to specify the product where my LID can be found or maybe change
>> user.forecast to check both PFM/AFM products for the specified LID?
>>
>> Thanks for this great extension and weewx!
>>
>> Mike/AJ9X
>>
>> --
>> 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/b6b535da-6144-4a81-8a20-a2ac930e68adn%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/24573746-8249-4f99-8d31-b53ac909d784n%40googlegroups.com
> 
> .
>
> --
> 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/MacwBYfTheY/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/0F4DD4F4-0F99-40F2-83D2-46412C23E385%40johnkline.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] Re: how can I correct mistakes in the database in past? how to get year.json?

2020-09-27 Thread Astrid
Hello!

I thought year.json was from weewx it self, but this was my mistake,
it comes from Hightchart-skin, which I use too (0.3).

I wait overnight, but it does not appear again. :(

Regards, Astrid

-- 
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/9277550b-ec7b-4720-a285-4d946e59e951o%40googlegroups.com.


Re: [weewx-user] how can I correct mistakes in the database in past? how to get year.json?

2020-09-27 Thread Tom Keffer
I'm not familiar with the file year.json. Where did it come from? If it
works like the rest of WeeWX reports, if you delete it, then it will be
regenerated using the current data.

On Sun, Sep 27, 2020 at 3:47 AM Astrid  wrote:

> Hello!
>
> In my database are some errors, which I
> did not recognized before.
> E.g. in June some outtemp minus values, which
> do not have been in reality.
>
> My weatherstation creates ascii-tables.
> I get the data to weewx with fileparse.
> And if computer is rebooting it
> sometimes delivers wrong data.
>
> I try to fix it. I deleted all recordes is
> table "archive" from 01.05 up to now,
> I delelte the wrong line with the wrong
> values from my ascii-table and import
> the data from 01.05 up to now again
> into the database, start weewx again
> and do wee_reports.
> But it did not solve the problem.
>
> I run this too:
> wee_database --rebuild-daily
> But problem still there.
>
> I deleted in /var/www/htdocs/weewx/json
> both json files and run wee_reports again.
> week.json is created, but not year.json.
>
> How can I create a year.json again?
>
> Regards, Astrid
>
>
> --
> 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/24b502f1-3d90-4188-97c5-4f0742d197a4o%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/CAPq0zEDWf-Pw%2BHstjd%2BMBf2fbbbMe3ag0SZAXpnAidrUtt4Vqw%40mail.gmail.com.


Re: [weewx-user] Re: Missing code for UV-sensor-debug in wmr200.py (4.1.1)

2020-09-27 Thread Tom Keffer
You would have to ask the driver's author. I suspect it's just a
belt-and-suspenders approach to making sure it has a proper value.

On Sun, Sep 27, 2020 at 12:09 AM peredst...@gmail.com <
peredstrom@gmail.com> wrote:

> Btw..
>
> Why do I need to change in two places to get debug-info in the syslog? I
> thought that the thing was to just change in the beginning of the file.
>
> First here:
>
> DEBUG_PACKETS_COOKED = 0
> # Prints raw pre-processed packets from console.
> DEBUG_PACKETS_RAW = 1
>
> Then here:
>
> global DEBUG_CONFIG_DATA
> DEBUG_CONFIG_DATA = int(stn_dict.get('debug_config_data', 0))
> global DEBUG_PACKETS_RAW
> DEBUG_PACKETS_RAW = int(stn_dict.get('debug_packets_raw', 1))
>
>
> söndag 27 september 2020 kl. 01:26:44 UTC+2 skrev tke...@gmail.com:
>
>> Thanks. Commit 995d11
>> 
>>
>> On Sat, Sep 26, 2020 at 12:04 PM peredst...@gmail.com <
>> peredst...@gmail.com> wrote:
>>
>>> This is also missing, for READS:
>>>
>>> global DEBUG_READS
>>> DEBUG_READS = int(stn_dict.get('debug_reads', 1))
>>>
>>>
>>> lördag 26 september 2020 kl. 20:44:19 UTC+2 skrev peredst...@gmail.com:
>>>
 All DEBUG_ .. = 1 to activate debug of sensor data. UV is not showing
 in syslog.
 All of the below have the global-code but UVI:

 # Prints respective packets individually.
 DEBUG_PACKETS_ARCHIVE = 1
 DEBUG_PACKETS_PRESSURE = 1
 DEBUG_PACKETS_RAIN = 1
 DEBUG_PACKETS_STATUS = 1
 DEBUG_PACKETS_TEMP = 1
 DEBUG_PACKETS_UVI = 1
 DEBUG_PACKETS_WIND = 1

 Suggested change (add):

 global DEBUG_PACKETS_UVI
 DEBUG_PACKETS_UVI = int(stn_dict.get('debug_packets_uvi', 1))

 After the change the following is added to syslog (the 255-value should
 be 0 - this was why I was debugging):

 Sep 26 17:42:15 RPi-3Bp-Arelien weewx[3863] DEBUG
 weewx.drivers.wmr200:   UV index:255

 --
>>> 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/8211e6d3-78a7-4720-8139-07cf2e7a4980n%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/1161a323-251a-4280-ae84-863235bac79cn%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/CAPq0zEDtHhZdUJ%3DVCW41Fzdgmg0hNVracXX_gpowr0iXjbQKEQ%40mail.gmail.com.


Re: [weewx-user] Re: Davis AirLink and PurpleAir

2020-09-27 Thread Tom Keffer
The "WeeWX way" is to emit what the hardware offers, then let
StdWXCalculate determine whether to keep it or calculate a new value in
software.

Right now, it's fairly easy to extend StdWXCalculate to calculate new types
via the XTypes facility. Gary and I are working on a version that will make
it even easier.

On Sat, Sep 26, 2020 at 10:30 PM Graham Eddy  wrote:

> i was about to pinch john’s code for the AQI side of things - i get PM2.5
> values via gw1000 - when i see this new driver announced. (i have found
> ecowitt’s purported 24 hour average values very unreliable - drifting,
> random resets, etc - but the actual pm2.5 values seem fine → derive the
> averaged values myself)
>
> can i suggest that acquiring PMx.x values and deriving AQI values be kept
> as separate services? the AQI service would provide AQI xtype (mainly for
> cheetah) and convert PMx.x values in weewx packets to equivalent AQI values
> inserted into weewx packet (this is what i was going to implement).
> design-wise this would also allow support of AQI values derived from
> multiple pollution types (NO, etc) as well as abstracting the pollutant
> monitors
>
> On 27 Sep 2020, at 1:43 pm, John Kline  wrote:
>
> Hi Rich,
>
> I’ve created the github project here:
> https://github.com/chaunceygardiner/weewx-airlink
>
> I haven’t had any issues with the extension, but it’s not a priority for
> me until more is known about the AirLink.
>
> Cheers,
> John
>
>
> --
> 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/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%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/CAPq0zEATLW%2BWMaguZvAN0VULz%3DbyZWHUO8CHq6V%3DmVhG7nE-Sg%40mail.gmail.com.


[weewx-user] how can I correct mistakes in the database in past? how to get year.json?

2020-09-27 Thread Astrid
Hello!

In my database are some errors, which I
did not recognized before.
E.g. in June some outtemp minus values, which
do not have been in reality.

My weatherstation creates ascii-tables.
I get the data to weewx with fileparse.
And if computer is rebooting it
sometimes delivers wrong data.

I try to fix it. I deleted all recordes is
table "archive" from 01.05 up to now,
I delelte the wrong line with the wrong
values from my ascii-table and import
the data from 01.05 up to now again
into the database, start weewx again
and do wee_reports.
But it did not solve the problem.

I run this too:
wee_database --rebuild-daily
But problem still there.

I deleted in /var/www/htdocs/weewx/json
both json files and run wee_reports again.
week.json is created, but not year.json.

How can I create a year.json again?

Regards, Astrid


-- 
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/24b502f1-3d90-4188-97c5-4f0742d197a4o%40googlegroups.com.


Re: [weewx-user] Re: Missing code for UV-sensor-debug in wmr200.py (4.1.1)

2020-09-27 Thread peredst...@gmail.com
Btw..

Why do I need to change in two places to get debug-info in the syslog? I 
thought that the thing was to just change in the beginning of the file.

First here:

DEBUG_PACKETS_COOKED = 0
# Prints raw pre-processed packets from console.
DEBUG_PACKETS_RAW = 1

Then here:

global DEBUG_CONFIG_DATA
DEBUG_CONFIG_DATA = int(stn_dict.get('debug_config_data', 0))
global DEBUG_PACKETS_RAW
DEBUG_PACKETS_RAW = int(stn_dict.get('debug_packets_raw', 1))


söndag 27 september 2020 kl. 01:26:44 UTC+2 skrev tke...@gmail.com:

> Thanks. Commit 995d11 
> 
>
> On Sat, Sep 26, 2020 at 12:04 PM peredst...@gmail.com <
> peredst...@gmail.com> wrote:
>
>> This is also missing, for READS:
>>
>> global DEBUG_READS
>> DEBUG_READS = int(stn_dict.get('debug_reads', 1))
>>
>>
>> lördag 26 september 2020 kl. 20:44:19 UTC+2 skrev peredst...@gmail.com:
>>
>>> All DEBUG_ .. = 1 to activate debug of sensor data. UV is not showing in 
>>> syslog.
>>> All of the below have the global-code but UVI:
>>>
>>> # Prints respective packets individually.
>>> DEBUG_PACKETS_ARCHIVE = 1
>>> DEBUG_PACKETS_PRESSURE = 1
>>> DEBUG_PACKETS_RAIN = 1
>>> DEBUG_PACKETS_STATUS = 1
>>> DEBUG_PACKETS_TEMP = 1
>>> DEBUG_PACKETS_UVI = 1
>>> DEBUG_PACKETS_WIND = 1
>>>
>>> Suggested change (add):
>>>
>>> global DEBUG_PACKETS_UVI
>>> DEBUG_PACKETS_UVI = int(stn_dict.get('debug_packets_uvi', 1))
>>>
>>> After the change the following is added to syslog (the 255-value should 
>>> be 0 - this was why I was debugging):
>>>
>>> Sep 26 17:42:15 RPi-3Bp-Arelien weewx[3863] DEBUG 
>>> weewx.drivers.wmr200:   UV index:255
>>>
>>> -- 
>> 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/8211e6d3-78a7-4720-8139-07cf2e7a4980n%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/1161a323-251a-4280-ae84-863235bac79cn%40googlegroups.com.


Re: [weewx-user] Re: Missing code for UV-sensor-debug in wmr200.py (4.1.1)

2020-09-27 Thread peredst...@gmail.com
Just happy to contribute to the greater good..

söndag 27 september 2020 kl. 01:26:44 UTC+2 skrev tke...@gmail.com:

> Thanks. Commit 995d11 
> 
>
> On Sat, Sep 26, 2020 at 12:04 PM peredst...@gmail.com <
> peredst...@gmail.com> wrote:
>
>> This is also missing, for READS:
>>
>> global DEBUG_READS
>> DEBUG_READS = int(stn_dict.get('debug_reads', 1))
>>
>>
>> lördag 26 september 2020 kl. 20:44:19 UTC+2 skrev peredst...@gmail.com:
>>
>>> All DEBUG_ .. = 1 to activate debug of sensor data. UV is not showing in 
>>> syslog.
>>> All of the below have the global-code but UVI:
>>>
>>> # Prints respective packets individually.
>>> DEBUG_PACKETS_ARCHIVE = 1
>>> DEBUG_PACKETS_PRESSURE = 1
>>> DEBUG_PACKETS_RAIN = 1
>>> DEBUG_PACKETS_STATUS = 1
>>> DEBUG_PACKETS_TEMP = 1
>>> DEBUG_PACKETS_UVI = 1
>>> DEBUG_PACKETS_WIND = 1
>>>
>>> Suggested change (add):
>>>
>>> global DEBUG_PACKETS_UVI
>>> DEBUG_PACKETS_UVI = int(stn_dict.get('debug_packets_uvi', 1))
>>>
>>> After the change the following is added to syslog (the 255-value should 
>>> be 0 - this was why I was debugging):
>>>
>>> Sep 26 17:42:15 RPi-3Bp-Arelien weewx[3863] DEBUG 
>>> weewx.drivers.wmr200:   UV index:255
>>>
>>> -- 
>> 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/8211e6d3-78a7-4720-8139-07cf2e7a4980n%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/dbb24257-5b2d-4035-b835-3c028d9f3c98n%40googlegroups.com.


[weewx-user] WMR200-driver reports UV-sensor value as 255 when h'FF = no sensor installed

2020-09-27 Thread Per Edström
The wmr200.py should not report h'ff as a value out of range as there is no 
value from the UV-sensor as there is no sensor installed. Alternative 
report is record out of order, sensor lost or sensor not installed.

Debug and archive log info:

Sep 27 06:00:35 RPi-3Bp-Arelien weewx[16407] DEBUG weewx.drivers.wmr200:   UV 
index:255
Sep 27 06:00:36 RPi-3Bp-Arelien weewx[16407] WARNING weewx.qc: 2020-09-27 
06:00:08 CEST (1601179208) Archive value 'UV' 255 outside limits (0.0, 6.0)

Raw data from console:

Sep 27 06:00:35 RPi-3Bp-Arelien weewx[16407] DEBUG weewx.drivers.wmr200: 
Packet raw:d2 70 07 05 1b 09 14 00 00 00 00 19 00 bb 41 00 0c 01 01 07 06 
0c 0f 60 01 86 01 ff cd 43 cd 33 0a 00 e8 00 19 14 00 00 00 00 40 1d 3c 00 
00 04 e1 00 29 5a 00 00 00 00 40 30 14 80 00 00 e9 00 15 00 00 00 0f 02 5e 
56 46 80 00 08 01 55 52 5a 80 00 01 33 00 46 00 00 00 00 00 40 0f 50 80 00 
00 00 40 25 3c 00 00 07 c5 00 23 28 00 00 50 12

Information on the D2-data:
https://www.bashewa.com/wmr200-protocol.php

*D5 UV 
*
   Byte 27: (xI) Reports value of [#ff] in history [D2] records when out of 
order, not
 installed or sensor is lost.
 (x) byte(27:H) .. unknown / always [#0] .. maybe alarm or sensor 
absent?
 (I) byte(27:L) .. UVI 0-15
 ... (0-2 low / 3-5 moderate / 6-7 high / 8-10 very high / 11+ 
extremely high)

-- 
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/20860b37-a03f-4566-aacc-d2b83f3c110co%40googlegroups.com.