[weewx-user] Re: Belchertown Skin 0.8.2 Released

[Scott Grayban]

Pat are any of these variables/settings used in your skin ?

interceptor: MainThread: unrecognized parameter hourlyrainin=0.00
> interceptor: MainThread: unrecognized parameter eventrainin=0.00
> interceptor: MainThread: unrecognized parameter totalrainin=1.88
> interceptor: MainThread: unrecognized parameter 
> stationtype=AMBWeatherV4.0.7
> interceptor: MainThread: unrecognized parameter maxdailygust=6.9
> interceptor: MainThread: unrecognized parameter baromrelin=29.92



On Tuesday, January 1, 2019 at 4:50:49 AM UTC-8, Pat wrote:
>
> I've just released version 0.8.2 of the Belchertown skin which fixes the 
> New Year bug some of you are seeing. It also adds some other features. 
>
>
> Download and install instructions here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
>
> * Fixed an error where the skin would fail when the date rolls to the New 
> Year due to no data being in certain tables in the database yet. 
> * Added the ability to show any weather alerts provided by the DarkSky 
> API. Weather alerts are off by default, use forecast_alert_enabled in 
> weewx.conf skin options to enable it.
> * New option to show cloudbase. You must have your database schema 
> extended for the cloudbase observation to be calculated by weewx. Check the 
> Belchertown skin wiki for details.
> * Fixes an issue where the MQTT updates showed altimeter instead of 
> barometer.
> * Updated Google Analytics page to be in header based on Google 
> recommendations. 
> * Updated Google Analytics to a more recent script block. 
> * Added a Google Analytics page view per MQTT update as per Google 
> Recommendations on background updates. 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[Steve2Q]

I will try substituting an older version of the driver to see if that makes any 
difference.  

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[vince]

On Monday, February 11, 2019 at 6:43:06 PM UTC-8, Steve2Q wrote:
>
> Is there any possibility that substituting an older driver may work? The 
> newest version (0.18) is quite different than the older ones.
>
>
>
Still think you need to find a weewx user with the same driver+version and 
usb-to-serial configuration, if possible.

But if you change things, change 'one' thing at a time and keep track of 
what you changed.  This one's pretty odd. 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx is stopping with errors

[Luc Heijst]

After upgrading today from 3.8.2 to v3.9.1 I noticed on some raspberry pi’s 
similar error messages. I have 5 pi’s with cmon installed.
The error did not return after rebooting the systems.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[Steve2Q]

Tom: Thanks for checking in..I was going to get back to you after a few 
more days of running. At at this point, it still appears to be acting the 
same way. It is so regular that I derived a formula for % of memory v 
time:  % = .253 (time in hours) + 3.24  

For 2 Days 6 hours 50 minutes, % = .253 (56.83) + 3.24  = 17.62   Top show 
17.0%  I know this is irrelevant, but it is interesting nonetheless.

Is there any possibility that substituting an older driver may work? The 
newest version (0.18) is quite different than the older ones.

Steve

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx is stopping with errors

[gjr80]

Hi,

It looks like cmon is returning a string value of 7928150 but looking 
through the cmon code every field that is added to the cmon generated 
record uses float() or int() so that shouldn't be happening. Can you post 
some more of the log from before the error. Alternatively, can you leave 
debug = 1 and restart WeeWX then post the log extract from WeeWX startup 
until the error occurs (assuming the error is ongoing).

Gary

