Re: [weewx-user] Ecowitt lightning sensor WH57

2024-03-14 Thread Colin Larsen
Sometimes a piezo device will do the trick. A BBQ lighter or such like.

On Fri, 15 Mar 2024, 06:50 Joachim Puttkammer, 
wrote:

> How can I simulate lightning for the WH57 sensor?
>
> --
> 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/9689547b-9855-4e8d-acfb-b89c38aa690en%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/CACjxfUuKV67wDtUO0TQ0h6ECnXpUfEsK87496V_Qpg%3D0pSPSfA%40mail.gmail.com.


Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

2024-01-20 Thread Colin Larsen
I guess he means this "feels like" which as far as I know is a
derived/calculated field in the skin

[image: image.png]

On Sun, 21 Jan 2024 at 03:13, Tom Keffer  wrote:

> Richard, you're going to have to give us more information than this. The
> only reference to "feels like" that I can find in the Belchertown skin has
> been commented out. Where are you seeing this?
>
> On Fri, Jan 19, 2024 at 7:25β€―PM Richard Whitcombe 
> wrote:
>
>> Actually follow up that ive only just noticed.
>> Since performing this fix ive lost the "Feels like" temperature display
>> on my skin on all pages.
>>
>> On Friday 19 January 2024 at 19:47:31 UTC+9 Richard Whitcombe wrote:
>>
>>> I just did AppTemperature but its working for me.
>>> Although i dont think i use any of the other columns as my station
>>> doesnt provide it.
>>>
>>> Missing data calculations took about 8 minutes for 7 years of data on a
>>> Pi4.
>>>
>>> On Friday 19 January 2024 at 19:14:09 UTC+9 mh081...@gmail.com wrote:
>>>
 Hi,

 as i read in the other posts about this Problem i doing now following.

 weectl database add-column appTemp
 weectl database add-column cloudbase
 weectl database add-column visibility
 weectl database add-column windrun
 weectl database add-column cloud_cover
 weectl database add-column aqi

 weectl database calc-missing

 Answer all wit 'y'

 Now it seems that the Problem was solved. Belchertown Reports was
 generated in about 6 seconds. Thanks @vince for your right direction.
 ##
 Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading
 station type Vantage (weewx.drivers.vantage)
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert
 target unit is 0x1
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices:
 StdWXCalculate will use data binding wx_binding
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive will
 use data binding wx_binding
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record
 generation will be attempted in 'hardware'
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using archive
 interval of 300 seconds (specified by hardware)
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx:
 StationRegistry: Registration not requested.
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx:
 Wunderground-PWS: Data for station IMECKLEN47 will be posted
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather:
 Data for station MHROSTOCK will be posted
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: Posting
 not enabled.
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: WOW: Posting
 not enabled.
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: AWEKAS:
 Posting not enabled.
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: service version
 is 0.23
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: binding to
 ['archive', 'loop']
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: topic is weather
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: desired unit
 system is METRIC
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: data will be
 uploaded to mqtt://pi:x...@gw.martenhinrichs.de:8883/
 
 Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: network
 encryption/authentication will be attempted
 Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: 'pyephem'
 detected, extended almanac data is available
 Jan 19 11:09:53 wetter weewxd[293936]: INFO __main__: Starting up weewx
 version 5.0.0
 Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Clock error
 is 2.69 seconds (positive is fast)
 Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Using binding
 'wx_binding' to database 'weewx.sdb'
 Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Starting
 backfill of daily summaries
 Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Daily
 summaries up to date
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.wxxtypes: Type
 beaufort has been deprecated. Use unit beaufort instead.
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
 2024-01-19 10:50:00 CET (1705657800) to database 'weewx.sdb'
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
 2024-01-19 10:50:00 CET (1705657800) to daily summary in 'weewx.sdb'
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
 2024-01-19 10:55:00 CET (1705658100) to database 'weewx.sdb'
 Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record
 2024-01-19 10:55:00 CET (1705658100) to daily summary in 'weewx.sdb'
 Jan 19 11:09:56 wetter weewxd[293936]: IN

Re: [weewx-user] V5.0.0 available

2024-01-14 Thread Colin Larsen
Congratulations on the release of V5 team.
Now I just have to remember how I did my original install 😊

Colin

On Mon, 15 Jan 2024, 11:25 Tom Keffer,  wrote:

> A year in the making, V5 is finally available! Some minor new features,
> but most of the work has been to keep up with the changing world of Python
> --- lots of things have become obsolete (distutils), while others have just
> changed.
>
> A few changes to highlight:
>
>- WeeWX can now be installed using pip. The old setup.py method is
>gone.
>- Support for the latest versions of Python.
>- Improved documentation.
>- The utilities have been pulled together under one master utility,
>weectl, making it easier to find the functionality you need.
>- Management of multiple stations is easier and more modular.
>
> Complete change list .
>
> Quickstart install and upgrade instructions
> .
>
> Be sure to read the Upgrade Guide
> .
>
> - Tom, Matt, and Gary.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEDyOXhODJ_XaCw%3Dcxm9L3B2t3k70Y3L2fkZQwYSyb71Og%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/CACjxfUvkKFUa%3DtmzHqtKvtHZ4f0OnDQAjfeBVZ4hKXUh60M1EQ%40mail.gmail.com.


Re: [weewx-user] want to use lux value to calculate value for 'radiation'

2023-09-27 Thread Colin Larsen
My graph is almost perfect with that calculation

Colin
41south.nz



On Thu, 28 Sept 2023, 11:53 Kevin Crivelli, 
wrote:

> I have the same problem but this didn't work for me. any ideas?
>
> On Tuesday, May 18, 2021 at 6:04:08β€―PM UTC-4 Greg Troxel wrote:
>
>>
>> Eric K  writes:
>>
>> > The Acurite Atlas weather sensor provides a UV and a lux value, but not
>> a
>> > radiation value.
>> > I want to use this formula to calculate solar radiation from the lux
>> sensor
>> > in the Acurite Atlas: radiation = lux * 0.0079
>>
>> See also
>>
>> https://github.com/weewx/weewx/wiki/Watts-and-lux
>>
> --
> 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/1a02cf03-4452-4be4-8ccf-8f7dfbcf899an%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/CACjxfUt8%2BPAr%3DWXLj3WxsPMhCg275xUS%3D3ej%2B0P6yUTfTGuUJg%40mail.gmail.com.


Re: [weewx-user] a followup on light measurement

2023-09-01 Thread Colin Larsen
This may or may not be pertinent from the Ecowitt driver wiki

https://github.com/gjr80/weewx-gw1000/wiki/Understanding-Ecowitt-LAN-Wi-Fi-Gateway-API-radiation-fields

Colin

On Sat, 2 Sept 2023, 12:18 Greg Troxel,  wrote:

> I'm writing a new message since the list is wackily rejecting mail.
>
>
> Total light is an interesting concept, and it is not clear that it makes
> sense.
>
> One could measure an energy flavor of illuminance and thus the units
> would be lux-s or lux-hours.   However, lux is a perceptual unit across
> wavelength, and that raises the question as to how 1 lux for an hour
> compares to 3600 lux for 1s and then total darkness the rest of the
> hour.  That's  extreme, but still.
>
> One could also integrate a radiometric measurement, taking W/m^2 and
> ending up with J/m^2.  This makes clearer physical sense.
>
> I am curious what the conceptual basis and rationale is for what Acurite
> is graphing.  I'm not saying it doesn't make sense, just that it
> immediately seems very tricky.
>
> --
> 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/rmiwmx9a0m5.fsf%40s1.lexort.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/CACjxfUvK8jv6Zxjc9309_dgAPi5rneAfZmtrmHCPdPNv4xa8iw%40mail.gmail.com.


Re: [weewx-user] StdCalibrate/corrections for radiation reading

2023-08-12 Thread Colin Larsen
Thanks Dale - appreciate your thoughts and agree with you. It's always
great to have your thought process tested occasionally :)

Colin

On Sun, 13 Aug 2023 at 12:31, Dale  wrote:

> Just chiming in:  I have had some luck over the years calibrating my
> solar sensor and having it track pretty close to the curve generated to
> predict what the maximum should be.
>
>
> Then I noticed that while most of the time it is within a tiny bit of
> the displayed readings and the predicted curve, sometimes it goes nuts
> and exceeds the value by a 5% or so.
>
> It never happens on a clear day.  It often happens when clouds are
> passing over.  It never happens when truly cloudy.
>
> I have received the same advice and conclude it is NOT any gremlin nor a
> reflection (which I thought of as an initial possibility) but due to the
> cloud edge effect.
>
> Now I just take it as part of the function, and on perfectly sunny
> cloudless days enjoy the sensor output tracking predicted values.
>
> Dale
>
>
> --
> 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/3a8388e7-7449-1a8a-4d58-468901f5e762%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/CACjxfUuf65UOR4_RsS_tx3sSJRCX0BuEa7pWfxCk_ENo6XuoGg%40mail.gmail.com.


Re: [weewx-user] StdCalibrate/corrections for radiation reading

2023-08-12 Thread Colin Larsen
Hi Greg

Many thanks for your reply, you raise some very valid points about data in
the real world. Maybe I'll just leave it as it is :)

Cheers
Colin

On Sun, 13 Aug 2023 at 11:16, Greg Troxel  wrote:

> "colin@gmail.com"  writes:
>
> > Hi all
> > I have a situation whereby (I think) I have some odd building
> reflections
> > spiking my solar radiation sensor. This results in occasional readings
> way
> > above the expected maxSolarRad value.
> > I'm going to try and sort out exactly what's happening but in the
> meantime
> > I wondered if it would be possible to use StdCalibrate to correct those
> > errant readings?
> > Putting it simplistically what I'm aiming for is a statement along the
> > lines of;
> >
> > radiation = maxSolarRad if radiation > maxSolarRad
> >
> > I'm not sure if that syntax is correct above or will even work,  but
> this
> > will hopefully remove any spikes greater than the expected maxSolarRad?
> >
> > Am I barking up completely the wrong tree?
>
> Yes.  You have data and you should record it.
>
> There are three situations, at least, where you will measure a radiation
> that is higher than maxSolarRad.
>
>   - small amounts, because the formula is approximate
>
>   - reflections from mirror-ish surfaces resulting in direct plus extra
>
>   - lensing from cloud edges, where you see = in clear sky, lower in
> cloud, and a messy pattern as the edge happens
>
> In these cases, you really can get measurements that are valid and above
> maxSolarRad.
>
> The question is: what are you trying to do and what do you think it
> means?
>
> If you are trying to find some value that represents the highest value
> you saw more than momementarily, compute the 98th percentile of
> radiation, or 95th or 99th.  Then the data means what it says.
>
> As soon as you extract data with a conditional on theory, you have
> something that is very hard to reason about and describe.  My advice is
> don't go there.
>
> This is different from rejecting values of 120% humidity reveived from a
> sensor as obviously bit errors.  Seeing too-high radiation happens
> without corruption.
>
>
> I just record it, and graph it, and I don't worry that it's sometimes
> higher than theory.  Real data is like that.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUsz36A026ft9YyH25SKNOuRYL4NCCUJPdkyMqHoQMB5pw%40mail.gmail.com.


Re: [weewx-user] Connecting to new Davis Console model 6313

2023-08-08 Thread Colin Larsen
Strangely enough I just replaced all my DIY hardware (weatherduino) with an
Ecowitt setup and it's excellent for the money

Colin

On Wed, 9 Aug 2023 at 14:35, vince  wrote:

> rtl_davis driver can help somewhat at a higher complexity level FWIW
>
> --
> 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/72f7c54d-ed55-4631-8eeb-0339cbf93588n%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/CACjxfUvy3bmgNZ9uJVkhx_LJwFGPX4DPmgQrf7XSzPO90S2jfQ%40mail.gmail.com.


Re: [weewx-user] Re: "maxSolarRad" - what is it exactly, and how is it translated?

2023-07-23 Thread Colin Larsen
Karen

Is there a detailed explanation of those adjustments anywhere? I graph the
maxsolarrad "under" my actual at 41south.nz (currently under reconstruction)

Thanks
Colin

On Mon, 24 Jul 2023, 05:56 Karen K,  wrote:

> Please remember that there are parameters in weewx.conf to adjust the
> calculation of maxSolarRad:
>
> [StdWXCalculate]
> ...
> [[WXXTypes]]
> ...
> [[[maxSolarRad]]]
> algorithm = rs
> atc = 0.8
> nfac = 2
>
> michael.k...@gmx.at schrieb am Sonntag, 23. Juli 2023 um 18:15:04 UTC+2:
>
>> Sounds sane, I'll use that for "my" skin, for the English language. For
>> German, it still sounds a little "bumpy", as we would call it, where I am
>> from. :D
>>
>> Greg Troxel schrieb am Sonntag, 23. Juli 2023 um 13:22:24 UTC+2:
>>
>>> I agree that "theoretical clear-sky radiation" (with English pedant
>>> hyphenation, required when an adjective modifies a second one instead of
>>> the noun, although that is getting lost over time) is the proper term.
>>>
>>> In addition to the reflections and cloud edge lensing (both of which
>>> I've seen), there are the issues that the theory is an approximation and
>>> the measurements have errors. Even still, I sometimes see measured over
>>> theory, but it's close and it's the same shape.
>>>
>> --
> 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/08bb2b5a-47f3-4337-9ff1-875c6f8568e2n%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/CACjxfUuEziHPs%3DKZtp4RgRqCzQvY8bWzvjikbqt_vH25wOyZLQ%40mail.gmail.com.


[weewx-user] Announcement: AerisWeather Acquired by Vaisala

2022-01-27 Thread Colin Larsen
For all those using Aeris Weather


We are writing the next chapter of our company history – together with
Vaisala β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
We are writing the next chapter of our company history – together with
Vaisala.
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ
β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ β€Œ


Announcement: AerisWeather acquired by Vaisala

January 27th, 2022

To our valued clients, partners & associates:

We’re excited to share the news with you that AerisWeather has been
acquired by Vaisala, in a transaction that was settled earlier today.
Vaisala, a global leader in weather, environmental & industrial
measurements will integrate AerisWeather into their surging data solutions
business - elevating its market position as a leading global provider of
environmental data & imagery solutions.

You can read more about the acquisition in Vaisala’s official stock
exchange release which can be found here
.

In Vaisala we have found a partner with a matching vision and high standard
for success. While the entire AerisWeather team is proud of our
accomplishments to date, we’re already looking ahead to accelerating our
shared product roadmap to create the industry’s most compelling
data-as-a-service solutions, including:

   - Proprietary global weather models, including Europe’s most accurate
   weather forecasts
   - Road & runway surface conditions
   - Renewable energy historical data and forecasts
   - Port, coastal and offshore maritime weather observations
   - Proprietary global lightning network

Additionally, our customers will now have access to world-class
environmental monitoring solutions.  From weather stations and lightning
detection to air quality monitoring and wind lidar, we will have site-level
solutions that are designed to perform in the most severe environments,
protecting life and property.

Finally, we’d like to thank our clients and partners who have supported us
over the last five and a half years, both for their loyalty as well as
their invaluable feedback on our technology platform. We can assure our
clients that API & Mapping services will continue to function normally and
there will be no disruption to our existing services.  If you have any
questions, please reach out to your Account Executive directly or, visit
www.aerisweather.com/vaisala-aerisweather-faqs
 to review our FAQ’s
regarding today’s news.

We look forward to working with you all as we strive to accurately &
seamlessly measure, monitor and deliver environmental conditions across our
every-changing planet.

Thanks!
The AerisWeather Team




AerisWeather, a Vaisala Company

6569 City West Parkway
Eden Prairie, MN 55344



Unsubscribe 

-- 
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/CACjxfUv4TUM%2BqGYF6jVSuWCdhn22_tmj4q97bCVq5siwx%3D8EoQ%40mail.gmail.com.


Re: [weewx-user] Re: Getting LoRa data from server into weewx

2021-11-30 Thread Colin Larsen
Good work Bob, well done getting it sorted :)

Cheers
Colin

On Wed, 1 Dec 2021 at 09:21, bgra...@umw.edu  wrote:

> I'm very happy to say that I have three successful (hourly) readings of
> CO2 in the weewx db, thanks to everyone who has been patient and helpful
> with an 81-year-old retired librarian attempting to do something that was
> beyond his reach.
> [I just heard a cumulative sigh of relief circle
> the globe]
> In the end, my main problem was adjusting the elements in weewx.conf with
> a combination of some of the last suggestions. I found that the sensor,
> once every 24 hours, sends out a different string of data with battery
> information which doesn't include any CO2 data. My next step is setting
> up a display of the data with a graph on my main page.
>
> Many thanks again to everyone who helped solve my problem. I now have
> another window into the ills that plague our planet
>
> Cheers,
> Bob
> http://grattans.org/wx
>
> On Tuesday, November 30, 2021 at 12:15:33 AM UTC-5 vince wrote:
>
>> I'd go with something like..
>>
>> [[topics]]
>> [[[mytopic]]]
>>CO2_Value_PPM
>>name = co2
>>contains total = false
>>conversion type = float
>>measurementID
>>ignore = true
>>report_telemetry
>>ignore = true
>>
>> Define the topic to subscribe to.
>> Do not ignore the one element therein that you want.
>> Ignore the elements you don't want.
>>
>> On Monday, November 29, 2021 at 6:20:28 PM UTC-8 storm...@gmail.com
>> wrote:
>>
>>>  *"Is it possible to have weewx ignore these elements and only process
>>> the  "CO2_Value_PPM": 419 ?"  *Yes, Rich provided the possible solution.
>>>
>>> * "I'm not sure what "float" does but mayve that's a problem...?"  *A
>>> float is a real number.  It is trying to convert  'report_telemetry' which
>>> is a string to a real number causing the failure.
>>>
>>> On Monday, November 29, 2021 at 9:05:54 PM UTC-5 bell...@gmail.com
>>> wrote:
>>>
 Bob,
 You are correct. The extra data is causing the problem. Due to a poor
 early design decision, MQTTSubscribe defaults to converting everything to
 float. Obviously, 'report_telemetry' cannot be converted to float. The
 following configuration should work. It ignores all but 'CO2_Value_PPM'.
 [[topics]]
 [[[mytopic]]]
 ignore = true
 CO2_Value_PPM
 name = co2
 ignore = false
 If that doesn't work, let me know and I can give a different
 configuration.
 rich

 On Monday, 29 November 2021 at 19:53:46 UTC-5 bgra...@umw.edu wrote:

> Last post of the day, I promise!
> I think the node-red flow is working the way it should and reporting
> the parsed message as in my last post.
>
> weewx.conf configuration (changed topic to "mytopic" in the flow and
> in weewx).
>
> [MQTTSubscribeService]
> # This section is for the MQTTSubscribe service.
> enable = true# false
>
> # The MQTT server.
> # Default is localhost.
> host = localhost
> port = 1883
> keepalive = 60
>
> username = None #admin#None
>password = None  #admin#None
>   binding = loop
>
>[[message_callback]]
> type = json#REPLACE_ME
>
> #  mytopic  is the topic to subscribe to.
> [[topics]]
>
> unit_system = US
>
> [[[mytopic]]]
>
> #data  sent from RAK7244
> #ignore = true
> CO2_Value_PPM
> #weewx db field name
> name = co2
> ignore = false
> contains total = false
> conversion type = float
> #units = ppm
> #[[[SECOND/REPLACE_ME]]]
>
> *This is the weewx.log debug info:*
>
> Nov 29 19:20:58 n4mrv weewx[17143] DEBUG user.MQTTSubscribe: (Service)
> MessageCallbackProvider data-> incoming topic: mytopic, QOS: 0, retain: 0,
> payload: b'{\n"CO2_Value_PPM": 419,\n"measurementId": 4100,\n
>  "type": "report_telemetry"\n}'
> Nov 29 19:20:58 n4mrv weewx[17143] ERROR user.MQTTSubscribe: (Service)
> MessageCallbackProvider on_message_json failed with  'user.MQTTSubscribe.ConversionError'> and reason Failed converting field
> type with value report_telemetry using 'lambda x: to_float(x)' with reason
> could not convert string to float: 'report_telemetry'..
> Nov 29 19:20:58 n4mrv weewx[17143] ERROR user.MQTTSubscribe: (Service)
>  MessageCallbackProvider Ignoring topic=mytopic and payload=b'{\n
>  "CO2_Value_PPM": 419,\n"measurementId": 4100,\n"type":
> "report_telemetry"\n}'
> Nov 29 19:20:58 n4mrv weewx[17143] ERROR user.MQTTSubscr

Re: [weewx-user] WeeWX-MQTTSubscribe - use of - sanity check

2021-04-08 Thread Colin Larsen
Thanks Rich

Yes both sets of data are on the same mqtt server. I agree with the single
point of failure issue, but I think I have that anyway. I may look at some
sort of parallel data logging maybe?

Graham - nice work :)

Cheers
Colin

On Fri, 9 Apr 2021 at 13:10, Graham Eddy  wrote:

> i am nearly finished doing something similar, except
>   (1) i position weewx as the manager of the wx hardware via
> station-specific interface - weewx is the app that encapsulates the wx and
> provides its data as mqtt to the world (unless the wx is natively mqtt).
> e.g. the vantage driver is solid.
>   (2) i also position weewx as manager of an abstract weather station that
> receives its observations from many sources - and i have chosen mqtt as the
> common messaging medium i.e. lots of little IoT devices provide data to
> weewx via mqtt. this is a different role from (1), and i know some weewx
> users stream to data consolidaters that can provide this abstraction
> instead.
>   (3) i wrote my own bi-directional mqtt gateway, for use in all my mqtt
> apps (the paho client leaves a lot ’to the reader’ to implement in a
> production environment so needs a whole software layer above it). most of
> my former data services have been migrated to separate apps that talk to
> weewx via mqtt. (some of my weewx data services manipulate data within
> weewx so are not externalised.) i have a weewx data service built on the
> bi-directional gateway as the interface between weewx and mqtt world.
>
> i expect there is a lot of overlap with the excellent MQTTSubscribe. but
> my requirement was for a generic gateway outside of weewx, and the weewx
> interface is just one of the apps built on it
>
> On 9 Apr 2021, at 5:47 am, Colin Larsen  wrote:
>
> I'm thinking about rewriting my current weather station code to solely use
> MQTT to deliver data to WeeWX
>
>
> --
> 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/8BAB1C3E-DE3C-4D57-84FA-6B6AFBD0326C%40gmail.com
> <https://groups.google.com/d/msgid/weewx-user/8BAB1C3E-DE3C-4D57-84FA-6B6AFBD0326C%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUtuS7G_ijuvn1KWPHLfmCm9q7WSENL1830SZ6oOLbpydg%40mail.gmail.com.


[weewx-user] WeeWX-MQTTSubscribe - use of - sanity check

2021-04-08 Thread Colin Larsen
Learned WeeWX folk

I'm thinking about rewriting my current weather station code to solely use
MQTT to deliver data to WeeWX. At present the station runs on WeatherDuino
which transmits data (via wifi) to a console which then emulates the Davis
protocol via usb to a Pi running WeeWX.

I really don't use the console for anything more than connecting to the Pi,
so my thought is to bypass it, send all the data from the TX unit to my
MQTT server (already up and taking AQI/AQM data from sensors via wifi) and
then use WeeWX-MQTTSubscribe in driver mode to supply loop packets to WeeWX.

Oh and before anyone using WeatherDuino jumps in, I have just completely
redesigned the TX units to use the ESP8266 (WemosD1 mini) rather than the
old Arduino board and 433 Mhz splatter TX :)

Are there any holes in my plan??

Many thanks for your thoughts

Colin
ZL2FL

-- 
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/CACjxfUvHVLVHTOn%2B-Nqn%3D2xOE_U4VUA%2BRPywkNkWrxpm8MXRiw%40mail.gmail.com.


Re: [weewx-user] It never rains, but apparently it pours .....

2021-03-30 Thread Colin Larsen
Thanks Gary, much appreciated. I just found the wiki
https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data and used
that to delete the data, yes it was today. Will rebuild the daily summaries
now.

I used 'null' so there is just nothing in those parts of the table (rather
than 0.0 in the rest) - does that matter?

Colin


On Wed, 31 Mar 2021 at 19:20, gjr80  wrote:

> If you know it definitely didn't rain in the archive periods concerned
> then use 0.0, if it did rain but you don't know how much then you could use
> None to indicate no rainfall data for those periods. Or you could just use
> 0.0 for the lot, not really going to make too much difference at the end of
> the day. None values may show a gap in your day rain plot, zeros will not.
>
> Also, don't forget to rebuild your daily summaries for the day concerned
> once you have fixed the data. Assuming it is today there will be no need to
> rebuild any NOAA reports, if it was an earlier month/year you would need to
> delete from that month/year onwards to force regeneration.
>
> Gary
>
> On Wednesday, 31 March 2021 at 15:25:09 UTC+10 colin@gmail.com wrote:
>
>> OK, so used epoch time to find the records I want to delete (with rain
>> and rainRate), now do I just delete them or do they need to be replaced by
>> null (or 0.0?). I may need a hand with the correct syntax for that please
>>
>> *pi@wduino*:*~ $* echo "SELECT rainRate FROM archive WHERE (dateTime >
>> 1617159600);" | sudo sqlite3 /var/lib/weewx/weewx.sdb
>>
>> 0.0419816511200587
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 279.980998292116
>>
>> 247.545269518011
>>
>> 19.3118544276522
>>
>> 13.7807155122679
>>
>> 5.58392519958292
>>
>> 0.957907401564173
>>
>> 4.75823850308484
>>
>> 5.67484207064662
>>
>> 0.84798164620346
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> *pi@wduino*:*~ $*
>>
>> On Wed, 31 Mar 2021 at 18:05, Colin Larsen  wrote:
>>
>>> I'm thinking that the easiest road here is to delete (or null??) all of
>>> todays rain data. So that would be 'rain' and 'rainRate'?
>>>
>>> Thanks
>>> Colin
>>>
>>> On Wed, 31 Mar 2021 at 17:44, colin@gmail.com 
>>> wrote:
>>>
>>>> It's not my week lol!
>>>>
>>>> Now that I've rebuilt Weewx my weather station decided to go rogue and
>>>> tell me it rained about 500mm in the last hour. I've stopped it thinking
>>>> it's raining but now how do I get rid of the rogue data from the database
>>>> in Weewx? I did a search for all kinds of database issues here but my
>>>> search fu is failing me.
>>>>
>>>> Cheers for any help (and yes I have no doubt it's easy!)
>>>>
>>>> Colin
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to weewx-user+...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/ce3e4ec1-e936-487e-8df8-ebd96d376619n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/ce3e4ec1-e936-487e-8df8-ebd96d376619n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
> 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/18b79bfa-91e7-47dd-ba1d-2d894401fb1en%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/18b79bfa-91e7-47dd-ba1d-2d894401fb1en%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUvtnwn29fM-zt545RBtoKGrDUKoubehWF-A5xGw4yZZnw%40mail.gmail.com.


Re: [weewx-user] It never rains, but apparently it pours .....

2021-03-30 Thread Colin Larsen
OK, so used epoch time to find the records I want to delete (with rain and
rainRate), now do I just delete them or do they need to be replaced by null
(or 0.0?). I may need a hand with the correct syntax for that please

*pi@wduino*:*~ $* echo "SELECT rainRate FROM archive WHERE (dateTime >
1617159600);" | sudo sqlite3 /var/lib/weewx/weewx.sdb

0.0419816511200587

0.0

0.0

0.0

0.0

0.0

0.0

0.0

279.980998292116

247.545269518011

19.3118544276522

13.7807155122679

5.58392519958292

0.957907401564173

4.75823850308484

5.67484207064662

0.84798164620346

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

*pi@wduino*:*~ $*

On Wed, 31 Mar 2021 at 18:05, Colin Larsen  wrote:

> I'm thinking that the easiest road here is to delete (or null??) all of
> todays rain data. So that would be 'rain' and 'rainRate'?
>
> Thanks
> Colin
>
> On Wed, 31 Mar 2021 at 17:44, colin@gmail.com 
> wrote:
>
>> It's not my week lol!
>>
>> Now that I've rebuilt Weewx my weather station decided to go rogue and
>> tell me it rained about 500mm in the last hour. I've stopped it thinking
>> it's raining but now how do I get rid of the rogue data from the database
>> in Weewx? I did a search for all kinds of database issues here but my
>> search fu is failing me.
>>
>> Cheers for any help (and yes I have no doubt it's easy!)
>>
>> Colin
>>
>> --
>> 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/ce3e4ec1-e936-487e-8df8-ebd96d376619n%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/ce3e4ec1-e936-487e-8df8-ebd96d376619n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/CACjxfUt%2BC2f%3D8796Ayg43%3D%2Bh7aKOKLwENfjUMruWpjocgeto4Q%40mail.gmail.com.


Re: [weewx-user] It never rains, but apparently it pours .....

2021-03-30 Thread Colin Larsen
I'm thinking that the easiest road here is to delete (or null??) all of
todays rain data. So that would be 'rain' and 'rainRate'?

Thanks
Colin

On Wed, 31 Mar 2021 at 17:44, colin@gmail.com 
wrote:

> It's not my week lol!
>
> Now that I've rebuilt Weewx my weather station decided to go rogue and
> tell me it rained about 500mm in the last hour. I've stopped it thinking
> it's raining but now how do I get rid of the rogue data from the database
> in Weewx? I did a search for all kinds of database issues here but my
> search fu is failing me.
>
> Cheers for any help (and yes I have no doubt it's easy!)
>
> Colin
>
> --
> 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/ce3e4ec1-e936-487e-8df8-ebd96d376619n%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/CACjxfUvn%2B5Mxv%3D%3DR4LDA6sx_Q6QzA%2BejNCR7B-8C8NgSpLKtrg%40mail.gmail.com.


Re: [weewx-user] Problem with upgrade

2021-03-30 Thread Colin Larsen
Hi Vince

Well when I started the process I didn't actually think that the sdcard was
bad, I just needed more space to do the OS and Weewx upgrade. And then
.. your second suggestion is exactly what ended up happening :)

But certainly a valuable lesson in the vital things to have backed up other
than what's covered in the general documentation

Cheers
Colin

On Wed, 31 Mar 2021 at 16:04, vince  wrote:

> For the future, never 'copy' a possibly bad SD to a new SD card.  All
> you're doing then is switching which physical media the bad bits are on.
>
> Reimage the os onto the new card with Balena Etcher or similar imaging
> software, put it in the pi,  and reinstall any added software like weewx
> onto it.  Then restore your database.'That' is a clean reinstallation.
>
> --
> 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/22233ebc-bc8b-4732-83a7-ec39cb510be5n%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/CACjxfUsW%3DRKFybi99tus1z%2BWNK9hLeDd4SSeMcaoTXtw5j0FDg%40mail.gmail.com.


Re: [weewx-user] Problem with upgrade

2021-03-30 Thread Colin Larsen
Well this turned into a bit of a nightmare. After purchasing a bigger sd
card and copying the complete original card over i couldn't get the Pi to
boot. No problems I thought, I'll just go back to the original again
but no, that doesn't want to boot either!

So .complete rebuild of the system later (thank goodness I backed up
99% of the files I needed - and now I know a few more I need to backup as
well!)

I did manage to mount the original sd card on my Mac and recover some of
the other files that I needed as well, so all was not lost.

The upshot is I'm now on Weewx 4.4.0 with a nice big sd card. It was a nice
exercise but not one to repeat too often :)

