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:
The wind rose was not drawn, only the shadow
The countdown timer was at 0 all the time and the gauges did NOT update
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.
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 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 - 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 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.
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.
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
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