Re: [weewx-user] Simple ObserverIP plugin that works well

[Pat]

I don't know why I did either :-) 

Happy to change it, and also Doug, I'm happy to include your changes as an 
update if they've been working for you. It could help others in the future.

On Sunday, November 24, 2019 at 12:08:45 PM UTC-5, Thomas Keffer wrote:
>
> Credit goes 100% to Pat O'Brian. I don't know why he put my name on the 
> driver!
>
> -tk
>
> On Sun, Nov 24, 2019 at 8:57 AM Doug Braun  > wrote:
>
>> Hello,
>>
>> A while ago I did some changes to Pat O'Brian's version of Tom Keffer's 
>> ObserverIP plugin.  It works by "scraping" the data from the ObserverIP's 
>> public web page.
>> This technique has been considered flaky, but I found a simple fix for 
>> the hangups and crashes:  every 24 hours the driver reboots the ObserverIP.
>> The driver has been working flawlessly for me for almost a year.
>>
>> I have attached the .py file, and you can also get it from here:  
>> http://dougbraun.com/software/observerip_scraper_py.txt
>>
>> Doug
>>
>> -- 
>> You received this message because you are 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/8a077335-3f0c-4ac8-a6e4-7521635691af%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/8a077335-3f0c-4ac8-a6e4-7521635691af%40googlegroups.com?utm_medium=email_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/31a36c76-699e-4eea-a84c-b3fb464394cb%40googlegroups.com.

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

[Pat]

Kike, so far so good with my testing in the 1.1 beta release. I have not 
committed it to my development GitHub branch yet because I still need to 
work out how to get the dark mode to show the gradients. 

On Friday, October 25, 2019 at 8:18:29 AM UTC-4, Kike .Asekas wrote:
>
> You're right. I had not taken into account the light and dark mode. You 
> have to change the color, at least for the dark mode. As is the 
> transition is not seen. I put the colors at the beginning of the 
> run(self) method and in weewx.conf I created 2 new variables, plotDayNight 
> to enable or disable it and daynight_gradient for the number of bands of 
> the gradient.
>
> El miércoles, 23 de octubre de 2019, 16:05:08 (UTC+2), Pat escribió:
>>
>> Looking at it now and it looks great. Quite a bit of work to figure this 
>> out. 
>>
>> I may change the config to be in graphs.conf so there is granular control 
>> on the plot bands- will think about this. 
>>
>> Will the color bands change based on light/dark mode? Or is the selected 
>> color ok for both site modes?
>>
>>
>> On Wednesday, October 23, 2019 at 8:35:11 AM UTC-4, Kike .Asekas wrote:
>>>
>>> I send you the files here. The configuration has two parameters.
>>> plotDayNight and daynight_gradient. The first is to activate or 
>>> deactivate it and the second is the number of gradient bands that by 
>>> default is 20 as in plotgen.py.
>>> The changes are basically from line 1237 at belchertown.js.tmpl and line 
>>> 1247 from belchertown.py, although there are other lines.
>>>
>>> El martes, 22 de octubre de 2019, 14:58:12 (UTC+2), Pat escribió:
>>>>
>>>> Great thanks. You can try the GitHub but if that confuses you then you 
>>>> can just attach the files here and I can try to figure it out when I have 
>>>> some time. 
>>>>
>>>> On Tuesday, October 22, 2019 at 8:52:37 AM UTC-4, Kike .Asekas wrote:
>>>>>
>>>>> What I did was adapt the renderDayNight function of genplot.py to get 
>>>>> the timestamps of dawn and dusk and with those timestamps write plotBands 
>>>>> (HighCharts function) in xAxis in the json.
>>>>> The code already has the possibility to activate them or not. It 
>>>>> takes about a second on the daily chart in a rpi 2b + to paint them.
>>>>> I am watching the github desktop program so I can send it to you. I 
>>>>> guess you will have to make some changes, I don't dominate much python or 
>>>>> js.
>>>>>
>>>>> El sábado, 19 de octubre de 2019, 22:26:17 (UTC+2), Pat escribió:
>>>>>>
>>>>>> Hi Kike, this looks very interesting! Perhaps I can add it as a skin 
>>>>>> option to enable/disable it. How did you do it?
>>>>>>
>>>>>> On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas wrote:
>>>>>>>
>>>>>>> Hi, Pat. I wanted to make a contribution to such an impressive 
>>>>>>> skin, but I don't know very well how to do it. If you are 
>>>>>>> interested tell me how.
>>>>>>> They are the transitions between night and day in the graphics.
>>>>>>>
>>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather 
>>>>>>> Conditions(1).png]
>>>>>>>
>>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather 
>>>>>>> Conditions(2).png]
>>>>>>>
>>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.png]
>>>>>>>
>>>>>>>
>>>>>>>

-- 
You received this message because you are subscribed to the Google 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/fdcce113-96ed-4fa7-86f7-2b4f5b56c769%40googlegroups.com.

Re: [weewx-user] Not archiving Signal Quality (rxCheckPercent) data

[Pat]

I wasn't sure which way to tackle this - in the end I decided that the 
console should track rxCheckPercent, and it would be easier to have weewx 
calculate wind direction. This is because different models of Vantage have 
different ways to calculate the rxCheckPercent. Seemed too complicated to 
replicate.

Thanks to Tom's help with this one, this was easier than I thought. When 
the archive runs, weewx downloads the archive off the console. Then this 
extension deletes the wind data from that archive. By way of how weewx 
works, the weewx wind direction gets re-inserted into the archive from the 
accumulator. Easier than I thought!

If weewx is offline for a certain period of time, it will download the 
archive off the console as a catchup. In this case then the windDir from 
the console will be used. Once a loop is established then the extension 
will use weewx's method of calculating windDir. 

I did add a quick check in the extension to make sure the [Station] --> 
station_type = Vantage because in my testing I was bouncing back and forth 
between drivers. This also makes sure you're not deleting wind direction 
from another driver. If you want to run this on a system that isn't running 
Vantage, then you can remove the check within the extension easily. 

I've been testing it for a few days and it seems pretty good. 


   1. Have a backup of anything and everything. Your database, your weewx 
   folder, your extensions, everything! I'm don't want to be responsible if 
   something goes sideways.
   2. Add the attached extension to your bin/user folder. 
   3. Set your [StdArchive] --> record_generation setting back to hardware
   4. Update the data_services setting here: [Engine] --> [[Services]] 
   --> data_services = user.deleteVantageWindDir.DeleteWindDir
   5. Restart weewx




On Sunday, October 27, 2019 at 6:30:55 PM UTC-4, Pat wrote:
>
> I recently picked up a 2nd hand Weatherlink IP for my Davis VP2 console 
> and have been running it on a test weewx instance. I'm now facing this same 
> challenge where I don't like the way Davis archives wind direction, but I 
> lose rxCheckPercent when switching to software record generation. 
>
> I agree with you that it would be nice to be able to choose where each 
> datum comes from (like windDir = [hardware|software|prefer_hardware]), 
> but since that's not possible I'll look into forking the vantage driver and 
> adding in the rxCheckPercent method from the Meteostick driver and see if 
> that helps bridge the gap in this specific use case.
>
>
> On Wednesday, September 25, 2019 at 10:02:27 PM UTC-4, Thomas Keffer wrote:
>>
>> Looking through the Meteostick driver, it seems to emit rxCheckPercent 
>> data on a running basis in its LOOP packets (not archive packets). These 
>> would then get stored in the WeeWX accumulators, then extracted as part of 
>> the software record generation.
>>
>> That is certainly a reasonable approach:  modify the Vantage driver to 
>> keep track of dropped packets, and emit the results in the LOOP packets.
>>
>> I'm not going to do it, but, as always, pull requests are welcome! :-)
>>
>> -tk
>>
>>
>>
>> On Wed, Sep 25, 2019 at 6:49 PM Pat  wrote:
>>
>>> I'm not sure how the Davis driver works, but with the Meteostick driver 
>>> it's able to calculate rxCheckPercent 
>>> <https://github.com/matthewwall/weewx-meteostick/blob/master/bin/user/meteostick.py#L404-L413>
>>>  
>>> based on number of RF packets received over a known interval 
>>> <https://github.com/matthewwall/weewx-meteostick/blob/master/bin/user/meteostick.py#L356-L373>
>>>  
>>> and doing that math. Since I use the Meteostick driver for my Davis 
>>> station, I'm set to software generation and I get the rxCheckPercent. I 
>>> wonder if there's a way to incorporate this bit of code into a Davis driver 
>>> fork? 
>>>
>>> Could be a large project (which I'm not volunteering for) but thought 
>>> I'd at least mention it and link to the code.
>>>
>>>
>>> On Monday, September 23, 2019 at 5:47:02 PM UTC-4, Thomas Keffer wrote:
>>>>
>>>> Sorry, but the value of rxCheckPercent comes only from the console, and 
>>>> then only in archive records (not LOOP packets). If you disable hardware 
>>>> record generation, you lose it.
>>>>
>>>> It would be a nice feature to be able to pick and chose where each 
>>>> datum in the archive record comes from, but, unfortunately, that's not the 
>>>> way WeeWX works now.
>>>>
>>>> -tk
>>>>
>>>> On Mon, Sep 23, 2019 at 9:46 AM Erick Dorsett  
>>>> wrote:
>>

Re: [weewx-user] Not archiving Signal Quality (rxCheckPercent) data

[Pat]

I recently picked up a 2nd hand Weatherlink IP for my Davis VP2 console and 
have been running it on a test weewx instance. I'm now facing this same 
challenge where I don't like the way Davis archives wind direction, but I 
lose rxCheckPercent when switching to software record generation. 

I agree with you that it would be nice to be able to choose where each 
datum comes from (like windDir = [hardware|software|prefer_hardware]), but 
since that's not possible I'll look into forking the vantage driver and 
adding in the rxCheckPercent method from the Meteostick driver and see if 
that helps bridge the gap in this specific use case.


On Wednesday, September 25, 2019 at 10:02:27 PM UTC-4, Thomas Keffer wrote:
>
> Looking through the Meteostick driver, it seems to emit rxCheckPercent 
> data on a running basis in its LOOP packets (not archive packets). These 
> would then get stored in the WeeWX accumulators, then extracted as part of 
> the software record generation.
>
> That is certainly a reasonable approach:  modify the Vantage driver to 
> keep track of dropped packets, and emit the results in the LOOP packets.
>
> I'm not going to do it, but, as always, pull requests are welcome! :-)
>
> -tk
>
>
>
> On Wed, Sep 25, 2019 at 6:49 PM Pat > 
> wrote:
>
>> I'm not sure how the Davis driver works, but with the Meteostick driver 
>> it's able to calculate rxCheckPercent 
>> <https://github.com/matthewwall/weewx-meteostick/blob/master/bin/user/meteostick.py#L404-L413>
>>  
>> based on number of RF packets received over a known interval 
>> <https://github.com/matthewwall/weewx-meteostick/blob/master/bin/user/meteostick.py#L356-L373>
>>  
>> and doing that math. Since I use the Meteostick driver for my Davis 
>> station, I'm set to software generation and I get the rxCheckPercent. I 
>> wonder if there's a way to incorporate this bit of code into a Davis driver 
>> fork? 
>>
>> Could be a large project (which I'm not volunteering for) but thought I'd 
>> at least mention it and link to the code.
>>
>>
>> On Monday, September 23, 2019 at 5:47:02 PM UTC-4, Thomas Keffer wrote:
>>>
>>> Sorry, but the value of rxCheckPercent comes only from the console, and 
>>> then only in archive records (not LOOP packets). If you disable hardware 
>>> record generation, you lose it.
>>>
>>> It would be a nice feature to be able to pick and chose where each datum 
>>> in the archive record comes from, but, unfortunately, that's not the way 
>>> WeeWX works now.
>>>
>>> -tk
>>>
>>> On Mon, Sep 23, 2019 at 9:46 AM Erick Dorsett  
>>> wrote:
>>>
>>>> I recently installed weewx on a Pi to use with my ancient Davis Vantage 
>>>> Pro.  In order to get the winds to report actual degrees instead of 
>>>> quantized to the cardinals, I had to set  "record_generation = software" 
>>>> in 
>>>> the weewx.conf file.  However, after I did that, the data point for signal 
>>>> quality (rxCheckPercent) is no longer archived in weewx.sdb. 
>>>>
>>>> I use rxCheckPercent data for a bunch of reasons.  How do I get it back?
>>>>
>>>>
>>>> -- 
>>>> You received this message because you are 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/e564d660-ec57-4887-a74b-a28969ebf374%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/e564d660-ec57-4887-a74b-a28969ebf374%40googlegroups.com?utm_medium=email_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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/09aa1d9c-1e40-4dbd-bcb0-9e4184ecd255%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/09aa1d9c-1e40-4dbd-bcb0-9e4184ecd255%40googlegroups.com?utm_medium=email_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/66ffe7f2-1755-4328-a390-025f8a82aff1%40googlegroups.com.

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Pat]

Check my previous email. You need to tell mqtt extension what you're 
looking for. The skin gets its values from mqtt. 

On Saturday, October 26, 2019 at 8:45:18 AM UTC-4, Matt wrote:
>
> Yes, I realise that, but my weewx.conf is the same as the section you 
> highlight but I'm still not seeing celcius and mph...
>
> This is my current weewx.conf
>
> [[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 = foot# Options are 'foot' or 'meter'
>group_degree_day = degree_C_day# Options are 
> 'degree_F_day' or 'degree_C_day'
>group_pressure = mbar# 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 = mile_per_hour# Options are 
> 'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
>group_speed2 = mile_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'
>
>
> On Saturday, 26 October 2019 13:38:22 UTC+1, Pat wrote:
>>
>> A lot of these items are covered in the documentation 
>> <https://github.com/poblabs/weewx-belchertown#table-of-contents>. Check 
>> out this section 
>> <https://github.com/poblabs/weewx-belchertown#using-metric>. 
>>
>>
>> On Saturday, October 26, 2019 at 8:36:24 AM UTC-4, Matt wrote:
>>>
>>> Superb! That worked. Thank you very much.  I am in the UK and use 
>>> degrees Celcius and Miles per hour.  What should I set unit_system to 
>>> (METRIC gives me celcius but kmh, US gives me fahrenheit and miles per 
>>> hour)?
>>>
>>> On Saturday, 26 October 2019 12:22:41 UTC+1, Pat wrote:
>>>>
>>>> Try changing mqtt_websockets_topic to weather/loop
>>>
>>>

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

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Pat]

Ah, sorry, my mistake. I mis-read your question. 

You'll want to configure the MQTT extension to send the units you want. So 
you'd want something like shown in this question 
<https://github.com/poblabs/weewx-belchertown/issues/23#issuecomment-440529099>
.

[[MQTT]]
... your other mqtt config options here ...
[[[inputs]]]
windSpeed
name = windSpeed_mph
units = mile_per_hour


The mqtt extension documentation 
<https://github.com/weewx/weewx/wiki/mqtt#examples> has more info too.


On Saturday, October 26, 2019 at 8:38:22 AM UTC-4, Pat wrote:
>
> A lot of these items are covered in the documentation 
> <https://github.com/poblabs/weewx-belchertown#table-of-contents>. Check 
> out this section 
> <https://github.com/poblabs/weewx-belchertown#using-metric>. 
>
>
> On Saturday, October 26, 2019 at 8:36:24 AM UTC-4, Matt wrote:
>>
>> Superb! That worked. Thank you very much.  I am in the UK and use degrees 
>> Celcius and Miles per hour.  What should I set unit_system to (METRIC gives 
>> me celcius but kmh, US gives me fahrenheit and miles per hour)?
>>
>> On Saturday, 26 October 2019 12:22:41 UTC+1, Pat wrote:
>>>
>>> Try changing mqtt_websockets_topic to weather/loop
>>
>>

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

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Pat]

A lot of these items are covered in the documentation 
<https://github.com/poblabs/weewx-belchertown#table-of-contents>. Check out 
this section <https://github.com/poblabs/weewx-belchertown#using-metric>. 


On Saturday, October 26, 2019 at 8:36:24 AM UTC-4, Matt wrote:
>
> Superb! That worked. Thank you very much.  I am in the UK and use degrees 
> Celcius and Miles per hour.  What should I set unit_system to (METRIC gives 
> me celcius but kmh, US gives me fahrenheit and miles per hour)?
>
> On Saturday, 26 October 2019 12:22:41 UTC+1, Pat wrote:
>>
>> Try changing mqtt_websockets_topic to weather/loop
>
>

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

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Pat]

Try changing mqtt_websockets_topic to weather/loop

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

[weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Pat]

Your host needs to be the IP of your broker. Not localhost. 


On Friday, October 25, 2019 at 3:57:10 PM UTC-4, Matt wrote:
>
> I noticed a typo myself...now changed the websockets port and put the host 
> and topic in quotes, but still not connecting...
>
> # MQTT Websockets defaults
>mqtt_websockets_enabled = 1
>mqtt_websockets_host = "localhost"
>mqtt_websockets_port = 9001
>mqtt_websockets_ssl = 0
>mqtt_websockets_topic = "weather"
>disconnect_live_website_visitor = 180
>
>
>
> On Friday, 25 October 2019 19:57:45 UTC+1, Matt wrote:
>>
>> Hi,
>>
>> I followed the instructions in 
>> https://github.com/poblabs/weewx-belchertown to install an MQTT broker 
>> and subscribe to the weather data.  It's working according to the logs...
>>
>> Weewx syslog
>>
>> Oct 25 19:49:13 weatherpi weewx[3082]: restx: MQTT: Published record 
>> 2019-10-25 19:49:13 BST (1572029353)
>> Oct 25 19:49:29 weatherpi weewx[3082]: restx: MQTT: Published record 
>> 2019-10-25 19:49:29 BST (1572029369)
>> Oct 25 19:49:44 weatherpi weewx[3082]: restx: MQTT: Published record 
>> 2019-10-25 19:49:44 BST (1572029384)
>> Oct 25 19:50:01 weatherpi weewx[3082]: restx: MQTT: Published record 
>> 2019-10-25 19:50:00 BST (1572029400)
>> Oct 25 19:50:17 weatherpi weewx[3082]: restx: MQTT: Published record 
>> 2019-10-25 19:50:16 BST (1572029416)
>>
>> Mosquitto log
>>
>> 1572029465: New connection from ::1 on port 1883.
>> 1572029465: New client connected from ::1
>>  as weewx_7f9ef501 (c1, k60, u'pi').
>> 1572029465: Client weewx_7f9ef501 disconnected.
>> 1572029481: New connection from ::1 on port 1883.
>> 1572029481: New client connected from ::1
>>  as weewx_65035d79 (c1, k60, u'pi').
>> 1572029481: Client weewx_65035d79 disconnected.
>> 1572029497: New connection from ::1 on port 1883.
>> 1572029497: New client connected from ::1
>>  as weewx_29b0c150 (c1, k60, u'pi').
>> 1572029497: Client weewx_29b0c150 disconnected.
>> 1572029513: New connection from ::1 on port 1883.
>>
>> weewx.conf
>>
>> [[MQTT]]
>> server_url = mqtt://pi:xxx@localhost:1883
>> topic = weather
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>> log_failure = true
>> log_success = true
>>
>> skin.conf
>>
>> # MQTT Websockets defaults
>> mqtt_websockets_enabled = 1
>> mqtt_websockets_host = localhost
>> mqtt_websockets_port = 1883
>> mqtt_websockets_ssl = 0
>> mqtt_websockets_topic = weather
>> disconnect_live_website_visitor = 180
>>
>> But the webpage constantly says...
>>
>> [image: Untitled.png]
>>
>> I've been over and over the config, re-writing, adding quotes, you name 
>> it I've tried it but still no success.  Can any bright spark see something 
>> obvious that's wrong...please!!
>>
>> Many thanks,
>>
>> Matt
>>
>

-- 
You received this message because you are subscribed to the Google 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/b0004563-6cdb-480a-a8e4-64e86f65784e%40googlegroups.com.

[weewx-user] Re: Does weewx output conditions as text?

[Pat]

Not that I'm aware of. I've been using DarkSky to give me that forecasting 
capability in my skin.

On Wednesday, October 23, 2019 at 6:34:15 AM UTC-4, Andy Hudson-Smith wrote:
>
> Morning - Just wondering if there is a way to output a text string for 
> conditions - ie raining, partly cloudy etc? I cant seem to find one but 
> thought i might be missing something basic so thought i would ask here,
>
> Andy
>

-- 
You received this message because you are subscribed to the Google 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/d16e66cc-56db-4708-bfa3-057dbba71c51%40googlegroups.com.

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

[Pat]

Looking at it now and it looks great. Quite a bit of work to figure this 
out. 

I may change the config to be in graphs.conf so there is granular control 
on the plot bands- will think about this. 

Will the color bands change based on light/dark mode? Or is the selected 
color ok for both site modes?


On Wednesday, October 23, 2019 at 8:35:11 AM UTC-4, Kike .Asekas wrote:
>
> I send you the files here. The configuration has two parameters.
> plotDayNight and daynight_gradient. The first is to activate or deactivate 
> it and the second is the number of gradient bands that by default is 20 as 
> in plotgen.py.
> The changes are basically from line 1237 at belchertown.js.tmpl and line 
> 1247 from belchertown.py, although there are other lines.
>
> El martes, 22 de octubre de 2019, 14:58:12 (UTC+2), Pat escribió:
>>
>> Great thanks. You can try the GitHub but if that confuses you then you 
>> can just attach the files here and I can try to figure it out when I have 
>> some time. 
>>
>> On Tuesday, October 22, 2019 at 8:52:37 AM UTC-4, Kike .Asekas wrote:
>>>
>>> What I did was adapt the renderDayNight function of genplot.py to get 
>>> the timestamps of dawn and dusk and with those timestamps write plotBands 
>>> (HighCharts function) in xAxis in the json.
>>> The code already has the possibility to activate them or not. It takes 
>>> about a second on the daily chart in a rpi 2b + to paint them.
>>> I am watching the github desktop program so I can send it to you. I 
>>> guess you will have to make some changes, I don't dominate much python or 
>>> js.
>>>
>>> El sábado, 19 de octubre de 2019, 22:26:17 (UTC+2), Pat escribió:
>>>>
>>>> Hi Kike, this looks very interesting! Perhaps I can add it as a skin 
>>>> option to enable/disable it. How did you do it?
>>>>
>>>> On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas wrote:
>>>>>
>>>>> Hi, Pat. I wanted to make a contribution to such an impressive skin, 
>>>>> but I don't know very well how to do it. If you are interested tell 
>>>>> me how.
>>>>> They are the transitions between night and day in the graphics.
>>>>>
>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(1).png]
>>>>>
>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(2).png]
>>>>>
>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.png]
>>>>>
>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google 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/b1d990fc-84a5-42bb-9a4f-1a5b3c34a361%40googlegroups.com.

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

[Pat]

Great, thanks. I will take a look at this when I can. Some of the variable 
names will probably change to match the skin variables, but this is a very cool 
addition.

-- 
You received this message because you are subscribed to the Google 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/666eeef0-1465-4e16-8fd9-796e075dbfb1%40googlegroups.com.

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

[Pat]

Great thanks. You can try the GitHub but if that confuses you then you can 
just attach the files here and I can try to figure it out when I have some 
time. 

On Tuesday, October 22, 2019 at 8:52:37 AM UTC-4, Kike .Asekas wrote:
>
> What I did was adapt the renderDayNight function of genplot.py to get the 
> timestamps of dawn and dusk and with those timestamps write plotBands 
> (HighCharts function) in xAxis in the json.
> The code already has the possibility to activate them or not. It takes 
> about a second on the daily chart in a rpi 2b + to paint them.
> I am watching the github desktop program so I can send it to you. I guess 
> you will have to make some changes, I don't dominate much python or js.
>
> El sábado, 19 de octubre de 2019, 22:26:17 (UTC+2), Pat escribió:
>>
>> Hi Kike, this looks very interesting! Perhaps I can add it as a skin 
>> option to enable/disable it. How did you do it?
>>
>> On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas wrote:
>>>
>>> Hi, Pat. I wanted to make a contribution to such an impressive skin, 
>>> but I don't know very well how to do it. If you are interested tell me 
>>> how.
>>> They are the transitions between night and day in the graphics.
>>>
>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(1).png]
>>>
>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(2).png]
>>>
>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.png]
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google 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/b3e38cde-46af-4149-82db-9f85a25fcba9%40googlegroups.com.

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