Thanks
Colin

On Tue, 30 Mar 2021 at 15:03, Colin Larsen  wrote:

> OK, we're gonna need a bigger SD card! Lol, ran out of space on the 8 gig
> card, might as well just do a rebuild and then restore by backed up files :)
>
> Colin
>
> On Tue, 30 Mar 2021 at 13:24, Colin Larsen  wrote:
>
>> Thanks John, underway now, will post results when it finishes
>>
>> On Tue, 30 Mar 2021 at 13:11, John Kline  wrote:
>>
>>> Please run:
>>> sudo apt update
>>> sudo apt full-upgrade
>>>
>>> Then try your install.
>>>
>>> On Mar 29, 2021, at 4:52 PM, colin@gmail.com 
>>> wrote:
>>>
>>> ο»ΏHi Team
>>>
>>> I'm attempting to upgrade from 4.0.0 to the latest version via Deb. Did
>>> a sudo apt-get update, then sudo apt-get install weewx as per the guide and
>>> came up with this error ..
>>>
>>> The following packages have unmet dependencies:
>>>
>>>  weewx : Depends: python3-cheetah but it is not installable
>>>
>>> E: Unable to correct problems, you have held broken packages.
>>>
>>> Tried to install it using sudo apt install python3-cheetah which failed
>>>
>>> Tried using Pip3 which said
>>>
>>> Requirement already satisfied: Cheetah3 in
>>> /usr/local/lib/python3.5/dist-packages
>>>
>>>
>>> Not quite sure where to go from here, any help appreciated.
>>>
>>>
>>> Cheers
>>>
>>> Colin
>>>
>>> --
>>> 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/8fae1af2-d0a6-40dc-bb75-3944e3af513an%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/8fae1af2-d0a6-40dc-bb75-3944e3af513an%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> --
>>> 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/27EFCF67-B4F1-419B-B55C-78D7BDE8FDBC%40johnkline.com
>>> <https://groups.google.com/d/msgid/weewx-user/27EFCF67-B4F1-419B-B55C-78D7BDE8FDBC%40johnkline.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/CACjxfUsc4p_6tsHCDjAyZcxP78Kcb_aeW30q%3DjLz7MttovxEhw%40mail.gmail.com.


Re: [weewx-user] Problem with upgrade

2021-03-29 Thread Colin Larsen
OK, we're gonna need a bigger SD card! Lol, ran out of space on the 8 gig
card, might as well just do a rebuild and then restore by backed up files :)

Colin

On Tue, 30 Mar 2021 at 13:24, Colin Larsen  wrote:

> Thanks John, underway now, will post results when it finishes
>
> On Tue, 30 Mar 2021 at 13:11, John Kline  wrote:
>
>> Please run:
>> sudo apt update
>> sudo apt full-upgrade
>>
>> Then try your install.
>>
>> On Mar 29, 2021, at 4:52 PM, colin@gmail.com 
>> wrote:
>>
>> ο»ΏHi Team
>>
>> I'm attempting to upgrade from 4.0.0 to the latest version via Deb. Did a
>> sudo apt-get update, then sudo apt-get install weewx as per the guide and
>> came up with this error ..
>>
>> The following packages have unmet dependencies:
>>
>>  weewx : Depends: python3-cheetah but it is not installable
>>
>> E: Unable to correct problems, you have held broken packages.
>>
>> Tried to install it using sudo apt install python3-cheetah which failed
>>
>> Tried using Pip3 which said
>>
>> Requirement already satisfied: Cheetah3 in
>> /usr/local/lib/python3.5/dist-packages
>>
>>
>> Not quite sure where to go from here, any help appreciated.
>>
>>
>> Cheers
>>
>> Colin
>>
>> --
>> 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/8fae1af2-d0a6-40dc-bb75-3944e3af513an%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/8fae1af2-d0a6-40dc-bb75-3944e3af513an%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> --
>> 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/27EFCF67-B4F1-419B-B55C-78D7BDE8FDBC%40johnkline.com
>> <https://groups.google.com/d/msgid/weewx-user/27EFCF67-B4F1-419B-B55C-78D7BDE8FDBC%40johnkline.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/CACjxfUtfQo-9t8Z5mGTiqRhWqb-ZvoqzWU0M%2B-_WKX%3DAcnDojg%40mail.gmail.com.


Re: [weewx-user] Problem with upgrade

2021-03-29 Thread Colin Larsen
Thanks John, underway now, will post results when it finishes

On Tue, 30 Mar 2021 at 13:11, John Kline  wrote:

> Please run:
> sudo apt update
> sudo apt full-upgrade
>
> Then try your install.
>
> On Mar 29, 2021, at 4:52 PM, colin@gmail.com 
> wrote:
>
> ο»ΏHi Team
>
> I'm attempting to upgrade from 4.0.0 to the latest version via Deb. Did a
> sudo apt-get update, then sudo apt-get install weewx as per the guide and
> came up with this error ..
>
> The following packages have unmet dependencies:
>
>  weewx : Depends: python3-cheetah but it is not installable
>
> E: Unable to correct problems, you have held broken packages.
>
> Tried to install it using sudo apt install python3-cheetah which failed
>
> Tried using Pip3 which said
>
> Requirement already satisfied: Cheetah3 in
> /usr/local/lib/python3.5/dist-packages
>
>
> Not quite sure where to go from here, any help appreciated.
>
>
> Cheers
>
> Colin
>
> --
> 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/8fae1af2-d0a6-40dc-bb75-3944e3af513an%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/27EFCF67-B4F1-419B-B55C-78D7BDE8FDBC%40johnkline.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUuTCi%2B9DpfZioSU1-AL2%2BMMkHWks7sPa7eORO0JkJt4wA%40mail.gmail.com.


Re: [weewx-user] How to change weewx service from python2 to python3 on Debian

2021-01-26 Thread Colin Larsen
I remember I had to change /etc/default/weewx it to tell Weewx to start
with Python3

WEEWX_PYTHON=python2<== change to python3

WEEWX_BINDIR=/usr/share/weewx

WEEWX_BIN=/usr/bin/weewxd

WEEWX_CFG=/etc/weewx/weewx.conf

Colin

On Wed, 27 Jan 2021 at 11:04, Tom Keffer  wrote:

> Easiest is to just follow the install directions in the Debian guide
> :
>
>
>
>
> *wget -qO - https://weewx.com/apt/weewx-python3.list
>  | sudo tee
> /etc/apt/sources.list.d/weewx.listsudo apt-get updatesudo apt-get install
> weewx*
>
>
> On Tue, Jan 26, 2021 at 1:58 PM Gordon Dickens 
> wrote:
>
>> How do I make weewx use python3 instead of python2?  I initially
>> installed weewx on Debian using the Debian package over a year ago and it
>> was originally setup to use python2. I recently upgraded to weewx 4.3.0
>> with the Belchertown skin version 1.2 and so I want to also upgrade to
>> python3.   The normal way to change default packages in Debian is with the
>> update-alternatives command, however, when I set python3 as the default,
>> weewx continues to use python2 as seen from the command, "ps aux | grep
>> weewx" whose output contains:
>>
>> python2 /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid
>> /etc/weewx/weewx.conf
>>
>> So, the service is started with python2.  How do I change the weewx
>> service to use python3?
>>
>> Thanks,
>>
>> Gordon
>>
>> --
>> 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/807bfd14-5724-4116-b369-c7d2d49f15b9n%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/CAPq0zEA76i1OPAqpLZqC4AYf%2BxLY%3DTiu2FB%3DgD51Fc635PpHuQ%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/CACjxfUv6LcGyjQWjPKfD6hPfyLJj8NuHeBBfxMx2_nPdrauw_A%40mail.gmail.com.


Re: [weewx-user] Re: skin Belchertown " earth Quake"

2021-01-10 Thread Colin Larsen
I just looked at your site and the distance is in miles as I would expect
for the US. What part do you think is buggy?

Colin

On Mon, 11 Jan 2021 at 03:48, John Mora  wrote:

> I am following these threads with interest as my Belchertown "Earthquake"
> is working but not as I desire it to work. The skin installed without a
> hitch and is running but the Eathquake  distance is in km instead of miles
> and I also tried to change the earthquake_maxradiuskm setting from 1000 to
> 2000 and the changes aren't being reflected in the output.
>
> I've tried making changes to belchertown.py (
> https://github.com/poblabs/weewx-belchertown/issues/422) and changing the
> skin.conf by setting the belchertown_locale from auto to en_US.UTF-8 and
> doing the locale-gen command to no avail.
>
> I will continue to follow this thread hoping that there is some final
> solution as to why the Earthquake is "buggy". Thanks to all who post, you
> have been a great help in trying to figure this anomaly out.
>
> my site: http://weather.codetales.com
>
>
>
>
> On Saturday, January 9, 2021 at 7:34:41 PM UTC-5 Greg from Oz wrote:
>
>> Yes I did that to but it made no difference.
>>
>> You can change the locale = (in the belchertown skin.conf) to "*en_AU.UTF-8"
>> *and that works  but if you leave it as auto and do the regen then it
>> works as expected.
>>
>>
>> On Sunday, 10 January 2021 at 10:12:38 UTC+11 colin@gmail.com wrote:
>>
>>> My simple fix for this was to make sure that in weewx.conf (or skin.conf
>>> if you prefer) you have under the stanza
>>>
>>> [[belchertown]]
>>> [[[units]]]
>>> groups
>>>
>>> An entry that says
>>>
>>> group_distance = km
>>>
>>>
>>>
>>> On Sun, 10 Jan 2021 at 11:12, Greg from Oz  wrote:
>>>
 Run the command: locale

 See if *LC_MEASUREMENT *is in your units

 If it is like this: *LC_MEASUREMENT="en_US.UTF-8" *the the measurement
 units will be in US (miles)

 To regenerate all your locale settings run: *locale-gen*

 There is a lot of discussion here:
 https://groups.google.com/g/weewx-user/c/BckKUHu2_DQ/m/30YJPrKkBwAJ


 On Sunday, 10 January 2021 at 06:48:26 UTC+11 sali...@gmail.com wrote:

> hello,
> in which file, can I modify miles in kilometers.
>
> inside joint file
>
> thanks
>
> 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+...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/06af1676-3a27-4989-945d-af379f5b1647n%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/544e2f70-aecc-4199-87bd-f8cd0940d371n%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/CACjxfUt9vbjdz4AYF-hNQ2BSHGGcK22BfrGX0uTLuHxkZ43Q8A%40mail.gmail.com.


Re: [weewx-user] Re: skin Belchertown " earth Quake"

2021-01-09 Thread Colin Larsen
My simple fix for this was to make sure that in weewx.conf (or skin.conf if
you prefer) you have under the stanza

[[belchertown]]
[[[units]]]
groups

An entry that says

group_distance = km



On Sun, 10 Jan 2021 at 11:12, Greg from Oz  wrote:

> Run the command: locale
>
> See if *LC_MEASUREMENT *is in your units
>
> If it is like this: *LC_MEASUREMENT="en_US.UTF-8" *the the measurement
> units will be in US (miles)
>
> To regenerate all your locale settings run: *locale-gen*
>
> There is a lot of discussion here:
> https://groups.google.com/g/weewx-user/c/BckKUHu2_DQ/m/30YJPrKkBwAJ
>
>
> On Sunday, 10 January 2021 at 06:48:26 UTC+11 sali...@gmail.com wrote:
>
>> hello,
>> in which file, can I modify miles in kilometers.
>>
>> inside joint file
>>
>> thanks
>>
>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/06af1676-3a27-4989-945d-af379f5b1647n%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/CACjxfUvTFGcrSPDcw8-WLjdVH7qox%3D7ibaO_zvjVHM_-WmbKww%40mail.gmail.com.


Re: [weewx-user] Belchertown - suppressing graph=homepage >

2021-01-07 Thread Colin Larsen
Nice detective work, well done sorting it!

On Fri, 8 Jan 2021, 11:40 David Levine,  wrote:

> I wanted to close this out as I identified the cause of my trials and
> tribulations but you have to read a bit to get to it. As a recap, I wanted
> to remove Homepage and have Day, Yesterday, Week and Month graphs displayed
> like at https://belchertownweather.com/graphs/
>
> The default w/o graphs.conf or with graphs.conf.example copied to
> graphs.conf results in Homepage, Day, Week, Month & Year.  Homepage and Day
> are the same graphs with the default config. As I read in
> https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation
> , [day], [week], [month] & [year] must be present. Ok, that's fine so I
> should be able to delete [homepage] and add [yesterday] - piece of cake.
> Well that didn't work with an error being thrown to syslog and no graph on
> the front page.
>
> Next I read in the same charts documentation page to use the following in
> the weewx.conf file to override which graph set is displayed on the home
> page: highcharts_frontpage_graphgroup = week.  Well, that just didn't work
> for me. After many dozens of weewx.conf adjustments w/ stop & start and
> with many, many, many Belchertown/graphs.conf adjustments, I couldn't
> figure out what wasn't right. Today I looked at the source code and found
> what was tripping me up... the override parameter name should be
> highcharts_homepage_graphgroup and not _frontpage_ as the documentation
> has. Once I made the adjustment with highcharts_homepage_graphgroup = day
> in weewx.conf, I was able to successfully remove [homepage] from
> graph.conf.
>
> This is the second time I got tripped up by the documentation using a
> different/outdated override name. I'll do another source code pull request
> to adjust the documentation to match the current source. Anyway, on to the
> next adventure.
>
> David
>
> On Wednesday, January 6, 2021 at 8:41:12 AM UTC-5 David Levine wrote:
>
>> Using https://belchertownweather.com/graphs/ as a reference, none of the
>> links are to graph=homepage, There are links to graph=all, graph=day,
>> graph=week, ... No graph=homepage.  If I remove the [homepage] section in
>> graphs.conf,  an error is generated to syslog and when I go to .../graphs/
>> I get no graphs displayed on that landing page.
>>
>> Not to complicate things further but if leave [homepage] and change the
>> button to say Today, I get an acceptable approach, but then I'd like to
>> remove the [day] section as it seems to be a duplicate. If I remove [day] I
>> also seem to get no graphs generated on the .../graphs/ page.
>>
>> If it helps, this is where the generated pages are getting FTP'ed to from
>> my local Raspberry pi - http://www.levinecentral.com/weather/graphs/
>>
>> If I comment out [day] in graphs.conf,
>> http://www.levinecentral.com/weather/graphs/ won't show any graphs
>> between the buttons and footer.
>>
>> David
>>
>> On Tuesday, January 5, 2021 at 11:12:54 PM UTC-5 colin@gmail.com
>> wrote:
>>
>>> Why do you wish to remove it, what are you trying to achieve? I'm a
>>> little confused sorry
>>>
>>> Colin
>>>
>>> On Wed, 6 Jan 2021 at 16:25, David  wrote:
>>>
 Thanks but that does not seem to be the situation I’m encountering.

 I can’t seem to remove/rename [homepage] in graphs.conf



 On Tue, Jan 5, 2021 at 10:07 PM Timothy L 
 wrote:

> Is this thread what you are asking?
> https://groups.google.com/g/weewx-user/c/qUt0XdqREqk/m/gGh5Of8cAgAJ
>
>
> On January 5, 2021, at 7:34 PM, David Levine  wrote:
>
>
> When I look at https://belchertownweather.com/graphs/ there is no
> ?graph=homepage present.  When I comment out, rename or remove the
> [homepage] section in graphs.conf, an error is generated to syslog and
> there's nothing displayed on my site at /graphs/ .
>
> I can add other sections such as [yesterday] but I've not found the
> magic to remove.rename homepage.
>
> What am I missing? Running the new 4.3 version of weewx and latest
> Belchertown skin.
>
> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
> Generate failed with exception ''
>
> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>  Ignoring template /etc/weewx/skins/Belchertown/index.html.tmpl
>
> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>  Reason: 'homepage'
>
> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>   Traceback (most recent call last):
>
> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in
> generate
>
> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>   unicode_string = compiled_template.respond()
>
> Jan  5 22:55:41 

Re: [weewx-user] Belchertown - suppressing graph=homepage >

2021-01-05 Thread Colin Larsen
Why do you wish to remove it, what are you trying to achieve? I'm a little
confused sorry

Colin

On Wed, 6 Jan 2021 at 16:25, David  wrote:

> Thanks but that does not seem to be the situation I’m encountering.
>
> I can’t seem to remove/rename [homepage] in graphs.conf
>
>
>
> On Tue, Jan 5, 2021 at 10:07 PM Timothy L 
> wrote:
>
>> Is this thread what you are asking?
>> https://groups.google.com/g/weewx-user/c/qUt0XdqREqk/m/gGh5Of8cAgAJ
>>
>>
>> On January 5, 2021, at 7:34 PM, David Levine  wrote:
>>
>>
>> When I look at https://belchertownweather.com/graphs/ there is no
>> ?graph=homepage present.  When I comment out, rename or remove the
>> [homepage] section in graphs.conf, an error is generated to syslog and
>> there's nothing displayed on my site at /graphs/ .
>>
>> I can add other sections such as [yesterday] but I've not found the magic
>> to remove.rename homepage.
>>
>> What am I missing? Running the new 4.3 version of weewx and latest
>> Belchertown skin.
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>> Generate failed with exception ''
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>>  Ignoring template /etc/weewx/skins/Belchertown/index.html.tmpl
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>>  Reason: 'homepage'
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>>   Traceback (most recent call last):
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in
>> generate
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>>   unicode_string = compiled_template.respond()
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>> File "_etc_weewx_skins_Belchertown_index_html_tmpl.py", line 1508,
>> in respond
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>> File "_etc_weewx_skins_Belchertown_index_html_tmpl.py", line 631,
>> in __errorCatcher81
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>> File "", line 1, in 
>>
>> Jan  5 22:55:41 raspberrypi weewx[17253] ERROR weewx.cheetahgenerator:
>>   KeyError: 'homepage'
>>
>> David
>>
>> --
>> 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/b08a5bed-c75b-4148-a586-9e8ed16f0c05n%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/Zmli8blPTIM/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/c4dgvo32pceu9rro6rkqv5s9.1609902439052%40email.android.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/CAGu77J8UuuJocDp%2ByOapPdHuP8jp2zTEQvXAQGZTjuJsXvcX0Q%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/CACjxfUuO%3DDu0TvXxHEqcU5xdj53MMxQj%2BFxcmOxy-kBVM9pFhA%40mail.gmail.com.


Re: [weewx-user] Re: Belchertown: earthquake miles vs km's

2020-12-26 Thread Colin Larsen
Arend

Great call sir! In fact even though I use all metric units with my station
that unit was not set at all. Added group_distance = km to the Belchertown
skin and that has solved the problem

Many thanks!

Regards and best to you.
Colin

On Sun, 27 Dec 2020 at 01:07, Arend  wrote:

> Hi Colin,
>
> Could you please check in weewx.conf if your setting for group_distance is
> set to km? Like this:
>
> [[Defaults]]
> [[[Units]]]
> # The following section sets what unit to use for each unit
> group.
> # NB: The unit is always in the singular. I.e.,
> 'mile_per_hour',
> # NOT 'miles_per_hour'
> Groups
> group_altitude = meter# Options are 'foot' or 'meter'
> group_degree_day = degree_C_day# Options are
> 'degree_F_day' or 'degree_C_day'
> *group_distance = km# Options are 'mile' or 'km'*
> group_pressure = hPa# Options are 'inHg', 'mmHg',
> 'mbar', or 'hPa'
> group_rain = mm# Options are 'inch', 'cm', or 'mm'
> group_rainrate = mm_per_hour# Options are
> 'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
> group_speed = km_per_hour# Options are
> 'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
> group_speed2 = km_per_hour2# Options are
> 'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
> group_temperature = degree_C# Options are 'degree_F'
> or 'degree_C'
>
> Regards, Arend
> Op vrijdag 25 december 2020 om 19:40:31 UTC+1 schreef colin@gmail.com:
>
>> With the GeoNet problem I had now fixed I am also getting distances to
>> earthquake locations in miles, when the rest of my site is km
>>
>> Thanks
>> Colin
>>
>> On Fri, 25 Dec 2020, 23:35 moth...@gmail.com,  wrote:
>>
>>> yes, it works, thanks for the adjustment.
>>> Ton
>>> http://weerstationnibbixwoud.nl/
>>>
>>> Op woensdag 28 oktober 2020 om 18:45:37 UTC+1 schreef blee...@xs4all.nl:
>>>
 Hallo Arend,

 Yes, it's working!

 Just aligning the new line after #25-10.4 solved the problem, manymany
 thanks!

 Best regards, Keimpe

 Op woensdag 28 oktober 2020 om 15:31:29 UTC+1 schreef Arend:

> Hi Keimpe,
>
> I have a suspicion why it didn't work out for you. Copying your code
> from your previous post into a text editor revealed that the changes you
> made were not properly alligned. The Python language is sensitive to
> indentation. The screenshot below shows a green and red line. The second
> eqmag (#25-10.4) should have been lined up to the green line like the 
> first
> eqmag (#25-10.3). But instead it was lined up to the red line, probably
> causing an exception (error) which would result in displaying that there
> was no earthquake data available.
>
> [image: Toelichting uitlijning code.png]
>
> I have included a new version of belchertown.py that has already been
> modified with the correct changes. Could you be so kind to download this
> file and use it to replace the existing belchertown.py. If this works then
> I will use this file for a pull request.
>
>
> Mvg, Arend
>
>
> Op woensdag 28 oktober 2020 om 11:38:34 UTC+1 schreef
> blee...@xs4all.nl:
>
>> Hoi Arend,
>>
>> Thanks for your efforts.
>>
>> Now changed back to the original file and (of cours) the EQ data is
>> back, as expected in 'mijl'.
>> In the log there is no related error, the only recursive error is a
>> Failed to publish record  to WOW.
>> Undermentioned you may find the earthquake section of belchertown.py
>> with the recommended changes. Between empty lines the original lines ar
>> commented out with #25-10.1 (#date and 1 is the line-number as suggested 
>> in
>> your GitHub post), following the line copied from GitHub.
>>
>> Regards, Keimpe
>>
>>
>> """
>> Earthquake Data
>> """
>> # Only process if Earthquake data is enabled
>> if self.generator.skin_dict['Extras']['earthquake_enabled']
>> == "1":
>> earthquake_file = html_root + "/json/earthquake.json"
>> earthquake_stale_timer =
>> self.generator.skin_dict['Extras']['earthquake_stale']
>> latitude =
>> self.generator.config_dict['Station']['latitude']
>> longitude =
>> self.generator.config_dict['Station']['longitude']
>>
>> #25-10.1distance_unit =
>> converter.group_unit_dict["group_distance"]
>> distance_unit =
>> self.generator.converter.group_unit_dict["group_distance"]
>>
>> eq_distance_label =
>> self.generator.skin_dict['Units']['Labels'].get(distance_unit, "")
>> eq_distance_round =
>> self.generator.skin_dict['Un

Re: [weewx-user] Re: Belchertown: earthquake miles vs km's

2020-12-25 Thread Colin Larsen
With the GeoNet problem I had now fixed I am also getting distances to
earthquake locations in miles, when the rest of my site is km

Thanks
Colin

On Fri, 25 Dec 2020, 23:35 moth...@gmail.com,  wrote:

> yes, it works, thanks for the adjustment.
> Ton
> http://weerstationnibbixwoud.nl/
>
> Op woensdag 28 oktober 2020 om 18:45:37 UTC+1 schreef blee...@xs4all.nl:
>
>> Hallo Arend,
>>
>> Yes, it's working!
>>
>> Just aligning the new line after #25-10.4 solved the problem, manymany
>> thanks!
>>
>> Best regards, Keimpe
>>
>> Op woensdag 28 oktober 2020 om 15:31:29 UTC+1 schreef Arend:
>>
>>> Hi Keimpe,
>>>
>>> I have a suspicion why it didn't work out for you. Copying your code
>>> from your previous post into a text editor revealed that the changes you
>>> made were not properly alligned. The Python language is sensitive to
>>> indentation. The screenshot below shows a green and red line. The second
>>> eqmag (#25-10.4) should have been lined up to the green line like the first
>>> eqmag (#25-10.3). But instead it was lined up to the red line, probably
>>> causing an exception (error) which would result in displaying that there
>>> was no earthquake data available.
>>>
>>> [image: Toelichting uitlijning code.png]
>>>
>>> I have included a new version of belchertown.py that has already been
>>> modified with the correct changes. Could you be so kind to download this
>>> file and use it to replace the existing belchertown.py. If this works then
>>> I will use this file for a pull request.
>>>
>>>
>>> Mvg, Arend
>>>
>>>
>>> Op woensdag 28 oktober 2020 om 11:38:34 UTC+1 schreef blee...@xs4all.nl:
>>>
 Hoi Arend,

 Thanks for your efforts.

 Now changed back to the original file and (of cours) the EQ data is
 back, as expected in 'mijl'.
 In the log there is no related error, the only recursive error is a
 Failed to publish record  to WOW.
 Undermentioned you may find the earthquake section of belchertown.py
 with the recommended changes. Between empty lines the original lines ar
 commented out with #25-10.1 (#date and 1 is the line-number as suggested in
 your GitHub post), following the line copied from GitHub.

 Regards, Keimpe


 """
 Earthquake Data
 """
 # Only process if Earthquake data is enabled
 if self.generator.skin_dict['Extras']['earthquake_enabled'] ==
 "1":
 earthquake_file = html_root + "/json/earthquake.json"
 earthquake_stale_timer =
 self.generator.skin_dict['Extras']['earthquake_stale']
 latitude = self.generator.config_dict['Station']['latitude']
 longitude =
 self.generator.config_dict['Station']['longitude']

 #25-10.1distance_unit = converter.group_unit_dict["group_distance"]
 distance_unit =
 self.generator.converter.group_unit_dict["group_distance"]

 eq_distance_label =
 self.generator.skin_dict['Units']['Labels'].get(distance_unit, "")
 eq_distance_round =
 self.generator.skin_dict['Units']['StringFormats'].get(distance_unit,
 "%.1f")
 earthquake_maxradiuskm =
 self.generator.skin_dict['Extras']['earthquake_maxradiuskm']
 #Sample URL from Belchertown Weather:
 http://earthquake.usgs.gov/fdsnws/event/1/query?limit=1&lat=42.223&lon=-72.374&maxradiuskm=1000&format=geojson&nodata=204&minmag=2
 if self.generator.skin_dict['Extras']['earthquake_server']
 == "USGS":
 earthquake_url = "
 http://earthquake.usgs.gov/fdsnws/event/1/query?limit=1&lat=%s&lon=%s&maxradiuskm=%s&format=geojson&nodata=204&minmag=2";
 % ( latitude, longitude, earthquake_maxradiuskm )
 elif
 self.generator.skin_dict['Extras']['earthquake_server'] == "GeoNet":
 earthquake_url = "https://api.geonet.org.nz/quake?MMI=4
 "
 earthquake_is_stale = False

 # Determine if the file exists and get it's modified time
 if os.path.isfile( earthquake_file ):
 if ( int( time.time() ) - int( os.path.getmtime(
 earthquake_file ) ) ) > int( earthquake_stale_timer ):
 earthquake_is_stale = True
 else:
 # File doesn't exist, download a new copy
 earthquake_is_stale = True

 # File is stale, download a new copy
 if earthquake_is_stale:
 # Download new earthquake data
 try:
 try:
 # Python 3
 from urllib.request import Request, urlopen
 except ImportError:
 # Python 2
 from urllib2 import Request, urlopen
 user_agent = 'Mozil

Re: [weewx-user] AQI with Belchertown ??

2020-09-22 Thread Colin Larsen
I modified the code on this AQI unit to send the data via UDP packets to my
Weewx server

https://wiki.weatherduino.com/air_quality_monitor_ii

I also use the complete WeatherDuino suite as my station, so it made sense
to head this direction


Cheers
Colin

On Wed, 23 Sep 2020, 04:07 Daniel Rich,  wrote:

> I  have it working with my PurpleAir and the weewx-purple extension.
>
> All I had to do was add pm2_5 to my sensor list and create a graph:
> station_observations = barometer, dewpoint, outHumidity, rainWithRainRate,
> pm2_5, radiation
>
> And in /etc/weewx/skins/Belchertown/graphs.conf:
> [[chart7]]
> title = Air Quality
> [[[pm2_5]]]
>name = AQI PM 2.5
>zIndex = 1
>color = "#becc00"
> [[[pm1_0]]]
>name = AQI PM 1.0
>zIndex = 1
>color = "#ffc83f"
> [[[pm10_0]]]
>name = AQI PM 10.0
>zIndex = 1
>color = "#c83fff"
>
> You can see it in action at https://www.lapseofthought.com/weather/
>
> Dan Rich  
> http://www.employees.org/~drich/
> "Step up to red alert!" "Are you sure, sir?
> It means changing the bulb in the sign..."
> - Red Dwarf (BBC)
> On Sep 22, 2020, 03:42 -0700, Tim Tuck , wrote:
>
> Hi all,
>
> Just wondering if anyone is displaying AQI with their Belchertown skin ?
>
> I'm using the AQI extension
>
> https://github.com/jonathankoren/weewx-aqi
>
> It appears to be working but I'll have to wait 24hrs to see if the data
> is being recorded in the aqi.db.
>
> I haven't tried to display the data yet since I don't have any data to
> display as yet :)
>
> But I thought I'd ask if any has AQI on their Belchertown skin would
> they like to share the config to achieve that.
>
> thanks
>
> Tim
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/cc75c921-d92a-6289-7af7-b19062a1f2e6%40skybase.net
> .
>
> --
> 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/dc7365e6-75fd-41b2-b024-57361d3e363b%40Spark
> 
> .
>

-- 
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/CACjxfUuaBw3_9o3fqevp6whMTAYELzBx7G-_xpk0yW6_KBi2vg%40mail.gmail.com.


Re: [weewx-user] AQI with Belchertown ??

2020-09-22 Thread Colin Larsen
Hi Tim

That's a custom AQI sensor forwarding data over wifi, captured by the pi
that runs weewx, saved to a file then grabbed by a weewx utility called
Filepile and the data added to the database. The rest is easy :)

Colin

On Tue, 22 Sep 2020, 22:48 Tim Tuck,  wrote:

> Hi Colin,
>
> That looks good, what sensors are you using for that ?
>
> Are you using the AQI extension or doing something else ?
>
> cheers
>
> Tim
> On 22/9/20 8:39 pm, Colin Larsen wrote:
>
> http://41south.nz/graphs/?graph=AQM
>
> Does this help?
>
> On Tue, 22 Sep 2020, 22:37 Tim Tuck,  wrote:
>
>> Hi all,
>>
>> Just wondering if anyone is displaying AQI with their Belchertown skin ?
>>
>> I'm using the AQI extension
>>
>> https://github.com/jonathankoren/weewx-aqi
>>
>> It appears to be working but I'll have to wait 24hrs to see if the data
>> is being recorded in the aqi.db.
>>
>> I haven't tried to display the data yet since I don't have any data to
>> display as yet :)
>>
>> But I thought I'd ask if any has AQI on their Belchertown skin would
>> they like to share the config to achieve that.
>>
>> thanks
>>
>> Tim
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/cc75c921-d92a-6289-7af7-b19062a1f2e6%40skybase.net
>> .
>>
> --
> 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/CACjxfUuX%2B9kot8hfjtS5MBdjzp5yVhxKf41myjuufH%3D6TWarYA%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CACjxfUuX%2B9kot8hfjtS5MBdjzp5yVhxKf41myjuufH%3D6TWarYA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> 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/d11b3880-152b-7f33-c24c-b13734694576%40skybase.net
> <https://groups.google.com/d/msgid/weewx-user/d11b3880-152b-7f33-c24c-b13734694576%40skybase.net?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUv5%2B%3Dws9T2JEEMthrYfvPwtoakBEUqxJnQdFCmw-jr%3D1g%40mail.gmail.com.


