I have applied an offset for the windspeeds on my station (adjusted for height using the Met Office calculation) but Fresh WDL seems to be using the original speed not the adjusted speed, what can I do to force FreshWDL to use the adjusted speeds?
In WD. However, I think I have solved the mystery. What caused me to doubt my readings was a quick glance at the Met Office page for my location that was showing windspeeds way above what I’m getting. It would appear that their website, whilst stating that windspeeds are in mph are actually showing windspeeds in kmh!! When you calculate what they’re displaying in mph it’s similar to mine (I’ve also been able to double check this with the weather station at the local airport so it’s definitely them not me lol).
Hey, to add another temperature sensor, do the following:
FreshWDLmaster.html changes:
On line 7: Change stylesheet01.css to stylesheet02.css
On line 16: Change InnerContent.js to InnerContent-02.js
Config.js changes:
Change the gaugeSettings field so it matches the following:
gaugeSettings = { //Gauges: apparent temperature barometer windChill graphHandlerBarometer graphHandlerRainfall graphHandlerTemperature graphHandlerWindSpeed humidity moonSun solar status rainfallTitle rainfallDay rainfallMonth rainfallYear UV windDirection windSpeed
solar: {
enabled: false
},
UV: {
enabled: false
},
windChill: {
mode: “windchill”, //The default mode, either “heatIndex” or “windchill” (note: lowercase c)
autoSwitch: true //If true, will switch between heat index/wind chill depending on what is appropriate.
},
temperature: {
title: " default "
},
temperature02: {
enabled: true,
title: “default”,
input: 2
},
temperature03: {
enabled: true,
title: “default”,
input: 3
}
};
You can change the title of each of the temperature sensors by adjusting the title field. So, for example, if you wanted to change the title of one of them to be Other Temperature, you
Currently that is going to be a bit of an issue. It might seem strange, but it’s actually quite a pain to move the gauges around. So even though there’s an obvious spot to put the UV, it’s no small job to get it there :lol:
I’ll add it to the todo list, but it will probably be a couple months before I have time to adjust it (apologies, life is very busy for me at the moment!)
Unfortunately for the time being you may have to chose between the extra temperatures and UV
thank you so much!
using your changes second temperature shows +255 max and 100 min
Changing “input 2” to “input 1” in config.js:
temperature02: {
enabled: true,
title: “Secondo Sensore”,
input: 1
},
in fact, in globals.js it refers to “input 1”:
//Widget Config / Settings
var widgetList = {
apparent: {enabled: true},
temperature: {enabled: true, title: “default”, highLowEnabled: true},
temperature02: {enabled: true, title: “default”, highLowEnabled: true, input: 1}, //input: extra sensor 1
temperature03: {enabled: true, title: “default”, highLowEnabled: true, input: 2}, //input: extra sensor 1
All time you need, Yerren!!
It’s a great job anyway.
If i can I would just suggest you to change, in the future, wind speed and gust bars with a round widget (as in old wdl, to understand); or try to put words “wind” and “gust” outside bars.
Thank you Yerrin your a gentleman and a scholar…just one small issue, the min - max for the indoor is showing between 0 and 1 …have i done something else wrong.
And also, are you aware the rain gauges changed, now it is the yearly rainfall gauge that is first rather than the daily rainfall gauge i.e they changed order from daily, monthly, yearly to yearly monthly, daily
From memory, the indoor temperature doesn’t have high/low data records for whatever reason.
To deal with this, you can disable them for that gauge, by using: highLowEnabled: false. So your whole config for that gauge looks something like:
Hi again Yerren. Again thank you for your prompt response.
The indoor temp does have a high low as it is enabled on my old WDL and is still working. In the interim, i will disable the high low but someday if you do get to look at it that would be much appreciated.
Thanks for that! I must have missed it, as it is called inTemp in the parser I’m using, as opposed to indoor temp.
I’ll let you know when I’ve fixed that up, but it’ll be a little while, assignments galore for the next two weeks!