Icon format in forecast changed about core

[iprak]

I was able to get nws component working by bumping the pynws dependency=1.8.2.

[home-assistant]

Hey there @MatthewFlamm, @kamiyo, mind taking a look at this issue as it has been labeled with an integration (nws) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nws can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign nws Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

nws documentation
nws source
_{^{(message by IssueLinks)}}

[3of9]

This also started happening for me today at 11:42 am Eastern US time.

[SCBionicle]

I'm having the same issue.

[kevinhaas]

@MatthewFlamm Is there anyway I can apply the patch for pynws myself?

[kevinhaas]

Thanks! All good now.

[iprak]

@MatthewFlamm Is there anyway I can apply the patch for pynws myself?

You can copy nws from core\components into custom_components\nws, edit the manifest to use 1.8.2 and restart.

[kevinhaas]

Was good for couple days but yesterday around 3-4pm EST both stations went unavailable and haven't come back since. I tried adding a few other random stations, and all return Failed to call service weather.get_forecasts. Service call requested response data but did not match any entities.

I have the fix from #119114 (comment) applied as well as pynws bumped to 1.8.2 so I'm hesitant to open a new issue since I don't think it's made its way to core yet. I'll keep an eye on it.

[MatthewFlamm]

This is a separate issue. Please open a new one.