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

Found my mistake as I am still on skin version 1.0.1. So no worries... I am just getting started with the graphs.conf after installing a new weather station in my garden. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this

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

Hej Pat, I am facing an issue with the weather radials. I used the graphs.conf.example and renamed it to graphs.conf and finally inserted this snippet at the end: [weatherRadialGraphGroup] title = Temperature Range Radial show_button = true button_text = Weather Radial

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

Hi there. It should look like the first (1.JPG) graphic. The second does not represent the months, but the days (2.JPG). Am Dienstag, 24. März 2020 08:30:57 UTC+1 schrieb Gert Andersen: > > Hi > > Please explain what you think is wrong? > > Gert > > On Tuesday, March 24, 2020 at 7:30:31 AM

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

Are you running the development 1.1 beta version of the skin? You can download it here . Install it just like you did the first time then restart weewx. Also save your graphs.conf.example and move them to graphs.conf since

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

Hi Please explain what you think is wrong? Gert On Tuesday, March 24, 2020 at 7:30:31 AM UTC+1, Meteo Oberwallis wrote: > > > Hello Pat. > > Thank you very much. But now it looks like this to me. Why is that? > > Thanks for you Help! > > > Am Montag, 23. März 2020 17:58:24 UTC+1 schrieb Pat: >>

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

Place the code I've pasted to you beneath the Solarstrahlung chart you've created. [[avgclimatethisyear]] title = "Average Climatological Values for This Year" type = spline time_length = year aggregate_type = max aggregate_interval = 86400 # 1 day

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

You need to provide more information, such as the error, your skin.conf config for your homepage graph group, etc. More information the better. On Monday, March 23, 2020 at 4:46:29 AM UTC-4, Meteo Oberwallis wrote: > > Hi there. > Sorry for the stupid question. That would be under the "tab"

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

Hi there. Sorry for the stupid question. That would be under the "tab" homepage. If I use this now, then weewx gives an error message. [homepage] # Chart Timespan Defaults title = "Homepage" show_button = true button_text = "Homepage" time_length = today

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

Yes, place it under the section you have defined for highcharts_homepage_graphgroup On Sunday, March 22, 2020 at 1:36:18 PM UTC-4, Meteo Oberwallis wrote: > > Ok thanks. > > Can I install the current

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

Ok thanks. Can I install the current graphics on the Belchertown homepage? What code? I have to replace the [day]? Or how does it work? thanks Am Sonntag, 22. März 2020 18:15:19 UTC+1 schrieb Pat: > > This is exactly how I have it in my graphs.conf. Which is the same as the > wiki and the

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

This is exactly how I have it in my graphs.conf. Which is the same as the wiki and the example. [day] title = Today since Midnight show_button = true button_text = Today time_length = today gapsize = 30 [[avgclimatethisyear]] title = "Average Climatological

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

Hello It should appear that way Am Sonntag, 22. März 2020 18:08:26 UTC+1 schrieb p q: > > The problem with your graph isn't obvious to me. What's wrong with it? > > On Sun, Mar 22, 2020 at 9:57 AM Meteo Oberwallis > wrote: > >> Hello everybody. >> >> Can someone please help me with this

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

The problem with your graph isn't obvious to me. What's wrong with it? On Sun, Mar 22, 2020 at 9:57 AM Meteo Oberwallis wrote: > Hello everybody. > > Can someone please help me with this problem? Why is this graphic not > displayed correctly? > > Thanks for Help > > > > Am Dienstag, 17. März

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

Yes use the proper skin names. What errors are you getting on your RPi4 running WeeWX 4b with Belchertown skin 1.1b7/b8 using python 3? On Thursday, December 19, 2019 at 10:17:14 PM UTC-5, Xant wrote: > > Tom previously mentioned that Bskin may not be ready for W4 yet, but now >

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

Can you use the correct names for skins rather than your own abbreviations as it makes it appear that there is another skin available! On Friday, 20 December 2019 05:17:14 UTC+2, Xant wrote: > > > Tom previously mentioned that Bskin may not be ready for W4 yet, but now > clarified. > >

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

Tom previously mentioned that Bskin may not be ready for W4 yet, but now clarified. Will investigate further. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to

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

