[weewx-user] Re: cmon - Extension / cpu_temp missing on raspberry

[Dr__Bob]

In the file cmon.py, there is a check on a directory (tdir) and a check on 
a specific file (tfile).  Apparently on some unices, the directory tdir 
contains a file with the cpu temp.  On raspberries, the directory exists, 
but doesn’t contain the temperature file.  The cpu temp is actually in the 
file tfile.  So basically, you have to swap the order of the check:  check 
first for tfile then tdir.  I’d post the necessary mod, but I don’t have 
access to my rpi right now.

Hope this helps and sorry for not being able to give more details!

On Wednesday, March 10, 2021 at 9:12:00 AM UTC-8 plin...@googlemail.com 
wrote:

> Hello,
>
> i have installed the cmon extension as described in 
> https://github.com/weewx/weewx/wiki/cmon
>
> In the plots the cpu_temp - Graph has no values.
>
> I use an raspberry pi 4
>
> does someone have a tip about it?
>
> Many thanks and greetings
>
> plinepa
>
>
>

-- 
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/df7404aa-e50c-4451-af49-a9b9b1de5b53n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Thank you  for that suggestion, I will expeditiously follow up!
On Saturday, 13 March 2021 at 14:05:03 UTC+13 gjr80 wrote:

> So you are back using the original Envoy that was 'tripping the fuse'? 
> Regards the two beeps from the Envoy I understand the first indicates 
> successful startup of the processor and the second verifies the 
> installation of the logger so it seems your single beep does point to an 
> issue with the logger.  Given you have things working again it might be 
> worthwhile contacting Davis in slower time and finding out if you do have 
> an incompatible Envoy/logger or if there is some other issue with one or 
> the other. If your original Envoy just started working again it could just 
> as easily stop as well; having a backup would be handy.
>
> Gary
> On Saturday, 13 March 2021 at 10:38:16 UTC+10 monmul wrote:
>
>> A big THANK YOU to all who helped me out on this, I really appreciate the 
>> help and guidancesorry it turned into a wild goose chase!
>>
>> On Friday, 12 March 2021 at 16:24:28 UTC+13 monmul wrote:
>>
>>> Yep fully functional againupdating on the website...WTF!.are 
>>> these things sent to us to just test our patience!!
>>>
>>> On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote:
>>>
 Hmmm! even more curiouserI notice from my webpage that data was 
 collected and posted yesterdayafter having nothing updated for almost 
 2 
 weeks!

 On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote:

> So, if it is the RPi then it is either a sofward corruption on the 
> card caused by the repeated rebooting after the fuse tripsor else 
> some 
> hardward failure on the board was the cause of the tripping. Its strange 
> that since reassembling the Envoy, RPi etc there has not been a fuse trip.
>
> One other thought occurs to me...I have a powered USB Hub attached to 
> the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
> directly into the RPi..if minicom works that would point to the Hub 
> as 
> being the culpit!!??
>
> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:
>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ wee_device --clear-memory
>> Using configuration file /etc/weewx/weewx.conf
>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>> Proceeding will erase all archive records.
>> Are you sure you wish to proceed (y/n)? y
>> Erasing all archive records ...
>> Archive records erased.
>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 12:49:30
>>
>> Press CTRL-A Z for help on special keys
>> .
>> .
>> .
>>
>>
>> Again no return of TEST or NVER
>>
>> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:
>>
>>> So, having put the old Envoy back on the Rpi (having shown it worked 
>>> on the PC) this is what I getlooks like some kind of continuous 
>>> Loop 
>>> situation.
>>>
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n 
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 12:42:51
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
>>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
>>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿÿ

Re: [weewx-user] Belchertown skin not linked to nginx

[vince]

David - you seem to be fishing, but it's not clear for what exactly.  There 
are hundreds of pages of documentation about weewx on the wiki and in the 
various guides.  There are thousands of posts.   There is so much 
documentation out there I can't even guess what you're not finding or what 
you're looking for.

If you want a super-simple skin that is installable via the extension 
installer, see my skin (here) 
 that displays the outside 
temperature and its graph.   Try installing that.  Then change its 
look+feel.  Add or change the elements or fonts.   Change the graph.  Add 
more graphs. Go wild.  Learn by experimentation.

Otherwise I'm at a loss for what you're trying to do.

-- 
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/07a2c23a-0fed-432a-8118-00bdcc00b85en%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

So you are back using the original Envoy that was 'tripping the fuse'? 
Regards the two beeps from the Envoy I understand the first indicates 
successful startup of the processor and the second verifies the 
installation of the logger so it seems your single beep does point to an 
issue with the logger.  Given you have things working again it might be 
worthwhile contacting Davis in slower time and finding out if you do have 
an incompatible Envoy/logger or if there is some other issue with one or 
the other. If your original Envoy just started working again it could just 
as easily stop as well; having a backup would be handy.

Gary
On Saturday, 13 March 2021 at 10:38:16 UTC+10 monmul wrote:

> A big THANK YOU to all who helped me out on this, I really appreciate the 
> help and guidancesorry it turned into a wild goose chase!
>
> On Friday, 12 March 2021 at 16:24:28 UTC+13 monmul wrote:
>
>> Yep fully functional againupdating on the website...WTF!.are 
>> these things sent to us to just test our patience!!
>>
>> On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote:
>>
>>> Hmmm! even more curiouserI notice from my webpage that data was 
>>> collected and posted yesterdayafter having nothing updated for almost 2 
>>> weeks!
>>>
>>> On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote:
>>>
 So, if it is the RPi then it is either a sofward corruption on the card 
 caused by the repeated rebooting after the fuse tripsor else some 
 hardward failure on the board was the cause of the tripping. Its strange 
 that since reassembling the Envoy, RPi etc there has not been a fuse trip.

 One other thought occurs to me...I have a powered USB Hub attached to 
 the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
 directly into the RPi..if minicom works that would point to the Hub as 
 being the culpit!!??

 On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ wee_device --clear-memory
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
> Proceeding will erase all archive records.
> Are you sure you wish to proceed (y/n)? y
> Erasing all archive records ...
> Archive records erased.
> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 12:49:30
>
> Press CTRL-A Z for help on special keys
> .
> .
> .
>
>
> Again no return of TEST or NVER
>
> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:
>
>> So, having put the old Envoy back on the Rpi (having shown it worked 
>> on the PC) this is what I getlooks like some kind of continuous Loop 
>> situation.
>>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 12:42:51
>>
>> Press CTRL-A Z for help on special keys
>>
>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> /‚LOO1 =vŠ 4I Àÿÿÿ