Re: [weewx-user] AQI with Belchertown ??

2020-09-22 Thread Colin Larsen
http://41south.nz/graphs/?graph=AQM

Does this help?

On Tue, 22 Sep 2020, 22:37 Tim Tuck,  wrote:

> Hi all,
>
> Just wondering if anyone is displaying AQI with their Belchertown skin ?
>
> I'm using the AQI extension
>
> https://github.com/jonathankoren/weewx-aqi
>
> It appears to be working but I'll have to wait 24hrs to see if the data
> is being recorded in the aqi.db.
>
> I haven't tried to display the data yet since I don't have any data to
> display as yet :)
>
> But I thought I'd ask if any has AQI on their Belchertown skin would
> they like to share the config to achieve that.
>
> thanks
>
> Tim
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/cc75c921-d92a-6289-7af7-b19062a1f2e6%40skybase.net
> .
>

-- 
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/CACjxfUuX%2B9kot8hfjtS5MBdjzp5yVhxKf41myjuufH%3D6TWarYA%40mail.gmail.com.


Re: [weewx-user] Belchertown Skin 1.2 (finally) released!

2020-09-11 Thread Colin Larsen
Great work Pat, thanks!

Cheers
Colin

On Sat, 12 Sep 2020, 06:46 Pat,  wrote:

> Belchertown Skin 1.2 is out of beta and released! You can download it here
> 
> .
>
> Thanks to everyone who helped test all the new changes, especially with
> the new Aeris Weather integration testing! DarkSky will be missed but Aeris
> is a great replacement.
>
> If you're upgrading, please pay attention to the breaking changes that you
> will need to migrate to.
>
> --
> 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/347ce4fe-f9b0-436e-9657-7212ddd694c1n%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/CACjxfUsPOjbyKjm2uzZWeUe%3D9%2BBGH%2BDuVEdT5J6Gak_JAcMw2A%40mail.gmail.com.


Re: [weewx-user] Unicode/UTF-8 characters no longer translating

2020-06-20 Thread Colin Larsen
Ah, that's brilliant, thanks Tom

Cheers
Colin

On Sun, 21 Jun 2020, 06:29 Tom Keffer,  wrote:

> It looks like you sorted this problem out yourself, but I thought I'd
> explain why your code was not working.
>
> Under Python 3, all strings are unicode. So, the line
>
> weewx.units.default_unit_label_dict['microgramm_per_meter_cubic']  = '
> \xce\xbcg/m\xc2\xb3'
>
>
> creates a unicode string with code points 32. 206, 188, 103, etc., which
> corresponds to characters 'μg/m³'. The key here is that your code
> is specifying *code points,* not UTF encodings.
>
> If you want to use UTF encodings, then you must decode them into unicode.
> So, it becomes:
>
> weewx.units.default_unit_label_dict['microgramm_per_meter_cubic']  = b'
> \xce\xbcg/m\xc2\xb3'.decode()
>
>
> The right hand side is now a *byte string*, which gets decoded into
> unicode.
>
> -tk
>
>
> On Wed, Jun 17, 2020 at 8:00 PM Colin Larsen 
> wrote:
>
>> Hi all
>>
>> As part of my installation I have FilePile grabbing some air quality
>> data. To get the proper unit formatting for micrograms per cubic meter I
>> use the units line below -
>>
>> weewx.units.default_unit_label_dict[*'microgramm_per_meter_cubic'*]  = *'
>> \xce\xbcg/m\xc2\xb3'*
>>
>> which was working fine until (I think) the update to either Weewx 4.0 or
>> Python 3. The output now looks like this ..
>>
>> CO2 level is 4904 ppm, AQM2.5 is 2.4 μg/m³, AQM10.0 is 2.8 μg/m³, Air
>> Quality Index is 10
>>
>> Any help appreciated
>>
>> Colin
>>
>> --
>> 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/CACjxfUubdgLPY1BaHv3Qe2p%3DkPteM4Ux76azcUpVLfDET117mA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CACjxfUubdgLPY1BaHv3Qe2p%3DkPteM4Ux76azcUpVLfDET117mA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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/CAPq0zEAHn9p%3DkBfP3UWF2Ue9Jp9QCb8DuZVV89veAJ4onzxrFQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEAHn9p%3DkBfP3UWF2Ue9Jp9QCb8DuZVV89veAJ4onzxrFQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUuLFw%2Bm4rCEPO3OgunZf3C-mxQrhvXjYs0QcsoFO3DBZg%40mail.gmail.com.


Re: [weewx-user] Unicode/UTF-8 characters no longer translating

2020-06-17 Thread Colin Larsen
Or it would help if I edited the right version of the file! My bad, time to
tidy up the file system a bit.

Cheers

On Thu, 18 Jun 2020 at 16:02, Colin Larsen  wrote:

> Whew!
>
> So interestingly that hasn't changed the results published on the web
> page, so I wonder if this is a skin problem not a Weewx one? I'm using the
> Belchertown skin (it's the latest beta but the latest production release
> also displayed the same) The 'about.inc' file has the following line in it
>
> "At $current.dateTime the following AQI data has been recorded. CO2 level
> is $current.AQICO2, AQM2.5 is $current.AQI25, AQM10.0 is $current.AQI100,
> Air Quality Index is $current.AQIIndex"
>
> The data is fine, it's just the units that haven't translated.
> Unfortunately this is something I rarely look at so I didn't see which
> update caused the change
>
>
> On Thu, 18 Jun 2020 at 15:44, gjr80  wrote:
>
>> Ha, did not even notice!
>>
>> Gary
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/3c059fd1-d0a5-453d-8813-0cb622d9dc42o%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/CACjxfUvk6M3Y_4O_DuTk3oEEei1wLSxF-%2BrKnUBd6WDuWm4osA%40mail.gmail.com.


Re: [weewx-user] Unicode/UTF-8 characters no longer translating

2020-06-17 Thread Colin Larsen
Whew!

So interestingly that hasn't changed the results published on the web page,
so I wonder if this is a skin problem not a Weewx one? I'm using the
Belchertown skin (it's the latest beta but the latest production release
also displayed the same) The 'about.inc' file has the following line in it

"At $current.dateTime the following AQI data has been recorded. CO2 level
is $current.AQICO2, AQM2.5 is $current.AQI25, AQM10.0 is $current.AQI100,
Air Quality Index is $current.AQIIndex"

The data is fine, it's just the units that haven't translated.
Unfortunately this is something I rarely look at so I didn't see which
update caused the change


On Thu, 18 Jun 2020 at 15:44, gjr80  wrote:

> Ha, did not even notice!
>
> Gary
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/3c059fd1-d0a5-453d-8813-0cb622d9dc42o%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/CACjxfUtY2J-YoeB7%3DH5oXku5gJmRP4zPidB075s5LSHXAmdyhw%40mail.gmail.com.


Re: [weewx-user] Unicode/UTF-8 characters no longer translating

2020-06-17 Thread Colin Larsen
Thanks gery

I've edited my FilePile.py to change all of my microgramm_per_meter_cubic
to microgram_per_meter_cubed and removed the other line, will see how that
goes.

Cheers
Colin

On Thu, 18 Jun 2020 at 15:28, gjr80  wrote:

> Hi,
>
> If you are using WeeWX 4.x you should be able to do away with that line as
> WeeWX now includes an (appropriate) entry for microgram_per_meter_cubed in
> weewx.units.default_unit_label_dict.
> https://github.com/weewx/weewx/blob/master/bin/weewx/units.py#L489 refers.
>
> Gary
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/edf04bf5-6686-4d28-9f6f-a8eea40bee66o%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/CACjxfUtxBivDHb3-4bnPWxgV%2BQsQ3TCTJpXas9dESjnEx68sQQ%40mail.gmail.com.


Re: [weewx-user] Unicode/UTF-8 characters no longer translating

2020-06-17 Thread Colin Larsen
Sorry, typo -- Gary :)

On Thu, 18 Jun 2020 at 15:37, Colin Larsen  wrote:

> Thanks gery
>
> I've edited my FilePile.py to change all of my microgramm_per_meter_cubic
> to microgram_per_meter_cubed and removed the other line, will see how
> that goes.
>
> Cheers
> Colin
>
> On Thu, 18 Jun 2020 at 15:28, gjr80  wrote:
>
>> Hi,
>>
>> If you are using WeeWX 4.x you should be able to do away with that line
>> as WeeWX now includes an (appropriate) entry for microgram_per_meter_cubed
>> in weewx.units.default_unit_label_dict.
>> https://github.com/weewx/weewx/blob/master/bin/weewx/units.py#L489
>> refers.
>>
>> Gary
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/edf04bf5-6686-4d28-9f6f-a8eea40bee66o%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/CACjxfUuv-DTmq6sn9KtXqJ7q%2B2_YRU%2BnLqdTkJoaTMXDufb5CQ%40mail.gmail.com.


[weewx-user] Unicode/UTF-8 characters no longer translating

2020-06-17 Thread Colin Larsen
Hi all

As part of my installation I have FilePile grabbing some air quality data.
To get the proper unit formatting for micrograms per cubic meter I use the
units line below -

weewx.units.default_unit_label_dict[*'microgramm_per_meter_cubic'*]  = *'
\xce\xbcg/m\xc2\xb3'*

which was working fine until (I think) the update to either Weewx 4.0 or
Python 3. The output now looks like this ..

CO2 level is 4904 ppm, AQM2.5 is 2.4 μg/m³, AQM10.0 is 2.8 μg/m³, Air
Quality Index is 10

Any help appreciated

Colin

-- 
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/CACjxfUubdgLPY1BaHv3Qe2p%3DkPteM4Ux76azcUpVLfDET117mA%40mail.gmail.com.


Re: [weewx-user] Looking for somewhat 'open' weather station to use with Raspberry based projects

2020-05-17 Thread Colin Larsen
https://wiki.weatherduino.com/



On Mon, 18 May 2020 at 12:34, Tom Keffer  wrote:

> Just to correct the record, the Vantage protocol was not reverse
> engineered. They are one of the few vendors who have published their
> protocol
> ,
> and have for many years.
>
> On Sun, May 17, 2020 at 5:13 PM Greg Troxel  wrote:
>
>> "'Ben Luria' via weewx-user"  writes:
>>
>> > apologies if this topic came up before or in case I am off-topic here.
>> I'm
>> > toying with SDR and home automation on a Raspberry Pi and would like to
>> add
>> > weather data via WeeWX and a weather station. Is there any particular
>> brand
>> > / model I should go for or maybe avoid? Am looking for something solar
>> > powered optimally, but that is not a must.
>>
>> You put "open" in quotes, which means that I don't know what you mean by
>> that word :-)
>>
>> There are a few things you could mean:
>>
>>   1) well-understood interfaces and existing drivers so that you can get
>>   at the weather data and use it, and not have problems due to closed
>>   interfaces
>>
>>   2) open protocol, or perhaps reverse-engineered protocols, for the
>>   sensor suite (outside part) to talk to the console (inside, that you
>>   look at, and that usually is interfaced to a computer), so that you
>>   can sniff it with an SDR instead of using the console receiver.
>>
>>   3) being able to get at the weather data locally, without the device
>>   talking to some cloud service (not under your control, subject to the
>>   company stopping it, and likely run with proprietary software)
>>
>>   3A) separately from transport via cloud, can the local station produce
>>   observations by itself, or does it need a (perhaps implemented with
>>   proprietary software) cloud service to do that?
>>
>>   4) firmware/software for the weather station equipment being open source
>>
>>   5) an open hardware design for the station, even if it uses proprietary
>>   chips
>>
>>   6) full-on open, meaning open licenses for all silicon in the station,
>>   including CPUs and sensors, which leads you to RISC-V and for
>>   temp/humidity I'm really not sure what.
>>
>>
>> You mentioned home automation, so I would recommend you check out the
>> mqtt extension, which is I think what most use to bridge weewx data into
>> an automation system (such as Home Assistant, which is the natural
>> choice for weewx fans, being open source and python).
>>   https://github.com/weewx/weewx/wiki/mqtt
>>
>>
>> For 1, there are lots of choices, and basically you should look at what
>> weewx supports.
>>
>> For 2, I am not really aware of anything open, except for build-your-own
>> kinds of stations.  But maybe weatherflow is UDP over IP and counts
>> here.  The Davis VP2 protocol has been reverse engineered and there is
>> rtldavis.  However, the Davis datalogger/interface in the console has
>> the really nice property that when your computer goes down, it keeps
>> storing data, and then when you straighten out your computer from the
>> botched upgrade, or you get power back, weewx reads the data and your
>> historical record is 100% fine, as if you never went down.   So I don't
>> really want to get my data with an SDR on a unix computer, even though
>> I'd like to try that, because I really like it that I haven't lost data
>> the probably 6 times I've had an issue in about 2.5 years.
>>
>> For 3, Davis is fine, and some acurite setups have local USB.  Various
>> other systems have "interceptor" drivers that snoop the data going to
>> the cloud, and I have the impression that sometimes people fetch their
>> own data back from the cloud because that's all they can do.
>>
>> For 3a, note Vince's comments about weatherflow and rain.  (I think
>> weatherflow is really interesting and don't mean to knock them.  I just
>> find the notion that you don't know how much rain you got without the
>> internet quite curious.  On the other hand sometimes with Davis it rains
>> and you conclude from the readings that you have a bird's nest, wasp's
>> nest or pine needles in your rain collector or blocking the tipping
>> bucket from tipping.)
>>
>> For 4, and even more so for 5, I'm not aware of any contenders, other
>> than build-your-own with arduino and e.g. i2c sensors.  But this is
>> very interesting and may qualify:
>>
>> https://www.tinkerforge.com/en/doc/Kits/WeatherStation/WeatherStation.html
>>   https://www.tinkerforge.com/en/shop/bricklets/sensors.html
>> However, I don't see rain and wind.
>>
>> For 6, my impresssion is that I will be viewed as crazy just for
>> bringing it up.
>>
>>
>> That leaves you with all the other considerations, which is that Davis
>> is expensive but otherwise viewed favorably by most, and that various
>> cheap stations are cheap and tend to fail.  And weatherflow seems to
>> turn everyone who plays with one into a fan, which is a very positive
>> comme

Re: [weewx-user] Python versions

2020-05-09 Thread Colin Larsen
Perfect, thank you sir, case closed :)

And again many thanks for all the work that goes into this project.

On Sun, 10 May 2020, 08:55 gjr80,  wrote:

> A couple of things happened in WeeWX 4, a fair amount of code was moved
> from engine.py to weewxd, this included the code that adds the stack trace
> on exit, plus WeeWX logging changed from using the syslog package to using
> the logging package. Under 3.9.2 the stack trace on exit was sent to the
> log as debug level output, so it was only seen if debug >= 1. There was a
> subsequent change by Tom that explicitly states he was changing the log
> level for that stack trace to info (will appear in log irrespective of
> debug setting). But I had some trouble following the commits on github as
> the code seemed to unexplainably change again. I think it is one for Tom
> given the explicit commit he made on it.
>
> Bottom line it is nothing wrong with your install or nor is it caused by
> anything you have done (other than shutting down or restarting 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1a88958e-02d1-456b-a37f-321c1394d960%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/CACjxfUtx-nJGS1FJkvms9FwHmpRgKmhz%3D215kmQG2_cw3RcOqw%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-09 Thread Colin Larsen
Thanks Gary, does that mean that it's just peculiar to my setup? I haven't
heard of any others reporting it.

Good to know it's nothing serious :)

Colin


On Sun, 10 May 2020, 08:25 gjr80,  wrote:

> There is no error. It is an informational stack trace on WeeWX exit and it
> cannot be turned off without modifying the code base.
>
> Gary
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/34e60342-0957-4a54-83e7-c959004745b4%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/CACjxfUuigZjCqb1mD3iz%2BPUn0WVOso7hwi-t6Y%2BYu5XEtbs%2BXA%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-09 Thread Colin Larsen
Hi gents

Is there anything I can do for the error I posted above that only seems to
happen on Weewx service stop?

Thanks
Colin

On Fri, 8 May 2020, 11:00 gjr80,  wrote:

> Good, I have submitted a PR for the change to the repo owner.
>
> Gary
>
> On Thursday, 7 May 2020 17:32:49 UTC+10, Greg from Oz wrote:
>>
>> Hi Gary,
>>
>> I add the highlighted text you suggested into line 277
>> of gauge-data.txt.tmpl
>> so it in now like this:
>> #if $hour.rain.sum.raw is not None and $hour.rain.sum.raw > $hourlyrainTH
>> and I had no errors and the gauges have now appeared.
>>
>> So it works. I don't think I could have worked that one out by myself.
>>
>> Hopefully this will help someone else as well. I will let you know if
>> anything else happens but so far so good.
>>
>> Thanks
>>
>>
>>
>> On Thursday, 7 May 2020 17:03:06 UTC+10, gjr80 wrote:
>>>
>>> As you are no doubt aware by now tracking down python errors that occur
>>> in a template (as distinct from python errors in a SLE or the WeeWX code
>>> base) can be a real pain as we can't reconcile the line number given in the
>>> error message with any source code. The following line tells us the error
>>> is in some in-line python code in the gauge-data.txt.tmpl template:
>>>
>>> May  7 09:35:24 jed165 weewx[2390] ERROR weewx.cheetahgenerator: 
>>>  File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 339, in respond
>>>
>>> If the error was in an SLE or the WeeWX code base we would have a nicely
>>> named (and known) .py (eg mySLE.py or cheetahgenerator.py) file rather
>>> than the cryptic name above. We can't use the line number from
>>> _etc_weewx_skins_ss_gauge_data_txt_tmpl.py as it is a temporary file
>>> created by Cheetah that we have no access to. The only thing we can use
>>> is the error message text, in your case:
>>>
>>> May  7 09:35:24 jed165 weewx[2390] ERROR weewx.cheetahgenerator: 
>>> TypeError: '>' not supported between instances of 'NoneType' and 'int'
>>>
>>> That message tells us a few things. We know that we have an error in an
>>> expression involving '>' (greater than). As it turns out > appears in the
>>> template only twice, at lines 69 and 277:
>>>
>>> #if $h > 0
>>>
>>> and
>>>
>>> #if $hour.rain.sum.raw > $hourlyrainTH
>>>
>>> We also know the left hand side is equating to None (the cause of the
>>> error) and the right hand side of the comparison is equating to an integer.
>>> If we look at line 69 if $h was None that would throw the error we are
>>> getting (0 in considered an int). $h is calculated at the line 68 and
>>> indirectly involves lines 66 and 67:
>>>
>>> #set $dp_K = $current.dewpoint.degree_C.raw + 273.16
>>> #set $e = 6.11 * math.exp(5417.7530 * ((1/273.16) - 1/$dp_K))
>>> #set $h = 0. * ($e - 10.0)
>>>
>>> We know $dp_K is not None; if it was we would get and error on line 66
>>> where $dp_K is calculated (None + 273.16). Therefore we know $h cannot
>>> be None. So line 69 is not the source of the error.
>>>
>>> If we look at line 277 to get the error we are seeing $hour.rain.sum.raw
>>> would need to be None and $hourlyrainTH would need to be an int.
>>> $hourlyrainTH is initialised to 0 at line 274, so $hourlyrainTH could
>>> be well be an int. Could $hour.rain.sum.raw be None, quite possible if
>>> there is no rain data (as distinct from there being data but it is 0) for a
>>> full hour sometime today. So it looks like we have found the problem line.
>>> How to fix it? Given the purpose of that piece of that piece of code is to
>>> find the hour of the highest rainfall today we can just put another
>>> conditional in there so we skip hours with no rainfall data, eg (not
>>> tested):
>>>
>>> #for $hour in $day.hours
>>> #if $hour.rain.sum.raw is not None and $hour.rain.sum.raw >
>>> $hourlyrainTH
>>> #set $hourlyrainTH = $hour.rain.sum.raw
>>>
>>> Now if $hour.rain.sum.raw is None the first conditional will cause
>>> execution to skip the rest of the if statement avoiding the problematic '>'.
>>>
>>> Apologies this was somewhat long winded, but I thought it a perfect
>>> opportunity to highlight one of the (few) techniques for tracking down
>>> in-line python errors in templates.
>>>
>>> Gary
>>>
>>> On Thursday, 7 May 2020 09:52:07 UTC+10, Greg from Oz wrote:

 I can live without the gauges. Below is the error:

 May  7 09:35:24 jed165 weewx[2390] DEBUG weewx.reportengine: Running
 report 'SteelSeries'
 May  7 09:35:24 jed165 weewx[2390] DEBUG weewx.reportengine: Found
 configuration file /etc/weewx/skins/ss/skin.conf for report 'SteelSeries'
 May  7 09:35:24 jed165 weewx[2390] INFO weewx.reportengine: Copied 0
 files to /var/www/html/weather/ss
 May  7 09:35:24 jed165 weewx[2390] DEBUG weewx.cheetahgenerator: Using
 search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.S
 tation', 'weewx.cheetahgenerator.Current',
 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
 'weewx.cheetahgenerator.Extras']
 May  

Re: [weewx-user] Re: Belchertown skin 1.1 released!

2020-05-09 Thread Colin Larsen
I have logged an issue in GitHub for the update error.

On Sun, 10 May 2020, 03:01 Maarten van der Hoeven, 
wrote:

> Hi,
>
> I have a general question about the skin. I calculate myself (using a
> php-script that reads mysql-data and write the output to a txt-file) the
> amount of lack of rain. It's a sum of daily Evapotranspìration (ET) minus
> the amounted precipitation.
>
> So I have this value inside a single TXT-file. What is the best way to
> display this value on the main belchertown-page? I can hack around, and I
> am sure I will succeeed :), but I want to do it the belchertown-skin-way,
> not to break it with future updates.
>
> Anyone?
>
> Op woensdag 8 april 2020 20:26:33 UTC+2 schreef Pat:
>>
>> As mentioned in this thread
>> , I've
>> released Belchertown skin 1.1. This will be the last skin that uses the
>> DarkSky API for weather conditions and forecasts. I'm going to begin
>> working on 1.2 soon to migrate to OpenWeatherMap.
>>
>> Read the entire release details here
>> 
>>  which
>> outline the breaking changes, new changes, items removed, etc.
>>
>> Always have a backup before you upgrade!
>>
>> Download:
>>
>> wget
>> https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.1/weewx-belchertown-release-1.1.tar.gz
>>
>> Then run:
>>
>> sudo wee_extension --install weewx-belchertown-release-1.1.tar.gz
>>
>>
>> Restart weewx when finished configuring.
>>
>>
>> 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/ecacebed-41d9-4306-a57f-cb83fa776702%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/CACjxfUuWzu4dtZVvXTrV5P6ew2WaYK6iziCEw%2BNUPn3w699ZNw%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-06 Thread Colin Larsen
That fixed it - thanks!!

My only error now is the one at service stop - no eros reported at start or
while running

May  7 16:24:53 raspberrypi systemd[1]: Stopping LSB: weewx weather
system...

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: Received signal
TERM (15).

May  7 16:24:53 raspberrypi weewx[10196] INFO weewx.engine: Main loop
exiting. Shutting engine down.

May  7 16:24:53 raspberrypi weewx[10196] INFO weewx.engine: Shutting down
StdReport thread

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: Terminating weewx
version 4.0.0

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__:   Traceback
(most recent call last):

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: File
"/usr/share/weewx/weewxd", line 154, in main

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: 
engine.run()

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: File
"/usr/share/weewx/weewx/engine.py", line 188, in run

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__:   for
packet in self.console.genLoopPackets():

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: File
"/usr/share/weewx/weewx/drivers/vantage.py", line 532, in genLoopPackets

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__:   for
_loop_packet in self.genDavisLoopPackets(200):

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: File
"/usr/share/weewx/weewx/drivers/vantage.py", line 559, in
genDavisLoopPackets

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: 
loop_packet
= self._get_packet()

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: File
"/usr/share/weewx/weewx/drivers/vantage.py", line 572, in _get_packet

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__:   _buffer
= self.port.read(99)

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: File
"/usr/share/weewx/weewx/drivers/vantage.py", line 279, in read

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__:   _buffer
= self.serial_port.read(chars)

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: File
"/usr/lib/python3/dist-packages/serial/serialposix.py", line 472, in read

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__:   ready,
_, _ = select.select([self.fd, self.pipe_abort_read_r], [], [],
timeout.time_left())

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__: File
"/usr/share/weewx/weewxd", line 257, in sigTERMhandler

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__:   raise
Terminate

May  7 16:24:53 raspberrypi weewx[10372]: Stopping weewx weather system:
weewx.

May  7 16:24:53 raspberrypi systemd[1]: Stopped LSB: weewx weather system.

May  7 16:24:53 raspberrypi weewx[10196] INFO __main__:   Terminate

On Thu, 7 May 2020 at 15:02, Tom Keffer  wrote:

> Missed that.
>
> Give it another try:
>
> https://raw.githubusercontent.com/tkeffer/weewx-owm/master/bin/user/owm.py
>
> -tk
>
> On Wed, May 6, 2020 at 4:57 PM Colin Larsen 
> wrote:
>
>> Whoops - nope, now getting this error from owm.py
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: OWM:
>> Unexpected exception of type 
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** Traceback
>> (most recent call last):
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
>> "/usr/share/weewx/weewx/restx.py", line 378, in run_loop
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** 
>> self.process_record(_record,
>> dbmanager)
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
>> "/usr/share/weewx/user/owm.py", line 210, in process_record
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***
>> self.post_with_retries(req)
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
>> "/usr/share/weewx/weewx/restx.py", line 472, in post_with_retries
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** _response
>> = self.post_request(request, data)
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
>> "/usr/share/weewx/weewx/restx.py", line 539, in post_request
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** _response
>> = urllib.request.urlopen(request, data=data_bytes, timeout=self.timeout)
>>
>> May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
>> "/usr/lib/python3.5/urllib/request.py", line 163, in urlopen
>>
>> May  7 11:55:15 raspberrypi 

Re: [weewx-user] Python versions

2020-05-06 Thread Colin Larsen
Whoops - nope, now getting this error from owm.py

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: OWM: Unexpected
exception of type 

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** Traceback
(most recent call last):

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
"/usr/share/weewx/weewx/restx.py", line 378, in run_loop

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***
self.process_record(_record,
dbmanager)

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
"/usr/share/weewx/user/owm.py", line 210, in process_record

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***
self.post_with_retries(req)

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
"/usr/share/weewx/weewx/restx.py", line 472, in post_with_retries

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** _response
= self.post_request(request, data)

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
"/usr/share/weewx/weewx/restx.py", line 539, in post_request

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** _response
= urllib.request.urlopen(request, data=data_bytes, timeout=self.timeout)

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
"/usr/lib/python3.5/urllib/request.py", line 163, in urlopen

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** return
opener.open(url, data, timeout)

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
"/usr/lib/python3.5/urllib/request.py", line 464, in open

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** req =
meth(req)

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: ***   File
"/usr/lib/python3.5/urllib/request.py", line 1183, in do_request_

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** raise
TypeError(msg)

May  7 11:55:15 raspberrypi weewx[4010] ERROR weewx.restx: *** TypeError:
POST data should be bytes or an iterable of bytes. It cannot be of type str.

May  7 11:55:15 raspberrypi weewx[4010] CRITICAL weewx.restx: OWM: Thread
terminating. Reason: POST data should be bytes or an iterable of bytes. It
cannot be of type str.

On Thu, 7 May 2020 at 11:55, Colin Larsen  wrote:

> That seems to have fixed owm - thanks!
>
> Getting this error on a restart - but no errors during the start itself
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO weewx.engine: Main loop
> exiting. Shutting engine down.
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: Terminating weewx
> version 4.0.0
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__:   Traceback
> (most recent call last):
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: File
> "/usr/share/weewx/weewxd", line 154, in main
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: 
> engine.run()
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: File
> "/usr/share/weewx/weewx/engine.py", line 188, in run
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__:   for
> packet in self.console.genLoopPackets():
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: File
> "/usr/share/weewx/weewx/drivers/vantage.py", line 532, in genLoopPackets
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__:   for
> _loop_packet in self.genDavisLoopPackets(200):
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: File
> "/usr/share/weewx/weewx/drivers/vantage.py", line 559, in
> genDavisLoopPackets
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__:   
> loop_packet
> = self._get_packet()
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: File
> "/usr/share/weewx/weewx/drivers/vantage.py", line 572, in _get_packet
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__:   _buffer
> = self.port.read(99)
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: File
> "/usr/share/weewx/weewx/drivers/vantage.py", line 279, in read
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__:   _buffer
> = self.serial_port.read(chars)
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: File
> "/usr/lib/python3/dist-packages/serial/serialposix.py", line 472, in read
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__:   ready,
> _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [],
> timeout.time_left())
>
> May  7 11:53:05 raspberrypi weewx[3923] INFO __main__: File
> "/usr/share/weewx/weewxd", line 257, in sig

Re: [weewx-user] Python versions

2020-05-06 Thread Colin Larsen
n/latest/> does a little
>> better and its results will run under 2 or 3, but they will also depend on
>> the library 'six'.
>>
>> Drivers and uploaders are especially tricky because they have to do
>> string <--> byte conversions. Those almost always have to be hand coded.
>>
>> In the end, I've found it easiest just to grind through the code manually.
>>
>> -tk
>>
>> On Wed, May 6, 2020 at 4:17 PM Greg from Oz  wrote:
>>
>>> I have run a program called 2to3 python converter program on some of the
>>> python2 scripts and it fixed most of the problems and did the conversion to
>>> the python3 syntax.
>>>
>>> example: 2to3 -w /usr/share/weewx/user/owm.py
>>>
>>>
>>> On Wednesday, 6 May 2020 12:31:23 UTC+10, Colin Larsen wrote:
>>>>
>>>> Fixed that one with; sudo python3 -m pip install paho-mqtt
>>>>
>>>> Now I have an error that looks like it is Open Wetaher map?
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: Caught
>>>> unrecoverable exception:
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   
>>>> invalid
>>>> syntax (owm.py, line 84)
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   
>>>> Traceback
>>>> (most recent call last):
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
>>>> "/usr/share/weewx/weewxd", line 148, in main
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>>>>   engine = weewx.engine.StdEngine(config_dict)
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
>>>> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>>>>   self.loadServices(config_dict)
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
>>>> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>>>>   obj = weeutil.weeutil.get_object(svc)(self,config_dict)
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
>>>> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>>>>   mod = __import__(module)
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
>>>> "/usr/share/weewx/user/owm.py", line 84
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>>>>   except KeyError, e:
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>>>>   ^
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   
>>>> SyntaxError:
>>>> invalid syntax
>>>>
>>>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>>>> Exiting.
>>>>
>>>> On Wed, 6 May 2020 at 14:19, Colin Larsen  wrote:
>>>>
>>>>> Still going ..
>>>>>
>>>>> Installed the new mqtt and now get this error
>>>>>
>>>>> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: Caught
>>>>> unrecoverable exception:
>>>>>
>>>>> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   No
>>>>> module named 'paho'
>>>>>
>>>>> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   
>>>>> Traceback
>>>>> (most recent call last):
>>>>>
>>>>> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
>>>>>   File "/usr/share/weewx/weewxd", line 148, in main
>>>>>
>>>>> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
>>>>> engine = weewx.engine.StdEngine(config_dict)
>>>>>
>>>>> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
>>>>>   File "/usr/

Re: [weewx-user] Python versions

2020-05-06 Thread Colin Larsen
Righto, back to Python2 it is, apologies for asking but hadn't seen this
one before.

Cheers and thanks
Colin

On Thu, 7 May 2020, 02:32 vince,  wrote:

> On Tuesday, May 5, 2020 at 7:31:23 PM UTC-7, Colin Larsen wrote:
>>
>>
>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   
>> except
>> KeyError, e:
>>
>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>> ^
>>
>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   
>> SyntaxError:
>> invalid syntax
>>
>> May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
>> Exiting.
>>
>>
>>
> This is almost the most frequently asked question.
>
> Any time you see that error, you are running python2 code that has not
> been updated to python3 syntax.   Either update your driver or extension to
> the latest version, or stay with python2 until the author of the
> driver/extension has updated their software to python3.
>
> --
> 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/10c129b2-7488-418c-8380-07115b479be2%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/10c129b2-7488-418c-8380-07115b479be2%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUsqFccLY_T0oPPwatGRd9tJs-ceOGqJyH1T2ps3VJ6mvw%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-05 Thread Colin Larsen
Fixed that one with; sudo python3 -m pip install paho-mqtt

Now I have an error that looks like it is Open Wetaher map?

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: Caught
unrecoverable exception:

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   invalid
syntax (owm.py, line 84)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   Traceback
(most recent call last):

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/weewxd", line 148, in main

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   engine
= weewx.engine.StdEngine(config_dict)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 75, in __init__

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
self.loadServices(config_dict)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   obj
= weeutil.weeutil.get_object(svc)(self,config_dict)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   mod
= __import__(module)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/user/owm.py", line 84

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   except
KeyError, e:

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
^

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
SyntaxError:
invalid syntax

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
Exiting.

On Wed, 6 May 2020 at 14:19, Colin Larsen  wrote:

> Still going ..
>
> Installed the new mqtt and now get this error
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: Caught
> unrecoverable exception:
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   No
> module named 'paho'
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   Traceback
> (most recent call last):
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/weewxd", line 148, in main
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   
> engine
> = weewx.engine.StdEngine(config_dict)
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
> self.loadServices(config_dict)
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   obj
> = weeutil.weeutil.get_object(svc)(self,config_dict)
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   mod
> = __import__(module)
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/user/mqtt.py", line 94, in 
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   
> import
> paho.mqtt.client as mqtt
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   
> ImportError:
> No module named 'paho'
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
> Exiting.
>
>
> Tried to install Paho and I get  ...
>
>
> *pi@raspberrypi*:*/etc/default $* sudo pip install paho-mqtt
>
> Requirement already satisfied: paho-mqtt in
> /usr/local/lib/python2.7/dist-packages
>
>
> So how do I install it for python3 please :)
>
>
>
> Cheers
>
> Colin
>
> On Tue, 5 May 2020 at 00:18, Graham Eddy  wrote:
>
>> this (ujson instead of python-cjson, then install mqtt extension) seems
>> to have worked up to point that weewx.log reports its mqtt client is
>> successfully publishing loop data
>>
>> sudo python3.7 -m pip install ujson
>>
>>
>> On 4 May 2020, at 8:58 pm, Graham Eddy  wrote:
>>
>> i have only just become interested in mqtt (to make my custom weewx
>> gauges near realtime).
>> the link to the MQTT weewx extension mentioned below lists two
>> prerequisites: paho-mqtt, python-cj

Re: [weewx-user] Python versions

2020-05-05 Thread Colin Larsen
Still going ..

Installed the new mqtt and now get this error

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: Caught
unrecoverable exception:

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   No
module named 'paho'

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   Traceback
(most recent call last):

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/weewxd", line 148, in main

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   engine
= weewx.engine.StdEngine(config_dict)

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 75, in __init__

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
self.loadServices(config_dict)

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   obj
= weeutil.weeutil.get_object(svc)(self,config_dict)

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   mod
= __import__(module)

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/user/mqtt.py", line 94, in 

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   import
paho.mqtt.client as mqtt

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
ImportError:
No module named 'paho'

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
Exiting.


Tried to install Paho and I get  ...


*pi@raspberrypi*:*/etc/default $* sudo pip install paho-mqtt

Requirement already satisfied: paho-mqtt in
/usr/local/lib/python2.7/dist-packages


So how do I install it for python3 please :)



Cheers

Colin

On Tue, 5 May 2020 at 00:18, Graham Eddy  wrote:

> this (ujson instead of python-cjson, then install mqtt extension) seems to
> have worked up to point that weewx.log reports its mqtt client is
> successfully publishing loop data
>
> sudo python3.7 -m pip install ujson
>
>
> On 4 May 2020, at 8:58 pm, Graham Eddy  wrote:
>
> i have only just become interested in mqtt (to make my custom weewx gauges
> near realtime).
> the link to the MQTT weewx extension mentioned below lists two
> prerequisites: paho-mqtt, python-cjson.
> paho-mqtt installed fine.
> python-cjson fails.
>
>
> --
> 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/296D8321-100E-45B1-A47A-2657960A2942%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/CACjxfUtC14PaLfQAduzGhZNaNeN4M6okpfM-rBGF7DDT0gb-mQ%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-03 Thread Colin Larsen
Perfect will do that tonight, thanks Tom

On Mon, 4 May 2020, 07:28 Tom Keffer,  wrote:

> Colin, yes, your version of mqtt.py needs to be updated. You can the link
> on the MQTT wiki page <https://github.com/weewx/weewx/wiki/mqtt>.
>
> On Sun, May 3, 2020 at 12:21 PM Colin Larsen 
> wrote:
>
>> So just double checking, Matt was this the definitive answer that the
>> version of mqtt needs updating?
>>
>> Cheers
>> Colin
>>
>> On Sun, 3 May 2020, 20:32 Jaap de Munck,  wrote:
>>
>>> That means your MQTT extension is not Python3 proof!
>>> Get your self an updated version.
>>> Is it this one: https://github.com/weewx/weewx/wiki/mqtt ?
>>> <https://github.com/weewx/weewx/wiki/mqtt>
>>>
>>>
>>> Op zondag 3 mei 2020 06:29:34 UTC+2 schreef Colin Larsen:
>>>>
>>>> This may be a problem? After changing to python3 ..
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: Caught
>>>> unrecoverable exception:
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   
>>>> invalid
>>>> syntax (mqtt.py, line 196)
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   
>>>> Traceback
>>>> (most recent call last):
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>>>> "/usr/share/weewx/weewxd", line 148, in main
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>>>>   engine = weewx.engine.StdEngine(config_dict)
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>>>> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>>>>   self.loadServices(config_dict)
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>>>> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>>>>   obj = weeutil.weeutil.get_object(svc)(self,config_dict)
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>>>> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>>>>   mod = __import__(module)
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>>>> "/usr/share/weewx/user/mqtt.py", line 196
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>>>>   except KeyError, e:
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>>>>   ^
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   
>>>> SyntaxError:
>>>> invalid syntax
>>>>
>>>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>>>> Exiting.
>>>>
>>>> On Sun, 3 May 2020 at 15:45, Colin Larsen  wrote:
>>>>
>>>>> Ah .. that will be the missing piece of the puzzle! Off to sort
>>>>> that now, will report back.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> On Sun, 3 May 2020 at 15:30, mwall 
>>>>> wrote:
>>>>>
>>>>>> On Saturday, May 2, 2020 at 9:11:51 PM UTC-4, Colin Larsen wrote:
>>>>>>>
>>>>>>> I found this /etc/default
>>>>>>>
>>>>>>> WEEWX_PYTHON=python2
>>>>>>>
>>>>>>> WEEWX_BINDIR=/usr/share/weewx
>>>>>>>
>>>>>>> WEEWX_BIN=/usr/bin/weewxd
>>>>>>>
>>>>>>> WEEWX_CFG=/etc/weewx/weewx.conf
>>>>>>>
>>>>>>>
>>>>>>> Changing it to python3 breaks weewx so I'll just leave well enough
>>>>>>> alone
>>>>>>>
>>>>>>
>>>>>> you *should* be able to switch from python2 to python3 simply by
>>>>>> changing the WEEWX_PYTHON line.  however, if you were run

Re: [weewx-user] Python versions

2020-05-03 Thread Colin Larsen
So just double checking, Matt was this the definitive answer that the
version of mqtt needs updating?

Cheers
Colin

On Sun, 3 May 2020, 20:32 Jaap de Munck,  wrote:

> That means your MQTT extension is not Python3 proof!
> Get your self an updated version.
> Is it this one: https://github.com/weewx/weewx/wiki/mqtt ?
> <https://github.com/weewx/weewx/wiki/mqtt>
>
>
> Op zondag 3 mei 2020 06:29:34 UTC+2 schreef Colin Larsen:
>>
>> This may be a problem? After changing to python3 ..
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: Caught
>> unrecoverable exception:
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   invalid
>> syntax (mqtt.py, line 196)
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   
>> Traceback
>> (most recent call last):
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>> "/usr/share/weewx/weewxd", line 148, in main
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   
>> engine
>> = weewx.engine.StdEngine(config_dict)
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>> self.loadServices(config_dict)
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   obj
>> = weeutil.weeutil.get_object(svc)(self,config_dict)
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   mod
>> = __import__(module)
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
>> "/usr/share/weewx/user/mqtt.py", line 196
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   
>> except
>> KeyError, e:
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>> ^
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   
>> SyntaxError:
>> invalid syntax
>>
>> May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
>> Exiting.
>>
>> On Sun, 3 May 2020 at 15:45, Colin Larsen  wrote:
>>
>>> Ah .. that will be the missing piece of the puzzle! Off to sort that
>>> now, will report back.
>>>
>>> Thanks!
>>>
>>> On Sun, 3 May 2020 at 15:30, mwall  wrote:
>>>
>>>> On Saturday, May 2, 2020 at 9:11:51 PM UTC-4, Colin Larsen wrote:
>>>>>
>>>>> I found this /etc/default
>>>>>
>>>>> WEEWX_PYTHON=python2
>>>>>
>>>>> WEEWX_BINDIR=/usr/share/weewx
>>>>>
>>>>> WEEWX_BIN=/usr/bin/weewxd
>>>>>
>>>>> WEEWX_CFG=/etc/weewx/weewx.conf
>>>>>
>>>>>
>>>>> Changing it to python3 breaks weewx so I'll just leave well enough
>>>>> alone
>>>>>
>>>>
>>>> you *should* be able to switch from python2 to python3 simply by
>>>> changing the WEEWX_PYTHON line.  however, if you were running with python2
>>>> and you have not installed the python3 dependencies, then of course weewx
>>>> won't run.
>>>>
>>>> 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...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
> 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/f3000d48-6728-47f3-9b3f-cc6dff38018d%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/f3000d48-6728-47f3-9b3f-cc6dff38018d%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUt%2BN8tPjO6m6iSU9CiAYPXcSyeuwiB1wUMtPsVg_rQZqQ%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-02 Thread Colin Larsen
This may be a problem? After changing to python3 ..

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: Caught
unrecoverable exception:

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   invalid
syntax (mqtt.py, line 196)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   Traceback
(most recent call last):

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/weewxd", line 148, in main

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   engine
= weewx.engine.StdEngine(config_dict)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 75, in __init__

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
self.loadServices(config_dict)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   obj
= weeutil.weeutil.get_object(svc)(self,config_dict)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   mod
= __import__(module)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/user/mqtt.py", line 196

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   except
KeyError, e:

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
^

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
SyntaxError:
invalid syntax

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
Exiting.

On Sun, 3 May 2020 at 15:45, Colin Larsen  wrote:

> Ah .. that will be the missing piece of the puzzle! Off to sort that
> now, will report back.
>
> Thanks!
>
> On Sun, 3 May 2020 at 15:30, mwall  wrote:
>
>> On Saturday, May 2, 2020 at 9:11:51 PM UTC-4, Colin Larsen wrote:
>>>
>>> I found this /etc/default
>>>
>>> WEEWX_PYTHON=python2
>>>
>>> WEEWX_BINDIR=/usr/share/weewx
>>>
>>> WEEWX_BIN=/usr/bin/weewxd
>>>
>>> WEEWX_CFG=/etc/weewx/weewx.conf
>>>
>>>
>>> Changing it to python3 breaks weewx so I'll just leave well enough alone
>>>
>>
>> you *should* be able to switch from python2 to python3 simply by changing
>> the WEEWX_PYTHON line.  however, if you were running with python2 and you
>> have not installed the python3 dependencies, then of course weewx won't run.
>>
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/CACjxfUuaE3hjkN14VvRaCpsgc1d6Lgan5HL0972%2BdmThXGbD0w%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-02 Thread Colin Larsen
Ah .. that will be the missing piece of the puzzle! Off to sort that
now, will report back.

Thanks!

On Sun, 3 May 2020 at 15:30, mwall  wrote:

> On Saturday, May 2, 2020 at 9:11:51 PM UTC-4, Colin Larsen wrote:
>>
>> I found this /etc/default
>>
>> WEEWX_PYTHON=python2
>>
>> WEEWX_BINDIR=/usr/share/weewx
>>
>> WEEWX_BIN=/usr/bin/weewxd
>>
>> WEEWX_CFG=/etc/weewx/weewx.conf
>>
>>
>> Changing it to python3 breaks weewx so I'll just leave well enough alone
>>
>
> you *should* be able to switch from python2 to python3 simply by changing
> the WEEWX_PYTHON line.  however, if you were running with python2 and you
> have not installed the python3 dependencies, then of course weewx won't run.
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUtM_R7ZeBsCQ%2B4UoZPLDnFQQP3cMygOryLWNj5cHDsBtQ%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-02 Thread Colin Larsen
Whoops sorry /etc/default/weewx that should have been

On Sun, 3 May 2020 at 13:11, Colin Larsen  wrote:

> I found this /etc/default
>
> WEEWX_PYTHON=python2
>
> WEEWX_BINDIR=/usr/share/weewx
>
> WEEWX_BIN=/usr/bin/weewxd
>
> WEEWX_CFG=/etc/weewx/weewx.conf
>
>
> Changing it to python3 breaks weewx so I'll just leave well enough alone
>
>
> Colin
>
> On Sun, 3 May 2020 at 12:54, Colin Larsen  wrote:
>
>> Hi Graham
>>
>> Thanks for that and I understand all of what you are saying - except I
>> have no idea whereabouts in /etc/init.d/weewx to change to make it use
>> Python3. I thought I might find the line command line containing weewxd in
>> there somewhere but alas no (or I've done a "boy look"). And I know enough
>> this part of the system to be dangerous, so I'll keep fingers off until I
>> can actually figure this out! Still learning lots here so appreciate the
>> patience and explanations :)
>>
>> Colin
>>
>> On Sun, 3 May 2020 at 12:44, Graham Eddy  wrote:
>>
>>> as others have already mentioned you can instruct use of python3 either
>>>  (a) system-wide e.g. /etc/default or defaults
>>>  (b) startup e.g. /etc/init.d/weewx or /Library/LaunchDaemons/com
>>> <http://LaunchDameons.com>.weewx.weewxd
>>>  (c) embedded e.g. shebang (insert #!python3 in first line of weewxd)
>>>
>>> my platform (macos) provides python2.7 native not python3.7 and i
>>> hesitate to set system-wide in case it impacts some other platform-provided
>>> utilities. i find startup approach inconvenient on macos so i usually use
>>> embedded (shebang), in my case #!/opt/local/bin/python3.7 because that’s
>>> where macports puts python3
>>>
>>> On 3 May 2020, at 10:30 am, Colin Larsen  wrote:
>>>
>>> Thanks Tom
>>>
>>> Well /etc/init.d/weewx is there and the other one isn't so I'll go with
>>> that but to be honest the innards of that file is out of my depth.
>>>
>>> On Sun, 3 May 2020 at 12:20, Tom Keffer  wrote:
>>>
>>>> You will have to edit whatever script you use to start weewx as a
>>>> daemon.
>>>>
>>>> Look in /etc/init.d/weewx. If not there, then
>>>> /etc/systemd/system/weewx.service.
>>>>
>>>> -tk
>>>>
>>>> On Sat, May 2, 2020 at 5:13 PM Colin Larsen 
>>>> wrote:
>>>>
>>>>> Hi all
>>>>>
>>>>> I know that this is buried somewhere in the threads of information,
>>>>> sorry apologies for not being able to find it.
>>>>>
>>>>> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
>>>>> method. Ihas Python3 installed but is still using Python2 as can be seen
>>>>> here. I thought I had read that if Python3 was already installed then the
>>>>> update would use that version - apparently not :)
>>>>>
>>>>
>>> --
>>> 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/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.com
>>> <https://groups.google.com/d/msgid/weewx-user/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/CACjxfUsP%2B31UVQ2tKBVmLFTgkt9OxfM5t96hy3hxUtar6RjJvw%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-02 Thread Colin Larsen
I found this /etc/default

WEEWX_PYTHON=python2

WEEWX_BINDIR=/usr/share/weewx

WEEWX_BIN=/usr/bin/weewxd

WEEWX_CFG=/etc/weewx/weewx.conf


Changing it to python3 breaks weewx so I'll just leave well enough alone


Colin

On Sun, 3 May 2020 at 12:54, Colin Larsen  wrote:

> Hi Graham
>
> Thanks for that and I understand all of what you are saying - except I
> have no idea whereabouts in /etc/init.d/weewx to change to make it use
> Python3. I thought I might find the line command line containing weewxd in
> there somewhere but alas no (or I've done a "boy look"). And I know enough
> this part of the system to be dangerous, so I'll keep fingers off until I
> can actually figure this out! Still learning lots here so appreciate the
> patience and explanations :)
>
> Colin
>
> On Sun, 3 May 2020 at 12:44, Graham Eddy  wrote:
>
>> as others have already mentioned you can instruct use of python3 either
>>  (a) system-wide e.g. /etc/default or defaults
>>  (b) startup e.g. /etc/init.d/weewx or /Library/LaunchDaemons/com
>> <http://LaunchDameons.com>.weewx.weewxd
>>  (c) embedded e.g. shebang (insert #!python3 in first line of weewxd)
>>
>> my platform (macos) provides python2.7 native not python3.7 and i
>> hesitate to set system-wide in case it impacts some other platform-provided
>> utilities. i find startup approach inconvenient on macos so i usually use
>> embedded (shebang), in my case #!/opt/local/bin/python3.7 because that’s
>> where macports puts python3
>>
>> On 3 May 2020, at 10:30 am, Colin Larsen  wrote:
>>
>> Thanks Tom
>>
>> Well /etc/init.d/weewx is there and the other one isn't so I'll go with
>> that but to be honest the innards of that file is out of my depth.
>>
>> On Sun, 3 May 2020 at 12:20, Tom Keffer  wrote:
>>
>>> You will have to edit whatever script you use to start weewx as a daemon.
>>>
>>> Look in /etc/init.d/weewx. If not there, then
>>> /etc/systemd/system/weewx.service.
>>>
>>> -tk
>>>
>>> On Sat, May 2, 2020 at 5:13 PM Colin Larsen 
>>> wrote:
>>>
>>>> Hi all
>>>>
>>>> I know that this is buried somewhere in the threads of information,
>>>> sorry apologies for not being able to find it.
>>>>
>>>> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
>>>> method. Ihas Python3 installed but is still using Python2 as can be seen
>>>> here. I thought I had read that if Python3 was already installed then the
>>>> update would use that version - apparently not :)
>>>>
>>>
>> --
>> 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/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/CACjxfUviu1eGsfs5hXO4wOeivJCN267BKYk74-kF_v5DvxRtHQ%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-02 Thread Colin Larsen
Hi Graham

Thanks for that and I understand all of what you are saying - except I have
no idea whereabouts in /etc/init.d/weewx to change to make it use Python3.
I thought I might find the line command line containing weewxd in there
somewhere but alas no (or I've done a "boy look"). And I know enough this
part of the system to be dangerous, so I'll keep fingers off until I can
actually figure this out! Still learning lots here so appreciate the
patience and explanations :)

Colin

On Sun, 3 May 2020 at 12:44, Graham Eddy  wrote:

> as others have already mentioned you can instruct use of python3 either
>  (a) system-wide e.g. /etc/default or defaults
>  (b) startup e.g. /etc/init.d/weewx or /Library/LaunchDaemons/com
> <http://LaunchDameons.com>.weewx.weewxd
>  (c) embedded e.g. shebang (insert #!python3 in first line of weewxd)
>
> my platform (macos) provides python2.7 native not python3.7 and i hesitate
> to set system-wide in case it impacts some other platform-provided
> utilities. i find startup approach inconvenient on macos so i usually use
> embedded (shebang), in my case #!/opt/local/bin/python3.7 because that’s
> where macports puts python3
>
> On 3 May 2020, at 10:30 am, Colin Larsen  wrote:
>
> Thanks Tom
>
> Well /etc/init.d/weewx is there and the other one isn't so I'll go with
> that but to be honest the innards of that file is out of my depth.
>
> On Sun, 3 May 2020 at 12:20, Tom Keffer  wrote:
>
>> You will have to edit whatever script you use to start weewx as a daemon.
>>
>> Look in /etc/init.d/weewx. If not there, then
>> /etc/systemd/system/weewx.service.
>>
>> -tk
>>
>> On Sat, May 2, 2020 at 5:13 PM Colin Larsen 
>> wrote:
>>
>>> Hi all
>>>
>>> I know that this is buried somewhere in the threads of information,
>>> sorry apologies for not being able to find it.
>>>
>>> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
>>> method. Ihas Python3 installed but is still using Python2 as can be seen
>>> here. I thought I had read that if Python3 was already installed then the
>>> update would use that version - apparently not :)
>>>
>>
> --
> 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/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.com
> <https://groups.google.com/d/msgid/weewx-user/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUsK1bUg9xt0_ecvhQG3%3DYgMya%3DjeET_1YsvrxMCukBwoA%40mail.gmail.com.


Re: [weewx-user] Python versions

2020-05-02 Thread Colin Larsen
Thanks Tom

Well /etc/init.d/weewx is there and the other one isn't so I'll go with
that but to be honest the innards of that file is out of my depth.

On Sun, 3 May 2020 at 12:20, Tom Keffer  wrote:

> You will have to edit whatever script you use to start weewx as a daemon.
>
> Look in /etc/init.d/weewx. If not there, then
> /etc/systemd/system/weewx.service.
>
> -tk
>
> On Sat, May 2, 2020 at 5:13 PM Colin Larsen 
> wrote:
>
>> Hi all
>>
>> I know that this is buried somewhere in the threads of information, sorry
>> apologies for not being able to find it.
>>
>> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
>> method. Ihas Python3 installed but is still using Python2 as can be seen
>> here. I thought I had read that if Python3 was already installed then the
>> update would use that version - apparently not :)
>>
>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>>
>> permitted by applicable law.
>>
>> Last login: Wed Apr 29 09:47:37 2020 from 192.168.20.45
>>
>> *pi@raspberrypi*:*~ $* ps -ef|grep weewx
>>
>> pi   30253 30223  0 12:01 pts/000:00:00 grep --color=auto *weewx*
>>
>> root 32235 1  5 May01 ?02:23:06 python2 /usr/share/
>> *weewx*/*weewx*d --daemon --pidfile=/var/run/*weewx*.pid /etc/*weewx*/
>> *weewx*.conf
>>
>> *pi@raspberrypi*:*~ $* python3 --version
>>
>> Python 3.5.3
>>
>> *pi@raspberrypi*:*~ $*
>>
>>
>> Whats the trick that I've missed to tell it to use Python3?
>>
>>
>> Many thanks
>>
>> Colin
>>
>> --
>> 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/CACjxfUv_62X8mX2Q8zG7SO6-9TWXgWaFHYLRO8LTnPmrMRTJYw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CACjxfUv_62X8mX2Q8zG7SO6-9TWXgWaFHYLRO8LTnPmrMRTJYw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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/CAPq0zECE9FUpRR_gZ6TCrRM6zp1msX0OhGPVpbFBgSpP93TdOA%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zECE9FUpRR_gZ6TCrRM6zp1msX0OhGPVpbFBgSpP93TdOA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUsEoKux5XztQik_7Yj16fsj59EE6w02pJyQFFu5Evby%2BQ%40mail.gmail.com.


[weewx-user] Python versions

2020-05-02 Thread Colin Larsen
Hi all

I know that this is buried somewhere in the threads of information, sorry
apologies for not being able to find it.

I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
method. Ihas Python3 installed but is still using Python2 as can be seen
here. I thought I had read that if Python3 was already installed then the
update would use that version - apparently not :)

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.

Last login: Wed Apr 29 09:47:37 2020 from 192.168.20.45

*pi@raspberrypi*:*~ $* ps -ef|grep weewx

pi   30253 30223  0 12:01 pts/000:00:00 grep --color=auto *weewx*

root 32235 1  5 May01 ?02:23:06 python2 /usr/share/*weewx*/
*weewx*d --daemon --pidfile=/var/run/*weewx*.pid /etc/*weewx*/*weewx*.conf

*pi@raspberrypi*:*~ $* python3 --version

Python 3.5.3

*pi@raspberrypi*:*~ $*


Whats the trick that I've missed to tell it to use Python3?


Many thanks

Colin

-- 
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/CACjxfUv_62X8mX2Q8zG7SO6-9TWXgWaFHYLRO8LTnPmrMRTJYw%40mail.gmail.com.


Re: [weewx-user] Re: Version 4.0 is (finally) here!

2020-04-30 Thread Colin Larsen
I've just updated from 3.9 to 4.0 on my RPi using Belchertown skins. Easy
update - many thanks for all the work that's gone into this!

Cheers
Colin
41south.nz

On Fri, 1 May 2020 at 16:34, Greg from Oz  wrote:

