pirateweather icon indicating copy to clipboard operation
pirateweather copied to clipboard

Current Apparent Temperature results inconsistent

Open cloneofghosts opened this issue 8 months ago • 8 comments

Describe the bug

I know this was reported before in #76 and was fixed by using NBM/GFS apparent temperature. While for the most part this fixes the issue I've found that if NBM and HRRR forecast different temperatures then the apparent temperature shown in the API can be off.

This is what I see in the API currently:

"currently": {
  "time": 1717703760,
  "summary": "Rain",
  "icon": "rain",
  "nearestStormDistance": 0,
  "nearestStormBearing": 0,
  "precipIntensity": 3.3043,
  "precipProbability": 0.98,
  "precipIntensityError": 1.61,
  "precipType": "rain",
  "temperature": 22,
  "apparentTemperature": 20.45,
  "dewPoint": 20.55,
  "humidity": 0.89,
  "pressure": 986.47,
  "windSpeed": 4.59,
  "windGust": 7.08,
  "windBearing": 259,
  "cloudCover": 0.86,
  "uvIndex": 0.94,
  "visibility": 4.65,
  "ozone": 333.81
},

Expected behavior

The apparentTemperature results are inconsistent depending on HRRR and NBM temperatures.

Actual behavior

The apparentTemperature should be consistent no matter what temperatures are returned by the models.

API Endpoint

Production

Location

Ottawa, Ontario

Other details

No response

Troubleshooting steps

  • [X] I have searched this repository and Home Assistant Repository to see if the issue has already been reported.
  • [X] I have read through the API documentation before opening this issue.
  • [X] I have written an informative title.

cloneofghosts avatar Jun 06 '24 19:06 cloneofghosts