[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[Karen K]

Warning: According to my experience memory cards get corrupted after some 
time of use. You may think of doing backup more often or running a second 
WeeWX on another computer.

Joe schrieb am Montag, 21. Dezember 2020 um 03:22:33 UTC+1:

> I'm curious if anyone has any suggestions on this.
>
> I had to revert back to a WEEWX backup from June of this year.  
>
> I re imaged the SD card and booted it up. It began doing its thing.
>
> I loaded the HTML and, the graph has 6 months of data not listed on the 
> graphs.
>
> Is there something I should be doing when I revert to a backup?
>
> Thanks again guys.
>

-- 
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/424091e2-9975-409f-baf2-119f9d8c5cf3n%40googlegroups.com.

[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[michael.k...@gmx.at]

If you didn't put the caurrent database, holding the values up until now, 
on the card, after reverting, that's exactly the expected behaviour.

Joe schrieb am Montag, 21. Dezember 2020 um 03:22:33 UTC+1:

> I'm curious if anyone has any suggestions on this.
>
> I had to revert back to a WEEWX backup from June of this year.  
>
> I re imaged the SD card and booted it up. It began doing its thing.
>
> I loaded the HTML and, the graph has 6 months of data not listed on the 
> graphs.
>
> Is there something I should be doing when I revert to a backup?
>
> Thanks again guys.
>

-- 
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/a27391f5-6aba-4a75-9d36-46c8f97b8085n%40googlegroups.com.

Re: [weewx-user] Best Skin for Kiosk (8 inch tablet) Mode

[Rob Cranfill]

Wow. I sent the previous message, did a little more work on the code, and 
then... my server crashed, with massive disk errors. So you can still look 
at that "live" page, but it stopped updating about 15 minutes ago. 

I guess I know what I'm doing all tomorrow, now. :-(

On Sunday, December 20, 2020 at 9:32:48 PM UTC-8 Rob Cranfill wrote:

> I won't say this is the "best", but I just wrote this (OK, I'm still 
> tweaking it) for my Raspberry Pi 7". It's a super simple example you could 
> modify to your liking.
>
> It gives my wife and I just the info we care about to gear up to go dog 
> walking. (Plus a little more)
>
> https://github.com/RobCranfill/Crandard
>
> See it in glorious action at http://robcranfill.net/weather/Crandard/
>
> Sorry, I haven't got round to packaging it in the proper way WeeWX wants, 
> so you'd have to put the files in the right place... or if anyone expresses 
> a desire, I could figure out how to do the packaging.
>
>  /r
>
> On Sunday, December 20, 2020 at 6:46:25 PM UTC-8 kb1...@gmail.com wrote:
>
>> Only take you about 30 seconds to add a refresh line in the html file
>>
>>
>> Dave-KB1PVH
>>
>>
>> Sent from my Galaxy S9
>> On Sun, Dec 20, 2020, 7:47 PM gary@gmail.com  
>> wrote:
>>
>>> It doesn't update, so not useful for a tablet running unattended.
>>>
>>> On Saturday, December 19, 2020 at 5:55:59 PM UTC-5 kb1...@gmail.com 
>>> wrote:
>>>
 Look at this one.
  http://kc1azz.ddns.net/weather/phone.html

 Dave-KB1PVH


 Sent from my Galaxy S9

 On Sat, Dec 19, 2020, 5:49 PM gary@gmail.com  
 wrote:

> What is the best skin to run unattended on an 8 inch display Android 
> tablet?
> I tried Belchertown and while it works, it is mighty small at 4+ feet.
>
> -- 
> 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/f0ad4ee2-40c9-42f3-a917-7471d8f575f8n%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/940d0c54-1529-4198-bf89-2d2b71f553ebn%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/17169cdb-1d7e-413c-a3d6-31c1bbf5b3e2n%40googlegroups.com.

Re: [weewx-user] Re: CWOP not Posting to APRSgateway, and no Indication of Error in Log

[chris]

Gary, your referring to the /var/log/messages log, correct?

Thanks,

Chris Maness KQ6UP

On 12/19/20 5:14 PM, gjr80 wrote:
To get a debug startup log edit weewx.conf, set debug = 1, save 
weewx.conf and restart WeeWX. Let WeeWX run for a number of archive 
periods (in this I want to see at least three archive periods) and 
take an extract of the log from when WeeWX was restarted through until 
the number of archive periods has elapsed. Don’t edit the log extract 
and post it here.


As I said, sometimes the clue is not in an error message or what is in 
the log, rather it can be what is not in the log. For example, if 
WeeWX is not producing archive records than the RESTful services are 
never run and consequently nothing is ever posted to CWOP.


Gary

On Sunday, 20 December 2020 at 11:08:08 UTC+10 christoph...@gmail.com 
wrote:


What is a debug startup log?  I can cat /var/log/message | grep weewx
post all relevant entries.  I have the verbose flat set.  Is that
what
you mean?  I don't see any CWOP lines in any log other than the
ones I
posted.

Thanks,

Chris KQ6UP

On 12/19/20 4:55 PM, gjr80 wrote:
> Um, you’ve effectively shown us one second of a debug startup log.
> Sometimes the clue is not an error message in the log but rather
what
> WeeWX is/is not doing and what is/is not in the log. Please post a
> debug startup log extract that shows the entire startup sequence
and
> at least 20 minutes of log.
>
> Gary
>
>

--
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/c3600e03-6dd1-47c5-aada-090c1182b99fn%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/c8a38576-0a22-270a-1bd7-0431694d44c1%40gmail.com.


OpenPGP_0x55BE65AD1B41D696.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [weewx-user] Re: Solar Radiation > Theoretical Max

[t...@tom.org]

kk, glad you corroborated my observations. I am no expert in this for sure. 
I am just tired of all of the comments I get from visitors to the website 
about how my readings exceed theoretical max. I could remove the max, but 
that doesn't seem fun.

I do not have the expertise to validate the way weewx calculates it nor am 
I even competent in Python, but for those who may, here is a link to the 
code:

https://github.com/weewx/weewx/blob/d91635f3bc429f906d1f084c6a6bc8ee09fa1a27/bin/weewx/wxformulas.py#L332



On Sunday, December 20, 2020 at 1:26:31 PM UTC-5 kk44...@gmail.com wrote:

> I found that thread interesting, so I added the column "maxSolarRad", too. 
>
> [image: dayradiation.png]
> Readings of the console and the WeatherLinkLive device are quite the same. 
> And the readings of "radiation" are higher than "maxSolarRad". The values I 
> upload to the local weather network are well in the range of other stations 
> nearby.
>
>
> Greg Troxel schrieb am Sonntag, 20. Dezember 2020 um 17:58:01 UTC+1:
>
>>
>> Greg Troxel  writes:
>>
>> > Can someone share how to add maxSolarRad (when it is in the db) to the
>> > graphs for the traditional skin? Can I graph radiation, max (observed),
>> > and theory all at once, having three?
>>
>> The answer is to just add it and label it; it comes out in green after
>> radiation in blue and max in red. Pro Tip: add it after radiation_max,
>> which is the max of local observations, and don't stick the line after
>> the radiation_max header and the 4 lines defining how max should be.
>>
>>
>> [[[dayradiation]]]
>> radiation
>> radiation_max
>> data_type = radiation
>> aggregate_type = max
>> aggregate_interval = 3600
>> label = max
>> maxSolarRad
>> label = theory
>>
>

-- 
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/8b44e185-9f77-4cfd-b024-a7df7f79b617n%40googlegroups.com.

[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[wes...@gmail.com]

running an RPI on an SSD is a bad idea as kk44 point out.  run your RPI on 
an SSD and life will be way better.

-- 
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/f1495006-31ce-4f9a-ab74-f6834d167d2cn%40googlegroups.com.

Re: [weewx-user] Re: MQTT and home-assistant

[wes...@gmail.com]

i think this is a fantastic idea. what greg is doing is awesome.  i'd 
totally use this.

-- 
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/2e50a272-0b01-428c-bb47-64a6e58b50d0n%40googlegroups.com.

Re: [weewx-user] Re: Solar Radiation > Theoretical Max

[Tom Keffer]

Well, if someone has a better source for calculating maximum solar
radiation, that matches the radiation spectrum of popular sensors, I'm all
ears.

On Mon, Dec 21, 2020 at 8:19 AM t...@tom.org  wrote:

> kk, glad you corroborated my observations. I am no expert in this for
> sure. I am just tired of all of the comments I get from visitors to the
> website about how my readings exceed theoretical max. I could remove the
> max, but that doesn't seem fun.
>
> I do not have the expertise to validate the way weewx calculates it nor am
> I even competent in Python, but for those who may, here is a link to the
> code:
>
>
> https://github.com/weewx/weewx/blob/d91635f3bc429f906d1f084c6a6bc8ee09fa1a27/bin/weewx/wxformulas.py#L332
>
>
>
> On Sunday, December 20, 2020 at 1:26:31 PM UTC-5 kk44...@gmail.com wrote:
>
>> I found that thread interesting, so I added the column "maxSolarRad",
>> too.
>>
>> [image: dayradiation.png]
>> Readings of the console and the WeatherLinkLive device are quite the
>> same. And the readings of "radiation" are higher than "maxSolarRad". The
>> values I upload to the local weather network are well in the range of other
>> stations nearby.
>>
>>
>> Greg Troxel schrieb am Sonntag, 20. Dezember 2020 um 17:58:01 UTC+1:
>>
>>>
>>> Greg Troxel  writes:
>>>
>>> > Can someone share how to add maxSolarRad (when it is in the db) to the
>>> > graphs for the traditional skin? Can I graph radiation, max
>>> (observed),
>>> > and theory all at once, having three?
>>>
>>> The answer is to just add it and label it; it comes out in green after
>>> radiation in blue and max in red. Pro Tip: add it after radiation_max,
>>> which is the max of local observations, and don't stick the line after
>>> the radiation_max header and the 4 lines defining how max should be.
>>>
>>>
>>> [[[dayradiation]]]
>>> radiation
>>> radiation_max
>>> data_type = radiation
>>> aggregate_type = max
>>> aggregate_interval = 3600
>>> label = max
>>> maxSolarRad
>>> label = theory
>>>
>> --
> 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/8b44e185-9f77-4cfd-b024-a7df7f79b617n%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/CAPq0zED5QRXgKmrSyEwBmvbFv0BY3QKy%3DbvOP5x8u%3D58eC6wwg%40mail.gmail.com.

Re: [weewx-user] Re: Solar Radiation > Theoretical Max

[Karen K]

First, I see 2 different formulas in WeeWX. Additionally there is a factor 
that can be between 0.7 and 0.91. It may be an idea to adjust those values. 
(But in the moment I found no place to put "atc" and "maxSolarRad_algo" 
into weewx.conf.

tke...@gmail.com schrieb am Montag, 21. Dezember 2020 um 19:38:30 UTC+1:

> Well, if someone has a better source for calculating maximum solar 
> radiation, that matches the radiation spectrum of popular sensors, I'm all 
> ears.
>
> On Mon, Dec 21, 2020 at 8:19 AM t...@tom.org  wrote:
>
>> kk, glad you corroborated my observations. I am no expert in this for 
>> sure. I am just tired of all of the comments I get from visitors to the 
>> website about how my readings exceed theoretical max. I could remove the 
>> max, but that doesn't seem fun.
>>
>> I do not have the expertise to validate the way weewx calculates it nor 
>> am I even competent in Python, but for those who may, here is a link to the 
>> code:
>>
>>
>> https://github.com/weewx/weewx/blob/d91635f3bc429f906d1f084c6a6bc8ee09fa1a27/bin/weewx/wxformulas.py#L332
>>
>>
>>
>> On Sunday, December 20, 2020 at 1:26:31 PM UTC-5 kk44...@gmail.com wrote:
>>
>>> I found that thread interesting, so I added the column "maxSolarRad", 
>>> too. 
>>>
>>> [image: dayradiation.png]
>>> Readings of the console and the WeatherLinkLive device are quite the 
>>> same. And the readings of "radiation" are higher than "maxSolarRad". The 
>>> values I upload to the local weather network are well in the range of other 
>>> stations nearby.
>>>
>>>
>>> Greg Troxel schrieb am Sonntag, 20. Dezember 2020 um 17:58:01 UTC+1:
>>>

 Greg Troxel  writes: 

 > Can someone share how to add maxSolarRad (when it is in the db) to 
 the 
 > graphs for the traditional skin? Can I graph radiation, max 
 (observed), 
 > and theory all at once, having three? 

 The answer is to just add it and label it; it comes out in green after 
 radiation in blue and max in red. Pro Tip: add it after radiation_max, 
 which is the max of local observations, and don't stick the line after 
 the radiation_max header and the 4 lines defining how max should be. 


 [[[dayradiation]]] 
 radiation 
 radiation_max 
 data_type = radiation 
 aggregate_type = max 
 aggregate_interval = 3600 
 label = max 
 maxSolarRad 
 label = theory 

>>> -- 
>> 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/8b44e185-9f77-4cfd-b024-a7df7f79b617n%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/bddae2eb-83d0-48f6-a4ae-7b996a49fe45n%40googlegroups.com.

Re: [weewx-user] Re: Solar Radiation > Theoretical Max

[Tom Keffer]

Selection of the algorithm is in there --- just not documented. (I often do
that with configurations that are not quite settled.)

Here's the default. It will be documented in V4.3.

[StdWXCalculate]
  [[WXXTypes]]
[[[maxSolarRad]]]
  algorithm = rs
  atc = 0.8
  nfac = 2

Adjust as you please.

-tk

On Mon, Dec 21, 2020 at 10:47 AM Karen K  wrote:

> First, I see 2 different formulas in WeeWX. Additionally there is a factor
> that can be between 0.7 and 0.91. It may be an idea to adjust those values.
> (But in the moment I found no place to put "atc" and "maxSolarRad_algo"
> into weewx.conf.
>
> tke...@gmail.com schrieb am Montag, 21. Dezember 2020 um 19:38:30 UTC+1:
>
>> Well, if someone has a better source for calculating maximum solar
>> radiation, that matches the radiation spectrum of popular sensors, I'm all
>> ears.
>>
>> On Mon, Dec 21, 2020 at 8:19 AM t...@tom.org  wrote:
>>
>>> kk, glad you corroborated my observations. I am no expert in this for
>>> sure. I am just tired of all of the comments I get from visitors to the
>>> website about how my readings exceed theoretical max. I could remove the
>>> max, but that doesn't seem fun.
>>>
>>> I do not have the expertise to validate the way weewx calculates it nor
>>> am I even competent in Python, but for those who may, here is a link to the
>>> code:
>>>
>>>
>>> https://github.com/weewx/weewx/blob/d91635f3bc429f906d1f084c6a6bc8ee09fa1a27/bin/weewx/wxformulas.py#L332
>>>
>>>
>>>
>>> On Sunday, December 20, 2020 at 1:26:31 PM UTC-5 kk44...@gmail.com
>>> wrote:
>>>
 I found that thread interesting, so I added the column "maxSolarRad",
 too.

 [image: dayradiation.png]
 Readings of the console and the WeatherLinkLive device are quite the
 same. And the readings of "radiation" are higher than "maxSolarRad". The
 values I upload to the local weather network are well in the range of other
 stations nearby.


 Greg Troxel schrieb am Sonntag, 20. Dezember 2020 um 17:58:01 UTC+1:

>
> Greg Troxel  writes:
>
> > Can someone share how to add maxSolarRad (when it is in the db) to
> the
> > graphs for the traditional skin? Can I graph radiation, max
> (observed),
> > and theory all at once, having three?
>
> The answer is to just add it and label it; it comes out in green after
> radiation in blue and max in red. Pro Tip: add it after radiation_max,
> which is the max of local observations, and don't stick the line after
> the radiation_max header and the 4 lines defining how max should be.
>
>
> [[[dayradiation]]]
> radiation
> radiation_max
> data_type = radiation
> aggregate_type = max
> aggregate_interval = 3600
> label = max
> maxSolarRad
> label = theory
>
 --
>>> 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/8b44e185-9f77-4cfd-b024-a7df7f79b617n%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/bddae2eb-83d0-48f6-a4ae-7b996a49fe45n%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/CAPq0zEAZQv_%3DvC4ric8P11FKiBX%3DG5G%2BpSM1kDAf3P89pfQDZw%40mail.gmail.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[Tom Keffer]

I have successfully run WeeWX on an SD card for over 6 years and counting
without a problem. Currently, there has been almost 2 years of continuous
uptime. http://www.threefools.org/weewx/status/index.html

You *always* want to do a backup, even for an SSD, but SD cards can provide
long life provided:

   - You get a good one. Not the one that came with the $59 IP camera you
   bought 3 years ago; and
   - You use a UPS.

-tk


On Mon, Dec 21, 2020 at 8:31 AM wes...@gmail.com  wrote:

> running an RPI on an SSD is a bad idea as kk44 point out.  run your RPI on
> an SSD and life will be way better.
>
> --
> 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/f1495006-31ce-4f9a-ab74-f6834d167d2cn%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/CAPq0zEDH%2BRUUr59CLYz0HqC2ekVB1WFNKpLNxLaWessGt0ve6Q%40mail.gmail.com.

Re: [weewx-user] Re: Solar Radiation > Theoretical Max

[Karen K]

http://www.michler-fischer.privat.t-online.de/Bulletin68_83_94.pdf
(from Switzerland, unfortunately in german)

tke...@gmail.com schrieb am Montag, 21. Dezember 2020 um 19:53:14 UTC+1:

> Selection of the algorithm is in there --- just not documented. (I often 
> do that with configurations that are not quite settled.)
>
> Here's the default. It will be documented in V4.3.
>
> [StdWXCalculate]
>   [[WXXTypes]]
> [[[maxSolarRad]]]
>   algorithm = rs
>   atc = 0.8
>   nfac = 2
>
> Adjust as you please.
>
> -tk
>
> On Mon, Dec 21, 2020 at 10:47 AM Karen K  wrote:
>
>> First, I see 2 different formulas in WeeWX. Additionally there is a 
>> factor that can be between 0.7 and 0.91. It may be an idea to adjust those 
>> values. (But in the moment I found no place to put "atc" and 
>> "maxSolarRad_algo" into weewx.conf.
>>
>> tke...@gmail.com schrieb am Montag, 21. Dezember 2020 um 19:38:30 UTC+1:
>>
>>> Well, if someone has a better source for calculating maximum solar 
>>> radiation, that matches the radiation spectrum of popular sensors, I'm all 
>>> ears.
>>>
>>> On Mon, Dec 21, 2020 at 8:19 AM t...@tom.org  wrote:
>>>
 kk, glad you corroborated my observations. I am no expert in this for 
 sure. I am just tired of all of the comments I get from visitors to the 
 website about how my readings exceed theoretical max. I could remove the 
 max, but that doesn't seem fun.

 I do not have the expertise to validate the way weewx calculates it nor 
 am I even competent in Python, but for those who may, here is a link to 
 the 
 code:


 https://github.com/weewx/weewx/blob/d91635f3bc429f906d1f084c6a6bc8ee09fa1a27/bin/weewx/wxformulas.py#L332



 On Sunday, December 20, 2020 at 1:26:31 PM UTC-5 kk44...@gmail.com 
 wrote:

> I found that thread interesting, so I added the column "maxSolarRad", 
> too. 
>
> [image: dayradiation.png]
> Readings of the console and the WeatherLinkLive device are quite the 
> same. And the readings of "radiation" are higher than "maxSolarRad". The 
> values I upload to the local weather network are well in the range of 
> other 
> stations nearby.
>
>
> Greg Troxel schrieb am Sonntag, 20. Dezember 2020 um 17:58:01 UTC+1:
>
>>
>> Greg Troxel  writes: 
>>
>> > Can someone share how to add maxSolarRad (when it is in the db) to 
>> the 
>> > graphs for the traditional skin? Can I graph radiation, max 
>> (observed), 
>> > and theory all at once, having three? 
>>
>> The answer is to just add it and label it; it comes out in green 
>> after 
>> radiation in blue and max in red. Pro Tip: add it after 
>> radiation_max, 
>> which is the max of local observations, and don't stick the line 
>> after 
>> the radiation_max header and the 4 lines defining how max should be. 
>>
>>
>> [[[dayradiation]]] 
>> radiation 
>> radiation_max 
>> data_type = radiation 
>> aggregate_type = max 
>> aggregate_interval = 3600 
>> label = max 
>> maxSolarRad 
>> label = theory 
>>
> -- 
 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/8b44e185-9f77-4cfd-b024-a7df7f79b617n%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/bddae2eb-83d0-48f6-a4ae-7b996a49fe45n%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/e24504ba-65bb-402c-b12c-e3a10eed5429n%40googlegroups.com.

Re: [weewx-user] Re: Solar Radiation > Theoretical Max

[moth...@gmail.com]

These are the mine measurements in the Netherlands today 21-12-2020.
Ton

Op maandag 21 december 2020 om 20:24:13 UTC+1 schreef kk44...@gmail.com:

> http://www.michler-fischer.privat.t-online.de/Bulletin68_83_94.pdf
> (from Switzerland, unfortunately in german)
>
> tke...@gmail.com schrieb am Montag, 21. Dezember 2020 um 19:53:14 UTC+1:
>
>> Selection of the algorithm is in there --- just not documented. (I often 
>> do that with configurations that are not quite settled.)
>>
>> Here's the default. It will be documented in V4.3.
>>
>> [StdWXCalculate]
>>   [[WXXTypes]]
>> [[[maxSolarRad]]]
>>   algorithm = rs
>>   atc = 0.8
>>   nfac = 2
>>
>> Adjust as you please.
>>
>> -tk
>>
>> On Mon, Dec 21, 2020 at 10:47 AM Karen K  wrote:
>>
>>> First, I see 2 different formulas in WeeWX. Additionally there is a 
>>> factor that can be between 0.7 and 0.91. It may be an idea to adjust those 
>>> values. (But in the moment I found no place to put "atc" and 
>>> "maxSolarRad_algo" into weewx.conf.
>>>
>>> tke...@gmail.com schrieb am Montag, 21. Dezember 2020 um 19:38:30 UTC+1:
>>>
 Well, if someone has a better source for calculating maximum solar 
 radiation, that matches the radiation spectrum of popular sensors, I'm all 
 ears.

 On Mon, Dec 21, 2020 at 8:19 AM t...@tom.org  wrote:

> kk, glad you corroborated my observations. I am no expert in this for 
> sure. I am just tired of all of the comments I get from visitors to the 
> website about how my readings exceed theoretical max. I could remove the 
> max, but that doesn't seem fun.
>
> I do not have the expertise to validate the way weewx calculates it 
> nor am I even competent in Python, but for those who may, here is a link 
> to 
> the code:
>
>
> https://github.com/weewx/weewx/blob/d91635f3bc429f906d1f084c6a6bc8ee09fa1a27/bin/weewx/wxformulas.py#L332
>
>
>
> On Sunday, December 20, 2020 at 1:26:31 PM UTC-5 kk44...@gmail.com 
> wrote:
>
>> I found that thread interesting, so I added the column "maxSolarRad", 
>> too. 
>>
>> [image: dayradiation.png]
>> Readings of the console and the WeatherLinkLive device are quite the 
>> same. And the readings of "radiation" are higher than "maxSolarRad". The 
>> values I upload to the local weather network are well in the range of 
>> other 
>> stations nearby.
>>
>>
>> Greg Troxel schrieb am Sonntag, 20. Dezember 2020 um 17:58:01 UTC+1:
>>
>>>
>>> Greg Troxel  writes: 
>>>
>>> > Can someone share how to add maxSolarRad (when it is in the db) to 
>>> the 
>>> > graphs for the traditional skin? Can I graph radiation, max 
>>> (observed), 
>>> > and theory all at once, having three? 
>>>
>>> The answer is to just add it and label it; it comes out in green 
>>> after 
>>> radiation in blue and max in red. Pro Tip: add it after 
>>> radiation_max, 
>>> which is the max of local observations, and don't stick the line 
>>> after 
>>> the radiation_max header and the 4 lines defining how max should be. 
>>>
>>>
>>> [[[dayradiation]]] 
>>> radiation 
>>> radiation_max 
>>> data_type = radiation 
>>> aggregate_type = max 
>>> aggregate_interval = 3600 
>>> label = max 
>>> maxSolarRad 
>>> label = theory 
>>>
>> -- 
> 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/8b44e185-9f77-4cfd-b024-a7df7f79b617n%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/bddae2eb-83d0-48f6-a4ae-7b996a49fe45n%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/1b50e5cc-db3b-4352-8707-1436508561b8n%40googlegroups.com.

[weewx-user] Build of weewx on M1 Mac

[geoffs...@gmail.com]

Setup pyenv using Homebrew M1 experimental version and then installed 
python 3.9.1
Then installed all necessary libraries. Needed to use homebrew to install 
FreeType and libjpeg to get a working Pillow install.

can be started as a daemon using 

cd /Users/Shared/weewx
python3 ./bin/weewxd weewx.conf -d
Runs as native on M1 ARM64 arch
*weewx[1269] INFO __main__: Initializing weewx version 4.2.0*
*weewx[1269] INFO __main__: Using Python 3.9.1 (default, Dec 21 2020, 
07:33:29) *
*[Clang 12.0.0 (clang-1200.0.32.28)]*
*weewx[1269] INFO __main__: Platform macOS-11.1-arm64-arm-64bit*
*weewx[1269] INFO __main__: Locale is 'en_US.UTF-8'*
*weewx[1269] INFO __main__: PID file is /var/run/weewx.pid*
*weewx[1288] INFO __main__: Using configuration file weewx.conf*
*weewx[1288] INFO __main__: Debug is 0*

 
Still will not start from launchctl
get:

Dec 21 10:58:10 Mac-mini com.apple.xpc.launchd[1] (com.weewx.weewxd[893]): 
Service could not initialize: 20C69: xpcproxy + 23696 
[839][D05D0576-CE1E-3530-B74C-0EB266FFBFDD]: 0x2

Dec 21 10:58:10 Mac-mini com.apple.xpc.launchd[1] (com.weewx.weewxd[893]): 
Service exited with abnormal code: 78

Any ideas on how to set up launchctl start to work?

-- 
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/fdbf0065-499c-4b9b-bca2-4156ba76ea31n%40googlegroups.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[vince]

On Monday, December 21, 2020 at 11:00:40 AM UTC-8 Tom Keffer wrote:
You *always* want to do a backup, even for an SSD, but SD cards can provide 
long life provided:

   - You get a good one. Not the one that came with the $59 IP camera you 
   bought 3 years ago; and
   - You use a UPS.



...and adding on - ALWAYS use a quality power supply when using a pi, as 
poor power is the quickest way to get a SD card to fail, 'especially' on a 
pi that is not a pi3 or pi4 model.   Check your syslogs for evidence of 
periodic low power as these things might be transient.  For example - I'm 
driving a pi3 attached to a 10" display that came with its own power supply 
that can feed the pi.  All it's doing is running a browser with an always 
on dashboard, but every time weewx runs its archive interval I get a 
low-power set of messages in syslog saying that even that is pushing the 
borderline power a little too far.  It's very repeatable.  The pi are 
'very' sensitive to borderline power being provided...


-- 
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/c41dd291-6aa7-4029-8ce1-da7df3f0c971n%40googlegroups.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[chris]

I want to piggy back on this.  Is it feasible to do the old dump/restore 
to a NFS mount on a Pi4?  I used to do this on FreeBSD and it worked 
really nicely -- even from a live system.


Thanks, Chris KQ6UP

On 12/21/20 11:59 AM, vince wrote:

On Monday, December 21, 2020 at 11:00:40 AM UTC-8 Tom Keffer wrote:
You /always/ want to do a backup, even for an SSD, but SD cards can 
provide long life provided:


  * You get a good one. Not the one that came with the $59 IP camera
you bought 3 years ago; and
  * You use a UPS.



...and adding on - ALWAYS use a quality power supply when using a pi, 
as poor power is the quickest way to get a SD card to fail, 
'especially' on a pi that is not a pi3 or pi4 model.   Check your 
syslogs for evidence of periodic low power as these things might be 
transient.  For example - I'm driving a pi3 attached to a 10" display 
that came with its own power supply that can feed the pi.  All it's 
doing is running a browser with an always on dashboard, but every time 
weewx runs its archive interval I get a low-power set of messages in 
syslog saying that even that is pushing the borderline power a little 
too far.  It's very repeatable.  The pi are 'very' sensitive to 
borderline power being provided...



--
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/c41dd291-6aa7-4029-8ce1-da7df3f0c971n%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/c5fbe954-c1f4-770a-2375-99b30e504650%40gmail.com.


OpenPGP_0x55BE65AD1B41D696.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[vince]

On Monday, December 21, 2020 at 12:18:02 PM UTC-8 ch...@chrismaness.com 
wrote:

> I want to piggy back on this.  Is it feasible to do the old dump/restore 
> to a NFS mount on a Pi4?  I used to do this on FreeBSD and it worked really 
> nicely -- even from a live system.
>
>
Weewx doesn't care either way.
The operating system doesn't care either way.
So of course yes it is feasible.

That said, sqlite3 used to have some wording in its docs saying they don't 
guarantee data integrity if you have the db network mounted, although most 
people tend to ignore that caveat.Lots of people NFS/SMB mount sqlite4 
databases. FWIW, I do it at $job with db with over 20M records, although 
once the db is generated batch by some python magic it's essentially 
read-only so it's not quite an apples-and-apples comparison to weewx 
writing every few minutes to the db.


-- 
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/af8bb4e6-a786-4c44-a2bf-08f4387b51d4n%40googlegroups.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[vince]

(sigh - sqlite3 db in my previous post, of course...)

-- 
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/282b27c5-f9ef-41f1-a08d-61ecdda3ce60n%40googlegroups.com.

Re: [weewx-user] Best Skin for Kiosk (8 inch tablet) Mode

[Rob Cranfill]

(Sorry to hog the conversation, and I'm sure no-one cares, but just in case 
anyone does, the above website is back online. After a quick 'chkdsk', all 
was well!)

On Monday, December 21, 2020 at 1:29:18 AM UTC-8 Rob Cranfill wrote:

> Wow. I sent the previous message, did a little more work on the code, and 
> then... my server crashed, with massive disk errors. So you can still look 
> at that "live" page, but it stopped updating about 15 minutes ago. 
>
> I guess I know what I'm doing all tomorrow, now. :-(
>
> On Sunday, December 20, 2020 at 9:32:48 PM UTC-8 Rob Cranfill wrote:
>
>> I won't say this is the "best", but I just wrote this (OK, I'm still 
>> tweaking it) for my Raspberry Pi 7". It's a super simple example you could 
>> modify to your liking.
>>
>> It gives my wife and I just the info we care about to gear up to go dog 
>> walking. (Plus a little more)
>>
>> https://github.com/RobCranfill/Crandard
>>
>> See it in glorious action at http://robcranfill.net/weather/Crandard/
>>
>> Sorry, I haven't got round to packaging it in the proper way WeeWX wants, 
>> so you'd have to put the files in the right place... or if anyone expresses 
>> a desire, I could figure out how to do the packaging.
>>
>>  /r
>>
>> On Sunday, December 20, 2020 at 6:46:25 PM UTC-8 kb1...@gmail.com wrote:
>>
>>> Only take you about 30 seconds to add a refresh line in the html file
>>>
>>>
>>> Dave-KB1PVH
>>>
>>>
>>> Sent from my Galaxy S9
>>> On Sun, Dec 20, 2020, 7:47 PM gary@gmail.com  
>>> wrote:
>>>
 It doesn't update, so not useful for a tablet running unattended.

 On Saturday, December 19, 2020 at 5:55:59 PM UTC-5 kb1...@gmail.com 
 wrote:

> Look at this one.
>  http://kc1azz.ddns.net/weather/phone.html
>
> Dave-KB1PVH
>
>
> Sent from my Galaxy S9
>
> On Sat, Dec 19, 2020, 5:49 PM gary@gmail.com  
> wrote:
>
>> What is the best skin to run unattended on an 8 inch display Android 
>> tablet?
>> I tried Belchertown and while it works, it is mighty small at 4+ feet.
>>
>> -- 
>> 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/f0ad4ee2-40c9-42f3-a917-7471d8f575f8n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/940d0c54-1529-4198-bf89-2d2b71f553ebn%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/d1f90bcf-e225-4c3c-bd7a-f60cd14c5e74n%40googlegroups.com.

[weewx-user] Belchertown skin with MQTT not working?

[Mark Jenks]

What am I missing?  I can't seem to get this to work.  The website won't 
connect to mqtt to get the data.  Even though I can see it when I watch the 
topic.

Failed connecting to the weather station. Please try again later!  

[StdRESTful]
[[MQTT]]
server_url = mqtt://weather:passwordx@localhost:1883/
topic = "weather/weewx"
unit_system = US
binding = archive, loop
aggregation = aggregate

[[Belchertown]]
skin = Belchertown
#HTML_ROOT = /var/www/html/weewx/belchertown
[[[Extras]]]
mqtt_websockets_enabled = 1
mqtt_websockets_host = "127.0.0.1"
mqtt_websockets_port = 1883
mqtt_websockets_topic = "weather/weewx/loop"

I see data when I run this, so it's getting populated.
#mosquitto_sub -h localhost -t weather/weewx/loop

-- 
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/594e29e7-6a7e-4b32-9f00-4e8e668d3de2n%40googlegroups.com.

Re: [weewx-user] Belchertown skin with MQTT not working?

[Greg Troxel]

Mark Jenks  writes:

> Failed connecting to the weather station. Please try again later!  
>
> [StdRESTful]
> [[MQTT]]
> server_url = mqtt://weather:passwordx@localhost:1883/
> topic = "weather/weewx"
> unit_system = US
> binding = archive, loop
> aggregation = aggregate
>
> [[Belchertown]]
> skin = Belchertown
> #HTML_ROOT = /var/www/html/weewx/belchertown
> [[[Extras]]]
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = "127.0.0.1"
> mqtt_websockets_port = 1883
> mqtt_websockets_topic = "weather/weewx/loop"
>
> I see data when I run this, so it's getting populated.
> #mosquitto_sub -h localhost -t weather/weewx/loop

I have not set this up, but I think what you are missing is that 1883 is
MQTT and you need to set up "mqtt over websockets" in mosquitto and
point the skin at that.And if you are using a browswer on the same
machine as the broker, ok, but really the mqtt_websockets_host needs to
be the global name and reachable.

-- 
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/rmio8imwxg5.fsf%40s1.lexort.com.


signature.asc
Description: PGP signature

Re: [weewx-user] Belchertown skin with MQTT not working?

[Mark Jenks]

I guess I should have included this...

# more mosquitto.conf
persistence false

# mqtt
listener 1883 127.0.0.1
protocol mqtt

# websockets
listener 9001 127.0.0.1
protocol websockets


On Monday, December 21, 2020 at 5:28:48 PM UTC-6 Greg Troxel wrote:

>
> Mark Jenks  writes:
>
> > Failed connecting to the weather station. Please try again later! 
> >
> > [StdRESTful]
> > [[MQTT]]
> > server_url = mqtt://weather:passwordx@localhost:1883/
> > topic = "weather/weewx"
> > unit_system = US
> > binding = archive, loop
> > aggregation = aggregate
> >
> > [[Belchertown]]
> > skin = Belchertown
> > # HTML_ROOT = /var/www/html/weewx/belchertown
> > [[[Extras]]]
> > mqtt_websockets_enabled = 1
> > mqtt_websockets_host = "127.0.0.1"
> > mqtt_websockets_port = 1883
> > mqtt_websockets_topic = "weather/weewx/loop"
> >
> > I see data when I run this, so it's getting populated.
> > #mosquitto_sub -h localhost -t weather/weewx/loop
>
> I have not set this up, but I think what you are missing is that 1883 is
> MQTT and you need to set up "mqtt over websockets" in mosquitto and
> point the skin at that. And if you are using a browswer on the same
> machine as the broker, ok, but really the mqtt_websockets_host needs to
> be the global name and reachable.
>

-- 
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/740e546b-0acb-4afc-ba84-6bd1a6f7c8een%40googlegroups.com.

Re: [weewx-user] [[Calculations]] on archive record not loop packet?

[Tom Keffer]

Hi, Graham

Seems like a reasonable thing to do but, no, there is no way at this point.
Perhaps the [[Calculations]] section should be expanded to:

[StdWXCalculate]
  [[Calculations]]
aqi = software, record

That is, it takes an optional second positional parameter that can be one
of 'loop', 'record', or 'both'. The default would be 'both'.



On Fri, Dec 18, 2020 at 7:10 AM Graham Eddy  wrote:

> my reading of the 4.3.0 source is that [[Calculations]] calculates the
> specified xtypes on each loop packet. is there a simple way now, or is it
> in plan, to be able to have them calculated for archive records only?
>
> i do not want to calculate AQI from averaged pollutant values except when
> the averages are updated, which for me is at the end of each archive
> interval. i have written a data service to call the xtypes each archive
> record, but i would prefer StdWXCalculate handled it for me with ‘=
> software’ declarations
>
> --
> 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/D43D0E70-13A6-4B6B-905C-F7597C97DE0A%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/CAPq0zEARNBu0cB18MDYiVc0101vw4W9PEcutpJ3ZFvGmYvt8GQ%40mail.gmail.com.

Re: [weewx-user] Belchertown skin with MQTT not working?

[vince]

Assuming you have the MQTT broker side set up correctly

With 90% certainty 'failure to connect' is because you are trying to 
connect to localhost (or 127.0.0.1) and rather than the ip address or FQDN 
of the webserver.   Belchertown works by establishing a connection from 
your browser to the remote websockets host, so you need to use the ip 
address of your MQTT listener there.

The javascript code that Belchertown runs in your browser can't connect to 
itself (127.0.0.1), it needs to connect to the server with the 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/7500b6be-e1bd-4ea9-9fcf-01698fd1241bn%40googlegroups.com.

Re: [weewx-user] Belchertown skin with MQTT not working?

[vince]

Old thread where I battled the same thing a year ago, with solution...

https://groups.google.com/g/weewx-user/c/w8aSTyX1UVo/m/eU52eJReCAAJ

-- 
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/9802c069-1c5b-437c-9130-42e2f97ab1a8n%40googlegroups.com.

Re: [weewx-user] [[Calculations]] on archive record not loop packet?

[Graham Eddy]

good idea. i'll code & submit that

On Tue, 22 Dec 2020, 11:06 am Tom Keffer,  wrote:

> Hi, Graham
>
> Seems like a reasonable thing to do but, no, there is no way at this
> point. Perhaps the [[Calculations]] section should be expanded to:
>
> [StdWXCalculate]
>   [[Calculations]]
> aqi = software, record
>
> That is, it takes an optional second positional parameter that can be one
> of 'loop', 'record', or 'both'. The default would be 'both'.
>
>
>
> On Fri, Dec 18, 2020 at 7:10 AM Graham Eddy  wrote:
>
>> my reading of the 4.3.0 source is that [[Calculations]] calculates the
>> specified xtypes on each loop packet. is there a simple way now, or is it
>> in plan, to be able to have them calculated for archive records only?
>>
>> i do not want to calculate AQI from averaged pollutant values except when
>> the averages are updated, which for me is at the end of each archive
>> interval. i have written a data service to call the xtypes each archive
>> record, but i would prefer StdWXCalculate handled it for me with ‘=
>> software’ declarations
>>
>> --
>> 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/D43D0E70-13A6-4B6B-905C-F7597C97DE0A%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/CAPq0zEARNBu0cB18MDYiVc0101vw4W9PEcutpJ3ZFvGmYvt8GQ%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/CAKwQt_ptTtJBJdHAdSZpL6ayy9OF23mcrORcS%3DdO965nq5NE%2Bg%40mail.gmail.com.

Re: [weewx-user] Re: belchertown question

[Neville Davis]

Thanks for that info, just tried again, still the sameI'm blaming covid 
:)

Neville

On Monday, December 21, 2020 at 1:51:05 AM UTC+10 sali...@gmail.com wrote:

> hello Neville
>
> Me, I was waiting for " 7 days " after inscription.
>
> Patrick from France
> Le 19/12/2020 à 07:50, Neville Davis a écrit :
>
> Pat 
>
> I am about to go to 1.2, have configured weewx and pwsweather receiving 
> data and my station is now considered active and appears on the main map.
> I am now attempting to link AerisWeather and pwsweather but the create 
> Aerisweather contributor account page will not do the link..it keeps 
> reporting "something went wrong please try submitting again". This has been 
> happening for several days. Are you aware of any problems with this 
> procedure?
>
>
> Neville
>
> On Tuesday, July 21, 2020 at 11:00:32 AM UTC+10 Pat wrote:
>
>> Yep! Aeris is only working in the development version right now. I'm 
>> working on final clean up of the skin and will be publishing the 
>> development as a release soon. 
>>
>>
>> On Monday, July 20, 2020 at 8:32:14 PM UTC-4, Jamie Stephens wrote: 
>>>
>>> do i need to be running the development version to use the forecast with 
>>> aeris? go easy on me i'm still learning linux and weewx 
>>>
>>>
>>> ERROR weewx.reportengine:   Warning: Error downloading 
>>> forecast data. Check the URL in your configuration and try again. You are 
>>> trying to use URL: 
>>> https://api.darksky.net/forecast//35.17491,-81.02416?units=auto&lang=en, 
>>> and the error is: HTTP Error 400: Bad Request
>>>
>>>
>>>
>>>   enable = false
>>> [[Belchertown]]
>>> skin = Belchertown
>>> HTML_ROOT = /var/www/html
>>> [[[Extras]]]
>>> forecast_enabled = 1
>>> forecast_api_id = "removed"
>>> forecast_api_secret = "removed"
>>>
>> -- 
> 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/00a80cc9-4b6d-4174-beda-451ef1ae7e21n%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/a8a7c0fd-301c-4827-915f-bc772293f742n%40googlegroups.com.

[weewx-user] how to archive (write into the DB) unmapped GW1000 API sensor fields to unused database fields in the extended schema

[Rainer Lang]

I have several sensors which in my observation do not have a counterpart 
in the extended weewx database schema.


But I still want them stored in the weewx database and have them and 
their history displayed in the web interface under http://IP-address/weewx


E.g. there seems to be only one (1) field for PM2.5 sensors, however 
I've got two of the WH41 sensors and the GW1000 provides values for both.
I already managed to get one of them displayed in the current conditions 
and daily chart page (and also making them show on the weekly, monthly, 
yearly pages is now just a matter a


I suspect that the second simply gets lost as there is no standard field 
in the database to accommodate them.


In a post in the WXforum Gary mentions several approaches how to store 
("archive" in weewx terminology) such sensor values ("observations") in 
the weewx database.

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

"So in summary the following approaches (in order of complexity) are 
available:

1. utilise existing but unused database fields
2. use a customised database schema by adding to the existing schema
3. use a customised database schema by creating a new schema
4. use a second database"

I want to go for number 1 but didn't find instructions how (and where) 
to do so.


Can anyone provide guidance here please ?

Thanks and regards

Rainer

--
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/bf603cb8-33e7-208d-e88c-41a3395e475c%40gmail.com.

[weewx-user] Re: how to archive (write into the DB) unmapped GW1000 API sensor fields to unused database fields in the extended schema

[gjr80]

Rainer,

There are a few approaches that would solve you problem. You could use the 
*StdCalibrate* service to simply assign your existing sensor data to a 
another field or if you needed to do something beyond the limited 
capabilities of the *StdCalibrate* service could write your own custom 
service to do what you need. The other alternative for data that comes from 
a driver with a sensor/field map is to simply change the sensor/field map 
so that the driver places the data concerned into the field you wish to use 
right from the start.

Please note, in the following examples I have used *extraTemp2* as the 
field to be recycled, this is a poor choice for a couple of reasons; 
firstly it is quite possible a GW1000 user would want to use *extraTemp2* 
for additional temperature sensors. Secondly, *extraTemp2* normally holds 
temperature data and we will now be storing non-temperature data in the 
field, better to use a field that stores the same type of data if possible 
(more precisely the same unit type, eg pressure, concentration, speed etc). 
In this case the use of WeeWX field *no2* or *pm1_0* may have been better.

In your case I would customise the GW1000 driver field map. In this example 
let's assume you want to store your second PM2.5 sensor in WeeWX field 
*extraTemp2* and your GW1000 is emitting data from your second PM2.5 sensor 
in field *pm25_2*. In order to change the sensor map for the GW1000 we need 
to know two things, what field we are mapping from and what field we are 
mapping to. We know we are mapping to *extraTemp2* but we are not actually 
mapping from *pm25_2*, we are actually mapping from GW1000 internal field 
*pm252* (in many cases the internal GW1000 field is the same as the field 
name that appears in the loop packet but some are different for a number of 
reasons that I will not go into here). You will find details of the GW1000 
driver default field map and internal field names in the GW1000 driver Field 
map wiki entry . If 
we want to alter just a small number of field map entries we can do so 
using the *[[field_map_extensions]]* stanza (if we wanted to re-define the 
entire field map we would use the *[[field_map]]* stanza) under *[GW1000]* 
in *weewx.conf* as follows:

[GW1000]

[[field_map_extensions]]
extraTemp2 = pm252

There is one other step you will need to follow and that is to ensure that 
your 'recycled' field is set to the appropriate unit group. All fields in 
the WeeWX database schema are assigned to a unit group, that way WeeWX 
knows the data in, for example, WeeWX field *outTemp* is a temperature and 
not a pressure. In this case, we have used *extraTemp2* and by default 
WeeWX will treat any data in that field as temperature. We need to change 
that, this can be done in a number of ways but the simplest is to simply 
assign the appropriate unit group in the file *extensions.py *(
*extensions.py* is located in */home/weewx/bin/user* or 
*/usr/share/weewx/user* depending on how you installed WeeWX). In this case 
edit *extensions.py* and add the following lines to the bottom of the file:

import weewx.units
weewx.units.obs_group_dict['extraTemp2'] = 'group_concentration'

In this case we have re-assigned field *extraTemp2* to belong to the unit 
group *group_concentration* (the WeeWX unit group used for concentrations). 
A similar but slightly different approach is covered in the Assigning a 
unit group  
section in the Customization Guide .

Note the *extensions.py* modification was necessary because the destination 
field and and source data are of different unit groups, if they were the 
same then there is no need to change any unit groups.

Save *weewx.conf* and *extensions.py* and restart WeeWX and the PM2.5 data 
from the second sensor will appear in field *extraTemp2* in loop packets 
emitted by the GW1000 driver. WeeWX will accumulate this loop data and 
*extraTemp2* will be included in archive records synthesised by WeeWX. You 
can then use *extraTemp2* in tags in WeeWX report templates.

That covers the GW1000 field map approach. For the sake of completeness I 
will cover the *StdCalibrate* approach as well. 

To achieve the same result with the *StdCalibrate* service we add an entry 
under *[StdCalibrate] [[Corrections]]* in *weewx.conf*. In this case we 
would use:

[StdCalibrate]

[[Corrections]]

extraTemp2 = pm25_2

Note that in this case we used field *pm25_2* as we are actually using the 
field from the loop packet and archive record rather than an internal field 
in the GW1000 driver.

You would also need to make the same addition to *extensions.py* to deal 
with the units as was done with the GW1000 field map example above.

Gary
On Tuesday, 22 December 2020 at 14:44:50 UTC+10 lang@googlemail.com 
wrote:

> I have several sen

[weewx-user] Re: how to archive (write into the DB) unmapped GW1000 API sensor fields to unused database fields in the extended schema

[gjr80]

One thing I forgot, a side effect of the *StdCalibrate* approach is that 
loop packets and archive records will contain both fields *pm25_2* and 
*extraTemp2* and they will contain the same data. The GW1000 field map 
approach will result in *extraTemp2* but not *pm25_2* appearing in loop 
packets and archive records. Having both fields appear is not a problem as 
*pm25_2* is essentially ignored as it does not appear in the database 
schema.

Gary

On Tuesday, 22 December 2020 at 16:06:11 UTC+10 gjr80 wrote:

> Rainer,
>
> There are a few approaches that would solve you problem. You could use the 
> *StdCalibrate* service to simply assign your existing sensor data to a 
> another field or if you needed to do something beyond the limited 
> capabilities of the *StdCalibrate* service could write your own custom 
> service to do what you need. The other alternative for data that comes from 
> a driver with a sensor/field map is to simply change the sensor/field map 
> so that the driver places the data concerned into the field you wish to use 
> right from the start.
>
> Please note, in the following examples I have used *extraTemp2* as the 
> field to be recycled, this is a poor choice for a couple of reasons; 
> firstly it is quite possible a GW1000 user would want to use *extraTemp2* 
> for additional temperature sensors. Secondly, *extraTemp2* normally holds 
> temperature data and we will now be storing non-temperature data in the 
> field, better to use a field that stores the same type of data if possible 
> (more precisely the same unit type, eg pressure, concentration, speed etc). 
> In this case the use of WeeWX field *no2* or *pm1_0* may have been better.
>
> In your case I would customise the GW1000 driver field map. In this 
> example let's assume you want to store your second PM2.5 sensor in WeeWX 
> field *extraTemp2* and your GW1000 is emitting data from your second 
> PM2.5 sensor in field *pm25_2*. In order to change the sensor map for the 
> GW1000 we need to know two things, what field we are mapping from and what 
> field we are mapping to. We know we are mapping to *extraTemp2* but we 
> are not actually mapping from *pm25_2*, we are actually mapping from 
> GW1000 internal field *pm252* (in many cases the internal GW1000 field is 
> the same as the field name that appears in the loop packet but some are 
> different for a number of reasons that I will not go into here). You will 
> find details of the GW1000 driver default field map and internal field 
> names in the GW1000 driver Field map wiki entry 
> . If we want to 
> alter just a small number of field map entries we can do so using the 
> *[[field_map_extensions]]* stanza (if we wanted to re-define the entire 
> field map we would use the *[[field_map]]* stanza) under *[GW1000]* in 
> *weewx.conf* as follows:
>
> [GW1000]
> 
> [[field_map_extensions]]
> extraTemp2 = pm252
>
> There is one other step you will need to follow and that is to ensure that 
> your 'recycled' field is set to the appropriate unit group. All fields in 
> the WeeWX database schema are assigned to a unit group, that way WeeWX 
> knows the data in, for example, WeeWX field *outTemp* is a temperature 
> and not a pressure. In this case, we have used *extraTemp2* and by 
> default WeeWX will treat any data in that field as temperature. We need to 
> change that, this can be done in a number of ways but the simplest is to 
> simply assign the appropriate unit group in the file *extensions.py *(
> *extensions.py* is located in */home/weewx/bin/user* or 
> */usr/share/weewx/user* depending on how you installed WeeWX). In this 
> case edit *extensions.py* and add the following lines to the bottom of 
> the file:
>
> import weewx.units
> weewx.units.obs_group_dict['extraTemp2'] = 'group_concentration'
>
> In this case we have re-assigned field *extraTemp2* to belong to the unit 
> group *group_concentration* (the WeeWX unit group used for 
> concentrations). A similar but slightly different approach is covered in 
> the Assigning a unit group 
>  section in 
> the Customization Guide .
>
> Note the *extensions.py* modification was necessary because the 
> destination field and and source data are of different unit groups, if they 
> were the same then there is no need to change any unit groups.
>
> Save *weewx.conf* and *extensions.py* and restart WeeWX and the PM2.5 
> data from the second sensor will appear in field *extraTemp2* in loop 
> packets emitted by the GW1000 driver. WeeWX will accumulate this loop data 
> and *extraTemp2* will be included in archive records synthesised by 
> WeeWX. You can then use *extraTemp2* in tags in WeeWX report templates.
>
> That covers the GW1000 field map approach. For the sake of completeness I 
> will cover the *StdCalibrate* approach as well. 
>
> To ac