On Tuesday, 12 February 2019 08:28:15 UTC+10, ted frohling wrote:
>
> I recently upgraded the Pi that I'm running weewx on.  Did the usual 
> install with a down
> load.  I saved my old weewx.conf file and started it.   Found that weewx 
> was stopping.
>
> Here's the logfile with debug set to 1.
>
> Feb 11 10:30:18 weewx weewx[26950]: manager: Added record 2019-02-11 
> 10:30:19 MST (1549906219) to database 'cmon.sdb'
> Feb 11 10:30:18 weewx weewx[26950]: engine: Main loop exiting. Shutting 
> engine down.
> Feb 11 10:30:18 weewx weewx[26950]: engine: Shutting down StdReport thread
> Feb 11 10:30:18 weewx weewx[26950]: engine: StdReport thread has been 
> terminated
> Feb 11 10:30:18 weewx weewx[26950]: restx: Shut down WOW thread.
> Feb 11 10:30:18 weewx weewx[26950]: restx: Shut down CWOP thread.
> Feb 11 10:30:18 weewx weewx[26950]: restx: Shut down PWSWeather thread.
> Feb 11 10:30:18 weewx weewx[26950]: restx: Shut down Wunderground-PWS 
> thread.
> Feb 11 10:30:18 weewx weewx[26950]: engine: Caught unrecoverable exception 
> in engine:
> Feb 11 10:30:18 weewx weewx[26950]:   accum: ScalarStats.addHiLo 
> expected float or int, got 7928150
> Feb 11 10:30:18 weewx weewx[26950]:   Traceback (most recent call 
> last):
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/engine.py", line 890, in main
> Feb 11 10:30:18 weewx weewx[26950]:   engine.run()
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/engine.py", line 202, in run
> Feb 11 10:30:18 weewx weewx[26950]:   
> self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> Feb 11 10:30:18 weewx weewx[26950]:   callback(event)
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/engine.py", line 580, in post_loop
> Feb 11 10:30:18 weewx weewx[26950]:   
> self._catchup(self.engine.console.genArchiveRecords)
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/engine.py", line 635, in _catchup
> Feb 11 10:30:18 weewx weewx[26950]:   origin='hardware'))
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> Feb 11 10:30:18 weewx weewx[26950]:   callback(event)
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/user/cmon.py", line 319, in new_archive_record
> Feb 11 10:30:18 weewx weewx[26950]:   
> self.save_data(self.get_data(now, self.last_ts))
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/user/cmon.py", line 326, in save_data
> Feb 11 10:30:18 weewx weewx[26950]:   
> self.dbm.addRecord(record)
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/manager.py", line 246, in addRecord
> Feb 11 10:30:18 weewx weewx[26950]:   
> self._addSingleRecord(record, cursor, log_level)
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
> Feb 11 10:30:18 weewx weewx[26950]:   
> _day_summary.addRecord(record, weight=_weight)
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/accum.py", line 256, in addRecord
> Feb 11 10:30:18 weewx weewx[26950]:   func(self, record, 
> obs_type, add_hilo, weight)
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/accum.py", line 314, in add_value
> Feb 11 10:30:18 weewx weewx[26950]:   
> self[obs_type].addHiLo(val, record['dateTime'])
> Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/accum.py", line 77, in addHiLo
> Feb 11 10:30:18 weewx weewx[26950]:   raise ValueError("accum: 
> ScalarStats.addHiLo expected float or int, got %s" % val)
> Feb 11 10:30:18 weewx weewx[26950]:   ValueError: accum: 
> ScalarStats.addHiLo expected float or int, got 7928150
> Feb 11 10:30:18 weewx weewx[26950]:   Exiting.
>
>
> Here's the config file with usernames and passwords emptied.
>
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2015 Tom Keffer >
> # See the file LICENSE.txt for your rights.
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise 

RE: [weewx-user] 3.9.1 PIL & Pillow

[Carlingford Weather]

I suppose so. It may reinforce what the wiki already says, but normally I don’t 
like to bloat Wikis.

Will add the links.

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Tuesday, 12 February 2019 12:42 PM
To: weewx-user 
Subject: Re: [weewx-user] 3.9.1 PIL & Pillow

Do you think the two StackOverflow links would be useful?

On Mon, Feb 11, 2019 at 5:30 PM Darryn Capes-Davis 
mailto:weather@carlingfordweather.sydney>> 
wrote:
Checked out the Wiki. If you follow it, including the uninstall and reinstall 
steps, all should be good. Nothing extra to add that I can see.

On Tuesday, February 12, 2019 at 11:42:56 AM UTC+11, Darryn Capes-Davis wrote:
Good suggestion. Will do.

From: weewx-user@googlegroups.com 
mailto:weewx-user@googlegroups.com>> On Behalf Of 
Thomas Keffer
Sent: Tuesday, 12 February 2019 11:41 AM
To: weewx-user mailto:weewx-user@googlegroups.com>>
Subject: Re: [weewx-user] 3.9.1 PIL & Pillow

Thanks, Darryn,

Perhaps you could add your thoughts to our Troubleshooting 
Pillow wiki page?

On Mon, Feb 11, 2019 at 4:38 PM Darryn Capes-Davis 
mailto:weather@carlingfordweather.sydney>> 
wrote:
All,

Just upgraded to 3.9.1. On suggestion from Gary I took the graphing styles from 
the seasons Skin to put into my Responsive Skin 
(https://darryn.capes-davis.com/2016/10/23/weewx-weather-software-responsive-skin/).
 The small issue was that the Axes labels (both X and Y) were offset by a pixel 
or two, with the bottom X axis label being cut off. Looking into it, weewx 
positions the labels based on their size, so I concluded that PIL (Pillow) must 
have had an issue. Checking it out (use command 'pip list') my pillow was at 
2.3. So I went through the process to upgrade pillow to 5.4 which solved the 
issue.

NOTE: Upgrade to pillow was not straightforward. I encountered some issues so I 
include some links below which helped me across these two issues.

https://stackoverflow.com/questions/44043906/the-headers-or-library-files-could-not-be-found-for-jpeg-installing-pillow-on
https://stackoverflow.com/questions/4011705/python-the-imagingft-c-module-is-not-installed


Regards

Darryn Capes-Davis
https://carlingfordweather.sydney


--
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.
For more options, visit https://groups.google.com/d/optout.
--
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/KCL8cBqA4ng/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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.
For more options, visit https://groups.google.com/d/optout.
--
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/KCL8cBqA4ng/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[Thomas Keffer]

Steve, how is it going with this?

On Wed, Feb 6, 2019 at 9:16 AM Steve2Q  wrote:

> Tom: I upgraded pyserial and have rebooted. I will run just the regular
> instance of weewx without the simulator, and will see how that goes. Weewxd
> started at 3.4% mem usage.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] 3.9.1 PIL & Pillow

[Thomas Keffer]

Do you think the two StackOverflow links would be useful?

On Mon, Feb 11, 2019 at 5:30 PM Darryn Capes-Davis
 wrote:

> Checked out the Wiki. If you follow it, including the uninstall and
> reinstall steps, all should be good. Nothing extra to add that I can see.
>
> On Tuesday, February 12, 2019 at 11:42:56 AM UTC+11, Darryn Capes-Davis
> wrote:
>>
>> Good suggestion. Will do.
>>
>>
>>
>> *From:* weewx-user@googlegroups.com  *On
>> Behalf Of *Thomas Keffer
>> *Sent:* Tuesday, 12 February 2019 11:41 AM
>> *To:* weewx-user 
>> *Subject:* Re: [weewx-user] 3.9.1 PIL & Pillow
>>
>>
>>
>> Thanks, Darryn,
>>
>>
>>
>> Perhaps you could add your thoughts to our *Troubleshooting Pillow
>> * wiki page?
>>
>>
>>
>> On Mon, Feb 11, 2019 at 4:38 PM Darryn Capes-Davis <
>> weather@carlingfordweather.sydney> wrote:
>>
>> All,
>>
>>
>>
>> Just upgraded to 3.9.1. On suggestion from Gary I took the graphing
>> styles from the seasons Skin to put into my Responsive Skin (
>> https://darryn.capes-davis.com/2016/10/23/weewx-weather-software-responsive-skin/).
>> The small issue was that the Axes labels (both X and Y) were offset by a
>> pixel or two, with the bottom X axis label being cut off. Looking into it,
>> weewx positions the labels based on their size, so I concluded that PIL
>> (Pillow) must have had an issue. Checking it out (use command 'pip list')
>> my pillow was at 2.3. So I went through the process to upgrade pillow to
>> 5.4 which solved the issue.
>>
>>
>>
>> NOTE: Upgrade to pillow was not straightforward. I encountered some
>> issues so I include some links below which helped me across these two
>> issues.
>>
>>
>>
>>
>> https://stackoverflow.com/questions/44043906/the-headers-or-library-files-could-not-be-found-for-jpeg-installing-pillow-on
>>
>>
>> https://stackoverflow.com/questions/4011705/python-the-imagingft-c-module-is-not-installed
>>
>>
>>
>>
>>
>> Regards
>>
>>
>>
>> Darryn Capes-Davis
>>
>> https://carlingfordweather.sydney
>>
>>
>>
>>
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> 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/KCL8cBqA4ng/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] 3.9.1 PIL & Pillow

[Darryn Capes-Davis]

Checked out the Wiki. If you follow it, including the uninstall and 
reinstall steps, all should be good. Nothing extra to add that I can see.

On Tuesday, February 12, 2019 at 11:42:56 AM UTC+11, Darryn Capes-Davis 
wrote:
>
> Good suggestion. Will do.
>
>  
>
> *From:* weewx-user@googlegroups.com  *On 
> Behalf Of *Thomas Keffer
> *Sent:* Tuesday, 12 February 2019 11:41 AM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] 3.9.1 PIL & Pillow
>
>  
>
> Thanks, Darryn,
>
>  
>
> Perhaps you could add your thoughts to our *Troubleshooting Pillow 
> * wiki page?
>
>  
>
> On Mon, Feb 11, 2019 at 4:38 PM Darryn Capes-Davis <
> weather@carlingfordweather.sydney> wrote:
>
> All,
>
>  
>
> Just upgraded to 3.9.1. On suggestion from Gary I took the graphing styles 
> from the seasons Skin to put into my Responsive Skin (
> https://darryn.capes-davis.com/2016/10/23/weewx-weather-software-responsive-skin/).
>  
> The small issue was that the Axes labels (both X and Y) were offset by a 
> pixel or two, with the bottom X axis label being cut off. Looking into it, 
> weewx positions the labels based on their size, so I concluded that PIL 
> (Pillow) must have had an issue. Checking it out (use command 'pip list') 
> my pillow was at 2.3. So I went through the process to upgrade pillow to 
> 5.4 which solved the issue.
>
>  
>
> NOTE: Upgrade to pillow was not straightforward. I encountered some issues 
> so I include some links below which helped me across these two issues.
>
>  
>
>
> https://stackoverflow.com/questions/44043906/the-headers-or-library-files-could-not-be-found-for-jpeg-installing-pillow-on
>
>
> https://stackoverflow.com/questions/4011705/python-the-imagingft-c-module-is-not-installed
>
>  
>
>  
>
> Regards
>
>  
>
> Darryn Capes-Davis
>
> https://carlingfordweather.sydney
>
>  
>
>  
>
> -- 
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
> -- 
> 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/KCL8cBqA4ng/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New Skin Seasons on iPhone/iPad

[mwall]

On Saturday, February 9, 2019 at 9:12:16 AM UTC-5, Phil Green wrote:
>
> Hi,
> Thanks for the great update to 3.9.1. Works well. 
> One question about viewing the web page on iOS devices. I have discovered 
> when viewing the web page in Safari browser on my Mac that I have to hover 
> over the values for the Min/Max over the last 24 hours to get the time when 
> the min/max occurred. 
> My question is how do I view the time of the min/max using Safari on my 
> iPhone/iPad?


excellent question!  the notion of 'hover' simply does not exist for touch 
devices.

one alternative is to use a modal javascript dialog, but that requires more 
overhead than just a 'title' field in the html.

if you go to the statistics page (touch the 'High/Low' link) you will see 
the date/time of each event, no hover or additional touching required.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Modify the elements on the website - newbie questions

[vince]

That seasons skin is pretty slick.  Definitely love just editing 
index.html.tmpl 'once' and it automagically does the right thing for 
day/week/month/year without needing to edit a bunch of template files.   
Really cool.   I need to take that approach for all my custom skins here.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

RE: [weewx-user] 3.9.1 PIL & Pillow

[Carlingford Weather]

Good suggestion. Will do.

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Tuesday, 12 February 2019 11:41 AM
To: weewx-user 
Subject: Re: [weewx-user] 3.9.1 PIL & Pillow

Thanks, Darryn,

Perhaps you could add your thoughts to our Troubleshooting 
Pillow wiki page?

On Mon, Feb 11, 2019 at 4:38 PM Darryn Capes-Davis 
mailto:weather@carlingfordweather.sydney>> 
wrote:
All,

Just upgraded to 3.9.1. On suggestion from Gary I took the graphing styles from 
the seasons Skin to put into my Responsive Skin 
(https://darryn.capes-davis.com/2016/10/23/weewx-weather-software-responsive-skin/).
 The small issue was that the Axes labels (both X and Y) were offset by a pixel 
or two, with the bottom X axis label being cut off. Looking into it, weewx 
positions the labels based on their size, so I concluded that PIL (Pillow) must 
have had an issue. Checking it out (use command 'pip list') my pillow was at 
2.3. So I went through the process to upgrade pillow to 5.4 which solved the 
issue.

NOTE: Upgrade to pillow was not straightforward. I encountered some issues so I 
include some links below which helped me across these two issues.

https://stackoverflow.com/questions/44043906/the-headers-or-library-files-could-not-be-found-for-jpeg-installing-pillow-on
https://stackoverflow.com/questions/4011705/python-the-imagingft-c-module-is-not-installed


Regards

Darryn Capes-Davis
https://carlingfordweather.sydney


--
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.
For more options, visit https://groups.google.com/d/optout.
--
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/KCL8cBqA4ng/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Modify the elements on the website - newbie questions

[Thomas Keffer]

Trying to turn him into a beta tester, eh?  

On Mon, Feb 11, 2019 at 4:24 PM mwall  wrote:

>
>
> On Monday, February 11, 2019 at 6:34:46 PM UTC-5, Wiggytoo wrote:
>>
>> Many thanks, I've tracked down the templates and will take another look.
>>
>> Would the changes be easier if I were using one of the standard weewx
>> skins?
>>
>
> the Seasons skin is a bit more modular than past skins, so it is a little
> easier to customize as you are trying to do.
>
> but the process is the same for any skin.
>
> take a look at this derivative of the Seasons skin:
>
> https://github.com/matthewwall/weewx-4seasons
>
> i started with Seasons, but i made the display of data (values and plots)
> conditional upon the existence of data. as a result, the skin is a bit more
> adaptive and should require less customization.
>
> it is a work in progress, but it might give you some ideas for how to
> customize your templates.
>
> m
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] 3.9.1 PIL & Pillow

[Thomas Keffer]

Thanks, Darryn,

Perhaps you could add your thoughts to our *Troubleshooting Pillow
* wiki page?

On Mon, Feb 11, 2019 at 4:38 PM Darryn Capes-Davis
 wrote:

> All,
>
> Just upgraded to 3.9.1. On suggestion from Gary I took the graphing styles
> from the seasons Skin to put into my Responsive Skin (
> https://darryn.capes-davis.com/2016/10/23/weewx-weather-software-responsive-skin/).
> The small issue was that the Axes labels (both X and Y) were offset by a
> pixel or two, with the bottom X axis label being cut off. Looking into it,
> weewx positions the labels based on their size, so I concluded that PIL
> (Pillow) must have had an issue. Checking it out (use command 'pip list')
> my pillow was at 2.3. So I went through the process to upgrade pillow to
> 5.4 which solved the issue.
>
> NOTE: Upgrade to pillow was not straightforward. I encountered some issues
> so I include some links below which helped me across these two issues.
>
>
> https://stackoverflow.com/questions/44043906/the-headers-or-library-files-could-not-be-found-for-jpeg-installing-pillow-on
>
> https://stackoverflow.com/questions/4011705/python-the-imagingft-c-module-is-not-installed
>
>
> Regards
>
> Darryn Capes-Davis
> https://carlingfordweather.sydney
>
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] 3.9.1 PIL & Pillow

[Darryn Capes-Davis]

All,

Just upgraded to 3.9.1. On suggestion from Gary I took the graphing styles 
from the seasons Skin to put into my Responsive Skin 
(https://darryn.capes-davis.com/2016/10/23/weewx-weather-software-responsive-skin/).
 
The small issue was that the Axes labels (both X and Y) were offset by a 
pixel or two, with the bottom X axis label being cut off. Looking into it, 
weewx positions the labels based on their size, so I concluded that PIL 
(Pillow) must have had an issue. Checking it out (use command 'pip list') 
my pillow was at 2.3. So I went through the process to upgrade pillow to 
5.4 which solved the issue.

NOTE: Upgrade to pillow was not straightforward. I encountered some issues 
so I include some links below which helped me across these two issues.

https://stackoverflow.com/questions/44043906/the-headers-or-library-files-could-not-be-found-for-jpeg-installing-pillow-on
https://stackoverflow.com/questions/4011705/python-the-imagingft-c-module-is-not-installed


Regards

Darryn Capes-Davis
https://carlingfordweather.sydney


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Modify the elements on the website - newbie questions

[mwall]

On Monday, February 11, 2019 at 6:34:46 PM UTC-5, Wiggytoo wrote:
>
> Many thanks, I've tracked down the templates and will take another look. 
>
> Would the changes be easier if I were using one of the standard weewx 
> skins?
>

the Seasons skin is a bit more modular than past skins, so it is a little 
easier to customize as you are trying to do.

but the process is the same for any skin.

take a look at this derivative of the Seasons skin:

https://github.com/matthewwall/weewx-4seasons

i started with Seasons, but i made the display of data (values and plots) 
conditional upon the existence of data. as a result, the skin is a bit more 
adaptive and should require less customization.

it is a work in progress, but it might give you some ideas for how to 
customize your templates.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Problems converting to MySQL database

[Jeremy Rousseau]

Thomas,

Lets go with FALSE ALARM at this point. Data is showing up and I am able to 
query the msyql database. Sorry for any troubles. I will delete the post.

-jwr

On Monday, February 11, 2019 at 5:16:49 PM UTC-7, Thomas Keffer wrote:
>
> Hello, Jeremy,
>
> You're not giving us much information. Did you follow the instructions in 
> the wiki guide *Transfer from sqlite to MySQL 
> *
> ?
>
> Don't know what you mean by "no graphing." Your website showed some graphs 
> that look reasonable. Perhaps you could tell us what you expected?
>
> You're also not telling us what didn't work about the ALTER TABLE command.
>
> -tk
>
> On Mon, Feb 11, 2019 at 3:53 PM Jeremy Rousseau  > wrote:
>
>> I'm attempting to convert from a sqlite db to a mysql db. I'm getting 
>> records in mysql but no graphing.
>>
>> I did run into an issue with attempting to run this command "ALTER TABLE 
>> *your-wview-archive-name* CHANGE arcInt `interval` INTEGER NOT NULL;"
>>
>> I changed the command to match my environment but it never worked.
>>
>> Link to site: http://jeremyrousseau.me/weather/index.html
>>
>> I am OK with wiping out weewx and starting over but not sure would 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Problems converting to MySQL database

[Thomas Keffer]

Hello, Jeremy,

You're not giving us much information. Did you follow the instructions in
the wiki guide *Transfer from sqlite to MySQL
*
?

Don't know what you mean by "no graphing." Your website showed some graphs
that look reasonable. Perhaps you could tell us what you expected?

You're also not telling us what didn't work about the ALTER TABLE command.

-tk

On Mon, Feb 11, 2019 at 3:53 PM Jeremy Rousseau 
wrote:

> I'm attempting to convert from a sqlite db to a mysql db. I'm getting
> records in mysql but no graphing.
>
> I did run into an issue with attempting to run this command "ALTER TABLE
> *your-wview-archive-name* CHANGE arcInt `interval` INTEGER NOT NULL;"
>
> I changed the command to match my environment but it never worked.
>
> Link to site: http://jeremyrousseau.me/weather/index.html
>
> I am OK with wiping out weewx and starting over but not sure would 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Modify the elements on the website - newbie questions

[Wiggytoo]

Many thanks, I've tracked down the templates and will take another look. 

Would the changes be easier if I were using one of the standard weewx skins?

Thanks 
Gav 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: NOAA reports not available

[bgrattan]

Thanks for the time you spent on this. I'll try eliminating things until I 
find it. I may even have to reinstall weewx.  Much appreciated for the 
help.   Bob 

On Monday, February 11, 2019 at 5:59:39 PM UTC-5, mwall wrote:
>
> On Saturday, February 9, 2019 at 9:19:27 AM UTC-5, bgrattan wrote:
>>
>> Matt,
>> Here are the three files. ForecastVariables is commented out. I can 
>> change it if you need. NOAA drop down menus now work.  Thanks.  Bob
>>
>
> i cannot replicate the behavior you are seeing.  no matter what i do, the 
> NOAA menus are always generated properly.
>
> there must be something else about your environment that is causing the 
> problem, but i am at a loss as to what that might be.
>
> you could try disabling all of your other reports - leave only the 
> standard report enabled.  then enable/disable ForecastVariables to see if 
> you get the same behavior.
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Modify the elements on the website - newbie questions

[Thomas Keffer]

You'd have to ask the newwx author for a definitive opinion, but odds are
you need to modify a template in its skin subdirectory, which is probably
either /etc/weewx/skins/neowx if you did a Debian install, or
/home/weewx/skins/neowx if you did a setup.py install. I may have the exact
name off.

Inside that subdirectory should be all the template files, which end with a
suffix .tmpl.

-tk



On Mon, Feb 11, 2019 at 3:12 PM Wiggytoo  wrote:

> Hi,
>
> I have installed weewx and connected it to my Netatmo weather station, at
> this point it is collecting temp etc. I don't have the rain or wind gauge.
>
> I am using the neowx skin for now and have got that working to generate a
> website and ftp it to the Web.
>
> I want to comment out the wind and other elements from my website until I
> add the rain and wind sensors.
>
> I can't quite unpick the place to do this despite reading the
> customization pages, the customization I want seems trivial in comparison,
> what am I missing?
>
> Any guidance welcome.
>
> Thanks
> Gav
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Modify the elements on the website - newbie questions

[Wiggytoo]

Hi,

I have installed weewx and connected it to my Netatmo weather station, at this 
point it is collecting temp etc. I don't have the rain or wind gauge.

I am using the neowx skin for now and have got that working to generate a 
website and ftp it to the Web.

I want to comment out the wind and other elements from my website until I add 
the rain and wind sensors. 

I can't quite unpick the place to do this despite reading the customization 
pages, the customization I want seems trivial in comparison, what am I missing? 

Any guidance welcome. 

Thanks 
Gav

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: NOAA reports not available

[mwall]

On Saturday, February 9, 2019 at 9:19:27 AM UTC-5, bgrattan wrote:
>
> Matt,
> Here are the three files. ForecastVariables is commented out. I can change 
> it if you need. NOAA drop down menus now work.  Thanks.  Bob
>

i cannot replicate the behavior you are seeing.  no matter what i do, the 
NOAA menus are always generated properly.

there must be something else about your environment that is causing the 
problem, but i am at a loss as to what that might be.

you could try disabling all of your other reports - leave only the standard 
report enabled.  then enable/disable ForecastVariables to see if you get 
the same behavior.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx is stopping with errors

[vince]

On Monday, February 11, 2019 at 2:28:15 PM UTC-8, ted frohling wrote:

> *Feb 11 10:30:18 weewx weewx[26950]: File 
> "/usr/share/weewx/weewx/accum.**py", line 77, in addHiLo*
> *Feb 11 10:30:18 weewx weewx[26950]:   raise 
> ValueError("accum: ScalarStats.addHiLo expected float or int, got %s" % 
> val)*
> *Feb 11 10:30:18 weewx weewx[26950]:   ValueError: accum: 
> ScalarStats.addHiLo expected float or int, got 7928150*
>
>
Looks to me like you have a string in your data wherever that 7928150 is 
located.
That's an unusual value that doesn't look like a timestamp or anything I 
can think of.

Have you messed with your data at all ?  Tried to fix bad data or the like 
perhaps ?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx is stopping with errors

[ted frohling]

I recently upgraded the Pi that I'm running weewx on.  Did the usual 
install with a down
load.  I saved my old weewx.conf file and started it.   Found that weewx 
was stopping.

Here's the logfile with debug set to 1.

Feb 11 10:30:18 weewx weewx[26950]: manager: Added record 2019-02-11 
10:30:19 MST (1549906219) to database 'cmon.sdb'
Feb 11 10:30:18 weewx weewx[26950]: engine: Main loop exiting. Shutting 
engine down.
Feb 11 10:30:18 weewx weewx[26950]: engine: Shutting down StdReport thread
Feb 11 10:30:18 weewx weewx[26950]: engine: StdReport thread has been 
terminated
Feb 11 10:30:18 weewx weewx[26950]: restx: Shut down WOW thread.
Feb 11 10:30:18 weewx weewx[26950]: restx: Shut down CWOP thread.
Feb 11 10:30:18 weewx weewx[26950]: restx: Shut down PWSWeather thread.
Feb 11 10:30:18 weewx weewx[26950]: restx: Shut down Wunderground-PWS 
thread.
Feb 11 10:30:18 weewx weewx[26950]: engine: Caught unrecoverable exception 
in engine:
Feb 11 10:30:18 weewx weewx[26950]:   accum: ScalarStats.addHiLo 
expected float or int, got 7928150
Feb 11 10:30:18 weewx weewx[26950]:   Traceback (most recent call 
last):
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/engine.py", line 890, in main
Feb 11 10:30:18 weewx weewx[26950]:   engine.run()
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/engine.py", line 202, in run
Feb 11 10:30:18 weewx weewx[26950]:   
self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Feb 11 10:30:18 weewx weewx[26950]:   callback(event)
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/engine.py", line 580, in post_loop
Feb 11 10:30:18 weewx weewx[26950]:   
self._catchup(self.engine.console.genArchiveRecords)
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/engine.py", line 635, in _catchup
Feb 11 10:30:18 weewx weewx[26950]:   origin='hardware'))
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Feb 11 10:30:18 weewx weewx[26950]:   callback(event)
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/user/cmon.py", line 319, in new_archive_record
Feb 11 10:30:18 weewx weewx[26950]:   
self.save_data(self.get_data(now, self.last_ts))
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/user/cmon.py", line 326, in save_data
Feb 11 10:30:18 weewx weewx[26950]:   self.dbm.addRecord(record)
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/manager.py", line 246, in addRecord
Feb 11 10:30:18 weewx weewx[26950]:   
self._addSingleRecord(record, cursor, log_level)
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
Feb 11 10:30:18 weewx weewx[26950]:   
_day_summary.addRecord(record, weight=_weight)
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/accum.py", line 256, in addRecord
Feb 11 10:30:18 weewx weewx[26950]:   func(self, record, 
obs_type, add_hilo, weight)
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/accum.py", line 314, in add_value
Feb 11 10:30:18 weewx weewx[26950]:   
self[obs_type].addHiLo(val, record['dateTime'])
Feb 11 10:30:18 weewx weewx[26950]: File 
"/usr/share/weewx/weewx/accum.py", line 77, in addHiLo
Feb 11 10:30:18 weewx weewx[26950]:   raise ValueError("accum: 
ScalarStats.addHiLo expected float or int, got %s" % val)
Feb 11 10:30:18 weewx weewx[26950]:   ValueError: accum: 
ScalarStats.addHiLo expected float or int, got 7928150
Feb 11 10:30:18 weewx weewx[26950]:   Exiting.


Here's the config file with usernames and passwords emptied.

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

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.1

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Agua Caliente Park Area, Tucson, AZ"

# 

Re: [weewx-user] Re: CloudMQTT & Belchertown Skin

[Tom Mitchell]

Yes! That simple.

--
Tom Mitchell
t...@tom.org
Real Time Beverly, MA Weather
http://weather.tom.org

"The whole problem with the world
  is that fools and fanatics are
  always so certain of themselves,
  and wiser people so full of doubts."
  - Bertrand Russell


On Mon, Feb 11, 2019 at 3:49 PM Pat  wrote:

> Thanks Tom. No need to authenticate to post to the topic? It's a public
> broker?
>
> On Monday, February 11, 2019 at 3:46:32 PM UTC-5, Tom Mitchell wrote:
>>
>> Here is what worked for me:
>>
>> [[MQTT]]
>> server_url = mqtt://broker.hivemq.com:1883
>> topic = topic/subtopic
>> unit_system = US
>> binding = archive, loop
>> aggregation = aggregate
>>
>>
>> ...
>> [[[Extras]]]
>> # Set to 1 to enable the real-time streaming website updates from your
>> MQTT broker (server)
>> mqtt_enabled = 1
>> mqtt_ssl = 0
>> mqtt_host = broker.hivemq.com # The MQTT broker hostname or IP
>> mqtt_port = 8000 # The port of the MQTT broker's Websockets port. Check
>> your broker's documentation.
>> mqtt_topic = "topic/subtopic/#" # The topic to subscribe to for your
>> weather data
>> disconnect_live_website_visitor = 180 #The number of seconds after a
>> visitor has loaded your page that we disconnect them from the live
>> streaming updates. The idea here is to save your broker from a streaming
>> connection that never ends. Time is in milliseconds. 0 = disabled. 30 =
>> 5 minutes. 180 = 30 minutes
>>
>> --
>> Tom Mitchell
>> t...@tom.org
>> Real Time Beverly, MA Weather
>> http://weather.tom.org
>>
>> "The whole problem with the world
>>   is that fools and fanatics are
>>   always so certain of themselves,
>>   and wiser people so full of doubts."
>>   - Bertrand Russell
>>
>>
>> On Mon, Feb 11, 2019 at 3:18 PM Pat  wrote:
>>
>>> Feel free to share your hivemq settings that worked for you and I'll
>>> update the skin's wiki file.
>>>
>>> On Monday, February 11, 2019 at 1:38:08 PM UTC-5, Colin Larsen wrote:

 Same here. Built my own MQTT server, no problems at all

 Colin

 On Tue, 12 Feb 2019, 00:52 Tom Mitchell >>>
> Never got it to work - just switched to hivemq and all is good.
>
> --
> Tom Mitchell
> t...@tom.org
> Real Time Beverly, MA Weather
> http://weather.tom.org
>
> "The whole problem with the world
>   is that fools and fanatics are
>   always so certain of themselves,
>   and wiser people so full of doubts."
>   - Bertrand Russell
>
>
> On Sun, Feb 10, 2019 at 12:26 PM vince  wrote:
>
>> On Monday, September 24, 2018 at 7:11:05 PM UTC-7, G Hammer wrote:
>>>
>>> Is anyone using CloudMQTT broker with the Belchertown skin?
>>> I have data published to the broker, but will not connect via
>>> SSL/TLS Websockets.
>>> I can connect via TLS websockets using a different client.
>>>
>>>
>>>
>> I'd lean toward it being a cert problem in how you configured
>> Belchertown (just a guess)
>> Did you do it ala his docs at
>> https://github.com/poblabs/weewx-belchertown#mqtt-optional ?
>>
>>
>>
>>
>> --
>> 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/cXlnH9kui9U/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx-user+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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/cXlnH9kui9U/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/cXlnH9kui9U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: CloudMQTT & Belchertown Skin

[Pat]

Thanks Tom. No need to authenticate to post to the topic? It's a public 
broker?

On Monday, February 11, 2019 at 3:46:32 PM UTC-5, Tom Mitchell wrote:
>
> Here is what worked for me:
>
> [[MQTT]] 
> server_url = mqtt://broker.hivemq.com:1883 
> topic = topic/subtopic 
> unit_system = US 
> binding = archive, loop 
> aggregation = aggregate 
>
>
> ...
> [[[Extras]]]
> # Set to 1 to enable the real-time streaming website updates from your 
> MQTT broker (server) 
> mqtt_enabled = 1 
> mqtt_ssl = 0 
> mqtt_host = broker.hivemq.com # The MQTT broker hostname or IP 
> mqtt_port = 8000 # The port of the MQTT broker's Websockets port. Check 
> your broker's documentation. 
> mqtt_topic = "topic/subtopic/#" # The topic to subscribe to for your 
> weather data 
> disconnect_live_website_visitor = 180 #The number of seconds after a 
> visitor has loaded your page that we disconnect them from the live 
> streaming updates. The idea here is to save your broker from a streaming 
> connection that never ends. Time is in milliseconds. 0 = disabled. 30 = 
> 5 minutes. 180 = 30 minutes 
>
> --
> Tom Mitchell
> t...@tom.org 
> Real Time Beverly, MA Weather
> http://weather.tom.org
>
> "The whole problem with the world
>   is that fools and fanatics are
>   always so certain of themselves,
>   and wiser people so full of doubts."
>   - Bertrand Russell
>
>
> On Mon, Feb 11, 2019 at 3:18 PM Pat > 
> wrote:
>
>> Feel free to share your hivemq settings that worked for you and I'll 
>> update the skin's wiki file. 
>>
>> On Monday, February 11, 2019 at 1:38:08 PM UTC-5, Colin Larsen wrote:
>>>
>>> Same here. Built my own MQTT server, no problems at all
>>>
>>> Colin
>>>
>>> On Tue, 12 Feb 2019, 00:52 Tom Mitchell >>
 Never got it to work - just switched to hivemq and all is good.

 --
 Tom Mitchell
 t...@tom.org
 Real Time Beverly, MA Weather
 http://weather.tom.org

 "The whole problem with the world
   is that fools and fanatics are
   always so certain of themselves,
   and wiser people so full of doubts."
   - Bertrand Russell


 On Sun, Feb 10, 2019 at 12:26 PM vince  wrote:

> On Monday, September 24, 2018 at 7:11:05 PM UTC-7, G Hammer wrote:
>>
>> Is anyone using CloudMQTT broker with the Belchertown skin?
>> I have data published to the broker, but will not connect via SSL/TLS 
>> Websockets.
>> I can connect via TLS websockets using a different client.
>>
>>
>>
> I'd lean toward it being a cert problem in how you configured 
> Belchertown (just a guess)
> Did you do it ala his docs at 
> https://github.com/poblabs/weewx-belchertown#mqtt-optional ?
>
>
>  
>
> -- 
> 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/cXlnH9kui9U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> 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/cXlnH9kui9U/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: CloudMQTT & Belchertown Skin

[Tom Mitchell]

Here is what worked for me:

[[MQTT]]
server_url = mqtt://broker.hivemq.com:1883
topic = topic/subtopic
unit_system = US
binding = archive, loop
aggregation = aggregate


...
[[[Extras]]]
# Set to 1 to enable the real-time streaming website updates from your MQTT
broker (server)
mqtt_enabled = 1
mqtt_ssl = 0
mqtt_host = broker.hivemq.com # The MQTT broker hostname or IP
mqtt_port = 8000 # The port of the MQTT broker's Websockets port. Check
your broker's documentation.
mqtt_topic = "topic/subtopic/#" # The topic to subscribe to for your
weather data
disconnect_live_website_visitor = 180 #The number of seconds after a
visitor has loaded your page that we disconnect them from the live
streaming updates. The idea here is to save your broker from a streaming
connection that never ends. Time is in milliseconds. 0 = disabled. 30 =
5 minutes. 180 = 30 minutes

--
Tom Mitchell
t...@tom.org
Real Time Beverly, MA Weather
http://weather.tom.org

"The whole problem with the world
  is that fools and fanatics are
  always so certain of themselves,
  and wiser people so full of doubts."
  - Bertrand Russell


On Mon, Feb 11, 2019 at 3:18 PM Pat  wrote:

> Feel free to share your hivemq settings that worked for you and I'll
> update the skin's wiki file.
>
> On Monday, February 11, 2019 at 1:38:08 PM UTC-5, Colin Larsen wrote:
>>
>> Same here. Built my own MQTT server, no problems at all
>>
>> Colin
>>
>> On Tue, 12 Feb 2019, 00:52 Tom Mitchell >
>>> Never got it to work - just switched to hivemq and all is good.
>>>
>>> --
>>> Tom Mitchell
>>> t...@tom.org
>>> Real Time Beverly, MA Weather
>>> http://weather.tom.org
>>>
>>> "The whole problem with the world
>>>   is that fools and fanatics are
>>>   always so certain of themselves,
>>>   and wiser people so full of doubts."
>>>   - Bertrand Russell
>>>
>>>
>>> On Sun, Feb 10, 2019 at 12:26 PM vince  wrote:
>>>
 On Monday, September 24, 2018 at 7:11:05 PM UTC-7, G Hammer wrote:
>
> Is anyone using CloudMQTT broker with the Belchertown skin?
> I have data published to the broker, but will not connect via SSL/TLS
> Websockets.
> I can connect via TLS websockets using a different client.
>
>
>
 I'd lean toward it being a cert problem in how you configured
 Belchertown (just a guess)
 Did you do it ala his docs at
 https://github.com/poblabs/weewx-belchertown#mqtt-optional ?




 --
 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/cXlnH9kui9U/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 weewx-user+...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/cXlnH9kui9U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: CloudMQTT & Belchertown Skin

[Pat]

Feel free to share your hivemq settings that worked for you and I'll update 
the skin's wiki file. 

On Monday, February 11, 2019 at 1:38:08 PM UTC-5, Colin Larsen wrote:
>
> Same here. Built my own MQTT server, no problems at all
>
> Colin
>
> On Tue, 12 Feb 2019, 00:52 Tom Mitchell  wrote:
>
>> Never got it to work - just switched to hivemq and all is good.
>>
>> --
>> Tom Mitchell
>> t...@tom.org 
>> Real Time Beverly, MA Weather
>> http://weather.tom.org
>>
>> "The whole problem with the world
>>   is that fools and fanatics are
>>   always so certain of themselves,
>>   and wiser people so full of doubts."
>>   - Bertrand Russell
>>
>>
>> On Sun, Feb 10, 2019 at 12:26 PM vince > 
>> wrote:
>>
>>> On Monday, September 24, 2018 at 7:11:05 PM UTC-7, G Hammer wrote:

 Is anyone using CloudMQTT broker with the Belchertown skin?
 I have data published to the broker, but will not connect via SSL/TLS 
 Websockets.
 I can connect via TLS websockets using a different client.



>>> I'd lean toward it being a cert problem in how you configured 
>>> Belchertown (just a guess)
>>> Did you do it ala his docs at 
>>> https://github.com/poblabs/weewx-belchertown#mqtt-optional ?
>>>
>>>
>>>  
>>>
>>> -- 
>>> 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/cXlnH9kui9U/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: CloudMQTT & Belchertown Skin

[Colin Larsen]

Same here. Built my own MQTT server, no problems at all

Colin

On Tue, 12 Feb 2019, 00:52 Tom Mitchell  Never got it to work - just switched to hivemq and all is good.
>
> --
> Tom Mitchell
> t...@tom.org
> Real Time Beverly, MA Weather
> http://weather.tom.org
>
> "The whole problem with the world
>   is that fools and fanatics are
>   always so certain of themselves,
>   and wiser people so full of doubts."
>   - Bertrand Russell
>
>
> On Sun, Feb 10, 2019 at 12:26 PM vince  wrote:
>
>> On Monday, September 24, 2018 at 7:11:05 PM UTC-7, G Hammer wrote:
>>>
>>> Is anyone using CloudMQTT broker with the Belchertown skin?
>>> I have data published to the broker, but will not connect via SSL/TLS
>>> Websockets.
>>> I can connect via TLS websockets using a different client.
>>>
>>>
>>>
>> I'd lean toward it being a cert problem in how you configured Belchertown
>> (just a guess)
>> Did you do it ala his docs at
>> https://github.com/poblabs/weewx-belchertown#mqtt-optional ?
>>
>>
>>
>>
>> --
>> 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/cXlnH9kui9U/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: version 3.9.1 (skin Season)

[Patrick Tranchant]

I needed the graph " soilTemp1 "
but now is OK, I could add
Patrick

On Monday, February 11, 2019 at 6:57:48 PM UTC+1, Patrick Tranchant wrote:
>
> Hello,
> I just installed version 3.9.1. I found the files to modify to put the 
> names in French;
> I still have to add a Graph that does not appear on the basic version 
> (Seasons skin); how to add a graph?
> thank you.
>
> Patrick
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: version 3.9.1 (skin Season)

[Andrew Milner]

What are you wanting to add??

To answer the question - modify weewx/skins/Seasons/skin.conf  to have the 
graph created and modify the template(s) in 
weewx/skins/Seasons/x.html.tmpl to include the graph on the required 
web page(s)



On Monday, 11 February 2019 19:57:48 UTC+2, Patrick Tranchant wrote:
>
> Hello,
> I just installed version 3.9.1. I found the files to modify to put the 
> names in French;
> I still have to add a Graph that does not appear on the basic version 
> (Seasons skin); how to add a graph?
> thank you.
>
> Patrick
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] version 3.9.1 (skin Season)