[Pat]

I don't store a copy of the translated files. I leave that up to the site 
owners to use skin.conf to translate themselves. Often I am adding new 
features and can't maintain individual language files.

That said, this issue on the Belchertown GitHub page 
 has a few people 
who have translated into French and Spanish.


On Monday, October 21, 2019 at 4:56:03 PM UTC-4, Francesco Scaramella wrote:
>
> what parts of the skin do you need to translate for customization in your 
> own language??
>

-- 
You received this message because you are subscribed to the Google 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/7a4a8189-3bb6-441f-8486-fe0f5dc53230%40googlegroups.com.

[weewx-user] Re: Highcharts - yAxis 0 value at bottom

[Pat]

I see that an empty Belchertown rain chart will have the y axis 0 at the 
bottom of the chart. So I played with jsfiddle for a few minutes and think 
I have 2 ideas for you. Option #1 is the easiest fix. 

There's 2 bits to it that may work for you:

1. If you split your observations so that they use both yAxis = 0 and yAxis 
= 1, then it'll force the 0 to the bottom of the chart. Here you can see I 
have removed all yAxis options, except left the series on opposite yAxis 
. 
2. Or you can try a manual override with like the rain code is doing with 
minRange 
.
 You'll 
need to define also the min = 0 or the chart won't be at the bottom. Here 
is a chart with the minRange and min defined 
 in yAxis. and ... Here you 
can see what I mean  if you 
leave min omitted. 

Making minRange and min = 0 a global option is not advised since some 
charts will go into the negative - like outTemp. Setting the min to 0 will 
hide negative values. 


On Saturday, October 19, 2019 at 2:14:00 AM UTC-4, Xant wrote:
>
>
> Even if placing "yAxis_min = 0" on Graphs.conf of Belchertown skin, 
> Highcharts place a line right at the middle of the chart, instead of a line 
> at the bottom when value is at timeframe is all "zero". Also of much 
> distress when graph actually refers to "Area", then Highchart paint solid 
> color under line.
>
>
>
>
> This seems a "normal" behaviour for Highcharts, as many also complaining (
> https://stackoverflow.com/questions/13991873/highcharts-ensure-y-axis-0-value-is-at-chart-bottom).
>  
> I tried many combinations and options into Graphs.conf, at no solution.
>
> Suggestions?
>
> 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/27635336-57f8-4990-8afc-acc67ee558a3%40googlegroups.com.

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

[Pat]

Hi Kike, this looks very interesting! Perhaps I can add it as a skin option 
to enable/disable it. How did you do it?

On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas wrote:
>
> Hi, Pat. I wanted to make a contribution to such an impressive skin, but 
> I don't know very well how to do it. If you are interested tell me how.
> They are the transitions between night and day in the graphics.
>
> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(1).png]
>
> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(2).png]
>
> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.png]
>
>
>

-- 
You received this message because you are subscribed to the Google 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/9b0dc068-8f68-45af-89db-779bcf38b7fd%40googlegroups.com.

[weewx-user] Re: CSV extension writing bad data

[Pat]

It's probably not too bad to fork the extension and add the CachedValues 
method as seen in the restx extension 
 
(read: 
copy/paste). Once tested and working this should satisfy option 3.

Other important information found for CachedValues are here 
, 
and here 
. 
You can see on every loop it updates the cached dictionary of those values 
with the update() function. Then it outputs the observations that just came 
in, plus the missing ones from Cached values, to the LOOP with 
the get_packet() function.

On Wednesday, October 16, 2019 at 12:03:41 PM UTC-4, Dave wrote:
>
> On Tuesday, October 15, 2019 at 11:39:03 PM UTC-7, gjr80 wrote:
>>
>> Hi,
>>
>> The problem you are experiencing is due an incompatibility between your 
>> station emitting what is known as partial loop packets (ie not all obs are 
>> included in all loop packets) and the mode in which you are operating the 
>> csv extension.
>>
>> You are running the CSV extension such that it emits loop data to file 
>> and includes a header line. Subsequent loop packets are appended to the 
>> file. The header line is only written (1) when the csv output file is first 
>> created or (2) on each loop packet but only if mode = 'overwrite'. In 
>> your case you are using 'append' mode so the header line is only written 
>> when the csv output file is first created. Think now of the situation where 
>> the first loop packet has, say, observation outTemp but the next loop 
>> packet does not. So the header line is written and includes 'outTemp' in 
>> the relevant place. The line of csv data for that packet is written to file 
>> and each field matches with the header line. When the next loop packet is 
>> processed there is no outTemp field in the loop packet so nothing is 
>> written in outTemp's place in the line of csv data (well in fact something 
>> will be written it will be the next field if there is one). Consequently 
>> when your parser parses that line it expects to see outTemp data when in 
>> fact it sees the next value instead (perhaps it was outTempBatteryStatus) 
>> and hence you get nonsense values from your parser.
>>
>
> Thank you very much for this explanation. I am familiar with this idea but 
> It seems the behavior changed between 3.5.0 and 3.9.2. It used to write 
> each header line when mode was 'append'. Since part of the upgrade was 
> moving weewx to another server, I still have the old server's data and 
> binaries available. If you look in the weewx.csv for the 3.5.0 server:
>
>
> dateTime,altimeter,appTemp,barometer,channel,cloudbase,dewpoint,heatindex,humidex,inDewpoint,maxSolarRad,outHumidity,outTemp,rainRate,rssi,rxCheckPercent,sensor_battery,sensor_id,txTempBatteryStatus,usUnits,windSpeed,windchill
>
> 1571075730,None,71.4621394073,None,None,3276.5581345,56.6531442082,70.3,76.0399971396,None,None,62,70.3,0,3,100.0,0,1228,0,1,1.65011333748,70.3
>
> dateTime,altimeter,appTemp,barometer,channel,cloudbase,dewpoint,heatindex,humidex,inDewpoint,maxSolarRad,rain,rainRate,rain_total,rssi,rxCheckPercent,sensor_battery,sensor_id,txTempBatteryStatus,usUnits,windDir,windSpeed,windchill
>
> 1571075748,None,None,None,None,None,None,None,None,None,None,0.0,0,110.4646,3,100.0,0,1228,0,1,180.0,2.16448441021,None
>
> dateTime,altimeter,appTemp,barometer,channel,cloudbase,dewpoint,heatindex,humidex,inDewpoint,inTemp,maxSolarRad,outHumidity,outTemp,pressure,rainRate,rssi,rxCheckPercent,sensor_battery,sensor_id,txTempBatteryStatus,usUnits,windSpeed,windchill
>
> 1571075766,29.9423211803,71.4621394073,29.9470837144,None,3276.5581345,56.6531442082,70.3,76.0399971396,None,74.39,None,62,70.3,29.7622563497,0,3,100.0,0,1228,0,1,1.65011333748,70.3
>
>
> ...it's writing a header line each time, even in 'append' mode. My config 
> for that server was:
>
> [CSV]
> filename = /var/db/weewx/weewx.csv
> header = true
>
>
> So it's clear that something changed to exhibit the behavior you describe 
> above instead of the old behavior.
>
>
>> Solutions, there are a few possibilities:
>>
>> 1. use 'overwrite' mode instead of append, in this mode the header line 
>> is written each time a packet is processed but there is only ever one line 
>> in your csv output file
>> 2. delete the csv output file after each loop packet is read by your 
>> parser (this is a pretty lame solution)
>> 3. rewrite the csv extension to cache loop packet data so that a 
>> 'complete' loop packet is written each time
>> 4. emit archive record data rather than loop packet data
>>
>
> IMO option 3 provides the best solution as there's zero way to parse a 
> partial packet without keys for the values. ;) This would also restore my 
> nagios plugin's proper functionality. Unfortunately, I've too little 
> experience in python to attempt 3 in a public software 

[weewx-user] Re: CSV extension writing bad data

[Pat]

You're right. Not much here. What are your other skins (like Standard or 
Seasons) showing? Do they seem accurate?

On Tuesday, October 15, 2019 at 1:50:48 PM UTC-4, Dave wrote:
>
>
>
> On Tuesday, October 15, 2019 at 9:39:42 AM UTC-7, Pat wrote:
>>
>> I saw the debug, but didn't see any actual helpful debug output. That's 
>> why I asked for a syslog.
>
>
> Oct 15 08:09:55 myserver weewx[18438]: engine: Debug is 1
> Oct 15 08:09:55 myserver weewx[18438]: engine: Initializing engine
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service 
> weewx.engine.StdTimeSynch
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> weewx.engine.StdTimeSynch
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service 
> weewx.engine.StdConvert
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> weewx.engine.StdConvert
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service 
> weewx.engine.StdCalibrate
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> weewx.engine.StdCalibrate
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service 
> weewx.engine.StdQC
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> weewx.engine.StdQC
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> weewx.wxservices.StdWXCalculate
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service user.csv.CSV
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> user.csv.CSV
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service 
> weewx.engine.StdArchive
> Oct 15 08:09:55 myserver weewx[18438]: engine: Use LOOP data in hi/low 
> calculations: 1
> Oct 15 08:09:55 myserver weewx[18438]: manager: Daily summary version is 
> 2.0
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> weewx.engine.StdArchive
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service 
> weewx.engine.StdPrint
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> weewx.engine.StdPrint
> Oct 15 08:09:55 myserver weewx[18438]: engine: Loading service 
> weewx.engine.StdReport
> Oct 15 08:09:55 myserver weewx[18438]: engine: Finished loading service 
> weewx.engine.StdReport
> Oct 15 08:09:55 myserver weewx[18438]: engine: Station does not support 
> reading the time
> Oct 15 08:09:56 myserver weewx[18438]: acurite: Found station at bus= 
> device=
> Oct 15 08:09:56 myserver weewx[18438]: acurite: next read in 18 seconds
> Oct 15 08:10:14 myserver weewx[18438]: acurite: Found station at bus= 
> device=
> Oct 15 08:10:14 myserver weewx[18438]: acurite: next read in 18 seconds
>
>
> I dont think this is helpful, which is why I didn't post it. Nevertheless, 
> here it is. Hopefully I'm wrong. :)
>

-- 
You received this message because you are subscribed to the Google 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/b8100124-e94a-4958-a11c-2cd4e611f47f%40googlegroups.com.

[weewx-user] Re: CSV extension writing bad data

[Pat]

Answered my own question. The debug shows it's 0.10 which looks like it's 
the latest available <https://github.com/weewx/weewx/wiki/csv>. 

Sort of running out of options on why yours is acting differently than 
mine. Hopefully syslog has a clue or two. 


On Tuesday, October 15, 2019 at 12:39:42 PM UTC-4, Pat wrote:
>
> I saw the debug, but didn't see any actual helpful debug output. That's 
> why I asked for a syslog. 
>
> Also, I am assuming you're on the latest CSV extension version, but I 
> shouldn't assume anything. Are you on the latest CSV extension version?
>

-- 
You received this message because you are subscribed to the Google 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/a283abd6-58b4-4bf1-84a8-55522e8b913b%40googlegroups.com.

[weewx-user] Re: CSV extension writing bad data

[Pat]

I saw the debug, but didn't see any actual helpful debug output. That's why I 
asked for a syslog. 

Also, I am assuming you're on the latest CSV extension version, but I shouldn't 
assume anything. Are you on the latest CSV extension version?

-- 
You received this message because you are subscribed to the Google 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/e1e2ce1a-b477-4dd4-a550-483561d1599a%40googlegroups.com.

[weewx-user] Re: CSV extension writing bad data

[Pat]

I've never played with this extension, but I just installed it and copied 
your weewx.conf [CSV] settings. It appears to be working fine for me on 
3.9.2 - my outTemp field is correct (see below). It's 49F outside and 
that's what's in the CSV.

Is there anything in your syslog that would point to an error? Perhaps set 
debug = 1 in weewx.conf, restart and let it run for a few archive intervals 
and see if anything comes up. 

Are you running another skin to make sure that weewx is seeing your outTemp 
correctly? Ruling out a bad sensor?

What if you run weewxd manually 
and check that the LOOP packets are what you'd expect them to be?


# 
dateTime,maxSolarRad,outTemp,rainRate,txBatteryStatus,usUnits,windDir,windSpeed,windchill
1571103610,0.0,49.4,0,0,1,None,0.0,49.4
1571103612,0.0,0.0,0,0,1,None,0.0
1571103615,0.0,0.0,0,1,None,0.0
1571103617,0.0,0.0,0,0,1,None,0.0
1571103620,0.0,49.4,0,0,1,None,0.0,49.4
1571103625,0.0,0.0,0,1,None,0.0
1571103627,30.0690643936,47.1460416382,44.15,69.98,0.0,29.6138526645,0,1



On Monday, October 14, 2019 at 9:35:50 PM UTC-4, Dave wrote:
>
> I recently upgraded weewx to 3.9.2. Now it appears the CSV extension is 
> writing bad data. I like the fact that it stops writing the key line every 
> time but now the data doesn't match the key. 
>
> For those who might need a reminder, the key line looks like this:
> # 
> dateTime,altimeter,appTemp,barometer,channel,cloudbase,dewpoint,heatindex,humidex,inTemp,maxSolarRad,outHumidity,outTemp,outTempBatteryStatus,pressure,rainRate,rssi,rxCheckPercent,sensor_battery,sensor_id,usUnits,windSpeed,windchill
>
> Next you get lines of data like so:
>
>
> 1571077878,75.1909422213,None,3733.59877061,57.2421654093,72.9,78.9824045747,None,58,72.9,0,0,3,100.0,0,1228,1,None,0.0,72.9
>
> 1571077931,29.9314717722,None,76.19,None,0,29.7514624062,None,0,110.4646,3,100.0,0,1228,1,180.0,3.70760684504
>
> 1571077949,74.1763675742,None,3850.99831681,57.225607406,73.4,79.472688903,None,57,73.4,0,0,3,100.0,0,1228,1,2.67886214224,73.4
>
>
> Astute readers will note that "outTemp" is 3 degrees. This is southern 
> california. ;)
>
> I've no idea how to begin to debug this. A wee_debug info is attached. 
> Thanks in advance for any assistance. 
>

-- 
You received this message because you are subscribed to the Google 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/280a8908-1aae-4c0d-b22d-3b4d397c29cb%40googlegroups.com.

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

[Pat]

Xant, instead of another switch or skin option, if you wish to hide the 
forecast row, you can do so by adding this to the bottom of style.css

.forecastrow {
display:none;
}


This will hide that whole row for all versions of the website (desktop and 
mobile)


On Monday, October 7, 2019 at 7:45:10 PM UTC-4, Xant wrote:
>
>
> Hey Pat
>
> DarkSky 8 Day Forecast its interesting, but takes a lot of "real state", 
> specially when or if you check WeeWX/Belchertown from a mobile device. 
> Sure, there is an option in 'skin.conf' to turn it off, but by doing that, 
> the "current weather icon" on side on current Temp, and probably weather 
> warnings will go off too.
>
> I managed to turned the "2nd row" off, by tweaking the 'index.html.tmpl' 
> file. But would be interesting if you may add "another switch", to turn the 
> 2nd row off, while still keeping "current weather icon" and weather 
> warnings On.
>
> Or better yet, make "current weather icon" and weather warning 'skin 
> standard', while still keeping DarkSky 8 Day Forecast On/Off switch.
>
> Thank you always for B-skin,
> 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/710effef-225e-4090-908e-4474f82fcb87%40googlegroups.com.

[weewx-user] Re: Keeping every monthly/yearly statistics and plots

[Pat]

You can try the Belchertown skin as well. This can be installed in addition 
to w34 skin, sofaskin, etc. 

You can see on my own graphs page  
that I have graphs setup for this current year 
, one for last year 
, etc. It's easily 
customized so you can show a specific year, a specific day or a date range 
of your choosing.

You can download it here , 
and read about how to configure your charts in the wiki here 

. 

On Saturday, October 5, 2019 at 7:01:04 PM UTC-4, . fankyy wrote:
>
> Is there a built-in funcion/setting to keep the statistics and plots of 
> every single month/year (and week), in a way that the visitors can choose a 
> certain year and all plots from that year will appear? 
>
> Or is there a setting to auto-export e.g. the monthly plots at the end of 
> a month to, as an example "2019-05-temp.gif" or "2019-05-gust.gif"? 
>
> Always had that in wswin and somehow no one with weewx seems to have it. 
> And I couldnt find anything in the manual/wiki.
>
> Or is a database export plus highcharts the way to go?
>
> Thanks for any advice!
>
>

-- 
You received this message because you are subscribed to the Google 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/ce20150d-fa58-4e2d-b5d5-a66a76c19295%40googlegroups.com.

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

[Pat]

Please change your xaxis_categories 

 
to represent this change. 

>From the wiki:

> You will need to give the right labels, and do not expect all output to 
start with January. For example, if you start a new database in June, then 
you would use xaxis_categories = 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 
'Dec'. **It is up to you to provide the right labels for the data you're 
expecting. **

On Saturday, October 12, 2019 at 4:35:52 AM UTC-4, Stefan wrote:
>
> Hi.
> I added this extension. But now it starts in January instead of in July. I 
> have no weather data starting from January. Do I have to change something?
>
> [image: Unbenannt.JPG]
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks for your help
>
>
>>

-- 
You received this message because you are subscribed to the Google 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/fd48d77b-73e4-426b-80d0-bec3efa2d254%40googlegroups.com.

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

[Pat]

Take a look at Common Titles config options 
<https://github.com/poblabs/weewx-belchertown#common-titles-under-labels-section-to-change>
 
from the skin options documentation 
<https://github.com/poblabs/weewx-belchertown#skin-options>. 


On Thursday, October 10, 2019 at 3:24:31 PM UTC-4, Wiggytoo wrote:
>
> Maybe it is called something else, see attached.
>
> It says "My station weather conditions" below the logo and menu 
> "hamburger".
>
> This is the text I want to change.
>
> Gavin
>
> On Thu, 10 Oct 2019, 16:19 Pat, > 
> wrote:
>
>> It says "Great Coxwell, Oxon, UK Weather Conditions" for me. Maybe you 
>> have a conflict in skin.conf, or maybe try a hard reload in your browser?
>>
>> On Thursday, October 10, 2019 at 11:11:47 AM UTC-4, Wiggytoo wrote:
>>>
>>> Hi Pat,
>>>
>>> I may have missed something here but I have set this in weewx.conf
>>>
>>> site_title = "Great Coxwell Weather Conditions"
>>>
>>> But the website still shows the default
>>>
>>> www,wiggytoo.co.uk
>>>
>>> Anywhere I should look for my error?
>>>
>>> Gav
>>>
>>> On Saturday, 1 June 2019 17:57:56 UTC+1, 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 a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/VyVMEfuxClo/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/3e0ed132-1108-4062-8881-13c276970889%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/3e0ed132-1108-4062-8881-13c276970889%40googlegroups.com?utm_medium=email_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/da5d60ee-8b5e-48ca-acb1-aaa636037187%40googlegroups.com.

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

[Pat]

It says "Great Coxwell, Oxon, UK Weather Conditions" for me. Maybe you have 
a conflict in skin.conf, or maybe try a hard reload in your browser?

On Thursday, October 10, 2019 at 11:11:47 AM UTC-4, Wiggytoo wrote:
>
> Hi Pat,
>
> I may have missed something here but I have set this in weewx.conf
>
> site_title = "Great Coxwell Weather Conditions"
>
> But the website still shows the default
>
> www,wiggytoo.co.uk
>
> Anywhere I should look for my error?
>
> Gav
>
> On Saturday, 1 June 2019 17:57:56 UTC+1, 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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3e0ed132-1108-4062-8881-13c276970889%40googlegroups.com.

Re: [weewx-user] Re: Mqtt live data

[Pat]

No, not for mqtt websockets. That's connected to your mosquitto 
installation and not a webserver like nginx or apache. 

Check your mosquitto logs to see what's happening

On Thursday, October 3, 2019 at 9:45:02 PM UTC-4, K Weaver wrote:
>
> Does it matter if I'm using Apache or nginx?
>
>
> On Thu, Oct 3, 2019, 2:54 PM K Weaver > 
> wrote:
>
>> I used cloud but couldn't get the client to connect
>>
>> I can't figure out why it shuts down like that around 9 every morning.
>>
>> It seems like the sub for the client is connecting separately to the raw 
>> data and the real time. 
>>
>> On Thu, Oct 3, 2019, 1:25 PM Pat > 
>> wrote:
>>
>>> Have you considered trying a free public broker to resolve some of the 
>>> other issues outlined in this post for the interim? Then once those are 
>>> fixed you can focus on making your broker stable?
>>>
>>>
>>>
>>> On Thursday, October 3, 2019 at 11:40:38 AM UTC-4, K Weaver wrote:
>>>>
>>>> And checking from work its back down again...
>>>>
>>>> On Wed, Oct 2, 2019, 10:40 PM K Weaver  wrote:
>>>>
>>>>> 10:39 pm Its up. I'm not gonna try to make any edits if anyone wants 
>>>>> to check it out.
>>>>> Sorry about that
>>>>>
>>>>>
>>>>> On Wed, Oct 2, 2019, 7:51 PM Pat  wrote:
>>>>>
>>>>>> I still think you have something else going on. You posted 18 minutes 
>>>>>> ago, and I cannot reach it. 
>>>>>>
>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' 
>>>>>> failed: Unknown reason
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>>>>>>
>>>>>>> It's accessable online now if anyone is available to check it out.
>>>>>>>
>>>>>>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>>>>>>
>>>>>>>> for some reason it disconnects every morning around 9 am
>>>>>>>>
>>>>>>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>>>>>>
>>>>>>>>> I'm able to pull it up on my phone without WiFi .
>>>>>>>>>
>>>>>>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>>>>>>
>>>>>>>>>> Looks like it's down again - or it's not working externally still
>>>>>>>>>>
>>>>>>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>>>>>>>
>>>>>>>>>>> I'm home from work now and reset it.
>>>>>>>>>>> I'm not sure why it shut down...
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Looks like it's down again or you have a firewall issue again. 
>>>>>>>>>>>>
>>>>>>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' 
>>>>>>>>>>>> failed: Unknown reason
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hey, its back up and running now. Only thing now it appears to 
>>>>>>>>>>>>> be  flipping between raw data and real time data..
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here is a snippet of the log.  You can really see it flipping 
>>>>>>>>>>>>> back and forth on the site.  
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ': 1}
>>>>>>>>>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: 
>>>>>>>>>>>>> Published record 2019-09-30 19:57:26 EDT (1569887846)
>>>

Re: [weewx-user] Re: Mqtt live data

[Pat]

Have you considered trying a free public broker to resolve some of the 
other issues outlined in this post for the interim? Then once those are 
fixed you can focus on making your broker stable?