On Thursday, December 19, 2019 at 2:27:28 PM UTC-8, Xant wrote > > I'm not reporting errors (yet), but must assure the basics as this post > relates to Belchertown skin. > > 1) Does Bskin works with Weewx? > 2) Does Bskin works with Python 3? > > With this assurance, will then investigate

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

This post has thoroughly confused me since you are using Belchertown. 1) yes. I'm confused why this is being asked. 2) yes if you use the beta in the development branch. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this

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

Vince I'm not reporting errors (yet), but must assure the basics as this post relates to Belchertown skin. 1) Does Bskin works with Weewx? 2) Does Bskin works with Python 3? With this assurance, will then investigate further. X -- You received this message because you are subscribed to

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

Correct. Bskin = Belchertown skin -- You received this message because you are subscribed to the Google 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

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

I do not know what "Bskin" is. Belchertown? Something else? Yes, we would like to see the errors. Please include configuration information. In particular, what driver and any extensions you are using. -tk On Thu, Dec 19, 2019 at 11:33 AM Xant wrote: > >- RPi3 (base machine), WeeWX 3.9.2,

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

On Thursday, December 19, 2019 at 10:33:08 AM UTC-8, Xant wrote: > > >- RPi3 (base machine), WeeWX 3.9.2, Bskin 1.1b7, python 2 --> working >- RPi4 (test machine), WeeWX 4b, Bskin 1.1b7/b8, python 3 --> errors > > Should wait for WeeWX 4 and Python 3? > > Should post what errors you are

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

- RPi3 (base machine), WeeWX 3.9.2, Bskin 1.1b7, python 2 --> working - RPi4 (test machine), WeeWX 4b, Bskin 1.1b7/b8, python 3 --> errors Should wait for WeeWX 4 and Python 3? X -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To

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

If this is still a problem for you, then you need to add the name parameter. This will change the name in the MQTT payload and adjust the website values For example [[[inputs]]] windSpeed name = windSpeed_kmh On Thursday, November 28, 2019 at 3:09:10 PM UTC-5, Kike .Asekas wrote: >

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

Sorry. I didn't see your message. It was that. I change MQTT inputs and now the speed is in km/h althought it reports windSpeed_mps {"noise_dB": "-29.591", "cloudbase_meter": "134.366868777", "outHumidity": "96.0", "pressure_mbar": "1004.74", "maxSolarRad": "0.0", "barometer_mbar":

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

"Kike .Asekas" writes: > I use MQTT y I have configure it with METRICWX. > [[MQTT]] > server_url = mqtt://broker.hivemq.com:1883 > topic = estacion/datos > unit_system = METRICWX > binding = loop > ... > When I load the page goes well, but at the time of

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

Perfect - thanks. Gavin On Thu, Oct 10, 2019 at 8:44 PM Pat wrote: > Take a look at Common Titles config options > > from the skin options documentation >

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

Take a look at Common Titles config options from the skin options documentation . On Thursday, October 10, 2019 at 3:24:31 PM UTC-4,

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

Ok, thanks, you are right there is no data for January. Gavin On Tue, 1 Oct 2019, 20:33 Pat, wrote: > 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

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

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,

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

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

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

OK thanks anyway. On Thu, 19 Sep 2019 at 11:38, Pat wrote: > 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).

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

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

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

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,

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

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

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

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

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

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

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

Maybe in the readme put an example like: radar_html = " " 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

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

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,

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

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 with a section for the skin.conf options , can be updated adhoc. This is where

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

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

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

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

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

Thanks for that. Looking forward to the new version. On Thu., 5 Sep. 2019, 23:26 Pat, wrote: > 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 >

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

Cancel On Sat, 31 Aug 2019, 17:07 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:

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

how do I do a select from the database? I created a back up to run a select statement. I have sqlite running. im just not sure where to go from here. On 8/19/19, vince wrote: > On Monday, August 19, 2019 at 2:23:34 PM UTC-7, rich T wrote: >> >> Look in the "lightning_strikes" column of your

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

On Monday, August 19, 2019 at 2:23:34 PM UTC-7, rich T wrote: > > Look in the "lightning_strikes" column of your weewx dB, the strike data > contains a value something like "15.8906578" Try adding lightning_strikes > = %0f under [StringFormat] the Belchertown skin.conf to see if that >

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

Look in the "lightning_strikes" column of your weewx dB, the strike data contains a value something like "15.8906578" Try adding lightning_strikes = %0f under [StringFormat] the Belchertown skin.conf to see if that resolves the issue. I almost have the same issue, but with the 06045M and

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

