[weewx-user] Re: [Belchertown] Daily/Monthly Snapshots Not Working

[Andre]

Thanks for your reply, Pat.
It's solved. https://groups.google.com/forum/#!topic/weewx-user/0d7_nXWin7I


Am Sonntag, 12. Juli 2020 03:34:17 UTC+2 schrieb Pat:
>
> That's weird that those tags aren't working. Those are default weewx tags 
> (not Belchertown skin specific).
>
> Any errors in your syslog?
>
> On Thursday, July 9, 2020 at 2:29:22 AM UTC-4, Andre wrote:
>>
>> After I tried to correct a too high rainRate value, the daily and monthly 
>> snapshot is no longer updated. You could see it here 
>> www.wetter-norderstedt.de.
>> My HighCharts seems to be working fine. Maybe there is a connection to 
>> this forum post 
>> 
>> @Pat: If you are reading this, maybe you have an idea to solve the issue?
>>
>>

-- 
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/b6d31521-d2dd-4bfd-9879-af10306f8c59o%40googlegroups.com.

[weewx-user] Re: [Belchertown] Daily/Monthly Snapshots Not Working

[Pat]

That's weird that those tags aren't working. Those are default weewx tags 
(not Belchertown skin specific).

Any errors in your syslog?

On Thursday, July 9, 2020 at 2:29:22 AM UTC-4, Andre wrote:
>
> After I tried to correct a too high rainRate value, the daily and monthly 
> snapshot is no longer updated. You could see it here 
> www.wetter-norderstedt.de.
> My HighCharts seems to be working fine. Maybe there is a connection to this 
> forum post 
> 
> @Pat: If you are reading this, maybe you have an idea to solve the issue?
>
>

-- 
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/345b33b4-eaf8-4070-ad0f-eaf14270b05ao%40googlegroups.com.

[weewx-user] Y-Axis label on combined plot?

[Rob Cranfill]

I have combined my basement ("inside") temperature and humidity plots into 
one graph - cuz I kinda don't look at that much, so why take up space with 
two graphs? - and I can't figure out how to change the y-axis label. (I 
realize I am kinda plotting apples and oranges, here, in that they are 
different units. so sue me. ;-) )

In Seasons' skin.conf:

[[[daytemphumin]]]
inTemp
inHumidity