Re: [weewx-user] Belchertown skin not linked to nginx

[gjr80]

David,

I guess it really depends where you want to start and where you want to go. 
Its hard to beat the Standard skin 
 for it's 
simplicity; it's a series of fairly basic pages that just use basic html, 
WeeWX tags and plots. There is no specific documentation for the Standard 
skin but fairly much all the components except the html (ie the WeeWX tags 
and plots) are covered in the Customization Guide 
 under the 
*Customizing 
reports*, *The cheetah generator* and *The image generator* sections. The 
Standard skin has been superseded as the default WeeWX skin by the Seasons 
skin, but the Standard skin is still shipped and installed with WeeWX, it 
is just disabled by default. The Seasons skin is a step up from the 
Standard skin, it still uses basic html and WeeWX tags and plots but with a 
better layout/appearance. Seasons is much more modular and in that regard 
it can be a bit hard to follow (and work out what to change and where to 
change it if you do want to change something). New users must grapple with 
the 'flow and structure' of the templates as well as getting their heads 
around WeeWX tags and plots. Again no specific documentation other than the 
general tag and plot documentation in the Customization Guide. Belchertown 
is a step up again with a very smart looking display but using 
significantly more JavaScript and external JavaScript libraries to get the 
responsive design and third party plots. Pat has documented it well.

I guess it really comes down to your current skills and what you are 
seeking as the end point. Despite the documentation I would expect diving 
head first into extensively modifying the look and feel of Belchertown 
could be an exercise in frustration. By the same token I expect you 
probably don't want the look and feel of the Standard skin so spending a 
lot of time on it may end up being wasted time. Perhaps spend a little time 
with Standard, changing it, breaking it etc to get the feeling of tags and 
plots and then see where you want to go.

Gary
On Saturday, 13 March 2021 at 10:00:03 UTC+10 david.a@gmail.com wrote:

> Thanks! I started with Belchertown because of the rich amount of 
> documentation and help that's available. If not Belchertown, then what 
> would you both suggest i start with to build up a better understanding of 
> weewx, skins, graphs and weather info presentation?
> /David
>
> On Thursday, March 11, 2021 at 7:57:15 AM UTC-8 vince wrote:
>
>> On Thursday, March 11, 2021 at 3:25:55 AM UTC-8 kk44...@gmail.com wrote:
>>
>>> Belchertown is a very complex skin with lots of JavaScript and Python 
>>> scripts contributing some values. Major changes in layout require deep 
>>> study of the internal structure. If you have to fulfill special 
>>> requirements in layout, may be you want to start based on another skin like 
>>> Seasons.
>>>
>>>
>> Agree.  Belchertown supports only minimal configurability within some 
>> pretty strict bounds.   Figuring it all out end to end would require 
>> examining the source html and the reasonably complicated javascript code 
>> under the hood.  This is non-trivial especially for folks new to doing that 
>> kind of stuff.
>>
>> See 
>> https://github.com/poblabs/weewx-belchertown#add-custom-content-to-the-front-page
>>  
>> for the documentation.
>>  
>>
>

-- 
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/df1c94d0-4881-4d4b-8c17-afcd40943417n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

A big THANK YOU to all who helped me out on this, I really appreciate the 
help and guidancesorry it turned into a wild goose chase!

On Friday, 12 March 2021 at 16:24:28 UTC+13 monmul wrote:

> Yep fully functional againupdating on the website...WTF!.are these 
> things sent to us to just test our patience!!
>
> On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote:
>
>> Hmmm! even more curiouserI notice from my webpage that data was 
>> collected and posted yesterdayafter having nothing updated for almost 2 
>> weeks!
>>
>> On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote:
>>
>>> So, if it is the RPi then it is either a sofward corruption on the card 
>>> caused by the repeated rebooting after the fuse tripsor else some 
>>> hardward failure on the board was the cause of the tripping. Its strange 
>>> that since reassembling the Envoy, RPi etc there has not been a fuse trip.
>>>
>>> One other thought occurs to me...I have a powered USB Hub attached to 
>>> the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
>>> directly into the RPi..if minicom works that would point to the Hub as 
>>> being the culpit!!??
>>>
>>> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:
>>>
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ wee_device --clear-memory
 Using configuration file /etc/weewx/weewx.conf
 Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
 Proceeding will erase all archive records.
 Are you sure you wish to proceed (y/n)? y
 Erasing all archive records ...
 Archive records erased.
 pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0


 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 12:49:30

 Press CTRL-A Z for help on special keys
 .
 .
 .


 Again no return of TEST or NVER

 On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:

> So, having put the old Envoy back on the Rpi (having shown it worked 
> on the PC) this is what I getlooks like some kind of continuous Loop 
> situation.
>
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 12:42:51
>
> Press CTRL-A Z for help on special keys
>
> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
>
> ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2
> âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½   b 2
> ¾LOO1 =vŠ 4I Áÿÿÿ
>
> On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote:
>
>> But from the tests on my PC, it seems the old Envoy is 
>> workingdoes it not.(so we do not have to worry about the new Envoy 
>> for 
>> now!)...so it would appear as if the RPi is the culpithave I 
>> deducted 
>> correctly?
>>
>> On Friday, 12 March 2021 at 02:29:03 U

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Thanks! I started with Belchertown because of the rich amount of 
documentation and help that's available. If not Belchertown, then what 
would you both suggest i start with to build up a better understanding of 
weewx, skins, graphs and weather info presentation?
/David

On Thursday, March 11, 2021 at 7:57:15 AM UTC-8 vince wrote:

> On Thursday, March 11, 2021 at 3:25:55 AM UTC-8 kk44...@gmail.com wrote:
>
>> Belchertown is a very complex skin with lots of JavaScript and Python 
>> scripts contributing some values. Major changes in layout require deep 
>> study of the internal structure. If you have to fulfill special 
>> requirements in layout, may be you want to start based on another skin like 
>> Seasons.
>>
>>
> Agree.  Belchertown supports only minimal configurability within some 
> pretty strict bounds.   Figuring it all out end to end would require 
> examining the source html and the reasonably complicated javascript code 
> under the hood.  This is non-trivial especially for folks new to doing that 
> kind of stuff.
>
> See 
> https://github.com/poblabs/weewx-belchertown#add-custom-content-to-the-front-page
>  
> for the documentation.
>  
>