On Thursday, October 3, 2019 at 11:40:38 AM UTC-4, K Weaver wrote:
>
> And checking from work its back down again...
>
> On Wed, Oct 2, 2019, 10:40 PM K Weaver > 
> wrote:
>
>> 10:39 pm Its up. I'm not gonna try to make any edits if anyone wants to 
>> check it out.
>> Sorry about that
>>
>>
>> On Wed, Oct 2, 2019, 7:51 PM Pat > 
>> wrote:
>>
>>> I still think you have something else going on. You posted 18 minutes 
>>> ago, and I cannot reach it. 
>>>
>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' 
>>> failed: Unknown reason
>>>
>>>
>>>
>>> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>>>
>>>> It's accessable online now if anyone is available to check it out.
>>>>
>>>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>>>
>>>>> for some reason it disconnects every morning around 9 am
>>>>>
>>>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>>>
>>>>>> I'm able to pull it up on my phone without WiFi .
>>>>>>
>>>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>>>
>>>>>>> Looks like it's down again - or it's not working externally still
>>>>>>>
>>>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>>>>
>>>>>>>> I'm home from work now and reset it.
>>>>>>>> I'm not sure why it shut down...
>>>>>>>>
>>>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>>>>
>>>>>>>>> Looks like it's down again or you have a firewall issue again. 
>>>>>>>>>
>>>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' 
>>>>>>>>> failed: Unknown reason
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>>>>>>>>>
>>>>>>>>>> Hey, its back up and running now. Only thing now it appears to 
>>>>>>>>>> be  flipping between raw data and real time data..
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Here is a snippet of the log.  You can really see it flipping 
>>>>>>>>>> back and forth on the site.  
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ': 1}
>>>>>>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published 
>>>>>>>>>> record 2019-09-30 19:57:26 EDT (1569887846)
>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: 
>>>>>>>>>> ServerThread: GET: 
>>>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: 
>>>>>>>>>> MainThread: raw data: 
>>>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: 
>>>>>>>>>> MainThread: ignored parameter realtime=1
>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: 
>>>>>>>>>> MainThread: ignored parameter action=updateraw
>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: 
>>>>>>>>>> MainThread: raw packet: {'sensor_type.4264.24C86E0936CB': 
>>>>>>>>>> 'tower', 
>>>>>>>>>> 'battery.4264.24C86E0936CB': 1, 
>>>>>>>>>> 'sensor_id.4264.24C86E0936CB': 
>>>>>>>>>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851, 
>>>>>>>>>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851, 
>>>>>>>>>> 'temperature.4264.24C8

Re: [weewx-user] Re: Mqtt live data

[Pat]

I still think you have something else going on. You posted 18 minutes ago, 
and I cannot reach it. 

WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed: 
Unknown reason



On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>
> It's accessable online now if anyone is available to check it out.
>
> On Wed, Oct 2, 2019, 2:12 PM K Weaver > 
> wrote:
>
>> for some reason it disconnects every morning around 9 am
>>
>> On Tue, Oct 1, 2019, 10:18 PM K Weaver > 
>> wrote:
>>
>>> I'm able to pull it up on my phone without WiFi .
>>>
>>> On Tue, Oct 1, 2019, 8:07 PM Pat > 
>>> wrote:
>>>
>>>> Looks like it's down again - or it's not working externally still
>>>>
>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>
>>>>> I'm home from work now and reset it.
>>>>> I'm not sure why it shut down...
>>>>>
>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>
>>>>>> Looks like it's down again or you have a firewall issue again. 
>>>>>>
>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' 
>>>>>> failed: Unknown reason
>>>>>>
>>>>>>
>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>>>>>>
>>>>>>> Hey, its back up and running now. Only thing now it appears to be  
>>>>>>> flipping between raw data and real time data..
>>>>>>>
>>>>>>>
>>>>>>> Here is a snippet of the log.  You can really see it flipping back 
>>>>>>> and forth on the site.  
>>>>>>>
>>>>>>>
>>>>>>> ': 1}
>>>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published 
>>>>>>> record 2019-09-30 19:57:26 EDT (1569887846)
>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: ServerThread: 
>>>>>>> GET: 
>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: 
>>>>>>> raw data: 
>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: 
>>>>>>> ignored parameter realtime=1
>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: 
>>>>>>> ignored parameter action=updateraw
>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: 
>>>>>>> raw packet: {'sensor_type.4264.24C86E0936CB': 'tower', 
>>>>>>> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB': 
>>>>>>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851, 
>>>>>>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851, 
>>>>>>> 'temperature.4264.24C86E0936CB': 73.4, 
>>>>>>> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB': 
>>>>>>> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB', 
>>>>>>> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: 
>>>>>>> mapped packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 
>>>>>>> 56.0, 
>>>>>>> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0, 
>>>>>>> 'usUnits': 1}
>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published 
>>>>>>> record 2019-09-30 19:57:31 EDT (1569887851)
>>>>>>> Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread: 
>>>>>>> empty queue
>>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: ServerThread: 
>>>>>>> GET: 
>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: 
>>>>>>> raw data: 
>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=

Re: [weewx-user] Re: Mqtt live data

[Pat]

Looks like it's down again - or it's not working externally still

On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>
> I'm home from work now and reset it.
> I'm not sure why it shut down...
>
> On Tue, Oct 1, 2019, 3:29 PM Pat > 
> wrote:
>
>> Looks like it's down again or you have a firewall issue again. 
>>
>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed: 
>> Unknown reason
>>
>>
>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>>
>>> Hey, its back up and running now. Only thing now it appears to be  
>>> flipping between raw data and real time data..
>>>
>>>
>>> Here is a snippet of the log.  You can really see it flipping back and 
>>> forth on the site.  
>>>
>>>
>>> ': 1}
>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published record 
>>> 2019-09-30 19:57:26 EDT (1569887846)
>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: ServerThread: 
>>> GET: 
>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw 
>>> data: 
>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: 
>>> ignored parameter realtime=1
>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: 
>>> ignored parameter action=updateraw
>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw 
>>> packet: {'sensor_type.4264.24C86E0936CB': 'tower', 
>>> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB': 
>>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851, 
>>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851, 
>>> 'temperature.4264.24C86E0936CB': 73.4, 
>>> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB': 
>>> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB', 
>>> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: 
>>> mapped packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 56.0, 
>>> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0, 
>>> 'usUnits': 1}
>>> Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published record 
>>> 2019-09-30 19:57:31 EDT (1569887851)
>>> Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread: empty 
>>> queue
>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: ServerThread: 
>>> GET: 
>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw 
>>> data: 
>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: 
>>> ignored parameter realtime=1
>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: 
>>> ignored parameter rainin=0.00
>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: 
>>> ignored parameter action=updateraw
>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw 
>>> packet: {'rainfall.0583.24C86E0936CB': 0.0, 
>>> 'battery.0583.24C86E0936CB': 0, 'sensor_id.0583.24C86E0936CB': 
>>> '0583', 'rssi.0583.24C86E0936CB': 75.0, 
>>> 'windspeed.0583.24C86E0936CB': 0.0, 'winddir.0583.24C86E0936CB': 
>>> 338.0, 'dateTime': 1569887864, 'pressure.0583.24C86E0936CB': 29.31, 
>>> 'usUnits.0583.24C86E0936CB': 1, 'rain_total.0583.24C86E0936CB': 
>>> 0.0, 'bridge_id.0583.24C86E0936CB': '24C86E0936CB', 
>>> 'dateTime.0583.24C86E0936CB': 1569887864, 
>>> 'sensor_type.0583.24C86E0936CB': '5N1x31', 'usUnits': 1}
>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: 
>>> mapped packet: {'txBatteryStatus': 0, 'rain': 0.0, 'dateTime': 1569887864, 
>>> 'windDir': 338.0, 'pressure': 29.31, 'windSpeed': 0.0, 'rxCheckPercent': 
>>> 75.0, 'usUnits': 1}
>>> Sep 30 19:57:44 raspberrypi weewx[23528]: restx: MQTT: Published record 
>>> 2019-09-30 19:57:44 EDT (1569887864)
>>> Sep 30 19:57:46 raspberrypi weewx[23528]: interceptor: ServerThread: 
>>> GET: 
>>> dateutc=now=updateraw=1=24C86E0936CB=tower=

[weewx-user] Re: Help with Weewx install

[Pat]

If you installed using apt-get, then your weewx.conf will be in /etc/weewx.

Try sudo weewxd /etc/weewx/weewx.conf 


On Tuesday, October 1, 2019 at 12:01:48 PM UTC-4, Jason wrote:
>
> Installed with these 2 commands
>
> sudo apt-get update
> sudo apt-get install weewx
> The configuration went through ok.
> -
> pi@raspberrypi:~/Desktop/weewx/consolewdfiles $ sudo apt-get install weewx
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Suggested packages:
>   sqlite ftp httpd
> The following NEW packages will be installed:
>   weewx
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/1,572 kB of archives.
> After this operation, 5,972 kB of additional disk space will be used.
> Preconfiguring packages ...
> Selecting previously unselected package weewx.
> (Reading database ... 94076 files and directories currently installed.)
> Preparing to unpack .../archives/weewx_3.9.2-1_all.deb ...
> Unpacking weewx (3.9.2-1) ...
> Setting up weewx (3.9.2-1) ...
>
> Setting record_generation to software.
> Saved configuration to /etc/weewx/weewx.conf
> Processing triggers for systemd (241-7~deb10u1+rpi1) ...
> pi@raspberrypi:~/Desktop/weewx/consolewdfiles $ 
>
> ---
>
>
> On Tuesday, 1 October 2019 13:44:42 UTC+1, Jason wrote:
>>
>> I have installed Weewx on a Raspberry Pi 4 and get the message on the 
>> image above. It weems to be directing the command to the wrong directory.
>> Weewx is installed in  /etc/weewx so cannot be found.
>> How do I change the startup command to the correct directory.
>> Is there a way to view the working application on the local pc to test it 
>> before uploading to my ftp.
>> What files do I need to put on the ftp to display it.
>> 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/281e8771-14a2-4fbb-8709-3e417c8d741c%40googlegroups.com.

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

[Pat]

Does your database have data for January? I'm guessing no. So you'll need 
to update your graphs.conf to remove January from the xaxis categories. The 
graphs JSON code isn't "smart" enough to determine the first month of your 
dataset, so it relies on you knowing that and setting those categories 
accordingly. 


On Tuesday, October 1, 2019 at 6:58:14 AM UTC-4, Wiggytoo wrote:
>
> Hi Pat,
>
> I've just noticed that the Average Climatological Values for this Year 
> Chart on my homepage (http://www.wiggytoo.co.uk/) seems to be one month 
> out
>
> For example
>
> Jun - Max 35.6, Min 15.2, Rain 43.03
> July - Max 33, Min 12.2, Rain 49.35
> Aug - Max 24.5, Min 8.5, Rain 87.14
> Sep - Max 16.2, Min 14.2, Rain 7.3
>
> The actual values from the Reports page (
> http://www.wiggytoo.co.uk/reports/?yr=2019) are
>
> July - Max 35.6, Min 15.2, Rain 43.0
> Aug - Max 33, Min 12.2, Rain 49.4
> Sep - Max 24.5, Min 8.5, Rain 87.1
> Oct - Max 16.2, Min 14.2, Rain 7.3
>
> Any ideas - I have used the sample code from the Charts WIki
> Thanks,
> Gavin
>

-- 
You received this message because you are subscribed to the Google 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/d9f975a4-8220-4309-99bf-8262f952e304%40googlegroups.com.

[weewx-user] Re: Mqtt live data

[Pat]

Looks like it's down again or you have a firewall issue again. 

WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed: 
Unknown reason


On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>
> Hey, its back up and running now. Only thing now it appears to be  
> flipping between raw data and real time data..
>
>
> Here is a snippet of the log.  You can really see it flipping back and 
> forth on the site.  
>
>
> ': 1}
> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published record 
> 2019-09-30 19:57:26 EDT (1569887846)
> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: ServerThread: GET: 
> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw 
> data: 
> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
> parameter realtime=1
> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
> parameter action=updateraw
> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw 
> packet: {'sensor_type.4264.24C86E0936CB': 'tower', 
> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB': 
> '4264', 'dateTime.4264.24C86E0936CB': 1569887851, 
> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851, 
> 'temperature.4264.24C86E0936CB': 73.4, 
> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB': 
> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB', 
> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: mapped 
> packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 56.0, 
> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0, 
> 'usUnits': 1}
> Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published record 
> 2019-09-30 19:57:31 EDT (1569887851)
> Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread: empty 
> queue
> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: ServerThread: GET: 
> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw 
> data: 
> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
> parameter realtime=1
> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
> parameter rainin=0.00
> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
> parameter action=updateraw
> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw 
> packet: {'rainfall.0583.24C86E0936CB': 0.0, 
> 'battery.0583.24C86E0936CB': 0, 'sensor_id.0583.24C86E0936CB': 
> '0583', 'rssi.0583.24C86E0936CB': 75.0, 
> 'windspeed.0583.24C86E0936CB': 0.0, 'winddir.0583.24C86E0936CB': 
> 338.0, 'dateTime': 1569887864, 'pressure.0583.24C86E0936CB': 29.31, 
> 'usUnits.0583.24C86E0936CB': 1, 'rain_total.0583.24C86E0936CB': 
> 0.0, 'bridge_id.0583.24C86E0936CB': '24C86E0936CB', 
> 'dateTime.0583.24C86E0936CB': 1569887864, 
> 'sensor_type.0583.24C86E0936CB': '5N1x31', 'usUnits': 1}
> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: mapped 
> packet: {'txBatteryStatus': 0, 'rain': 0.0, 'dateTime': 1569887864, 
> 'windDir': 338.0, 'pressure': 29.31, 'windSpeed': 0.0, 'rxCheckPercent': 
> 75.0, 'usUnits': 1}
> Sep 30 19:57:44 raspberrypi weewx[23528]: restx: MQTT: Published record 
> 2019-09-30 19:57:44 EDT (1569887864)
> Sep 30 19:57:46 raspberrypi weewx[23528]: interceptor: ServerThread: GET: 
> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: raw 
> data: 
> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
> parameter realtime=1
> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
> parameter action=updateraw
> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: raw 
> packet: {'sensor_type.4264.24C86E0936CB': 'tower', 
> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB': 
> '4264', 'dateTime.4264.24C86E0936CB': 1569887867, 
> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887867, 
> 'temperature.4264.24C86E0936CB': 73.4, 
> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB': 
> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB', 
> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: mapped 
> packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 56.0, 
> 'dateTime': 1569887867, 

Re: [weewx-user] N/A / unavailable wind data

[Pat]

What does your console show? I've had my VP2 for about 18 months as well 
and my wind vane died on me. Reported windDir 0 for majority of they day, 
but wasn't constantly at 0. Davis sent me a test cable to test the ISS. I 
ended up paying for a replacement anemometer/wind vane unit. If you find 
that your console is also showing bad wind data, then it may not be weewx's 
fault. 


On Monday, September 30, 2019 at 9:36:34 AM UTC-4, mrbalky wrote:
>
> Simple answer: RTFM.
>
> My apologies!
>
> Thanks!
>
>
> On Monday, September 30, 2019 at 7:23:36 AM UTC-6, Thomas Keffer wrote:
>>
>> See the section *There is no wind direction when wind speed is zero 
>> * in the User's 
>> Guide.
>>
>> -tk
>>
>> On Mon, Sep 30, 2019 at 6:19 AM mrbalky  wrote:
>>
>>> Howdy,
>>>
>>> VantagePro2 wireless, console connected via USB to a RPi running WeeWX 
>>> 3.9.2. WeeWX is logging to MySQL on a separate machine.
>>>
>>> I have been having what I think is a problem with unavailable wind data.
>>>
>>> The data logging packets are showing "windDir: None", which results in 
>>> the current conditions on the generated HTML showing as "Wind 0 mph N/A ( 
>>> N/A)", and my PWS page on wunderground showing wind data as "unavailable".
>>>
>>> The archive rows have NULLs in the windDir column.
>>>
>>> I've had this VP2 for about 18 months, and haven't noticed this before, 
>>> and have been presuming this to be a new anemometer/cabling/transmitter 
>>> issue. But I do not find any rows in the archive database where windSpeed 
>>> is 0 and windDir is not NULL. Unfortunately, my server died a month or so 
>>> ago, and I lost all archive data prior to that.
>>>
>>> Now, with a wind speed of 0, a direction of None does make some sense, 
>>> but it seems that N/A and Unavaliable do not. Is this expected WeeWX 
>>> behavior and I've just been chasing a non-existent hardware issue?
>>>
>>> TIA,
>>> Charlie
>>>
>>> -- 
>>> You received this message because you are 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/e9d50a1a-db55-414d-b593-b8d43c4ff71a%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/f7cf3102-0fde-48c9-ab22-649311ec6d3d%40googlegroups.com.

Re: [weewx-user] Re: Belchertown Skin - display Units

[Pat]

Is this resolved? Have you added this new 'lux' observation to the known 
observation group dictionary?

Here's how you would do it for the lightning sensor's average distance. 
Change the values below to lux, and you'll need to find the relevant group 
for lux. 

weewx.units.obs_group_dict['avg_distance'] = 'group_distance'




On Monday, September 23, 2019 at 5:02:00 PM UTC-4, Xant wrote:
>
> Funny, but typo only on posting. It is correct at config files.
>
>
>
> On September 23, 2019 at 2:54 PM, vince (vince...@gmail.com ) 
> wrote:
>
> Belchertown skin.conf:
>
> [[Lables]]
> lux = " lux"
>
>
> You have 'Labels' spelled wrong :-)
>
>
> --
>
> 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/CMwtsQ6SrpE/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/9c133fc9-3dfb-4c63-af2f-bb1df3dd17e0%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/e24cbce4-1654-4748-9b5c-1629e597dc08%40googlegroups.com.

Re: [weewx-user] No space left on device when generating Highcharts_Belchertown/json/year.json.tmpl

[Pat]

And before I forget, here's the instructions on how to upgrade from your 
older version. As always, please have a working backup. 

https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0


On Wednesday, September 25, 2019 at 10:16:28 PM UTC-4, Pat wrote:
>
> Off topic, but maybe relevant. Please upgrade to the latest version of 
> Belchertown. There's been a lot of optimizations since the version you're 
> running. For example, the "sub-skin" Highcharts_Belchertown has been 
> fully removed.
>
>

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

Re: [weewx-user] No space left on device when generating Highcharts_Belchertown/json/year.json.tmpl

[Pat]

Off topic, but maybe relevant. Please upgrade to the latest version of 
Belchertown. There's been a lot of optimizations since the version you're 
running. For example, the "sub-skin" Highcharts_Belchertown has been fully 
removed.

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

[weewx-user] Re: image caching problem with Chrome

[Pat]

> This is from a different web published RPi dodad raspberryshake (mine is 
broken at the moment).  Anyhow, the trick is to add a timestamp to the href 
that updates with the image so that it tricks the caching mechanism into 
reloading the same named file when the timestamp has changed.  Does cheetah 
support that sort of thing?

Yes, Cheetah supports it. I use this trick in my Belchertown skin 
 to prevent caching. Here's 
how you can use it too. 

This is *NOT TESTED* on Seasons, so be sure to have a backup. Find the 
images you want to stop caching for. For example inside the 
index.html.tmpl. Add this to the end of the image src: ?v=#echo int( 
time.time() ) #

For example in a full line:



That'll change the img src to have a timestamp at the end, similar to your a 
href you have mentioned. The timestamp will not be when you refresh the 
page, but rather the time when weewx generated the index.html page. So it 
should update every archive interval with a new timestamp appended. 

On Sunday, September 22, 2019 at 6:34:07 PM UTC-4, Chris Richmond wrote:
>
> All, this can't be a new thing, but using Chrome and weewx 3.9.1, the 
> graphs don't reload when refreshing the
> web page.  Rather than having to clear the image cache in Chrome's 
> Settings, is it reasonable to add a trick like this:
> http://www.csrhome.online/myshake/gifs/RD066_EHZ_AM_00.2019090100.gif?v=1567339258>
> ">
>
> This is from a different web published RPi dodad raspberryshake (mine is 
> broken at the moment).  Anyhow, the trick
> is to add a timestamp to the href that updates with the image so that it 
> tricks the caching mechanism into reloading the
> same named file when the timestamp has changed.  Does cheetah support that 
> sort of thing?
>
> Semi-unrelated, but is there a way to get the rsync report to run after 
> the the images are generated rather than
> before?  As it is, the images are always a cycle behind the rest of the 
> page updates.  The report module isn't sorting
> the names, but maybe naming rsync ZRSYNC and sorting the report names 
> would work???
>
> Sep 22 16:20:38 pivue weewx[30301]: copygenerator: copied 0 files to 
> /home/weewx/public_html.vp2
> Sep 22 16:25:14 pivue weewx[30301]: manager: Added record 2019-09-22 
> 16:25:00 MDT (1569191100) to database 'weewx.sdb'
> Sep 22 16:25:15 pivue weewx[30301]: manager: Added record 2019-09-22 
> 16:25:00 MDT (1569191100) to daily summary in 'weewx.sdb'
> Sep 22 16:25:16 pivue weewx[30301]: rsyncupload: rsync'd 23 files (168,268 
> bytes) in 0.96 seconds
> Sep 22 16:25:32 pivue weewx[30301]: cheetahgenerator: Generated 9 files 
> for report SeasonsReport in 14.57 seconds
> Sep 22 16:25:38 pivue weewx[30301]: imagegenerator: Generated 14 images 
> for SeasonsReport in 6.61 seconds
> Sep 22 16:25:38 pivue weewx[30301]: copygenerator: copied 0 files to 
> /home/weewx/public_html.vp2
>
> Site is here: http://www.csrhome.online/vp2weather/index.html
>
> thx,Chris 
>
>

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

Re: [weewx-user] Not archiving Signal Quality (rxCheckPercent) data

[Pat]

I'm not sure how the Davis driver works, but with the Meteostick driver 
it's able to calculate rxCheckPercent 

 
based on number of RF packets received over a known interval 

 
and doing that math. Since I use the Meteostick driver for my Davis 
station, I'm set to software generation and I get the rxCheckPercent. I 
wonder if there's a way to incorporate this bit of code into a Davis driver 
fork? 