[Patrick Tranchant]

Hello,
I just installed version 3.9.1. I found the files to modify to put the 
names in French;
I still have to add a Graph that does not appear on the basic version 
(Seasons skin); how to add a graph?
thank you.

Patrick

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: timesync vs NTP on Raspberry Pi 3B+

[V. Kelly Bellis]

Many thanks Vince and Scott. 

On Sunday, February 10, 2019 at 7:24:12 PM UTC-5, Scott Grayban wrote:
>
> If you look 
> at 
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
>
> # don't run timesyncd if we have another NTP daemon installed
> *ConditionFileIsExecutable=!/usr/sbin/ntpd*
> ConditionFileIsExecutable=!/usr/sbin/openntpd
> ConditionFileIsExecutable=!/usr/sbin/chronyd
> ConditionFileIsExecutable=!/usr/sbin/VBoxService
>
> So it's completely disabled with NTP
>
> On Sunday, February 10, 2019 at 11:05:40 AM UTC-8, vince wrote:
>>
>> On Sunday, February 10, 2019 at 10:44:48 AM UTC-8, V. Kelly Bellis wrote:
>>>
>>> http://weewx.com/docs/usersguide.htm states that I should run a NTP 
>>>  daemon, but doesn't address an existing/ running 
>>> pre-installed timesync service; e.g., installed with Raspbian via NOOBS
>>>
>>> Elsewhere , 
>>> we read that timesync and NTP should not be run at the same time - "*but 
>>> you can not have running both of them at the same time*"
>>>
>>> Is the pre-installed timesync sufficient for weewx? Either way, could 
>>> the users guide include some mention of timesync's shortcomings or 
>>> sufficiency insofar as weewx is concerned?
>>>
>>>
>>>
>> The users guide can't/shouldn't try to cover all the nuances of every 
>> operating system nor the sheer unfettered joy that is systemd (ha - beat 
>> Matthew to it!)
>>
>> What happens is if you run NTP, systemd gets out of the way and doesn't 
>> enable its ntp hack/feature/whatever.
>>
>> So, FWIW, I always run NTP because I have decades of positive experience 
>> with that software.   It's a well-understood thing.   Much easier to debug 
>> when that's needed.
>>
>> (and any time I can disable systemd 'helping' me, I tend to do so.  That 
>> thing is much harder to debug when it goes whacko.)
>>  
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: RTL-SDR setup help

