Environment Canada integration stopped working

As of two days ago (approximately), my Environment Canada integration stopped working. All entities are unavailable, except AQHI, oddly.

Deleted it and tried to recreate it but auto-discovery fails and no matter what station ID I enter, it comes back not found in the database.

I’m guessing something changed or is broken at the Environment Canada end.

1 Like

Yes, Environment Canada changed their data structure on the 25th. This has been patched; upgrade to 2025.6.0 or later.

Are the station codes still working?
I’m currently running 2025.6.0, upgrading to 2025.7.0 and it is still not reading any data from Environment Canada for station s0000054

I upgraded to 2025.6.0 and it’s working for me. I’m using station ON/s0000430.

I tested s0000054 in 2025.7.0 and it loaded up Victoriaville correctly.

I just wanted to report as of today/yesterday, it seems like it stopped working again. I tried to remove the integration and re-add it but keep getting this error. Clear browser cache and all.

image

I am on Ha 2025.10.1
image

The link https://dd.weather.gc.ca/citypage_weather/docs/site_list_towns_en.csv is giving me a 404 error.

Try this:

https://dd.weather.gc.ca/today/citypage_weather/siteList.xml

No luck. The same error shows up… Last time it was able to automatically select the closest station.

According to the screenshot you posted, the Weather Station ID field expects a two-letter provincial abbreviation followed by the station ID.

For example:

ON/s0000585

However, I tried it, as well as a station ID in another province, and it failed to work. It suggests something has changed on Environment Canada’s side and now the integration’s configurator is no longer able to correctly validate the station ID.

FWIW, someone has reported the problem in the Core repository:

All of my entities related to the EnviroCan integration are also reporting unavailable.


EDIT

I just looked at EnviroCan’s site and it appears that they have “rearranged the furniture” again. The required data files are now located in new directories. The integration’s code will need to be modified.

This will be fixed in 2025.10.2

1 Like

For those having this problem, looking at the commit, it is a very simple one line fix which is very easy to manually change by going into the homeassistant docker container and editing the manifest.json file. Will get you working again until the next release comes out with the fix. I don’t have the home assistant OS set up, but I imagine it would be even simpler there.

In the docker container, the file is /usr/src/homeassistant/homeassistant/components/environment_canada/manifest.json

and you just need to bump up the version number to 0.11.3 in the requirments line:

“requirements”: [“env-canada==0.11.3”]

Then restart HA. After the next refresh cycle (may take a few seconds) data will start showing up again.

1 Like

I don’t think many users know how to do that. Would you be willing to provide instructions?


FWIW, I use Home Assistant Supervised and have already made the suggested change. The modification itself is trivial but the steps required to perform it would not be obvious to a first-time user.

I am running HA on a Pi and can’t get to the /usr/src/homeassistant/… directory to edit it (not even with terminal) … will need to wait for 2025.10.2.

thanks for continuing to support this

For Home Assistant OS, Home Assistant Container, and Home Assistant Supervised, the directory exists inside a docker container. You have to “enter” the homeassistant container to get to the aforementioned directory. Whatever terminal program you use must first have access to the homeassistant container.

tl;dr
Some knowledge of docker is required to implement rbm42’s suggestion.

2025.10.2 is now available

if you don’t see it, try going to Settings - System - Updates and click on the circular arrow in the top right. The update should then appear

@RobLatour
For future reference, there are two reply icons in a topic. One in a person’s post and one at the bottom of the topic.

  • The one in the person’s post replies directly to them and they receive a notification.

  • The one at the bottom of the topic doesn’t reply to any specific person. No one receives a notification unless they are subscribed to the topic.

I am not subscribed to this topic so I don’t get notifications unless someone replies directly to me. I was notified by both of your replies so it means you chose the wrong reply icon.

Hi, I still have the same issue. The PP/xxx format does not work. I have normally the version 0.12.1 of the integration now, as we are after october 15, 2025. I have also tried to install the integration code under the “homeassistant/components/” in my docker home assistant installation. When I’m logging in this container with the ssh integration, the /usr/src/homeassistant/xxxxxx" does not exist. The URL that I see on the web gui when I try to install the “environnement canada” plugin is still incorrect. However, I found the right url in this thread. All of this to say that I’am wondering what is the version that HA tries to pull when I’am trying to install this integration. I have to say that according to the “about” menu I still have core version 2025.8.3 with the following details:

  • Home Assistant OS
  • Core 2025.8.3
  • Supervisor 2025.08.3
  • Operating System 11.5
  • user interface 20250811.1

, so this issue may come from this. Is there a delay when HAOS receive an update and the HA version on github? However, when I try to update HAOS it does not show up any new update. “ha refresh-updates” is blocked.

Thank you.

OD

It definitely won’t work with any version older than 2025.10.2.

This topic is about the Environment Canada integration, not about the inability to upgrade Home Assistant. If you can’t upgrade it, report the problem in a separate topic or report it is an Issue in Home Assistant’s Core repository

I am also having trouble with HA 2025.10.3 most EC values are “UNKNOWN”
All worked well with 2025.10.2

Have you tried removing and re-adding the entry? If that doesn’t fix it, can you share more about your configuration?