UV Index graph only graphs integer values?

[GizmoEV]

I don't know if this has been addressed before since the forum search engine doesn't allow searching for "UV Index".

I have a Meteobridge Pro (red) with two Weatherflow Smart Weather stations. When I look at the graph of UV Index it only shows integer values even though the Live Data does show to the tenth place. You can see this here: https://admin.meteobridge.com/efbeb8326 ... D7&stop=D0

Is this by design? If so, why?

Thank you,

[Mattk]

Have not checked this but could this be a function of the .chart variables which can be modified. In any case UV Index scale is whole numbers, nobody splits hairs between Low (0-2), Moderate (3-5), high (6-7), Very High (8-10), Extreme (11+), like what is the point of decimals with such an index scale?

[weatherist34]

matt its just the way the weatherflow formulates the light sensor component . there are many things i found that dont conform the familiar ways we have become accustom to with our weather hardware over the years.weatherflow has some bizarre or non standard ways of displaying data . it blows my mind sometimes and ive tried in vain to communicate these variances without any success it gets drowned out by noise by others. the constant zero wind speed and direction every couple of seconds just frustrates me and screws up any chart average data recorded .i wish was it was calm here sometimes but calm days in a year you could count on one hand.

best meteobridge sticks to the common formula outputs . brian

[GizmoEV]

In any case UV Index scale is whole numbers, nobody splits hairs between Low (0-2), Moderate (3-5), high (6-7), Very High (8-10), Extreme (11+), like what is the point of decimals with such an index scale?

While the way people use the scale might be integers, it is most definitely continuous since it is dependent upon the intensity of UV radiation. Why explicitly program to graph only integer values rather than the real number values? Why throw out values which give better visuals for rates of change?

In any case, it appears this is by design so I'll live with it even though I don't like it.

the constant zero wind speed and direction every couple of seconds just frustrates me and screws up any chart average data recorded

Did you see that I took one of my SKY units and turned it so its North faced due West. It helped WF find a bug in their formulas where null values were getting turned to zeros and messing up the averages. I'm not sure when a fix will be pushed out.

Thank you for the responses,

[weatherist34]

In any case UV Index scale is whole numbers, nobody splits hairs between Low (0-2), Moderate (3-5), high (6-7), Very High (8-10), Extreme (11+), like what is the point of decimals with such an index scale?

While the way people use the scale might be integers, it is most definitely continuous since it is dependent upon the intensity of UV radiation. Why explicitly program to graph only integer values rather than the real number values? Why throw out values which give better visuals for rates of change?

In any case, it appears this is by design so I'll live with it even though I don't like it.

the constant zero wind speed and direction every couple of seconds just frustrates me and screws up any chart average data recorded

Did you see that I took one of my SKY units and turned it so its North faced due West. It helped WF find a bug in their formulas where null values were getting turned to zeros and messing up the averages. I'm not sure when a fix will be pushed out.

Thank you for the responses,

Matt is referring to the WHO standards of reporting UV index commonly used in health warnings etc.. but the extra decimal has no real value the value should have been rounded of correctly in the firmware . but obviously the noise surrounding this product is hard to get this point across clearly to anyone on that forum.

No sorry i did not see any reference as I said above too much noise and misinformation , i get accused of being arrogant whenever I raise an issue and there are many underlying issues. I gave up a few weeks ago 5th Sky unit arrived and same old teething baffling issues . 18 months of testing ive seen little improvement in the areas that really matter. Its a weather station meant for measuring data but all I see is non conforming methods .

Sorry to be negative but Im not a believer that this product is ready for prime time and with 1000+ units in circulation it needed more time and Im not a convert for measuring rainfall by an haptic sensor . The wind speeds ,direction play nicely in dry conditions throw at bit of steady rain or dense fog and it all goes awol and erratic. These are my personal experiences cant speak for others but having just installed another new piece of hardware on monday a Davis VP2 everything worked out the box and data conforms to the familar readings of previous hardware I have owned .. anyway there is my rant and to SUM it up meteobridge UV values is based on traditional UV index scale https://www.epa.gov/sunsafety/uv-index-scale-1

brian

[GizmoEV]

Thanks, Brian. I understand where it comes from. I still think that the integer interpretation should come from the user's reading of the graph of the actual data. If the WF sensor actually measures the intensity of the specific UV ranges to come up with the UV index and doesn't calculate it from a more general brightness value then it makes sense to report a finer grained value. I can imagine a situation where, for the same lux, the UV index could be different. This difference, however, might not be noticeable with single digit precision. I have no idea what the sensor in the WF is actually measuring so this may be a case of "increasing precision through calculation" rather than actual measurement precision.

I see the WF station as still in the beta stage. That might be why they aren't releasing it to non-Indegogo backers just yet. As you pointed out to me, with the Meteobridge I can easily add different weather stations and have all the data stored/sent by the MB and not be tied to just WF. I'll see how things go this winter. If I'm understanding things correctly, I can just have the MB ignore any sensors I want.

[weatherist34]

hello you will understand its not a dedicated UV sensor its a light sensor component and i guess a formula is at work to determine the output value hence the decimal place..

many months ago I came up with simple formula to calculate an average UV index figure for a 10-15 minute period by just using a dedicated Solar Sensor from Davis. the formula simply takes into consideration latitude and a simple additional divider. [sol0rad-avg10:--]/$lat/5 or [sol0rad-avg15:--]/$lat/5

basically simply only adjust the last value in this case 5 is to get an average UV value for UK users the value is increased further north you go but only in small increments of 1 decimal place..

basically adjust the last value to get an average example istanbul would be [sol0rad-avg15:--]/$lat/3.45

so i use it now my solar value under cloudy conditions right now is 311 actual UV calculated is 2.15 or rounded down to 2

it was always within expected .it was primarily worked out for those that couldnt justify the £400 price tag of the davis uv sensor at the time.

beta sure is but over 1000 units in circulation doesnt do it justice.. another topic for another day ..take care brian..