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.
1 Like
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.
Thank you vey much. 
Thanks for your work.
Hey folks, here is a status update on the state of the Environment Canada integration.
A PR was just merged and will show up in 2022.3 that is a breaking change. Simple summary is that alerts have changed format and a timestamp sensor was added. I’ll let you read the PR notes and ask questions from there. Add SensorEntityClass support for Environment Canada integration by gwww · Pull Request #58615 · home-assistant/core · GitHub.
Also in the same PR is converting the sensors to SensorEntityClass. This is not a breaking change. It does add the functionality that many of the sensors can be tracked in history. Look here Add SensorEntityClass support for Environment Canada integration by gwww · Pull Request #58615 · home-assistant/core · GitHub for sensors described with StateClassEntity.MEASUREMENT for those that record history.
Upcoming changes… this PR Use _attr_ and add radar_type service for Environment Canada by gwww · Pull Request #58657 · home-assistant/core · GitHub needs some rework. Its around selecting the radar type. Even though the PR is there, it is lower priority than the next item below.
Higher priority is to add back AQHI. PR to be written but is reasonably trivial. This PR was waiting for the sensor PR at the top of this note. I expect to submit that in the next couple of days.
One last note which we have not talked about recently. Radar entities were overwhelming the Environment Canada servers. We add a patch in early December to cache as many of the radar images as we could. This results in a 92% reduction in requests to the EC servers. Yeah!
Two requests to this group. If you are not using radar, please disable it in your configuration. If you are, really really, using radar, please make sure that you are running at least 2021.12 release of HA where the caching is turned on.
1 Like
Thanks for all your hard work!
1 Like
Great work with the caching functionality! Not only does it make life easier for EC’s servers and IT crew, but it’s significantly improved the load times of my dash.
1 Like
Hi everyone! a fellow Canadian here with a question that is burning me: I’m trying to use this simple template {{ states("sensor.warnings") }} but it returns “” (empty string)… if I check the history, I can see that the current state is:
Can anyone help me out to understand why I get “” (empty string) instead of “Extreme Cold Warning”? If I access this entity using python_scripts, I do get the correct value!!!
Hello, my camera displays nothing with the default integration parameters and with only the station ID. The color scale is displayed, but no satellite image. But you are right, the camera works fine when I also set the lat/lon coordinates.
Thank’s for your work, my Rhasspy voice system now tells me in french, the temperatures and "les previsions meteo !
The following does not explain your problem but here is config works and will work after a bug fix that might show in the March release.
Right now if station and coordinates are specified then station is used for weather and coordinates are used for radar. If only station is specified then coordinates from the station are used. If only coordinates are specified they are used for radar and to find the closest station for weather.
In the future the current plan is if both station and coordinates are specified then station will be used for weather (same as now) and the station’s coordinates will be used for radar (instead of what was in in the config screen). This is proposed. Feedback appreciated! There is no change if only one of station or coordinates are specified.
Regardless of where we end up, this would be a good update to the docs.
As to the mostly blank radar, that usually occurs when Environment Canada doesn’t return radar data. It could be there is no radar data for the coordinates.
Hello and thanks for your answer, personnally I found out why my satellite map was not working by reading the forum and your comment about it. Since I could not find any documentation about it, I guess an easy fix would simply be to add a comment in the initial configuration section that station ID is required for weather and lon/lat are required for radar data. If there was a reason you kept these two separated to start with, I would say this a minor change… Of course if you impose/request to add in both station ID and coordinates at initial configuration time, as I understand what you propose, then you would achieved the same result. Bye and have fun ! jrb.
Thanks for your reply… Something funny was going on with my HASS instance… after reading your response I checked again and had the same issue… power cycled the server (using HassOS) and then it worked… cheers!
Hey folks, a couple more updates and a reminder on the request we asked of the group. Let me start with the request.
If you are not using radar please disable the entity. This will reduce the load on the Environment Canada servers. Thanks!
On to the updates…
AQHI is added back in and works as expected.
Radar being down will no longer block weather!
Both of those should show up in the March release.
What is left is to figure out the best approach to be able to switch radar between snow/rain and there is a small inconvenience (bug?) with the config flow where it will use the station for weather and the coordinates for AQHI and radar. It most notable when the station and the coordinates are not the same place and causes the possibility of getting a duplicate entity.
Both the above are low priority.
Thanks for the work that went into this integration. I’m trying to set up some automations to notify us when weather alerts come up, but would like to be able to react based on the severity of the weather event (Tornado Warning vs Rainfall Warning). Can anyone point me to a list of the advisories, warnings, watches, and statements that EC uses in their messaging?
I hadn’t looked for this info before, but I believe that this is the list of alert types:
However, I wouldn’t recommend relying on Home Assistant for life-threatening alerts like tornado warnings. For that I would recommend push notifications via the WeatherCAN app:
2 Likes
Thank you for the link. I do have the WeatherCAN app installed, and I have a weather radio, this will be another layer for notifications. I want to try using HA to flash some lights to draw attention to a new alert. I’ve found that I can’t rely on the weather radio, the reception from our local transmitter has dropped off and I no longer receive weekly tests or alerts. Several years ago we did have a tornado warning in our area… we received thunderstorm warnings before and after the tornado warning via weather radio, but did not receive a tornado warning. I lost some faith in the weather radio service after that.
1 Like
You wouldn’t happen to have a handy link to a list of the weather icon values would you? I see the mapping in but I can’t find a list of what the icon numbers represent.