here is the grapf.conf [[lightninggroupby]] title = Lightning Strikes This Year yAxisLabel = "" time_length = year xaxis_groupby = month xaxis_categories = 'Aug', 'Sep', 'Oct', 'Nov', 'Dec' [[[lightning_strikes]]] name = Lightning

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

On Monday, August 19, 2019 at 8:05:05 AM UTC-7, Ron Sell wrote: > > I am using these: > lightning_strikes = lightning_strike_count.AR-00015732.obs_air > avg_distance = lightning_strike_avg_distance.AR-00015732.obs_air > > > We need to see how you have the 'skin' configured.

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

I am using these: lightning_strikes = lightning_strike_count.AR-00015732.obs_air avg_distance = lightning_strike_avg_distance.AR-00015732.obs_air I am using the Belchertown weather skin. On Mon, Aug 19, 2019 at 10:50 AM vince wrote: > On Monday, August 19, 2019 at 4:26:41 AM

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

On Monday, August 19, 2019 at 4:26:41 AM UTC-7, Ron Sell wrote: > > Here is my weewx.conf file. > > Lightning Count is 16.20 > Average Distance is .032 > > > Ok, your sensor map looks like: [[sensor_map]] lightning_strikes = lightning_strike_count.AR-00015732.obs_air

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

Here is my weewx.conf file. Lightning Count is 16.20 Average Distance is .032 Thanks On Sun, Aug 18, 2019 at 6:47 PM vince wrote: > On Sunday, August 18, 2019 at 2:47:32 PM UTC-7, Ron Sell wrote: >> >> 15.4 is the strike count. Do you want the weewx.config ? >> >>> >>> > I think we'd

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

On Sunday, August 18, 2019 at 2:47:32 PM UTC-7, Ron Sell wrote: > > 15.4 is the strike count. Do you want the weewx.config ? > >> >> I think we'd probably need to see your weatherflow driver section from weewx.conf to understand what you're reporting. The WF station UDP interface reports

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

What detector are you using: 06045M or AS3935 module.? The 06045M seems to only display the counter number with a decimal point. Rolls back to "0" after "127". The AS3935 displays the information without any issues. . >> > -- You received this message because you are subscribed to the

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

What detector are you using: 06045M or AS3935 module.? The 06045M seems to only display the counter number with a decimal point. Rolls back to "0" after "127". The AS3935 displays the information without any issues. >> -- You received this message because you are subscribed to the Google

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

I am using Weather flow. I apologize for all the questions as I am new to all of this. On Sun, Aug 18, 2019 at 5:47 PM rich T wrote: > What detector are you using: 06045M or AS3935 module.? The 06045M seems > to only display the counter number with a decimal point. Rolls back to "0" > after

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

15.4 is the strike count. Do you want the weewx.config ? On Sun, Aug 18, 2019 at 4:57 PM Pat wrote: > 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,

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

What detector are you using: 06045M or AS3935 module.? The 06045M seems to only display the counter number with a decimal point. Rolls back to "0" after "127". The AS3935 displays the information without any issues. On Sunday, August 18, 2019 at 4:39:47 PM UTC-4, Ron Sell wrote: > got it

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

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

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

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

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

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

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

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 >

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

Here's what I have for my climatological values chart on the homepage : [[avgclimatethisyear]] title = "Average Climatological Values for This Year" type = spline time_length = year aggregate_type = max

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

Try this in the graph.conf [[Lightning_chart_yr]] title = Lightning (Year) time_length = year aggregate_type = max aggregate_interval = 86400 # 1 day gapsize = 8640 type = column [[[lightning_strikes]]] name = Lightning Count

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

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 >

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

If you're looking at the lightning charts that I'm doing on my homepage , add something like this to your homepage's graph group inside graphs.conf [[lightninggroupby]] title = Lightning Strikes This Year yAxisLabel = ""

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

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 >

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

Thank you On Fri, Aug 16, 2019 at 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 >

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

