Big problems with V2.0.3

I installed the SteelSeriesGauges, V2.0.2 a couple of weeks ago, and it has ben working fine. After installing V2.0.3 I have started having big problems.

After installing V2.0.3 everything was fine. Then I discovered 2 days ago that I had a problem:

  1. The wind rose was not drawn, only the shadow
  2. The countdown timer was at 0 all the time and the gauges did NOT update
  3. When pointing the mouse to a gauge, I only got an empty frame with no graph.

All the gauges got the correct value when opening or refreshing the page, but they didn’t update.

This was strange, because I had not done any changes. I also tried 3 browsers on my PC and 3 browsers on my iPad with the same result.

I gave up and went to bed. Next morning everything was working! It has been working until this afternoon. Then the same happened. For a couple of hours I had the error. And then suddenly now it’s working again.

I have one theory, the wind rose gauge. I noticed that when this happened 2 days ago I had no wind for a long time, and the direction was 0 degrees. The same happened today, no wind and 0 degrees. Then when it started to work again I see that I had a little wind and a direction of 270 degrees. Can that be the problem? And that the script fails because of that? I have checked, but I’m not good enough in HTML5 and JavaScript.

I had planned to remove the windrose to see if that would help, but then it started working again. I will do that the next time I see it.

Do any of you know more about this?

My wind speed was zero for about 20 hours because it froze. The wind rose was just the outline and the graphs didn’t work. Once the wind started everything worked like before. I’m sure it has to do with the wind rose and no wind. When it wasn’t working the wind rose data was all zeros.

That confirms my theory. Let’s hope that Mark can find the cause of the problem.

Have you looked at the customclientraw in that condition? Maybe it’s getting — or something for speed or direction that the code can’t handle.

That was my thoughts too, but I never managed to get a copy of the file when it was happening to someone, every time I looked the wind had started again.

I suspect that is the problem though as my anemometer froze up the other day and the Wind Rose still displayed OK - with nothing plotted of course :slight_smile: - so there must be a difference between Cumulus and WD in how the ‘no wind’ situation is handled. Cumulus returns an array of zeros for the rose data in the absence of wind.

I will check the customclientraw the next time it happens (I’m sure it will happen again :slight_smile: ). Anything else I should chech the next time?

I had looked at the windrose data in the custom clientraw file when this happened. The data had zeros.

Did you capture the whole file by any chance? If so please attach it.

I’m sorry I didn’t. If it happens again I will get it for you.

it should be zeros…
but I will check the code

on checking the code
one problem might be that, is the script expecting
00.0
or
0.0
for the windrose data arrary?
?

Could be Brian, but if I can get a copy of a problematic customclientraw.txt file it should be easy to see the problem and fix it.

I haven’t had a wind gust in a little over 3 hours. The wind rose is just a shadow and the graphs stopped working. I’ve attached the customclientraw file. I hope this helps.

Edit: Just after I posted this I had a small wind gust and the wind rose and graphs came back. The attached file is from when there wasn’t a gust.

{“date”:“09:22 AM”,“dateFormat”:“m/d/y”,“temp”:“23.7”,“tempTL”:“19.6”,“tempTH”:“25.8”,“intemp”:“63.2”,“dew”:“11.5”,“dewpointTL”:“8.5”,“dewpointTH”:“13.1”,“apptemp”:“19.5”,“apptempTL”:“13.8”,“apptempTH”:“25.6”,“wchill”:“23.7”,“wchillTL”:“10.7”,“heatindex”:“23.7”,“heatindexTH”:“25.8”,“humidex”:“16.3”,“wlatest”:“0.0”,“wspeed”:“0.0”,“wgust”:“2.7”,“wgustTM”:“18.8”,“bearing”:“78”,“avgbearing”:“51”,“press”:“30.059”,“pressTL”:“24.191”,“pressTH”:“30.070”,“pressL”:“24.191”,“pressH”:“30.540”,“rfall”:“0.00”,“rrate”:“0.00”,“rrateTM”:“0.000”,“hum”:“59”,“humTL”:“50”,“humTH”:“67”,“inhum”:“0”,“SensorContactLost”:“0”,“forecast”:“”,“tempunit”:“F”,“windunit”:“mph”,“pressunit”:“inHg”,“rainunit”:“in”,“temptrend”:“+1.9”,“TtempTL”:“6:36 AM”,“TtempTH”:“12:14 AM”,“TdewpointTL”:“5:56 AM”,“TdewpointTH”:“8:37 AM”,“TapptempTL”:“6:35 AM”,“TapptempTH”:“2:01 PM”,“TwchillTL”:“12:04 AM”,“TheatindexTH”:“12:14 AM”,“TrrateTM”:“00:00 AM”,“ThourlyrainTH”:“”,“LastRainTipISO”:“1/16/2013 11:39 AM”,“hourlyrainTH”:“0.000”,“ThumTL”:“12:00 AM”,“ThumTH”:“8:02 AM”,“TpressTL”:“1:58 AM”,“TpressTH”:“8:27 AM”,“presstrendval”:“+0.010 “,“Tbeaufort”:“8”,“TwgustTM”:“1:30 AM”,“windTM”:“11.6”,“bearingTM”:“282”,“timeUTC”:“2013,01,21,14,22,51”,“BearingRangeFrom10”:“360”,“BearingRangeTo10”:“99”,“UV”:“0.0”,“SolarRad”:“0”,“CurrentSolarMax”:“0”,“SolarTM”:”-1”,“domwinddir”:“Northwesterly”,“WindRoseData”:[17.0,25.0,7.0,2.0,6.0,0.0,0.0,0.0,0.0,1.0,5.0,3.0,5.0,12.0,30.0,41.0],“version”:“10.37R”,“build”:“45”,“ver”:“8”}

This is the file with the wind gust.


customclientraw.txt (1.44 KB)

customclientrawwithwind.txt (1.44 KB)

OK, I see the problem - a cut’n’paste error in the SteelSeries library - I’ll get a fix out for it soon…

Edit: Also it seems your ‘low pressure today’ value is being set to your ‘record all time low’ value? And that seems very low too?

Version 2.0.4 is now available for download, which should fix this issue.

Edit: Also it seems your 'low pressure today' value is being set to your 'record all time low' value? And that seems very low too?

the custom tags used are for all time record hi/lo barometer (%recordlowbaro%)
what should be used?

The relevant sections of the customclientrawlocal.txt are:


"pressTL":"%lowbaro%",          // Today's lowest pressure
"pressTH":"%highbaro%",         // Today's highest pressure
"pressL":"%recordlowbaro%",     // All time lowest pressure
"pressH":"%recordhighbaro%",    // All time highest pressure

You can see the processed ccr file above has:


"pressTL":"24.191",
"pressTH":"30.070",
"pressL":"24.191",
"pressH":"30.540",

So Today’s low and the all time low are the same?

WD recorded that low barometer reading. It was an error. The weather station didn’t have that low a reading. I don’t think it had anything to do with the steel gauges script.

So Today's low and the all time low are the same?
no weatherbee would have reset the all time record low, I would say, so that it is now the current baro (i.e today's low) ideally WD should not be recording a 0 for record low baro, ie it should be ignoring that I will check on that

Mark,

My system was still dropping the wind rose gauge on occasion through 2.0.3. Didn’t keep reporting it because I didn’t want to be a bigger pest than I already am. However, what I finally nailed down in the failures was that, every time, the direction reported from WD was 360