gwww
April 25, 2025, 3:41pm
243
Serious bug in 2025.4.3. Will be fixed in 2025.4.5 or 2025.5.0. A touch more here. Environment Canada Integration - Error 404 Every Night at 8:02 - #18 by gwww
I noticed this morning the radar map in the Environment Canada integration has become washed out (map almost completely white) and can hardly see any map details. The radar overlay is fine (has vivid colours of intensity), just the map.
It flicker from normal to washed out yesterday as it went through the radar animation, but now it seems to be washed out all the time. Not sure if this is a Hass thing or on the Environment Canada end?
Has anyone else noticed that the radar got washed out? I don’t usually use th integration radar but caught another post here asking about it, when I checked sure enough it’s totally washed out.
The other post can be found here .
Can confirm mine is washed out as well. I linked back to this thread from the main integration thread as it gets dev visibility.
1 Like
Yes, I noticed this yesterday along with a new legend. I’ll try to see if I can figure out what Environment Canada changed to cause this.
Thanks, I asked the mods to merge that thread into this one.
I’m not sure what Environment Canada changed to cause this but I’ll look into it.
I’ve opened a PR to fix the radar issue, and to prevent the weather data from breaking on June 25:
dev ← michaeldavie:env-canada-0.11.0
opened 08:23PM - 08 Jun 25 UTC
## Proposed change
- Bump `env-canada` to v0.11.1
- Required by June 25 to s… upport a [breaking change](https://comm.collab.science.gc.ca/mailman3/hyperkitty/list/[email protected] /thread/T25LGILGF5BIJMU3LYEY72IXLNVTGUWB/) in the upstream data
- Changelog: https://github.com/michaeldavie/env_canada/blob/master/CHANGELOG.md
- Comparison: https://github.com/michaeldavie/env_canada/compare/0.10.2...v0.11.1
## Type of change
- [x] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: [Radar map washed out](https://community.home-assistant.io/t/environment-canada-integration-2021-11-onwards/353003/244?u=michaeldavie)
- This PR is related to issue:
- Link to documentation pull request:
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
4 Likes
The fix has been approved for 2025.6.0, which is listed as “due by June 11”.
I’ve also opened a second PR that will fix the issue of multiple radars not working.
dev ← michaeldavie:env-canada-0.11.2
opened 12:26AM - 09 Jun 25 UTC
## Proposed change
Fixes an upstream caching issue that prevented the use of … multiple camera (radar) entities.
Changelog: https://github.com/michaeldavie/env_canada/blob/master/CHANGELOG.md
Compare: https://github.com/michaeldavie/env_canada/compare/v0.11.1...v0.11.2
## Type of change
- [x] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #122971 #92071
- This PR is related to issue:
- Link to documentation pull request:
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
1 Like
The weather parts of the integration are currently not working, and will be fixed in 2025.10.2.
dev ← michaeldavie:env-canada-0.11.3
opened 11:47PM - 07 Oct 25 UTC
## Proposed change
Bump `env-canada` to v0.11.3 to address upstream data chan… ges.
Release notes: https://github.com/michaeldavie/env_canada/releases/tag/v0.11.3
## Type of change
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #153938
- This PR is related to issue:
- Link to documentation pull request:
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [x] I understand the code I am submitting and can explain how it works.
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
- [x] Any generated code has been carefully reviewed for correctness and compliance with project standards.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
4 Likes
Since yesterday I’ve had no weather update from the integration, just checking now and the doc links to the weeather station IDs and the raw XML data are returning 404s. Could something have changed on their end?
site_list_towns_en.csv citypage_weather/xml/
123
October 8, 2025, 12:40pm
253
Yes. They rearranged the location of their data files. See michaeldavie’s linked PR.
LOL that wasn’t there when I started writing that I swear, but I also didn’t look back as I was in a hurry.
Thanks michaeldavie.
1 Like
I put together a custom weather card using animated versions of Environment Canada’s icons created by a user, @MattMckenzy . It also uses Environment Canada’s condition description, rather than the more limited ones provided by the weather data type.
See the (static) screenshot and code linked below.
custom-card-setup.md
# Custom Weather Card Setup Instructions
## Step 1: Copy the Card File
Copy `custom-weather-card.js` to your Home Assistant `www` folder:
```
/config/www/custom-weather-card.js
```
show original
custom-weather-card.js
/**
* Custom Weather Card for Home Assistant
*
* Uses a weather entity for forecast data but overrides the current
* condition text and icon using separate sensors.
*/
class CustomWeatherCard extends HTMLElement {
// Define card configuration properties
static getConfigElement() {show original
2 Likes
Yesterday my radar image using the environment canada integration stopped working. Specifically, camera.toronto_radar just shows black where the radar image should be. When I try to reload it, I get the message:
This entity is no longer being provided by the environment_canada integration. If the entity is no longer in use, delete it in settings.
Does anyone else have this issue?
1 Like