-- 
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/1bbc2ca6-30ed-4555-8aa1-5ba2ecb6b1edn%40googlegroups.com.

Re: [weewx-user] Question on heat index

[Les Niles]

It looks strange to see the heat index suddenly dropping a few degrees below 
the temperature when the temperature gets above 40ºF. (I just saw this this 
morning.) After looking through the thread on weewx’s new heat index 
calculation, I noticed an oddity at the National Weather Service: while their 
calculator calculates a heat index down to 40ºF, on the page where they 
describe the HI equation 
 they say the 
“Rothfusz regression is not valid for extreme temperature and relative humidity 
conditions beyond the range of data considered by Steadman.” Looking at 
Steadman’s sultriness papers from 1979 
  he never 
looked at temperatures below 68ºF. I couldn’t find any reference to indicate 
why they arbitrarily extended the javascript calculator down to 40ºF. Other 
authors, and the NWS tables, suggest that the heat index isn’t really of value 
below 80ºF.  

So I tweaked dewpointF() in my installation to return None if the temperature 
is below 68, and now I feel better.  

  -Les



> On 24 Feb 2021, at 12:54, gjr80  wrote:
> 
> Pat,
> 
> v4.2.0 saw a new heatindex formula implemented, refer issue 601 
> . The new formula gives some 
> results in some circumstances that may appear counterintuitive. v4.3.0 added 
> back the ‘old’ heatindex formula and gives the user the ability to choose 
> between the two algorithms . This is covered here 
>  in the User’s 
> Guide under [[[heatindex]]].
> 
> By the looks of it you are seeing the ‘new’ algorithm.
> 
> Gary
> 
> On Thursday, 25 February 2021 at 06:36:38 UTC+10 pobri...@gmail.com wrote:
> I thought heat index wasn't calculated unless the temperature was over 80F? 
> Today it's about 49 F and I'm seeing heat index in my charts (which is 
> reporting lower than temperature - I thought that was wind chill?). I don't 
> recall seeing it before at this temperature range. 
> 
> I just want to make sure this is expected for temperatures so low to have a 
> heat index reading?
> 
> Top graph is Seasons skin and bottom is Belchertown skin. The values match 
> across skins
> 
> -- 
> 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/f46bd022-500d-414e-b96b-c2bc382d37b9n%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/23595CDF-1D28-49B5-AE8C-A108967A34AE%402pi.org.

[weewx-user] Re: update identifier for HIDEKI-wind and hideki rain to the new style SDR.

[Michael]

Hi Giuseppe,

try this modified sdr.py

Michael

-- 
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/ae6ff367-a594-42ab-bcbb-ff4c28a9dc72n%40googlegroups.com.
#!/usr/bin/env python
# Copyright 2016-2020 Matthew Wall
# Distributed under the terms of the GNU Public License (GPLv3)
"""
Collect data from stl-sdr.  Run rtl_433 on a thread and push the output onto
a queue.

The SDR detects many different sensors and sensor types, so this driver
includes a mechanism to filter the incoming data, and to map the filtered
data onto the weewx database schema and identify the type of data from each
sensor.

Sensors are filtered based on a tuple that identifies uniquely each sensor.
A tuple consists of the observation name, a unique identifier for the hardware,
and the packet type, separated by periods:

  ..

The filter and data types are specified in a sensor_map stanza in the driver
stanza.  For example:

[SDR]
driver = user.sdr
[[sensor_map]]
inTemp = temperature.25A6.AcuriteTowerPacket
outTemp = temperature.24A4.AcuriteTowerPacket
rain_total = rain_total.A52B.Acurite5n1Packet

If no sensor_map is specified, no data will be collected.

The deltas stanza indicates which observations are cumulative measures and
how they should be split into delta measures.

[SDR]
...
[[deltas]]
rain = rain_total

In this case, the value for rain will be a delta calculated from sequential
rain_total observations.

To identify sensors, run the driver directly.  Alternatively, use the options
log_unknown_sensors and log_unmapped_sensors to see data from the SDR that are
not yet recognized by your configuration.

[SDR]
driver = user.sdr
log_unknown_sensors = True
log_unmapped_sensors = True

The default for each of these is False.

Eventually we would prefer to have all rtl_433 output as json.  Unfortunately,
many of the rtl_433 decoders do not emit this format yet (as of January 2017).
So this driver is designed to look for json first, then fall back to single-
or multi-line plain text format.

WARNING: Handling of units and unit systems in rtl_433 is a mess, but it is
getting better.  Although there is an option to request SI units, there is no
indicate in the decoder output whether that option is respected, nor does
rtl_433 specify exactly which SI units are used for various types of measure.
There seems to be a pattern of appending a unit label to the observation name
in the JSON data, for example 'wind_speed_mph' instead of just 'wind_speed'.
"""

from __future__ import with_statement
from calendar import timegm
try:
# Python 3
import queue
except ImportError:
# Python 2:
import Queue as queue
import fnmatch
import os
import re
import subprocess
import threading
import time

try:
import cjson as json
setattr(json, 'dumps', json.encode)
setattr(json, 'loads', json.decode)
except (ImportError, AttributeError):
try:
import simplejson as json
except ImportError:
import json

import weewx.drivers
import weewx.units
from weeutil.weeutil import tobool

try:
# New-style weewx logging
import weeutil.logger
import logging
log = logging.getLogger(__name__)

def logdbg(msg):
log.debug(msg)

def loginf(msg):
log.info(msg)

def logerr(msg):
log.error(msg)

except ImportError:
# Old-style weewx logging
import syslog

def logmsg(level, msg):
syslog.syslog(level, 'sdr: %s: %s' %
  (threading.currentThread().getName(), msg))

def logdbg(msg):
logmsg(syslog.LOG_DEBUG, msg)

def loginf(msg):
logmsg(syslog.LOG_INFO, msg)

def logerr(msg):
logmsg(syslog.LOG_ERR, msg)

DRIVER_NAME = 'SDR'
DRIVER_VERSION = '0.79'

# The default command requests json output from every decoder
# Use the -R option to indicate specific decoders

# -q  - suppress non-data messages (for older versions of rtl_433)
# -M utc  - print timestamps in UTC (-U for older versions of rtl_433)
# -F json - emit data in json format (not all rtl_433 decoders support this)
# -G  - emit data for all rtl decoders (only available in newer rtl_433)
#   as of early 2020, the syntax is '-G4', but use only for testing