[torrin]

Heh, yup, that is what I get for trying to do this from memory.  I do not 
see the WH24 mapped in your confrig, and perhaps the error in the log is 
you have logging turned on for unknown protocols.  Try this in your SDR 
section:

[SDR]
# This section is for the software-defined radio driver.

# The driver to use
driver = user.sdr
path = /usr/local/bin
cmd = rtl_433 -q -M utc -F json -p 39.741 -R 78 -f 91498
[[sensor_map]]
outTemp = temperature.140.FOWH24Packet
outHumidity = humidity.140.FOWH24Packet
windDir = wind_dir.140.FOWH24Packet
windSpeed = wind_speed.140.FOWH24Packet
windGust = wind_gust.140.FOWH24Packet
rain_total = rain_total.140.FOWH24Packet
UV = uv_index.140.FOWH24Packet
radiation = light.140.FOWH24Packet
outTempBatteryStatus = battery.140.FOWH24Packet
inTemp = temperature.104.FOWH25Packet
inHumidity = humidity.104.FOWH25Packet
pressure = pressure.104.FOWH25Packet
inTempBatteryStatus = battery.104.FOWH25Packet
[[deltas]]
rain = rain_total


On Monday, February 11, 2019 at 5:24:06 AM UTC-6, N0ZO wrote:
>
> Is -p not for the ppm offset error?
> I think -R is the one needed to select 78 for the device type. I tried 
> switching it around both ways, and still get the exact same error.
>
>
>
> On Sunday, February 10, 2019 at 10:26:18 PM UTC-6, tor...@torrin.org 
> wrote:
>>
>> You're running protocol 66 and the WH24 is 78.  Try this:
>>
>>
>> rtl_433 -M utc -F json  -p 78 -f 91500
>>
>> (you don't need -G here, since you don't want all protocols turned on)  
>> Also, please post your entire weewx.conf, especially the SDR section.
>>
>>
>> On Sunday, February 10, 2019 at 10:09:04 PM UTC-6, N0ZO wrote:
>>>
>>> So I've wanted to use SDR to capture the data of the ObserverIP that I 
>>> have. I have the WS-1400-IP which is a rebranded HP-1000 by Fine Offset.
>>> It took me forever to actually get where my Pi3B could read the data 
>>> from the SDR. But now I finally got that working when I setup weewx by the 
>>> setup.py method.
>>>
>>> Now I have hit a block that I'm not sure I can figure out, especially 
>>> since I'm not finding anything of a fix on the internet.
>>>
>>> Running sudo PYTHONPATH=bin python bin/user/sdr.py --cmd="rtl_433 -M utc 
 -F json -G -p 66 -f 91500"