Great, now it works;) group_distance not present (weewx 3.9.1), i add group_distance = km in /etc/weewx/weewx.conf (probably it is ok in weewx 3.9.1.1?) ps, for show cloudbase, app temp and windrun i add show_apptemp = 1 show_windrun = 1 show_cloudbase = 1 AND (these i haven't read in your

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

Ok, if you are not using Websockets, then check what you have set for group_distance in weewx.conf. That's where windrun gets its units from. On Sunday, June 30, 2019 at 7:41:19 AM UTC-4, Maurizio Mezzetti wrote: > > thank you very much, i'm not use MQTT, for now, i have a as3935 in test >

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

thank you very much, i'm not use MQTT, for now, i have a as3935 in test over arduino, so probably i need mqtt ;) Il giorno dom 30 giu 2019 alle ore 13:31 Pat ha scritto: > Hi, > > 1) Are you using MQTT Websockets? If so, you may need to define the MQTT > extension to send windrun in km/hr. This

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

Thanks for the clarification. (and no, nothing different or special). On Thursday, June 27, 2019 at 9:49:18 AM UTC-4, Thomas Keffer wrote: > > Changes in skin.conf do not require a restart. It is read in with every > reporting cycle. > > Unless your custom reporting service is doing something

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

Changes in skin.conf do not require a restart. It is read in with every reporting cycle. Unless your custom reporting service is doing something different... On Thu, Jun 27, 2019 at 5:31 AM Pat wrote: > Yes at quick glance, that looks good. Any changes to skin.conf require a > weewx restart,

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

Great, thanks. Gavin On Wed, 26 Jun 2019, 17:55 Pat, wrote: > My site logo is actually the same logo for both light/dark. It has a > transparent background and a 2px white stroke around the outside of the > state and 2px white stroke at 75% opacity around the text. I found that > helps pop it

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

hi all it's good , I found, it is OK now for Average Wind = Vent moyen Patrick On Monday, June 17, 2019 at 8:45:04 PM UTC+2, Patrick Tranchant wrote: > > just a question PAT, I didn't find the translation for "Average Wind", in > which file ? > I don't remenber that I done for the old version.

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

just a question PAT, I didn't find the translation for "Average Wind", in which file ? I don't remenber that I done for the old version. Patrick On Monday, June 17, 2019 at 8:41:48 PM UTC+2, Patrick Tranchant wrote: > > hello Pat > I installed the 1.1b3 version of skin "Belchertown"; it's

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

hello Pat I installed the 1.1b3 version of skin "Belchertown"; it's works very good. good job Patrick On Monday, June 17, 2019 at 4:29:40 PM UTC+2, Pat wrote: > > You can add belchertownweather.com to your homescreen to get the full > experience. -- You received this message because you are

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

You can add belchertownweather.com to your homescreen to get the full experience. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to

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

Great skin with great charting options. Can someone post a snapshot of how the web app looks like when added to homescreen. My biggest concern is that I have to scroll up/down on mobile to even see the default graphs. In seasons skin, I dont need to do any scrolling to see the entire page. On

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

Great news :) On Sat, 15 Jun 2019, 08:08 Maarten van der Hoeven, wrote: > Back home, and now with full focus. All is working now! I have put > everything in weewx.conf, nothing left in skin.conf > > Very cool > > Op vrijdag 14 juni 2019 11:03:11 UTC+2 schreef Colin Larsen: >> >> I did a test on

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

Back home, and now with full focus. All is working now! I have put everything in weewx.conf, nothing left in skin.conf Very cool Op vrijdag 14 juni 2019 11:03:11 UTC+2 schreef Colin Larsen: > > I did a test on my system and that label definitely works :) > > On Fri, Jun 14, 2019 at 8:19 PM

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

I did a test on my system and that label definitely works :) On Fri, Jun 14, 2019 at 8:19 PM Colin Larsen wrote: > I think it would need a Weewx restart, again hopefully Pat can confirm I > have the right spot. > > On Fri, 14 Jun 2019, 20:17 Maarten van der Hoeven, > wrote: > >> Thanks again

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

I think it would need a Weewx restart, again hopefully Pat can confirm I have the right spot. On Fri, 14 Jun 2019, 20:17 Maarten van der Hoeven, wrote: > Thanks again Colin! I did a quick change, but didnt see the label being > changed at the website. Must have been doing something wrong, as

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

Thanks again Colin! I did a quick change, but didnt see the label being changed at the website. Must have been doing something wrong, as being in a hurry, work is calling. Will check this evening, and will also read the wiki... As I understand correctly, there's pretty much howto's written down

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

