Incorrect Temperature

[t34wrj]

Describe the bug

My latitude and longitude are entered correctly but the current temperature is incorrect. It is now currently 18 degrees celsius according to numerous weather sources but PirateWeather is reporting the temperature as 15.7 degrees celsius which is incorrect.

Expected behavior

For the temperature to be correct.

Actual behavior

An incorrect temperature is shown.

Home Assistant version

2024.4.2

Integration version

1.4.5.1

Other details

No response

Troubleshooting steps

• I have updated my Home Assistant installation to the latest version.
• I have updated the Pirate Weather Integration to the latest version.
• I have gone through the documentation, parameter documentation and sensor documentation before opening this issue.
• I have searched this repository and Pirate Weather Repository to see if the issue has already been reported.
• I have restarted my Home Assistant installation.
• I have checked to see if the issue is not an API issue.
• I have written an informative title.

[alexander0042]

Hi, thanks for using this service, and apologies for the issue here. Do you mind sharing your approximate location, since that will help me dial in the issue

[t34wrj]

Hey - thanks for putting the service together. I'm [REMOVED]. Having enabled the apparent temperature sensors, these seem to give a more consistent temperature compared to the other weather services.

[alexander0042]

Thanks for the info! The apparent temperature might line up closer to what other sources say, since they often default to that. The other possibility is depending on how close to the ocean you area, it'll sometimes be swayed by that, but only if you're within a couple km

[t34wrj]

No worries. As an aside, can I ask what the difference is between the 0h and the 'normal' sensor. For example, my sensor.pirateweather_wind_speed sensor states 11.03mph but the sensor.pirateweather_wind_speed_0h states 10.25mph? Thanks for your help.

[alexander0042]

Good question, and something I should improve in the docs. 0h is the top of the hour, while the other sensor is the current condition. Behind the scenes it's just a linear interpolation, between hours 0 and 1, so you should see values between those two numbers

[RollingStar]

I might be running into this. Since I updated my Hass and all associated addons (PirateWeather) a few days ago it seems like the weather is out of sync with PW's hourly forecast. rn it's showing 66F which isn't supposed to happen for 3 hours. I think this is my first time Hass has been on PW 2.x but I'm not sure. (Time zone issues? I'm in New York time which is UTC-4 +/- DST).

This is weather.com which generally feels right to me:

My ecobee thermostat shows 70F from whatever cloud service it's pulling from.

I have PW updating every 15 minutes. I would expect the current temperature to be between the current hour's forecasted temp and the next hour's forecasted temp. (Fun wrinkle: I think my PW hourly forecast and some other info do not update in lockstep, so for example it will show 10pm on the hourly forecast when it's 11:06. But nothing in my data should be older than 15 minutes.)

[cloneofghosts]

The reason why you're seeing the current temperature below the forecasted hourly temperature is due to the fact that the current temp and the hourly temp come from different models. The current temp is coming from HRRR whereas the hourly temp is coming from NBM.

This is something that @alexander0042 should improve in the docs as they haven't fully been updated for version 2.0.