>>>
>>>
>>> gives me this:
>>>
>>>  out: ['{"time" : "2019-02-11 03:44:32", "model" : "Fine Offset WH24", 
 "id" : 140, "temperature_C" : 12.600, "humidity" : 80, "wind_dir_deg" : 
 111, "wind_speed_ms" : 0.280, "gust_speed_ms" : 1.120, "rainfall_mm" : 
 1150.800, "uv" : 1, "uvi" : 0, "light_lux" : 0.000, "battery" : "OK", 
 "mic" 
 : "CRC"}\n', '{"time" : "2019-02-11 03:44:33", "model" : "Fine Offset 
 Electronics, WH25", "id" : 104, "temperature_C" : 20.000, "humidity" : 57, 
 "pressure_hPa" : 1004.100, "battery" : "OK", "mic" : "CHECKSUM"}\n']
 parsed: {'temperature.104.FOWH25Packet': 20.0, 
 'battery.104.FOWH25Packet': 0, 'dateTime': 1549856673, 
 'humidity.104.FOWH25Packet': 57.0, 'pressure.104.FOWH25Packet': 1004.1, 
 'usUnits': 16}
 out: ['{"time" : "2019-02-11 03:44:48", "model" : "Fine Offset WH24", 
 "id" : 140, "temperature_C" : 12.600, "humidity" : 80, "wind_dir_deg" : 
 109, "wind_speed_ms" : 0.980, "gust_speed_ms" : 1.120, "rainfall_mm" : 
 1150.800, "uv" : 1, "uvi" : 0, "light_lux" : 0.000, "battery" : "OK", 
 "mic" 
 : "CRC"}\n']
