Pirate-Weather/pirateweather

Negative/Unrealistic UV Index Value & Precipitation Intensity

cloneofghosts opened this issue · 5 comments

cloneofghosts commented

I noticed late night on Thursday that the API was giving some unrealistic values for the UV index. I first noticed this in my HA installation and checked in the browser and I can confirm that it's an API issue rather than a HA issue.

The first thing I noticed was at 11:50 PM there was a UV index of 0.03 which shouldn't be possible at that point. I wonder if it was using the absolute value of -0.03 which is why it returned 0.03 instead of -0.03.
image

  "currently": {
    "time": 1687492260,
    "uvIndex": 0.03,
  },

The second thing I noticed was that the current day has a forecasted UV index of -0.03 which makes no sense. I know I mentioned this in #7 and #4 but it was never fixed.
image

  "daily": {
    "summary": "Rain",
    "icon": "rain",
    "data": [
      {
        "time": 1687406400,
        "uvIndex": -0.03,
      },

EDIT: Seems to be a common occurrence late at night (around 10/11pm) as I noticed it again a few days ago.

cloneofghosts commented

The 1.5.4 update seems to have fixed this as well. Will close for now but if it pops up again I will re-open.

cloneofghosts commented

Just noticed the same issue pop up again. Current UV is 0.03, the daily UV index is -0.0 but the hourly data is fine.

cloneofghosts commented

@alexander0042 I also found that a negative precipIntensity and precipIntensityError are still possible

  "currently": {
    "time": 1690053600,
    "summary": "Clear",
    "icon": "clear-day",
    "nearestStormDistance": 0,
    "nearestStormBearing": 0,
    "precipIntensity": -0.0005,
    "precipProbability": 0.0,
    "precipIntensityError": -0.0,
    "precipType": "rain",
    "temperature": 21.7,
    "apparentTemperature": 27.49,
    "dewPoint": 17.72,
    "humidity": 0.78,
    "pressure": 1009.08,
    "windSpeed": 16.63,
    "windGust": 31.36,
    "windBearing": 166,
    "cloudCover": 0.18,
    "uvIndex": 5.51,
    "visibility": 4.5,
    "ozone": 302.01
  },

I found this issue while using these coordinates 47.486771,-52.751787 so maybe it's just a GFS/GEFS issue but I have seen precipIntensityError be -0.0 before in the HRRR domain.

cloneofghosts commented

Going to bump this before I get the stale notification. I just checked and I'm seeing "uvIndex": 0.05, 2 hours after sunset which seems a little bit off? I think the negative issues can still happen though I haven't seen it lately.

EDIT: Seeing the negative precipIntensityError for my location currently. "precipIntensityError": -0.0,

cloneofghosts commented

There's already #88 to take care of the unrealistic UV Index values and the negative values seem to be fixed in the V2 beta.