# very old implmentations:
#DEFAULT_CMD = 'rtl_433 -q -U -F json -G'
# as of dec2018:
#DEFAULT_CMD = 'rtl_433 -M utc -F json -G'
# as of feb2020:
DEFAULT_CMD = 'rtl_433 -M utc -F json'

def loader(config_dict, _):
return SDRDriver(**config_dict[DRIVER_NAME])

def confeditor_loader():
return SDRConfigurationEditor()


class AsyncReader(threading.Thread):

def __init__(self, fd, queue, label):
threading.Thread.__init__(self)
self._fd = fd
self._que

Re: [weewx-user] Re: Problem deleting old data

[Tom Keffer]

The records are definitely coming from the logger. Try clearing the logger
again, except this time

   1. Make sure weewxd is stopped.
   2. Make sure you have the necessary privileges. You may have to use
   'sudo' before wee_device.
   3. Use "wee_device --clear-memory".
   4. If you get no satisfaction, post the logs from the invocation of
   wee_device through its termination.

-tk

On Fri, Mar 12, 2021 at 9:38 AM Jon B  wrote:

> Sorry, forgot to add the logs! Here's one example (there are lots of
> entries like this)
>
> INFO weewx.manager: Added record 2020-11-26 08:30:00 GMT (1606379400) to
> database 'weewx.sdb'
> INFO weewx.manager: Added record 2020-11-26 08:30:00 GMT (1606379400) to
> daily summary in 'weewx.sdb'
>
> Seems as though it is picking up old data from the logger as you suggest,
> which is strange as I've tried clearing it a few times so presumably it
> isn't deleting properly when I do that. I've barely had it turned on since
> December, hence why the dates are a few months ago
>
> I'll do as you suggest and try clearing it out in a couple of weeks,
> unless anyone can suggest a reason that it's not clearing properly
> On Friday, 12 March 2021 at 17:04:25 UTC vince wrote:
>
>> On Friday, March 12, 2021 at 8:26:29 AM UTC-8 jonbe...@gmail.com wrote:
>>
>>> I've got a new Davis Vantage Pro2 which I've got setup with weewx, using
>>> the Belchertown skin. While I was testing it, I had the station indoors and
>>> so I've got some data from that period. I've installed the station outdoors
>>> now so want to delete the old data, but I can't seem to get rid of it!
>>>
>>>
>> Hard to say without any logs in your post, but my guess is you see old
>> data from your datalogger.
>>
>> You might want to just wait a couple weeks til the logger has only
>> outside data in it, then stop weewx and clean up any data before a
>> particular date+time.  There are lots of docs online for how to do that.
>>
>>
> --
> 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/6ebdd45f-ffe9-4837-9dfe-22047bbcaef1n%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/CAPq0zEDJQD4O6-n%3DX7uBbzwaOYrEx93NWadWPVrA%3D5jpbpTCVg%40mail.gmail.com.

[weewx-user] Re: Problem deleting old data

[Jon B]

Sorry, forgot to add the logs! Here's one example (there are lots of 
entries like this)

INFO weewx.manager: Added record 2020-11-26 08:30:00 GMT (1606379400) to 
database 'weewx.sdb'
INFO weewx.manager: Added record 2020-11-26 08:30:00 GMT (1606379400) to 
daily summary in 'weewx.sdb'

Seems as though it is picking up old data from the logger as you suggest, 
which is strange as I've tried clearing it a few times so presumably it 
isn't deleting properly when I do that. I've barely had it turned on since 
December, hence why the dates are a few months ago

I'll do as you suggest and try clearing it out in a couple of weeks, unless 
anyone can suggest a reason that it's not clearing properly
On Friday, 12 March 2021 at 17:04:25 UTC vince wrote:

> On Friday, March 12, 2021 at 8:26:29 AM UTC-8 jonbe...@gmail.com wrote:
>
>> I've got a new Davis Vantage Pro2 which I've got setup with weewx, using 
>> the Belchertown skin. While I was testing it, I had the station indoors and 
>> so I've got some data from that period. I've installed the station outdoors 
>> now so want to delete the old data, but I can't seem to get rid of it! 
>>
>>
> Hard to say without any logs in your post, but my guess is you see old 
> data from your datalogger.
>
> You might want to just wait a couple weeks til the logger has only outside 
> data in it, then stop weewx and clean up any data before a particular 
> date+time.  There are lots of docs online for how to do that.
>  
>

-- 
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/6ebdd45f-ffe9-4837-9dfe-22047bbcaef1n%40googlegroups.com.

[weewx-user] Re: Problem deleting old data

[vince]

On Friday, March 12, 2021 at 8:26:29 AM UTC-8 jonbe...@gmail.com wrote:

> I've got a new Davis Vantage Pro2 which I've got setup with weewx, using 
> the Belchertown skin. While I was testing it, I had the station indoors and 
> so I've got some data from that period. I've installed the station outdoors 
> now so want to delete the old data, but I can't seem to get rid of it! 
>
>
Hard to say without any logs in your post, but my guess is you see old data 
from your datalogger.

You might want to just wait a couple weeks til the logger has only outside 
data in it, then stop weewx and clean up any data before a particular 
date+time.  There are lots of docs online for how to do that.
 

-- 
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/192fdfbb-5cd7-4d19-ab43-5c8257313e04n%40googlegroups.com.

[weewx-user] Problem deleting old data

[Jon B]

I've got a new Davis Vantage Pro2 which I've got setup with weewx, using 
the Belchertown skin. While I was testing it, I had the station indoors and 
so I've got some data from that period. I've installed the station outdoors 
now so want to delete the old data, but I can't seem to get rid of it! 

I've tried stopping weewx, then deleting the database file in 
/var/lib/weewx/, as well as all the files in /var/www/html/weewx and the 
equivalent ones on the webserver, then clearing the data on the console 
(which appears to work correctly, as it says "clearing now"), before 
restarting weewx - but the old data keeps reappearing! Is the old data also 
stored somewhere else? I can't understand where it's coming from!

-- 
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/b64c5373-87ed-4617-8701-e465d30f8c65n%40googlegroups.com.

[weewx-user] Re: ERROR weewx.reportengine: ftpgenerator: (0): caught exception '': [Errno -3]

[Karen K]

That's what I guessed. Therefore I asked you that ping thing, although it 
does not reveal the real problem.

Artvd schrieb am Freitag, 12. März 2021 um 13:37:28 UTC+1:

> It is resolved. It was a problem at my web hosting provider. Thanks for 
> your assistence.
>
> Op donderdag 11 maart 2021 om 23:40:56 UTC+1 schreef Artvd:
>
>> It  means  " Temporary problem in name redirection" .
>> I have taken up contact with my hosting company. There is perhaps a 
>> problem on their side. but i gueas i will have to wait till tomorrow.
>> Op donderdag 11 maart 2021 om 23:22:58 UTC+1 schreef kk44...@gmail.com:
>>
>>> Ok, that is good. I am not used to dutch language, and I wondered what 
>>> the error message "Tijdelijk probleem in naamsherleiding" means, and I 
>>> thought, may be, the computer does not find any sites in the internet. But 
>>> it does. So that is not the problem.
>>>
>>> But still, the error log let me think that WeeWX cannot cannot convert 
>>> names to IP addresses.
>>>
>>> What if you put an IP address instead of the name in the config?
>>>
>>> Artvd schrieb am Donnerstag, 11. März 2021 um 23:10:05 UTC+1:
>>>
 This is what i get

 $ ping ibm.com
 PING ibm.com (23.213.242.74) 56(84) bytes of data.
 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
 (23.213.242.74): icmp_seq=1 ttl=59 time=9.90 ms
 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
 (23.213.242.74): icmp_seq=2 ttl=59 time=10.1 ms
 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
 (23.213.242.74): icmp_seq=3 ttl=59 time=9.45 ms
 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
 (23.213.242.74): icmp_seq=4 ttl=59 time=9.63 ms
 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
 (23.213.242.74): icmp_seq=5 ttl=59 time=9.61 ms


 Op donderdag 11 maart 2021 om 22:29:38 UTC+1 schreef kk44...@gmail.com:

> Where do you enter commands to start/stop WeeWX or edit config files? 
> There you can enter that ping command.
>
> Artvd schrieb am Donnerstag, 11. März 2021 um 22:26:57 UTC+1:
>
>> Thanks for your reaction. I do not have a console so i do not knkow 
>> how to do that otherwise 
>>
>> Op donderdag 11 maart 2021 om 22:18:45 UTC+1 schreef 
>> kk44...@gmail.com:
>>
>>> That looks like a resolver problem that does not relate to WeeWX.
>>>
>>> What happens if you enter ping www.ibm.com on the console?
>>>
>>> Artvd schrieb am Donnerstag, 11. März 2021 um 21:32:48 UTC+1:
>>>
 Hello 

 I am experiencing a problem with ftp upload. It even remaind after 
 reinstalling Weewx and hope someone can help me to resolve this. This 
 is 
 the log:

 Mar 11 21:25:51 raspberrypi weewx[8796] INFO weewx.reportengine: 
 Copied 97 files to /var/www/html/weewx
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine: 
 ftpgenerator: (0): caught exception '': 
 [Errno -3] 
 Tijdelijk probleem in naamsherleiding
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
  Traceback (most recent call last):
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
File "/usr/share/weewx/weewx/reportengine.py", line 
 331, in 
 run
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
  n = ftp_data.run()
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
File "/usr/share/weewx/weeutil/ftpupload.py", line 127, 
 in 
 run
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
  ftp_server.connect(self.server, self.port)
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
File "/usr/lib/python3.7/ftplib.py", line 152, in 
 connect
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
  source_address=self.source_address)
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
File "/usr/lib/python3.7/socket.py", line 707, in 
 create_connection
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
  for res in getaddrinfo(host, port, 0, SOCK_STREAM):
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
File "/usr/lib/python3.7/socket.py", line 748, in 
 getaddrinfo
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:  
  for res in _socket.getaddrinfo(host, port, family, 
 type, 
 proto, flags):
 Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine

[weewx-user] Re: ERROR weewx.reportengine: ftpgenerator: (0): caught exception '': [Errno -3]

[Artvd]

It is resolved. It was a problem at my web hosting provider. Thanks for 
your assistence.

Op donderdag 11 maart 2021 om 23:40:56 UTC+1 schreef Artvd:

> It  means  " Temporary problem in name redirection" .
> I have taken up contact with my hosting company. There is perhaps a 
> problem on their side. but i gueas i will have to wait till tomorrow.
> Op donderdag 11 maart 2021 om 23:22:58 UTC+1 schreef kk44...@gmail.com:
>
>> Ok, that is good. I am not used to dutch language, and I wondered what 
>> the error message "Tijdelijk probleem in naamsherleiding" means, and I 
>> thought, may be, the computer does not find any sites in the internet. But 
>> it does. So that is not the problem.
>>
>> But still, the error log let me think that WeeWX cannot cannot convert 
>> names to IP addresses.
>>
>> What if you put an IP address instead of the name in the config?
>>
>> Artvd schrieb am Donnerstag, 11. März 2021 um 23:10:05 UTC+1:
>>
>>> This is what i get
>>>
>>> $ ping ibm.com
>>> PING ibm.com (23.213.242.74) 56(84) bytes of data.
>>> 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
>>> (23.213.242.74): icmp_seq=1 ttl=59 time=9.90 ms
>>> 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
>>> (23.213.242.74): icmp_seq=2 ttl=59 time=10.1 ms
>>> 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
>>> (23.213.242.74): icmp_seq=3 ttl=59 time=9.45 ms
>>> 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
>>> (23.213.242.74): icmp_seq=4 ttl=59 time=9.63 ms
>>> 64 bytes from a23-213-242-74.deploy.static.akamaitechnologies.com 
>>> (23.213.242.74): icmp_seq=5 ttl=59 time=9.61 ms
>>>
>>>
>>> Op donderdag 11 maart 2021 om 22:29:38 UTC+1 schreef kk44...@gmail.com:
>>>
 Where do you enter commands to start/stop WeeWX or edit config files? 
 There you can enter that ping command.

 Artvd schrieb am Donnerstag, 11. März 2021 um 22:26:57 UTC+1:

> Thanks for your reaction. I do not have a console so i do not knkow 
> how to do that otherwise 
>
> Op donderdag 11 maart 2021 om 22:18:45 UTC+1 schreef kk44...@gmail.com
> :
>
>> That looks like a resolver problem that does not relate to WeeWX.
>>
>> What happens if you enter ping www.ibm.com on the console?
>>
>> Artvd schrieb am Donnerstag, 11. März 2021 um 21:32:48 UTC+1:
>>
>>> Hello 
>>>
>>> I am experiencing a problem with ftp upload. It even remaind after 
>>> reinstalling Weewx and hope someone can help me to resolve this. This 
>>> is 
>>> the log:
>>>
>>> Mar 11 21:25:51 raspberrypi weewx[8796] INFO weewx.reportengine: 
>>> Copied 97 files to /var/www/html/weewx
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine: 
>>> ftpgenerator: (0): caught exception '': [Errno 
>>> -3] 
>>> Tijdelijk probleem in naamsherleiding
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>    Traceback (most recent call last):
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>  File "/usr/share/weewx/weewx/reportengine.py", line 331, 
>>> in run
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>    n = ftp_data.run()
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>  File "/usr/share/weewx/weeutil/ftpupload.py", line 127, in 
>>> run
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>    ftp_server.connect(self.server, self.port)
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>  File "/usr/lib/python3.7/ftplib.py", line 152, in connect
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>    source_address=self.source_address)
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>  File "/usr/lib/python3.7/socket.py", line 707, in 
>>> create_connection
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>    for res in getaddrinfo(host, port, 0, SOCK_STREAM):
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>  File "/usr/lib/python3.7/socket.py", line 748, in 
>>> getaddrinfo
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>    for res in _socket.getaddrinfo(host, port, family, type, 
>>> proto, flags):
>>> Mar 11 21:25:51 raspberrypi weewx[8796] ERROR weewx.reportengine:
>>>    socket.gaierror: [Errno -3] Tijdelijk probleem in 
>>> naamsherleiding
>>>
>>>

-- 
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: [weewx-user] Calculating Sun Energy from Radiation Reading

[Karen K]

Thanks for your patience.

belin@gmail.com schrieb am Freitag, 12. März 2021 um 10:05:52 UTC+1:

> Thanks for your help, it works
>
> Le 11 mars 2021 à 19:20, Karen K  a écrit :
>
> You have version 0.3 installed. In order to calculate solar power you need 
> version 0.4.1. Please install the latest version and try again. 
>
> belin@gmail.com schrieb am Donnerstag, 11. März 2021 um 19:15:33 
> UTC+1:
>
>> prep_services = weewx.engine.StdTimeSynch
>> data_services = ,
>> process_services = weewx.engine.StdConvert, 
>> weewx.engine.StdCalibrate, weewx.engine.StdQC, 
>> weewx.wxservices.StdWXCalculate
>> xtype_services = weewx.wxxtypes.StdWXXTypes, 
>> weewx.wxxtypes.StdPressureCooker, weewx.wxxtypes.StdRainRater, 
>> weewx.wxxtypes.StdDelta, user.GTS.GTSService, 
>> user.phenologyservice.PhenologyService
>> archive_services = weewx.engine.Std.Archive
>> restful_services = weewx.restx.StdStationRegistry, 
>> weewx.restx.StdWunderground, weewx.restx.StdPWSweather, 
>> weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS, 
>> user.mqtt.MQTT
>> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>>
>>
>>
>> [Calculations]]
>> # How to calculate derived quantities.  Possible values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> altimeter = prefer_hardware
>> appTemp = prefer_hardware
>> barometer = 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
>> GTS = "software,archive"
>> GTSdate = "software,archive"
>> utcoffsetLMT = "software,archive"
>> dayET = "software,archive"
>> ET24 = "software,archive"
>>
>>
>>11 19:07:11 Meteo3 weewx[4992] INFO weewx.engine: StdConvert 
>> target unit is 0x10
>> Mar 11 19:07:11 Meteo3 weewx[4992] INFO user.GTS: Version 0.3
>> Mar 11 19:07:11 Meteo3 weewx[4992] INFO user.GTS: Local mean time (LMT) 
>> UTC offset 0:21:00
>> Mar 11 19:07:12 Meteo3 weewx[4992] INFO weewx.engine: Archive will use 
>> data binding wx_binding
>> Mar 11 19:07:12 Meteo3 weewx[4992] INFO weewx.engine: Record generation 
>> will be attempted in 'hardware'
>> Mar 11 19:07:12 Meteo3 weewx[4992] INFO weewx.engine: Using archive 
>> interval of 300 seconds (specified in weewx configuration)
>> Mar 11 19:07:12 Meteo3 weewx[4992] INFO weewx.restx: StationRegistry: 
>> Registration not requested.
>>
>>11 19:10:29 Meteo3 weewx[4992] INFO user.GTS: GTS initialized 
>> 2021-01-01 00:39:00 
>> Mar 11 19:10:29 Meteo3 weewx[4992] INFO user.GTS: GTS 235.42205669182695, 
>> 69 loops
>>
>>
>>
>> Le 11 mars 2021 à 18:14, Karen K  a écrit :
>>
>> That seems to me that the GTS extension is not really activated. Could 
>> you send the sections [StdWXCalculate] and [Engine] from weewx.conf? 
>> Additionally send all messages in syslog regarding GTS during the start of 
>> WeeWX.
>>
>> belin@gmail.com schrieb am Donnerstag, 11. März 2021 um 17:12:58 
>> UTC+1:
>>
>>> Thanks for your answer, but when I copy the info I get these errors:
>>>
>>> ar 11 17:00:27 Meteo3 weewx[30301] INFO weewx.cheetahgenerator: 
>>> Generated 11 files for report Belchertown in 3.60 seconds
>>> Mar 11 17:00:27 Meteo3 weewx[30301] INFO weewx.reportengine: Copied 2 
>>> files to /var/www/html
>>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine: Caught 
>>> unrecoverable exception in generator 
>>> 'user.belchertown.HighchartsJsonGenerator'
>>> ghchartsJsonGenerator'
>>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine: 
>>>   Error trying to use database binding wx_binding to graph observation 
>>> radiation. Error was: energy_integral('radiation').
>>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine: 
>>>   Traceback (most recent call last):
>>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine: 
>>> File "/usr/share/weewx/user/belchertown.py", line 2423, in 
>>> get_observation_data
>>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine: 
>>>   (time_start_vt, time_stop_vt, obs_vt) = 
>>> archive.getSqlVectors(TimeSpan(start_ts, end_ts), obs_lookup, 
>>> aggregate_type, aggregate_interval)
>>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine: 
>>> File "/usr/share/weewx/weewx/manager.py", line 456, in getSqlVec

[weewx-user] Re: Belchertown - MQTT with webhosting

[Christian Gruber]

ok i think i didn't do the first extension with extension.py because mine 
is empty :-)