>>>
>>>
>>> Under parsed I get that I can now enter the temperature.104.FOWH25Packet 
>>> under the  [[Sensor_map]] under SDR. I also understand that my indoor 
>>> device is the Fine Offset WH25, and the outdoor is the Fine Offset WH24. 
>>> But part of what I can't figure out is this:
>>> It gave me the detail I needed for the Sensor_Map when it parsed the 
>>> WH25, but it didn't do that for WH24. I think my questions may be linked in 
>>> a way since it didn't parse that out. 
>>>
>>> Now, when I run weewx instead of the sdr.py, I get this:
>>>
>>> Feb 10 21:50:27 raspberrypi weewx[2692]: sdr: MainThread: parse_json: 
> unknown model Fine Offset WH24

 Feb 10 21:50:27 raspberrypi weewx[2692]: sdr: MainThread: punt 
> unrecognized line '{"time" : "2019-02-11 03:50:24", "model" : "Fine 
> Offset 
> WH24", "id" : 140, "temperature_C" : 12.600, "humidity" : 81, 
> "wind_dir_deg" : 152, "wind_speed_ms" : 0.840, "gust_speed_ms" : 1.120, 
> "rainfall_mm" : 1150.800, "uv" : 1, "uvi" : 0, "light_lux" : 0.000, 
> "battery" : "OK", "mic" : "CRC"}#012'

 Weewx is generating without error, and even has the inside temperature 
