I am having the same problem as of this morning. Connect Call to 192.67.45.111 fails.
Dittoā¦
The server at EC seems to be currently unresponsive and times out on requests.
Here is the apparent contact email. [email protected]
The map layer is provided by Natural Resources Canada, and it seems to be currently unavailable.
Does anyone have a connection at NRC? It is probably something that could be fixed easily with some communication.
For future consideration: It would be ideal if the entire integration wasnāt prevented from being set up / started up if only the radar canāt be loaded.
In my install I did not add the map at all in the UI nor yaml, however the entire integration seems broken right now, not pulling any data
Just confirming that Iām also seeing this same error, thought it was because of my recent update to 2021.12
Not sure on the simplicity. It might be easy. Or not. The challenge is that the data coordinator for radar is setup at the same time as the one for weather. They cannot be separated as far as I know.
Iām more curious why hung radar is blocking weather. Weāll have to see if thereās another API that can be used in init.
Me too! I rolled back and itās still broken. Then I searched.
The vulnerability āLog4Shellā is making headlines worldwide. Many GoC Servers are shut down as a precaution until a patch is applied. I suspect itās whatās got us into this problem.
Yes, that most likely explains it!
Iāve added a fallback map service that will correct this error, and the change will be released with 2021.12.2. Thanks for your patience.
Thank you for your diligent work on this issue. Very much appreciated.
Thatās great Michael. Thanks for pushing this out so quickly. What fallback map service did you use?
For the future, you may want to add in a config option to the set-up dialog in config flow for the map service like some HA integrations do.
Iām using Mapbox. Since it requires an API key Iām running the requests through a proxy function in my AWS account for now, but longer term we could look at adding an API key parameter to the config so users could provide their own.
2021.12.2 has been released and has resolved this issue in my local install. Please update to this version and let me know if you have any issues.
Rookie questionā¦ I pulled in the fix before updating to 2021.12.2 by fumbling my way through the āCustom deps deploymentā add-on. Now that itās been officially updated, is there anything I need to do to disable that? Or will the new update simply overwrite it?
Working well for me.