> I just upgraded mine from 3.9.2 to 4 and it was OK.
> I had Steel series skin and that caused a problem but you just rename
> rainrate to rainRate in the skin and that was fixed.
> I also have Belechertown skin running so I downloaded the latest version
> and that worked as well.
> So it was fairly smooth upgrade and it is working.
>
> Good luck, you should be fine but backup if you are concerned.
>
>
> On Friday, 1 May 2020 14:23:05 UTC+10, Gert Andersen wrote:
>>
>> Hi
>>
>> I have version 3.9.2 running today. I'm a little unsure if I can update
>> to 4.0 by following the installation description or I need to delete
>> version 3.9.2 first and do a clean install of version 4.0. Have read
>> through the guide and can't really find anything about it. If I can update,
>> is there something to save, weewx.conf, weewx.dg, etc.
>>
>> Thank you very much for Weewx and the great work you do.
>>
>> Gert
>>
>> On Thursday, April 30, 2020 at 7:09:47 PM UTC+2, Tom Keffer wrote:
>>>
>>> After months of waiting, Version 4 has finally arrived! The major new
>>> feature is that WeeWX will not run under either Python 2 or Python 3.
>>>
>>> It took a long time to get the packaging right but now, thanks to
>>> Matthew Wall, WeeWX is easier than ever to install. Be sure to read the
>>> installation instructions for your specific operating system
>>> . As always, a setup.py install method is
>>> also supported.
>>>
>>> Generally, the package installers will use Python 3, if its available.
>>> On older systems, the installers will use Python 2.
>>>
>>>
>>> CHANGE LOG
>>> Ported to Python 3. WeeWX should now run under Python 3.5 and greater,
>>> as well
>>> as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.
>>>
>>> New facility for creating new user-defined derived types. See the Wiki
>>> article
>>> https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types
>>>
>>> WeeWX now uses the Python 'logging' facility. This means log, formats,
>>> and other
>>> things can now be customized. Fixes issue #353.
>>>
>>> Strings appearing in the data stream no longer cause a TypeError if they
>>> can be
>>> converted to a number.
>>>
>>> Strings can now be accumulated and extracted in the accumulators, making
>>> it
>>> possible to include them in the database schemas.
>>>
>>> The utility wee_reports now loads services, allowing it to use
>>> user-supplied
>>> extensions. Fixes issue #95.
>>>
>>> New default schema ("wview_extended") that offers many new types. The
>>> old schema
>>> is still supported. Fixes issue #115.
>>>
>>> Optional, more flexible, way of specifying schemas for the daily
>>> summaries. The
>>> old way is still supported.
>>>
>>> The install process now offers to register a user's station with
>>> weewx.com.
>>>
>>> The package MySQL-python, which we used previously, is not always
>>> available on
>>> Python 3. Ported the MySQL code to use the package mysqlclient as an
>>> alternative.
>>>
>>> The default for WOW no longer throttles posting frequency (the default
>>> used to
>>> be no more than once every 15 minutes).
>>>
>>> Added new aggregate types minsum, minsumtime, sum_le. PR #382.
>>>
>>> Unit group group_distance is now a first-class group.
>>>
>>> Added new tag $python_version.
>>>
>>> Ported to Python2-PyMySQL package on OpenSUSE.
>>>
>>> Added new aggregation types 'first' (similar to 'last'), 'diff' (the
>>> difference
>>> between last and first value in the aggregation interval), and 'tderiv'
>>> (the
>>> difference divided by the time difference).
>>>
>>> Created new unit group 'group_energy2', defined as watt-seconds. Useful
>>> for high
>>> resolution energy monitors.
>>>
>>> An observation type known to the system, but not in a record, will now
>>> return a
>>> proper ValueTuple, rather than UnknownType.
>>>
>>> Type "stormStart" was added to the unit system. Fixes issue #380.
>>>
>>> Added new aggregation type 'growdeg'. Similar to 'heatdeg', or
>>> 'cooldeg', it
>>> measures growing degree-days. Basically, cooldeg, but with a different
>>> base.
>>> Fixes issue #367. Thanks to user Clay Jackson for guidance!
>>>
>>> Ported OS uptime to OpenBSD. Fixes issue #428. Thanks to user Jeff Ross!
>>>
>>> Catch SSL certificate errors in uploaders. Retry after an hour. Fixes
>>> issue
>>> #413.
>>>
>>> Wunderfixer has been ported to the new WU API. This API requires an API
>>> key,
>>> which you can get from the WU. Put it in weewx.conf. Added option
>>> --upload-only.
>>> Thanks to user Leon Shaner! Fixes issues #414 and #445.
>>>
>>> Wee_import can now import Weather Display monthly log files.
>>>
>>> Fixed problem where sub-sections DegreeDays and Trend were located under
>>> the
>>> wrong weewx.conf section. Fixes issue #432. Thanks to user mph for
>>> 

Re: [weewx-user] Belchertown skin 1.1 released!

2020-04-08 Thread Colin Larsen
I think my last was 1.04 beta or such. Just looking at tweaking some
options now :)

On Thu, 9 Apr 2020 at 12:08, Pat  wrote:

> If you had a 1.1 beta version running then you may have already made a
> bunch of the changes you needed. Looks good on my end too!
>
> On Wednesday, April 8, 2020 at 7:40:52 PM UTC-4, Colin Larsen wrote:
>>
>> Whoops sorry - 41south.nz
>>
>> Colin
>>
>> On Thu, 9 Apr 2020 at 11:40, Colin Larsen  wrote:
>>
>>> Update done at 41south.net, as far as I can tell nothing broke and I
>>> haven't had to make any changes to graphs.conf - possibly I'm not using any
>>> of the changed options?
>>>
>>> Colin
>>>
>>> On Thu, 9 Apr 2020 at 08:18, Colin Larsen  wrote:
>>>
>>>> Thanks Pat, I'll tackle this sometime in the next few days after I have
>>>> a good read of the breaks ;)
>>>>
>>>> Cheers
>>>> Colin
>>>>
>>>> On Thu, 9 Apr 2020, 06:26 Pat,  wrote:
>>>>
>>>>> As mentioned in this thread
>>>>> <https://groups.google.com/forum/#!topic/weewx-user/m_47lX0fsIM>,
>>>>> I've released Belchertown skin 1.1. This will be the last skin that uses
>>>>> the DarkSky API for weather conditions and forecasts. I'm going to begin
>>>>> working on 1.2 soon to migrate to OpenWeatherMap.
>>>>>
>>>>> Read the entire release details here
>>>>> <https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.1>
>>>>>  which
>>>>> outline the breaking changes, new changes, items removed, etc.
>>>>>
>>>>> Always have a backup before you upgrade!
>>>>>
>>>>> Download:
>>>>>
>>>>> wget
>>>>> https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.1/weewx-belchertown-release-1.1.tar.gz
>>>>>
>>>>> Then run:
>>>>>
>>>>> sudo wee_extension --install weewx-belchertown-release-1.1.tar.gz
>>>>>
>>>>>
>>>>> Restart weewx when finished configuring.
>>>>>
>>>>>
>>>>> 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...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/weewx-user/b880b654-fe1f-4bf8-9dff-f8ef7fff54b3%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/b880b654-fe1f-4bf8-9dff-f8ef7fff54b3%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> --
> 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/434401fc-6e71-4b30-b36a-2c1e2adc5b8e%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/434401fc-6e71-4b30-b36a-2c1e2adc5b8e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUt6ABuHBLT38%2BrEqV2C25ezKBmGWa8fqrbNCRB3qO%2BTKQ%40mail.gmail.com.


Re: [weewx-user] Belchertown skin 1.1 released!

2020-04-08 Thread Colin Larsen
Whoops sorry - 41south.nz

Colin

On Thu, 9 Apr 2020 at 11:40, Colin Larsen  wrote:

> Update done at 41south.net, as far as I can tell nothing broke and I
> haven't had to make any changes to graphs.conf - possibly I'm not using any
> of the changed options?
>
> Colin
>
> On Thu, 9 Apr 2020 at 08:18, Colin Larsen  wrote:
>
>> Thanks Pat, I'll tackle this sometime in the next few days after I have a
>> good read of the breaks ;)
>>
>> Cheers
>> Colin
>>
>> On Thu, 9 Apr 2020, 06:26 Pat,  wrote:
>>
>>> As mentioned in this thread
>>> <https://groups.google.com/forum/#!topic/weewx-user/m_47lX0fsIM>, I've
>>> released Belchertown skin 1.1. This will be the last skin that uses the
>>> DarkSky API for weather conditions and forecasts. I'm going to begin
>>> working on 1.2 soon to migrate to OpenWeatherMap.
>>>
>>> Read the entire release details here
>>> <https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.1>
>>>  which
>>> outline the breaking changes, new changes, items removed, etc.
>>>
>>> Always have a backup before you upgrade!
>>>
>>> Download:
>>>
>>> wget
>>> https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.1/weewx-belchertown-release-1.1.tar.gz
>>>
>>> Then run:
>>>
>>> sudo wee_extension --install weewx-belchertown-release-1.1.tar.gz
>>>
>>>
>>> Restart weewx when finished configuring.
>>>
>>>
>>> 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/b880b654-fe1f-4bf8-9dff-f8ef7fff54b3%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/b880b654-fe1f-4bf8-9dff-f8ef7fff54b3%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/CACjxfUv6DHu1MVuZq4RQ8E0e92wX7t_qiK-FzC4mEMLuQdk%3DgQ%40mail.gmail.com.


Re: [weewx-user] Belchertown skin 1.1 released!

2020-04-08 Thread Colin Larsen
Update done at 41south.net, as far as I can tell nothing broke and I
haven't had to make any changes to graphs.conf - possibly I'm not using any
of the changed options?

Colin

On Thu, 9 Apr 2020 at 08:18, Colin Larsen  wrote:

> Thanks Pat, I'll tackle this sometime in the next few days after I have a
> good read of the breaks ;)
>
> Cheers
> Colin
>
> On Thu, 9 Apr 2020, 06:26 Pat,  wrote:
>
>> As mentioned in this thread
>> <https://groups.google.com/forum/#!topic/weewx-user/m_47lX0fsIM>, I've
>> released Belchertown skin 1.1. This will be the last skin that uses the
>> DarkSky API for weather conditions and forecasts. I'm going to begin
>> working on 1.2 soon to migrate to OpenWeatherMap.
>>
>> Read the entire release details here
>> <https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.1>
>>  which
>> outline the breaking changes, new changes, items removed, etc.
>>
>> Always have a backup before you upgrade!
>>
>> Download:
>>
>> wget
>> https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.1/weewx-belchertown-release-1.1.tar.gz
>>
>> Then run:
>>
>> sudo wee_extension --install weewx-belchertown-release-1.1.tar.gz
>>
>>
>> Restart weewx when finished configuring.
>>
>>
>> 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/b880b654-fe1f-4bf8-9dff-f8ef7fff54b3%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/b880b654-fe1f-4bf8-9dff-f8ef7fff54b3%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/CACjxfUvqr4uC6q00F3ZU97jRpBub0xyL-a8NcgwM8S-Vj0qO8A%40mail.gmail.com.


Re: [weewx-user] Re: Changes with Belchertown skin & DarkSky

2020-04-08 Thread Colin Larsen
Plan approved :) :)

But make sure you get some sleep too (and your good wife of course!)

Colin

On Thu, 9 Apr 2020, 03:52 G Hammer,  wrote:

> Sounds like a plan.
>
> On Wed, Apr 8, 2020, 10:31 AM Pat  wrote:
>
>> Think I'll release 1.1 as it stands right now as soon as I can, then work
>> on OWM as part of the update for 1.2 and retire DarkSky in the skin for 1.2.
>>
>>
>> On Tuesday, April 7, 2020 at 10:01:21 PM UTC-4, Xant wrote:
>>>
>>>
>>> Colin
>>>
>>> I honor that! And, indeed, brought a smile in my face! (we need that
>>> good humor spirit nowadays...)
>>>
>>> Either one is fine...
>>>
>>> BTW, Pat can not have a good night sleep he has a newborn...  :
>>>
>>> X
>>>
>>>
>>> On Tuesday, April 7, 2020 at 9:41:40 PM UTC-4, Colin Larsen wrote:
>>>>
>>>> If there is a vote going I like OWM :) Good luck with that sleep thing
>>>> pat!
>>>>
>>>> Cheers
>>>> Colin
>>>>
>>>> On Wed, 8 Apr 2020 at 13:32, G Hammer  wrote:
>>>>
>>>>> 3AM is a great time to introduce them to coding πŸ˜‰
>>>>>
>>>>> On Tue, Apr 7, 2020, 9:30 PM Pat  wrote:
>>>>>
>>>>>> Right. OWM is more of a drop in replacement so I'm leaning that way.
>>>>>>
>>>>>> Still, this all requires me to get some spare time and a full night's
>>>>>> sleep. Newborns aren't very cooperative with their parents hobbies :-)
>>>>>>
>>>>>> --
>>>>>> 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/m_47lX0fsIM/unsubscribe.
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> weewx...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/weewx-user/ae476015-8d47-4be0-87e6-20ed71685837%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/CALBRR-0%2B%3D%3DH2pmmDgVBH%2BhyD%2B-7UOP-_QAoWuwu3F9Eqr4zwiw%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/CALBRR-0%2B%3D%3DH2pmmDgVBH%2BhyD%2B-7UOP-_QAoWuwu3F9Eqr4zwiw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> --
>> 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/m_47lX0fsIM/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/5ab62903-2246-4009-ba93-361b242aee11%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/5ab62903-2246-4009-ba93-361b242aee11%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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/CALBRR-3d7YyudWGsnzfV19jgV6wWv8HdWYB1keUXOVxAt7hESg%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CALBRR-3d7YyudWGsnzfV19jgV6wWv8HdWYB1keUXOVxAt7hESg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACjxfUtqEcMWG%2BiCNiivdnAdUwcu-k0ut1Y%3DwDaYSAfkXw%3Divw%40mail.gmail.com.


Re: [weewx-user] Belchertown skin 1.1 released!

2020-04-08 Thread Colin Larsen
Thanks Pat, I'll tackle this sometime in the next few days after I have a
good read of the breaks ;)

Cheers
Colin

On Thu, 9 Apr 2020, 06:26 Pat,  wrote:

> As mentioned in this thread
> , I've
> released Belchertown skin 1.1. This will be the last skin that uses the
> DarkSky API for weather conditions and forecasts. I'm going to begin
> working on 1.2 soon to migrate to OpenWeatherMap.
>
> Read the entire release details here
> 
>  which
> outline the breaking changes, new changes, items removed, etc.
>
> Always have a backup before you upgrade!
>
> Download:
>
> wget
> https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.1/weewx-belchertown-release-1.1.tar.gz
>
> Then run:
>
> sudo wee_extension --install weewx-belchertown-release-1.1.tar.gz
>
>
> Restart weewx when finished configuring.
>
>
> 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/b880b654-fe1f-4bf8-9dff-f8ef7fff54b3%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/CACjxfUs0yy4JHYOM8tsq4CKPdeT0mvCdcud5r7RTG5UL36BOPQ%40mail.gmail.com.


Re: [weewx-user] Re: Changes with Belchertown skin & DarkSky

2020-04-07 Thread Colin Larsen
If there is a vote going I like OWM :) Good luck with that sleep thing pat!

Cheers
Colin

On Wed, 8 Apr 2020 at 13:32, G Hammer  wrote:

> 3AM is a great time to introduce them to coding πŸ˜‰
>
> On Tue, Apr 7, 2020, 9:30 PM Pat  wrote:
>
>> Right. OWM is more of a drop in replacement so I'm leaning that way.
>>
>> Still, this all requires me to get some spare time and a full night's
>> sleep. Newborns aren't very cooperative with their parents hobbies :-)
>>
>> --
>> 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/m_47lX0fsIM/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/ae476015-8d47-4be0-87e6-20ed71685837%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/CALBRR-0%2B%3D%3DH2pmmDgVBH%2BhyD%2B-7UOP-_QAoWuwu3F9Eqr4zwiw%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/CACjxfUv0aYSW2JqYt74nXeoeCr2Zs54fS0hop2Eay0%3DZ5i74Hg%40mail.gmail.com.


Re: [weewx-user] Changes with Belchertown skin & DarkSky

2020-03-31 Thread Colin Larsen
Congratulations Pat, trying times, hope you and are your family stay well

Colin

On Wed, 1 Apr 2020, 07:10 steeple ian,  wrote:

> Congratulations Pat
>
> On Tue, Mar 31, 2020 at 7:03 PM Pat  wrote:
>
>> Hi everyone, I'm a bit tied up and offline with the birth of my new
>> daughter, but I got news today that DarkSky has been acquired by Apple. For
>> existing API users, API will remain online until 2021, but they are not
>> accepting any new sign ups.
>>
>> That's the sad reality of using free hosted services - they can be shut
>> down without a moments notice.
>>
>> I'll research a new method for local conditions and forecasts. If anyone
>> knows of any that are free and has a public API, please let me know!
>>
>> ( Maybe it's a good thing I haven't released 1.1 yet! )
>>
>> --
>> 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/4cccd134-5baa-4657-9327-8070e2fb39d5%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/CADASSaTP%2ByPD8MdbJiZj_YKcKAko0MO4qbDYZdxWX8SP_yjTLQ%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/CACjxfUtEXi60xKRudnaGORJUrurnWtO%2BrP5h2jfoxGLUTq07Fg%40mail.gmail.com.


Re: [weewx-user] WeatherDuino - "trouble or fun"?

2019-08-21 Thread Colin Larsen
Hi Xant

If you like to build your own weather station equipment and tinker lots
then Weatherduino is a great system. It is Arduino based as the name
implies so a little experience in that area is good but not 100% necessary.
W'Duino is very very flexible but definitely not plug and play, if you want
that then Davis or similar is needed. Happy to offer further advice.

Colin

On Thu, 22 Aug 2019, 05:47 Xant,  wrote:

>
> Hi Colin
>
> Thank you for prompt reply (tried to directly, but no contact info on
> site... pls, consider).
>
> Davis is the "Cadillac" of PWS's, but at a price. Discovered WeatherDuino
> through your weewx site (which seems an interesting take). Please, share if
> "too much trouble", "too much time", or actually "fun" as to put all
> together.
>
> Best (from this side of the World),
> Xant
>
> --
> 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/59abdfa9-6354-4689-9802-1b39fff4a6e7%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/CACjxfUvj%2B0-TWrZ3GYgSn4X5Nbtz1Uwz64ioMeK1bf1oA1_H0Q%40mail.gmail.com.


Re: [weewx-user] WeatherDuino - "trouble or fun"?

2019-08-21 Thread Colin Larsen
That's my site, what would you like to know :)

Colin

On Thu, 22 Aug 2019, 05:18 Xant,  wrote:

>
> Does somebody went through WeatherDuino path?! (as in
> http://www.41south.net.nz/)
>
> https://wiki.weatherduino.com/
>
> Can share experience?
>
> Xant
>
> --
> 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/89f2a547-bb9e-4fe0-bf58-312aa433c37a%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/CACjxfUtbYr7UQRT2GM8dNR5t5D6u_un4LUz-b3hipWHMfE020w%40mail.gmail.com.


Re: [weewx-user] UV Index and radiation calculated by software

2019-06-28 Thread Colin Larsen
Weewx will calculate the maximum theoretical solar radiation value, but
this of course will bear no relation to your actual conditions.
I'm not sure about UV, but once again any such calculation would not relate
to your observed conditions.

Colin

On Fri, 28 Jun 2019, 20:47 Rolf Zanchettin,  wrote:

> Hi all,
>
> unfortunately my weather station does not have a UV and solar radiation
> sensor. Is it possible to calculate the values by weewx, based on lat/lng?
>
> Thanks in advance
> Best regards
> Rolf
>
> --
> 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/ff8d2bfc-1152-40d7-b294-cfeb9377290b%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUvWwRfmc8dDHzph-ykonaOQWuWfWRKoiYmSc2EJc_6tAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Error after upgrading to Belchertown skin 1.0.1

2019-06-26 Thread Colin Larsen
I'm not sure you have followed the upgrade instructions properly. Certainly
Highcharts_Belchertown is no longer required.
What version did you upgrade from?

Colin

On Thu, 27 Jun 2019, 07:46 G400,  wrote:

> After upgaring Belchertown 1.0.1 skin I'm struggeling with errors:
>
> I followed the recommended upgrade path as detailed on this page:
> https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0
>
> WeeWX is installed in /home/weewx
>
> Error messages after restarting weewx:
>
> Belchertown Extension: version 1.0.1
> reportengine: Caught unrecoverable exception in generator
> 'weewx.cheetahgenerator.CheetahGenerator'
>   Parsing failed with several errors.#012First error at line
> 29.
>   Traceback (most recent call last):
> File "/home/weewx/bin/weewx/reportengine.py", line 204, in
> run
>   obj.start()
> File "/home/weewx/bin/weewx/reportengine.py", line 300, in
> start
>   self.run()
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line
> 160, in run
>   ngen = self.generate(gen_dict[section_name], self.gen_ts)
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line
> 234, in generate
>   ngen += self.generate(section[subsection], gen_ts)
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line
> 234, in generate
>   ngen += self.generate(section[subsection], gen_ts)
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line
> 322, in generate
>   default_binding)
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line
> 374, in _getSearchList
>   searchList += obj.get_extension_list(timespan, db_lookup)
> File "/home/weewx/bin/user/belchertown.py", line 175, in
> get_extension_list
>   chart_dict = configobj.ConfigObj(chart_config_path,
> file_error=True)
> File "/usr/lib/python2.7/dist-packages/configobj.py", line
> 1229, in __init__
>   self._load(infile, configspec)
> File "/usr/lib/python2.7/dist-packages/configobj.py", line
> 1318, in _load
>   raise error
>   ConfigObjError: Parsing failed with several errors.
>   First error at line 29.
>   Generator terminated
>
> This is what I have in [StdReport] section:
>
>
>   [[Highcharts_Belchertown]]
> HTML_ROOT = /home/weewx/public_html/belchertown
> skin = Highcharts_Belchertown
> [[[Units]]]
>   Groups
>group_rain = mm
>group_altitude = meter
>
>
>
>group_pressure = mbar
>group_rainrate = mm_per_hour
>group_speed = meter_per_second
>group_speed2 = meter_per_second2
>group_temperature = degree_C
>group_degre_day = degree_C_day
>
> [[Belchertown]]
> HTML_ROOT = /home/weewx/public_html/belchertown
> skin = Belchertown
> [[[Extras]]]
> belchertown_root_url = "http://xxx";
> earthquake_enabled = 0
> twitter_enabled = 0
> footer_copyright_text = xx
> site_title = xx
> manifest_name = "xx"
> show_cloudbase = 1
> forecast_enabled = 1
> darksky_secret_key = xx
> darksky_units = si
> darksky_lang = no
>
> If I remove  [[Highcharts_Belchertown]] and   [[Belchertown]] I get no
> errors
>
> --
> 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/24b3f234-30d6-4554-8928-b2eb9d10f7b8%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUv__SGvuASgOCFZOfnuXgEwBM1_m%3D4ZT4cbktwVAjOSVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-14 Thread Colin Larsen
Great news :)

On Sat, 15 Jun 2019, 08:08 Maarten van der Hoeven, 
wrote:

> Back home, and now with full focus. All is working now! I have put
> everything in weewx.conf, nothing left in skin.conf
>
> Very cool
>
> Op vrijdag 14 juni 2019 11:03:11 UTC+2 schreef Colin Larsen:
>>
>> I did a test on my system and that label definitely works :)
>>
>> On Fri, Jun 14, 2019 at 8:19 PM Colin Larsen  wrote:
>>
>>> I think it would need a Weewx restart, again hopefully Pat can confirm I
>>> have the right spot.
>>>
>>> On Fri, 14 Jun 2019, 20:17 Maarten van der Hoeven, 
>>> wrote:
>>>
>>>> Thanks again Colin! I did a quick change, but didnt see the label being
>>>> changed at the website. Must have been doing something wrong, as being in a
>>>> hurry, work is calling. Will check this evening, and will also read the
>>>> wiki... As I understand correctly, there's pretty much howto's written down
>>>> how about howto's :)  Will follow up later today.
>>>>
>>>> Op vrijdag 14 juni 2019 09:36:28 UTC+2 schreef Colin Larsen:
>>>>>
>>>>> Probably just extraTemp1 = Grass Temperature or whatever you need
>>>>>
>>>>> On Fri, Jun 14, 2019 at 7:33 PM Colin Larsen 
>>>>> wrote:
>>>>>
>>>>>> This is it I think, add your desired label in here
>>>>>>
>>>>>> [Labels]
>>>>>> # Labels used in this skin
>>>>>> [[Generic]]
>>>>>> # Generic labels, keyed by an observation type.
>>>>>> # To change a label or translate it to your language
>>>>>> # change the text after the equal sign.
>>>>>> # Extra Observation labels
>>>>>> appTemp = Apparent Temperature
>>>>>> cloudbase = Cloud Base
>>>>>> visibility = Visibility
>>>>>> windrun = Wind Run
>>>>>>
>>>>>>
>>>>>> On Fri, Jun 14, 2019 at 7:30 PM Colin Larsen 
>>>>>> wrote:
>>>>>>
>>>>>>> Excellent! And yes I'm 99% sure that Temperature1 can be changed in
>>>>>>> either skin.conf or Weewx.conf. Don't forget to get all of your config
>>>>>>> settings into weewx.conf so they don't get overwritten by an update to
>>>>>>> skin.conf. Again it's in the Wiki. Let me go and look for that setting 
>>>>>>> to
>>>>>>> change :)
>>>>>>>
>>>>>>> On Fri, Jun 14, 2019 at 7:15 PM Maarten van der Hoeven <
>>>>>>> hoev...@gmail.com> wrote:
>>>>>>>
>>>>>>>> How cool is that! This is all too easy 😊
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Adding β€œextraTemp1” at the end of the mentioned line (in skin.conf)
>>>>>>>> did already the trick.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Barometer  1014.2 mbar
>>>>>>>>
>>>>>>>> Dew Point   13.8 Β°C
>>>>>>>>
>>>>>>>> Humidity 88%
>>>>>>>>
>>>>>>>> Rain   0.0 mm  0.0 mm/hr
>>>>>>>>
>>>>>>>> Temperature116.1 Β°C
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Amazing 😊 Now to find out where to change the label Temperature1
>>>>>>>> into something else (Temp grass or something alike).
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks for your help Colin.Op vrijdag 14 juni 2019 09:00:04 UTC+2
>>>>>>>> schreef Colin Larsen:
>>>>>>>>>
>>>>>>>>> Sorry, that formatted horribly I think - it's actually just on 2
>>>>>>>>> lines of code
>>>>>>>>>
>>>>>>>>> On Fri, Jun 14, 2019 at 6:59 PM Colin Larsen 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Maarten
>>>>>>>>>>
>>>>>>>>>> I think you may be able to add your extraTemp1 into th

Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-14 Thread Colin Larsen
I did a test on my system and that label definitely works :)

On Fri, Jun 14, 2019 at 8:19 PM Colin Larsen  wrote:

> I think it would need a Weewx restart, again hopefully Pat can confirm I
> have the right spot.
>
> On Fri, 14 Jun 2019, 20:17 Maarten van der Hoeven, 
> wrote:
>
>> Thanks again Colin! I did a quick change, but didnt see the label being
>> changed at the website. Must have been doing something wrong, as being in a
>> hurry, work is calling. Will check this evening, and will also read the
>> wiki... As I understand correctly, there's pretty much howto's written down
>> how about howto's :)  Will follow up later today.
>>
>> Op vrijdag 14 juni 2019 09:36:28 UTC+2 schreef Colin Larsen:
>>>
>>> Probably just extraTemp1 = Grass Temperature or whatever you need
>>>
>>> On Fri, Jun 14, 2019 at 7:33 PM Colin Larsen  wrote:
>>>
>>>> This is it I think, add your desired label in here
>>>>
>>>> [Labels]
>>>> # Labels used in this skin
>>>> [[Generic]]
>>>> # Generic labels, keyed by an observation type.
>>>> # To change a label or translate it to your language
>>>> # change the text after the equal sign.
>>>> # Extra Observation labels
>>>> appTemp = Apparent Temperature
>>>> cloudbase = Cloud Base
>>>> visibility = Visibility
>>>> windrun = Wind Run
>>>>
>>>>
>>>> On Fri, Jun 14, 2019 at 7:30 PM Colin Larsen 
>>>> wrote:
>>>>
>>>>> Excellent! And yes I'm 99% sure that Temperature1 can be changed in
>>>>> either skin.conf or Weewx.conf. Don't forget to get all of your config
>>>>> settings into weewx.conf so they don't get overwritten by an update to
>>>>> skin.conf. Again it's in the Wiki. Let me go and look for that setting to
>>>>> change :)
>>>>>
>>>>> On Fri, Jun 14, 2019 at 7:15 PM Maarten van der Hoeven <
>>>>> hoev...@gmail.com> wrote:
>>>>>
>>>>>> How cool is that! This is all too easy 😊
>>>>>>
>>>>>>
>>>>>>
>>>>>> Adding β€œextraTemp1” at the end of the mentioned line (in skin.conf)
>>>>>> did already the trick.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Barometer  1014.2 mbar
>>>>>>
>>>>>> Dew Point   13.8 Β°C
>>>>>>
>>>>>> Humidity 88%
>>>>>>
>>>>>> Rain   0.0 mm  0.0 mm/hr
>>>>>>
>>>>>> Temperature116.1 Β°C
>>>>>>
>>>>>>
>>>>>>
>>>>>> Amazing 😊 Now to find out where to change the label Temperature1
>>>>>> into something else (Temp grass or something alike).
>>>>>>
>>>>>>
>>>>>> Thanks for your help Colin.Op vrijdag 14 juni 2019 09:00:04 UTC+2
>>>>>> schreef Colin Larsen:
>>>>>>>
>>>>>>> Sorry, that formatted horribly I think - it's actually just on 2
>>>>>>> lines of code
>>>>>>>
>>>>>>> On Fri, Jun 14, 2019 at 6:59 PM Colin Larsen 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Maarten
>>>>>>>>
>>>>>>>> I think you may be able to add your extraTemp1 into this section
>>>>>>>> below in skin.conf/weewx.conf (depending on where you have the [Extras]
>>>>>>>> stanza). Give it a try, I'm sure Pat will jump in and correct me if I'm
>>>>>>>> wrong. Otherwise you may need to use one of the custom content areas as
>>>>>>>> described in the Wiki. Let us know how you get on :)
>>>>>>>>
>>>>>>>> # Station Observations. Special observation rainWithRainRate
>>>>>>>> combines Daily Rain with Rain Rate in 1 line station_observations =
>>>>>>>> "barometer", "dewpoint", "outHumidity", "rainWithRainRate
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Jun 14, 2019 at 6:46 PM Maarten van der Hoeven <
>>>>>>>> hoev...@gmail.com> wrote:
>>>>>>>>
>>>

Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-14 Thread Colin Larsen
I think it would need a Weewx restart, again hopefully Pat can confirm I
have the right spot.

On Fri, 14 Jun 2019, 20:17 Maarten van der Hoeven, 
wrote:

> Thanks again Colin! I did a quick change, but didnt see the label being
> changed at the website. Must have been doing something wrong, as being in a
> hurry, work is calling. Will check this evening, and will also read the
> wiki... As I understand correctly, there's pretty much howto's written down
> how about howto's :)  Will follow up later today.
>
> Op vrijdag 14 juni 2019 09:36:28 UTC+2 schreef Colin Larsen:
>>
>> Probably just extraTemp1 = Grass Temperature or whatever you need
>>
>> On Fri, Jun 14, 2019 at 7:33 PM Colin Larsen  wrote:
>>
>>> This is it I think, add your desired label in here
>>>
>>> [Labels]
>>> # Labels used in this skin
>>> [[Generic]]
>>> # Generic labels, keyed by an observation type.
>>> # To change a label or translate it to your language
>>> # change the text after the equal sign.
>>> # Extra Observation labels
>>> appTemp = Apparent Temperature
>>> cloudbase = Cloud Base
>>> visibility = Visibility
>>> windrun = Wind Run
>>>
>>>
>>> On Fri, Jun 14, 2019 at 7:30 PM Colin Larsen  wrote:
>>>
>>>> Excellent! And yes I'm 99% sure that Temperature1 can be changed in
>>>> either skin.conf or Weewx.conf. Don't forget to get all of your config
>>>> settings into weewx.conf so they don't get overwritten by an update to
>>>> skin.conf. Again it's in the Wiki. Let me go and look for that setting to
>>>> change :)
>>>>
>>>> On Fri, Jun 14, 2019 at 7:15 PM Maarten van der Hoeven <
>>>> hoev...@gmail.com> wrote:
>>>>
>>>>> How cool is that! This is all too easy 😊
>>>>>
>>>>>
>>>>>
>>>>> Adding β€œextraTemp1” at the end of the mentioned line (in skin.conf)
>>>>> did already the trick.
>>>>>
>>>>>
>>>>>
>>>>> Barometer  1014.2 mbar
>>>>>
>>>>> Dew Point   13.8 Β°C
>>>>>
>>>>> Humidity 88%
>>>>>
>>>>> Rain   0.0 mm  0.0 mm/hr
>>>>>
>>>>> Temperature116.1 Β°C
>>>>>
>>>>>
>>>>>
>>>>> Amazing 😊 Now to find out where to change the label Temperature1
>>>>> into something else (Temp grass or something alike).
>>>>>
>>>>>
>>>>> Thanks for your help Colin.Op vrijdag 14 juni 2019 09:00:04 UTC+2
>>>>> schreef Colin Larsen:
>>>>>>
>>>>>> Sorry, that formatted horribly I think - it's actually just on 2
>>>>>> lines of code
>>>>>>
>>>>>> On Fri, Jun 14, 2019 at 6:59 PM Colin Larsen 
>>>>>> wrote:
>>>>>>
>>>>>>> Maarten
>>>>>>>
>>>>>>> I think you may be able to add your extraTemp1 into this section
>>>>>>> below in skin.conf/weewx.conf (depending on where you have the [Extras]
>>>>>>> stanza). Give it a try, I'm sure Pat will jump in and correct me if I'm
>>>>>>> wrong. Otherwise you may need to use one of the custom content areas as
>>>>>>> described in the Wiki. Let us know how you get on :)
>>>>>>>
>>>>>>> # Station Observations. Special observation rainWithRainRate
>>>>>>> combines Daily Rain with Rain Rate in 1 line station_observations =
>>>>>>> "barometer", "dewpoint", "outHumidity", "rainWithRainRate
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Jun 14, 2019 at 6:46 PM Maarten van der Hoeven <
>>>>>>> hoev...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Thanks for the skin 1.0. Running without a flaw, and looking nice :)
>>>>>>>>
>>>>>>>> One question... I am using a second temperature sensor (temperature
>>>>>>>> on the grass, 10cm above the surface), data is stored in the database 
>>>>>>>> as
>>>>>>>> extraTemp1. What I understood from the wiki-chart, it

Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-14 Thread Colin Larsen
Probably just extraTemp1 = Grass Temperature or whatever you need

On Fri, Jun 14, 2019 at 7:33 PM Colin Larsen  wrote:

> This is it I think, add your desired label in here
>
> [Labels]
> # Labels used in this skin
> [[Generic]]
> # Generic labels, keyed by an observation type.
> # To change a label or translate it to your language
> # change the text after the equal sign.
> # Extra Observation labels
> appTemp = Apparent Temperature
> cloudbase = Cloud Base
> visibility = Visibility
> windrun = Wind Run
>
>
> On Fri, Jun 14, 2019 at 7:30 PM Colin Larsen 
> wrote:
>
>> Excellent! And yes I'm 99% sure that Temperature1 can be changed in
>> either skin.conf or Weewx.conf. Don't forget to get all of your config
>> settings into weewx.conf so they don't get overwritten by an update to
>> skin.conf. Again it's in the Wiki. Let me go and look for that setting to
>> change :)
>>
>> On Fri, Jun 14, 2019 at 7:15 PM Maarten van der Hoeven <
>> hoeve...@gmail.com> wrote:
>>
>>> How cool is that! This is all too easy 😊
>>>
>>>
>>>
>>> Adding β€œextraTemp1” at the end of the mentioned line (in skin.conf) did
>>> already the trick.
>>>
>>>
>>>
>>> Barometer  1014.2 mbar
>>>
>>> Dew Point   13.8 Β°C
>>>
>>> Humidity 88%
>>>
>>> Rain   0.0 mm  0.0 mm/hr
>>>
>>> Temperature116.1 Β°C
>>>
>>>
>>>
>>> Amazing 😊 Now to find out where to change the label Temperature1 into
>>> something else (Temp grass or something alike).
>>>
>>>
>>> Thanks for your help Colin.Op vrijdag 14 juni 2019 09:00:04 UTC+2
>>> schreef Colin Larsen:
>>>>
>>>> Sorry, that formatted horribly I think - it's actually just on 2 lines
>>>> of code
>>>>
>>>> On Fri, Jun 14, 2019 at 6:59 PM Colin Larsen 
>>>> wrote:
>>>>
>>>>> Maarten
>>>>>
>>>>> I think you may be able to add your extraTemp1 into this section below
>>>>> in skin.conf/weewx.conf (depending on where you have the [Extras] stanza).
>>>>> Give it a try, I'm sure Pat will jump in and correct me if I'm wrong.
>>>>> Otherwise you may need to use one of the custom content areas as described
>>>>> in the Wiki. Let us know how you get on :)
>>>>>
>>>>> # Station Observations. Special observation rainWithRainRate combines
>>>>> Daily Rain with Rain Rate in 1 line station_observations = "barometer",
>>>>> "dewpoint", "outHumidity", "rainWithRainRate
>>>>>
>>>>>
>>>>> On Fri, Jun 14, 2019 at 6:46 PM Maarten van der Hoeven <
>>>>> hoev...@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Thanks for the skin 1.0. Running without a flaw, and looking nice :)
>>>>>>
>>>>>> One question... I am using a second temperature sensor (temperature
>>>>>> on the grass, 10cm above the surface), data is stored in the database as
>>>>>> extraTemp1. What I understood from the wiki-chart, it should not be a
>>>>>> problem to plot this value (simply mention the database-field to plot).
>>>>>> However, I also want to show he value of this field on the webpage.
>>>>>>
>>>>>> What would be the correct and logical way to get this done? Although
>>>>>> I can hack around a bit and get it done, I  am wondering if there is a 
>>>>>> more
>>>>>> sophisticated approach to hook up this sensor-data in the data-stream and
>>>>>> to show it on the webpage. Or is all data already available in the
>>>>>> data-stream (MQTT), and is the question only how to show this value at 
>>>>>> the
>>>>>> website...
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Op zaterdag 1 juni 2019 18:57:56 UTC+2 schreef Pat:
>>>>>>>
>>>>>>> Belchertown skin 1.0 is released!
>>>>>>>
>>>>>>> This update contains a lot of updates and changes including *an
>>>>>>> entire rewrite of the Highcharts system* which allows you to make
>>>>>>> almost any graph you want for almost 

Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-14 Thread Colin Larsen
This is it I think, add your desired label in here

[Labels]
# Labels used in this skin
[[Generic]]
# Generic labels, keyed by an observation type.
# To change a label or translate it to your language
# change the text after the equal sign.
# Extra Observation labels
appTemp = Apparent Temperature
cloudbase = Cloud Base
visibility = Visibility
windrun = Wind Run


On Fri, Jun 14, 2019 at 7:30 PM Colin Larsen  wrote:

> Excellent! And yes I'm 99% sure that Temperature1 can be changed in either
> skin.conf or Weewx.conf. Don't forget to get all of your config settings
> into weewx.conf so they don't get overwritten by an update to skin.conf.
> Again it's in the Wiki. Let me go and look for that setting to change :)
>
> On Fri, Jun 14, 2019 at 7:15 PM Maarten van der Hoeven 
> wrote:
>
>> How cool is that! This is all too easy 😊
>>
>>
>>
>> Adding β€œextraTemp1” at the end of the mentioned line (in skin.conf) did
>> already the trick.
>>
>>
>>
>> Barometer  1014.2 mbar
>>
>> Dew Point   13.8 Β°C
>>
>> Humidity 88%
>>
>> Rain   0.0 mm  0.0 mm/hr
>>
>> Temperature116.1 Β°C
>>
>>
>>
>> Amazing 😊 Now to find out where to change the label Temperature1 into
>> something else (Temp grass or something alike).
>>
>>
>> Thanks for your help Colin.Op vrijdag 14 juni 2019 09:00:04 UTC+2
>> schreef Colin Larsen:
>>>
>>> Sorry, that formatted horribly I think - it's actually just on 2 lines
>>> of code
>>>
>>> On Fri, Jun 14, 2019 at 6:59 PM Colin Larsen  wrote:
>>>
>>>> Maarten
>>>>
>>>> I think you may be able to add your extraTemp1 into this section below
>>>> in skin.conf/weewx.conf (depending on where you have the [Extras] stanza).
>>>> Give it a try, I'm sure Pat will jump in and correct me if I'm wrong.
>>>> Otherwise you may need to use one of the custom content areas as described
>>>> in the Wiki. Let us know how you get on :)
>>>>
>>>> # Station Observations. Special observation rainWithRainRate combines
>>>> Daily Rain with Rain Rate in 1 line station_observations = "barometer",
>>>> "dewpoint", "outHumidity", "rainWithRainRate
>>>>
>>>>
>>>> On Fri, Jun 14, 2019 at 6:46 PM Maarten van der Hoeven <
>>>> hoev...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Thanks for the skin 1.0. Running without a flaw, and looking nice :)
>>>>>
>>>>> One question... I am using a second temperature sensor (temperature on
>>>>> the grass, 10cm above the surface), data is stored in the database as
>>>>> extraTemp1. What I understood from the wiki-chart, it should not be a
>>>>> problem to plot this value (simply mention the database-field to plot).
>>>>> However, I also want to show he value of this field on the webpage.
>>>>>
>>>>> What would be the correct and logical way to get this done? Although I
>>>>> can hack around a bit and get it done, I  am wondering if there is a more
>>>>> sophisticated approach to hook up this sensor-data in the data-stream and
>>>>> to show it on the webpage. Or is all data already available in the
>>>>> data-stream (MQTT), and is the question only how to show this value at the
>>>>> website...
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Op zaterdag 1 juni 2019 18:57:56 UTC+2 schreef Pat:
>>>>>>
>>>>>> Belchertown skin 1.0 is released!
>>>>>>
>>>>>> This update contains a lot of updates and changes including *an
>>>>>> entire rewrite of the Highcharts system* which allows you to make
>>>>>> almost any graph you want for almost any time span you want. You can see
>>>>>> some examples of the charts you can make on the BelchertownWeather.com
>>>>>> website graphs page
>>>>>> <https://belchertownweather.com/graphs/?graph=all>.
>>>>>>
>>>>>> You can add/remove/change/reorder any chart, change colors, add
>>>>>> observation plots, categorize for all time. Almost anything you want to 
>>>>>> do
>>>>>> is available! The skin comes with the standard 4 charts ready to go, but
>>>>>> there's extensive Bel

Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-14 Thread Colin Larsen
Excellent! And yes I'm 99% sure that Temperature1 can be changed in either
skin.conf or Weewx.conf. Don't forget to get all of your config settings
into weewx.conf so they don't get overwritten by an update to skin.conf.
Again it's in the Wiki. Let me go and look for that setting to change :)

On Fri, Jun 14, 2019 at 7:15 PM Maarten van der Hoeven 
wrote:

> How cool is that! This is all too easy 😊
>
>
>
> Adding β€œextraTemp1” at the end of the mentioned line (in skin.conf) did
> already the trick.
>
>
>
> Barometer  1014.2 mbar
>
> Dew Point   13.8 Β°C
>
> Humidity 88%
>
> Rain   0.0 mm  0.0 mm/hr
>
> Temperature116.1 Β°C
>
>
>
> Amazing 😊 Now to find out where to change the label Temperature1 into
> something else (Temp grass or something alike).
>
>
> Thanks for your help Colin.Op vrijdag 14 juni 2019 09:00:04 UTC+2 schreef
> Colin Larsen:
>>
>> Sorry, that formatted horribly I think - it's actually just on 2 lines of
>> code
>>
>> On Fri, Jun 14, 2019 at 6:59 PM Colin Larsen  wrote:
>>
>>> Maarten
>>>
>>> I think you may be able to add your extraTemp1 into this section below
>>> in skin.conf/weewx.conf (depending on where you have the [Extras] stanza).
>>> Give it a try, I'm sure Pat will jump in and correct me if I'm wrong.
>>> Otherwise you may need to use one of the custom content areas as described
>>> in the Wiki. Let us know how you get on :)
>>>
>>> # Station Observations. Special observation rainWithRainRate combines
>>> Daily Rain with Rain Rate in 1 line station_observations = "barometer",
>>> "dewpoint", "outHumidity", "rainWithRainRate
>>>
>>>
>>> On Fri, Jun 14, 2019 at 6:46 PM Maarten van der Hoeven <
>>> hoev...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Thanks for the skin 1.0. Running without a flaw, and looking nice :)
>>>>
>>>> One question... I am using a second temperature sensor (temperature on
>>>> the grass, 10cm above the surface), data is stored in the database as
>>>> extraTemp1. What I understood from the wiki-chart, it should not be a
>>>> problem to plot this value (simply mention the database-field to plot).
>>>> However, I also want to show he value of this field on the webpage.
>>>>
>>>> What would be the correct and logical way to get this done? Although I
>>>> can hack around a bit and get it done, I  am wondering if there is a more
>>>> sophisticated approach to hook up this sensor-data in the data-stream and
>>>> to show it on the webpage. Or is all data already available in the
>>>> data-stream (MQTT), and is the question only how to show this value at the
>>>> website...
>>>>
>>>> Thanks.
>>>>
>>>> Op zaterdag 1 juni 2019 18:57:56 UTC+2 schreef Pat:
>>>>>
>>>>> Belchertown skin 1.0 is released!
>>>>>
>>>>> This update contains a lot of updates and changes including *an
>>>>> entire rewrite of the Highcharts system* which allows you to make
>>>>> almost any graph you want for almost any time span you want. You can see
>>>>> some examples of the charts you can make on the BelchertownWeather.com
>>>>> website graphs page <https://belchertownweather.com/graphs/?graph=all>
>>>>> .
>>>>>
>>>>> You can add/remove/change/reorder any chart, change colors, add
>>>>> observation plots, categorize for all time. Almost anything you want to do
>>>>> is available! The skin comes with the standard 4 charts ready to go, but
>>>>> there's extensive Belchertown Charts Documentation
>>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>
>>>>> which can help you get started.
>>>>>
>>>>> In addition to the Charts there's now a dark mode (which has an
>>>>> auto-switching mode based on sunset/sunrise), more flexibility for
>>>>> translations, user customized station observation table which is updated 
>>>>> in
>>>>> real time if the MQTT Websockets are enabled, and a lot more. Check the
>>>>> release notes for all the details!
>>>>>
>>>>> You can download the latest release here
>>>>> <https://github.com/poblabs/weewx-belchertown/r

Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-14 Thread Colin Larsen
Sorry, that formatted horribly I think - it's actually just on 2 lines of
code

On Fri, Jun 14, 2019 at 6:59 PM Colin Larsen  wrote:

> Maarten
>
> I think you may be able to add your extraTemp1 into this section below in
> skin.conf/weewx.conf (depending on where you have the [Extras] stanza).
> Give it a try, I'm sure Pat will jump in and correct me if I'm wrong.
> Otherwise you may need to use one of the custom content areas as described
> in the Wiki. Let us know how you get on :)
>
> # Station Observations. Special observation rainWithRainRate combines
> Daily Rain with Rain Rate in 1 line station_observations = "barometer",
> "dewpoint", "outHumidity", "rainWithRainRate
>
>
> On Fri, Jun 14, 2019 at 6:46 PM Maarten van der Hoeven 
> wrote:
>
>> Hi,
>>
>> Thanks for the skin 1.0. Running without a flaw, and looking nice :)
>>
>> One question... I am using a second temperature sensor (temperature on
>> the grass, 10cm above the surface), data is stored in the database as
>> extraTemp1. What I understood from the wiki-chart, it should not be a
>> problem to plot this value (simply mention the database-field to plot).
>> However, I also want to show he value of this field on the webpage.
>>
>> What would be the correct and logical way to get this done? Although I
>> can hack around a bit and get it done, I  am wondering if there is a more
>> sophisticated approach to hook up this sensor-data in the data-stream and
>> to show it on the webpage. Or is all data already available in the
>> data-stream (MQTT), and is the question only how to show this value at the
>> website...
>>
>> Thanks.
>>
>> Op zaterdag 1 juni 2019 18:57:56 UTC+2 schreef Pat:
>>>
>>> Belchertown skin 1.0 is released!
>>>
>>> This update contains a lot of updates and changes including *an entire
>>> rewrite of the Highcharts system* which allows you to make almost any
>>> graph you want for almost any time span you want. You can see some examples
>>> of the charts you can make on the BelchertownWeather.com website graphs
>>> page <https://belchertownweather.com/graphs/?graph=all>.
>>>
>>> You can add/remove/change/reorder any chart, change colors, add
>>> observation plots, categorize for all time. Almost anything you want to do
>>> is available! The skin comes with the standard 4 charts ready to go, but
>>> there's extensive Belchertown Charts Documentation
>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>
>>> which can help you get started.
>>>
>>> In addition to the Charts there's now a dark mode (which has an
>>> auto-switching mode based on sunset/sunrise), more flexibility for
>>> translations, user customized station observation table which is updated in
>>> real time if the MQTT Websockets are enabled, and a lot more. Check the
>>> release notes for all the details!
>>>
>>> You can download the latest release here
>>> <https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.0/weewx-belchertown-release-1.0.tar.gz>,
>>> and read all of the details on the changes here:
>>> https://github.com/poblabs/weewx-belchertown/releases
>>>
>>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must
>>> uninstall everything and reinstall new. This is due to the Chart system
>>> being fully rewritten and the potential for conflicts. Please read this
>>> upgrade guide if you are upgrading from an older version of Belchertown skin
>>> <https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0>
>>> .
>>>
>>> Thanks to all the beta testers and translators over the last couple of
>>> months help me iron out all the kinks and shape the skin in a way that can
>>> be translated a little easier!
>>>
>>> Attached are some examples of the charts that can be made. If you find
>>> any issues, you can reply here or open an issue on the Belchertown skin
>>> GitHub page <https://github.com/poblabs/weewx-belchertown>.
>>>
>> --
>> 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/e84dcbf2-2174-4032-83a7-93c738e6c4ec%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/e84dcbf2-2174-4032-83a7-93c738e6c4ec%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUtEjEm69QYMeTJ4TPVFpfha1%2BganDbSN2D-GX5AYB5zMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-13 Thread Colin Larsen
Maarten

I think you may be able to add your extraTemp1 into this section below in
skin.conf/weewx.conf (depending on where you have the [Extras] stanza).
Give it a try, I'm sure Pat will jump in and correct me if I'm wrong.
Otherwise you may need to use one of the custom content areas as described
in the Wiki. Let us know how you get on :)

# Station Observations. Special observation rainWithRainRate combines Daily
Rain with Rain Rate in 1 line station_observations = "barometer",
"dewpoint", "outHumidity", "rainWithRainRate


On Fri, Jun 14, 2019 at 6:46 PM Maarten van der Hoeven 
wrote:

> Hi,
>
> Thanks for the skin 1.0. Running without a flaw, and looking nice :)
>
> One question... I am using a second temperature sensor (temperature on the
> grass, 10cm above the surface), data is stored in the database as
> extraTemp1. What I understood from the wiki-chart, it should not be a
> problem to plot this value (simply mention the database-field to plot).
> However, I also want to show he value of this field on the webpage.
>
> What would be the correct and logical way to get this done? Although I can
> hack around a bit and get it done, I  am wondering if there is a more
> sophisticated approach to hook up this sensor-data in the data-stream and
> to show it on the webpage. Or is all data already available in the
> data-stream (MQTT), and is the question only how to show this value at the
> website...
>
> Thanks.
>
> Op zaterdag 1 juni 2019 18:57:56 UTC+2 schreef Pat:
>>
>> Belchertown skin 1.0 is released!
>>
>> This update contains a lot of updates and changes including *an entire
>> rewrite of the Highcharts system* which allows you to make almost any
>> graph you want for almost any time span you want. You can see some examples
>> of the charts you can make on the BelchertownWeather.com website graphs
>> page .
>>
>> You can add/remove/change/reorder any chart, change colors, add
>> observation plots, categorize for all time. Almost anything you want to do
>> is available! The skin comes with the standard 4 charts ready to go, but
>> there's extensive Belchertown Charts Documentation
>> 
>> which can help you get started.
>>
>> In addition to the Charts there's now a dark mode (which has an
>> auto-switching mode based on sunset/sunrise), more flexibility for
>> translations, user customized station observation table which is updated in
>> real time if the MQTT Websockets are enabled, and a lot more. Check the
>> release notes for all the details!
>>
>> You can download the latest release here
>> ,
>> and read all of the details on the changes here:
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must
>> uninstall everything and reinstall new. This is due to the Chart system
>> being fully rewritten and the potential for conflicts. Please read this
>> upgrade guide if you are upgrading from an older version of Belchertown skin
>> 
>> .
>>
>> Thanks to all the beta testers and translators over the last couple of
>> months help me iron out all the kinks and shape the skin in a way that can
>> be translated a little easier!
>>
>> Attached are some examples of the charts that can be made. If you find
>> any issues, you can reply here or open an issue on the Belchertown skin
>> GitHub page .
>>
> --
> 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/e84dcbf2-2174-4032-83a7-93c738e6c4ec%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUuBvDKYurEftDCtcbfvXgNviQKC_TbSac7xLpWrJ%2B9j_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-07 Thread Colin Larsen
Happy to help - it's pretty warm there!

On Sat, 8 Jun 2019, 17:32 Adnan Mumtaz,  wrote:

> Thanks a lot Colin, it worked.
>
> On Saturday, 8 June 2019 08:08:12 UTC+3, Colin Larsen wrote:
>>
>> Adnan, look for a line in your skin.conf/weewx.conf (depending on where
>> you have things specified) like this one. Add observations in the order
>> that you like to see them
>>
>> station_observations = barometer, dewpoint, outHumidity, cloudbase,
>> rainWithRainRate, UV, radiation
>>
>>
>>
>>
>>
>> On Sat, Jun 8, 2019 at 4:37 PM Adnan Mumtaz  wrote:
>>
>>> Hi,
>>>
>>> Superb looking skin, thanks a lot Pat. I was able to upgrade it,
>>> everything is working fine except for some reason the following are not
>>> appearing on the main page
>>>
>>> Visibility
>>> Cloud Base
>>> UV Index
>>> Radiation
>>>
>>> http://www.riyadhweather.com/
>>>
>>> On Saturday, 1 June 2019 19:57:56 UTC+3, Pat wrote:
>>>>
>>>> Belchertown skin 1.0 is released!
>>>>
>>>> This update contains a lot of updates and changes including *an entire
>>>> rewrite of the Highcharts system* which allows you to make almost any
>>>> graph you want for almost any time span you want. You can see some examples
>>>> of the charts you can make on the BelchertownWeather.com website
>>>> graphs page <https://belchertownweather.com/graphs/?graph=all>.
>>>>
>>>> You can add/remove/change/reorder any chart, change colors, add
>>>> observation plots, categorize for all time. Almost anything you want to do
>>>> is available! The skin comes with the standard 4 charts ready to go, but
>>>> there's extensive Belchertown Charts Documentation
>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>
>>>> which can help you get started.
>>>>
>>>> In addition to the Charts there's now a dark mode (which has an
>>>> auto-switching mode based on sunset/sunrise), more flexibility for
>>>> translations, user customized station observation table which is updated in
>>>> real time if the MQTT Websockets are enabled, and a lot more. Check the
>>>> release notes for all the details!
>>>>
>>>> You can download the latest release here
>>>> <https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.0/weewx-belchertown-release-1.0.tar.gz>,
>>>> and read all of the details on the changes here:
>>>> https://github.com/poblabs/weewx-belchertown/releases
>>>>
>>>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must
>>>> uninstall everything and reinstall new. This is due to the Chart system
>>>> being fully rewritten and the potential for conflicts. Please read
>>>> this upgrade guide if you are upgrading from an older version of
>>>> Belchertown skin
>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0>
>>>> .
>>>>
>>>> Thanks to all the beta testers and translators over the last couple of
>>>> months help me iron out all the kinks and shape the skin in a way that can
>>>> be translated a little easier!
>>>>
>>>> Attached are some examples of the charts that can be made. If you find
>>>> any issues, you can reply here or open an issue on the Belchertown
>>>> skin GitHub page <https://github.com/poblabs/weewx-belchertown>.
>>>>
>>> --
>>> 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/a6b80885-b537-4114-9a3d-3ae697a28e38%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/a6b80885-b537-4114-9a3d-3ae697a28e38%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4ad77290-4ebf-41a8-bcff-791a895857ac%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/4ad77290-4ebf-41a8-bcff-791a895857ac%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUvS3-nSoxTo5G7Wm9RPJGb3mHDP4yL1A5r7TcsCu_MY5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Re: Belchertown skin 1.0 released!

2019-06-07 Thread Colin Larsen
Adnan, look for a line in your skin.conf/weewx.conf (depending on where you
have things specified) like this one. Add observations in the order that
you like to see them

station_observations = barometer, dewpoint, outHumidity, cloudbase,
rainWithRainRate, UV, radiation





On Sat, Jun 8, 2019 at 4:37 PM Adnan Mumtaz  wrote:

> Hi,
>
> Superb looking skin, thanks a lot Pat. I was able to upgrade it,
> everything is working fine except for some reason the following are not
> appearing on the main page
>
> Visibility
> Cloud Base
> UV Index
> Radiation
>
> http://www.riyadhweather.com/
>
> On Saturday, 1 June 2019 19:57:56 UTC+3, Pat wrote:
>>
>> Belchertown skin 1.0 is released!
>>
>> This update contains a lot of updates and changes including *an entire
>> rewrite of the Highcharts system* which allows you to make almost any
>> graph you want for almost any time span you want. You can see some examples
>> of the charts you can make on the BelchertownWeather.com website graphs
>> page .
>>
>> You can add/remove/change/reorder any chart, change colors, add
>> observation plots, categorize for all time. Almost anything you want to do
>> is available! The skin comes with the standard 4 charts ready to go, but
>> there's extensive Belchertown Charts Documentation
>> 
>> which can help you get started.
>>
>> In addition to the Charts there's now a dark mode (which has an
>> auto-switching mode based on sunset/sunrise), more flexibility for
>> translations, user customized station observation table which is updated in
>> real time if the MQTT Websockets are enabled, and a lot more. Check the
>> release notes for all the details!
>>
>> You can download the latest release here
>> ,
>> and read all of the details on the changes here:
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must
>> uninstall everything and reinstall new. This is due to the Chart system
>> being fully rewritten and the potential for conflicts. Please read this
>> upgrade guide if you are upgrading from an older version of Belchertown skin
>> 
>> .
>>
>> Thanks to all the beta testers and translators over the last couple of
>> months help me iron out all the kinks and shape the skin in a way that can
>> be translated a little easier!
>>
>> Attached are some examples of the charts that can be made. If you find
>> any issues, you can reply here or open an issue on the Belchertown skin
>> GitHub page .
>>
> --
> 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/a6b80885-b537-4114-9a3d-3ae697a28e38%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUuG_X%3DswveV4%2Bo-qDLzg53UMmdKPCqyqU2uQsi_cFTeiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Re: Is There an Alternative to Windy for Embed in Belchertown Skin

2019-05-17 Thread Colin Larsen
Also just a thought, there is a switch in the Windy API to force the units,
but I would have thought it was in the generated link too. I'll see if I
can fish it out but I know it's documented on the Windy website somewhere

On Sat, 18 May 2019, 07:13 G Hammer,  wrote:

> I understand that the embed configuration indicates you can choose how to
> display wind and temperature.
> The temperature never shows any but metric no matter what I choose in the
> setup. See image step-01
> Rain is always in mm, wind however does show mph. See image step-02
>
> What I mean by 'clicking the label' is, for example, click the C next to
> Temperature and it should change to F. That applies to any of the data
> displayed, Rain Wind Wind Gusts
> This also only works with Wind.
>
> Are these Windy problems? Yes. Which is why I wanted to know if anyone had
> a different radar display they like.
>
>
>
> On Friday, May 17, 2019 at 2:23:48 PM UTC-4, Colin Larsen wrote:
>>
>> As was pointed out this map is highly configurable via Windy.com, just
>> decide what you information you want and paste the link into the
>> appropriate conf file. Otherwise you may of course change the link to any
>> other source you like too.
>> Can you post an example of what you mean by "clicking the label"
>>
>> On Sat, 18 May 2019, 06:17 G Hammer,  wrote:
>>
>>> The radar map.
>>>
>>> On Fri, May 17, 2019 at 2:16 PM Colin Larsen  wrote:
>>>
>>>> Are you wanting to change the map picture or the 8 day forecast?
>>>>
>>>> On Sat, 18 May 2019, 02:34 G Hammer,  wrote:
>>>>
>>>>> Except that doesn’t work.
>>>>>
>>>>> On Fri, May 17, 2019 at 10:33 AM HoracioDos  wrote:
>>>>>
>>>>>> Hello.
>>>>>> Windy iframe designer allows to change wind and temperature units to
>>>>>> F and mph. This is the link
>>>>>> https://www.windy.com/-Embed-widget-on-page/widgets?
>>>>>> Then you can generate the iframe code that suits you and paste in
>>>>>> radar_html keyword
>>>>>>
>>>>>> On Friday, May 17, 2019 at 10:04:59 AM UTC-3, G Hammer wrote:
>>>>>>>
>>>>>>> I use and like the Belchertown skin.
>>>>>>> I like the Windy.com website and the app on my mobile.
>>>>>>>
>>>>>>> I do not care for the embed, it only shows metric values and
>>>>>>> clicking the label does not change this as it should.
>>>>>>>
>>>>>>> So, any favorite to replace the Windy embed?
>>>>>>>
>>>>>>> --
>>>>>> 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/Gt0v5Tf79T4/unsubscribe.
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> weewx...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/weewx-user/0eef6966-de3b-4371-912c-12b40ab4cf29%40googlegroups.com
>>>>>> <https://groups.google.com/d/msgid/weewx-user/0eef6966-de3b-4371-912c-12b40ab4cf29%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>> 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...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/weewx-user/CALBRR-0Aq28qXUfxUs1pwq1-Zhqteu%2BasgON0Nd75oam6fP7qQ%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/CALBRR-0Aq28qXUfxUs1pwq1-Zhqteu%2BasgON0Nd75oam6fP7qQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> 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 un

