Unable to connect to PirateWeather - CertificateError

When HA starts, I’m getting the following error: 2022-05-27 19:27:28 ERROR (SyncWorker_3) [custom_components.pirateweather.weather] Unable to connect to PirateWeather. HTTPSConnectionPool(host='api.pirateweather.net', port=443): Max retries exceeded with url: /forecast/om3xxPNoEt94XXXXXXXXXXCM78xtHiJ2s5iZsYa/XX.XXX50780789178,-XXX.XXX9254007341?units=us (Caused by SSLError(CertificateError("hostname 'api.pirateweather.net' doesn't match either of 'susi.comcast.net', '*.aws-np.susi.comcast.net', '*.aws-np.susi.xfinity.com', '*.aws.susi.comcast.net', '*.aws.susi.xfinity.com', '*.susi.comcast.net', '*.susi.xfinity.com', 'register-dev.xfinity.com', 'register-ng.xfinity.com', 'register-qa.xfinity.com', 'register-st.be.xfinity.com', 'register-st.xfinity.com', 'register-wg-st.bi.xfinity.com', 'register-wg-st.xfinity.com', 'register-wg.bi.xfinity.com', 'register-wg.xfinity.com', 'register.be.xfinity.com', 'register.xfinity.com'")))

Yet when I visit the URL directly I get valid JSON: https://api.pirateweather.net/forecast/om3xXXXXXXXXXXXXXXXXXn3fCM78xtHiJ2s5iZsYa/XX.XX450780789178,-XXX.XXX29254007341?units=us

(sensitive info redacted)

Running: e95083f HA: 2022.5.5 In Docker; official container

I’m not understanding why it’s trying to compare api.pirateweather.net with a .xfinity.* cert.

[xstrex]

So this is a weird one, but it seems to have been an issue with Comcast/Xfinity. I don’t make any configuration change, and it just started working a few days ago.

For anyone else who finds this… My “deal” expired with xfinity (though I still had service), once I got a new “deal” with a better price, the issue seems to of resolved itself, or so it appears. May be completely unrelated, but seems like an odd coincidence.

Component is working great again!

[alexander0042]

Thank you so much for posting the update here! I can’t say enough how much I appreciate it when I’m looking for a solution and someone posted the fix that works for them in the thread, so this is idea (even if it’s still a bit of a mystery).

I’m hoping that it was a fix Comcast rolled out, but either way, good that it’s resolved. If you run into any other issues or have another idea, feel free to open a new issue and we can go from there!

Thanks, Alexander