Probably just extraTemp1 = Grass Temperature or whatever you need On Fri, Jun 14, 2019 at 7:33 PM Colin Larsen wrote: > This is it I think, add your desired label in here > > [Labels] > # Labels used in this skin > [[Generic]] > # Generic labels, keyed by an observation type. > # To change a

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

This is it I think, add your desired label in here [Labels] # Labels used in this skin [[Generic]] # Generic labels, keyed by an observation type. # To change a label or translate it to your language # change the text after the equal sign. # Extra Observation labels appTemp = Apparent Temperature

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

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

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

How cool is that! This is all too easy  Adding “extraTemp1” at the end of the mentioned line (in skin.conf) did already the trick. Barometer 1014.2 mbar Dew Point 13.8 °C Humidity 88% Rain 0.0 mm 0.0 mm/hr Temperature116.1 °C

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

Sorry, that formatted horribly I think - it's actually just on 2 lines of code On Fri, Jun 14, 2019 at 6:59 PM Colin Larsen wrote: > Maarten > > I think you may be able to add your extraTemp1 into this section below in > skin.conf/weewx.conf (depending on where you have the [Extras] stanza). >

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

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

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

If you are on 1.0, then you can upgrade to 1.0.1+ easily. The special instructions were only for 0.9.1 and older. On Tuesday, June 11, 2019 at 9:59:57 AM UTC-4, Adnan Mumtaz wrote: > > Hi Pat, > > I am at v1.0, in order to upgrade to 1.0.1 will i have to remove it > completely and re-install

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

Hi Pat, I am at v1.0, in order to upgrade to 1.0.1 will i have to remove it completely and re-install like I did for 1.0? Thanks Adnan On Sunday, 9 June 2019 21:48:54 UTC+3, Pat wrote: > > All, version 1.0.1 has been released. This is a bug fix and maintenance > update. > > You can download

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

Yes you can either download the tar.gz and copy the files into place, or run the wee_extension install. Just have a backup of your skin.conf since new version has new things added to it. On Monday, June 10, 2019 at 2:06:33 AM UTC-4, Johannes Ebner wrote: > > Hi, > > If I have already the dev

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

Hi, If I have already the dev code running, can I do a normal upgrade? Belchertown 1.0rc8.1 Br, Johannes Am Sonntag, 9. Juni 2019 20:48:54 UTC+2 schrieb Pat: > > All, version 1.0.1 has been released. This is a bug fix and maintenance > update. > > You can download 1.0.1 here: >

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

All, version 1.0.1 has been released. This is a bug fix and maintenance update. You can download 1.0.1 here: https://github.com/poblabs/weewx-belchertown/releases Work on 1.1 has already begun! -- You received this message because you are subscribed to the Google Groups "weewx-user"

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

That was it. Thanks Pat! Love the skin. On Sun, Jun 9, 2019 at 10:55 AM Pat O'Brien wrote: > Yes, your archive interval isn't 300 which is the default gapsize for the > charts.. > > So you will need to change the gapsize setting in the graphs.conf.example > (or graphs.conf) to match your

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

Yes, your archive interval isn't 300 which is the default gapsize for the charts.. So you will need to change the gapsize setting in the graphs.conf.example (or graphs.conf) to match your weewx.conf archive_interval in milliseconds. Sent from mobile On Sun, Jun 9, 2019, 11:52 AM Chris P

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

Yes very warm :/ in the coming weeks we can grill burgers on our cars :) Isn't it like Arizona? On Saturday, 8 June 2019 08:50:08 UTC+3, Colin Larsen wrote: > > Happy to help - it's pretty warm there! > > On Sat, 8 Jun 2019, 17:32 Adnan Mumtaz, > > wrote: > >> Thanks a lot Colin, it worked. >>

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

Happy to help - it's pretty warm there! On Sat, 8 Jun 2019, 17:32 Adnan Mumtaz, wrote: > Thanks a lot Colin, it worked. > > On Saturday, 8 June 2019 08:08:12 UTC+3, Colin Larsen wrote: >> >> Adnan, look for a line in your skin.conf/weewx.conf (depending on where >> you have things specified)

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

Thanks a lot Colin, it worked. On Saturday, 8 June 2019 08:08:12 UTC+3, Colin Larsen wrote: > > Adnan, look for a line in your skin.conf/weewx.conf (depending on where > you have things specified) like this one. Add observations in the order > that you like to see them > > station_observations

  1   2   >