>>> on the page it generated in public_html
>>>
>>> I can provide actual logs if needed, but I'm thinking it's some issue 
>>> that I'm not seeing either with rtl_433 or something I missed in a setting 
>>> with weewx.
>>>
>>> Also, I'm not sure if it matters or not, but I ran this line under SDR 
>>> so that it 

[weewx-user] Re: Belchertown Skin 0.8.2 Released

[Andrew Milner]

well it won't change by itself once the data is in the database

You could run wee_database and drop daily and then rebuild daily - this 
will rebuild the daily tables (which contain the hi/low data) from the data 
in the archive table, which would not include any loop hi/low data.  see 
the utilities manual and take a copy of your database sdb file before 
manipulating the database - just as a precaution

my earlier changes/suggestions would only affect future rainfall.



onday, 11 February 2019 13:00:47 UTC+2, Adnan Mumtaz wrote:

> Tried both options by removing Hi/Lo and using sofware as preferred 
> calculation with both the number didnt change.
>
> On Monday, 11 February 2019 10:24:07 UTC+3, Andrew Milner wrote:
>>
>> It is more than likely a result of multiplying a loop value to get an 
>> hourly value.  Best 'solution' is to NOT use loop Hi/Lo for daily data by 
>> setting weewx.conf accordingly.  An alternative (or as well) is to use 
>> software preferred for rain rate and let weewx calculate the rate using its 
>> sliding window.
>>
>>
>>
>> On Monday, 11 February 2019 08:48:29 UTC+2, Adnan Mumtaz wrote:
>>>
>>> Experienced first good rain since I installed the WS, I see the highest 
>>> rate 1680 mm/hr and total rain rate 3.8 mm which is correct, but i dont 
>>> know how it calculated 1680 mm/hr, dont know if this is correct. 
>>> http://www.riyadhweather.com
>>>
>>> On Saturday, 2 February 2019 19:38:03 UTC+3, Juan Antonio Mosquera wrote:

 The internationalization would be very interesting. That way we would 
 not have to change the code with each update. Thank you for your work.

 El sábado, 2 de febrero de 2019, 13:57:13 (UTC+1), Pat escribió:
>
> Thanks. I'm working on skin version 0.9 now which I'm hoping to 
> release soon. Many bug fixes.
>
> To change the chart names, check the files within 
> skins/Highcharts_Belchertown/json
>
> I haven't had a chance to look into internationalization yet. 
> Hopefully soon.
>
>
>
> On Saturday, February 2, 2019 at 7:35:31 AM UTC-5, opc...@gmail.com 
> wrote:
>>
>> Hi Guys!Thank you, Pat, for the great skin! I am about to translate 
>> everything into German. I am currently stuck at renaming the graphs. 
>> Where 
>> do I need to change the titles of the diagrams and also the names of the 
>> single lines?
>>
>>
>> Am Donnerstag, 31. Januar 2019 23:07:46 UTC+1 schrieb Pat:
>>>
>>> The skin is showing the alerts that are downloaded from DarkSky. I 
>>> have no more developer notes than that. If there's too many alerts, you 
>>> can 
>>> reach out to DarkSky themselves to ask about it. 
>>>
>>> On Thursday, January 31, 2019 at 3:32:05 PM UTC-5, mercurystorm 
>>> wrote:

 I just implemented this skin and its fantastic

 I do however seem to be getting to many weather warnings..

 Currently showing 4 weather warnings for my area.. but there is 
 currently only one active on darksky

 https://stormy.ie/weather/live/
 https://darksky.net/forecast/53.3272,-9.1737/ca12/en
 https://www.met.ie/warnings

 Each time the MET seems to update it.. I get another weather 
 warning on my site.. any ideas?

 On Tuesday, 1 January 2019 12:50:49 UTC, Pat wrote:
>
> I've just released version 0.8.2 of the Belchertown skin which 
> fixes the New Year bug some of you are seeing. It also adds some 
> other 
> features. 
>
>
> Download and install instructions here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
>
> * Fixed an error where the skin would fail when the date rolls to 
> the New Year due to no data being in certain tables in the database 
> yet. 
> * Added the ability to show any weather alerts provided by the 
> DarkSky API. Weather alerts are off by default, use 
> forecast_alert_enabled 
> in weewx.conf skin options to enable it.
> * New option to show cloudbase. You must have your database schema 
> extended for the cloudbase observation to be calculated by weewx. 
> Check the 
> Belchertown skin wiki for details.
> * Fixes an issue where the MQTT updates showed altimeter instead 
> of barometer.
> * Updated Google Analytics page to be in header based on Google 
> recommendations. 
> * Updated Google Analytics to a more recent script block. 
> * Added a Google Analytics page view per MQTT update as per Google 
> Recommendations on background updates. 
>
>

-- 
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 

Re: [weewx-user] Re: CloudMQTT & Belchertown Skin

[Tom Mitchell]

Never got it to work - just switched to hivemq and all is good.

--
Tom Mitchell
t...@tom.org
Real Time Beverly, MA Weather
http://weather.tom.org

"The whole problem with the world
  is that fools and fanatics are
  always so certain of themselves,
  and wiser people so full of doubts."
  - Bertrand Russell


On Sun, Feb 10, 2019 at 12:26 PM vince  wrote:

> On Monday, September 24, 2018 at 7:11:05 PM UTC-7, G Hammer wrote:
>>
>> Is anyone using CloudMQTT broker with the Belchertown skin?
>> I have data published to the broker, but will not connect via SSL/TLS
>> Websockets.
>> I can connect via TLS websockets using a different client.
>>
>>
>>
> I'd lean toward it being a cert problem in how you configured Belchertown
> (just a guess)
> Did you do it ala his docs at
> https://github.com/poblabs/weewx-belchertown#mqtt-optional ?
>
>
>
>
> --
> 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/cXlnH9kui9U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: RTL-SDR setup help

[N0ZO]

Is -p not for the ppm offset error?
I think -R is the one needed to select 78 for the device type. I tried 
switching it around both ways, and still get the exact same error.



On Sunday, February 10, 2019 at 10:26:18 PM UTC-6, tor...@torrin.org wrote:
>
> You're running protocol 66 and the WH24 is 78.  Try this:
>
>
> rtl_433 -M utc -F json  -p 78 -f 91500
>
> (you don't need -G here, since you don't want all protocols turned on)  
> Also, please post your entire weewx.conf, especially the SDR section.
>
>
> On Sunday, February 10, 2019 at 10:09:04 PM UTC-6, N0ZO wrote:
>>
>> So I've wanted to use SDR to capture the data of the ObserverIP that I 
>> have. I have the WS-1400-IP which is a rebranded HP-1000 by Fine Offset.
>> It took me forever to actually get where my Pi3B could read the data from 
>> the SDR. But now I finally got that working when I setup weewx by the 
>> setup.py method.
>>
>> Now I have hit a block that I'm not sure I can figure out, especially 
>> since I'm not finding anything of a fix on the internet.
>>
>> Running sudo PYTHONPATH=bin python bin/user/sdr.py --cmd="rtl_433 -M utc 
>>> -F json -G -p 66 -f 91500"
>>
>>
>> gives me this:
>>
>>  out: ['{"time" : "2019-02-11 03:44:32", "model" : "Fine Offset WH24", 
>>> "id" : 140, "temperature_C" : 12.600, "humidity" : 80, "wind_dir_deg" : 
>>> 111, "wind_speed_ms" : 0.280, "gust_speed_ms" : 1.120, "rainfall_mm" : 
>>> 1150.800, "uv" : 1, "uvi" : 0, "light_lux" : 0.000, "battery" : "OK", "mic" 
>>> : "CRC"}\n', '{"time" : "2019-02-11 03:44:33", "model" : "Fine Offset 
>>> Electronics, WH25", "id" : 104, "temperature_C" : 20.000, "humidity" : 57, 
>>> "pressure_hPa" : 1004.100, "battery" : "OK", "mic" : "CHECKSUM"}\n']
>>> parsed: {'temperature.104.FOWH25Packet': 20.0, 
>>> 'battery.104.FOWH25Packet': 0, 'dateTime': 1549856673, 
>>> 'humidity.104.FOWH25Packet': 57.0, 'pressure.104.FOWH25Packet': 1004.1, 
>>> 'usUnits': 16}
>>> out: ['{"time" : "2019-02-11 03:44:48", "model" : "Fine Offset WH24", 
>>> "id" : 140, "temperature_C" : 12.600, "humidity" : 80, "wind_dir_deg" : 
>>> 109, "wind_speed_ms" : 0.980, "gust_speed_ms" : 1.120, "rainfall_mm" : 
>>> 1150.800, "uv" : 1, "uvi" : 0, "light_lux" : 0.000, "battery" : "OK", "mic" 
>>> : "CRC"}\n']
>>
>>
>> Under parsed I get that I can now enter the temperature.104.FOWH25Packet 
>> under the  [[Sensor_map]] under SDR. I also understand that my indoor 
>> device is the Fine Offset WH25, and the outdoor is the Fine Offset WH24. 
>> But part of what I can't figure out is this:
>> It gave me the detail I needed for the Sensor_Map when it parsed the 
>> WH25, but it didn't do that for WH24. I think my questions may be linked in 
>> a way since it didn't parse that out. 
>>
>> Now, when I run weewx instead of the sdr.py, I get this:
>>
>> Feb 10 21:50:27 raspberrypi weewx[2692]: sdr: MainThread: parse_json: 
 unknown model Fine Offset WH24