Re: [weewx-user] Re: Is There an Alternative to Windy for Embed in Belchertown Skin

2019-05-17 Thread Colin Larsen
Ok I see what you mean, I'm going to have a play and see if it's working
for me or not. I use metric anyway, but I'm sure many others use US units
with degrees F and wind mph etc. Does the copy and paste of the generated
link have a problem? Have you looked at that just in a browser, outside of
the skin?

On Sat, 18 May 2019, 07:13 G Hammer,  wrote:

> I understand that the embed configuration indicates you can choose how to
> display wind and temperature.
> The temperature never shows any but metric no matter what I choose in the
> setup. See image step-01
> Rain is always in mm, wind however does show mph. See image step-02
>
> What I mean by 'clicking the label' is, for example, click the C next to
> Temperature and it should change to F. That applies to any of the data
> displayed, Rain Wind Wind Gusts
> This also only works with Wind.
>
> Are these Windy problems? Yes. Which is why I wanted to know if anyone had
> a different radar display they like.
>
>
>
> On Friday, May 17, 2019 at 2:23:48 PM UTC-4, Colin Larsen wrote:
>>
>> As was pointed out this map is highly configurable via Windy.com, just
>> decide what you information you want and paste the link into the
>> appropriate conf file. Otherwise you may of course change the link to any
>> other source you like too.
>> Can you post an example of what you mean by "clicking the label"
>>
>> On Sat, 18 May 2019, 06:17 G Hammer,  wrote:
>>
>>> The radar map.
>>>
>>> On Fri, May 17, 2019 at 2:16 PM Colin Larsen  wrote:
>>>
>>>> Are you wanting to change the map picture or the 8 day forecast?
>>>>
>>>> On Sat, 18 May 2019, 02:34 G Hammer,  wrote:
>>>>
>>>>> Except that doesn’t work.
>>>>>
>>>>> On Fri, May 17, 2019 at 10:33 AM HoracioDos  wrote:
>>>>>
>>>>>> Hello.
>>>>>> Windy iframe designer allows to change wind and temperature units to
>>>>>> F and mph. This is the link
>>>>>> https://www.windy.com/-Embed-widget-on-page/widgets?
>>>>>> Then you can generate the iframe code that suits you and paste in
>>>>>> radar_html keyword
>>>>>>
>>>>>> On Friday, May 17, 2019 at 10:04:59 AM UTC-3, G Hammer wrote:
>>>>>>>
>>>>>>> I use and like the Belchertown skin.
>>>>>>> I like the Windy.com website and the app on my mobile.
>>>>>>>
>>>>>>> I do not care for the embed, it only shows metric values and
>>>>>>> clicking the label does not change this as it should.
>>>>>>>
>>>>>>> So, any favorite to replace the Windy embed?
>>>>>>>
>>>>>>> --
>>>>>> 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/Gt0v5Tf79T4/unsubscribe.
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> weewx...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/weewx-user/0eef6966-de3b-4371-912c-12b40ab4cf29%40googlegroups.com
>>>>>> <https://groups.google.com/d/msgid/weewx-user/0eef6966-de3b-4371-912c-12b40ab4cf29%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>> 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...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/weewx-user/CALBRR-0Aq28qXUfxUs1pwq1-Zhqteu%2BasgON0Nd75oam6fP7qQ%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/CALBRR-0Aq28qXUfxUs1pwq1-Zhqteu%2BasgON0Nd75oam6fP7qQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> --
>>>> You received this message because you are subscribed to a topic in the
&g

Re: [weewx-user] Re: Is There an Alternative to Windy for Embed in Belchertown Skin

2019-05-17 Thread Colin Larsen
As was pointed out this map is highly configurable via Windy.com, just
decide what you information you want and paste the link into the
appropriate conf file. Otherwise you may of course change the link to any
other source you like too.
Can you post an example of what you mean by "clicking the label"

On Sat, 18 May 2019, 06:17 G Hammer,  wrote:

> The radar map.
>
> On Fri, May 17, 2019 at 2:16 PM Colin Larsen 
> wrote:
>
>> Are you wanting to change the map picture or the 8 day forecast?
>>
>> On Sat, 18 May 2019, 02:34 G Hammer,  wrote:
>>
>>> Except that doesn’t work.
>>>
>>> On Fri, May 17, 2019 at 10:33 AM HoracioDos  wrote:
>>>
>>>> Hello.
>>>> Windy iframe designer allows to change wind and temperature units to F
>>>> and mph. This is the link
>>>> https://www.windy.com/-Embed-widget-on-page/widgets?
>>>> Then you can generate the iframe code that suits you and paste in
>>>> radar_html keyword
>>>>
>>>> On Friday, May 17, 2019 at 10:04:59 AM UTC-3, G Hammer wrote:
>>>>>
>>>>> I use and like the Belchertown skin.
>>>>> I like the Windy.com website and the app on my mobile.
>>>>>
>>>>> I do not care for the embed, it only shows metric values and clicking
>>>>> the label does not change this as it should.
>>>>>
>>>>> So, any favorite to replace the Windy embed?
>>>>>
>>>>> --
>>>> 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/Gt0v5Tf79T4/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/0eef6966-de3b-4371-912c-12b40ab4cf29%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/0eef6966-de3b-4371-912c-12b40ab4cf29%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/CALBRR-0Aq28qXUfxUs1pwq1-Zhqteu%2BasgON0Nd75oam6fP7qQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/weewx-user/CALBRR-0Aq28qXUfxUs1pwq1-Zhqteu%2BasgON0Nd75oam6fP7qQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> 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/Gt0v5Tf79T4/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/CACjxfUsdf2cyvRUsZAeSWjc%3DX-yZBzKXn0UFcBvCivmOY0emxA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CACjxfUsdf2cyvRUsZAeSWjc%3DX-yZBzKXn0UFcBvCivmOY0emxA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CALBRR-30t0-QcvqF3t9fH%3DEHgoOdCZDcmweRCxYxH0JVYxg5cg%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CALBRR-30t0-QcvqF3t9fH%3DEHgoOdCZDcmweRCxYxH0JVYxg5cg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUsBpWocOEpCBUTvGDe7vc9JTzYYJFU2-JGdrQA1Va39Lg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Re: Is There an Alternative to Windy for Embed in Belchertown Skin

2019-05-17 Thread Colin Larsen
Are you wanting to change the map picture or the 8 day forecast?

On Sat, 18 May 2019, 02:34 G Hammer,  wrote:

> Except that doesn’t work.
>
> On Fri, May 17, 2019 at 10:33 AM HoracioDos  wrote:
>
>> Hello.
>> Windy iframe designer allows to change wind and temperature units to F
>> and mph. This is the link
>> https://www.windy.com/-Embed-widget-on-page/widgets?
>> Then you can generate the iframe code that suits you and paste in
>> radar_html keyword
>>
>> On Friday, May 17, 2019 at 10:04:59 AM UTC-3, G Hammer wrote:
>>>
>>> I use and like the Belchertown skin.
>>> I like the Windy.com website and the app on my mobile.
>>>
>>> I do not care for the embed, it only shows metric values and clicking
>>> the label does not change this as it should.
>>>
>>> So, any favorite to replace the Windy embed?
>>>
>>> --
>> 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/Gt0v5Tf79T4/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/0eef6966-de3b-4371-912c-12b40ab4cf29%40googlegroups.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CALBRR-0Aq28qXUfxUs1pwq1-Zhqteu%2BasgON0Nd75oam6fP7qQ%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUsdf2cyvRUsZAeSWjc%3DX-yZBzKXn0UFcBvCivmOY0emxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[weewx-user] Re: Another FilePile question

2019-05-12 Thread Colin Larsen
I finally managed to wrap my head around this I think (well it's working!)
I looked back at an email I'd seen about this recently and this is the
result that I have in my filepile.py. The bit I couldn't wrap my head
around until just now was the link between defining the groups and units
and connecting them to the database recordings - which was this

weewx.units.obs_group_dict[*'AQI25'*] = *'group_dust'*

weewx.units.obs_group_dict[*'AQI100'*] = *'group_dust'*

weewx.units.obs_group_dict[*'AQICO2'*] = *'group_gas_concentration'*


Anyway problem solved, hopefully this is the right place for it?

*import* syslog

*import* weewx

*import* weewx.units

*from* weewx.wxengine *import* StdService

*from* weeutil.weeutil *import* to_float


weewx.units.USUnits[*'group_gas_concentration'*] = *'ppm'*

weewx.units.MetricUnits[*'group_gas_concentration'*] = *'ppm'*

weewx.units.MetricWXUnits[*'group_gas_concentration'*] = *'ppm'*

weewx.units.default_unit_format_dict[*'ppm'*]  = *'%.0f'*

weewx.units.default_unit_label_dict[*'ppm'*]  = *' ppm'*


weewx.units.USUnits[*'group_dust'*] = *'microgramm_per_meter_cubic'*

weewx.units.MetricUnits[*'group_dust'*] = *'microgramm_per_meter_cubic'*

weewx.units.MetricWXUnits[*'group_dust'*] = *'microgramm_per_meter_cubic'*

weewx.units.default_unit_format_dict[*'microgramm_per_meter_cubic'*]  =
*'%.1f'*

weewx.units.default_unit_label_dict[*'microgramm_per_meter_cubic'*]  = *'
\xce\xbcg/m\xc2\xb3'*


weewx.units.obs_group_dict[*'AQI25'*] = *'group_dust'*

weewx.units.obs_group_dict[*'AQI100'*] = *'group_dust'*

weewx.units.obs_group_dict[*'AQICO2'*] = *'group_gas_concentration'*

On Mon, May 13, 2019 at 9:15 AM Colin Larsen  wrote:

> Hi all
>
> I am successfully using FilePile to gather some air quality data and add
> it to my Weewx database. Upon using the tag $current.AQICO2 it returns the
> value in the database with 6 decimal points after it, in the database it is
> just a whole number of 672. I know I've something in the formatting
> somewhere but can't quite figure it out
>
> Here is how the data is displayed using my test tag
>
>
>- Test AQM Co2 level is 672.00
>
>  Thanks
> Colin
>

-- 
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/CACjxfUtOgmRN%3DF2i1CJ_FvGcwmm1sZoTXckW3B86Csme-Xdsfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[weewx-user] Another FilePile question

2019-05-12 Thread Colin Larsen
Hi all

I am successfully using FilePile to gather some air quality data and add it
to my Weewx database. Upon using the tag $current.AQICO2 it returns the
value in the database with 6 decimal points after it, in the database it is
just a whole number of 672. I know I've something in the formatting
somewhere but can't quite figure it out

Here is how the data is displayed using my test tag


   - Test AQM Co2 level is 672.00

 Thanks
Colin

-- 
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/CACjxfUsGz%2BMcmqop%3Dpdb2YcXjvLdjBGw%3DzxeVdm4c15jgH5CRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] FilePile help please

2019-05-07 Thread Colin Larsen
Hi Thomas,

Done :) and it's been stable overnight, thanks again for the advice.

Colin

On Wed, May 8, 2019 at 1:59 AM Thomas Keffer  wrote:

> You should terminate your lines with '\n', not '\r' when you write your
> file.
>
> while True:
> data, addr = sock.recvfrom(1024) # buffer size is 1024 bytes
> print "Received message:", data
> with open(fname, 'w') as f:
> for ds in data.split(','):
>     f.write(ds + "\n")
>
> -tk
>
>
> On Tue, May 7, 2019 at 3:35 AM Colin Larsen 
> wrote:
>
>> Thanks Gary appreciate the thoughts, I'll try those out tomorrow
>>
>> Colin
>>
>> On Tue, 7 May 2019, 20:23 gjr80,  wrote:
>>
>>> A few thoughts. If it works sometimes and not others there must be a
>>> problem with either the consistency of the format of the data or the
>>> algorithm being used to parse the data. Can't say I am a big fan of slicing
>>> in a situation like this, I think it can be a bit rigid at times. Maybe
>>> consider using split. To to obtain your name, value pair maybe something
>>> like:
>>>
>>> ...
>>> for line in fd:
>>> data = line.split("=")
>>> if len(data) != 2:
>>> continue
>>> name,value = data
>>> new_record_data[self.label_map.get(name, name)] =
>>> to_float(value)
>>> ...
>>>
>>> or cut out the middle man if you like:
>>>
>>>         ...
>>> for line in fd:
>>> data = line.split("=")
>>> if len(data) != 2:
>>> continue
>>> new_record_data[self.label_map.get(data[0], data[0])] =
>>> to_float(data[1])
>>> ...
>>>
>>> Gary
>>>
>>> On Tuesday, 7 May 2019 17:05:27 UTC+10, Colin Larsen wrote:
>>>>
>>>> And this is the code the writes the txt file - capturing a string via
>>>> UDP
>>>>
>>>> *#!/usr/bin/env python*
>>>>
>>>> *import* socket
>>>>
>>>> *from* shutil *import* copyfile
>>>>
>>>>
>>>> UDP_IP = *"0.0.0.0"*
>>>>
>>>> UDP_PORT = 9886
>>>>
>>>> fname = *"/home/pi/AQIData.txt"*
>>>>
>>>>
>>>> sock = socket.socket(socket.AF_INET,* # Internet*
>>>>
>>>>  socket.SOCK_DGRAM)* # UDP*
>>>>
>>>> sock.bind((UDP_IP, UDP_PORT))
>>>>
>>>>
>>>>
>>>> *while* True:
>>>>
>>>>
>>>> data, addr = sock.recvfrom(1024)* # buffer size is 1024 bytes*
>>>>
>>>> *print* *"Received message:"*, data
>>>>
>>>> dataSplit = data.split(*','*)
>>>>
>>>> f = open(fname,*'w'*)
>>>>
>>>> *for* ds *in* dataSplit:
>>>>
>>>> f.write(ds + *"\r"*)
>>>>
>>>> f.write(*'\n'*)
>>>>
>>>> f.close()
>>>>
>>>> On Tue, May 7, 2019 at 7:01 PM Colin Larsen  wrote:
>>>>
>>>>> Apparently #015 is a numeric representation of \r or 'return' to we
>>>>> can rule that out?
>>>>>
>>>>> On Tue, May 7, 2019 at 6:56 PM Colin Larsen 
>>>>> wrote:
>>>>>
>>>>>> Well this is a little strange. This went fine for a while then
>>>>>> stopped again with pretty much the same error. It appears to be missing 
>>>>>> the
>>>>>> beginning of the first line in the file which is AQI25 = then gets the
>>>>>> reading which is 4.55
>>>>>>
>>>>>> invalid literal for float(): 4.55#015AQI100 = 9.09#015AQIIndex =
>>>>>> 18#015AQICO2 = 863
>>>>>>
>>>>>> Is the #015 a clue of any sorts?
>>>>>>
>>>>>> The file looks ok
>>>>>>
>>>>>> AQI25 = 4.55
>>>>>>
>>>>>> AQI100 = 9.09
>>>>>>
>>>>>> AQIIndex = 18
>>>>>>
>>>>>> AQICO2 = 863
>>>>&

Re: [weewx-user] FilePile help please

2019-05-07 Thread Colin Larsen
Thanks Gary appreciate the thoughts, I'll try those out tomorrow

Colin

On Tue, 7 May 2019, 20:23 gjr80,  wrote:

> A few thoughts. If it works sometimes and not others there must be a
> problem with either the consistency of the format of the data or the
> algorithm being used to parse the data. Can't say I am a big fan of slicing
> in a situation like this, I think it can be a bit rigid at times. Maybe
> consider using split. To to obtain your name, value pair maybe something
> like:
>
> ...
> for line in fd:
> data = line.split("=")
> if len(data) != 2:
> continue
> name,value = data
> new_record_data[self.label_map.get(name, name)] = to_float
> (value)
> ...
>
> or cut out the middle man if you like:
>
> ...
> for line in fd:
> data = line.split("=")
> if len(data) != 2:
> continue
> new_record_data[self.label_map.get(data[0], data[0])] =
> to_float(data[1])
> ...
>
> Gary
>
> On Tuesday, 7 May 2019 17:05:27 UTC+10, Colin Larsen wrote:
>>
>> And this is the code the writes the txt file - capturing a string via UDP
>>
>> *#!/usr/bin/env python*
>>
>> *import* socket
>>
>> *from* shutil *import* copyfile
>>
>>
>> UDP_IP = *"0.0.0.0"*
>>
>> UDP_PORT = 9886
>>
>> fname = *"/home/pi/AQIData.txt"*
>>
>>
>> sock = socket.socket(socket.AF_INET,* # Internet*
>>
>>  socket.SOCK_DGRAM)* # UDP*
>>
>> sock.bind((UDP_IP, UDP_PORT))
>>
>>
>>
>> *while* True:
>>
>>
>> data, addr = sock.recvfrom(1024)* # buffer size is 1024 bytes*
>>
>> *print* *"Received message:"*, data
>>
>> dataSplit = data.split(*','*)
>>
>> f = open(fname,*'w'*)
>>
>> *for* ds *in* dataSplit:
>>
>> f.write(ds + *"\r"*)
>>
>> f.write(*'\n'*)
>>
>> f.close()
>>
>> On Tue, May 7, 2019 at 7:01 PM Colin Larsen  wrote:
>>
>>> Apparently #015 is a numeric representation of \r or 'return' to we can
>>> rule that out?
>>>
>>> On Tue, May 7, 2019 at 6:56 PM Colin Larsen  wrote:
>>>
>>>> Well this is a little strange. This went fine for a while then stopped
>>>> again with pretty much the same error. It appears to be missing the
>>>> beginning of the first line in the file which is AQI25 = then gets the
>>>> reading which is 4.55
>>>>
>>>> invalid literal for float(): 4.55#015AQI100 = 9.09#015AQIIndex =
>>>> 18#015AQICO2 = 863
>>>>
>>>> Is the #015 a clue of any sorts?
>>>>
>>>> The file looks ok
>>>>
>>>> AQI25 = 4.55
>>>>
>>>> AQI100 = 9.09
>>>>
>>>> AQIIndex = 18
>>>>
>>>> AQICO2 = 863
>>>>
>>>>
>>>> Error;
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]: engine: Main loop exiting.
>>>> Shutting engine down.
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]: engine: Caught unrecoverable
>>>> exception in engine:
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]:   invalid literal
>>>> for float(): 4.55#015AQI100 = 9.09#015AQIIndex = 18#015AQICO2 = 863
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]:   Traceback (most
>>>> recent call last):
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]: File
>>>> "/usr/share/weewx/weewx/engine.py", line 890, in main
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]:   engine.run()
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]: File
>>>> "/usr/share/weewx/weewx/engine.py", line 202, in run
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]: 
>>>> self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]: File
>>>> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
>>>>
>>>> May  7 18:50:16 raspberrypi weewx[11960]:   callback(event)
>>>>

Re: [weewx-user] FilePile help please

2019-05-06 Thread Colin Larsen
Well this is a little strange. This went fine for a while then stopped
again with pretty much the same error. It appears to be missing the
beginning of the first line in the file which is AQI25 = then gets the
reading which is 4.55

invalid literal for float(): 4.55#015AQI100 = 9.09#015AQIIndex =
18#015AQICO2 = 863

Is the #015 a clue of any sorts?

The file looks ok

AQI25 = 4.55

AQI100 = 9.09

AQIIndex = 18

AQICO2 = 863


Error;

May  7 18:50:16 raspberrypi weewx[11960]: engine: Main loop exiting.
Shutting engine down.

May  7 18:50:16 raspberrypi weewx[11960]: engine: Caught unrecoverable
exception in engine:

May  7 18:50:16 raspberrypi weewx[11960]:   invalid literal for
float(): 4.55#015AQI100 = 9.09#015AQIIndex = 18#015AQICO2 = 863

May  7 18:50:16 raspberrypi weewx[11960]:   Traceback (most recent
call last):

May  7 18:50:16 raspberrypi weewx[11960]: File
"/usr/share/weewx/weewx/engine.py", line 890, in main

May  7 18:50:16 raspberrypi weewx[11960]:   engine.run()

May  7 18:50:16 raspberrypi weewx[11960]: File
"/usr/share/weewx/weewx/engine.py", line 202, in run

May  7 18:50:16 raspberrypi weewx[11960]: 
self.dispatchEvent(weewx.Event(weewx.POST_LOOP))

May  7 18:50:16 raspberrypi weewx[11960]: File
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent

May  7 18:50:16 raspberrypi weewx[11960]:   callback(event)

May  7 18:50:16 raspberrypi weewx[11960]: File
"/usr/share/weewx/weewx/engine.py", line 574, in post_loop

May  7 18:50:16 raspberrypi weewx[11960]: 
self._software_catchup()

May  7 18:50:16 raspberrypi weewx[11960]: File
"/usr/share/weewx/weewx/engine.py", line 646, in _software_catchup

May  7 18:50:16 raspberrypi weewx[11960]: 
self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,
record=record, origin='software'))

May  7 18:50:16 raspberrypi weewx[11960]: File
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent

May  7 18:50:16 raspberrypi weewx[11960]:   callback(event)

May  7 18:50:16 raspberrypi weewx[11960]: File
"/usr/share/weewx/user/filepile.py", line 91, in new_archive_record

May  7 18:50:16 raspberrypi weewx[11960]: 
new_record_data[self.label_map.get(name,
name)] = to_float(value)

May  7 18:50:16 raspberrypi weewx[11960]: File
"/usr/share/weewx/weeutil/weeutil.py", line 1280, in to_float

May  7 18:50:16 raspberrypi weewx[11960]:   return float(x) if
x is not None else None

May  7 18:50:16 raspberrypi weewx[11960]:   ValueError: invalid
literal for float(): 4.55#015AQI100 = 9.09#015AQIIndex = 18#015AQICO2 = 863

May  7 18:50:16 raspberrypi weewx[11960]:   Exiting.

On Tue, May 7, 2019 at 3:23 PM Colin Larsen  wrote:

> Hi Thomas
>
> Thanks for the quick reply. It was just the format, it needs the spaces so
> each line in the text file is
>
>
> AQI25 = 1.60
>
> AQI100 = 3.30
>
> AQIIndex = 6
>
> AQICO2 = 683
>
>
> Once I did that and checked the database after an archive period the
> fields were populated
>
> Does my section with the units look valid? I've borrowed that from a
> similar service but I can't wrap my head around how the relationship
> between those and the data in the txt file get joined together
>
>
> Thanks again
>
> Colin
>
>
>
> On Tue, May 7, 2019 at 3:13 PM Thomas Keffer  wrote:
>
>> Hi, Colin
>>
>> Does your text file use newlines ('\n') as line delineators? Perhaps it
>> is using the MS-DOS standard of '\n\r'? Examine the file carefully and make
>> sure it contains what you think it contains.
>>
>> -tk
>>
>> On Mon, May 6, 2019 at 8:05 PM Colin Larsen 
>> wrote:
>>
>>> Hi all
>>>
>>> I'm trying to get Filepile working but have come across an error that I
>>> don't understand. Any help appreciated. The database has been extended with
>>> fields to match those below in the data file - am I just missing spaces in
>>> the layout? Should it be AQI25 = 1.60 etc etc
>>>
>>> Many thanks
>>>
>>> This is my data file;
>>>
>>> AQI25=1.60
>>>
>>> AQI100=3.30
>>>
>>> AQIIndex=6
>>>
>>> AQICO2=683
>>>
>>>
>>> This is my stanza in weewx.conf
>>>
>>>
>>> ##
>>>
>>>
>>> #   This section is for FilePile
>>>
>>>
>>> [FilePile]
>>>
>>>
>>> filename = /home/pi/AQIDat

Re: [weewx-user] FilePile help please

2019-05-06 Thread Colin Larsen
Hi Thomas

Thanks for the quick reply. It was just the format, it needs the spaces so
each line in the text file is


AQI25 = 1.60

AQI100 = 3.30

AQIIndex = 6

AQICO2 = 683


Once I did that and checked the database after an archive period the fields
were populated

Does my section with the units look valid? I've borrowed that from a
similar service but I can't wrap my head around how the relationship
between those and the data in the txt file get joined together


Thanks again

Colin



On Tue, May 7, 2019 at 3:13 PM Thomas Keffer  wrote:

> Hi, Colin
>
> Does your text file use newlines ('\n') as line delineators? Perhaps it is
> using the MS-DOS standard of '\n\r'? Examine the file carefully and make
> sure it contains what you think it contains.
>
> -tk
>
> On Mon, May 6, 2019 at 8:05 PM Colin Larsen 
> wrote:
>
>> Hi all
>>
>> I'm trying to get Filepile working but have come across an error that I
>> don't understand. Any help appreciated. The database has been extended with
>> fields to match those below in the data file - am I just missing spaces in
>> the layout? Should it be AQI25 = 1.60 etc etc
>>
>> Many thanks
>>
>> This is my data file;
>>
>> AQI25=1.60
>>
>> AQI100=3.30
>>
>> AQIIndex=6
>>
>> AQICO2=683
>>
>>
>> This is my stanza in weewx.conf
>>
>>
>> ##
>>
>>
>> #   This section is for FilePile
>>
>>
>> [FilePile]
>>
>>
>> filename = /home/pi/AQIData.txt
>>
>> unit_system = METRIC
>>
>>
>>
>> ##
>>
>>
>> This is my filepile.py (modified from original to suit)
>>
>>
>> *import* syslog
>>
>> *import* weewx
>>
>> *import* weewx.units
>>
>> *from* weewx.wxengine *import* StdService
>>
>> *from* weeutil.weeutil *import* to_float
>>
>>
>> weewx.units.USUnits[*'group_gas_concentration'*] = *'ppm'*
>>
>> weewx.units.MetricUnits[*'group_gas_concentration'*] = *'ppm'*
>>
>> weewx.units.MetricWXUnits[*'group_gas_concentration'*] = *'ppm'*
>>
>> weewx.units.default_unit_format_dict[*'ppm'*]  = *'%.0f'*
>>
>> weewx.units.default_unit_label_dict[*'ppm'*]  = *' ppm'*
>>
>>
>> weewx.units.USUnits[*'group_dust'*] = *'microgramm_per_meter_cubic'*
>>
>> weewx.units.MetricUnits[*'group_dust'*] = *'microgramm_per_meter_cubic'*
>>
>> weewx.units.MetricWXUnits[*'group_dust'*] =
>> *'microgramm_per_meter_cubic'*
>>
>> weewx.units.default_unit_format_dict[*'microgramm_per_meter_cubic'*]  =
>> *'%.1f'*
>>
>> weewx.units.default_unit_label_dict[*'microgramm_per_meter_cubic'*]  = *'
>> \xce\xbcg/m\xc2\xb3'*
>>
>>
>> *class* FilePile(StdService):
>>
>> *"""WeeWX service for augmenting a record with data parsed from a
>> file."""*
>>
>>
>> *def** __init__*(self, engine, config_dict):
>>
>>* # Initialize my superclass:*
>>
>> super(FilePile, self).__init__(engine, config_dict)
>>
>> *# Extract our stanza from the configuration dicdtionary*
>>
>> filepile_dict = config_dict.get(*'FilePile'*, {})
>>
>>* # Get the location of the file ...*
>>
>> self.filename = filepile_dict.get(*'filename'*,
>> *'/var/tmp/filepile.txt'*)
>>
>>* # ... and the unit system it will use*
>>
>> unit_system_name = filepile_dict.get(*'unit_system'*,
>> *'METRICWX'*).strip().upper()
>>
>>* # Make sure we know about the unit system. If not, raise an
>> exception.*
>>
>> *if* unit_system_name *not* *in* weewx.units.unit_constants:
>>
>> *raise* ValueError(*"FilePile: Unknown unit system: %s"* %
>> unit_system_name)
>>
>>* # Use the numeric code for the unit system*
>>
>> self.unit_system = weewx.units.unit_constants[unit_system_name]
>>
>>
>>* # Mapping from variable names to weewx names*
>>
>> self.label_map = filepile_dict.get(*'label_map'*, {})
>>
>

[weewx-user] FilePile help please

2019-05-06 Thread Colin Larsen
Hi all

I'm trying to get Filepile working but have come across an error that I
don't understand. Any help appreciated. The database has been extended with
fields to match those below in the data file - am I just missing spaces in
the layout? Should it be AQI25 = 1.60 etc etc

Many thanks

This is my data file;

AQI25=1.60

AQI100=3.30

AQIIndex=6

AQICO2=683


This is my stanza in weewx.conf

##


#   This section is for FilePile


[FilePile]


filename = /home/pi/AQIData.txt

unit_system = METRIC


##


This is my filepile.py (modified from original to suit)


*import* syslog

*import* weewx

*import* weewx.units

*from* weewx.wxengine *import* StdService

*from* weeutil.weeutil *import* to_float


weewx.units.USUnits[*'group_gas_concentration'*] = *'ppm'*

weewx.units.MetricUnits[*'group_gas_concentration'*] = *'ppm'*

weewx.units.MetricWXUnits[*'group_gas_concentration'*] = *'ppm'*

weewx.units.default_unit_format_dict[*'ppm'*]  = *'%.0f'*

weewx.units.default_unit_label_dict[*'ppm'*]  = *' ppm'*


