I think I'll let the solution 'mature' a little before considering including it in the base release - when all the required tags are supported for instance.
The wind rose data and dominant direction is for today (since local midnight), if you want it from 9am, let me know.Stu,
BTW, the request for UTC.... The format they expect in the file is yyyy,m,d,h,m,sStu,
I have attached the template JSON file that I have been using with the gauges to this posting.I have put this into the zip now, thanks.
Mark,Thanks Col. Amazingly I had caught all of those changes, though I have restructured the code a little here and there. I'll ignore the 'style' changes ;)
I have attached a file showing the differences between your version 2.1.1 and the one with my modifications. Please let me know if you have any questions regarding the changes I made.
Col.
Hi Mark, Col.Yep, I can put that in. Will the version string be exactly "1.1.4"? I'll have to spit it and handle as numerics in order to do a >= for future versions.
We're going to need people are running version 1.1.4 of WeatherCat to work correctly with the gauges - I'm estimating this will be publicly released in the next two weeks. Would it be possible to have the script pick up the WeatherCat version and show an error message if it's less than 1.1.4?
VM.mm, Build X
where'M' is the major version and 'mm' is the minor. 'X' is an integer which is incremented every time it's built. data.tempunit.replace('°', '?');to which I added the line
data.tempunit.replace('°', '?');to cater for WeatherCat
data.tempunit = data.tempunit.replace('°', '?');Hence why those couple of lines are different in yours and my script.
Mark,That is one of the bits I have changed, the existing code was never called because the gauges ended up requiring a later build of Cumulus than the one that included the degree symbol in the unit string anyway.
There was one odd thing in the gauges.js file that just would not work for me....
In your original script you hadQuotedata.tempunit.replace('°', '?');to which I added the lineQuotedata.tempunit.replace('°', '?');to cater for WeatherCat
But it just flat out refused to replace the °
In the end, the only way I could get it to work was to use the lineQuotedata.tempunit = data.tempunit.replace('°', '?');Hence why those couple of lines are different in yours and my script.
Col.
Aside this one it would be cool if someone can explain which files should point to which data - thanks in advance to all SteelSeries workers!
Cheers, Reinhard
By the way: what do you mean with Line 20 to 10? Line 20 wants to know the path to my "old" gauges page, but I have never had an old gauges page?
No success here on my side: I always get the reminder that the SteelSeries requires WeatherCat V 1.14 or later. No that I am using the german language settings my WeatherCat shows V 1,14 ... the point/comma issue returns. :'( Maybe there is a chance to tell the gauges.js that it should accept 1.14 and 1,14.Bah! I hadn't realised that the version string was locale specific - normally it is set in the program itself.
Aside this one it would be cool if someone can explain which files should point to which data - thanks in advance to all SteelSeries workers!
Cheers,
Reinhard
can't get it all to work see the attached this is all I get please help if possible
Hi ColRandall,
Thanks for the help here is the http://weatheronthehill.6te.net/gauges-ss/gauges-ss-basic.htm (http://weatheronthehill.6te.net/gauges-ss/gauges-ss-basic.htm)
I have tried both of your options and get about the same thing
thanks
[cheers1]
Hi Col,Actually that is a good point. You could leave the file where it is in the folder structure or you could move it to a location that makes more sense to you. I will change the Wiki page to reflect your suggestion.
maybe it should be better explained that before "Open WeatherCat Preferences --> Online --> Custom Web --> Additional Files" someone should make a copy of "realtimegaugesWC.txt" and store it somewhere where it can be found easily. Because this is the only file that is needed on the local computer to be processed - all other files within the "steels folder" are ftp'd to the server and not needed on the local computer any more. For me I did store it in the Custom Web folder.
Just a thought.
Cheers,
Reinhard
Now if I can just figure out how Reinhard got that great looking background !
body {
font-family: Verdana, Helvetica, sans-serif;
font-size: 10pt;
text-align: left;
background-image: url(/regenmetal.jpg);
}
I added the 4th line, and pointed the css to the place where the desired background pattern is stored on your web directory.Now if I can just figure out how Reinhard got that great looking background !
Hello David,
for adding an individual background image you have to edit the code in the gauges-ss.css:Code: [Select]body {
I added the 4th line, and pointed the css to the place where the desired background pattern is stored on your web directory.
font-family: Verdana, Helvetica, sans-serif;
font-size: 10pt;
text-align: left;
background-image: url(/regenmetal.jpg);
}
Cheers,
Reinhard
realTimeURL_WC : '/subdirectory/gauges-ss/realtimegaugesWC.txt', //*** WeatherCat Users: Change to your location of the JSON script generator ***
which specifies the wrong place for the realtimegaugesWC.txt file. It should read realTimeURL_WC : '/gauges-ss/realtimegaugesWC.txt', //*** WeatherCat Users: Change to your location of the JSON script generator ***
and then should work properly as the data is in http://weatheronthehill.6te.net/gauges-ss/realtimegaugesWC.txt realTimeURL_WC : './realtimegaugesWC.txt', //*** WeatherCat Users: Change to your location of the JSON script generator ***
as the spec, since the page itself is coming from the same directory (./gauges-ss/) as the realtimegaugesWC.txt file.realTimeURL_WC : '/realtimegaugesWC.txt',
Only one minor problem I've got, don't know if anybody else has seen this at all.
All the gauges except the wind rose update regularly and are accurate with the 'Cat. However the wind rose does not seem to update and the total wind run counter under reads.
Hi David and Jace
I notice if you set the wind to m/s instead of mph it matches WeatherCat
Wind Run and Speed
[cheers1]
To help diagnose the wind speed discrepancies I think we will need a screen shot of the gauge, and a copy of your realtimegaugesWC.txt file taken at the same time. Then we can see what data is being sent, and what is being done with it.
Thanks Mark
Col,
I do see that you have changed the background color of the gauges themselves to a background image - can you tell me how to? I want to change the background to the pattern attached in this post.
Cheers,
Reinhard
background : steelseries.BackgroundColor.BEIGE,
was changed tobackground : steelseries.BackgroundColor.BRUSHED_METAL,
You can yes, either you can overlay an image on top of the gauge background (this obviously works best with images that have transparency), or you can remove the gauge background completely and have whatever is behind the gauge on the web page show through.
I believe you can incorporate an image as a background on the gauges, however, I haven't explored that yet. Maybe Mark can give you an idea.
Yep, that looks to be behaving itself now.
I'd just like confirmation of all the unit strings WeatherCat can send for wind unit, pressure unit and rain unit if someone can provide this info?
How would I be able to alter the gauge size if I wanted to ?It is set by CSS, in gauges-ss.css, there is a class called .gaugeSizeStd, alter the width/height values in there to globally change the size.
To help diagnose the wind speed discrepancies I think we will need a screen shot of the gauge, and a copy of your realtimegaugesWC.txt file taken at the same time. Then we can see what data is being sent, and what is being done with it.Thanks Mark,
Thanks
Mark
data.windunit = data.windunit.toLowerCase();
if (data.windunit === 'kmh') { // WD wind unit omits '/'
Yep, that looks to be behaving itself now.
I'd just like confirmation of all the unit strings WeatherCat can send for wind unit, pressure unit and rain unit if someone can provide this info?
Precipitation: mm or in
Temperature: ?C or ?F
Windpseed: MPH, Knots, m/s, km/h
Pressure: inHg, mb, hPa
Hi Mark,Thanks for that, I will have to convert the "MPH" to "mph" and "Knots" to "kts" internally in script to make WeatherCat compatible with the existing logic.
Here are the strings:Code: [Select]Precipitation: mm or in
Temperature: ?C or ?F
Windpseed: MPH, Knots, m/s, km/h
Pressure: inHg, mb, hPa
If you need more info just shout.
Cheers,
Stu.
Thanks for advice, Mark - really appreciated![bounce] That is looking great - I used to have a very similar background myself on my gauges page some time ago, it disappeared for some reason!
Took it - that's it! http://wetter.unterwurzacher.at/steelgauges/gauges-ss-basic.htm
Thanks to all involved in this one!
Cheers,
Reinhard
[bounce] That is looking great - I used to have a very similar background myself on my gauges page some time ago, it disappeared for some reason!
I have attached a test version of v2.2.2 with just those two changes in if people would give it a whirl - including someone who uses Knots as their native wind speed unit would be good :)
Note that you left WeatherCat as the default application in the new file, which I assume you'd want as Cumulus in the final release.It was deliberate, just for WC users ;), but thanks for pointing it out.
Thanks for the update, Mark.
Attached a screenshot: I cannot arrive any of your pages... ???
Forbidden
You don't have permission to access /a/SteelSeries_FAQ on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
OK, fixed a problem with the .htaccess file, please try it again. If it still fails can you tell me the two or octets of your IP address please?
Could anyone have a look at http://spilderdalen.com , and give me some feedback what i need to implement this.
Hi Mark,Sorry, I thought I'd answered this (I think the same question may have been asked elsewhere).
thanks for the update and your hard work to provide us WeatherCat users with your impressive gauges. Update was no problem. One thing I noticed is that the counter (I set it to reload every 30 sec) is showing a 10 very short after going to zero, but then counts down from 29 again. It is only cosmetically, maybe I am missing a setting somewhere? Attached a movie that shows the behavior.
Cheers,
Reinhard
imgPathURL : './',
should readimgPathURL : '/',
without the dot.realTimeURL_WC : 'realtimegaugesWC.txt',
should readrealTimeURL_WC : '/realtimegaugesWC.txt',
All the files for the gauges are or will be in the top level (root) of the website (option 1)
After following these setup instructions, you should be able to access the gauges by going to http://www.yourpage.com/gauges-ss-basic.htm
Once you have downloaded the zip file from http://wiki.sandaysoft.com/a/SteelSeries_Gauges, extract all the files from the zip file (retaining the folder structure)
You should now have created a folder called gauges-ss-vX-X-X (where X-X-X represents the version of SS-Gauges)
my site is: http://spilderdalen.com
Any tip for me?
counter : 60, //download data counter (secs, default 60)
...better your friend should switch to WeatherCat...
got it: The searched tag is CPS$
2.3.2
* Only WeatherCat users need to update from v2.3.1
* Updated gauges.js
- Fixed handling of current theoretical solar radiation in doSolar() for WC users
- Made realtimegauges JSON file weather program dependent so updates to the JSON file for one program can
be made idenpendently of the others
* Updated realtimegaugesWC.txt
- Added tag value for CurrentSolarMax to replace "N/A"
- Version uplifted to 11
...can you check it out for errors, if it is OK it will become the official release...Adjusted all changes to fit optical with my weather site: It works as expected, give it a go!
I really need to recruit a WC beta tester or two for the next release.
Sorry, I hadn't realised WC v1.20 was a dev release - hopefully it will be production before too long.
2.4.0
* Updated gauges.js
- Added global gauge option fullScaleDeflectionTime to control pointer 'speed'
- Changed the UV gauge to use new gradient scale colours by default
- Added Today's High value to the UV gauge
- Changed rain gauge to always use blue LEDs - line 653
- Fixed the 0.5" rain gauge code introduced in version 2.3.1
- Applied fix for VWS not supplying the correct value for max rain rate today
* Updated the realtime JSON files to include today's high UV value
- Cumulus - realtimegaugesT.txt - v11
- Weather Display - customeclientrawlocal.txt - v10
- Weather Cat - realtimegaugesWC.txt - v12
- Meteobridge - see Ken True's web site for updated script - v10
press: "1,017.1"
pressH: "1,036.0"
pressL: "994.8"
pressTH: "1,017.1"
pressTL: "1,008.1"
presstrendval: "0.7"
pressunit: "hPa"
Some bugs and lot's of work to go, but I got it up and running.The link to your site isn't working for me this morning.
mac.technomonkeys.com/Weather (http://mac.technomonkeys.com/Weather)
Critique and suggestions always considered.
As I originally wrote the gauges for Cumulus which does not keep hi/lo data for the indoor humidity there is code in there to disable the sector when indoor humidity is displayed, if WC has this data then you will need to add it to the Jason data file, and undo the code in doHum() that suppresses the sector.
I'm on a tablet at the mo so cannot look at the code to suggest what you do, if you cannot figure it out I'll take a look tomorrow.
doHum = function (radio) {
//if rad isn't specified, just use existing value
var sel = (radio === undefined ? _hum.selected : radio.value),
popupImg, tip;
if (sel === 'out') {
_hum.value = extractDecimal(data.hum);
_hum.areas = [steelseries.Section(+extractDecimal(data.humTL), +extractDecimal(data.humTH), gauge.minMaxArea)];
_hum.title = strings.hum_title_out;
popupImg = 0;
} else {
_hum.value = extractDecimal(data.inhum);
if (data.inhumTL && data.inhumTH) {
_hum.areas = [steelseries.Section(+extractDecimal(data.inhumTL), +extractDecimal(data.inhumTH), gauge.minMaxArea)];
} else {
_hum.areas = [];
}
_hum.title = strings.hum_title_in;
popupImg = 1;
}
if (_hum.selected !== sel) {
_hum.selected = sel;
//Change gauge title
_gaugeHum.setTitleString(_hum.title);
if (config.showPopupGraphs) {
$('#imgtip4_img').attr('src', config.imgPathURL + config.tipImgs[4][popupImg] + _cacheDefeat);
}
}
_gaugeHum.setArea(_hum.areas);
_gaugeHum.setValueAnimated(_hum.value);
if (ddimgtooltip.showTips) {
//update tooltip
if (_hum.selected === 'out') {
tip = strings.hum_out_info + ':' +
'<br>' +
'- ' + strings.minimum_info + ': ' + extractDecimal(data.humTL) + '% ' + strings.at + ' ' + data.ThumTL +
' | ' + strings.maximum_info + ': ' + extractDecimal(data.humTH) + '% ' + strings.at + ' ' + data.ThumTH;
} else if (data.inhumTL && data.inhumTH) {
// we have indoor high/low data
tip = strings.hum_in_info + ':' +
'<br>' +
'- ' + strings.minimum_info + ': ' + extractDecimal(data.inhumTL) + '% ' + strings.at + ' ' + data.TinhumTL +
' | ' + strings.maximum_info + ': ' + extractDecimal(data.inhumTH) + '% ' + strings.at + ' ' + data.TinhumTH;
} else {
// no indoor high/low data
tip = strings.hum_in_info + ': ' + extractDecimal(data.inhum) + '%';
}
$('#imgtip4_txt').html(tip);
if (_refreshGraphs && config.showPopupGraphs && config.tipImgs[4][0] !== null) {
$('#imgtip4_img').attr('src', config.imgPathURL + config.tipImgs[4][popupImg] + _cacheDefeat);
}
}
},
No problem, I have added this as a standard feature for the next release (for those programs that supply the data).
For now, I have my DDNS porting to 984.
Thank you very much, Blick. Looks good!
v2.5.4 with support for the WC cloudbase tags is now available from GitHub.
Reinhard, did you just copy over the files into your existing structure or did you replace the whole thing and redo your customisations?
"forecast":"Current forecast is -- CF$ --",
"forecast":"de$ -- forecast is -- CF$ --",
You can put whatever tags you want into the ticker, just add them to the forecast entry fromCode: [Select]"forecast":"Current forecast is -- CF$ --",
to sayCode: [Select]"forecast":"de$ -- forecast is -- CF$ --",
OK, that one is fairly easy, windrose.js has been replaced with RGraph.rose.js (actually the supplied demo pages use the minimised version RGraph.rose.min.js).
In previous versions of the SteelSeries Gauges, there was a windrose.js file where one could change the colour of the windrose gradient. In the 2.5x releases this file is no longer part of the setup. I looked at your FAQ and it still refers to the windrose.js file. Where is the setting for wind rose plot colours?
'chart.colors': ['rgba(255,0,0,0.5)', 'rgba(255,255,0,0.5)', 'rgba(0,255,255,0.5)', 'rgb(0,255,0)', 'gray', 'blue', 'rgb(255,128,255)','green', 'pink', 'gray', 'aqua'],
rose.Set('chart.colors', ['Gradient(#408040:red:#7070A0)']);
So that sets the min. value colur to to 0x408040 (darkish green), mid point red (0xff0000), and max. value 0x7070A0 (darkish purple)Terrific. Thanks for the explanation.The rainfall rate and rainfall total 'stepped' colours (not enabled by default) are defined in createRainRateSections (line 3089) and createRainfallSections (line 3112).
Is there a similar override for the gradient colours used in the rainfall gauge? I notice that gauge starts in green and goes to yellow, but there does not appear to be a third colour in the gradient. I have searched through the gauges.js file but am a wee bit confused about the rainfall gauge gradient colour controls.
The rainfall rate and rainfall total 'stepped' colours (not enabled by default) are defined in createRainRateSections (line 3089) and createRainfallSections (line 3112).
The continuous gradient colours for rainfall are defined in createRainfallGradient (line 3143), the full range of colours will be displayed from 0 - 100 mm, or 0 - 4 inches. You may want to 'tweak' those values.
I'm new to WeatherCat and bringing the data to the web and ran
into some difficulties with the realtimegaugesWC.txt file.
Does WC not FTP those files to the webserver as long as the external sensors are offline?I hate to argue with the Dev, but I think WC was creating and uploading exactly what you gave it from the missing data; nothing! Fortunately, WC is a very 'smart' app and it saved some bits by compressing the non-existant data into only a single "mirco" bit and sent it via the same parcel service that only delivers on odd number days to even numbered addresses. I tell you, I doubt you came across a better bit builded than Stu! [cheer]
I hate to argue with the Dev,
but I think WC was creating and uploading exactly what you gave it
from the missing data; nothing!
Fortunately, WC is a very 'smart' app and it saved some bits by
compressing the non-existant data into only a single "mirco" bit
and sent it via the same parcel service that only delivers on odd
number days to even numbered addresses.
I tell you, I doubt you came across a better bit builded than Stu!
Hi Mark,
how about to add an additional temp sensor to the Temp-gauge?
*out*
*in*
*additional* (if turned on, user can give it a unique name in the script)
Possible?
Cheers,
Reinhard
Hi Mark,
how about to add an additional temp sensor to the Temp-gauge?
*out*
*in*
*additional* (if turned on, user can give it a unique name in the script)
Possible?
Cheers,
Reinhard
Hi Reinhard
Sorry I've not visited the forum for a while - been busy at work and enjoying my new motor - so, to answer the question, yes anything is possible, it just depends how much effort you want to put in.
It's not something I want to add to the standard scripts, but I can give you some help and guidance if you want to add to your site?
Cheers
Mark
I can't find a tag in WeatherCat for Aux Temperature 1.
STAT$T1:CURRENT:TODAY$
It is only possible to show the actual temp, no min or max (if I see this correct, Mark?).Yes, unless you are prepared to hack a bit of code and add the additional data into the data file.
Stylesheet http://timberlakesutah.com/weather-gauges-explained/# wurde nicht geladen, weil sein MIME-Typ, "text/html", nicht "text/css" ist.
Means: Stylesheet xxx can't be loaded because the MIME-Type is text/html instead of text/css. ['customgraph7.jpg', 'customgraph8.jpg'] // Temperature: outdoor, indoor
should be ['customgraph7.jpg', 'customgraph8.jpg'], // Temperature: outdoor, indoor
<link rel="stylesheet" id="style_selector_ss" href="#" />
realTimeURL_WC : './realtimegaugesWC.txt', //*** WeatherCat Users: Change to your location of the JSON script generator ***
to realTimeURL_WC : '../../realtimegaugesWC.txt', //*** WeatherCat Users: Change to your location of the JSON script generator ***
which will navigate two directories up to the document root where the file is, OR to realTimeURL_WC : '/realtimegaugesWC.txt', //*** WeatherCat Users: Change to your location of the JSON script generator ***
(which will access it from the document root of schwab1.com)Thanks to Blick & Ken as the issue was indeed fixed changing gauges.js LINE 65To be precise, the '../../realtimegaugestWC.txt' addressing just allowed a page in steel/web_server/ to access the file two directories up .. no files were 'moved'.. just addressed correctly based on their current location in the website's document tree.
from './realtimegaugesWC.txt'
to '../../realtimegaugesWC.txt'
which moved realtimegaugesWC.txt to the same directory as http://www.schwab1.com/steel/web_server/gauges-ss-basic.htm
It's all about the relative directory navigation.. since your basic page is two directories down the document tree, and the data is being uploaded two directories up from there, the '../../' will cause the file to be loaded from two directories up.
"Relatives" can be such problems... [banghead] [lol]LOL! So true . . .
gaugeMobileScaling: 0.65, //scaling factor to apply when displaying the gauges mobile devices, set to 1 to disable (default 0.85)
positiontooltip: function ($, $tooltip, e) {
// last ditch attempt to keep the graphs 'on page'
x = Math.max(x, 0);
y = Math.max(y, 0);
$tooltip.css({left: x, top: y});
gaugeMobileScaling: 0.65, //scaling factor to apply when displaying the gauges mobile devices, set to 1 to disable (default 0.85)
Hi Blic, I've just taken a look at this and the gauge resizing works if you just load up the gauges page (http://timberlakesutah.com/wp-content/uploads/Weather/SteelSeries/gauges-ss-basic.htm). Resize your desktop browser down so the window is pretty small and load that page to try it.
The problem I think is when you include the gauges as an iframe, you are specifying a fixed size, so when your main page loads the gauges stay the same width. If you try setting the iframe width to 100%, see what happens.
Thanks I down loaded them both and have 2.5.4 up and running I look at the latest version as soon as I have more time
"forecast":"Current Conditions -- CC$ *** Current Forecast -- CF$ --",
or something similar.The cloudbase rounding is pretty arbitrary, but currently defined as...
Metres: <1 000 m round to 10 m, >1 000 m round to 50 m
Feet: < 2 000 ft round to 50 ft > 2000 ft round to 100 ft
I'll probably add an option to the next release to turn rounding off/on (default on)
// ==================================================================================================================
// Nothing below this line needs to be modified for the gauges as supplied
// - unless you really know what you are doing
// - but remember, if you break it, it's up to you to fix it ;-)
// ==================================================================================================================
Talking about editors (I know I use Windows), I have switched from Sublime Text to Microsoft Visual Studio Code. Don't be put off by the name, it is nothing to do with Visual Studio, it's free, open source, and multiplatform - including Mac.
It is getting great community support and looks like it is going to be very popular. It is actively maintained and developed, and there are monthly update releases. The range of available plugins seems to grows daily.
Definitely worth a look. Like Sublime it is based on your browser engine, snd you do need to have Node.js installed to use it.
I just went to your web site and change it to meters and it worked just find and then I switch it back and it went back to feet I did this several times and it work for me
You chaps may be interested in another little PHP script for your web pages I knocked up last week - Sun Plot.
You can see it in use on my home page (http://weather.wilmslowastro.com/index.php) (not much sun today :( ), and the download is here (http://weather.wilmslowastro.com/scripts.php)
(http://sandaysoft.com/forum/download/file.php?id=13586)
It doesn't matter if you don't have a database that stores the sunshine data, you can use the plot just to show the Suns position as the day progresses and the relative day/night length and changes in Suns elevation. It's self contained, no other libraries etc. required.
I just took a look at your gauges and they are working fine - every change I make within the units the gauges take them at once.
...once you overcome the fear of changing something below the warning line.[lol] Fortune favours the brave! Code on. [computer]
[lol] Fortune favours the brave! Code on. [computer]
<img src="sunplot.php" alt="Sun Plot" width="X" height="Y">
<img src="sunplot.php" alt="Sun Plot" width="X" height="Y">
Have fun!
I almost did not dare to ask, but:
What about adding a time-line from 0 to 24 to the png?
:-X
And yes, put whatever you want in the ticker - so long as you have tags for it. Mine for instance has the date/time, sun hours, and min/max temps for the day.
http://weather.wilmslowastro.com/gauges-ss.php
Do you upload the realtimegaugesWC.txt file properly onto your webspace?
Hi Mark,Nicely done Reinhard - I think that is the first Meteotemplate/SteelSeries integration I have seen.
just want to tell you that your SteelSeries are working perfect not only on my main weather site but also on the Meteotemplate (http://wetter.unterwurzacher.at/template/pages/station/live.php)! Waiting on the Cloud-Height-Graph you are using in your website.
;)
Cheers,
Mark:Leave as is, they launch in a new page anyway so it doesn't really matter.
Thanks for the insight on complying with a security certificate. I am making progress. I have a few questions about some lines in three scripts.
gauges.js
line 170-176 are external links to the various websites of supported weather software programs, none of which currently support https, but as they are only an external link and not actually loading any data or scripts, I assume leaving the correct http link as is, is ok.
language.min.jsFor completeness they should all be changed. But I don't think anyone will ever notice - you never get download errors do you? ;)
line 2 has some error messages like StatusHttp:"HTTP Request Failed", in various languages.
I assume these are ok to leave as is, or should I change to read:
StatusHttp:"HTTPS Request Failed",
Same question about the language.js file:
line 2062 StatusHttp:"Erro no pedido HTTP",
I don't anticipate using this language but should I change the error message to
StatusHttp:"Erro no pedido HTTPS"
Otherwise, I believe I have successfully changed all other scripts referencing http to https.Well done, I might be brave enough to do it myself one day....
You are right, this is not a trivial exercise! :(
For completeness they should all be changed. But I don't think anyone will ever notice - you never get download errors do you? ;)Ha ha. You are correct, I've never had a download error with my SteelSeries Gauges because your scripts work. Thanks, mate. ThU5:-)
...
Well done, I might be brave enough to do it myself one day....
Hi mark and BlickAaaaagh! Don't tell me that. I just spent all day editing my 2.5.15 scripts to comply with my security certificate. Now I have to start all over again. :'(
I just updated to 2.5.18 ...
Can you help me understand the change to the Metar default on line 54 in gauges.js? If the default used to be enabled, but now is disabled, do i want to enable it here in order to keep the wind direction gauge functioning in 2.5.18 like it was in 2.5.15?The change just removes the bit of text in the hover pop-up on the gauge that displays a bit of pseudo METAR type info eg. METAR 17405G10KT 120V240
Thanks. The changes you made are nice, but Reinhard is going to ask you where is the altimeter face for the Cloud Base gauge. :)Ah, that needs some changes to both the script and the SteelSeries libraries.
Thank you for the explanation and quick reply. Again, the tweaks and enhancements that you incorporated are much appreciated. I went through a file by file comparison of every item in the download and you cleaned up a lot of extra spaces and lines, in addition to giving us some nice improvements. Very nice work, Mark, and much appreciated!Github will do the 'diffs' for you as well for a quick look-see what has changed on the web before you decide if it is worth updating in the future.
You are my favourite non-user of WeatherCat. :DAh, Jachym must be challenging me on that front now [cheers1]
@ -2224,6 +2224,7 @@ function () {
ctx.save();
// set the font
ctx.font = 0.08 * size + 'px serif';
+ ctx.strokeStyle = gaugeGlobals.background.labelColor.getRgbaColor();
ctx.fillStyle = gaugeGlobals.background.labelColor.getRgbColor();
ctx.textAlign = 'center';
ctx.textBaseline = 'middle';
@@ -2246,6 +2247,8 @@ function () {
ctx.textAlign = 'center';
ctx.textBaseline = 'middle';
ctx.font = 0.05 * cache.gaugeSize + 'px Arial,Verdana,sans-serif';
+ ctx.strokeStyle = gaugeGlobals.background.labelColor.getRgbaColor();
+ ctx.fillStyle = gaugeGlobals.background.labelColor.getRgbaColor();
ctx.fillText(cache.gaugeOdoTitle, cache.plotSize2, cache.plotSize * 0.75, cache.plotSize * 0.5);
ctx.restore();
}
Please Mark, can you turn on some light in my brain? :-[
Where can i find the full fat library - your first link (SteelSeries library) link takes me to your scripts. And if I can finally find the library, just replace it or add it to the webserver stuff?
Is it possible to add a third (or more) parameter(s) to the temperature gauge: Outdoor, Indoor, T1 (T2, T3, ...)? For the txt file it should be no problem to feed the script with additional parameters.
if (cache.selected === 'out') {
cache.areas = [steelseries.Section(+cache.low, +cache.high, gaugeGlobals.minMaxArea)];
} else {
cache.areas = [];
}
to a switch() as well.Actually, just take a look at the code in "singleDew", that has the framework you need in place already! ::)
If you want to make your code available I can take a look.
2.6.2So it seems that when the needle arrives this sector the LED "sunshine" begins to glow.
* Updated gauges.js
- Solar gauge: Fixed the "over theoretical" sector not displaying correctly above the default gauge max scale value.
- Solar gauge: Added sector to indicate 'sun is shining'.
- Wind gauge: Added animation to rescaling.
- UV gauge: Added rescaling back to default and animation.
- Rain gauge: Added rescaling back to default.
// Logo images are used to 'personalise' the gauge backgrounds
// To add a logo to a gauge, add the parameter:
params.customLayer = _imgBackground;
// to the corresponding drawXxxx() function below.
//
// These are for demo only, to add them remove the comments around the following lines, and
// the _imgBackground definition line above...
_imgBackground = document.createElement('img'); // small logo
$(_imgBackground).attr('src', config.imgPathURL + 'logoSmall.png');
// End of logo images
_imgBackground, // Uncomment if using a background image on the gauges */
// params.customLayer = _imgBackground;
params.customLayer = _imgBackground;
to the rest of the parameters. // Optional - add a background image
/*
if (g_imgSmall !== null) {
var drawSize = g_size * 0.831775;
var x = (g_size - drawSize) / 2;
buffers.ctxBackground.drawImage(g_imgSmall, x, x, cache.gaugeSize, cache.gaugeSize);
}
*/
You can easily have different sized gauges on the same page, in the gauges-ss.css I have created two additional classes ".gaugeSizeSml" and ".gaugeSizeLrg", (again you can edit the width/height values of these classes to whatever you want), to assign one of these alternative sizes to a gauge, edit the HTML and change (for example)...Great to have CSS involved, it really helps when media queries can be used.
"intemp":"STAT$INTTEMPERATURE:CURRENT$",
"intempTL":"STAT$INTTEMPERATURE:MIN:TODAY$",
"TintempTL":"STAT$INTTEMPERATURE:MIN:TODAY:TIME$",
"intempTH":"STAT$INTTEMPERATURE:MAX:TODAY$",
"TintempTH":"STAT$INTTEMPERATURE:MAX:TODAY:TIME$",
Quick question, I'm adding indoor temperature min/max (and times) at the request of Weather Display user to make it consistent with the indoor humidity. To add the extra data to the WC data file are these data values available, and would the correct fields be...Code: [Select]"intemp":"STAT$INTTEMPERATURE:CURRENT$",
"intempTL":"STAT$INTTEMPERATURE:MIN:TODAY$",
"TintempTL":"STAT$INTTEMPERATURE:MIN:TODAY:TIME$",
"intempTH":"STAT$INTTEMPERATURE:MAX:TODAY$",
"TintempTH":"STAT$INTTEMPERATURE:MAX:TODAY:TIME$",
Maybe one of these days, you will share your code for the altimeter look on the Cloud Base gauge so that Reinhard and I will stop feeling sorry for ourselves. ;DYou could always take a peek at my script and copy the changes to that gauge - but I'd do it on a test page and it's an unsupported process! ;)
824: cache.maxMinVisible = true;
831: cache.maxMinVisible = false;
After weeks of a heat wave and not a cloud in the sky - we are clouded out tonight [banghead]
Yeah, I haven't implemented trends on the indoor, sorry. :(
Yeah, I haven't implemented trends on the indoor, sorry. :(
Still an extremely impressive set of gauges, Mark. Even without trends on indoor. Thanks for sharing them.
yes Mark they are great I have them listed on my weather page just not the latest version
Update your files, brother; you'll be glad you did.
scriptVer : '2.7.3',
Scripts: Mark Crossley - version <span id="scriptVer"></span><br>
scriptVer : '2.7.3',
weatherProgram : 3, // Set 0=Cumulus, 1=Weather Display, 2=VWS, 3=WeatherCat, 4=Meteobridge, 5=WView, 6=WeeWX, 7=WLCOM
imgPathURL : '../', // *** Change this to the relative path for your 'Trend' graph images
oldGauges : 'gauges.htm', // *** Change this to the relative path for your 'old' gauges page.
realtimeInterval : 30, // *** Download data interval, set to your realtime data update interval in seconds
longPoll : false, // if enabled, use long polling and PHP generated data !!only enable if you understand how this is implemented!!
gaugeMobileScaling : 0.85, // scaling factor to apply when displaying the gauges mobile devices, set to 1 to disable (default 0.85)
graphUpdateTime : 15, // period of pop-up data graph refresh, in minutes (default 15)
stationTimeout : 3, // period of no data change before we declare the station off-line, in minutes (default 3)
pageUpdateLimit : 20, // period after which the page stops automatically updating, in minutes (default 20),
// - set to 0 (zero) to disable this feature
pageUpdatePswd : 'its-me', // password to over ride the page updates time-out, do not set to blank even if you do not use a password - http://<URL>&pageUpdate=its-me
digitalFont : false, // Font control for the gauges & timer
digitalForecast : false, // Font control for the status display, set this to false for languages that use accented characters in the forecasts
showPopupData : true, // Pop-up data displayed
showPopupGraphs : true, // If pop-up data is displayed, show the graphs?
mobileShowGraphs : false, // If false, on a mobile/narrow display, always disable the graphs
showWindVariation : true, // Show variation in wind direction over the last 10 minutes on the direction gauge
showWindMetar : false, // Show the METAR substring for wind speed/direction over the last 10 minutes on the direction gauge popup
showIndoorTempHum : false, // Show the indoor temperature/humidity options
showCloudGauge : true, // Display the Cloud Base gauge
showUvGauge : true, // Display the UV Index gauge
showSolarGauge : true, // Display the Solar gauge
showSunshineLed : true, // Show 'sun shining now' LED on solar gauge
showRoseGauge : true, // Show the optional Wind Rose gauge
showRoseGaugeOdo : false, // Show the optional Wind Rose gauge wind run Odometer
showRoseOnDirGauge : true, // Show the rose data as sectors on the direction gauge
showGaugeShadow : true, // Show a drop shadow outside the gauges
roundCloudbaseVal : true, // Round the value shown on the cloud base gauge to make it easier to read
// The realtime files should be absolute paths, "/xxx.txt" refers to the public root of your web server
realTimeUrlLongPoll: 'realtimegauges-longpoll.php', // *** ALL Users: If using long polling, change to your location of the PHP long poll realtime file ***
// *** the supplied file is for Cumulus only
realTimeUrlCumulus : 'realtimegauges.txt', // *** Cumulus Users: Change to your location of the realtime file ***
realTimeUrlWD : 'customclientraw.txt', // *** WD Users: Change to your location of the ccr file ***
realTimeUrlVWS : 'steelseriesVWSjson.php', // *** VWS Users: Change to your location of the JSON script generator ***
realTimeUrlWC : '../realtimegaugesWC.txt', // *** WeatherCat Users: Change to your location of the JSON script generator ***
realTimeUrlMB : 'MBrealtimegauges.txt', // *** Meteobridge Users: Change to the location of the JSON file
realTimeUrlWView : 'customclientraw.txt', // *** WView Users: Change to your location of the customclientraw.txt file ***
realTimeUrlWeewx : 'gauge-data.txt', // *** WeeWX Users: Change to your location of the gauge data file ***
realTimeUrlWLCOM : 'WLrealtimegauges.php', // *** WLCOM Users: change to location of WLCOMtags.php file ***
useCookies : true, // Persistently store user preferences in a cookie?
tipImages : [],
dashboardMode : false, // Used by Cumulus MX dashboard - SET TO FALSE OTHERWISE
dewDisplayType : 'app' // Initial 'scale' to display on the 'dew point' gauge.
Browser had a stale cache that got refreshed?
What do I need to type - and in which file please ?System Preferences->Language & Region->Advanced settings" You kay have hidden that pref but you can see it in the Menu Bar for System Prefs. You can also get there through the Date & Time prefs.
DOTSEPARATORS${"date":"de$",
"timeUTC":"DUTC$",
"SensorContactLost":"COMMSFAILFLAG$",
...
Question to the masses: Should I update the SS Gauges template file for WeatherCat to include the DOTSEPARATORS$ tag? It means it will then only work for ver 3.1 onwards, but new uesers will only be using that release anyway?
So the start of the file would become...Code: [Select]DOTSEPARATORS${"date":"de$",
"timeUTC":"DUTC$",
"SensorContactLost":"COMMSFAILFLAG$",
...
@WDev/Stu - is the tag "DOTSEPARATORS$" just removed? Does it need to be on a separate line?
Question to the masses: Should I update the SS Gauges template file for WeatherCat to include the DOTSEPARATORS$ tag? It means it will then only work for ver 3.1 onwards, but new uesers will only be using that release anyway?
So the start of the file would become...Code: [Select]DOTSEPARATORS${"date":"de$",
"timeUTC":"DUTC$",
"SensorContactLost":"COMMSFAILFLAG$",
...
@WDev/Stu - is the tag "DOTSEPARATORS$" just removed? Does it need to be on a separate line?