Could be a large project (which I'm not volunteering for) but thought I'd 
at least mention it and link to the code.


On Monday, September 23, 2019 at 5:47:02 PM UTC-4, Thomas Keffer wrote:
>
> Sorry, but the value of rxCheckPercent comes only from the console, and 
> then only in archive records (not LOOP packets). If you disable hardware 
> record generation, you lose it.
>
> It would be a nice feature to be able to pick and chose where each datum 
> in the archive record comes from, but, unfortunately, that's not the way 
> WeeWX works now.
>
> -tk
>
> On Mon, Sep 23, 2019 at 9:46 AM Erick Dorsett  > wrote:
>
>> I recently installed weewx on a Pi to use with my ancient Davis Vantage 
>> Pro.  In order to get the winds to report actual degrees instead of 
>> quantized to the cardinals, I had to set  "record_generation = software" in 
>> the weewx.conf file.  However, after I did that, the data point for signal 
>> quality (rxCheckPercent) is no longer archived in weewx.sdb. 
>>
>> I use rxCheckPercent data for a bunch of reasons.  How do I get it back?
>>
>>
>> -- 
>> You received this message because you are 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/e564d660-ec57-4887-a74b-a28969ebf374%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/09aa1d9c-1e40-4dbd-bcb0-9e4184ecd255%40googlegroups.com.

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

[Pat]

Those gaps represent missing data. 

Make sure your signal strength is good from the station, or if you don't 
want the gaps to show missing data, enable connectNulls 

.


On Tuesday, September 24, 2019 at 4:38:06 PM UTC-4, Greg from Oz wrote:
>
> I get those gaps when the communication from the console to the weather 
> station drops.
>
> I graph the signal quality and the gaps coincide with the missing data. 
>
> On Tue, 24 Sep. 2019, 21:47 Kike .Asekas, > 
> wrote:
>
>> I have some small gaps in the graphics that I don't know because they 
>> appear since those records exist in the database.
>> What can they be due to?
>>
>> [image: Screenshot_2019-09-24 Areal, Padrón Weather Conditions.png]
>>
>>
>>
>> -- 
>> 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/VyVMEfuxClo/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/231950ff-48fe-482f-af71-b012c12f4225%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/24fe7325-428a-4414-b7a4-e307a1773e11%40googlegroups.com.

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

[Pat]

Just top level, but I think I can move it to second level with some 
testing. I'll work on a commit and let you know when it is ready to test 
with. 

On Thursday, September 19, 2019 at 3:22:01 PM UTC-4, Kike .Asekas wrote:
>
> A question, can generate be in second level [[..]]  or only in top 
> level []?
>
>
>

-- 
You received this message because you are subscribed to the Google 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/dcff6f06-ca29-438d-b09b-29d2ae01b457%40googlegroups.com.

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

[Pat]

Unsure. I don't see a license on the file, so not sure if I can just add it 
to me belchertown.py. 

It also won't fix the charts or the MQTT. Those rely on the weewx-mqtt 
extension and built-in weewx functions (non-Belchertown). 

On Wednesday, September 18, 2019 at 9:35:07 PM UTC-4, Greg from Oz wrote:
>
> Could this be a standard option for your next release?
>
>
> On Thu, 19 Sep 2019 at 11:33, Pat > 
> wrote:
>
>> Ah, looks like you've got it. Probably won't help you for MQTT for the 
>> Charts, but you can at least replace the tags you're looking for
>>
>> On Wednesday, September 18, 2019 at 9:29:35 PM UTC-4, Greg from Oz wrote:
>>>
>>> Yes I think Gary wrote a python script to work out 9 am.
>>>
>>> https://github.com/weewx/weewx/files/2082668/since.py.txt
>>>
>>> It is called since.py
>>>
>>> There is a bit in the index.html.tmpl
>>>
>>> 
>>>
>>> Today's Rain since 9am
>>>     $since($hour=9).rain.sum
>>>   
>>> It was a long time since I installed this.
>>>
>>>
>>>
>>> On Thu, 19 Sep 2019 at 11:18, Pat  wrote:
>>>
>>>> In the skin, not that I'm aware of. The skin is using the standard 
>>>> weewx $tags for rain timespans on static pages, and weewx-mqtt gives the 
>>>> values for rain on live updates. The charts get their daily timespans from 
>>>> weewx's built in archiveDaySpan() function.
>>>>
>>>> The website you link isn't showing Belchertown though, so I'm not sure 
>>>> what that is or how it's showing 9am. 
>>>>
>>>> Maybe there's a setting in weewx.conf? 
>>>>
>>>> I'm not sure if Gary or someone would be able to offer insight. 
>>>>
>>>>
>>>>
>>>> On Wednesday, September 18, 2019 at 8:46:49 PM UTC-4, Greg from Oz 
>>>> wrote:
>>>>>
>>>>> Hi Pat.
>>>>>
>>>>> Is there an option in the skin to change the reporting time of rain?
>>>>> Here in Australia it is from 9 am to 9 am and I know in other 
>>>>> countries it is different.
>>>>> I show both on my web site.
>>>>> https://weather.ubeaut.work/
>>>>> It is good to have from 9 am as I can compare to the nearby official 
>>>>> weather station.
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>> On Sunday, 2 June 2019 02:57:56 UTC+10, 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/releas

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

[Pat]

Ah, looks like you've got it. Probably won't help you for MQTT for the 
Charts, but you can at least replace the tags you're looking for

On Wednesday, September 18, 2019 at 9:29:35 PM UTC-4, Greg from Oz wrote:
>
> Yes I think Gary wrote a python script to work out 9 am.
>
> https://github.com/weewx/weewx/files/2082668/since.py.txt
>
> It is called since.py
>
> There is a bit in the index.html.tmpl
>
> 
>
> Today's Rain since 9am
> $since($hour=9).rain.sum
>   
> It was a long time since I installed this.
>
>
>
> On Thu, 19 Sep 2019 at 11:18, Pat > 
> wrote:
>
>> In the skin, not that I'm aware of. The skin is using the standard weewx 
>> $tags for rain timespans on static pages, and weewx-mqtt gives the values 
>> for rain on live updates. The charts get their daily timespans from weewx's 
>> built in archiveDaySpan() function.
>>
>> The website you link isn't showing Belchertown though, so I'm not sure 
>> what that is or how it's showing 9am. 
>>
>> Maybe there's a setting in weewx.conf? 
>>
>> I'm not sure if Gary or someone would be able to offer insight. 
>>
>>
>>
>> On Wednesday, September 18, 2019 at 8:46:49 PM UTC-4, Greg from Oz wrote:
>>>
>>> Hi Pat.
>>>
>>> Is there an option in the skin to change the reporting time of rain?
>>> Here in Australia it is from 9 am to 9 am and I know in other countries 
>>> it is different.
>>> I show both on my web site.
>>> https://weather.ubeaut.work/
>>> It is good to have from 9 am as I can compare to the nearby official 
>>> weather station.
>>>
>>> Thanks
>>>
>>>
>>> On Sunday, 2 June 2019 02:57:56 UTC+10, 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

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

[Pat]

In the skin, not that I'm aware of. The skin is using the standard weewx 
$tags for rain timespans on static pages, and weewx-mqtt gives the values 
for rain on live updates. The charts get their daily timespans from weewx's 
built in archiveDaySpan() function.

The website you link isn't showing Belchertown though, so I'm not sure what 
that is or how it's showing 9am. 

Maybe there's a setting in weewx.conf? 

I'm not sure if Gary or someone would be able to offer insight. 



On Wednesday, September 18, 2019 at 8:46:49 PM UTC-4, Greg from Oz wrote:
>
> Hi Pat.
>
> Is there an option in the skin to change the reporting time of rain?
> Here in Australia it is from 9 am to 9 am and I know in other countries it 
> is different.
> I show both on my web site.
> https://weather.ubeaut.work/
> It is good to have from 9 am as I can compare to the nearby official 
> weather station.
>
> Thanks
>
>
> On Sunday, 2 June 2019 02:57:56 UTC+10, 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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3dcb13a7-2007-4ee8-9c4d-2b04bcabe2e1%40googlegroups.com.

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

[Pat]

Kike, how is the generate option working for you? So far in my tested it is 
working well. 

On Monday, September 16, 2019 at 8:33:10 PM UTC-4, Pat wrote:
>
> Kike, I've added my draft of the generate option. You will need to upgrade 
> to the 1.1 beta skin by downloading it from the Belchertown's GitHub 
> development branch 
> <https://github.com/poblabs/weewx-belchertown/tree/development>.
>
> Once you have upgraded, for information on how it works, why it works like 
> that and how to use it, refer to the wiki's generate option 
> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#generate>
>  
> section. 
>

-- 
You received this message because you are subscribed to the Google 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/d9ab03ed-a7d7-496d-8c49-7a9665d1fc5e%40googlegroups.com.

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

[Pat]

Kike, I've added my draft of the generate option. You will need to upgrade 
to the 1.1 beta skin by downloading it from the Belchertown's GitHub 
development branch 
.

Once you have upgraded, for information on how it works, why it works like 
that and how to use it, refer to the wiki's generate option 

 
section. 

-- 
You received this message because you are subscribed to the Google 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/f379c15b-6545-4f8b-bcc3-602751df8da3%40googlegroups.com.

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

[Pat]

Marten, any of the variables found within weewx will work. I don't maintain 
a list since this is not skin specific. You can check the source code of 
the Seasons skin, the Standard skin or see if the User's Guide can offer 
any insight. 

For the signal quality, I am using this code which was borrowed and 
modified from the Season skin :)

#if $day.txBatteryStatus.has_data

  
Transmitter Battery
  
#if $current.txBatteryStatus.raw == 0
OK
#else
LOW
#end if
  

#end if
#if $day.rxCheckPercent.has_data

Signal Quality
$current.rxCheckPercent

#end if




On Monday, September 16, 2019 at 5:06:12 PM UTC-4, Marten Hinrichs wrote:
>
> Hi,
>
> Your Skin is Great and i currently Customized my Website.
>
> I am edit my about.inc template file. Now i have a problem with the 
> Variables for the Station. Is there a List of available Variables? Like
>
>  $station.hardware
>  $station.os_uptime
>  $station.uptime
> $station.version
> $belchertown_version
>
> I am interested in Signal Quality/Battery Status/ Like your Page.  Can 
> anybody Help me? I have a Davis Vantage Pro 2.
>
> MfG Marten
>

-- 
You received this message because you are subscribed to the Google 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/c4e622e8-e3a1-4fff-90a3-abe7a503e321%40googlegroups.com.

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

[Pat]

*So you're asking for a complete re-write of the skin?* By all means fork 
it and make it your own! :)

weewx is only generating a small number of web pages for Belchertown. That 
overhead - even on a Pi - is very small. Disable Highcharts and you will 
see. Set Belchertown skin.conf option highcharts_enabled = 0. 

It's the charts with large time spans with a lot of data points. that will 
bog a Pi down. This is a known fact, and even documented with a warning 
inside of graphs.conf itself 

. 

As for the AJAX calls, it's calling 2 files and all the chart data. One is 
the weewx_data.json to populate various fields on the front page, forecast 
json for forecast data, and then all the chart data. 

Calling chart data over an AJAX call is not a problem for your Pi, only a 
problem for the client (like a cell phone not on wifi) if the data set is 
very large. 

Sorry, but I don't have the time to create and support a REST API which 
everyone can point their system to in order to get updates. This is why I 
chose MQTT and why the skin is using it. That's Scenario 5 

. 

As for the graphs, not everyone has web-facing access to MySQL, so the JSON 
files are preferred for many users of the skin based on feedback. 

There are other skins here, one of which have launched Highcharts within 
the last 3 days. That skin also uses the JSON method to transport data to 
the chart and client. 

I'm working on the generator delay option you've asked twice for. My draft 
is working but there's limitations to it. I'll commit something when I can. 



On Monday, September 16, 2019 at 12:52:04 PM UTC-4, Kike .Asekas wrote:
>
> I want to try it. I'm looking at the code but I don't know if I'll be 
> able to change it. I'm still getting it.
> I have been looking at the documentation of the weewx github wiki and I 
> think that in this skin that obtains the data with ajax it is not necessary 
> all the weewx page generation infrastructure to generate the same page at 
> each turn.
> https://github.com/weewx/weewx/wiki/dashboards
> Wouldn't it be interesting to have the skin as described in Scenario 3: 
> Upload LOOP / REC data to public-facing front-end? Weewx would handle 
> calculations, conversion, storage in the bd, publication in wu and others 
> and generate the json necessary for the skin but not the generation of web 
> pages.
>
> How about? Would it be a lot of change?
>
>

-- 
You received this message because you are subscribed to the Google 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/c54697cd-4c17-4232-85c0-67ecfe7506c1%40googlegroups.com.

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

[Pat]

No problem. I have something drafted. I will let you know when I commit it 
to development branch and you can try it. 

On Monday, September 16, 2019 at 7:41:24 AM UTC-4, Kike .Asekas wrote:
>
> Thanks for your answer. I thought of using a new page for that series of 
> graphics to put in cheetahgenerator in skin.conf that I generate it every 
> month but I think I don't get anything with that because even if it is 
> another page the generation is in graphs.conf and they are generated equally 
> in 
> every turn.
> I hope I can help you, but I don't know if I will have enough knowledge to 
> do it.
> Greetings
>
>
> El lunes, 16 de septiembre de 2019, 12:41:01 (UTC+2), Pat escribió:
>>
>> Hi Kike, I'm glad you're enjoying the skin. You've mentioned this 
>> problem of yours before 
>> <https://groups.google.com/d/msg/weewx-user/VyVMEfuxClo/n8D_YVjbAQAJ>. I 
>> have it written down to look into. I volunteer my time to this project and 
>> haven't had enough time to add this feature to development. 
>>
>> If you implement a way to do this before I can, a pull request is 
>> welcomed so it can be added in. It could possibly take the "crontab" 
>> approach of "generate = daily" or "generate = hourly" in the graph group. 
>> Then belchertown.py would have to translate that to a timestamp and compare 
>> that on every run. A lot of testing would have to take place.  
>>
>> On Monday, September 16, 2019 at 4:30:26 AM UTC-4, Kike .Asekas wrote:
>>>
>>> This skin allows us to make amazing graphics and this makes us want to 
>>> have many.
>>> The problem is that when we want to make a graph that compares the 
>>> average temperatures of the last 10 years per month and another similar 
>>> with the rain, it causes in my rpi 2b + to have blockages in the database 
>>> when it coincides that weewx is writing in the database.
>>> These graphs do not need to be made at each turn because only the last 
>>> query will change minimally and the queries are repeated to obtain data 
>>> already calculated and that do not vary. I believe that something would 
>>> have to be changed so that only the last query (the last month of the last 
>>> year in the example) should be done and take advantage of the previous json 
>>> data. I don't know if it's possible or complicated to do this.
>>> Another way could be marking some graphs so that they are not generated 
>>> every turn.
>>> In my case with the rpi in theory I can have amazing graphics but in 
>>> practice I have to remove them by having many queries that cause me to have 
>>> blockages and data loss.
>>>
>>

-- 
You received this message because you are subscribed to the Google 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/8ea28dd9-a4f9-45c3-8bc3-927aa905892f%40googlegroups.com.

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

[Pat]

Hi Kike, I'm glad you're enjoying the skin. You've mentioned this problem 
of yours before 
. I 
have it written down to look into. I volunteer my time to this project and 
haven't had enough time to add this feature to development. 

If you implement a way to do this before I can, a pull request is welcomed 
so it can be added in. It could possibly take the "crontab" approach of 
"generate = daily" or "generate = hourly" in the graph group. Then 
belchertown.py would have to translate that to a timestamp and compare that 
on every run. A lot of testing would have to take place.  

On Monday, September 16, 2019 at 4:30:26 AM UTC-4, Kike .Asekas wrote:
>
> This skin allows us to make amazing graphics and this makes us want to 
> have many.
> The problem is that when we want to make a graph that compares the average 
> temperatures of the last 10 years per month and another similar with the 
> rain, it causes in my rpi 2b + to have blockages in the database when it 
> coincides that weewx is writing in the database.
> These graphs do not need to be made at each turn because only the last 
> query will change minimally and the queries are repeated to obtain data 
> already calculated and that do not vary. I believe that something would 
> have to be changed so that only the last query (the last month of the last 
> year in the example) should be done and take advantage of the previous json 
> data. I don't know if it's possible or complicated to do this.
> Another way could be marking some graphs so that they are not generated 
> every turn.
> In my case with the rpi in theory I can have amazing graphics but in 
> practice I have to remove them by having many queries that cause me to have 
> blockages and data loss.
>

-- 
You received this message because you are subscribed to the Google 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/1db7b861-d36d-426e-9764-22348d8b6165%40googlegroups.com.

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

[Pat]

(And to remind me that it's HTML that's needed)

Done


On Tuesday, September 10, 2019 at 9:39:02 PM UTC-4, Greg from Oz wrote:
>
> Maybe in the readme put an example like:
>
> radar_html = " target='_blank'> width='360' height='360' /> "
>
> For the dummies like me who totally missed the point. :)
>
> On Wednesday, 11 September 2019 10:36:29 UTC+10, Greg from Oz wrote:
>>
>> I did see the  readme and I did see the radar_html bit but I overlooked 
>> the bit that says
>>
>>  Full HTML Allowed. Recommended size 650 pixels wide by 360 pixels high. 
>> This URL will be used as the radar iFrame or image hyperlink.
>> Couldn't see if for looking :)
>> Thanks
>>
>>
>> On Wed, 11 Sep 2019 at 10:27, Pat > 
>> wrote:
>>
>>> I've thought about that but afraid it'd make the skin.conf a mile long. 
>>> So I've opted for a mile long README 
>>> <https://github.com/poblabs/weewx-belchertown> with a section for the 
>>> skin.conf options 
>>> <https://github.com/poblabs/weewx-belchertown#skin-options>, can be 
>>> updated adhoc. This is where the official skin documentation resides 
>>> currently. 
>>>
>>> On Tuesday, September 10, 2019 at 8:24:41 PM UTC-4, Greg from Oz wrote:
>>>>
>>>> I did this and it works!
>>>> radar_html = ">>> target='_blank'>"
>>>>
>>>> As a suggestion maybe you should add comments and examples in the 
>>>> skin.conf for each configurable parameter?
>>>>
>>>> Thanks again.
>>>>
>>>>
>>>> On Wed, 11 Sep 2019 at 10:12, Pat  wrote:
>>>>
>>>>> Yep, since it's HTML you can do whatever you want with it, so a link 
>>>>> should work fine
>>>>>
>>>>> On Tuesday, September 10, 2019 at 8:11:41 PM UTC-4, Greg from Oz wrote:
>>>>>>
>>>>>> Yes that worked.
>>>>>> So I can just add a hyperlink that opens a new page to that as it is 
>>>>>> html?
>>>>>> Thanks
>>>>>>
>>>>>> Like I stated earlier the windy.com is good but when viewed on the 
>>>>>> phone I had to swipe the screen so I could get past the windy.com 
>>>>>> graphic because if you try swiping on the graphic the map moves and not 
>>>>>> the 
>>>>>> screen.
>>>>>> That is why I am changing it.
>>>>>>
>>>>>>
>>>>>> On Wed, 11 Sep 2019 at 10:06, Pat  wrote:
>>>>>>
>>>>>>> I guess it's been a long day. I've forgotten how this option works. 
>>>>>>> This option has to be in HTML, so users can display an iframe, a gif, a 
>>>>>>> png, whatever they want. 
>>>>>>>
>>>>>>> Try this, it's worked for me. 
>>>>>>>
>>>>>>> radar_html = ""
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, September 10, 2019 at 8:05:30 PM UTC-4, Greg from Oz 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Good to know that I didn't break it :)
>>>>>>>> I will leave it until the next version then?
>>>>>>>> If you want me to test the latest version let me know. I am good at 
>>>>>>>> breaking things..haha
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Wednesday, 11 September 2019 10:01:02 UTC+10, Pat wrote:
>>>>>>>>>
>>>>>>>>> Yes and apparently not since 1.0 was released :)
>>>>>>>>>
>>>>>>>>> On Tuesday, September 10, 2019 at 7:57:14 PM UTC-4, Greg from Oz 
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Is it designed to be able to change radar sites?
>>>>>>>>>> Has anyone else asked to change the site?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wednesday, 11 September 2019 09:54:07 UTC+10, Pat wrote:
>>>>>>>>>>>
>>>>>>>>>>> Yeah it was a long shot and I was being hopeful that those 
>>>>>>>>>>> numbers maybe were the problem. I just trie

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

[Pat]

I've thought about that but afraid it'd make the skin.conf a mile long. So 
I've opted for a mile long README 
<https://github.com/poblabs/weewx-belchertown> with a section for the 
skin.conf options 
<https://github.com/poblabs/weewx-belchertown#skin-options>, can be updated 
adhoc. This is where the official skin documentation resides currently. 

On Tuesday, September 10, 2019 at 8:24:41 PM UTC-4, Greg from Oz wrote:
>
> I did this and it works!
> radar_html = " target='_blank'>"
>
> As a suggestion maybe you should add comments and examples in the 
> skin.conf for each configurable parameter?
>
> Thanks again.
>
>
> On Wed, 11 Sep 2019 at 10:12, Pat > 
> wrote:
>
>> Yep, since it's HTML you can do whatever you want with it, so a link 
>> should work fine
>>
>> On Tuesday, September 10, 2019 at 8:11:41 PM UTC-4, Greg from Oz wrote:
>>>
>>> Yes that worked.
>>> So I can just add a hyperlink that opens a new page to that as it is 
>>> html?
>>> Thanks
>>>
>>> Like I stated earlier the windy.com is good but when viewed on the 
>>> phone I had to swipe the screen so I could get past the windy.com 
>>> graphic because if you try swiping on the graphic the map moves and not the 
>>> screen.
>>> That is why I am changing it.
>>>
>>>
>>> On Wed, 11 Sep 2019 at 10:06, Pat  wrote:
>>>
>>>> I guess it's been a long day. I've forgotten how this option works. 
>>>> This option has to be in HTML, so users can display an iframe, a gif, a 
>>>> png, whatever they want. 
>>>>
>>>> Try this, it's worked for me. 
>>>>
>>>> radar_html = ""
>>>>
>>>>
>>>>
>>>> On Tuesday, September 10, 2019 at 8:05:30 PM UTC-4, Greg from Oz wrote:
>>>>>
>>>>> Good to know that I didn't break it :)
>>>>> I will leave it until the next version then?
>>>>> If you want me to test the latest version let me know. I am good at 
>>>>> breaking things..haha
>>>>> Thanks
>>>>>
>>>>> On Wednesday, 11 September 2019 10:01:02 UTC+10, Pat wrote:
>>>>>>
>>>>>> Yes and apparently not since 1.0 was released :)
>>>>>>
>>>>>> On Tuesday, September 10, 2019 at 7:57:14 PM UTC-4, Greg from Oz 
>>>>>> wrote:
>>>>>>>
>>>>>>> Is it designed to be able to change radar sites?
>>>>>>> Has anyone else asked to change the site?
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, 11 September 2019 09:54:07 UTC+10, Pat wrote:
>>>>>>>>
>>>>>>>> Yeah it was a long shot and I was being hopeful that those numbers 
>>>>>>>> maybe were the problem. I just tried it myself and it failed so let me 
>>>>>>>> see 
>>>>>>>> if I can get it fixed up in development for the 1.1 release. 
>>>>>>>>
>>>>>>>> On Tuesday, September 10, 2019 at 7:53:05 PM UTC-4, Greg from Oz 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Same thing. It just displays text where the windy.com was and 
>>>>>>>>> shows whatever URL I typed in.
>>>>>>>>>
>>>>>>>>> On Wednesday, 11 September 2019 09:43:03 UTC+10, Pat wrote:
>>>>>>>>>>
>>>>>>>>>> What if you try it without the numbers at the end? 
>>>>>>>>>> http://www.bom.gov.au/radar/IDR033.gif ?
>>>>>>>>>>
>>>>>>>>>> On Tuesday, September 10, 2019 at 7:40:39 PM UTC-4, Greg from Oz 
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> The space does remove the windy.com site.
>>>>>>>>>>>
>>>>>>>>>>> The windy.com is pretty good but if I look at it on the phone 
>>>>>>>>>>> and I swipe up or down and accidentally press the graphic the map 
>>>>>>>>>>> moves so 
>>>>>>>>>>> I would like to change it to a different site.
>>>>>>>>>>>
>>>>>>>>>>> I want to replace it with 
>>>>>>>>>

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

[Pat]

Yep, since it's HTML you can do whatever you want with it, so a link should 
work fine