>>>
>>> Feb 10 21:50:27 raspberrypi weewx[2692]: sdr: MainThread: punt 
 unrecognized line '{"time" : "2019-02-11 03:50:24", "model" : "Fine Offset 
 WH24", "id" : 140, "temperature_C" : 12.600, "humidity" : 81, 
 "wind_dir_deg" : 152, "wind_speed_ms" : 0.840, "gust_speed_ms" : 1.120, 
 "rainfall_mm" : 1150.800, "uv" : 1, "uvi" : 0, "light_lux" : 0.000, 
 "battery" : "OK", "mic" : "CRC"}#012'
>>>
>>> Weewx is generating without error, and even has the inside temperature 
>> on the page it generated in public_html
>>
>> I can provide actual logs if needed, but I'm thinking it's some issue 
>> that I'm not seeing either with rtl_433 or something I missed in a setting 
>> with weewx.
>>
>> Also, I'm not sure if it matters or not, but I ran this line under SDR so 
>> that it captured data:
>>
>> cmd= rtl_433 -M utc -F json -G -p 66 -f 91500
>>
>>
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /home/weewx

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.1

##

#   This section is for information about the station.

[Station]

# Description of the station 

[weewx-user] Re: Belchertown Skin 0.8.2 Released

[Adnan Mumtaz]

Tried both options by removing Hi/Lo and using sofware as preferred 
calculation with both the number didnt change.

On Monday, 11 February 2019 10:24:07 UTC+3, Andrew Milner wrote:
>
> It is more than likely a result of multiplying a loop value to get an 
> hourly value.  Best 'solution' is to NOT use loop Hi/Lo for daily data by 
> setting weewx.conf accordingly.  An alternative (or as well) is to use 
> software preferred for rain rate and let weewx calculate the rate using its 
> sliding window.
>
>
>
> On Monday, 11 February 2019 08:48:29 UTC+2, Adnan Mumtaz wrote:
>>
>> Experienced first good rain since I installed the WS, I see the highest 
>> rate 1680 mm/hr and total rain rate 3.8 mm which is correct, but i dont 
>> know how it calculated 1680 mm/hr, dont know if this is correct. 
>> http://www.riyadhweather.com
>>
>> On Saturday, 2 February 2019 19:38:03 UTC+3, Juan Antonio Mosquera wrote:
>>>
>>> The internationalization would be very interesting. That way we would 
>>> not have to change the code with each update. Thank you for your work.
>>>
>>> El sábado, 2 de febrero de 2019, 13:57:13 (UTC+1), Pat escribió:

 Thanks. I'm working on skin version 0.9 now which I'm hoping to release 
 soon. Many bug fixes.

 To change the chart names, check the files within 
 skins/Highcharts_Belchertown/json

 I haven't had a chance to look into internationalization yet. Hopefully 
 soon.



 On Saturday, February 2, 2019 at 7:35:31 AM UTC-5, opc...@gmail.com 
 wrote:
>
> Hi Guys!Thank you, Pat, for the great skin! I am about to translate 
> everything into German. I am currently stuck at renaming the graphs. 
> Where 
> do I need to change the titles of the diagrams and also the names of the 
> single lines?
>
>
> Am Donnerstag, 31. Januar 2019 23:07:46 UTC+1 schrieb Pat:
>>
>> The skin is showing the alerts that are downloaded from DarkSky. I 
>> have no more developer notes than that. If there's too many alerts, you 
>> can 
>> reach out to DarkSky themselves to ask about it. 
>>
>> On Thursday, January 31, 2019 at 3:32:05 PM UTC-5, mercurystorm wrote:
>>>
>>> I just implemented this skin and its fantastic
>>>
>>> I do however seem to be getting to many weather warnings..
>>>
>>> Currently showing 4 weather warnings for my area.. but there is 
>>> currently only one active on darksky
>>>
>>> https://stormy.ie/weather/live/
>>> https://darksky.net/forecast/53.3272,-9.1737/ca12/en
>>> https://www.met.ie/warnings
>>>
>>> Each time the MET seems to update it.. I get another weather warning 
>>> on my site.. any ideas?
>>>
>>> On Tuesday, 1 January 2019 12:50:49 UTC, Pat wrote:

 I've just released version 0.8.2 of the Belchertown skin which 
 fixes the New Year bug some of you are seeing. It also adds some other 
 features. 


 Download and install instructions here: 
 https://github.com/poblabs/weewx-belchertown/releases


 * Fixed an error where the skin would fail when the date rolls to 
 the New Year due to no data being in certain tables in the database 
 yet. 
 * Added the ability to show any weather alerts provided by the 
 DarkSky API. Weather alerts are off by default, use 
 forecast_alert_enabled 
 in weewx.conf skin options to enable it.
 * New option to show cloudbase. You must have your database schema 
 extended for the cloudbase observation to be calculated by weewx. 
 Check the 
 Belchertown skin wiki for details.
 * Fixes an issue where the MQTT updates showed altimeter instead of 
 barometer.
 * Updated Google Analytics page to be in header based on Google 
 recommendations. 
 * Updated Google Analytics to a more recent script block. 
 * Added a Google Analytics page view per MQTT update as per Google 
 Recommendations on background updates. 



-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: AWEKAS stop accepting my posts

[gjr80]

I suspect that the clue is in the server's response in the log entries:

Feb 08 16:15:56 weewx weewx[13603]: restx: AWEKAS: Failed to publish record 
2019-02-08 16:10:00 MST (1549667400): server returned 'too many requests - 
try again later '
Feb 08 16:15:57 weewx weewx[13603]: restx: AWEKAS: Failed to publish record 
2019-02-08 16:15:00 MST (1549667700): server returned 'too many requests - 
try again later'

I believe that AWEKAS wants you to post data no more often than once every 
5 minutes, the above log entries are for two different records (16:10 and 
16:15) and they were attempted to be posted within a second or two of each 
other. Whilst most services specify the minimum period between posts some 
services ignore more frequent posts and others reject such posts with a 
message. It looks like AWEKAS is the latter type.

By default the AWEKAS uploader should limit posts to be no more frequent 
than once every 5 minutes, but for some reason that does not seem to have 
worked as intended. Just wondering, what kind of station do you have and 
does it have a logger/memory, did this occur after a restart when WeeWX was 
downloading records from a logger? In such cases records are usually 
downloaded quite quickly and the StdRESTful service still operates on these 
downloaded records. Could you post some more of your log from before and 
after these posts. Don't be worried about posting too much, Google has lots 
of storage :). May also help to see the [StdRESTful] section of weewx.conf, 
just make sure you remove any passwords, user names, API keys tokens, etc 
before posting.

Gary


On Saturday, 9 February 2019 11:02:19 UTC+10, ted frohling wrote:
>
> I recently became aware that AWEKAS stopped accepting my weewx uploads.  
> The errors I'm getting in the logs  are:
>
> Feb 08 16:15:56 weewx weewx[13603]: restx: AWEKAS: Failed to publish 
> record 2019-02-08 16:10:00 MST (1549667400): server returned 'too many 
> requests - try again later '
> Feb 08 16:15:57 weewx weewx[13603]: restx: AWEKAS: Failed to publish 
> record 2019-02-08 16:15:00 MST (1549667700): server returned 'too many 
> requests - try again later'
>
> Of course, I've restarted weewx many times.  This is running on a Pi 3.  
> All the other uploads are working just fine.
>
> Any thoughts?
>
> Thanks,
>
> ted
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Can't Post To WOW

[gjr80]

Once you have confirmed your WOW credentials you can set debug = 2 in 
weewx.conf and restart WeeWX. This will up the level of log output from 
StdRESTful (as well as a lot of other things) and you should be able to see 
in the log what is actually being posted to WOW. Your site authentication 
key (PIN?) will be obliterated but you should see everything else. That is 
about the limit of the debug info you can get from WeeWX.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.