i changed schema in weewx.config and recreated the database, then i got the 
new fields

i am a bit confused now what to do :-)

[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.manager.DaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = user.weatherlink_live.schema

Manfred Maier schrieb am Freitag, 12. März 2021 um 09:53:59 UTC+1:

> I've also extended my database scheme a second time - without any issues.
>
> Here's my extensions.py
> I've just added the additional three fields to the already extended scheme.
>
> grua...@gmail.com schrieb am Freitag, 12. März 2021 um 08:42:17 UTC+1:
>
>> got it, thank you manfred!
>>
>> now a question about radiationhours: i have extended the schema already 
>> one time for the weatherlink-driver: 
>> https://github.com/michael-slx/weewx-weatherlink-live
>>
>> whats the correct way to extend the schema a second time? i tried it one 
>> time, but then i lost the additional fields from the weatherlink-driver
>>
>> Manfred Maier schrieb am Donnerstag, 11. März 2021 um 19:28:55 UTC+1:
>>
>>> Yes, you are correct. If the page is using https, all components need to 
>>> have a ssl certificate.
>>>
>>> grua...@gmail.com schrieb am Donnerstag, 11. März 2021 um 10:00:07 
>>> UTC+1:
>>>
 hi,

 thanks for this file, i will try it after mqtt-setup :-)

 i always get failed connecting on my website and i think it's because 
 my site is using https

 the test here is working fine, i get the live data 
 http://www.hivemq.com/demos/websocket-client/

 do i have to run my local mosquitto installation also with ssl/tls or 
 is there another way to get it working?

 regards,
 chris

 Manfred Maier schrieb am Mittwoch, 10. März 2021 um 20:44:02 UTC+1:

> I'm using the attached file, which I found somewhere here in this user 
> forum. 
> I've slightly adapted it to bette fit my needs. 
>
> Don't get confused by the filed name 'EmptyReal'. That was just a 
> spare field I had in my database.
>
> The calculation of the theoretical radiation level is not 100% 
> perfect, but it does the job.
>
>
> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 20:05:55 
> UTC+1:
>
>> ok, i will try it locally before, but vserver is also a good (cheap) 
>> option :-)
>>
>> another question to you: how do you calculate sun hours on your site, 
>> is it from here? https://github.com/gjr80/weewx-weewx-wd
>>
>> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 19:23:40 UTC+1:
>>
>>> No, I didn't.
>>>
>>> I'm (unfortunately) sitting behind fiberglass without a static IPv4. 
>>> So I anyway had to rent a vServer for running my own tunneling 
>>> solution for my local webcam.
>>>
>>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 19:12:12 
>>> UTC+1:
>>>
 hi manfred,

 did you try to run the broker locally before? 

 i have a static ip with symmetric bandwidth. or are there other 
 reasons why it doesnt work?

 regards,
 chris

 Manfred Maier schrieb am Mittwoch, 10. März 2021 um 15:16:35 UTC+1:

> Hi Chris,
> I've been in a similar situation to you.
> My web hosting service didn't allow me to run a MQTT broker and 
> the (free) public brokers didn't perform very well. The majority of 
> MQTT 
> packages got lost and were not delivered to the web client.
> So in the end I've decided to rent an additional vServer and run 
> my own MQTT broker. The setup was really easy, but there's a server 
> cost of 
> approx. 2€ per month.
>
> Manfred  
>
> kk44...@gmail.com schrieb am Mittwoch, 10. März 2021 um 11:59:33 
> UTC+1:
>
>> You need a publicly available MQTT broker. Either you install one 
>> on your webhoster's webspace (if possible), or you use a public 
>> broker like 
>> test.mosquitto.org.
>>
>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 07:46:52 
>> UTC+1:
>>
>>> hello,
>>>
>>> i am uploading the reports via FTP to my webhoster. can i use 
>>> mqtt then for live data oder do i need a locally webserver?
>>>
>>> regards,
>>> chris
>

Re: [weewx-user] Calculating Sun Energy from Radiation Reading

[didier belin]

Thanks for your help, it works

> Le 11 mars 2021 à 19:20, Karen K  a écrit :
> 
> You have version 0.3 installed. In order to calculate solar power you need 
> version 0.4.1. Please install the latest version and try again. 
> 
> belin@gmail.com  schrieb am Donnerstag, 11. März 2021 
> um 19:15:33 UTC+1:
> prep_services = weewx.engine.StdTimeSynch
> data_services = ,
> process_services = weewx.engine.StdConvert, 
> weewx.engine.StdCalibrate, weewx.engine.StdQC, weewx.wxservices.StdWXCalculate
> xtype_services = weewx.wxxtypes.StdWXXTypes, 
> weewx.wxxtypes.StdPressureCooker, weewx.wxxtypes.StdRainRater, 
> weewx.wxxtypes.StdDelta, user.GTS.GTSService, 
> user.phenologyservice.PhenologyService
> archive_services = weewx.engine.Std.Archive
> restful_services = weewx.restx.StdStationRegistry, 
> weewx.restx.StdWunderground, weewx.restx.StdPWSweather, weewx.restx.StdCWOP, 
> weewx.restx.StdWOW, weewx.restx.StdAWEKAS, user.mqtt.MQTT
> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
> 
> 
> 
> [Calculations]]
> # How to calculate derived quantities.  Possible values are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
> 
> pressure = prefer_hardware
> altimeter = prefer_hardware
> appTemp = prefer_hardware
> barometer = 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
> GTS = "software,archive"
> GTSdate = "software,archive"
> utcoffsetLMT = "software,archive"
> dayET = "software,archive"
> ET24 = "software,archive"
> 
> 
>11 19:07:11 Meteo3 weewx[4992] INFO weewx.engine: StdConvert target 
> unit is 0x10
> Mar 11 19:07:11 Meteo3 weewx[4992] INFO user.GTS: Version 0.3
> Mar 11 19:07:11 Meteo3 weewx[4992] INFO user.GTS: Local mean time (LMT) UTC 
> offset 0:21:00
> Mar 11 19:07:12 Meteo3 weewx[4992] INFO weewx.engine: Archive will use data 
> binding wx_binding
> Mar 11 19:07:12 Meteo3 weewx[4992] INFO weewx.engine: Record generation will 
> be attempted in 'hardware'
> Mar 11 19:07:12 Meteo3 weewx[4992] INFO weewx.engine: Using archive interval 
> of 300 seconds (specified in weewx configuration)
> Mar 11 19:07:12 Meteo3 weewx[4992] INFO weewx.restx: StationRegistry: 
> Registration not requested.
> 
>11 19:10:29 Meteo3 weewx[4992] INFO user.GTS: GTS initialized 
> 2021-01-01 00:39:00 
> Mar 11 19:10:29 Meteo3 weewx[4992] INFO user.GTS: GTS 235.42205669182695, 69 
> loops
> 
> 
> 
> 
>> Le 11 mars 2021 à 18:14, Karen K > > a écrit :
>> 
> 
>> That seems to me that the GTS extension is not really activated. Could you 
>> send the sections [StdWXCalculate] and [Engine] from weewx.conf? 
>> Additionally send all messages in syslog regarding GTS during the start of 
>> WeeWX.
>> 
>> belin@gmail.com  schrieb am Donnerstag, 11. März 2021 
>> um 17:12:58 UTC+1:
>> Thanks for your answer, but when I copy the info I get these errors:
>> 
>> ar 11 17:00:27 Meteo3 weewx[30301] INFO weewx.cheetahgenerator: Generated 11 
>> files for report Belchertown in 3.60 seconds
>> Mar 11 17:00:27 Meteo3 weewx[30301] INFO weewx.reportengine: Copied 2 files 
>> to /var/www/html
>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> ghchartsJsonGenerator'
>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine:   
>> Error trying to use database binding wx_binding to graph observation 
>> radiation. Error was: energy_integral('radiation').
>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine:   
>> Traceback (most recent call last):
>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine:    
>>  File "/usr/share/weewx/user/belchertown.py", line 2423, in 
>> get_observation_data
>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine:    
>>(time_start_vt, time_stop_vt, obs_vt) = 
>> archive.getSqlVectors(TimeSpan(start_ts, end_ts), obs_lookup, 
>> aggregate_type, aggregate_interval)
>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine:    
>>  File "/usr/share/weewx/weewx/manager.py", line 456, in getSqlVectors
>> Mar 11 17:00:28 Meteo3 weewx[30301] ERROR weewx.reportengine:    
>>aggregate_type, aggregate_interval)
>> Mar 11 17:00