weewx.units.USUnits[*'group_dust'*] = *'microgramm_per_meter_cubic'*

weewx.units.MetricUnits[*'group_dust'*] = *'microgramm_per_meter_cubic'*

weewx.units.MetricWXUnits[*'group_dust'*] = *'microgramm_per_meter_cubic'*

weewx.units.default_unit_format_dict[*'microgramm_per_meter_cubic'*]  =
*'%.1f'*

weewx.units.default_unit_label_dict[*'microgramm_per_meter_cubic'*]  = *'
\xce\xbcg/m\xc2\xb3'*


*class* FilePile(StdService):

*"""WeeWX service for augmenting a record with data parsed from a
file."""*


*def** __init__*(self, engine, config_dict):

   * # Initialize my superclass:*

super(FilePile, self).__init__(engine, config_dict)

*# Extract our stanza from the configuration dicdtionary*

filepile_dict = config_dict.get(*'FilePile'*, {})

   * # Get the location of the file ...*

self.filename = filepile_dict.get(*'filename'*,
*'/var/tmp/filepile.txt'*)

   * # ... and the unit system it will use*

unit_system_name = filepile_dict.get(*'unit_system'*, *'METRICWX'*
).strip().upper()

   * # Make sure we know about the unit system. If not, raise an
exception.*

*if* unit_system_name *not* *in* weewx.units.unit_constants:

*raise* ValueError(*"FilePile: Unknown unit system: %s"* %
unit_system_name)

   * # Use the numeric code for the unit system*

self.unit_system = weewx.units.unit_constants[unit_system_name]


   * # Mapping from variable names to weewx names*

self.label_map = filepile_dict.get(*'label_map'*, {})

syslog.syslog(syslog.LOG_INFO, *"filepile: Using %s with the '%s'
unit system"*

  % (self.filename, unit_system_name))

syslog.syslog(syslog.LOG_INFO, *"filepile: Label map is %s"* %
self.label_map)


   * # Bind to the NEW_ARCHIVE_RECORD event*

self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)


*def** new_archive_record*(self, event):

new_record_data = {}

*try*:

*with* open(self.filename, *'r'*) *as* fd:

*for* line *in* fd:

eq_index = line.find(*'='*)

*# Ignore all lines that do not have an equal sign*

*if* eq_index == -1:

*continue*

name = line[:eq_index].strip()

value = line[eq_index + 1:].strip()

new_record_data[self.label_map.get(name, name)] =
to_float(value)

   * # Supply a unit system if one wasn't included in the file*

*if* *'usUnits'* *not* *in* new_record_data:

new_record_data[*'usUnits'*] = self.unit_system

   * # Convert the new values to the same unit system as the
record*

target_data = weewx.units.to_std_system(new_record_data,
event.record[*'usUnits'*])

   * # Add the converted values to the record:*

event.record.update(target_data)

*except* IOError *as* e:

   syslog.syslog(syslog.LOG_ERR, *"FilePile: Cannot open file. Reason:
%s"* % e)

This is the syslog error;

May  7 14:50:16 raspberrypi weewx[6605]: engine: Caught unrecoverable
exception in engine:

May  7 14:50:16 raspberrypi weewx[6605]:   invalid literal for
float(): 1.60#015AQI100=3.30#015AQIIndex=6#015AQICO2=683

May  7 14:50:16 raspberrypi weewx[6605]:   Traceback (most recent
call last):

May  7 14:50:16 raspberrypi weewx[6605]: File
"/usr/share/weewx/weewx/engine.py", line 890, in main

May  7 14:50:16 raspberrypi weewx[6605]:   engine.run()

May  7 14:50:16 raspberrypi weewx[6605]: File
"/usr/share/weewx/weewx/engine.py", line 202, in run

May  7 14:50:16 raspberrypi weewx[6605]: 
self.dispatch

Re: [weewx-user] Help creating a service to import data from file

2019-04-23 Thread Colin Larsen
With help from a friend I've got the data txt file sorted into the right
format so hopefully this will be easy from here.

I assume I still need some 'units' detail somewhere along the line in the
[FilePile] stanza?

Cheers
Colin

On Wed, Apr 24, 2019 at 7:48 AM Colin Larsen  wrote:

> This is how the data is constructed and sent in Arduino, it's sent as a
> complete line of ascii data
>
> // - AQI Data for Weewx -
>
> Data = F("AQI25=");
> Data += String(AQI_Monitor.AQI_PM2_5 / 10.0);
> Data += F(",AQI100=");
> Data += String(AQI_Monitor.AQI_PM10_0 / 10.0);
> Data += F(",AQIIndex=");
> Data += String(AQI_Monitor.AQI_Index / 10);
> Data += F(",AQICO2=");
> Data += String(AQI_Monitor.GAS_1);
>
> Then sent using
>
> //  Send AQI Datapacket 
>  udp1.beginPacket(broadcastIP, AQI_BROADCAST_PORT);
>  udp1.write((const uint8_t*)Data.c_str(), strlen(Data.c_str()));
>  udp1.endPacket();
>  udp1.stop();
>
> So I'm unsure how to get line feeds in there instead of the comma
> delimiter.
>
> Seems it would be easier to look for the comma in the txt file :)
>
> Cheers
> Colin
>
> On Wed, Apr 24, 2019 at 7:31 AM Colin Larsen 
> wrote:
>
>> Ok that sure looks like it would do the job but with my file format I
>> would need to use "," as a delimiter between records rather than a new line
>> something like (borrowed from another similar utility). I have never done
>> Python so I'm a little lost on how to change this sorry
>>
>> with open(self.filename) as f:
>> for line,row in enumerate(f.readlines()):
>> if line == 0:
>> names = row.strip().split(",")
>> if line == 0:
>> units = row.strip().split(",")
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Apr 24, 2019 at 1:40 AM Thomas Keffer  wrote:
>>
>>> Because of the syntax, it's tempting to look at a ConfigObj file and
>>> think of it as assigning the right hand side to the left hand side. But,
>>> it's really not. It's a mapping. The left hand side *maps to* the right
>>> hand side.
>>>
>>> As a key:value comes in from the file, we need to know what to do with
>>> the key. Given a key, what WeeWX name do we assign it to? With a mapping,
>>> we look it up, then do the assignment to the value. If we did it the other
>>> way around, we'd have to search all the *values* in the mapping to find
>>> what it should be mapped to. That's backwards from the way dictionaries
>>> work.
>>>
>>> -tk
>>>
>>> On Tue, Apr 23, 2019 at 5:51 AM Andrew Milner <
>>> andrew.s.r.mil...@gmail.com> wrote:
>>>
>>>> Tom
>>>> Forgive me for being a pedant - but shouldn't the label map for
>>>> filepile have the arguments the other way round
>>>> ie rather than
>>>>  myVoltage = Supply Voltage
>>>> it should be
>>>>  SupplyVoltage = myVoltage
>>>> ie
>>>>   weewx destination field = source data field
>>>>
>>>> normally left of equals sign is the result of operations right of
>>>> equals sign
>>>> eg
>>>>   a = 3 + 2 would put 5 into a
>>>>
>>>>
>>>>
>>>> On Tuesday, 23 April 2019 14:45:38 UTC+3, Thomas Keffer wrote:
>>>>>
>>>>> Take a look at Filepile <https://github.com/tkeffer/filepile>. It may
>>>>> do what you want, or help you write your own.
>>>>>
>>>>> -tk
>>>>>
>>>>> On Mon, Apr 22, 2019 at 7:43 PM  wrote:
>>>>>
>>>>>> Hi all
>>>>>>
>>>>>> I have devised a method to export my Air Quality Data (AQI) from my
>>>>>> Arduino based weather station to Weewx (it can't be sent via the usb port
>>>>>> with the rest of the data). It involves sending the data via a UDP
>>>>>> broadcast packet from the station, this is then captured by a small 
>>>>>> Python
>>>>>> script on my Weewx Pi and written to a txt file.
>>>>>>
>>>>>> The txt file data looks like this
>>>>>> AQI25=5.50,AQI100=4.10,AQIIndex=22,AQICO2=967
>>>>>>
>>>>>> From the Weewx wiki I have crafted the beginning of a service to
>>>>>> import the data to my Wewwx database (extended with the 4 

Re: [weewx-user] Help creating a service to import data from file

2019-04-23 Thread Colin Larsen
This is how the data is constructed and sent in Arduino, it's sent as a
complete line of ascii data

// - AQI Data for Weewx -

Data = F("AQI25=");
Data += String(AQI_Monitor.AQI_PM2_5 / 10.0);
Data += F(",AQI100=");
Data += String(AQI_Monitor.AQI_PM10_0 / 10.0);
Data += F(",AQIIndex=");
Data += String(AQI_Monitor.AQI_Index / 10);
Data += F(",AQICO2=");
Data += String(AQI_Monitor.GAS_1);

Then sent using

//  Send AQI Datapacket 
 udp1.beginPacket(broadcastIP, AQI_BROADCAST_PORT);
 udp1.write((const uint8_t*)Data.c_str(), strlen(Data.c_str()));
 udp1.endPacket();
 udp1.stop();

So I'm unsure how to get line feeds in there instead of the comma delimiter.

Seems it would be easier to look for the comma in the txt file :)

Cheers
Colin

On Wed, Apr 24, 2019 at 7:31 AM Colin Larsen  wrote:

> Ok that sure looks like it would do the job but with my file format I
> would need to use "," as a delimiter between records rather than a new line
> something like (borrowed from another similar utility). I have never done
> Python so I'm a little lost on how to change this sorry
>
> with open(self.filename) as f:
> for line,row in enumerate(f.readlines()):
> if line == 0:
> names = row.strip().split(",")
> if line == 0:
> units = row.strip().split(",")
>
>
>
>
>
>
>
> On Wed, Apr 24, 2019 at 1:40 AM Thomas Keffer  wrote:
>
>> Because of the syntax, it's tempting to look at a ConfigObj file and
>> think of it as assigning the right hand side to the left hand side. But,
>> it's really not. It's a mapping. The left hand side *maps to* the right
>> hand side.
>>
>> As a key:value comes in from the file, we need to know what to do with
>> the key. Given a key, what WeeWX name do we assign it to? With a mapping,
>> we look it up, then do the assignment to the value. If we did it the other
>> way around, we'd have to search all the *values* in the mapping to find
>> what it should be mapped to. That's backwards from the way dictionaries
>> work.
>>
>> -tk
>>
>> On Tue, Apr 23, 2019 at 5:51 AM Andrew Milner <
>> andrew.s.r.mil...@gmail.com> wrote:
>>
>>> Tom
>>> Forgive me for being a pedant - but shouldn't the label map for filepile
>>> have the arguments the other way round
>>> ie rather than
>>>  myVoltage = Supply Voltage
>>> it should be
>>>  SupplyVoltage = myVoltage
>>> ie
>>>   weewx destination field = source data field
>>>
>>> normally left of equals sign is the result of operations right of equals
>>> sign
>>> eg
>>>   a = 3 + 2 would put 5 into a
>>>
>>>
>>>
>>> On Tuesday, 23 April 2019 14:45:38 UTC+3, Thomas Keffer wrote:
>>>>
>>>> Take a look at Filepile <https://github.com/tkeffer/filepile>. It may
>>>> do what you want, or help you write your own.
>>>>
>>>> -tk
>>>>
>>>> On Mon, Apr 22, 2019 at 7:43 PM  wrote:
>>>>
>>>>> Hi all
>>>>>
>>>>> I have devised a method to export my Air Quality Data (AQI) from my
>>>>> Arduino based weather station to Weewx (it can't be sent via the usb port
>>>>> with the rest of the data). It involves sending the data via a UDP
>>>>> broadcast packet from the station, this is then captured by a small Python
>>>>> script on my Weewx Pi and written to a txt file.
>>>>>
>>>>> The txt file data looks like this
>>>>> AQI25=5.50,AQI100=4.10,AQIIndex=22,AQICO2=967
>>>>>
>>>>> From the Weewx wiki I have crafted the beginning of a service to
>>>>> import the data to my Wewwx database (extended with the 4 new data fields)
>>>>> but I'm not sure how to complete that task. So far I have this, which I
>>>>> think will grab the first value - how do I parse the other 3? Is it as
>>>>> simple as just adding more lines such as event.record['AQI100'] =
>>>>> float(value) etc?
>>>>>
>>>>> *import* syslog
>>>>>
>>>>> *import* weewx
>>>>>
>>>>> *from* weewx.wxengine *import* StdService
>>>>>
>>>>>
>>>>> *class* WDAQIService(StdService):
>>>>>
>>>>> *def** __init__*(self, engine, config_dict):
>>>>>
>>>>> super(WDAQ

Re: [weewx-user] Help creating a service to import data from file

2019-04-23 Thread Colin Larsen
Ok that sure looks like it would do the job but with my file format I would
need to use "," as a delimiter between records rather than a new line
something like (borrowed from another similar utility). I have never done
Python so I'm a little lost on how to change this sorry

with open(self.filename) as f:
for line,row in enumerate(f.readlines()):
if line == 0:
names = row.strip().split(",")
if line == 0:
units = row.strip().split(",")







On Wed, Apr 24, 2019 at 1:40 AM Thomas Keffer  wrote:

> Because of the syntax, it's tempting to look at a ConfigObj file and think
> of it as assigning the right hand side to the left hand side. But, it's
> really not. It's a mapping. The left hand side *maps to* the right hand
> side.
>
> As a key:value comes in from the file, we need to know what to do with the
> key. Given a key, what WeeWX name do we assign it to? With a mapping, we
> look it up, then do the assignment to the value. If we did it the other way
> around, we'd have to search all the *values* in the mapping to find what
> it should be mapped to. That's backwards from the way dictionaries work.
>
> -tk
>
> On Tue, Apr 23, 2019 at 5:51 AM Andrew Milner 
> wrote:
>
>> Tom
>> Forgive me for being a pedant - but shouldn't the label map for filepile
>> have the arguments the other way round
>> ie rather than
>>  myVoltage = Supply Voltage
>> it should be
>>  SupplyVoltage = myVoltage
>> ie
>>   weewx destination field = source data field
>>
>> normally left of equals sign is the result of operations right of equals
>> sign
>> eg
>>   a = 3 + 2 would put 5 into a
>>
>>
>>
>> On Tuesday, 23 April 2019 14:45:38 UTC+3, Thomas Keffer wrote:
>>>
>>> Take a look at Filepile . It may
>>> do what you want, or help you write your own.
>>>
>>> -tk
>>>
>>> On Mon, Apr 22, 2019 at 7:43 PM  wrote:
>>>
 Hi all

 I have devised a method to export my Air Quality Data (AQI) from my
 Arduino based weather station to Weewx (it can't be sent via the usb port
 with the rest of the data). It involves sending the data via a UDP
 broadcast packet from the station, this is then captured by a small Python
 script on my Weewx Pi and written to a txt file.

 The txt file data looks like this
 AQI25=5.50,AQI100=4.10,AQIIndex=22,AQICO2=967

 From the Weewx wiki I have crafted the beginning of a service to import
 the data to my Wewwx database (extended with the 4 new data fields) but I'm
 not sure how to complete that task. So far I have this, which I think will
 grab the first value - how do I parse the other 3? Is it as simple as just
 adding more lines such as event.record['AQI100'] = float(value) etc?

 *import* syslog

 *import* weewx

 *from* weewx.wxengine *import* StdService


 *class* WDAQIService(StdService):

 *def** __init__*(self, engine, config_dict):

 super(WDAQIService, self).__init__(engine, config_dict)

 d = config_dict.get(*'WDAQIService'*, {})

 self.filename = d.get(*'filename'*, *'/home/pi/AQIData.txt'*)

 syslog.syslog(syslog.LOG_INFO, *"WDAQIImport: using %s"* %
 self.filename)

 self.bind(weewx.NEW_ARCHIVE_RECORD, self.read_file)


 *def** read_file*(self, event):

 *try*:

 *with* open(self.filename) *as* f:

 value = f.read()

 syslog.syslog(syslog.LOG_DEBUG, *"WDAQIImport: found value
 of %s"* % value)

 event.record[*'AQI25'*] = float(value)

 *except* Exception *as* e:

 syslog.syslog(syslog.LOG_ERR, *"WDAQIImport: cannot read
 value: %s"* % e)

 Thanks
 Colin

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

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

[weewx-user] Help creating a service to import data from file

2019-04-22 Thread colin . larsen
Hi all

I have devised a method to export my Air Quality Data (AQI) from my Arduino 
based weather station to Weewx (it can't be sent via the usb port with the 
rest of the data). It involves sending the data via a UDP broadcast packet 
from the station, this is then captured by a small Python script on my 
Weewx Pi and written to a txt file.

The txt file data looks like this 
AQI25=5.50,AQI100=4.10,AQIIndex=22,AQICO2=967

>From the Weewx wiki I have crafted the beginning of a service to import the 
data to my Wewwx database (extended with the 4 new data fields) but I'm not 
sure how to complete that task. So far I have this, which I think will grab 
the first value - how do I parse the other 3? Is it as simple as just 
adding more lines such as event.record['AQI100'] = float(value) etc?

*import* syslog

*import* weewx

*from* weewx.wxengine *import* StdService


*class* WDAQIService(StdService):

*def** __init__*(self, engine, config_dict):

super(WDAQIService, self).__init__(engine, config_dict)  

d = config_dict.get(*'WDAQIService'*, {})

self.filename = d.get(*'filename'*, *'/home/pi/AQIData.txt'*)

syslog.syslog(syslog.LOG_INFO, *"WDAQIImport: using %s"* % 
self.filename)

self.bind(weewx.NEW_ARCHIVE_RECORD, self.read_file)


*def** read_file*(self, event):

*try*:

*with* open(self.filename) *as* f:

value = f.read()

syslog.syslog(syslog.LOG_DEBUG, *"WDAQIImport: found value of 
%s"* % value)

event.record[*'AQI25'*] = float(value)

*except* Exception *as* e:

syslog.syslog(syslog.LOG_ERR, *"WDAQIImport: cannot read value: 
%s"* % e)

Thanks
Colin

-- 
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] Upgrade issue 3.8.2 to 3.9.1

2019-04-07 Thread Colin Larsen
Thanks again Thomas, have made that change in weewx.conf and copied the
original engine.py back over and it's all working fine.

Cheers
Colin

On Mon, Apr 8, 2019 at 4:12 AM Thomas Keffer  wrote:

> Ah, yes, now I remember. In a later commit
> <https://github.com/weewx/weewx/commit/8929d365ab5f878671bec8ca3a62c77f2e156f99>,
> I changed the strategy so there is now an option to prevent hardware catch
> ups.
>
> Under [StdArchive], add option no_catchup and set it to True:
>
> [StdArchive]
> ...
> no_catchup = True
>
> -tk
>
> On Sat, Apr 6, 2019 at 9:52 PM Colin Larsen 
> wrote:
>
>> Hi Thomas, that's what I thought but my install of 3.9.1 still required
>> the engine.py file to be updated, so I'm not sure what happened there. I'm
>> up and running so I guess I'm just passing this on for the devs info,
>> perhaps something hasn't been updated or included :)
>> I'll make sure I have that file safely saved somewhere too
>>
>> Colin
>>
>> On Sun, Apr 7, 2019 at 4:21 PM Thomas Keffer  wrote:
>>
>>> Yes, this was in commit 6e7f3aac
>>> <https://github.com/weewx/weewx/commit/6e7f3aac1b2926cacfa63229db2dbbd55f3f2cab>,
>>> which is now part of v3.9.1.
>>>
>>> -tk
>>>
>>> On Sat, Apr 6, 2019 at 5:11 PM  wrote:
>>>
>>>> Hi all
>>>>
>>>> Just upgraded my installation as above. The hardware is WeatherDuino
>>>> emulating the Davis comms protocol. On a previous occasion I had an issue
>>>> which I think was similar to the errors below and was asked to use an
>>>> updated engine.py file - which fixed the problem. After the upgrade I had
>>>> to once again copy over the "new" engine.py to sort out this error. I'm not
>>>> sure if the fix I was supplied was supposed to be rolled through to the
>>>> 3.9.1 upgrade? Log below of the error.
>>>>
>>>> Cheers
>>>> Colin
>>>>
>>>> Apr  7 11:57:16 raspberrypi systemd[1]: Starting LSB: weewx weather
>>>> system...
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Initializing weewx
>>>> version 3.9.1
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Using Python 2.7.13
>>>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Platform
>>>> Linux-4.14.71-v7+-armv7l-with-debian-9.4
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Locale is
>>>> 'en_NZ.UTF-8'
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: pid file is
>>>> /var/run/weewx.pid
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21090]: Starting weewx weather
>>>> system: weewx.
>>>>
>>>> Apr  7 11:57:17 raspberrypi systemd[1]: Started LSB: weewx weather
>>>> system.
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Using configuration
>>>> file /etc/weewx/weewx.conf
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Loading station type
>>>> Vantage (weewx.drivers.vantage)
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: StdConvert target
>>>> unit is 0x10
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21106]: wxcalculate: The following
>>>> values will be calculated: barometer=prefer_hardware,
>>>> windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=software,
>>>> rainRate=prefer_hardware, windrun=prefer_hardware,
>>>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
>>>> humidex=prefer_hardware, pressure=prefer_hardware,
>>>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
>>>> cloudbase=prefer_hardware
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21106]: wxcalculate: The following
>>>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Archive will use
>>>> data binding wx_binding
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Record generation
>>>> will be attempted in 'software'
>>>>
>>>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Using archive
>>>> interval of 300 seconds (software record generation)
>

Re: [weewx-user] Upgrade issue 3.8.2 to 3.9.1

2019-04-06 Thread Colin Larsen
Hi Thomas, that's what I thought but my install of 3.9.1 still required the
engine.py file to be updated, so I'm not sure what happened there. I'm up
and running so I guess I'm just passing this on for the devs info, perhaps
something hasn't been updated or included :)
I'll make sure I have that file safely saved somewhere too

Colin

On Sun, Apr 7, 2019 at 4:21 PM Thomas Keffer  wrote:

> Yes, this was in commit 6e7f3aac
> ,
> which is now part of v3.9.1.
>
> -tk
>
> On Sat, Apr 6, 2019 at 5:11 PM  wrote:
>
>> Hi all
>>
>> Just upgraded my installation as above. The hardware is WeatherDuino
>> emulating the Davis comms protocol. On a previous occasion I had an issue
>> which I think was similar to the errors below and was asked to use an
>> updated engine.py file - which fixed the problem. After the upgrade I had
>> to once again copy over the "new" engine.py to sort out this error. I'm not
>> sure if the fix I was supplied was supposed to be rolled through to the
>> 3.9.1 upgrade? Log below of the error.
>>
>> Cheers
>> Colin
>>
>> Apr  7 11:57:16 raspberrypi systemd[1]: Starting LSB: weewx weather
>> system...
>>
>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Initializing weewx
>> version 3.9.1
>>
>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Using Python 2.7.13
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>>
>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Platform
>> Linux-4.14.71-v7+-armv7l-with-debian-9.4
>>
>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Locale is 'en_NZ.UTF-8'
>>
>> Apr  7 11:57:17 raspberrypi weewx[21102]: engine: pid file is
>> /var/run/weewx.pid
>>
>> Apr  7 11:57:17 raspberrypi weewx[21090]: Starting weewx weather system:
>> weewx.
>>
>> Apr  7 11:57:17 raspberrypi systemd[1]: Started LSB: weewx weather
>> system.
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Using configuration
>> file /etc/weewx/weewx.conf
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Loading station type
>> Vantage (weewx.drivers.vantage)
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: StdConvert target unit
>> is 0x10
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: wxcalculate: The following
>> values will be calculated: barometer=prefer_hardware,
>> windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=software,
>> rainRate=prefer_hardware, windrun=prefer_hardware,
>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
>> humidex=prefer_hardware, pressure=prefer_hardware,
>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
>> cloudbase=prefer_hardware
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: wxcalculate: The following
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Archive will use data
>> binding wx_binding
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Record generation will
>> be attempted in 'software'
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Using archive interval
>> of 300 seconds (software record generation)
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Using binding
>> 'wx_binding' to database 'weewx.sdb'
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: manager: Starting backfill of
>> daily summaries
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: StationRegistry:
>> Station will be registered.
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: Wunderground: Posting
>> not enabled.
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: PWSweather: Posting not
>> enabled.
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: CWOP: Data for station
>> ZL2ARL will be posted
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: WOW: Posting not
>> enabled.
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: AWEKAS: Posting not
>> enabled.
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: service version
>> is 0.18rc1
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: binding to loop
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: topic is
>> weather/41south
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: desired unit
>> system is METRIC
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: data will be
>> uploaded to mqtt://192.168.20.121:1883/
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Starting up weewx
>> version 3.9.1
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Clock error is -1.44
>> seconds (positive is fast)
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: No  received
>> from console
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: DMPAFT try #1; error:
>> No  received from Vantage console
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: No  received
>> from console
>>
>> Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: DMPAFT try #2; error:
>> No  received from Vantage c

[weewx-user] Upgrade issue 3.8.2 to 3.9.1

2019-04-06 Thread colin . larsen
Hi all

Just upgraded my installation as above. The hardware is WeatherDuino 
emulating the Davis comms protocol. On a previous occasion I had an issue 
which I think was similar to the errors below and was asked to use an 
updated engine.py file - which fixed the problem. After the upgrade I had 
to once again copy over the "new" engine.py to sort out this error. I'm not 
sure if the fix I was supplied was supposed to be rolled through to the 
3.9.1 upgrade? Log below of the error.

Cheers
Colin

Apr  7 11:57:16 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...

Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Initializing weewx 
version 3.9.1

Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]

Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Platform 
Linux-4.14.71-v7+-armv7l-with-debian-9.4

Apr  7 11:57:17 raspberrypi weewx[21102]: engine: Locale is 'en_NZ.UTF-8'

Apr  7 11:57:17 raspberrypi weewx[21102]: engine: pid file is 
/var/run/weewx.pid

Apr  7 11:57:17 raspberrypi weewx[21090]: Starting weewx weather system: 
weewx.

Apr  7 11:57:17 raspberrypi systemd[1]: Started LSB: weewx weather system.

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Using configuration file 
/etc/weewx/weewx.conf

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Loading station type 
Vantage (weewx.drivers.vantage)

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: StdConvert target unit is 
0x10

Apr  7 11:57:17 raspberrypi weewx[21106]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=software, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
altimeter=prefer_hardware, cloudbase=prefer_hardware

Apr  7 11:57:17 raspberrypi weewx[21106]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Archive will use data 
binding wx_binding

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Record generation will be 
attempted in 'software'

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Using archive interval of 
300 seconds (software record generation)

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'

Apr  7 11:57:17 raspberrypi weewx[21106]: manager: Starting backfill of 
daily summaries

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: StationRegistry: Station 
will be registered.

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: Wunderground: Posting not 
enabled.

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: PWSweather: Posting not 
enabled.

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: CWOP: Data for station 
ZL2ARL will be posted

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: WOW: Posting not enabled.

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: AWEKAS: Posting not 
enabled.

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: service version is 
0.18rc1

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: binding to loop

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: topic is 
weather/41south

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: desired unit system 
is METRIC

Apr  7 11:57:17 raspberrypi weewx[21106]: restx: MQTT: data will be 
uploaded to mqtt://192.168.20.121:1883/

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Starting up weewx version 
3.9.1

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Clock error is -1.44 
seconds (positive is fast)

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: No  received from 
console

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: DMPAFT try #1; error: No 
 received from Vantage console

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: No  received from 
console

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: DMPAFT try #2; error: No 
 received from Vantage console

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: No  received from 
console

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: DMPAFT try #3; error: No 
 received from Vantage console

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: No  received from 
console

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: DMPAFT try #4; error: No 
 received from Vantage console

Apr  7 11:57:17 raspberrypi weewx[21106]: vantage: DMPAFT max tries (4) 
exceeded.

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Main loop exiting. 
Shutting engine down.

Apr  7 11:57:17 raspberrypi weewx[21106]: engine: Caught WeeWxIOError: Max 
tries exceeded while getting archive data.

Apr  7 11:57:17 raspberrypi weewx[21106]:   Waiting 60 seconds then 
retrying...

Apr  7 11:58:02 raspberrypi systemd[1]: Stopping LSB: weewx weather 
system...

-- 
You received this messa

Re: [weewx-user] Display UV as graph in Belchertown skin

2019-03-20 Thread Colin Larsen
Version sounds like it's going to be awesome! Not that it isn't fabulous
now :)

On Thu, 21 Mar 2019, 08:57 Pat,  wrote:

> Very true. Version 1.0 allows more custom control over the charts. Hoping
> to get that out in the next few weeks
>
> On Tuesday, March 19, 2019 at 2:17:33 PM UTC-4, Colin Larsen wrote:
>>
>> Not currently, but keep an eye out for version 1.0. I think the
>> enhancements scheduled to roll out may make that possible, but I'm not
>> 100%  sure so don't guote me :)
>>
>> Colin
>>
>> On Wed, 20 Mar 2019, 04:55 G400,  wrote:
>>
>>> I have tried to find information about displaying UV measurements as a
>>> graph in the documentation, but I can't find any.
>>> Is this possible?
>>>
>>> --
>>> 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.
>

-- 
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] Display UV as graph in Belchertown skin

2019-03-19 Thread Colin Larsen
Not currently, but keep an eye out for version 1.0. I think the
enhancements scheduled to roll out may make that possible, but I'm not
100%  sure so don't guote me :)

Colin

On Wed, 20 Mar 2019, 04:55 G400,  wrote:

> I have tried to find information about displaying UV measurements as a
> graph in the documentation, but I can't find any.
> Is this possible?
>
> --
> 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] Re: Belchertown skin 0.9 now available

2019-03-01 Thread Colin Larsen
Yep, all good as far as I can tell, no errors. I see that the Darksky date
format is correct for me now too, not sure when you sorted that but thanks!
I may use that for a while again.

On Sat, Mar 2, 2019 at 3:36 PM Colin Larsen  wrote:

> Done, will let you know in under 5 minutes :)
>
> On Sat, Mar 2, 2019 at 3:33 PM Pat  wrote:
>
>> Colin, Yes. Scroll back a bit in this thread there's 2 links I sent Rich
>> to update to. Try that.
>>
>> Johannes, I'm working on a fix for your report too
>>
>> --
>> 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.


  1   2   3   >