and it more or less Does The Right Thing, but (from 
http://robcranfill.net/weather/daytemphumin.png)


I'd like that "%" label in the upper left corner to be, oh, "°F / %" or 
something like that.

Ideas?

This is WeeWX 4.1.1, if that matters.

Thanks!

-- 
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/593412ba-4986-465a-a521-a39768ab5febo%40googlegroups.com.

[weewx-user] Re: Public webpage using MQTT from weewx

[Michael Sanphillipo]

Did you ever get a response on this?

On Saturday, February 29, 2020 at 5:12:36 PM UTC-5, Radek Dohnal wrote:
>
> Hi.
> I Finally setup my cloud MQTT broker (flespi) and create bridge between 
> local MosquitoMQTT and cloud Flespi. Thats work fine, topis weather/loop 
> from Mosquito is sucesfully recieved in Flespi (I can see it in Subscriber 
> part). But when I try to to connect Belcherol skin webpage to this 
> FlespiMQTT, it stuck on "Connecting to weather station real time data."
> My skin.conf:
> # MQTT Websockets defaults
>
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = "
> ntLHZqh9S2DdCC5fYyQ6x0utCM07cSln9WUYc0VSSoWkOPpDb3zwTUQjuEfwlqKk:@mqtt.flespi.io
>  
> "
> mqtt_websockets_port = 80
> mqtt_websockets_ssl = 0
> mqtt_websockets_topic = "weather/loop"
> disconnect_live_website_visitor = 180
>
> Flespi has no password, but name/token generated (
> https://flespi.com/kb/tokens-access-keys-to-flespi-platform)
> Port for noSSL websocket is 80 (https://flespi.com/mqtt-api)
>
> Do you know where is the problem?
>
> Dne čtvrtek 21. listopadu 2019 6:27:02 UTC+1 Radek Dohnal napsal(a):
>>
>> Hello.
>> What is the safe way how to use public webpage with my meteo data (on 
>> public site) together with weex sending MQTT data on my local home network ?
>> I would like to use MQTT from my weewx (running on my home network). But 
>> I dont wont to open any port from my home network to the internet.
>> Now Im using FTP to transfer data (HTML_ROOT folder from my local RaspPI 
>> where weewx runnig) to public site where i rent a space for my webpages. 
>> But without MQTT.
>>
>

-- 
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/66c59551-ee27-4004-9edb-c817bd87364co%40googlegroups.com.

[weewx-user] Belchertown MQTT using flespi.io

[Michael Sanphillipo]

Is anyone using flespi.io as their MQTT broker that can help me with how to 
set up the server address configuration?

-- 
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/ec2405b2-8fd5-46b7-8441-a81c51d60af1o%40googlegroups.com.

Re: [weewx-user] Re: Unable to start Weewx

[Michael Grossie]

I will use wee_config.

Michael - via Honor 7

On Sat, Jul 11, 2020, 5:38 PM Tom Keffer  wrote:

> Please don't edit weewx.conf directly. You're likely to make a mistake.
> Use wee_config:
>
> *cd /home/weewx*
> *sudo python3 ./bin/wee_config --reconfigure*
>
>
> On Sat, Jul 11, 2020 at 3:13 PM Michael Grossie 
> wrote:
>
>> There was/is no Station Type described in the config file. I found it
>> interesting when going through the install the weewx.conf file did not
>> launch so that I could input that information.
>> I'll edit the information in the weewx.conf file and see what happens -
>>
>> Thanks
>>
>>
>> Michael H Grossie
>> mhgros...@sbcglobal.net
>>
>>
>> On Sat, Jul 11, 2020 at 4:56 PM Tom Keffer  wrote:
>>
>>> Actually, it looks like just the opposite: you may or may not have an
>>> appropriate block in weewx.conf, but you definitely have not specified a
>>> station type for option 'station'. Use utility wee_config to fix:
>>>
>>> *cd /home/weewx*
>>> *sudo python3 ./bin/wee_config --reconfigure*
>>>
>>> As for why it is running python 2, it will run whatever the "shebang"
>>> line on weewxd specifies. This is the very first line of the file. I'm
>>> betting that you ran setup.py without specifying a version of Python, so it
>>> went with the default on your system, python 2.
>>>
>>> To fix, either follow vince's suggestion and explicitly give the version
>>> of python:
>>>
>>> *sudo python3 ./bin/weewxd*
>>>
>>> Or, alternatively, you can start all over and reinstall, but this time
>>> explicitly specify the version of python you want to use:
>>>
>>> *sudo python3 ./setup.py install*
>>>
>>> setup.py will install a shebang line reflecting whatever you used to
>>> invoke it. In this case, python 3.
>>>
>>> -tk
>>>
>>> On Sat, Jul 11, 2020 at 1:53 PM vince  wrote:
>>>
 On Saturday, July 11, 2020 at 12:49:15 PM UTC-7, Michael Grossie wrote:
>
> Raspbian Stretch
> Python v2.7, v3.5, v3.8.3
> Default (for root) v3.8.3
> Raspberry Pi  2 Model B
> WeeWX v4.1.1
>
>
>
 Weewx doesn't currently care which python you use, as long as you have
 that python's prerequisites installed.  You can install with python2/pip or
 python3/pip3 either way as long as you're consistent.

 Tom usually gives different instructions, but I've found here that
 explicitly calling the python I want and the pip I want makes things more
 known good.  So for me here I'd do "pip3 install whatever" and "python3
 setup.py build ; python3 setup.py install" rather than expecting weewx to
 figure out which python I want to use.

 That said, the error message looks to me like you specified your
 desired Station type, but have no block in weewx.conf defining that kind of
 station and how it works.   Check that first before messing around with any
 python stuff.  Change one thing at a time so you don't lose track of what
 you changed.

 You didn't mention what kind of station you have, so I can't help much
 more there.  Usual 'how to report a problem' stuff applies.

 --
 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/f127e438-65fd-41d6-a635-cc7e4565e5f7o%40googlegroups.com
 
 .

>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/nDTCR1aXMYY/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBQGjqwpgriqM1t7XrEe4crzhBQprVY4aRHkuq%3DAJ6W3w%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/CAJBcQpWTQn8-X8ZuvjDLq3gswfBapvBqT12kVx6ycsZNjTfrRg%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" 

Re: [weewx-user] Re: Unable to start Weewx

[Tom Keffer]

Please don't edit weewx.conf directly. You're likely to make a mistake. Use
wee_config:

*cd /home/weewx*
*sudo python3 ./bin/wee_config --reconfigure*


On Sat, Jul 11, 2020 at 3:13 PM Michael Grossie 
wrote:

> There was/is no Station Type described in the config file. I found it
> interesting when going through the install the weewx.conf file did not
> launch so that I could input that information.
> I'll edit the information in the weewx.conf file and see what happens -
>
> Thanks
>
>
> Michael H Grossie
> mhgros...@sbcglobal.net
>
>
> On Sat, Jul 11, 2020 at 4:56 PM Tom Keffer  wrote:
>
>> Actually, it looks like just the opposite: you may or may not have an
>> appropriate block in weewx.conf, but you definitely have not specified a
>> station type for option 'station'. Use utility wee_config to fix:
>>
>> *cd /home/weewx*
>> *sudo python3 ./bin/wee_config --reconfigure*
>>
>> As for why it is running python 2, it will run whatever the "shebang"
>> line on weewxd specifies. This is the very first line of the file. I'm
>> betting that you ran setup.py without specifying a version of Python, so it
>> went with the default on your system, python 2.
>>
>> To fix, either follow vince's suggestion and explicitly give the version
>> of python:
>>
>> *sudo python3 ./bin/weewxd*
>>
>> Or, alternatively, you can start all over and reinstall, but this time
>> explicitly specify the version of python you want to use:
>>
>> *sudo python3 ./setup.py install*
>>
>> setup.py will install a shebang line reflecting whatever you used to
>> invoke it. In this case, python 3.
>>
>> -tk
>>
>> On Sat, Jul 11, 2020 at 1:53 PM vince  wrote:
>>
>>> On Saturday, July 11, 2020 at 12:49:15 PM UTC-7, Michael Grossie wrote:

 Raspbian Stretch
 Python v2.7, v3.5, v3.8.3
 Default (for root) v3.8.3
 Raspberry Pi  2 Model B
 WeeWX v4.1.1



>>> Weewx doesn't currently care which python you use, as long as you have
>>> that python's prerequisites installed.  You can install with python2/pip or
>>> python3/pip3 either way as long as you're consistent.
>>>
>>> Tom usually gives different instructions, but I've found here that
>>> explicitly calling the python I want and the pip I want makes things more
>>> known good.  So for me here I'd do "pip3 install whatever" and "python3
>>> setup.py build ; python3 setup.py install" rather than expecting weewx to
>>> figure out which python I want to use.
>>>
>>> That said, the error message looks to me like you specified your desired
>>> Station type, but have no block in weewx.conf defining that kind of station
>>> and how it works.   Check that first before messing around with any python
>>> stuff.  Change one thing at a time so you don't lose track of what you
>>> changed.
>>>
>>> You didn't mention what kind of station you have, so I can't help much
>>> more there.  Usual 'how to report a problem' stuff applies.
>>>
>>> --
>>> 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/f127e438-65fd-41d6-a635-cc7e4565e5f7o%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/nDTCR1aXMYY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBQGjqwpgriqM1t7XrEe4crzhBQprVY4aRHkuq%3DAJ6W3w%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/CAJBcQpWTQn8-X8ZuvjDLq3gswfBapvBqT12kVx6ycsZNjTfrRg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

RE: [weewx-user] Issue with exfoliation weewx 4.1.1 and python3 - I think?

['Scott Weis' via weewx-user]

I changed the first one and all my errors went away.  I’m not sure I was having 
the second part of the error.

 

 

Thanks,

Scott KB2EAR

http://weather.kb2ear.net/exfoliation

 

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Saturday, July 11, 2020 6:07 PM
To: weewx-user 
Subject: Re: [weewx-user] Issue with exfoliation weewx 4.1.1 and python3 - I 
think?

 

For the first error, in file index.html.tmpl, line 226, change this

 

#if $varExists('trend') and $trend.windSpeed.raw is not None

  $get_windspeed_trend($trend.windSpeed.formatted)

#end if

 

to this

 

#if $varExists('trend') and $trend.windSpeed.raw is not None

  $get_windspeed_trend($trend.windSpeed.raw)

#end if

 

For the second error, there are a number of candidates that could be causing 
this problem. I'd go with this one. Change this

 

#if $show_pop



  #if $period.pop.raw > 0

  $period.pop.format('%.0f',' ')

  #end if



  #if $period.qpf.raw > 0

  $period.qpf.nolabel('%.2f',' ') 

  #end if



  #if $period.qsf.raw > 0

  $period.qsf.nolabel('%.2f',' ') 

  #end if



#end if

 

to this

 

#if $show_pop



  #if $period.pop.raw is not None and $period.pop.raw > 0

  $period.pop.format('%.0f',' ')

  #end if



  #if $period.qpf.raw is not None and $period.qpf.raw > 0

  $period.qpf.nolabel('%.2f',' ') 

  #end if



  #if $period.qsf.raw is not None and $period.qsf.raw > 0

  $period.qsf.nolabel('%.2f',' ') 

  #end if



#end if

 

But I could be wrong on that.

 

-tk

 

 

On Thu, Jun 4, 2020 at 6:14 AM Mike Thompson mailto:mike.thomp...@noworries.plus.com> > wrote:

Hi Fourm & Matt,

 

I'm getting an issue with exfoliation to do with data types the message in the 
log is  "Reason: '>' not supported between instances of 'NoneType' and 'int'"

 

I've just migrated from 3.9.1 on RPI Ib running Wheezy.

Upgraded to 3.9.1 on RPI 1B running Buster with Python 2. All was working OK

Upgraded to 4.1.1 on Python3 and the issue occurred.

As apart of the upgrade to 4.1.1 on Python3 I had to make changes to alarm.py 
etc to update python2 code to python3

Installed latest exfoliation (0.45)  and forecast (3.4.0b1) extensions. It 
looks like exfoliation has over written my customisations so I think it's "out 
of the box"

 

Seasons is working - pages and graphs generate OK.

Forecast seems to be working. Sample pages generated OK, most without data but 
UK met office data on forecast-periods page. Time stamp on files in 
public_html/forecast are recent i.e post upgrade.

Some Exfoliation pages are generated OK and some not, index and forecast are 
not but history, almanac and links are.

 

>From syslog it looks like get_windspeed_trend is causing the issue

Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: Generate failed 
with exception ''
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:  Ignoring 
template /home/weewx/skins/exfoliation/index.html.tmpl
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:  Reason: 
'>' not supported between instances of 'str' and 'int'
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:   Traceback 
(most recent call last):
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in generate
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_exfoliation_index_html_tmpl.py", line 1292, in respond
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_exfoliation_index_html_tmpl.py", line 497, in 
__errorCatcher43
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"", line 1, in 
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_exfoliation_index_html_tmpl.py", line 187, in 
get_windspeed_trend
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:   
TypeError: '>' not supported between instances of 'str' and 'int'

from index.html.tmpl;

#def get_windspeed_trend($x)
#if $x > 0
  
#elif $x < 0
  
#end if
#end def

 

I'm also seeing;


Jun  4 13:01:32 weepi /weewxd: forecast: ReportThread: _get_stats: '>' not 
supported between instances of 'NoneType' and 'float'

 

around 50 of them followed by

Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: Generate failed 
with exception ''
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:  Ignoring 
template /home/weewx/skins/exfoliation/forecast.html.tmpl
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:  Reason: 
'>' not supported between instances of 'NoneType' and 'int'
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:   Traceback 

Re: [weewx-user] Re: Unable to start Weewx

[Michael Grossie]

There was/is no Station Type described in the config file. I found it
interesting when going through the install the weewx.conf file did not
launch so that I could input that information.
I'll edit the information in the weewx.conf file and see what happens -

Thanks


Michael H Grossie
mhgros...@sbcglobal.net


On Sat, Jul 11, 2020 at 4:56 PM Tom Keffer  wrote:

> Actually, it looks like just the opposite: you may or may not have an
> appropriate block in weewx.conf, but you definitely have not specified a
> station type for option 'station'. Use utility wee_config to fix:
>
> *cd /home/weewx*
> *sudo python3 ./bin/wee_config --reconfigure*
>
> As for why it is running python 2, it will run whatever the "shebang" line
> on weewxd specifies. This is the very first line of the file. I'm betting
> that you ran setup.py without specifying a version of Python, so it went
> with the default on your system, python 2.
>
> To fix, either follow vince's suggestion and explicitly give the version
> of python:
>
> *sudo python3 ./bin/weewxd*
>
> Or, alternatively, you can start all over and reinstall, but this time
> explicitly specify the version of python you want to use:
>
> *sudo python3 ./setup.py install*
>
> setup.py will install a shebang line reflecting whatever you used to
> invoke it. In this case, python 3.
>
> -tk
>
> On Sat, Jul 11, 2020 at 1:53 PM vince  wrote:
>
>> On Saturday, July 11, 2020 at 12:49:15 PM UTC-7, Michael Grossie wrote:
>>>
>>> Raspbian Stretch
>>> Python v2.7, v3.5, v3.8.3
>>> Default (for root) v3.8.3
>>> Raspberry Pi  2 Model B
>>> WeeWX v4.1.1
>>>
>>>
>>>
>> Weewx doesn't currently care which python you use, as long as you have
>> that python's prerequisites installed.  You can install with python2/pip or
>> python3/pip3 either way as long as you're consistent.
>>
>> Tom usually gives different instructions, but I've found here that
>> explicitly calling the python I want and the pip I want makes things more
>> known good.  So for me here I'd do "pip3 install whatever" and "python3
>> setup.py build ; python3 setup.py install" rather than expecting weewx to
>> figure out which python I want to use.
>>
>> That said, the error message looks to me like you specified your desired
>> Station type, but have no block in weewx.conf defining that kind of station
>> and how it works.   Check that first before messing around with any python
>> stuff.  Change one thing at a time so you don't lose track of what you
>> changed.
>>
>> You didn't mention what kind of station you have, so I can't help much
>> more there.  Usual 'how to report a problem' stuff applies.
>>
>> --
>> 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/f127e438-65fd-41d6-a635-cc7e4565e5f7o%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/nDTCR1aXMYY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBQGjqwpgriqM1t7XrEe4crzhBQprVY4aRHkuq%3DAJ6W3w%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/CAJBcQpWTQn8-X8ZuvjDLq3gswfBapvBqT12kVx6ycsZNjTfrRg%40mail.gmail.com.

Re: [weewx-user] Issue with exfoliation weewx 4.1.1 and python3 - I think?

[Tom Keffer]

For the first error, in file index.html.tmpl, line 226, change this

#if $varExists('trend') and $trend.windSpeed.raw is not None
  $get_windspeed_trend($trend.windSpeed.formatted)
#end if


to this

#if $varExists('trend') and $trend.windSpeed.raw is not None
  $get_windspeed_trend($trend.windSpeed.raw)
#end if


For the second error, there are a number of candidates that could be
causing this problem. I'd go with this one. Change this

#if $show_pop

  #if $period.pop.raw > 0
  $period.pop.format('%.0f',' ')
  #end if

  #if $period.qpf.raw > 0
  $period.qpf.nolabel('%.2f',' ') 
  #end if

  #if $period.qsf.raw > 0
  $period.qsf.nolabel('%.2f',' ') 
  #end if

#end if


to this

#if $show_pop

  #if $period.pop.raw is not None and $period.pop.raw > 0
  $period.pop.format('%.0f',' ')
  #end if

  #if $period.qpf.raw is not None and $period.qpf.raw > 0
  $period.qpf.nolabel('%.2f',' ') 
  #end if

  #if $period.qsf.raw is not None and $period.qsf.raw > 0
  $period.qsf.nolabel('%.2f',' ') 
  #end if

#end if


But I could be wrong on that.

-tk


On Thu, Jun 4, 2020 at 6:14 AM Mike Thompson <
mike.thomp...@noworries.plus.com> wrote:

> Hi Fourm & Matt,
>
> I'm getting an issue with exfoliation to do with data types the message in
> the log is  "Reason: '>' not supported between instances of 'NoneType' and
> 'int'"
>
> I've just migrated from 3.9.1 on RPI Ib running Wheezy.
> Upgraded to 3.9.1 on RPI 1B running Buster with Python 2. All was working
> OK
> Upgraded to 4.1.1 on Python3 and the issue occurred.
> As apart of the upgrade to 4.1.1 on Python3 I had to make changes to
> alarm.py etc to update python2 code to python3
> Installed latest exfoliation (0.45)  and forecast (3.4.0b1) extensions.
> It looks like exfoliation has over written my customisations so I think
> it's "out of the box"
>
> Seasons is working - pages and graphs generate OK.
> Forecast seems to be working. Sample pages generated OK, most without data
> but UK met office data on forecast-periods page. Time stamp on files in
> public_html/forecast are recent i.e post upgrade.
> Some Exfoliation pages are generated OK and some not, index and forecast
> are not but history, almanac and links are.
>
> From syslog it looks like get_windspeed_trend is causing the issue
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: Generate
> failed with exception ''
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> Ignoring template /home/weewx/skins/exfoliation/index.html.tmpl
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> Reason: '>' not supported between instances of 'str' and 'int'
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> Traceback (most recent call last):
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in generate
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> unicode_string = compiled_template.respond()
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 1292, in
> respond
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 497, in
> __errorCatcher43
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> File "", line 1, in 
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 187, in
> get_windspeed_trend
> Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> TypeError: '>' not supported between instances of 'str' and 'int'
> from index.html.tmpl;
> #def get_windspeed_trend($x)
> #if $x > 0
>   
> #elif $x < 0
>   
> #end if
> #end def
>
> I'm also seeing;
>
> Jun  4 13:01:32 weepi /weewxd: forecast: ReportThread: _get_stats: '>' not
> supported between instances of 'NoneType' and 'float'
>
> around 50 of them followed by
> Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: Generate
> failed with exception ''
> Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> Ignoring template /home/weewx/skins/exfoliation/forecast.html.tmpl
> Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> Reason: '>' not supported between instances of 'NoneType' and 'int'
> Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> Traceback (most recent call last):
> Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in generate
> Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> unicode_string = compiled_template.respond()
> Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: 
> File 

Re: [weewx-user] Re: Unable to start Weewx

[Tom Keffer]

Actually, it looks like just the opposite: you may or may not have an
appropriate block in weewx.conf, but you definitely have not specified a
station type for option 'station'. Use utility wee_config to fix:

*cd /home/weewx*
*sudo python3 ./bin/wee_config --reconfigure*

As for why it is running python 2, it will run whatever the "shebang" line
on weewxd specifies. This is the very first line of the file. I'm betting
that you ran setup.py without specifying a version of Python, so it went
with the default on your system, python 2.

To fix, either follow vince's suggestion and explicitly give the version of
python:

*sudo python3 ./bin/weewxd*

Or, alternatively, you can start all over and reinstall, but this time
explicitly specify the version of python you want to use:

*sudo python3 ./setup.py install*

setup.py will install a shebang line reflecting whatever you used to invoke
it. In this case, python 3.

-tk

On Sat, Jul 11, 2020 at 1:53 PM vince  wrote:

> On Saturday, July 11, 2020 at 12:49:15 PM UTC-7, Michael Grossie wrote:
>>
>> Raspbian Stretch
>> Python v2.7, v3.5, v3.8.3
>> Default (for root) v3.8.3
>> Raspberry Pi  2 Model B
>> WeeWX v4.1.1
>>
>>
>>
> Weewx doesn't currently care which python you use, as long as you have
> that python's prerequisites installed.  You can install with python2/pip or
> python3/pip3 either way as long as you're consistent.
>
> Tom usually gives different instructions, but I've found here that
> explicitly calling the python I want and the pip I want makes things more
> known good.  So for me here I'd do "pip3 install whatever" and "python3
> setup.py build ; python3 setup.py install" rather than expecting weewx to
> figure out which python I want to use.
>
> That said, the error message looks to me like you specified your desired
> Station type, but have no block in weewx.conf defining that kind of station
> and how it works.   Check that first before messing around with any python
> stuff.  Change one thing at a time so you don't lose track of what you
> changed.
>
> You didn't mention what kind of station you have, so I can't help much
> more there.  Usual 'how to report a problem' stuff applies.
>
> --
> 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/f127e438-65fd-41d6-a635-cc7e4565e5f7o%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/CAPq0zEBQGjqwpgriqM1t7XrEe4crzhBQprVY4aRHkuq%3DAJ6W3w%40mail.gmail.com.

RE: [weewx-user] Re: Issue with exfoliation weewx 4.1.1 and python3 - I think?

['Scott Weis' via weewx-user]

I’m having the exact same issue

 

From: weewx-user@googlegroups.com  On Behalf Of 
Mike Thompson
Sent: Saturday, June 6, 2020 6:16 AM
To: weewx-user 
Subject: [weewx-user] Re: Issue with exfoliation weewx 4.1.1 and python3 - I 
think?

 

I've had some time to investigate it's the forecast extension that's upsetting 
things. 

Had anyone else had this issue?

 

 


On Thursday, June 4, 2020 at 2:14:53 PM UTC+1, Mike Thompson wrote:

Hi Fourm & Matt,

 

I'm getting an issue with exfoliation to do with data types the message in the 
log is  "Reason: '>' not supported between instances of 'NoneType' and 'int'"

 

I've just migrated from 3.9.1 on RPI Ib running Wheezy.

Upgraded to 3.9.1 on RPI 1B running Buster with Python 2. All was working OK

Upgraded to 4.1.1 on Python3 and the issue occurred.

As apart of the upgrade to 4.1.1 on Python3 I had to make changes to alarm.py 
etc to update python2 code to python3

Installed latest exfoliation (0.45)  and forecast (3.4.0b1) extensions. It 
looks like exfoliation has over written my customisations so I think it's "out 
of the box"

 

Seasons is working - pages and graphs generate OK.

Forecast seems to be working. Sample pages generated OK, most without data but 
UK met office data on forecast-periods page. Time stamp on files in 
public_html/forecast are recent i.e post upgrade.

Some Exfoliation pages are generated OK and some not, index and forecast are 
not but history, almanac and links are.

 

>From syslog it looks like get_windspeed_trend is causing the issue

Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: Generate failed 
with exception ''
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:  Ignoring 
template /home/weewx/skins/exfoliation/index.html.tmpl
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:  Reason: 
'>' not supported between instances of 'str' and 'int'
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:   Traceback 
(most recent call last):
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in generate
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_exfoliation_index_html_tmpl.py", line 1292, in respond
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_exfoliation_index_html_tmpl.py", line 497, in 
__errorCatcher43
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"", line 1, in 
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_exfoliation_index_html_tmpl.py", line 187, in 
get_windspeed_trend
Jun  4 13:01:27 weepi weewx[8650] ERROR weewx.cheetahgenerator:   
TypeError: '>' not supported between instances of 'str' and 'int'

from index.html.tmpl;

#def get_windspeed_trend($x)
#if $x > 0
  
#elif $x < 0
  
#end if
#end def

 

I'm also seeing;


Jun  4 13:01:32 weepi /weewxd: forecast: ReportThread: _get_stats: '>' not 
supported between instances of 'NoneType' and 'float'

 

around 50 of them followed by

Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: Generate failed 
with exception ''
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:  Ignoring 
template /home/weewx/skins/exfoliation/forecast.html.tmpl
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:  Reason: 
'>' not supported between instances of 'NoneType' and 'int'
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:   Traceback 
(most recent call last):
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in generate
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_exfoliation_forecast_html_tmpl.py", line 384, in respond
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1707, in 
_handleCheetahInclude
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:   
self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_exfoliation_forecast_table_inc.py", line 538, in respond
Jun  4 13:01:34 weepi weewx[8650] ERROR weewx.cheetahgenerator:   
TypeError: '>' not supported between instances of 'NoneType' and 'int'

 

It may have something to do with changes and extensions I've made over the 
years. To be fair, I've just bumped along working this out from first 
principles until it worked so it's highly likely I've not 

[weewx-user] Re: Unable to start Weewx

[vince]

On Saturday, July 11, 2020 at 12:49:15 PM UTC-7, Michael Grossie wrote:
>
> Raspbian Stretch
> Python v2.7, v3.5, v3.8.3
> Default (for root) v3.8.3
> Raspberry Pi  2 Model B
> WeeWX v4.1.1
>
>
>
Weewx doesn't currently care which python you use, as long as you have that 
python's prerequisites installed.  You can install with python2/pip or 
python3/pip3 either way as long as you're consistent.

Tom usually gives different instructions, but I've found here that 
explicitly calling the python I want and the pip I want makes things more 
known good.  So for me here I'd do "pip3 install whatever" and "python3 
setup.py build ; python3 setup.py install" rather than expecting weewx to 
figure out which python I want to use.

That said, the error message looks to me like you specified your desired 
Station type, but have no block in weewx.conf defining that kind of station 
and how it works.   Check that first before messing around with any python 
stuff.  Change one thing at a time so you don't lose track of what you 
changed.

You didn't mention what kind of station you have, so I can't help much more 
there.  Usual 'how to report a problem' stuff applies.

-- 
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/f127e438-65fd-41d6-a635-cc7e4565e5f7o%40googlegroups.com.

[weewx-user] Unable to start Weewx

[Michael Grossie]

Raspbian Stretch
Python v2.7, v3.5, v3.8.3
Default (for root) v3.8.3
Raspberry Pi  2 Model B
WeeWX v4.1.1

Following WeeWX using setup.py
used "sudo ./bin/weewxd" from inside the /home/weewx directory.
had some problems loading the following - 
sudo apt update 
 # Required 
sudo apt install python3-distutils - *pi@raspberrypi:/ $ sudo apt install 
python3-distutils*
*Reading package lists... Done*
*Building dependency tree   *
*Reading state information... Done*
*E: Unable to locate package python3-distutils*
I was able to download and install "python-distutils-extra" from Debian.  
Could not download "python3-distutils-extra_2.40_all.deb."

sudo apt install python3-configobj  -Loaded without issue
 sudo apt install python3-pil - Loaded without issue
sudo apt install python3-serial - Loaded without issue
sudo apt install python3-usb - Loaded without issue
sudo apt install python3-pip - Loaded without issue
sudo pip3 install cheetah3 - Loaded without issue
 # Optional: for extended almanac information 
sudo apt install python3-ephem - Loaded with out issue
 # Required if you are using MySQL (MariaDB): 
sudo apt install mysql-client - Did not install by choice
sudo apt install python3-mysqldb  - Did not install by choice

When I run the start command (as above and as below) I got :
pi@raspberrypi:/home/weewx $ sudo ./bin/weewxd
Traceback (most recent call last):
  File "./bin/weewxd", line 261, in 
main()
  File "./bin/weewxd", line 148, in main
engine = weewx.engine.StdEngine(config_dict)
  File "/home/weewx/bin/weewx/engine.py", line 69, in __init__
self.setupStation(config_dict)
  File "/home/weewx/bin/weewx/engine.py", line 87, in setupStation
driver = config_dict[station_type]['driver']
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in 
__getitem__
val = dict.__getitem__(self, key)
KeyError: u'unspecified'

Checking the syslog -
pi@raspberrypi:/ $ sudo tail -f /var/log/syslog
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__: File 
"./bin/weewxd", line 148, in main
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__:   
engine = weewx.engine.StdEngine(config_dict)
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 69, in __init__
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__:   
self.setupStation(config_dict)
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 87, in setupStation
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__:   
driver = config_dict[station_type]['driver']
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__: File 
"/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__:   val 
= dict.__getitem__(self, key)
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__:   
KeyError: u'unspecified'
Jul 11 14:04:26 raspberrypi weewx[941] CRITICAL __main__:   Exiting.

It appears that the python-configobj is the problem. It appears to think 
that it should be a version for Python2.7.

In checking the file structure, I find that I have:
/home/weewx
/var/run/weewx.pid 
 /var/log/syslog

Based on this it looks like the install just dumped it all into the 
/home/weewx folder as all the other "required" folders are there.

Suggestions appreciated.

TIA - 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/36322a19-72f6-4136-b62f-77c8336884dfn%40googlegroups.com.

Re: [weewx-user] Wind Data Missing

[Andre]

Thank you very much, dear Tom.
Now it works as expected.
I learned more about weewx again.

Best regards, Andre

Am Samstag, 11. Juli 2020 20:21:19 UTC+2 schrieb Tom Keffer:
>
> My apologies. The option should be
>
> manager = weewx.wxmanager.WXDaySummaryManager
>
> -tk
>
> On Sat, Jul 11, 2020 at 11:18 AM Andre > 
> wrote:
>
>> Thanks for your help, Tom.
>> I got following message:
>>
>> pi@weewx:~ $ sudo wee_database --rebuild-daily
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_sqlite'
>> All daily summaries will be rebuilt.
>> Proceed (y/n)? y
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 1098, in get_object
>> mod = getattr(mod, part)
>> AttributeError: module 'weewx.manager' has no attribute 
>> 'WXDaySummaryManager'
>>
>>
>> During handling of the above exception, another exception occurred:
>>
>>
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_database", line 974, in 
>> main()
>>   File "/usr/share/weewx/wee_database", line 169, in main
>> rebuildDaily(config_dict, db_binding, options)
>>   File "/usr/share/weewx/wee_database", line 264, in rebuildDaily
>> with weewx.manager.open_manager_with_config(config_dict, db_binding, 
>> initialize=True) as dbmanager:
>>   File "/usr/share/weewx/weewx/manager.py", line 692, in 
>> open_manager_with_config
>> return open_manager(manager_dict, initialize)
>>   File "/usr/share/weewx/weewx/manager.py", line 676, in open_manager
>> manager_cls = weeutil.weeutil.get_object(manager_dict['manager'])
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 1102, in get_object
>> "Module '%s' has no attribute '%s' when searching for '%s'" % (mod.
>> __name__, part, module_class))
>> AttributeError: Module 'weewx.manager' has no attribute 
>> 'WXDaySummaryManager' when searching for 
>> 'weewx.manager.WXDaySummaryManager'
>>
>>
>>
>> Am Samstag, 11. Juli 2020 19:59:05 UTC+2 schrieb Tom Keffer:
>>>
>>> It's a subtle error, but you're mixing the old style way of specifying 
>>> and managing a schema with the new way. Try changing the [DataBindings] 
>>> section to look like this:
>>>
>>> [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.WXDaySummaryManager
>>> # The schema defines the structure of the database.
>>> # It is *only* used when the database is created.
>>> #schema = schemas.wview_extended.schema
>>> schema = user.extensions.schema_extended
>>>
>>> Then try rebuilding the daily summaries.
>>>
>>> Sorry. We really should have a better error message.
>>>
>>> -tk
>>>
>>>
>>> In 
>>>
>>> On Sat, Jul 11, 2020 at 5:57 AM Andre  wrote:
>>>
 This is the /usr/share/weewx/user/extensions.py

 #
 #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
 # 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, '')


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






 Am Samstag, 11. Juli 2020 14:16:43 UTC+2 schrieb Tom Keffer:
>
> It looks like you are using a custom schema. May we see it? It should 
> be in /usr/share/weewx/user/extensions.py
>
> -tk
>
> On Fri, Jul 10, 2020 at 10:57 PM Andre  wrote:
>
>> Thanks for reply, Tom.
>>
>> Here is my 
>> [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 = 

Re: [weewx-user] Wind Data Missing

[Tom Keffer]

My apologies. The option should be

manager = weewx.wxmanager.WXDaySummaryManager

-tk

On Sat, Jul 11, 2020 at 11:18 AM Andre  wrote:

> Thanks for your help, Tom.
> I got following message:
>
> pi@weewx:~ $ sudo wee_database --rebuild-daily
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database
> 'archive_sqlite'
> All daily summaries will be rebuilt.
> Proceed (y/n)? y
> Traceback (most recent call last):
>   File "/usr/share/weewx/weeutil/weeutil.py", line 1098, in get_object
> mod = getattr(mod, part)
> AttributeError: module 'weewx.manager' has no attribute
> 'WXDaySummaryManager'
>
>
> During handling of the above exception, another exception occurred:
>
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_database", line 974, in 
> main()
>   File "/usr/share/weewx/wee_database", line 169, in main
> rebuildDaily(config_dict, db_binding, options)
>   File "/usr/share/weewx/wee_database", line 264, in rebuildDaily
> with weewx.manager.open_manager_with_config(config_dict, db_binding,
> initialize=True) as dbmanager:
>   File "/usr/share/weewx/weewx/manager.py", line 692, in
> open_manager_with_config
> return open_manager(manager_dict, initialize)
>   File "/usr/share/weewx/weewx/manager.py", line 676, in open_manager
> manager_cls = weeutil.weeutil.get_object(manager_dict['manager'])
>   File "/usr/share/weewx/weeutil/weeutil.py", line 1102, in get_object
> "Module '%s' has no attribute '%s' when searching for '%s'" % (mod.
> __name__, part, module_class))
> AttributeError: Module 'weewx.manager' has no attribute
> 'WXDaySummaryManager' when searching for
> 'weewx.manager.WXDaySummaryManager'
>
>
>
> Am Samstag, 11. Juli 2020 19:59:05 UTC+2 schrieb Tom Keffer:
>>
>> It's a subtle error, but you're mixing the old style way of specifying
>> and managing a schema with the new way. Try changing the [DataBindings]
>> section to look like this:
>>
>> [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.WXDaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> #schema = schemas.wview_extended.schema
>> schema = user.extensions.schema_extended
>>
>> Then try rebuilding the daily summaries.
>>
>> Sorry. We really should have a better error message.
>>
>> -tk
>>
>>
>> In
>>
>> On Sat, Jul 11, 2020 at 5:57 AM Andre  wrote:
>>
>>> This is the /usr/share/weewx/user/extensions.py
>>>
>>> #
>>> #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
>>> # 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, '')
>>>
>>>
>>> import schemas.wview
>>> schema_extended = schemas.wview.schema + [('appTemp', 'REAL'), (
>>> 'windrun', 'REAL')]
>>>
>>>
>>>
>>>
>>>
>>>
>>> Am Samstag, 11. Juli 2020 14:16:43 UTC+2 schrieb Tom Keffer:

 It looks like you are using a custom schema. May we see it? It should
 be in /usr/share/weewx/user/extensions.py

 -tk

 On Fri, Jul 10, 2020 at 10:57 PM Andre  wrote:

> Thanks for reply, Tom.
>
> Here is my
> [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 = schemas.wview_extended.schema
> schema = user.extensions.schema_extended
>
>
> Am Samstag, 11. Juli 2020 03:26:02 UTC+2 schrieb Tom Keffer:
>>
>> You did not include a log, but on the basis of similar problems, I
>> would bet that you used the wrong combination of schema and 'manager' in
>> your configuration file, 

Re: [weewx-user] Wind Data Missing

[Andre]

Thanks for your help, Tom.
I got following message:

pi@weewx:~ $ sudo wee_database --rebuild-daily
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'
All daily summaries will be rebuilt.
Proceed (y/n)? y
Traceback (most recent call last):
  File "/usr/share/weewx/weeutil/weeutil.py", line 1098, in get_object
mod = getattr(mod, part)
AttributeError: module 'weewx.manager' has no attribute 
'WXDaySummaryManager'


During handling of the above exception, another exception occurred:


Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 974, in 
main()
  File "/usr/share/weewx/wee_database", line 169, in main
rebuildDaily(config_dict, db_binding, options)
  File "/usr/share/weewx/wee_database", line 264, in rebuildDaily
with weewx.manager.open_manager_with_config(config_dict, db_binding, 
initialize=True) as dbmanager:
  File "/usr/share/weewx/weewx/manager.py", line 692, in 
open_manager_with_config
return open_manager(manager_dict, initialize)
  File "/usr/share/weewx/weewx/manager.py", line 676, in open_manager
manager_cls = weeutil.weeutil.get_object(manager_dict['manager'])
  File "/usr/share/weewx/weeutil/weeutil.py", line 1102, in get_object
"Module '%s' has no attribute '%s' when searching for '%s'" % (mod.
__name__, part, module_class))
AttributeError: Module 'weewx.manager' has no attribute 
'WXDaySummaryManager' when searching for 'weewx.manager.WXDaySummaryManager'



Am Samstag, 11. Juli 2020 19:59:05 UTC+2 schrieb Tom Keffer:
>
> It's a subtle error, but you're mixing the old style way of specifying and 
> managing a schema with the new way. Try changing the [DataBindings] section 
> to look like this:
>
> [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.WXDaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> #schema = schemas.wview_extended.schema
> schema = user.extensions.schema_extended
>
> Then try rebuilding the daily summaries.
>
> Sorry. We really should have a better error message.
>
> -tk
>
>
> In 
>
> On Sat, Jul 11, 2020 at 5:57 AM Andre > 
> wrote:
>
>> This is the /usr/share/weewx/user/extensions.py
>>
>> #
>> #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
>> # 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, '')
>>
>>
>> import schemas.wview
>> schema_extended = schemas.wview.schema + [('appTemp', 'REAL'), ('windrun'
>> , 'REAL')]
>>
>>
>>
>>
>>
>>
>> Am Samstag, 11. Juli 2020 14:16:43 UTC+2 schrieb Tom Keffer:
>>>
>>> It looks like you are using a custom schema. May we see it? It should be 
>>> in /usr/share/weewx/user/extensions.py
>>>
>>> -tk
>>>
>>> On Fri, Jul 10, 2020 at 10:57 PM Andre  wrote:
>>>
 Thanks for reply, Tom.

 Here is my 
 [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 = schemas.wview_extended.schema
 schema = user.extensions.schema_extended


 Am Samstag, 11. Juli 2020 03:26:02 UTC+2 schrieb Tom Keffer:
>
> You did not include a log, but on the basis of similar problems, I 
> would bet that you used the wrong combination of schema and 'manager' in 
> your configuration file, weewx.conf.
>
> Please post the section [DataBindings] in weewx.conf
>
> -tk
>
> On Fri, Jul 10, 2020 at 7:26 AM Andre  wrote:
>
>> Hardware: Davis Vantage Vue
>> Raspberry Pi 4: Install with DEB package
>> WeeWX: 4.1.1
>> Skin: Belchertown 1.2b6
>>

Re: [weewx-user] Wind Data Missing

[Tom Keffer]

It's a subtle error, but you're mixing the old style way of specifying and
managing a schema with the new way. Try changing the [DataBindings] section
to look like this:

[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.WXDaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
#schema = schemas.wview_extended.schema
schema = user.extensions.schema_extended

Then try rebuilding the daily summaries.

Sorry. We really should have a better error message.

-tk


In

On Sat, Jul 11, 2020 at 5:57 AM Andre  wrote:

> This is the /usr/share/weewx/user/extensions.py
>
> #
> #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
> # 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, '')
>
>
> import schemas.wview
> schema_extended = schemas.wview.schema + [('appTemp', 'REAL'), ('windrun',
> 'REAL')]
>
>
>
>
>
>
> Am Samstag, 11. Juli 2020 14:16:43 UTC+2 schrieb Tom Keffer:
>>
>> It looks like you are using a custom schema. May we see it? It should be
>> in /usr/share/weewx/user/extensions.py
>>
>> -tk
>>
>> On Fri, Jul 10, 2020 at 10:57 PM Andre  wrote:
>>
>>> Thanks for reply, Tom.
>>>
>>> Here is my
>>> [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 = schemas.wview_extended.schema
>>> schema = user.extensions.schema_extended
>>>
>>>
>>> Am Samstag, 11. Juli 2020 03:26:02 UTC+2 schrieb Tom Keffer:

 You did not include a log, but on the basis of similar problems, I
 would bet that you used the wrong combination of schema and 'manager' in
 your configuration file, weewx.conf.

 Please post the section [DataBindings] in weewx.conf

 -tk

 On Fri, Jul 10, 2020 at 7:26 AM Andre  wrote:

> Hardware: Davis Vantage Vue
> Raspberry Pi 4: Install with DEB package
> WeeWX: 4.1.1
> Skin: Belchertown 1.2b6
>
> Actually, I just wanted to quickly correct a too high value of the
> rain rate. So I did:
>
> 1. wee_database --drop-daily
> 2. wee_database --rebuild-daily
> 3. wee_database --update
>
> After that the too high rain rate value was corrected, but the
> "snapshot" area in the Belchertown skin did not work anymore.
> [image: weewx01.png]
>
> So I uninstalled and reinstalled the Belchertown skin. After that
> everything worked as desired, but now the wind values were missing. Also
> the NOAA files were completely missing the wind data.
>
> I deleted all NOAA files and hoped that the wind data would be
> generated. Unfortunately without success.
> http://www.wetter-norderstedt.de/NOAA/NOAA-2020-07.txt
>
> Can someone help me to solve the problem?
>
> Best regards, Andre
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/eecad34a-41b2-4087-9221-460fffce4ee9o%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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> 

[weewx-user] Air quality in Belchertown skin

[didier....@gmail.com]

Hi

My site is based on Belchertown skin 1.2b6, thank's Pat

I would like to have air quality datas.
Is it possible to have Air Quality information on Belchertown skin, and 
which sensor is available and reliable (with a raisonnable price of course)?

Many thanks
Didier
meteo-auffargis.decoodt.eu 

-- 
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/ad649e26-1c28-4732-b57e-9c2738a7c88dn%40googlegroups.com.

Re: [weewx-user] Re: aqi_backfill gives error

[Rahul Bedi]

Sorry for the late reply. I tried running the latest rev with weewx shut
and here is where I wound up before it hung.

pi@PrideWeatherStation:/usr/share/weewx $ sudo ./aqi_backfill --start_time
1478193919 --end_time 1592548226 /etc/weewx/weewx.conf
Starting backfill from 1478193919 2016-11-03 22:55:19
No handlers could be found for logger "weewx.manager"
processed 30 days... 1480785900 2016-12-03 22:55:00
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
  File "/usr/share/weewx/weewx/drivers/wmr200.py", line 1229, in run
_ = self.usb_device.read_device()
  File "/usr/share/weewx/weewx/drivers/wmr200.py", line 259, in read_device
raise weewx.WeeWxIOError(msg)
WeeWxIOError: read_device() USB Error Reason:[Errno 110] Operation timed out

processed 60 days... 1483377900 2017-01-02 22:55:00
processed 90 days... 1485970200 2017-02-01 23:00:00
processed 120 days... 1488562200 2017-03-03 23:00:00
processed 150 days... 1491154200 2017-04-02 23:00:00
processed 180 days... 1493746200 2017-05-02 23:00:00
processed 210 days... 1496338800 2017-06-01 23:10:00
processed 240 days... 1498930800 2017-07-01 23:10:00
processed 270 days... 1501557600 2017-08-01 08:50:00
processed 300 days... 1504149600 2017-08-31 08:50:00
processed 330 days... 1506741600 2017-09-30 08:50:00
processed 360 days... 1509333600 2017-10-30 08:50:00
processed 390 days... 1511930700 2017-11-29 10:15:00
processed 420 days... 1514522700 2017-12-29 10:15:00
processed 450 days... 1517115900 2018-01-28 10:35:00
processed 480 days... 1519707900 2018-02-27 10:35:00
processed 510 days... 1522300200 2018-03-29 10:40:00
processed 540 days... 1525530600 2018-05-05 20:00:00
processed 570 days... 1528123800 2018-06-04 20:20:00
processed 600 days... 1530717900 2018-07-04 20:55:00
processed 630 days... 1533359100 2018-08-04 10:35:00
processed 660 days... 1535996400 2018-09-03 23:10:00
processed 690 days... 1538488800 2018-10-02 19:30:00
processed 810 days... 1548349800 2019-01-24 22:40:00
processed 900 days... 1555643400 2019-04-19 08:40:00
processed 1050 days... 1568389800 2019-09-13 21:20:00

On Sat, Jul 4, 2020 at 12:12 PM jonathan koren 
wrote:

>
> It creates a weewx engine.StdEngine to get handles to the databases to
> query. So no, it does not talk to any devices, but the device is getting
> opened as part of the engine startup,
>
> I have not seen anything like this with the Vantage driver. Have you tried
> shutting down weewx before running aqi_backfill?
>
>
> On Thursday, July 2, 2020 at 9:28:14 PM UTC-7, Rahul Bedi wrote:
>>
>> Yes. Works with no issues outside of the script.
>>
>> It's not clear to me as to why this script is even trying to talk to the
>> weather station. Shouldn't it be just be moving data from one database to
>> the other ?
>>
>>
>> On Fri, 3 Jul, 2020, 9:45 am jonathan koren, 
>> wrote:
>>
>>> It appears that weewx can't talk to whatever device is on your USB. Are
>>> you sure you have the WMR 200 configured correctly? Is it plugged in?
>>>
>>> These errors aren't even happening in the AQI code.
>>>
>>> On Wednesday, July 1, 2020 at 11:36:39 PM UTC-7, Rahul Bedi wrote:

 Tried and gives the following message and it hangs:

 pi@PrideWeatherStation:/var/lib/weewx $ sudo
 /usr/share/weewx/aqi_backfill --start_time 1592634016 --end_time 1593670517
 /etc/weewx/weewx.conf
 Starting backfill from 1592634016 2020-06-20 11:50:16
 No handlers could be found for logger "weewx.drivers.wmr200"
 Exception in thread Thread-2:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
 self.run()
   File "/usr/share/weewx/weewx/drivers/wmr200.py", line 1229, in run
 _ = self.usb_device.read_device()
   File "/usr/share/weewx/weewx/drivers/wmr200.py", line 259, in
 read_device
 raise weewx.WeeWxIOError(msg)
 WeeWxIOError: read_device() USB Error Reason:[Errno 110] Operation
 timed out

 On Thu, Jul 2, 2020 at 11:33 AM jonathan koren <
 spam-...@robotmonkeys.net> wrote:

> There's a new weewx-aqi release (1.3)
> https://github.com/jonathankoren/weewx-aqi/releases/tag/v1.3 so make
> sure you get that. It has some changes that effect aqi_backfill, including
> the fix for this.
>
> Be aware, aqi_backfill  pretty temperamental.
>
>
> On Wednesday, July 1, 2020 at 3:57:10 AM UTC-7, Rahul Bedi wrote:
>>
>> Hi,
>>
>> I tried running the "aqi_backfill" script which is part of the aqi
>> extension on a weewx 4.1.1 install and get the following error.
>>
>> Looks like way to pull the config seems to have changes since the
>> time this script was written.
>>
>> Any ideas?
>>
>> - Rahul
>>
>>
>> pi@PrideWeatherStation:/usr/share/weewx $ sudo ./aqi_backfill
>> weewx.conf
>> Traceback (most recent call 

Re: [weewx-user] Re: Skin Belchertown 1.1

[Didier Decoodt]

Hi Patrick

It's OK I have filled the right parameters...
https://meteo-auffargis.decoodt.eu

Le jeu. 9 juil. 2020 à 23:17, Didier Decoodt  a
écrit :

> Hi Patrick
>
> my station : https://meteo-auffargis.decoodt.eu
>
> How do you do for earthquake info with USGS Api?
> Is it possible to have information for France only?
>
> Bonne soirée
> Didier
>
> Le jeu. 9 juil. 2020 à 22:52, salinois  a écrit :
>
>> hello Didier;
>>
>> you can see my weather station
>>
>> http://jurassikpat.ddns.net/weewx/belchertown
>>
>> bonne soirée
>>
>> Patrick
>> Le 09/07/2020 à 12:48, Didier Decoodt a écrit :
>>
>> See below the modified presentation of records and the corresponding file
>> records/index.html.tmpl
>> [image: image.png]
>>
>> Bonne journée
>>
>> Le dim. 5 juil. 2020 à 15:43, Patrick Tranchant  a
>> écrit :
>>
>>> hello Didier,
>>>  I done as you say; it works well
>>> thanks
>>>
>>> bon Dimanche
>>>
>>> Patrick
>>>
>>> On Sunday, July 5, 2020 at 2:06:56 PM UTC+2, Patrick Tranchant wrote:

 Hello PAT,

 I just upgraded Weewx to 4.1.1 with Belchertown 1.1 ( already in use
 with weewx 3.9.2 )
 I want to know to modify the display in "RECORDS",
 modify : Barometer Records
 remove : Sun Records ( I don't have Sun Probe.

 thanks

 Patrick

 see my files

 --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/8fdb06b5-6d97-482f-8b20-6c8c82d41793o%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/CAAvt3%3DQ5vPPh2Tn5%3D%3DiVQJvTngJqAanH6bLGPLgoAa9mmrF%3DOg%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/7c82495d-dcc9-78de-4ae6-7b97c3fe0db5%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/CAAvt3%3DQN-zcXF2Zq%2BrfDTgx22KdquCy5VLT9weutF56DqYoCBw%40mail.gmail.com.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[John Kline]

Of course, loop-data.txt is not created with all fields.  It would be huge.  
Rather, it is created with the fields you specify in the LoopData fields line 
in weewx.conf.

The equivalent of $current.barometer in LoopData is barometer.  You don’t 
specify that field.  Instead, you specify FMT_barometer.  As such, you 
loop-data.txt file has the following (change FMT_barometer to barometer to get 
what you want):

"FMT_barometer": "1020.3 hPa"

The equivalent of $trend.barometer.formatted in LoopData is barometerRate.  I 
see it in your loop-data.txt file:

barometerRate": "0.00879"

It is barometerRate that might have too many decimal digits.  I will double 
check that for the next revision.

BTW, as I mentioned, I’m changing the language to specify LoopData.  In the 
next revision, you would specify $current.barometer and 
$trend.barometer.formatted in the fields entry in weewx.conf.

>> On Jul 11, 2020, at 2:03 AM, geni08...@gmail.com  
>> wrote:
> The loop-data.txt file is not created with all fields!
> 
> The entry: $current.barometer ($trend.barometer.formatted)
> in the index.html.tmpl results in the correct formatting.
> 
> 
> jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 20:09:30 UTC+2:
>> I had a look.  You never actually write FMT_windDir in the JavaScript.  Just 
>> add:
>> + ‘ (‘ + result[‘FMT_windDir’] + ‘)’
>> on the appropriate line in realtime_updater.inc.
>> 
>> As for barometerRate.  I do see it.  I just spills over to the next line.  
>> It looks like I am not properly formatting barometerRate.  I will fix that 
>> as part of the 2.0 release which I am working on and hope to have out this 
>> weekend.
>> 
>>> On Jul 10, 2020, at 9:03 AM, geni08...@gmail.com  
>>> wrote:
>>> 
>> 
>>> Hi John, I'm on the mountain, there was more. Can you please keep an eye on 
>>> the two files?
>>> 
>>> 
>>> jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 16:05:18 UTC+2:
 You need to add the fields:
 barometerRate
 FMT_windDir
 to the fields line in the LoopData section of weewx.conf.
 
 After you do that and restart WeeWX, verify that you see these readings in 
 loop-data.txt.
 
 Finally, you need to set these values in the JavaScript.
 
 If you have already done all of the above, perhaps you have a JavaScript 
 error.  Have a look in the JavaScript console in your browser (note: it 
 may be called something else, search for how to see JavaScript errors).
 
 BTW, this weekend, I should have a version of LoopData out that uses the 
 same naming scheme as cheetah.  As such, you will then specify 
 $current.windSpeed, $current.windDir.ordinal_compass and $current.windDir 
 (for example) in the fields line in weewx.conf and those keys will show up 
 in loop-data.txt.  There was no good reason to invent a new language for 
 this. 
 
>> On Jul 10, 2020, at 1:54 AM, geni08...@gmail.com  
>> wrote:
> 
 
> what do I have to change so that the two values (in the yellow circle) 
> are always displayed? Now they only flash briefly during a manual refresh.
 
> 
> 
> in index.html.templ:
>   style="font-family:monospace;font-size:85px;text-align:center;">$current.windSpeed
>  $current.windDir.ordinal_compass ($current.windDir)
> $current.barometer 
> ($trend.barometer.formatted)- id="FMT_outHumidity">$current.outHumidity
> 
> jo...@johnkline.com schrieb am Donnerstag, 9. Juli 2020 um 15:40:48 UTC+2:
>> 
>> 
 On Jul 9, 2020, at 1:52 AM, geni08...@gmail.com  
 wrote:
>>> Question for my understanding:
>> 
>>> 
>>> If or why is the id = string supplemented with $current, $day or not at 
>>> all?
>> 
>>> 
>> 
>> In the examples, no IDs is supplemented with current, day or none at 
>> all.  Some values say $current, which means the current observation.  
>> Some say day, which would be for the day and have an aggregator 
>> ($day.rain.sum).  In any event, all of these values are overwritten 
>> every couple of seconds by the javascript.  As such, they could be 
>> removed.
>> 
>> As for the ids.  They could be anything you wish.  They just are used by 
>> the JavaScript to look up the element.  As a naming scheme for ids, I 
>> chose to to name them for the corresponding key in loop-data.txt.
>> 
>> For example, FMT_HI_windGust.  The JavaScript will get lookup the 
>> element with the id FMT_HI_windGust.  It will then lookup the value in 
>> loop-data.txt for the key FMT_HI_windGust and set the contents of the 
>> HTML tag (innerHTML property) to that value.
>> 
>> If the id was foo on this element, the JavaScript would have to find the 
>> foo element in the DOM.  Of course, it will still need to use the key 
>> FMT_HI_windGust for looking up the loop-data value.
>> 
>> As for the naming scheme in 

Re: [weewx-user] Wind Data Missing

[Andre]

This is the /usr/share/weewx/user/extensions.py

#
#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
# 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, '')


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






Am Samstag, 11. Juli 2020 14:16:43 UTC+2 schrieb Tom Keffer:
>
> It looks like you are using a custom schema. May we see it? It should be 
> in /usr/share/weewx/user/extensions.py
>
> -tk
>
> On Fri, Jul 10, 2020 at 10:57 PM Andre > 
> wrote:
>
>> Thanks for reply, Tom.
>>
>> Here is my 
>> [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 = schemas.wview_extended.schema
>> schema = user.extensions.schema_extended
>>
>>
>> Am Samstag, 11. Juli 2020 03:26:02 UTC+2 schrieb Tom Keffer:
>>>
>>> You did not include a log, but on the basis of similar problems, I would 
>>> bet that you used the wrong combination of schema and 'manager' in your 
>>> configuration file, weewx.conf.
>>>
>>> Please post the section [DataBindings] in weewx.conf
>>>
>>> -tk
>>>
>>> On Fri, Jul 10, 2020 at 7:26 AM Andre  wrote:
>>>
 Hardware: Davis Vantage Vue
 Raspberry Pi 4: Install with DEB package
 WeeWX: 4.1.1
 Skin: Belchertown 1.2b6

 Actually, I just wanted to quickly correct a too high value of the rain 
 rate. So I did:

 1. wee_database --drop-daily
 2. wee_database --rebuild-daily
 3. wee_database --update

 After that the too high rain rate value was corrected, but the 
 "snapshot" area in the Belchertown skin did not work anymore. 
 [image: weewx01.png]

 So I uninstalled and reinstalled the Belchertown skin. After that 
 everything worked as desired, but now the wind values were missing. Also 
 the NOAA files were completely missing the wind data.

 I deleted all NOAA files and hoped that the wind data would be 
 generated. Unfortunately without success.
 http://www.wetter-norderstedt.de/NOAA/NOAA-2020-07.txt

 Can someone help me to solve the problem?

 Best regards, Andre



 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/eecad34a-41b2-4087-9221-460fffce4ee9o%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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d559ad6e-6e58-48aa-9efb-81cea691da02o%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/4feb1c39-961a-4ee5-a34d-151524e92bbco%40googlegroups.com.

Re: [weewx-user] Wind Data Missing

[Tom Keffer]

It looks like you are using a custom schema. May we see it? It should be in
/usr/share/weewx/user/extensions.py

-tk

On Fri, Jul 10, 2020 at 10:57 PM Andre  wrote:

> Thanks for reply, Tom.
>
> Here is my
> [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 = schemas.wview_extended.schema
> schema = user.extensions.schema_extended
>
>
> Am Samstag, 11. Juli 2020 03:26:02 UTC+2 schrieb Tom Keffer:
>>
>> You did not include a log, but on the basis of similar problems, I would
>> bet that you used the wrong combination of schema and 'manager' in your
>> configuration file, weewx.conf.
>>
>> Please post the section [DataBindings] in weewx.conf
>>
>> -tk
>>
>> On Fri, Jul 10, 2020 at 7:26 AM Andre  wrote:
>>
>>> Hardware: Davis Vantage Vue
>>> Raspberry Pi 4: Install with DEB package
>>> WeeWX: 4.1.1
>>> Skin: Belchertown 1.2b6
>>>
>>> Actually, I just wanted to quickly correct a too high value of the rain
>>> rate. So I did:
>>>
>>> 1. wee_database --drop-daily
>>> 2. wee_database --rebuild-daily
>>> 3. wee_database --update
>>>
>>> After that the too high rain rate value was corrected, but the
>>> "snapshot" area in the Belchertown skin did not work anymore.
>>> [image: weewx01.png]
>>>
>>> So I uninstalled and reinstalled the Belchertown skin. After that
>>> everything worked as desired, but now the wind values were missing. Also
>>> the NOAA files were completely missing the wind data.
>>>
>>> I deleted all NOAA files and hoped that the wind data would be
>>> generated. Unfortunately without success.
>>> http://www.wetter-norderstedt.de/NOAA/NOAA-2020-07.txt
>>>
>>> Can someone help me to solve the problem?
>>>
>>> Best regards, Andre
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/eecad34a-41b2-4087-9221-460fffce4ee9o%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/d559ad6e-6e58-48aa-9efb-81cea691da02o%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/CAPq0zEAGyWBwdROKUZsshQ9ktU1Q2O7%2BqTLXcN_uSfB7Rj7Cvw%40mail.gmail.com.

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

[Bill Morrow]

Sorry for the late reply. I don't have much time to work on my original 
wxMesh driver. 

>From what I have seen of MQTTSubscribe, it's a much more complete 
implementation of an MQTT subscriber, and offers the features I was 
planning on adding some day. When I get a chance, I plan on switching to 
using MQTTSubscribe.



On Wednesday, 24 June 2020 18:00:44 UTC-3, Rich Bell wrote:
>
> Great to hear. Just give a shout if you run into any other difficulties.
> rich
>
> On Wednesday, 24 June 2020 16:50:26 UTC-4, Christian Peters wrote:
>>
>> Hi Rich,
>>
>> thank you very much. 
>> It works like a charm! :-) 
>>
>> I set up a temporary mapping to values already available in the databae. 
>> For the temp and humid values it works out of the box, for CPM, CPS and 
>> radiation I have to setup unit groups later. 
>>
>> This is my working setup - just to have that written down for others:
>>
>> my data form the MQTT broker:
>>
>>
>> radiation:0.17,cpm:31,cps:0,temp_2m:25.97,temp_5cm:27.24,temp_dht22:34.30,hum_dht22:45.30,rain:0.00
>>
>> weewx.conf:
>>
>> [MQTTSubscribeService]
>> host = xxx.xxx.xxx.xxx # IP of the broker
>> payload_type = keyword
>> console = True
>> [[topics]]
>>  [[[weather]]]   # The topic you are subscribing to
>>unit_system = METRICWX # Not sure weather you want METRICWX or 
>> METRIC. See http://weewx.com/docs/customizing.htm#units
>>temp_2m # Name in the MQTT message
>>name = extraTemp1 # WeeWX name
>>temp_5cm
>>name = extraTemp2
>>temp_dht22
>>name = extraTemp3
>>hum_dht22
>>name = extraHumid3
>>rain
>>name = hail
>>radiation
>>name = signal1
>>cpm
>>name = signal2
>>cps
>>name = signal3
>>
>> [[message_callback]]
>>  type = keyword
>>  keyword_delimiter = "," # The delimiter between the name/value pairs
>>  keyword_separator = ":" # The separator between the name and the value
>>
>> [[Services]]
>> data_services = user.MQTTSubscribe.MQTTSubscribeService
>>
>> That's quite nice and more elegant as to set up a second weewx instance 
>> with a MQTT driver! 
>> Thank you very much.
>>
>> My MQTT broker runs on a BananaPi which is located in the garden near the 
>> sensors (Temp2m, Temp5cm, raingauge, temp and hum sensor inside the 
>> controlbox and a MightyOhm Geiger Counter Kit).
>> I can't figure out why...but somtimes I lost the WLAN connection (after 
>> 7-30 days). Then I restart the BananPi, start the mosquitto deamon...but 
>> the weewx instance running the wxMesh driver didn't reconnect. 
>> I have to start and stop this instance, then it works again. But I saw a 
>> post in weewx-development that someone pointed out the connection was setup 
>> once at initialisation...maybe there is no check of the connection and a 
>> reconnect condition?
>>
>> If the setup goes online (at the moment I run the simulator whil 
>> mograting all sensors and tweak the new webpage) and the VanatgeVP2 is 
>> connected, I will check the behavior of your drriver in my setup. 
>>
>> Thanks again for the excellent support. If I run into some problems I 
>> will contact you again. :-)
>>
>> Regards,
>>
>> Christian 
>>
>> P.S. Ken, thanks for you fix...it works..! :-) But the 
>> MQTTSubscribeService works great and I will prefer to run only one weewx 
>> instance to deal with all sensors. 
>>
>>
>> Am Mittwoch, 24. Juni 2020 19:25:05 UTC+2 schrieb Rich Bell:
>>>
>>>
>>> Well, I haven't heard of having to restart WeeWX when the connection is 
>>> lost, and if that happens I would certainly want to look into fixing that. 
>>> I'll do some experiments to see if I can recreate. 
>>>
>>> Sounds like picking the service might be the best long term choice, with 
>>> the caveat about the reconnect logic needing to be verified. But if you 
>>> want to get your feet wet, I would suggest that we get it up and running as 
>>> a driver - perhaps even running from the command line for a bit. The actual 
>>> configuration work is really the same. So you could migrate to the service 
>>> as you get more comfortable or after we prove that lost connections are not 
>>> a problem. 
>>>
>>> The following assumes that you install 1.5.4-rc01. This changed the way 
>>> to configure MQTTSubscribe. Once installed, there will be three key 
>>> sections the [MQTTSubscribeDriver]/[MQTTSubscribeService] section. This is 
>>> the MQTT connection information, and I believe this is pretty straight 
>>> forward. But after looking at it, if you have questions let me know.
>>>
>>> Next up is the [[topics]] section. Based on the information you posted, 
>>> I think this is what you would want
>>>
>>> [[topics]]
>>>  [[[weather]]]   # The topic you are subscribing to
>>>unit_system = METRICWX # Not sure weather you want METRICWX or 
>>> METRIC. See 

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

The loop-data.txt file is not created with all fields!

The entry: $current.barometer ($trend.barometer.formatted)
in the index.html.tmpl results in the correct formatting.


jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 20:09:30 UTC+2:

> I had a look.  You never actually write FMT_windDir in the JavaScript. 
>  Just add:
> + ‘ (‘ + result[‘FMT_windDir’] + ‘)’
> on the appropriate line in realtime_updater.inc.
>
> As for barometerRate.  I do see it.  I just spills over to the next line. 
>  It looks like I am not properly formatting barometerRate.  I will fix that 
> as part of the 2.0 release which I am working on and hope to have out this 
> weekend.
>
> On Jul 10, 2020, at 9:03 AM, geni08...@gmail.com  
> wrote:
>
>  
>
> Hi John, I'm on the mountain, there was more. Can you please keep an eye 
> on the two files?
>
>
> jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 16:05:18 UTC+2:
>
>> You need to add the fields:
>> barometerRate
>> FMT_windDir
>> to the fields line in the LoopData section of weewx.conf.
>>
>> After you do that and restart WeeWX, verify that you see these readings 
>> in loop-data.txt.
>>
>> Finally, you need to set these values in the JavaScript.
>>
>> If you have already done all of the above, perhaps you have a JavaScript 
>> error.  Have a look in the JavaScript console in your browser (note: it may 
>> be called something else, search for how to see JavaScript errors).
>>
>> BTW, this weekend, I should have a version of LoopData out that uses the 
>> same naming scheme as cheetah.  As such, you will then specify 
>> $current.windSpeed, $current.windDir.ordinal_compass and $current.windDir 
>> (for example) in the fields line in weewx.conf and those keys will show up 
>> in loop-data.txt.  There was no good reason to invent a new language for 
>> this. 
>>
>> On Jul 10, 2020, at 1:54 AM, geni08...@gmail.com  
>> wrote:
>>
>>  
>>
>> what do I have to change so that the two values (in the yellow circle) 
>> are always displayed? Now they only flash briefly during a manual 
>> refresh.
>>
>> 
>>
>> in index.html.templ:
>>  > style="font-family:monospace;font-size:85px;text-align:center;">$current.windSpeed
>>  
>> $current.windDir.ordinal_compass ($current.windDir)
>> $current.barometer 
>> ($trend.barometer.formatted)-> id="FMT_outHumidity">$current.outHumidity
>>
>> jo...@johnkline.com schrieb am Donnerstag, 9. Juli 2020 um 15:40:48 
>> UTC+2:
>>
>>>
>>>
>>> On Jul 9, 2020, at 1:52 AM, geni08...@gmail.com  
>>> wrote:
>>>
>>> Question for my understanding:
>>>
>>>
>>> If or why is the id = string supplemented with $current, $day or not at 
>>> all?
>>>
>>> 
>>>
>>>
>>> In the examples, no IDs is supplemented with current, day or none at 
>>> all.  Some values say $current, which means the current observation.  Some 
>>> say day, which would be for the day and have an aggregator ($day.rain.sum). 
>>>  In any event, all of these values are overwritten every couple of seconds 
>>> by the javascript.  As such, they could be removed.
>>>
>>> As for the ids.  They could be anything you wish.  They just are used by 
>>> the JavaScript to look up the element.  As a naming scheme for ids, I chose 
>>> to to name them for the corresponding key in loop-data.txt.
>>>
>>> For example, FMT_HI_windGust.  The JavaScript will get lookup the 
>>> element with the id FMT_HI_windGust.  It will then lookup the value in 
>>> loop-data.txt for the key FMT_HI_windGust and set the contents of the HTML 
>>> tag (innerHTML property) to that value.
>>>
>>> If the id was foo on this element, the JavaScript would have to find the 
>>> foo element in the DOM.  Of course, it will still need to use the key 
>>> FMT_HI_windGust for looking up the loop-data value.
>>>
>>> As for the naming scheme in loop-data.txt:
>>> FMT_HI_windGust
>>> The FMT_ means include the label.
>>> The HI_ means give me today’s high.
>>>
>>> FMT_windGust would be for the current observation and would include the 
>>> label.
>>>
>>> windGust would be for the current observation. It would NOT include a 
>>> label, but it would still be formatted.  That is, if wind should have 1 
>>> decimal place, it be formatted as such (e.g., 4.0).
>>>
>>> The README has this info, but to summarize:
>>>
>>> If the key is missing an aggregator (HI, LO, AVG, WAVG, SUM, RMS, 
>>> VEC_AVG, VEC_DIR), it is the current observation.  If it has an aggregator 
>>> prefix, it is for the day.  Exceptions are the items I made up 10mMaxGust 
>>> (which is 10 minutes) and barometerRate (which is a delta from 3 hours ago) 
>>> and windRose.
>>>
>>> FMT_ includes the label.
>>>
>>> UNITS_ is the unit for the observation.
>>>
>>> LABEL_ is the label for the observation.
>>>
>>> COMPASS_ for windDIr and windGustDir gives compass (text) direction.
>>>
>>> DESC_ for barometer rate gives a text description of the rate (and 
>>> probably needs to be internationalized).
>>>
>>> T_ is the time of the observation.  For example, T_HI_ would be the 
>>>