On Tuesday, September 10, 2019 at 8:11:41 PM UTC-4, Greg from Oz wrote:
>
> Yes that worked.
> So I can just add a hyperlink that opens a new page to that as it is html?
> Thanks
>
> Like I stated earlier the windy.com is good but when viewed on the phone 
> I had to swipe the screen so I could get past the windy.com graphic 
> because if you try swiping on the graphic the map moves and not the screen.
> That is why I am changing it.
>
>
> On Wed, 11 Sep 2019 at 10:06, Pat > 
> wrote:
>
>> I guess it's been a long day. I've forgotten how this option works. This 
>> option has to be in HTML, so users can display an iframe, a gif, a png, 
>> whatever they want. 
>>
>> Try this, it's worked for me. 
>>
>> radar_html = ""
>>
>>
>>
>> On Tuesday, September 10, 2019 at 8:05:30 PM UTC-4, Greg from Oz wrote:
>>>
>>> Good to know that I didn't break it :)
>>> I will leave it until the next version then?
>>> If you want me to test the latest version let me know. I am good at 
>>> breaking things..haha
>>> Thanks
>>>
>>> On Wednesday, 11 September 2019 10:01:02 UTC+10, Pat wrote:
>>>>
>>>> Yes and apparently not since 1.0 was released :)
>>>>
>>>> On Tuesday, September 10, 2019 at 7:57:14 PM UTC-4, Greg from Oz wrote:
>>>>>
>>>>> Is it designed to be able to change radar sites?
>>>>> Has anyone else asked to change the site?
>>>>>
>>>>>
>>>>> On Wednesday, 11 September 2019 09:54:07 UTC+10, Pat wrote:
>>>>>>
>>>>>> Yeah it was a long shot and I was being hopeful that those numbers 
>>>>>> maybe were the problem. I just tried it myself and it failed so let me 
>>>>>> see 
>>>>>> if I can get it fixed up in development for the 1.1 release. 
>>>>>>
>>>>>> On Tuesday, September 10, 2019 at 7:53:05 PM UTC-4, Greg from Oz 
>>>>>> wrote:
>>>>>>>
>>>>>>> Same thing. It just displays text where the windy.com was and shows 
>>>>>>> whatever URL I typed in.
>>>>>>>
>>>>>>> On Wednesday, 11 September 2019 09:43:03 UTC+10, Pat wrote:
>>>>>>>>
>>>>>>>> What if you try it without the numbers at the end? 
>>>>>>>> http://www.bom.gov.au/radar/IDR033.gif ?
>>>>>>>>
>>>>>>>> On Tuesday, September 10, 2019 at 7:40:39 PM UTC-4, Greg from Oz 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> The space does remove the windy.com site.
>>>>>>>>>
>>>>>>>>> The windy.com is pretty good but if I look at it on the phone and 
>>>>>>>>> I swipe up or down and accidentally press the graphic the map moves 
>>>>>>>>> so I 
>>>>>>>>> would like to change it to a different site.
>>>>>>>>>
>>>>>>>>> I want to replace it with 
>>>>>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640 and have 
>>>>>>>>> that as a hyperlink to http://m.bom.gov.au/nsw/moss-vale/radar/
>>>>>>>>>
>>>>>>>>> Similar to what I have on https://weather.ubeaut.work/
>>>>>>>>>
>>>>>>>>> I change the skin.conf radar_html = "
>>>>>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640; but the 
>>>>>>>>> web page doesn't display the graphic it just displays the text 
>>>>>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640
>>>>>>>>>
>>>>>>>>> Other than that it is working and is great.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tuesday, 10 September 2019 22:27:44 UTC+10, Roy Rutten wrote:
>>>>>>>>>>
>>>>>>>>>> Thanks a lot Pat the space did the trick to disable windy.com. i 
>>>>>>>>>> will have a go and see what happens with Chrome. i did find more 
>>>>>>>>>> such 
>>>>>>>>>> errors on Firefox when i went looking for it on google.
>>>>>>>>>>
>>>>>>>>> -- 
>> 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/VyVMEfuxClo/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/832b986c-f66f-45b1-a564-58b6e1fc5494%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/832b986c-f66f-45b1-a564-58b6e1fc5494%40googlegroups.com?utm_medium=email_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/6c5d5061-f435-40c5-a5ff-6f929abc653f%40googlegroups.com.

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

[Pat]

I guess it's been a long day. I've forgotten how this option works. This 
option has to be in HTML, so users can display an iframe, a gif, a png, 
whatever they want. 

Try this, it's worked for me. 

radar_html = ""



On Tuesday, September 10, 2019 at 8:05:30 PM UTC-4, Greg from Oz wrote:
>
> Good to know that I didn't break it :)
> I will leave it until the next version then?
> If you want me to test the latest version let me know. I am good at 
> breaking things..haha
> Thanks
>
> On Wednesday, 11 September 2019 10:01:02 UTC+10, Pat wrote:
>>
>> Yes and apparently not since 1.0 was released :)
>>
>> On Tuesday, September 10, 2019 at 7:57:14 PM UTC-4, Greg from Oz wrote:
>>>
>>> Is it designed to be able to change radar sites?
>>> Has anyone else asked to change the site?
>>>
>>>
>>> On Wednesday, 11 September 2019 09:54:07 UTC+10, Pat wrote:
>>>>
>>>> Yeah it was a long shot and I was being hopeful that those numbers 
>>>> maybe were the problem. I just tried it myself and it failed so let me see 
>>>> if I can get it fixed up in development for the 1.1 release. 
>>>>
>>>> On Tuesday, September 10, 2019 at 7:53:05 PM UTC-4, Greg from Oz wrote:
>>>>>
>>>>> Same thing. It just displays text where the windy.com was and shows 
>>>>> whatever URL I typed in.
>>>>>
>>>>> On Wednesday, 11 September 2019 09:43:03 UTC+10, Pat wrote:
>>>>>>
>>>>>> What if you try it without the numbers at the end? 
>>>>>> http://www.bom.gov.au/radar/IDR033.gif ?
>>>>>>
>>>>>> On Tuesday, September 10, 2019 at 7:40:39 PM UTC-4, Greg from Oz 
>>>>>> wrote:
>>>>>>>
>>>>>>> The space does remove the windy.com site.
>>>>>>>
>>>>>>> The windy.com is pretty good but if I look at it on the phone and I 
>>>>>>> swipe up or down and accidentally press the graphic the map moves so I 
>>>>>>> would like to change it to a different site.
>>>>>>>
>>>>>>> I want to replace it with 
>>>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640 and have that 
>>>>>>> as a hyperlink to http://m.bom.gov.au/nsw/moss-vale/radar/
>>>>>>>
>>>>>>> Similar to what I have on https://weather.ubeaut.work/
>>>>>>>
>>>>>>> I change the skin.conf radar_html = "
>>>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640; but the web 
>>>>>>> page doesn't display the graphic it just displays the text 
>>>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640
>>>>>>>
>>>>>>> Other than that it is working and is great.
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, 10 September 2019 22:27:44 UTC+10, Roy Rutten wrote:
>>>>>>>>
>>>>>>>> Thanks a lot Pat the space did the trick to disable windy.com. i 
>>>>>>>> will have a go and see what happens with Chrome. i did find more such 
>>>>>>>> errors on Firefox when i went looking for it on google.
>>>>>>>>
>>>>>>>

-- 
You received this message because you are subscribed to the Google 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/832b986c-f66f-45b1-a564-58b6e1fc5494%40googlegroups.com.

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

[Pat]

Yes and apparently not since 1.0 was released :)

On Tuesday, September 10, 2019 at 7:57:14 PM UTC-4, Greg from Oz wrote:
>
> Is it designed to be able to change radar sites?
> Has anyone else asked to change the site?
>
>
> On Wednesday, 11 September 2019 09:54:07 UTC+10, Pat wrote:
>>
>> Yeah it was a long shot and I was being hopeful that those numbers maybe 
>> were the problem. I just tried it myself and it failed so let me see if I 
>> can get it fixed up in development for the 1.1 release. 
>>
>> On Tuesday, September 10, 2019 at 7:53:05 PM UTC-4, Greg from Oz wrote:
>>>
>>> Same thing. It just displays text where the windy.com was and shows 
>>> whatever URL I typed in.
>>>
>>> On Wednesday, 11 September 2019 09:43:03 UTC+10, Pat wrote:
>>>>
>>>> What if you try it without the numbers at the end? 
>>>> http://www.bom.gov.au/radar/IDR033.gif ?
>>>>
>>>> On Tuesday, September 10, 2019 at 7:40:39 PM UTC-4, Greg from Oz wrote:
>>>>>
>>>>> The space does remove the windy.com site.
>>>>>
>>>>> The windy.com is pretty good but if I look at it on the phone and I 
>>>>> swipe up or down and accidentally press the graphic the map moves so I 
>>>>> would like to change it to a different site.
>>>>>
>>>>> I want to replace it with 
>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640 and have that 
>>>>> as a hyperlink to http://m.bom.gov.au/nsw/moss-vale/radar/
>>>>>
>>>>> Similar to what I have on https://weather.ubeaut.work/
>>>>>
>>>>> I change the skin.conf radar_html = "
>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640; but the web 
>>>>> page doesn't display the graphic it just displays the text 
>>>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640
>>>>>
>>>>> Other than that it is working and is great.
>>>>>
>>>>>
>>>>> On Tuesday, 10 September 2019 22:27:44 UTC+10, Roy Rutten wrote:
>>>>>>
>>>>>> Thanks a lot Pat the space did the trick to disable windy.com. i 
>>>>>> will have a go and see what happens with Chrome. i did find more such 
>>>>>> errors on Firefox when i went looking for it on google.
>>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google 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/79d6f4c8-deda-43a0-a260-768668eacaf4%40googlegroups.com.

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

[Pat]

Yeah it was a long shot and I was being hopeful that those numbers maybe 
were the problem. I just tried it myself and it failed so let me see if I 
can get it fixed up in development for the 1.1 release. 

On Tuesday, September 10, 2019 at 7:53:05 PM UTC-4, Greg from Oz wrote:
>
> Same thing. It just displays text where the windy.com was and shows 
> whatever URL I typed in.
>
> On Wednesday, 11 September 2019 09:43:03 UTC+10, Pat wrote:
>>
>> What if you try it without the numbers at the end? 
>> http://www.bom.gov.au/radar/IDR033.gif ?
>>
>> On Tuesday, September 10, 2019 at 7:40:39 PM UTC-4, Greg from Oz wrote:
>>>
>>> The space does remove the windy.com site.
>>>
>>> The windy.com is pretty good but if I look at it on the phone and I 
>>> swipe up or down and accidentally press the graphic the map moves so I 
>>> would like to change it to a different site.
>>>
>>> I want to replace it with 
>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640 and have that as 
>>> a hyperlink to http://m.bom.gov.au/nsw/moss-vale/radar/
>>>
>>> Similar to what I have on https://weather.ubeaut.work/
>>>
>>> I change the skin.conf radar_html = "
>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640; but the web page 
>>> doesn't display the graphic it just displays the text 
>>> http://www.bom.gov.au/radar/IDR033.gif?20170728112640
>>>
>>> Other than that it is working and is great.
>>>
>>>
>>> On Tuesday, 10 September 2019 22:27:44 UTC+10, Roy Rutten wrote:
>>>>
>>>> Thanks a lot Pat the space did the trick to disable windy.com. i will 
>>>> have a go and see what happens with Chrome. i did find more such errors on 
>>>> Firefox when i went looking for it on google.
>>>>
>>>

-- 
You received this message because you are subscribed to the Google 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/0c9b9ca3-31a7-4bce-b06f-82adeb2ac4a8%40googlegroups.com.

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

[Pat]

What if you try it without the numbers at the end? 
http://www.bom.gov.au/radar/IDR033.gif ?

On Tuesday, September 10, 2019 at 7:40:39 PM UTC-4, Greg from Oz wrote:
>
> The space does remove the windy.com site.
>
> The windy.com is pretty good but if I look at it on the phone and I swipe 
> up or down and accidentally press the graphic the map moves so I would like 
> to change it to a different site.
>
> I want to replace it with 
> http://www.bom.gov.au/radar/IDR033.gif?20170728112640 and have that as a 
> hyperlink to http://m.bom.gov.au/nsw/moss-vale/radar/
>
> Similar to what I have on https://weather.ubeaut.work/
>
> I change the skin.conf radar_html = "
> http://www.bom.gov.au/radar/IDR033.gif?20170728112640; but the web page 
> doesn't display the graphic it just displays the text 
> http://www.bom.gov.au/radar/IDR033.gif?20170728112640
>
> Other than that it is working and is great.
>
>
> On Tuesday, 10 September 2019 22:27:44 UTC+10, Roy Rutten wrote:
>>
>> Thanks a lot Pat the space did the trick to disable windy.com. i will 
>> have a go and see what happens with Chrome. i did find more such errors on 
>> Firefox when i went looking for it on google.
>>
>

-- 
You received this message because you are subscribed to the Google 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/9880e2f6-b244-494d-be7d-eb5a14747e4c%40googlegroups.com.

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

[Pat]

Creating a custom page isn't documented but it's not hard. Just copy how 
the other pages are created:

1. Create a new folder and create the index.html.tmpl within (copy the file 
from /about as a starter)
2. Then add this new folder to the navigation within header.html.tmpl. 
3. Create the graphs you want in graphs.conf as you normally would. 
4. Initialize and add the chart to your new page. 


Let's use this graphs.conf as an example - it is how I show rx check 
percent on my about page . 

[about]
show_button = false
time_length = 172800 # 48 hours in seconds
aggregate_type = last
aggregate_interval = 300 # 5 min
gapsize = 30 # 5 min

[[rxchart]]
title = ISS Receive Stats
yaxis_max = 100
[[[rxCheckPercent]]]
color = "#268bd2"

[[rxchartyear]]
title = ISS Receive Stats Average
yaxis_max = 100
xaxis_groupby = month
xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
time_length = year
[[[rxCheckPercent]]]
aggregate_type = avg
color = "#268bd2"


Then in the content of your new page, you need to add 2 things. 

1. At the top of the page add:
 
showChart("about");

This initializes the graphs.conf group "about". You see this matches the 
[about] wording in the graph.conf group. 


2. Then where you want to show the graph within the page, add a div with an 
ID of the observation from the graph group that you want to show:





You will see how the id= matches the observations within the double 
brackets. [[rxchart]] and [[rxchartyear]]]

Obviously swap out the graph group and observation names with what you're 
building and that should do it. 



On Tuesday, September 10, 2019 at 5:00:11 AM UTC-4, Kike .Asekas wrote:
>
> Is there any way to create another graphic page? I mean, a page called 
> for example climate where it has specific graphics.
> Where would the graph.conf of that page go?
>

-- 
You received this message because you are subscribed to the Google 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/f253b757-ecb2-4275-9f9d-e3aa4af6de0d%40googlegroups.com.

Re: [weewx-user] Re: Live on a Raspberry Pi 4

[Pat]

Oh wow. Makes sense, good luck!

-- 
You received this message because you are subscribed to the Google 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/a68f9891-dc30-4434-9662-b5798c39bd47%40googlegroups.com.

[weewx-user] Re: Live on a Raspberry Pi 4

[Pat]

Looks good! There's no webcam image showing for me though. 

On Thursday, September 5, 2019 at 10:31:59 AM UTC-4, WindnFog wrote:
>
> I have weewx running on a raspberry pi 4 with a Davis Vantage Vue 
> station.  Seems to work well.  Tried it with the Simulator for about a week 
> and yesterday I went "live" with real data,''
>
> https://www.ve1dx.net/
>
> So far, so good.  I'm downsizing from a CentOS suitcase-sized server to 
> the Pi.  Now if we didn't have that Hurricane Dorian bearing down on us, 
> things would be even better! 
>
> - Paul VE1DX
>

-- 
You received this message because you are subscribed to the Google 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/b6191933-898a-4501-a058-2e28ec928b76%40googlegroups.com.

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

[Pat]

Roy, interesting. I have 3 tabs of Belchertown open (all different test 
sites) all the time and haven't experienced that. I'm also using Chrome 
though. 

To disable the windy iframe, set radar_html = " ". If the "" are close 
together like that, it'll show windy by default. To get rid of windy, an 
empty space should do it. 


On Friday, September 6, 2019 at 1:28:38 PM UTC-4, Roy Rutten wrote:
>
> Hi Pat, 
> First of all thanks for creating this great skin! 
> I have one question, i saw you mention in one of your replies that it's 
> possible to turn off the embeded windy.com iframe but how exactly do i do 
> this? I have tried it with "radar_html = " but with no luck. 
> The reason i want to do this is that if i have the page open in a tab in 
> firefox whether on my windows pc or android phone and the tab is not active 
> for a while Windy will throw a webLG error and i don't want to have that 
> pop-up waiting for me when i return to the page.
>
> Thank you very much,
> Roy
>

-- 
You received this message because you are subscribed to the Google 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/1a52b364-9e5c-485c-a926-c27c66f34cb3%40googlegroups.com.

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

[Pat]

Greg, I've made this change where I flip the font icon if the station is in 
the southern hemisphere. I've committed it to my development branch 
<https://github.com/poblabs/weewx-belchertown/commit/c8290e8ecb35757b3f5371413db0d093b24b02ee>
 
for the skin. It'll be in the 1.1 version.


On Wednesday, September 4, 2019 at 8:00:40 PM UTC-4, Pat wrote:
>
> Greg, great question. The icons are actually a font 
> <https://erikflowers.github.io/weather-icons/>, and it doesn't look like 
> they observe northern or southern hemisphere in their default set. 
>
> Are all moon phases flipped for all southern hemisphere locations? 
>
> If so, I could use CSS to flip the font horizontally if the station's 
> latitude has a negative in it from weewx.conf. That's a potential 
> work-around. 
>
> Here's a jsfiddle I've done just now to show you 
> <https://jsfiddle.net/obrienlabs/uf19t2cq/> what I mean about the flip. 
>
>
>
> On Wednesday, September 4, 2019 at 7:26:51 PM UTC-4, Greg from Oz wrote:
>>
>> Hi Pat
>>
>> I was wondering if there is a way to make the moon icons southern 
>> hemisphere.
>>
>> [image: Screenshot from 2019-09-05 09-23-39.png]
>>
>> The crescent down here is on the left hand side.
>>
>>
>> It's just an aesthetic thing. The skin is great by the way.
>>
>>
>> Thanks
>>
>> Greg 
>>
>>
>> On Tuesday, 3 September 2019 21:53:30 UTC+10, Pat wrote:
>>>
>>> This is a Meteostick issue (and not a skin issue). The stick reports 10 
>>> minute average wind gust, but weewx and the archive schema don't support 
>>> that observation type 
>>> <https://github.com/matthewwall/weewx-meteostick/blob/master/bin/user/meteostick.py#L875-L886>.
>>>  
>>> As a result, wind gusts aren't available in real time from the stick. Weewx 
>>> has to do those calculations on the archive interval, so the website gets 
>>> updated at that time. 
>>>
>>

-- 
You received this message because you are subscribed to the Google 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/42dbeec3-362c-469f-9cb3-046852536bfc%40googlegroups.com.

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

[Pat]

Greg, great question. The icons are actually a font 
<https://erikflowers.github.io/weather-icons/>, and it doesn't look like 
they observe northern or southern hemisphere in their default set. 

Are all moon phases flipped for all southern hemisphere locations? 

If so, I could use CSS to flip the font horizontally if the station's 
latitude has a negative in it from weewx.conf. That's a potential 
work-around. 

Here's a jsfiddle I've done just now to show you 
<https://jsfiddle.net/obrienlabs/uf19t2cq/> what I mean about the flip. 



On Wednesday, September 4, 2019 at 7:26:51 PM UTC-4, Greg from Oz wrote:
>
> Hi Pat
>
> I was wondering if there is a way to make the moon icons southern 
> hemisphere.
>
> [image: Screenshot from 2019-09-05 09-23-39.png]
>
> The crescent down here is on the left hand side.
>
>
> It's just an aesthetic thing. The skin is great by the way.
>
>
> Thanks
>
> Greg 
>
>
> On Tuesday, 3 September 2019 21:53:30 UTC+10, Pat wrote:
>>
>> This is a Meteostick issue (and not a skin issue). The stick reports 10 
>> minute average wind gust, but weewx and the archive schema don't support 
>> that observation type 
>> <https://github.com/matthewwall/weewx-meteostick/blob/master/bin/user/meteostick.py#L875-L886>.
>>  
>> As a result, wind gusts aren't available in real time from the stick. Weewx 
>> has to do those calculations on the archive interval, so the website gets 
>> updated at that time. 
>>
>

-- 
You received this message because you are subscribed to the Google 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/6220f0b9-b3ec-4a06-ad7c-d042a785fec7%40googlegroups.com.

[weewx-user] Re: Acurite Atlas Help

[Pat]

Paul, the driver is very well documented. It might make sense to spend some 
time and read the instructions. It will help you get setup and understand 
what's going on. Otherwise, we'll need to see some debugs, some configs and 
more detail aside from "it's not working". 

https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user


On Tuesday, September 3, 2019 at 6:40:55 PM UTC-4, Xant wrote:
>
>
> Paul
>
> I start to suspect that the problem may not be WeeWX itself, but router.
>
> Are you trying Hijack DNS? Did you setup iptables?
>
> 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/8bb4c8f1-7705-471e-a5a8-fab899ff316c%40googlegroups.com.

[weewx-user] Re: Publishing aggregate data, the topic is TOPIC/loop?

[Pat]

The aggregate topic is hard-coded to /LOOP because weewx operates on the 
LOOP method. You can read more about that in the User Guide 
<http://www.weewx.com/docs/usersguide.htm>.

On Tuesday, September 3, 2019 at 2:28:33 PM UTC-4, Pat wrote:
>
> Yes, aggregate will publish all loop data as a single json array to the 
> /loop topic. 
>
> If you want individual observations published to their individual topic, 
> use aggregation = individual. 
>
> If you want a mixture of both, use aggregation = individual,aggregate
>
>
>
> On Tuesday, September 3, 2019 at 12:59:44 PM UTC-4, Rui Pinto wrote:
>>
>> Hello!! 
>>
>> These are my configurations for transmitting data through Weewx to the 
>> MQTT broker:
>>
>> [StdRESTful]
>> ...
>> [[MQTT]]
>> server_url = mqtt://username:password@localhost:1883/
>> topic = weather/default/default/VantagePro2/
>> unit_system = METRIC
>>
>> aggregation = aggregate   
>>
>> why the data is published to the TOPIC/loop? Is it because i'm publishing 
>> aggregate data so all the observations are pusblished in one go to the loop 
>> level?
>>
>>
>> Best Regards
>>
>>
>>

-- 
You received this message because you are subscribed to the Google 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/a10748a6-5714-4004-a536-7082eacd4d3e%40googlegroups.com.

[weewx-user] Re: Publishing aggregate data, the topic is TOPIC/loop?

[Pat]

Yes, aggregate will publish all loop data as a single json array to the 
/loop topic. 

If you want individual observations published to their individual topic, 
use aggregation = individual. 

If you want a mixture of both, use aggregation = individual,aggregate



On Tuesday, September 3, 2019 at 12:59:44 PM UTC-4, Rui Pinto wrote:
>
> Hello!! 
>
> These are my configurations for transmitting data through Weewx to the 
> MQTT broker:
>
> [StdRESTful]
> ...
> [[MQTT]]
> server_url = mqtt://username:password@localhost:1883/
> topic = weather/default/default/VantagePro2/
> unit_system = METRIC
>
> aggregation = aggregate   
>
> why the data is published to the TOPIC/loop? Is it because i'm publishing 
> aggregate data so all the observations are pusblished in one go to the loop 
> level?
>
>
> Best Regards
>
>
>

-- 
You received this message because you are subscribed to the Google 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/2f32de1f-3785-4fed-a816-12327e3b8533%40googlegroups.com.

[weewx-user] Re: Acurite Atlas Help

[Pat]

Try listen mode and see if you get any results. 

According to the documentation, Listen mode should work without installing 
any other dependant software


On Tuesday, September 3, 2019 at 8:00:07 AM UTC-4, Paul Levin wrote:
>
> OK. Let me try that driver. Do I set this up in "listen" or "sniff" mode?
> Thanks.
>  -- Paul
>
> On Tuesday, September 3, 2019 at 12:42:24 AM UTC-4, Xant wrote:
>>
>> Interceptor Driver by Matthew Wall:
>>
>> https://github.com/matthewwall/weewx-interceptor
>>
>> 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/0d842fb6-30da-4987-9d08-24c7f617ae6c%40googlegroups.com.

[weewx-user] Re: WeatherFlow - any feedback regarding WeeWX

[Pat]

I don't have a WF, but the lack of static IP may not be an issue if your 
router is able to do DHCP Reservations.

If you can get the MAC Address of the device, and set a DHCP Reservation 
for it, then the device will get the same IP every time it renews its DHCP 
lease. This is how I manage all my IoT devices (since most of those cannot 
be set to static). 

