I think this is a fantastic idea and should be included in the standard config so we can stop (or reduce) the flood of “you broke me HA, now the dog can’t turn on the nightlight” posts with every release.
I do want to report something though, mine reports
Is it getting the information directly from Issues (marked with appropriate tags) in Home Assistant’s GitHub repo?
How far does it look ahead? There are examples of upgrades on this forum by users who, in one step, have jumped 6 or more versions.
I agree this should be incorporated into the standard release. Users who don’t read Releases Notes, and skip 6 versions, aren’t likely to install a custom component.
In fact, for maximum visibility and minimal effort (no component or sensors to configure), this functionality should be accessible from Home Assistant’s Info page (or a related administrative page). One glance at that page and you get an idea of how many ‘breaking changes’ there are between the version you’re using and the latest one.
I’ve double checked my configuration.yaml and I don’t have either of those components included. unless my google calendar entries are being picked up as google_assistant?
are those some sort of a default config entry (and I don’t use “default_config:” or whatever the new entry is) or where else does the component look for installed components?
For the time being I will not do this, it will require a lot more testing, and I’m not sure that this is something that have a place as a core component, you can fully use it as a custom_component, there is nothing different about how it would work.
Currently it only look for the current stable version, for multiple reasons, the biggest one I did this in 1hour last night, but I plan on adding support to list changes between your installed version and the latest stable version.
Maybe someone will see this and implement that
@finityI just published version 0.0.4 of this that should fix that issue.
Looks really interesting. Would the provided information be different from the Hassio Check Home Assistant Configuration add-on, or is the main advantage in comparison (if you’re a Hassio user) simply that the info is available as a sensor?
You are comparing apples and skateboards here.
That addon checks your configuration to make sure it’s valid, this component gives you a list of potential problems.
I believe that there is room for both, and if you are running hassio you should not do an update without running that addon.
This component would be useful to include in notifications and potentially a custom lovelace card
Apparently iliad_italy is a platform that was removed by this PR: 22175 due to stability problems. My guess it’s being reported as a breaking change (even if you never used it) because it’s tagged under the (very broad) heading of ‘homeassistant’.
On GitHub, the Issue was tagged correctly and does indicate remove-platform and integration: iliad_italy.
However, this level of detail isn’t revealed at the level of the Breaking Changes list for 0.91. You have to dive into the associated PR and read its tags. I don’t imagine it would be easy to do this with web-scraping.
Correct, and it’s me that does that tagging.
It is returned by my scraper as None. if it returns None for a breaking_cahnge I assume it is something that changed in homeassistant (they are usually not tagged to a specific integration.
The alternative would be to hide all this, but then stuff like the slugify change we saw a couple of releases back that changed a lot of entity_ids also be hidden.
I believe that this is an acceptable tradeoff.
The default name of the sensors are “Potential breaking changes” so I’m covered there at least
It could work but I don’t see that as a valuable option.
Config changes require restarts, starting with 0.1.0 of this component if will only show things if there is a newer version published.
So adding / using an option like that would be too much work on the user.