[weewx-user] Re: Belchertown - MQTT with webhosting

[Manfred Maier]

I've also extended my database scheme a second time - without any issues.

Here's my extensions.py
I've just added the additional three fields to the already extended scheme.

grua...@gmail.com schrieb am Freitag, 12. März 2021 um 08:42:17 UTC+1:

> got it, thank you manfred!
>
> now a question about radiationhours: i have extended the schema already 
> one time for the weatherlink-driver: 
> https://github.com/michael-slx/weewx-weatherlink-live
>
> whats the correct way to extend the schema a second time? i tried it one 
> time, but then i lost the additional fields from the weatherlink-driver
>
> Manfred Maier schrieb am Donnerstag, 11. März 2021 um 19:28:55 UTC+1:
>
>> Yes, you are correct. If the page is using https, all components need to 
>> have a ssl certificate.
>>
>> grua...@gmail.com schrieb am Donnerstag, 11. März 2021 um 10:00:07 UTC+1:
>>
>>> hi,
>>>
>>> thanks for this file, i will try it after mqtt-setup :-)
>>>
>>> i always get failed connecting on my website and i think it's because my 
>>> site is using https
>>>
>>> the test here is working fine, i get the live data 
>>> http://www.hivemq.com/demos/websocket-client/
>>>
>>> do i have to run my local mosquitto installation also with ssl/tls or is 
>>> there another way to get it working?
>>>
>>> regards,
>>> chris
>>>
>>> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 20:44:02 UTC+1:
>>>
 I'm using the attached file, which I found somewhere here in this user 
 forum. 
 I've slightly adapted it to bette fit my needs. 

 Don't get confused by the filed name 'EmptyReal'. That was just a spare 
 field I had in my database.

 The calculation of the theoretical radiation level is not 100% perfect, 
 but it does the job.


 grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 20:05:55 UTC+1:

> ok, i will try it locally before, but vserver is also a good (cheap) 
> option :-)
>
> another question to you: how do you calculate sun hours on your site, 
> is it from here? https://github.com/gjr80/weewx-weewx-wd
>
> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 19:23:40 UTC+1:
>
>> No, I didn't.
>>
>> I'm (unfortunately) sitting behind fiberglass without a static IPv4. 
>> So I anyway had to rent a vServer for running my own tunneling 
>> solution for my local webcam.
>>
>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 19:12:12 
>> UTC+1:
>>
>>> hi manfred,
>>>
>>> did you try to run the broker locally before? 
>>>
>>> i have a static ip with symmetric bandwidth. or are there other 
>>> reasons why it doesnt work?
>>>
>>> regards,
>>> chris
>>>
>>> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 15:16:35 UTC+1:
>>>
 Hi Chris,
 I've been in a similar situation to you.
 My web hosting service didn't allow me to run a MQTT broker and the 
 (free) public brokers didn't perform very well. The majority of MQTT 
 packages got lost and were not delivered to the web client.
 So in the end I've decided to rent an additional vServer and run my 
 own MQTT broker. The setup was really easy, but there's a server cost 
 of 
 approx. 2€ per month.

 Manfred  

 kk44...@gmail.com schrieb am Mittwoch, 10. März 2021 um 11:59:33 
 UTC+1:

> You need a publicly available MQTT broker. Either you install one 
> on your webhoster's webspace (if possible), or you use a public 
> broker like 
> test.mosquitto.org.
>
> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 07:46:52 
> UTC+1:
>
>> hello,
>>
>> i am uploading the reports via FTP to my webhoster. can i use 
>> mqtt then for live data oder do i need a locally webserver?
>>
>> regards,
>> 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/d40856a9-6a35-4a27-8430-5a6e53654ce5n%40googlegroups.com.

#
#Copyright (c) 2009-2015 Tom Keffer 
#
#See the file LICENSE.txt for your full rights.
#

"""User extensions module

This module is imported from the main executable, so anything put here will be
executed before anything else happens. This makes it a good place to put user
extensions.
"""

import locale
import schemas.wview
# This will use the locale specified by the environment variable 'LANG'
# Other options are possible. See:
# http://docs.python.org/2/library/locale.html#locale.setlocale
locale.setlocale(locale.LC_ALL, '')

schema_extended = schemas.wview.schema + [('appTemp', 'REAL'), ('windrun',