On Tuesday, September 3, 2019 at 1:04:47 AM UTC-4, Xant wrote:
>
> Just got WF... so far, Im impress...
>
> Pros:
>
>- much sensors than any other, at this price point
>- MQTT updates at <3secs (maybe due to wind, but looks like a Davis); 
>I never had MQTT turn-out that quick... besides the 60sec actual loop 
>update timeframe (weewx website seems much quicker than "is"; but that 
>is a good thing... others lag till MQTT "connects")
>- easy to install an NO moving parts (impressive... other "early" 
>sellers were charging $1,000+ (without all this sensors) for the same "no 
>moving feature"
>- splitting in 2 units (actually 3 if you count Hub), it counts for 
>REAL OutTemp, as temp sensor does not have to be exposed in direct Sun 
>(without the need of any "radiator")
>
>
> Cons:
>
>- NOT Static IP (commo; specially for us WeeWX peps!; it 
>works other-else, but rather have Static)
>- NOT net hard-wire to Hub (as I would prefer, but only WiFi)
>
>
> As for this post, it seems "I can leave with the Cons, but would 
> appreciate even more if addressed.
>
> So far, better than Acurite Atlas, better than Ambient Weather WS-1550-IP 
> (with ObserverIP).
>
> Dont get me wrong... Atlas and WS-1550-IP are great price-point for the 
> regular Weather Home... but not for the WeeWX geek.
>
>
> 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/35497bf2-7889-4da5-ac3e-82022cff9ca9%40googlegroups.com.

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

[Pat]

This is a Meteostick issue (and not a skin issue). The stick reports 10 
minute average wind gust, but weewx and the archive schema don't support 
that observation type 
.
 
As a result, wind gusts aren't available in real time from the stick. Weewx 
has to do those calculations on the archive interval, so the website gets 
updated at that time. 

-- 
You received this message because you are subscribed to the Google 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/0955aeae-b8d1-491a-a8cb-6d99464667bd%40googlegroups.com.

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

[Pat]

That's one option, so I'm glad it's working. 

The other option is to change the StringFormats float value km_per_hour in 
weewx.conf (then restart weewx once changes). The skin should be using this 
value, so changing it here will update it without changing the code in the 
skin. (something to keep in mind for future skin updates in case it reverts 
back)

On Monday, September 2, 2019 at 7:39:45 AM UTC-4, Stefan wrote:
>
> Hello Andrew.
>
> That`s Works. Thank You very much :-D
>
> Am Montag, 2. September 2019 08:12:20 UTC+2 schrieb Andrew Milner:
>>
>> in the code you edited - have you tried changing maximumfractiondigits 
>> and minimumfractiondigits from 1 to 0?  It seems to me - without having the 
>> skin - that this should do what you want  If it does not do the trick 
>> then put it back to 1 and wait for Pat!!
>>
>>
>>
>> On Monday, 2 September 2019 09:04:07 UTC+3, Stefan wrote:
>>>
>>> Hello.
>>> I wanted to ask if the wind values (in the live view) could be displayed 
>>> as a whole, without them? I mean that. Currently, the values are always 
>>> displayed with 3.2 km/h, but more interesting would be 3 km/h. Is that 
>>> possible?
>>>
>>> Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb 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/10f6c74d-7eca-4028-9f20-b69f4b8206a2%40googlegroups.com.

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

[Pat]

(I'm having a hard time typing today). 

Yes, that was my error. I corrected it in another email. Here it is again, 
please try this:

// Windspeed Metric
if ( data.hasOwnProperty("windSpeed_kph") ) {
jQuery(".curwindspeed").text( parseFloat(parseFloat(data["windSpeed_kph"
])).toLocaleString("$system_locale_js", {minimumFractionDigits: 1, 
maximumFractionDigits: 1}) );
update_windSpeed_kph( parseFloat(parseFloat(data["windSpeed_kph"])).
toLocaleString("$system_locale_js", {minimumFractionDigits: 1, 
maximumFractionDigits: 1}) );
}



On Saturday, August 31, 2019 at 4:20:44 PM UTC-4, Stefan wrote:
>
> I have this line
> jQuery(".curwindspeed").text( 
> parseFloat(parseFloat(data["windSpeed_kph"])).toLocaleString("$system_locale_js",
>  
> {minimumFractionDigits: 1, maximumFractionDigits: 1}) );
> replaced by this line
> update_windSpeed_kph ( parseFloat ( parseFloat ( data [ "windSpeed_kph" 
> ])). toLocaleStri ng ( "$ system_locale_js" ,   { minimumFractionDigits : 
>   1 , maximumFractionDigits :   1 })   );
> but that does not work either. The color is displayed, but it always 
> stays at 0.0 km / h
>
>
> Am Samstag, 31. August 2019 21:20:54 UTC+2 schrieb Pat:
>>
>> Did you delete that line? I had an error and had you delete it but then I 
>> corrected myself and said do not delete and add the new line below it. 
>> Please try 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/0d4df9ef-f5d6-4578-88c4-b4220cf33082%40googlegroups.com.

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

[Pat]

Yes, that was my error (I corrected it in a follow up email). Here it is 
again, please try this. 


// Windspeed Metric
if ( data.hasOwnProperty("windSpeed_kph") ) {
jQuery(".curwindspeed").text( parseFloat(parseFloat(data["windSpeed_kph"
])).toLocaleString("$system_locale_js", {minimumFractionDigits: 1, 
maximumFractionDigits: 1}) );
update_windSpeed_kph ( parseFloat(parseFloat(data["windSpeed_kph"])).
toLocaleString("$system_locale_js", {minimumFractionDigits: 1, 
maximumFractionDigits: 1}) );
}



On Saturday, August 31, 2019 at 4:20:44 PM UTC-4, Stefan wrote:
>
> I have this line
> jQuery(".curwindspeed").text( 
> parseFloat(parseFloat(data["windSpeed_kph"])).toLocaleString("$system_locale_js",
>  
> {minimumFractionDigits: 1, maximumFractionDigits: 1}) );
> replaced by this line
> update_windSpeed_kph ( parseFloat ( parseFloat ( data [ "windSpeed_kph" 
> ])). toLocaleStri ng ( "$ system_locale_js" ,   { minimumFractionDigits : 
>   1 , maximumFractionDigits :   1 })   );
> but that does not work either. The color is displayed, but it always 
> stays at 0.0 km / h
>
>
> Am Samstag, 31. August 2019 21:20:54 UTC+2 schrieb Pat:
>>
>> Did you delete that line? I had an error and had you delete it but then I 
>> corrected myself and said do not delete and add the new line below it. 
>> Please try 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/6f9d8d27-09a2-4e31-a8e8-dabd73d10231%40googlegroups.com.

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

[Pat]

Did you delete that line? I had an error and had you delete it but then I 
corrected myself and said do not delete and add the new line below it. Please 
try 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/073d2983-7c1f-4fa9-b5fa-8b0bb0e2b032%40googlegroups.com.

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

[Pat]

You misunderstood. 

Your function looks good. 

You now need to update this line:

https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L799

To add this:

update_windSpeed_kph( parseFloat(parseFloat(data["windSpeed_kph"])).
toLocaleString("$system_locale_js", {minimumFractionDigits: 1,
 maximumFractionDigits: 1}) );


below it.


On Saturday, August 31, 2019 at 1:40:14 PM UTC-4, Stefan wrote:
>
> Something like that? Does not work too. Or have I misunderstood that?
>
> // Change the color of the windSpeed_kph variable
> function update_windSpeed_kph( wind ) {
>jQuery(".curwindspeed").text( update_windSpeed_kph( 
> parseFloat(parseFloat(data["windSpeed_kph"])).toLocaleString("$system_locale_js",
>  
> {minimumFractionDigits: 1, maximumFractionDigits: 1}) ) );
> if ( wind <= 0 ) {
> jQuery(".curwindspeed").css( "color", "#30bfef" );
> } else if ( wind <= 0 ) {
> jQuery(".curwindspeed").css( "color", "#1fafdd" );
> } else if ( wind <= 4.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(0,172,223,1)" );
> } else if ( wind <= 10 ) {
> jQuery(".curwindspeed").css( "color", "#71bc3c" );
> } else if ( wind <= 12.7 ) {
> jQuery(".curwindspeed").css( "color", "rgba(90,179,41,0.8)" );
> } else if ( wind <= 18.3 ) {
> jQuery(".curwindspeed").css( "color", "rgba(131,173,45,1)" );
> } else if ( wind <= 21.1 ) {
> jQuery(".curwindspeed").css( "color", "rgba(206,184,98,1)" );
> } else if ( wind <= 23.8 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,174,0,0.9)" );
> } else if ( wind <= 26.6 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,153,0,0.9)" );
> } else if ( wind <= 29.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,127,0,1)" );
> } else if ( wind <= 32.2 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,79,0,0.9)" );
> } else if ( wind <= 35 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,69,69,1)" );
> } else if ( wind <= 43.3 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,104,104,1)" );
> } else if ( wind >= 43.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(218,113,113,1)" );
> }
> }
>
> Am Samstag, 31. August 2019 18:53:25 UTC+2 schrieb Pat:
>>
>> It's a 2 step process. Looks like you've done step 1 with creating the 
>> function. You then need to tell this line to use that function 
>> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L799>.
>>  
>> Something like this? Untested:
>>
>> jQuery(".curwindspeed").text( update_windSpeed_kph( parseFloat(parseFloat
>> (data["windSpeed_kph"])).toLocaleString("$system_locale_js", {
>> minimumFractionDigits: 1, maximumFractionDigits: 1}) ) );
>>
>>
>>
>> On Saturday, August 31, 2019 at 12:07:20 PM UTC-4, Stefan wrote:
>>>
>>> Hello Pat.
>>> Thank you for your answer. I think you mean this one. I had made 
>>> various changes, but without success. Which variables do I have to use 
>>> there? 
>>> Do not see any color in the wind.
>>>
>>> See this: https://www.meteo-oberwallis.ch/wetter/glis/user/
>>>
>>> // Change the color of the windSpeed_kph variable
>>> function update_windSpeed_kph( wind ) {
>>> outTemp = parseFloat( wind ).toFixed(0); // Convert back to decimal 
>>> literal
>>> if ( wind <= 0 ) {
>>> jQuery(".curwindspeed").css( "color", "#1278c8" );
>>> } else if ( wind <= -3.8 ) {
>>> jQuery(".curwindspeed").css( "color", "#30bfef" );
>>> } else if ( wind <= 0 ) {
>>> jQuery(".curwindspeed").css( "color", "#1fafdd" );
>>> } else if ( wind <= 4.4 ) {
>>> jQuery(".curwindspeed").css( "color", "rgba(0,172,223,1)" );
>>> } else if ( wind <= 10 ) {
>>> jQuery(".curwindspeed").css( "color", &

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

[Pat]

Actually, that won't work. Leave that line alone but below it, add the 
function call. Untested but this seems like it should work. 

update_windSpeed_kph( parseFloat(parseFloat(data["windSpeed_kph"])).
toLocaleString("$system_locale_js", {minimumFractionDigits: 1, 
maximumFractionDigits: 1}) );




On Saturday, August 31, 2019 at 12:53:25 PM UTC-4, Pat wrote:
>
> It's a 2 step process. Looks like you've done step 1 with creating the 
> function. You then need to tell this line to use that function 
> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L799>.
>  
> Something like this? Untested:
>
> jQuery(".curwindspeed").text( update_windSpeed_kph( parseFloat(parseFloat(
> data["windSpeed_kph"])).toLocaleString("$system_locale_js", {
> minimumFractionDigits: 1, maximumFractionDigits: 1}) ) );
>
>
>
> On Saturday, August 31, 2019 at 12:07:20 PM UTC-4, Stefan wrote:
>>
>> Hello Pat.
>> Thank you for your answer. I think you mean this one. I had made various 
>> changes, but without success. Which variables do I have to use there? 
>> Do not see any color in the wind.
>>
>> See this: https://www.meteo-oberwallis.ch/wetter/glis/user/
>>
>> // Change the color of the windSpeed_kph variable
>> function update_windSpeed_kph( wind ) {
>> outTemp = parseFloat( wind ).toFixed(0); // Convert back to decimal 
>> literal
>> if ( wind <= 0 ) {
>> jQuery(".curwindspeed").css( "color", "#1278c8" );
>> } else if ( wind <= -3.8 ) {
>> jQuery(".curwindspeed").css( "color", "#30bfef" );
>> } else if ( wind <= 0 ) {
>> jQuery(".curwindspeed").css( "color", "#1fafdd" );
>> } else if ( wind <= 4.4 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(0,172,223,1)" );
>> } else if ( wind <= 10 ) {
>> jQuery(".curwindspeed").css( "color", "#71bc3c" );
>> } else if ( wind <= 12.7 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(90,179,41,0.8)" );
>> } else if ( wind <= 18.3 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(131,173,45,1)" );
>> } else if ( wind <= 21.1 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(206,184,98,1)" );
>> } else if ( wind <= 23.8 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(255,174,0,0.9)" );
>> } else if ( wind <= 26.6 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(255,153,0,0.9)" );
>> } else if ( wind <= 29.4 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(255,127,0,1)" );
>> } else if ( wind <= 32.2 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(255,79,0,0.9)" );
>> } else if ( wind <= 35 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(255,69,69,1)" );
>> } else if ( wind <= 43.3 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(255,104,104,1)" );
>> } else if ( wind >= 43.4 ) {
>> jQuery(".curwindspeed").css( "color", "rgba(218,113,113,1)" );
>> }
>> }
>>
>> Am Samstag, 31. August 2019 15:03:59 UTC+2 schrieb Pat:
>>>
>>> The code doesn't exist in the skin as it is right now, but it would be 
>>> easy to add. 
>>>
>>> Create a new function in the belchertown.js.tmpl file for the wind speed 
>>> and the colors you want. You could copy something like this for the 
>>> temperature 
>>> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L87-L120>.
>>>  
>>> Then have the wind speed go through that function 
>>> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L793-L804>
>>>  
>>> to change it's color. Use the temperature live section 
>>> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L751-L755>
>>>  
>>> for an example of this. 
>>>
>>> On Saturday, August 31, 2019 at 5:53:06 AM UTC-4, Stefan wrote:
>>>>
>>>> Hello.
>>>> I have a question. Can the wind speed in Belchertown also be colored? eg 
>>>> from 40 km yellow and from 80 red and from 120 purple? I mean in live 
>>>> view.
>>>>
>>>> [image: Unbenannt.PNG]
>>>>
>>>> Thanks for Help
>>>>
>>>>
>>>>

-- 
You received this message because you are subscribed to the Google 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/0cadb877-4671-43a7-876c-d835470c531c%40googlegroups.com.

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

[Pat]

It's a 2 step process. Looks like you've done step 1 with creating the 
function. You then need to tell this line to use that function 
<https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L799>.
 
Something like this? Untested:

jQuery(".curwindspeed").text( update_windSpeed_kph( parseFloat(parseFloat(
data["windSpeed_kph"])).toLocaleString("$system_locale_js", {
minimumFractionDigits: 1, maximumFractionDigits: 1}) ) );



On Saturday, August 31, 2019 at 12:07:20 PM UTC-4, Stefan wrote:
>
> Hello Pat.
> Thank you for your answer. I think you mean this one. I had made various 
> changes, but without success. Which variables do I have to use there? 
> Do not see any color in the wind.
>
> See this: https://www.meteo-oberwallis.ch/wetter/glis/user/
>
> // Change the color of the windSpeed_kph variable
> function update_windSpeed_kph( wind ) {
> outTemp = parseFloat( wind ).toFixed(0); // Convert back to decimal 
> literal
> if ( wind <= 0 ) {
> jQuery(".curwindspeed").css( "color", "#1278c8" );
> } else if ( wind <= -3.8 ) {
> jQuery(".curwindspeed").css( "color", "#30bfef" );
> } else if ( wind <= 0 ) {
> jQuery(".curwindspeed").css( "color", "#1fafdd" );
> } else if ( wind <= 4.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(0,172,223,1)" );
> } else if ( wind <= 10 ) {
> jQuery(".curwindspeed").css( "color", "#71bc3c" );
> } else if ( wind <= 12.7 ) {
> jQuery(".curwindspeed").css( "color", "rgba(90,179,41,0.8)" );
> } else if ( wind <= 18.3 ) {
> jQuery(".curwindspeed").css( "color", "rgba(131,173,45,1)" );
> } else if ( wind <= 21.1 ) {
> jQuery(".curwindspeed").css( "color", "rgba(206,184,98,1)" );
> } else if ( wind <= 23.8 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,174,0,0.9)" );
> } else if ( wind <= 26.6 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,153,0,0.9)" );
> } else if ( wind <= 29.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,127,0,1)" );
> } else if ( wind <= 32.2 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,79,0,0.9)" );
> } else if ( wind <= 35 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,69,69,1)" );
> } else if ( wind <= 43.3 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,104,104,1)" );
> } else if ( wind >= 43.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(218,113,113,1)" );
> }
> }
>
> Am Samstag, 31. August 2019 15:03:59 UTC+2 schrieb Pat:
>>
>> The code doesn't exist in the skin as it is right now, but it would be 
>> easy to add. 
>>
>> Create a new function in the belchertown.js.tmpl file for the wind speed 
>> and the colors you want. You could copy something like this for the 
>> temperature 
>> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L87-L120>.
>>  
>> Then have the wind speed go through that function 
>> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L793-L804>
>>  
>> to change it's color. Use the temperature live section 
>> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl#L751-L755>
>>  
>> for an example of this. 
>>
>> On Saturday, August 31, 2019 at 5:53:06 AM UTC-4, Stefan wrote:
>>>
>>> Hello.
>>> I have a question. Can the wind speed in Belchertown also be colored? eg 
>>> from 40 km yellow and from 80 red and from 120 purple? I mean in live 
>>> view.
>>>
>>> [image: Unbenannt.PNG]
>>>
>>> Thanks for Help
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google 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/01451bd3-3beb-4edf-ab38-ec76717d175a%40googlegroups.com.

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

[Pat]

The code doesn't exist in the skin as it is right now, but it would be easy 
to add. 

Create a new function in the belchertown.js.tmpl file for the wind speed 
and the colors you want. You could copy something like this for the 
temperature 
.
 
Then have the wind speed go through that function 

 
to change it's color. Use the temperature live section 

 
for an example of this. 

On Saturday, August 31, 2019 at 5:53:06 AM UTC-4, Stefan wrote:
>
> Hello.
> I have a question. Can the wind speed in Belchertown also be colored? eg 
> from 40 km yellow and from 80 red and from 120 purple? I mean in live 
> view.
>
> [image: Unbenannt.PNG]
>
> Thanks for Help
>
>
>

-- 
You received this message because you are subscribed to the Google 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/ca710529-774a-4356-8b69-9213aeb0c3f0%40googlegroups.com.

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

[Pat]

I added minorTicks to the 1.1 development version in a commit a couple of 
weeks ago 
<https://github.com/poblabs/weewx-belchertown/commit/b3066dcd9a631d111860ac7551bc6fc64523a0de>.
  
Use yAxis_minorTicks if you want to try it. I don't think it's documented 
yet in my wiki though (but it follows the same rules as the official highcharts 
yaxis minorticks <https://api.highcharts.com/highcharts/yAxis.minorTicks>)

I am also working on a chart type called weatherRadial in the development 
version. I commited it as a basic feature today but has a bit of work to go 
before it's done. 

Details are here 
<https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#the-weatherradial-observation>,
 
and if anyone's interested install the 1.1b5 development version to try it 
out. (Since this is development version, please note I may rename it (to 
something like outTempRadial or outTempRanges) in future release).


On Saturday, August 24, 2019 at 10:56:12 PM UTC-4, rich T wrote:
>
> Pat...Here are the latest graphs. I'm using Y axis 0 and Y axis 1 now.  Is 
> there a way to add minor grid lines and zones?
>
> [[Rain_Thunder_Day]]  
>   
>title = Past 24 Hr Rain / Lightning
>time_length = 86400
>aggregate_type = sum
>aggregate_interval = 900
>gapsize = 90
>
>[[[rainRate]]]
> name = Rain Rate
> yAxis = 1
> zIndex = 0
> color = Orange
> dashStyle = DashDot
>
>[[[rainTotal]]]
> name = Rain Total
> yAxis = 1
> zIndex = 1
> color = Yellow
> dashStyle = ShortDash
> 
> [[[outTemp]]]
> name = Temperature
> aggregate_type = max
> yAxis = 1
> zIndex = 2
> color = Cyan
> 
>  [[[dewpoint]]]
> name = Dewpoint
> aggregate_type = max
> yAxis = 1
> zIndex = 3
> color = Purple 
> dashStyle = Dash
> 
>  [[[lightning_strikes]]]
> name = Lightning Count
> aggregate_type = sum
> yAxis = 0
> yAxisLabel = AS3935 Lightning Strikes
> zIndex = 1
> color = Red
> type = column 
>  
>  
>  [[Rain_Thunder_Week]]
>  
> title = Weekly Rain / Lightning
> time_length = 604800
> aggregate_type = sum
> aggregate_interval = 900
> gapsize = 90
> 
>[[[rainRate]]]
> name = Rain Rate
> yAxis = 1
> zIndex = 0
> color = Orange
> dashStyle = DashDot
>
>[[[rainTotal]]]
> name = Rain Total
> yAxis = 1
> zIndex = 1
> color = Yellow
> dashStyle = ShortDash
> 
> [[[outTemp]]]
> name = Temperature
> aggregate_type = max
> yAxis = 1
> zIndex = 2
> color = Cyan
> 
>  [[[dewpoint]]]
> name = Dewpoint
> aggregate_type = max
> yAxis = 1
> zIndex = 3
> color = Purple 
> dashStyle = Dash
> 
>  [[[lightning_strikes]]]
> name = Lightning Count
> aggregate_type = sum
> yAxis = 0
> yAxisLabel = AS3935 Lightning Strikes
> zIndex = 1
> color = Red
> type = column
>
> 
>   [[Rain_Thunder_Month]]  
>   
>title = Monthly Rain / Lightning
>time_length = 2592000 # Last 30 days
>tooltip_date_format = " LL"
>aggregate_type = sum
>aggregate_interval = 86400 # 1 day
>gapsize = 8640 # 1 day in milliseconds
> 
> [[[rainRate]]]
> name = Rain Rate
> yAxis = 1
> zIndex = 0
> color = Orange
> dashStyle = DashDot
>
>[[[rainTotal]]]
> name = Rain Total
> yAxis = 1
> zIndex = 1
> color = Yellow
> dashStyle = ShortDash
> 
> [[[outTemp]]]
> name = Temperature
> aggregate_type = max
> yAxis = 1
> zIndex = 2
> color = Cyan
> 
>  [[[dewpoint]]]
>

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

[Pat]

Setting yaxis to 3 for me didn't work with my chart setup (I didn't try 
yours), but if I kept re-using yaxis 0 or yaxis 1 it stacks them. 

On Friday, August 23, 2019 at 4:15:22 PM UTC-4, rich T wrote:
>
> I believe it is valid by defintion.  "The Y axis or value axis. Normally 
> this is the vertical axis, though if the chart is inverted this is the 
> horizontal axis. In case of multiple axes, the yAxis node is an array of 
> configuration objects."
>
> On Friday, August 23, 2019 at 2:26:39 PM UTC-4, Pat wrote:
>>
>> Interesting! I thought something like "yAxis = 3" would be invalid, so 
>> maybe Highcharts is using that in some way? 
>>
>> On Friday, August 23, 2019 at 2:24:53 PM UTC-4, rich T wrote:
>>>
>>> By adding dewpoint to yAxis 3 is the only way so far got it to plot.  
>>> Later going try a couple more things on that chart.
>>>
>>> Rich
>>>
>>> On Friday, August 23, 2019 at 1:19:58 PM UTC-4, Pat wrote:
>>>
>>>> You're doing a lot more with this than I thought. Looks good! Your 
>>>> right side yAxis has 2 labels, I wonder why that is? 
>>>>
>>>> I've been thinking if I need to figure out a way to support multiple 
>>>> yAxis (like shown in this demo 
>>>> <https://www.highcharts.com/demo/combo-multi-axes>) and how I would 
>>>> add that. I see you're trying opposite = true, but I still need to define 
>>>> a 
>>>> yAxis to a a y axis array number. I need some time to sit down and think 
>>>> about that. 
>>>>
>>>>
>>>> On Thursday, August 22, 2019 at 11:30:35 PM UTC-4, rich T wrote:
>>>>>
>>>>> Here is the latest:
>>>>>
>>>>> In the graph.conf
>>>>>
>>>>> [Rain_Thunder]
>>>>>
>>>>> title = Rain / Lightning
>>>>> show_button = true 
>>>>> button_text = "Lightning"
>>>>> 
>>>>>  
>>>>>  [[Rain_Thunder_Day]]  
>>>>>   
>>>>>title = Daily Rain / Lightning
>>>>>time_length = 86400
>>>>>aggregate_type = sum
>>>>>aggregate_interval = 900
>>>>>gapsize = 90
>>>>>
>>>>>[[[rainRate]]]
>>>>> name = Rain Rate
>>>>> yAxis = 1
>>>>> zIndex = 1
>>>>> color = red
>>>>> #opposite = true
>>>>> dashStyle = DashDot
>>>>>
>>>>> [[[rainTotal]]]
>>>>> name = Rain Total
>>>>> yAxis = 1
>>>>> zIndex = 2
>>>>> dashStyle = ShortDash
>>>>> color = blue
>>>>> 
>>>>> [[[lightning_strikes]]]
>>>>> name = Lightning Count
>>>>> aggregate_type = sum
>>>>> yAxis = 0
>>>>> #yAxisLabel = AS3935 Lightning Count
>>>>> #opposite = true
>>>>> zIndex = 0
>>>>> color = orange
>>>>> type = column
>>>>>     
>>>>> [[[outTemp]]]
>>>>> aggregate_type = max
>>>>> yAxis = 2
>>>>> zIndex = 4
>>>>> name = Temperature
>>>>> dashStyle = Dot
>>>>> color = lime
>>>>> 
>>>>> [[[dewpoint]]]
>>>>> aggregate_type = max
>>>>> yAxis = 2
>>>>> zIndex = 3
>>>>> color = maroon
>>>>> yAxisLabel = AS3935 Lightning Strikes
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, August 21, 2019 at 2:45:18 PM UTC-4, Ron Sell wrote:
>>>>>>
>>>>>> Is there a way to do a count to get the value on a chart?
>>>>>>
>>>>>> It looks like the lightning strikes are stored with 
>>>>>> time,distance,energy in the database. Can I just count the records and 
>>>>>> use 
>>>>>> that as my l

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

[Pat]

Interesting! I thought something like "yAxis = 3" would be invalid, so 
maybe Highcharts is using that in some way? 

On Friday, August 23, 2019 at 2:24:53 PM UTC-4, rich T wrote:
>
> By adding dewpoint to yAxis 3 is the only way so far got it to plot.  
> Later going try a couple more things on that chart.
>
> Rich
>
> On Friday, August 23, 2019 at 1:19:58 PM UTC-4, Pat wrote:
>
>> You're doing a lot more with this than I thought. Looks good! Your right 
>> side yAxis has 2 labels, I wonder why that is? 
>>
>> I've been thinking if I need to figure out a way to support multiple 
>> yAxis (like shown in this demo 
>> <https://www.highcharts.com/demo/combo-multi-axes>) and how I would add 
>> that. I see you're trying opposite = true, but I still need to define a 
>> yAxis to a a y axis array number. I need some time to sit down and think 
>> about that. 
>>
>>
>> On Thursday, August 22, 2019 at 11:30:35 PM UTC-4, rich T wrote:
>>>
>>> Here is the latest:
>>>
>>> In the graph.conf
>>>
>>> [Rain_Thunder]
>>>
>>> title = Rain / Lightning
>>> show_button = true 
>>> button_text = "Lightning"
>>> 
>>>  
>>>  [[Rain_Thunder_Day]]  
>>>   
>>>title = Daily Rain / Lightning
>>>time_length = 86400
>>>aggregate_type = sum
>>>aggregate_interval = 900
>>>gapsize = 90
>>>
>>>[[[rainRate]]]
>>> name = Rain Rate
>>> yAxis = 1
>>> zIndex = 1
>>> color = red
>>> #opposite = true
>>> dashStyle = DashDot
>>>
>>> [[[rainTotal]]]
>>> name = Rain Total
>>> yAxis = 1
>>> zIndex = 2
>>> dashStyle = ShortDash
>>> color = blue
>>> 
>>> [[[lightning_strikes]]]
>>> name = Lightning Count
>>> aggregate_type = sum
>>> yAxis = 0
>>> #yAxisLabel = AS3935 Lightning Count
>>> #opposite = true
>>> zIndex = 0
>>> color = orange
>>> type = column
>>> 
>>> [[[outTemp]]]
>>> aggregate_type = max
>>> yAxis = 2
>>> zIndex = 4
>>> name = Temperature
>>> dashStyle = Dot
>>> color = lime
>>> 
>>> [[[dewpoint]]]
>>> aggregate_type = max
>>> yAxis = 2
>>> zIndex = 3
>>> color = maroon
>>> yAxisLabel = AS3935 Lightning Strikes
>>>
>>>
>>>
>>> On Wednesday, August 21, 2019 at 2:45:18 PM UTC-4, Ron Sell wrote:
>>>>
>>>> Is there a way to do a count to get the value on a chart?
>>>>
>>>> It looks like the lightning strikes are stored with 
>>>> time,distance,energy in the database. Can I just count the records and use 
>>>> that as my lightning strikes total? I just don't know how to show the 
>>>> count 
>>>> on the chart.
>>>>
>>>> On Monday, 19 August 2019 23:07:01 UTC-4, rich T wrote:
>>>>>
>>>>> Pat this is what I got so far.
>>>>>
>>>>> [[Rain_Thunder]]
>>>>> title = Rain and Lightning
>>>>> time_length = 604800
>>>>> aggregate_type = sum
>>>>> aggregate_interval = 3600
>>>>> gapsize = 360
>>>>> 
>>>>> [[[rainTotal]]]
>>>>> name = Rain Total
>>>>> yAxis = 1
>>>>> zIndex = 1
>>>>> 
>>>>> [[[rainRate]]]
>>>>> name = Rain Rate
>>>>> yAxis = 1
>>>>> zIndex = 2
>>>>> opposite = true
>>>>> 
>>>>> [[[lightning_strikes]]]
>>>>> name = Lightning Count
>>>>> aggregate_type = sum
>>>>> yAxis = 0
>>>>> yAxisLa

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

[Pat]

You're doing a lot more with this than I thought. Looks good! Your right 
side yAxis has 2 labels, I wonder why that is? 

I've been thinking if I need to figure out a way to support multiple yAxis 
(like 
shown in this demo <https://www.highcharts.com/demo/combo-multi-axes>) and 
how I would add that. I see you're trying opposite = true, but I still need 
to define a yAxis to a a y axis array number. I need some time to sit down 
and think about that. 


On Thursday, August 22, 2019 at 11:30:35 PM UTC-4, rich T wrote:
>
> Here is the latest:
>
> In the graph.conf
>
> [Rain_Thunder]
>
> title = Rain / Lightning
> show_button = true 
> button_text = "Lightning"
> 
>  
>  [[Rain_Thunder_Day]]  
>   
>title = Daily Rain / Lightning
>time_length = 86400
>aggregate_type = sum
>aggregate_interval = 900
>gapsize = 90
>
>[[[rainRate]]]
> name = Rain Rate
> yAxis = 1
> zIndex = 1
> color = red
> #opposite = true
> dashStyle = DashDot
>
> [[[rainTotal]]]
> name = Rain Total
> yAxis = 1
> zIndex = 2
> dashStyle = ShortDash
> color = blue
> 
> [[[lightning_strikes]]]
> name = Lightning Count
> aggregate_type = sum
> yAxis = 0
> #yAxisLabel = AS3935 Lightning Count
> #opposite = true
> zIndex = 0
> color = orange
> type = column
> 
> [[[outTemp]]]
> aggregate_type = max
> yAxis = 2
> zIndex = 4
> name = Temperature
> dashStyle = Dot
> color = lime
> 
> [[[dewpoint]]]
> aggregate_type = max
> yAxis = 2
> zIndex = 3
> color = maroon
> yAxisLabel = AS3935 Lightning Strikes
>
>
>
> On Wednesday, August 21, 2019 at 2:45:18 PM UTC-4, Ron Sell wrote:
>>
>> Is there a way to do a count to get the value on a chart?
>>
>> It looks like the lightning strikes are stored with time,distance,energy 
>> in the database. Can I just count the records and use that as my lightning 
>> strikes total? I just don't know how to show the count on the chart.
>>
>> On Monday, 19 August 2019 23:07:01 UTC-4, rich T wrote:
>>>
>>> Pat this is what I got so far.
>>>
>>> [[Rain_Thunder]]
>>> title = Rain and Lightning
>>> time_length = 604800
>>> aggregate_type = sum
>>> aggregate_interval = 3600
>>> gapsize = 360
>>> 
>>> [[[rainTotal]]]
>>> name = Rain Total
>>> yAxis = 1
>>> zIndex = 1
>>> 
>>> [[[rainRate]]]
>>> name = Rain Rate
>>> yAxis = 1
>>> zIndex = 2
>>> opposite = true
>>> 
>>> [[[lightning_strikes]]]
>>> name = Lightning Count
>>> aggregate_type = sum
>>> yAxis = 0
>>> yAxisLabel = Lightning Count
>>> zIndex = 0
>>> type = column  
>>>
>>> Rich
>>>
>>> On Sunday, August 18, 2019 at 8:01:53 PM UTC-4, Pat wrote:
>>>>
>>>> Rich have you found a good way to have lightning on the rain chart? 
>>>>
>>>> When I try adding it to yaxis = 1 (or 0) it messed up the chart. I know 
>>>> Highcharts supports *multiple *y axis' but Belchertown doesn't. Wasn't 
>>>> sure if you've found some interesting combination that has it all on the 
>>>> same chart.
>>>>
>>>> On Friday, August 16, 2019 at 6:31:50 PM UTC-4, rich T wrote:
>>>>>
>>>>> In the graphs.conf file add
>>>>>
>>>>> [homepage]
>>>>>
>>>>> .
>>>>>
>>>>> [[Lightning_chart]]
>>>>> title = Lightning (Last 3 Hour)
>>>>> time_length = 10800
>>>>> aggregate_interval = 300
>>>>> gapsize = 108000
>>>>> type = column
>>>>> 
>>>>> [[[lightning_strikes]]]
>>>>> name = L

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

[Pat]

Rich, thanks. I've been trying to find the right balance too, so I'll give 
this a try. We had some strong storms roll through yesterday which knocked 
power out for a good part of the day and evening. I'll try something 
tonight. 

I also saw this in a previous reply:

> Would like to see the rain total as a spline and lightning strikes as a 
column.

You can specify each observation type's chart type if you want. For 
example, in the code below I made dewpoint a column chart. You can apply 
this to your lightning chart if you wanted. 

[[chart1]]
title = Temperature
yAxisLabel = ""
[[[outTemp]]]
name = Temperature
zIndex = 1
[[[windchill]]]
[[[heatindex]]]
[[[dewpoint]]]
color = gray
type = column




On Monday, August 19, 2019 at 11:07:01 PM UTC-4, rich T wrote:
>
> Pat this is what I got so far.
>
> [[Rain_Thunder]]
> title = Rain and Lightning
> time_length = 604800
> aggregate_type = sum
> aggregate_interval = 3600
> gapsize = 360
> 
> [[[rainTotal]]]
> name = Rain Total
> yAxis = 1
> zIndex = 1
> 
> [[[rainRate]]]
> name = Rain Rate
> yAxis = 1
> zIndex = 2
> opposite = true
> 
> [[[lightning_strikes]]]
> name = Lightning Count
> aggregate_type = sum
> yAxis = 0
> yAxisLabel = Lightning Count
> zIndex = 0
> type = column  
>
> Rich
>
> On Sunday, August 18, 2019 at 8:01:53 PM UTC-4, Pat wrote:
>>
>> Rich have you found a good way to have lightning on the rain chart? 
>>
>> When I try adding it to yaxis = 1 (or 0) it messed up the chart. I know 
>> Highcharts supports *multiple *y axis' but Belchertown doesn't. Wasn't 
>> sure if you've found some interesting combination that has it all on the 
>> same chart.
>>
>> On Friday, August 16, 2019 at 6:31:50 PM UTC-4, rich T wrote:
>>>
>>> In the graphs.conf file add
>>>
>>> [homepage]
>>>
>>> .
>>>
>>> [[Lightning_chart]]
>>> title = Lightning (Last 3 Hour)
>>> time_length = 10800
>>> aggregate_interval = 300
>>> gapsize = 108000
>>> type = column
>>> 
>>> [[[lightning_strikes]]]
>>> name = Lightning Count
>>> zIndex = 1
>>> aggregate_type = sum
>>>
>>> Ensure the DB to contains the lightning fields, if not the db needs to 
>>> extended. 
>>> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>>>
>>> On Friday, August 16, 2019 at 3:15:20 PM UTC-4, Ron Sell wrote:
>>>>
>>>> Is there a way to show the lightning strikes? I was looking to add 
>>>> chart. 
>>>>
>>>> thanks 
>>>>
>>>> On Saturday, 1 June 2019 12:57:56 UTC-4, 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 
>>>>> relea

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

[Pat]

Rich have you found a good way to have lightning on the rain chart? 

When I try adding it to yaxis = 1 (or 0) it messed up the chart. I know 
Highcharts supports *multiple *y axis' but Belchertown doesn't. Wasn't sure 
if you've found some interesting combination that has it all on the same 
chart.

On Friday, August 16, 2019 at 6:31:50 PM UTC-4, rich T wrote:
>
> In the graphs.conf file add
>
> [homepage]
>
> .
>
> [[Lightning_chart]]
> title = Lightning (Last 3 Hour)
> time_length = 10800
> aggregate_interval = 300
> gapsize = 108000
> type = column
> 
> [[[lightning_strikes]]]
> name = Lightning Count
> zIndex = 1
> aggregate_type = sum
>
> Ensure the DB to contains the lightning fields, if not the db needs to 
> extended. 
> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>
> On Friday, August 16, 2019 at 3:15:20 PM UTC-4, Ron Sell wrote:
>>
>> Is there a way to show the lightning strikes? I was looking to add chart. 
>>
>> thanks 
>>
>> On Saturday, 1 June 2019 12:57:56 UTC-4, 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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/41f4eafe-dae9-43de-a8e6-671f46bdf4fc%40googlegroups.com.

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

[Pat]

Not without more detail. 15.4 is a little arbitrary for me. Is this km? mi? 
count? Is this a chart thing or a database thing? I'd need more details and 
possibly configs

On Sunday, August 18, 2019 at 4:39:47 PM UTC-4, Ron Sell wrote:
>
> got it thanks. One last thing my lightning strikes are coming up 15.4. any 
> idea why ?
>
>
>
> On Sun, Aug 18, 2019 at 3:27 PM Pat > 
> wrote:
>
>> Just remove the months from the chart's xaxis_categories  where you know 
>> you do not have data for. 
>>
>> On Sunday, August 18, 2019 at 3:25:45 PM UTC-4, Ron Sell wrote:
>>>
>>> Do you know why it would show January as the month for both 
>>> Climatological and Lightening ? I just extended the database yesterday for 
>>> the lightening. 
>>>
>>> On Sun, Aug 18, 2019 at 8:34 AM Pat  wrote:
>>>
>>>> Here's what I have for my climatological values chart on the homepage 
>>>> <https://belchertownweather.com/go/belchertown>:
>>>>
>>>> [[avgclimatethisyear]]
>>>> title = "Average Climatological Values for This Year"
>>>> type = spline
>>>> time_length = year
>>>> aggregate_type = max
>>>> aggregate_interval = 86400 # 1 day
>>>> gapsize = 8640
>>>> xaxis_groupby = month
>>>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>>>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>>> [[[outTemp]]]
>>>> zIndex = 2
>>>> name = Max Temperature
>>>> color = red
>>>> [[[outTemp_min]]]
>>>> name = Min Temperature
>>>> observation_type = outTemp
>>>> aggregate_type = min
>>>> zIndex = 2
>>>> [[[rainTotal]]]
>>>> name = Rain Total
>>>> type = column
>>>> yAxis = 1
>>>> zIndex = 0
>>>> color = "#268bd2"
>>>>
>>>>
>>>> To chart other years use something like this with the year_specific 
>>>> option
>>>>
>>>>
>>>> [[chart1]]
>>>> title = "Average Climatological Values for 2018"
>>>> time_length = year_specific
>>>> year_specific = 2018
>>>> xaxis_groupby = month
>>>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>>>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>>> [[[outTemp]]]
>>>> zIndex = 2
>>>> name = Max Temperature
>>>> color = "#fc0404"
>>>> marker
>>>> enabled = true
>>>> radius = 4
>>>> [[[outTemp_min]]]
>>>> name = Min Temperature
>>>> observation_type = outTemp
>>>> aggregate_type = min
>>>> zIndex = 2
>>>> color = "#173c6a"
>>>> marker
>>>> enabled = true
>>>> radius = 4
>>>> [[[rainTotal]]]
>>>> name = Rain Total
>>>> type = column
>>>> yAxis = 1
>>>> zIndex = 0
>>>> color = "#438bd6"
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sunday, August 18, 2019 at 8:29:02 AM UTC-4, Ron Sell wrote:
>>>>>
>>>>> Awesome thank you so much.
>>>>>
>>>>> I am also attempting to add Average Climatological Valuesfor This Year.
>>>>> I’ll see if I can get that one going too.
>>>>>
>>>>> On Sun, Aug 18, 2019 at 8:25 AM Pat  wrote:
>>>>>
>>>>>> If you're looking at the lightning charts that I'm doing on my 
>>>>>> homepage <https://belchertownweather.com/go/belchertown>, add 
>>>>>> something like this to your homepage's graph group inside graphs.conf
>>>>>>
>>>>>> [[lightninggroupby]]
>>>>>> title = Lightning Strikes This Year
>>>>>> yAxisLabel = ""
>&g

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

[Pat]

Just remove the months from the chart's xaxis_categories  where you know 
you do not have data for. 

On Sunday, August 18, 2019 at 3:25:45 PM UTC-4, Ron Sell wrote:
>
> Do you know why it would show January as the month for both Climatological 
> and Lightening ? I just extended the database yesterday for the lightening. 
>
> On Sun, Aug 18, 2019 at 8:34 AM Pat > 
> wrote:
>
>> Here's what I have for my climatological values chart on the homepage 
>> <https://belchertownweather.com/go/belchertown>:
>>
>> [[avgclimatethisyear]]
>> title = "Average Climatological Values for This Year"
>> type = spline
>> time_length = year
>> aggregate_type = max
>> aggregate_interval = 86400 # 1 day
>> gapsize = 8640
>> xaxis_groupby = month
>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>> [[[outTemp]]]
>> zIndex = 2
>> name = Max Temperature
>> color = red
>> [[[outTemp_min]]]
>> name = Min Temperature
>> observation_type = outTemp
>> aggregate_type = min
>> zIndex = 2
>> [[[rainTotal]]]
>> name = Rain Total
>> type = column
>> yAxis = 1
>> zIndex = 0
>> color = "#268bd2"
>>
>>
>> To chart other years use something like this with the year_specific option
>>
>>
>> [[chart1]]
>> title = "Average Climatological Values for 2018"
>> time_length = year_specific
>> year_specific = 2018
>> xaxis_groupby = month
>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>> [[[outTemp]]]
>> zIndex = 2
>> name = Max Temperature
>> color = "#fc0404"
>> marker
>> enabled = true
>> radius = 4
>> [[[outTemp_min]]]
>> name = Min Temperature
>> observation_type = outTemp
>> aggregate_type = min
>> zIndex = 2
>> color = "#173c6a"
>> marker
>> enabled = true
>> radius = 4
>> [[[rainTotal]]]
>>     name = Rain Total
>> type = column
>> yAxis = 1
>> zIndex = 0
>> color = "#438bd6"
>>
>>
>>
>>
>>
>>
>> On Sunday, August 18, 2019 at 8:29:02 AM UTC-4, Ron Sell wrote:
>>>
>>> Awesome thank you so much.
>>>
>>> I am also attempting to add Average Climatological Valuesfor This Year.
>>> I’ll see if I can get that one going too.
>>>
>>> On Sun, Aug 18, 2019 at 8:25 AM Pat  wrote:
>>>
>>>> If you're looking at the lightning charts that I'm doing on my homepage 
>>>> <https://belchertownweather.com/go/belchertown>, add something like 
>>>> this to your homepage's graph group inside graphs.conf
>>>>
>>>> [[lightninggroupby]]
>>>> title = Lightning Strikes This Year
>>>> yAxisLabel = ""
>>>> time_length = year
>>>> xaxis_groupby = month
>>>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>>>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>>>
>>>>
>>>> [[[lightning_strikes]]]
>>>> name = Lightning Count
>>>> type = column
>>>> yAxisLabel = Lightning Count
>>>> [[[avg_distance]]]
>>>> name = Average Distance (mi)
>>>> type = column
>>>> aggregate_interval = 300 # 5 minutes
>>>> aggregate_type = avg
>>>> yAxis = 1
>>>> yAxisLabel = Average Distance (mile)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sunday, August 18, 2019 at 8:19:01 AM UTC-4, Ron Sell wrote:
>>>>>
>>>>> I got the lightening to work. How do I get it to run for the year on 
>>>>> the homepage?
>>>>> Thanks Ron 
>>>>>
>>>>> On Fri

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

[Pat]

Here's what I have for my climatological values chart on the homepage 
<https://belchertownweather.com/go/belchertown>:

[[avgclimatethisyear]]
title = "Average Climatological Values for This Year"
type = spline
time_length = year
aggregate_type = max
aggregate_interval = 86400 # 1 day
gapsize = 8640
xaxis_groupby = month
xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
[[[outTemp]]]
zIndex = 2
name = Max Temperature
color = red
[[[outTemp_min]]]
name = Min Temperature
observation_type = outTemp
aggregate_type = min
zIndex = 2
[[[rainTotal]]]
name = Rain Total
type = column
yAxis = 1
zIndex = 0
color = "#268bd2"


To chart other years use something like this with the year_specific option


[[chart1]]
title = "Average Climatological Values for 2018"
time_length = year_specific
year_specific = 2018
xaxis_groupby = month
xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
[[[outTemp]]]
zIndex = 2
name = Max Temperature
color = "#fc0404"
marker
enabled = true
radius = 4
[[[outTemp_min]]]
name = Min Temperature
observation_type = outTemp
aggregate_type = min
zIndex = 2
color = "#173c6a"
marker
enabled = true
radius = 4
[[[rainTotal]]]
name = Rain Total
type = column
yAxis = 1
zIndex = 0
color = "#438bd6"






On Sunday, August 18, 2019 at 8:29:02 AM UTC-4, Ron Sell wrote:
>
> Awesome thank you so much.
>
> I am also attempting to add Average Climatological Valuesfor This Year.
> I’ll see if I can get that one going too.
>
> On Sun, Aug 18, 2019 at 8:25 AM Pat > 
> wrote:
>
>> If you're looking at the lightning charts that I'm doing on my homepage 
>> <https://belchertownweather.com/go/belchertown>, add something like this 
>> to your homepage's graph group inside graphs.conf
>>
>> [[lightninggroupby]]
>> title = Lightning Strikes This Year
>> yAxisLabel = ""
>> time_length = year
>> xaxis_groupby = month
>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>
>>
>> [[[lightning_strikes]]]
>> name = Lightning Count
>> type = column
>> yAxisLabel = Lightning Count
>> [[[avg_distance]]]
>> name = Average Distance (mi)
>> type = column
>> aggregate_interval = 300 # 5 minutes
>> aggregate_type = avg
>> yAxis = 1
>> yAxisLabel = Average Distance (mile)
>>
>>
>>
>>
>>
>> On Sunday, August 18, 2019 at 8:19:01 AM UTC-4, Ron Sell wrote:
>>>
>>> I got the lightening to work. How do I get it to run for the year on the 
>>> homepage?
>>> Thanks Ron 
>>>
>>> On Fri, Aug 16, 2019, 6:31 PM rich T  wrote:
>>>
>>>> In the graphs.conf file add
>>>>
>>>> [homepage]
>>>>
>>>> .
>>>>
>>>> [[Lightning_chart]]
>>>> title = Lightning (Last 3 Hour)
>>>> time_length = 10800
>>>> aggregate_interval = 300
>>>> gapsize = 108000
>>>> type = column
>>>> 
>>>> [[[lightning_strikes]]]
>>>> name = Lightning Count
>>>> zIndex = 1
>>>> aggregate_type = sum
>>>>
>>>> Ensure the DB to contains the lightning fields, if not the db needs to 
>>>> extended. 
>>>> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>>>>
>>>> On Friday, August 16, 2019 at 3:15:20 PM UTC-4, Ron Sell wrote:
>>>>>
>>>>> Is there a way to show the lightning strikes? I was looking to add 
>>>>> chart. 
>>>>>
>>>>> thanks 
>>>>>
>>>>> On Saturday, 1 June 2019 12:57:56 UTC-4, Pat wrote:
>>>>>>
>>&g

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

[Pat]

If you're looking at the lightning charts that I'm doing on my homepage 
<https://belchertownweather.com/go/belchertown>, add something like this to 
your homepage's graph group inside graphs.conf

[[lightninggroupby]]
title = Lightning Strikes This Year
yAxisLabel = ""
time_length = year
xaxis_groupby = month
xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
'Aug', 'Sep', 'Oct', 'Nov', 'Dec'


[[[lightning_strikes]]]
name = Lightning Count
type = column
yAxisLabel = Lightning Count
[[[avg_distance]]]
name = Average Distance (mi)
type = column
aggregate_interval = 300 # 5 minutes
aggregate_type = avg
yAxis = 1
yAxisLabel = Average Distance (mile)





On Sunday, August 18, 2019 at 8:19:01 AM UTC-4, Ron Sell wrote:
>
> I got the lightening to work. How do I get it to run for the year on the 
> homepage?
> Thanks Ron 
>
> On Fri, Aug 16, 2019, 6:31 PM rich T > 
> wrote:
>
>> In the graphs.conf file add
>>
>> [homepage]
>>
>> .
>>
>> [[Lightning_chart]]
>> title = Lightning (Last 3 Hour)
>> time_length = 10800
>> aggregate_interval = 300
>> gapsize = 108000
>> type = column
>> 
>> [[[lightning_strikes]]]
>> name = Lightning Count
>> zIndex = 1
>> aggregate_type = sum
>>
>> Ensure the DB to contains the lightning fields, if not the db needs to 
>> extended. 
>> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>>
>> On Friday, August 16, 2019 at 3:15:20 PM UTC-4, Ron Sell wrote:
>>>
>>> Is there a way to show the lightning strikes? I was looking to add 
>>> chart. 
>>>
>>> thanks 
>>>
>>> On Saturday, 1 June 2019 12:57:56 UTC-4, 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 

[weewx-user] Re: Translate moon phases

[Pat]

They are in weewx.conf as well, which will need to be updated. 

On Sunday, August 18, 2019 at 6:31:25 AM UTC-4, Mikael Fredriksson wrote:
>
> Hi!
>
> Where can I translate the moon phase labels? I've tried to change them in 
> skin.conf, but it doesn't seem to work.
> I've been looking trough moon.py, almanac.py but nothing there.
>
>
>
> ###
>
> [Almanac]
> # The labels to be used for the phases of the moon:
> moon_phases = Nymåne, Tidig månskära, Första kvarteret, Tilltagande 
> måne, Fullmåne, Avtagande måne, Sista kvarteret, Sen månskära
> #moon_phases = New, Waxing crescent, First quarter, Waxing gibbous, 
> Full, Waning gibbous, Last quarter, Waning crescent
>
>
> ###
>
> This is the part from skin.conf. translated to swedish.
>
> Any advise would be appreciated :)
>
> /Micael
>

-- 
You received this message because you are subscribed to the Google 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/8ac12973-bdde-43dc-8b0f-af26cc096691%40googlegroups.com.

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

[Pat]

Database is locked is not a Belchertown skin problem. Did you open the 
database while weewx was running?

Belchertown is developed when I have spare time. Lately there hasn't been 
much of that. If you see room for improvement that you can fix, feel free 
to submit a Pull Request on the skin's GitHub 
<https://github.com/poblabs/weewx-belchertown> and help me out!


On Sunday, August 18, 2019 at 5:08:01 AM UTC-4, Kike .Asekas wrote:
>
> I have troubles with graphs with graphics with many queries for being 
> several years . Graphs like the image. The error is database is locked. 
> It would not be much of a problem but I use the sdr driver and weewx when 
> blocking the database it starts from the beginning and when load the driver 
> it gives an error because there is an instance of rtl_433 running and it is 
> not able to launch a new instance for not having killed the process 
> previous.
> Surely it is a driver error, which does not kill the process well before 
> leaving but the result is that it stops working.
>
> I think the skin should give an option in graphs.conf to configure when 
> the graphics are generated. Because weather graphs like the one attached 
> here is not necessary to launch them every round. Maybe just once a month 
> would be enough.
> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>
>> 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/e07cf532-3c97-45cf-81cb-1cffd5a21db4%40googlegroups.com.

[weewx-user] Re: Historic Image Generator Time Periods

[Pat]

Shameless plug for my website  running the 
Belchertown 
skin . It can chart any 
timespan you want with some specific ones built in 
.
 
There's a small learning curve to the graphs.conf but it comes with 4 
standard graphs, documentation and there's quite a few users on this forum 
who can help if you get stuck. 

For example, to chart yesterday 

 you 
would use:

time_length = days_ago
time_ago = 1


Last month would be

time_length = months_ago
time_ago = 1


A specific special day would be

time_length = day_specific
month_specific = 10
day_specific = 31
year_specific = 2017


A specific special month would be

time_length = month_specific
month_specific = 10
year_specific = 2017


and much more. The Belchertown Charts wiki 

 
has a lot of information, and users are often finding more capabilities 


Another key feature of Belchertown is the live updates with MQTT Websockets 
- but that's optional and not required to run the skin or the graphs. 



On Thursday, August 15, 2019 at 8:48:41 AM UTC-4, Copain wrote:
>
> Standard 4 image generator time periods are day, week, month and year.
>
> Does weewx offer functionality to generate graphs e.g. for yesterday, last 
> year or a specific historic month / year
> OR is it depending on the skin which would have to offer such feature?
>
> Basically, I am looking for an 'optional_ago' tag for graphs.
>
> Is there any experience / solution with historic graphs additional to the 
> 4 standard ones in bootstrap skin?
>
> Many thanks for your comments.
>
>

-- 
You received this message because you are subscribed to the Google 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/cc7ad570-1276-40b5-aa21-a95a3f7cfe78%40googlegroups.com.

Re: [weewx-user] examples of skins - enhancement to registration

[Pat]

Makes sense, thanks mwall. 

It looks like the showcase and the map have the same screenshot for my site 
(its from 2016)


On Wednesday, August 14, 2019 at 2:41:18 PM UTC-4, mwall wrote:
>
> On Wednesday, August 14, 2019 at 9:59:30 AM UTC-4, Pat wrote:
>>
>> I think the showcase and the map aren't refreshing screenshots correctly. 
>> My site shows a screenshot from 2016. I do think Tom and mwall were aware 
>> of that issue though. 
>>
>
> the showcase is not automatically update - those screenshots are from the 
> date/time we made them
>
> the map is automatically updated - if your screenshot on the map is older 
> than a month, please let me know.
>
> i guess that is another feature request for the registry: keep old images 
> so you can go back in time for any given site :)
>
> 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/8414867a-0693-49ba-914f-22d5192f8939%40googlegroups.com.

Re: [weewx-user] examples of skins - enhancement to registration

[Pat]

I think the showcase and the map aren't refreshing screenshots correctly. 
My site shows a screenshot from 2016. I do think Tom and mwall were aware 
of that issue though. 

On Wednesday, August 14, 2019 at 8:58:18 AM UTC-4, Andrew Milner wrote:
>
> Aha - that's interesting Tom - because the showcase has Hood River using 
> Standard - so in my dotage I was not even convinced Hood River was your 
> site!!!
>
>
>
> On Wednesday, 14 August 2019 14:00:04 UTC+3, Thomas Keffer wrote:
>>
>> Good suggestion, although it would be a bigger project than you might 
>> think: the database would have to be rebuilt to accommodate the extra data. 
>> It all takes time!
>>
>> My own site uses *Seasons *.
>>
>>
>>
>> On Tue, Aug 13, 2019 at 10:32 PM Andrew Milner  
>> wrote:
>>
>>> I have just been trying to find an example of Seasons skin in use - I 
>>> have used modified Bootstrap for many years and was considering a change.  
>>> Does anyone think it would be useful for the station registration to be 
>>> expanded to give a site URL and skin used in addition to hardware to make 
>>> it easier to locate examples of specific skins.  Belchertown appears to be 
>>> the only skin which is easy to identify!!  I am still trying to locate an 
>>> example of the new Seasons skin (well it's new to me) and I really did not 
>>> want to go through the palaver of enabling the skin in my happily running 
>>> site.
>>>
>>> -- 
>>> You received this message because you are 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/9090c733-5b14-4fe6-ad3a-2714f15462fa%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/98e8e79a-7e44-4211-bf42-2f50f4513105%40googlegroups.com.

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

[Pat]

This makes sense. The NOAA reports would start on day 1 of the month. The 
"time_length = month" also starts on day 1 of the month. 

If you use numbers for the time_length, that is the time backwards from 
right now. So that may go past day 1 of the month. 

On Wednesday, August 14, 2019 at 7:13:50 AM UTC-4, Kike .Asekas wrote:
>
> If time_lenght is month instead of 2592000 the results are correct. Perhaps 
> that is why in the year chart that has time_lenght = year they are also 
> correct. Maybe if it were 31536000 no, I haven't tried it.
>
> El miércoles, 14 de agosto de 2019, 12:09:22 (UTC+2), Kike .Asekas 
> escribió:
>>
>> Pat, I think there is an error in the month chart. The NOAA data does 
>> not match the chart. Neither the minims nor the maxims. 
>> You can see with the images that I send that the NOAA data does not match 
>> the graph.
>> The section of graph.conf
>> [month]
>> # Chart Timespan Defaults
>> title = "Este Mes"
>> show_button = true
>> button_text = "Mes"
>> type = spline
>> time_length = 2592000 # Last 30 days
>> tooltip_date_format = " LL"
>> aggregate_type = max
>> aggregate_interval = 86400 # 1 day
>> gapsize = 8640 # 1 day in milliseconds
>>
>> [[chart1]]
>> title = Temperatura
>> [[[outTemp]]]
>> zIndex = 1
>> name = Max Temperature
>> color = red
>> [[[outTemp_min]]]
>> name = Min Temperature
>> observation_type = outTemp
>> aggregate_type = min
>> color = "#7cb5ec"
>>
>>

-- 
You received this message because you are subscribed to the Google 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/9dc089eb-73da-4067-aeb6-dee0a90e3adb%40googlegroups.com.

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

[Pat]

Manfred this one was a little tricky and I'm not sure if my [xAxis], 
[yAxis] idea would have worked on this particular request, but anyways 
here's how to do it. Place this bit of code in the line you have red above. 

options.yAxis[this_yAxis].plotLines = [{
value: 1013,
color: '#FF',
width: 2,
}]


Change the color (right now it's red) and the width. 

You will also need to grab the latest development Belchertown dark CSS file 
<https://raw.githubusercontent.com/poblabs/weewx-belchertown/development/skins/Belchertown/belchertown-dark.min.css>
 
since I had to make some changes to it for the line to appear in dark mode. 
Note: backup your current dark CSS file just in case. 



On Monday, August 12, 2019 at 9:06:36 PM UTC-4, Pat wrote:
>
> Your problem might be that you're missing a semi-colon at the end of the 
> line. 
>
> But this raises a larger question/problem. With the re-write of the 
> Highcharts generator in 1.0, it seems more and more xAxis and yAxis 
> customizations are needed. Instead of me maintaining a mapping of every 
> option available, I had an idea today of adding an [xAxis] and [yAxis] 
> graphs.conf config section for each graph group. I'll work on testing 
> something out which might make your belchertown.js modification easier. 
>
>
> On Monday, August 12, 2019 at 4:54:29 PM UTC-4, Manfred Maier wrote:
>>
>> Hi Pat,
>> I'm trying to implement a horizontal 'plotLine' in the barometer graph 
>> (for indicating the normal pressure at 1013mbar).
>>
>> Unfortunately my attempts haven't been successful. What I've tried is to 
>> implement it in the 'Belchertown.js.tmpl':
>>
>>// Barometer chart plots get a higher precision yAxis tick
>>
>> if (s.obsType == "barometer") {
>>
>> if ( typeof s.yaxis_tickinterval === "undefined" ) {
>>
>> // If no tick interval override, set 0.01 as 
>> default tick interval to satisfy an old request for this level of precision.
>>
>> options.yAxis[this_yAxis].tickInterval = 0.01;
>>
>> }
>>
>> // Define yAxis label float format if rounding is 
>> defined. Default to 2 decimals if nothing defined
>>
>> if ( typeof s.rounding !== "undefined" ) {
>>
>> options.yAxis[this_yAxis].labels = { format: 
>> '{value:.'+s.rounding+'f}' }
>>
>> } else {
>>
>> options.yAxis[this_yAxis].labels = { format: 
>> '{value:.2f}' }
>>
>> }
>>
>> options.yAxis[this_yAxis].plotLine.value = 1013
>>
>> }
>>
>> Would you have a hint for me? It's not urgent :)
>>
>> Thanks!
>> Manfred 
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google 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/4e71f485-acfb-46a3-967e-35420d395358%40googlegroups.com.

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

[Pat]

Your problem might be that you're missing a semi-colon at the end of the 
line. 

But this raises a larger question/problem. With the re-write of the 
Highcharts generator in 1.0, it seems more and more xAxis and yAxis 
customizations are needed. Instead of me maintaining a mapping of every 
option available, I had an idea today of adding an [xAxis] and [yAxis] 
graphs.conf config section for each graph group. I'll work on testing 
something out which might make your belchertown.js modification easier. 


On Monday, August 12, 2019 at 4:54:29 PM UTC-4, Manfred Maier wrote:
>
> Hi Pat,
> I'm trying to implement a horizontal 'plotLine' in the barometer graph 
> (for indicating the normal pressure at 1013mbar).
>
> Unfortunately my attempts haven't been successful. What I've tried is to 
> implement it in the 'Belchertown.js.tmpl':
>
>// Barometer chart plots get a higher precision yAxis tick
>
> if (s.obsType == "barometer") {
>
> if ( typeof s.yaxis_tickinterval === "undefined" ) {
>
> // If no tick interval override, set 0.01 as 
> default tick interval to satisfy an old request for this level of precision.
>
> options.yAxis[this_yAxis].tickInterval = 0.01;
>
> }
>
> // Define yAxis label float format if rounding is 
> defined. Default to 2 decimals if nothing defined
>
> if ( typeof s.rounding !== "undefined" ) {
>
> options.yAxis[this_yAxis].labels = { format: 
> '{value:.'+s.rounding+'f}' }
>
> } else {
>
> options.yAxis[this_yAxis].labels = { format: 
> '{value:.2f}' }
>
> }
>
> options.yAxis[this_yAxis].plotLine.value = 1013
>
> }
>
> Would you have a hint for me? It's not urgent :)
>
> Thanks!
> Manfred 
>
>
>
>

-- 
You received this message because you are subscribed to the Google 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/893600f3-d5e4-41e2-ba96-3d44fa660cb5%40googlegroups.com.

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

[Pat]

Hi Manfred, I took this one right from the Season's skin, but modified it 
slightly to include the CSS color so it was inline. Give this a try (remove 
it from the table's tr's and td's if you're not using a table)

#if $day.txBatteryStatus.has_data

  
Transmitter Battery
  
#if $current.txBatteryStatus.raw == 0
OK
#else
LOW
#end if
  

#end if


On Sunday, August 11, 2019 at 9:44:24 AM UTC-4, Manfred Maier wrote:
>
> Thanks Pat! It works.
>
> Yet, my website coding skills are unfortunately not the best. 
> How does your code look like, where you translate the 
> $current.txBatteryStatus into a green 'OK' (on your about-page)?
> I've tried all different kinds of if-statements but none worked.
>
>
>
> Am Sonntag, 11. August 2019 04:16:34 UTC+2 schrieb Pat:
>>
>> Is your station or driver tracking the rxCheckPercent? (check your 
>> database to see if its populated). If so then try $current.rxCheckPercent 
>> for the text representation. 
>>
>> To graph it add this to your graphs.conf
>>
>> [about]
>> show_button = false
>> time_length = 172800 # 48 hours in seconds
>> aggregate_type = last
>> aggregate_interval = 300 # 5 min
>> gapsize = 30 # 5 min
>> 
>> [[rxchart]]
>> title = ISS Receive Stats
>> yaxis_max = 100
>> [[[rxCheckPercent]]]
>> color = "#268bd2"
>> 
>> [[rxchartyear]]
>> title = ISS Receive Stats Average
>> yaxis_max = 100
>> xaxis_groupby = month
>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>> time_length = year
>> [[[rxCheckPercent]]]
>> aggregate_type = avg
>> color = "#268bd2"
>>
>>
>>
>> Then at the top of your about.inc add this line which initializes 
>> Highcharts for the [about] graph group
>>
>> showChart("about");
>>
>>
>> Then inside your about.inc where you want the graph to actually appear 
>> add this:
>>
>> 
>> 
>>
>>
>> Basically the top of the about.inc will initialize the Highcharts [about] 
>> code, and the 's tell it where to put those charts. You can see that 
>> the  is the same name as the chart name inside the [about] graph 
>> group. 
>>
>> With this simple logic in mind, you can put any chart on any page you 
>> want. 
>>
>>
>> On Saturday, August 10, 2019 at 5:13:31 PM UTC-4, Manfred Maier wrote:
>>>
>>> Hi Pat,
>>> a quick question: 
>>> How do I get the Signal Quality / ISS Receive Stats onto the About page? 
>>> I've tried $station.rxCheckPercent, but that triggered an error.
>>>
>>> Is the about.inc of your page somewhere available?
>>>
>>> Thanks!
>>> Manfred. 
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google 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/102f61d4-b97d-420f-9976-4d4e8e5450d4%40googlegroups.com.

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

[Pat]

For the observation which you have specified yaxis = 1, you also should 
specify the yaxis_tickinterval 
<https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#yaxis_tickinterval>
 
if you want more ticks on the yaxis. 

On Sunday, August 11, 2019 at 11:52:33 AM UTC-4, Pepe wrote:
>
> Correction: In red what I meant
>
> *Hi*
>
> *I am triying to draw a climate graph but I want to put doble values in 
> the right than left . For example if I got 20 in the left must be 40 in the 
> right, that is to say, the rainfall scale must always be twice that of 
> temperature. Attached the graph I get with precipitation scale column 
> wrong.*
>
> *Any idea?*
>
>
>
>
> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>
>> 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/4ae62220-d2dd-45f1-9eeb-7f236e22e06a%40googlegroups.com.

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

[Pat]

Is your station or driver tracking the rxCheckPercent? (check your database 
to see if its populated). If so then try $current.rxCheckPercent for the 
text representation. 

To graph it add this to your graphs.conf

[about]
show_button = false
time_length = 172800 # 48 hours in seconds
aggregate_type = last
aggregate_interval = 300 # 5 min
gapsize = 30 # 5 min

[[rxchart]]
title = ISS Receive Stats
yaxis_max = 100
[[[rxCheckPercent]]]
color = "#268bd2"

[[rxchartyear]]
title = ISS Receive Stats Average
yaxis_max = 100
xaxis_groupby = month
xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
time_length = year
[[[rxCheckPercent]]]
aggregate_type = avg
color = "#268bd2"



Then at the top of your about.inc add this line which initializes 
Highcharts for the [about] graph group

showChart("about");


Then inside your about.inc where you want the graph to actually appear add 
this:





Basically the top of the about.inc will initialize the Highcharts [about] 
code, and the 's tell it where to put those charts. You can see that 
the  is the same name as the chart name inside the [about] graph 
group. 

With this simple logic in mind, you can put any chart on any page you want. 


On Saturday, August 10, 2019 at 5:13:31 PM UTC-4, Manfred Maier wrote:
>
> Hi Pat,
> a quick question: 
> How do I get the Signal Quality / ISS Receive Stats onto the About page? 
> I've tried $station.rxCheckPercent, but that triggered an error.
>
> Is the about.inc of your page somewhere available?
>
> Thanks!
> Manfred. 
>
>
>

-- 
You received this message because you are subscribed to the Google 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/a6462df1-2c7e-46ea-80c6-e6ee1e8e50bc%40googlegroups.com.

[weewx-user] Re: Minimum host system requirements - Arduino?

[Pat]

What would you consider full tilt? 

At it's basic functionality weewx will just write LOOP data to a SQLite 
database. You don't have to have it generate a website or any reports. 

You could have it write to a remote MySQL database, then run your website 
off that database which reduces the load on the weewx host. 

Or you could have weewx create as many websites/reports as you want and 
then FTP or SCP them to a remote destination.

In my opinion it all depends on what you're trying to achieve in order to 
determine full tilt. 


On Saturday, August 10, 2019 at 3:48:11 PM UTC-4, Jason Nerothin wrote:
>
> I’m trying to figure out if I could fit weewx into a smaller form factor 
> than Pi - something like a Particle.io board. 
>
> Could one of our RPi users post back some system stats when weewx is 
> running “full tilt”?

-- 
You received this message because you are subscribed to the Google 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/81d86294-1206-4f3b-aec1-8ca6e87e684f%40googlegroups.com.

[weewx-user] Re: Live Update don't work anymore

[Pat]

Try this. If this doesn't work please provide a link to your website

[[MQTT]]
server_url = mqtt://broker.hivemq.com:1883/
topic = wetter/ficht
unit_system = METRIC
binding = archive, loop
aggregation = aggregate
[[[inputs]]]
barometer
name = barometer_hPa
units = hPa


On Saturday, August 10, 2019 at 3:30:12 PM UTC-4, Dirk wrote:
>
> Hi,
> The live update of my Website worked the whole day, but now it has stopped 
> working, i changed nothing.
> When i use Mqtt.fx on my laptop i see the Data, but on the Website i got 
> an error.
>
> Chrome Console say
>
> 10. August 2019, 21:16:22: mqtt Connection Lost: AMQJS0005E Internal 
> error. Error Message: Cannot read property 'barometer' of undefined, Stack 
> trace: TypeError: Cannot read property 'barometer' of undefined
>
> I tried to change the units in weewx.conf mqtt but that don't work
>
> here the weewx.conf
>
> [[MQTT]]
> server_url = mqtt://broker.hivemq.com:1883/
> topic = wetter/ficht
> unit_system = METRIC
> binding = archive, loop
> aggregation = aggregate
> [[[inputs]]]
> barometer
> units = hPa
>
> anyone an idea
>
> Dirk 
>

-- 
You received this message because you are subscribed to the Google 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/98540847-6082-4b7a-bb70-073343c9ebb8%40googlegroups.com.