basically everything in home assistant is an integration
I see what you mean, thank you. For example, I’ve been looking into the Statistics integration, and it appears to be part of the core; it’s not listed on the integrations page, and I don’t see any way to install or un-install it. But it is called an “integration.”
So it looks like checking just the handful I have on my Integrations page won’t identify known bugs on all the other integrations which don’t show up there. Is there any place I can look for those?
I’m sorry if I’m not understanding something. I looked at the page listing integrations and Statistics isn’t listed. If, as you say, everything in HA is an integration, presumably there are a lot more which are part of the core and not listed there.
Is there a list of all of them, which I could scroll down through looking for any that might apply to me? Then I could click each one, go to that integration’s page, and look for known issues. Still a bit of a chore but it would be well worth the effort. Far better than updating blind, not knowing I’m installing known bugs.
1 Like
Sorry, I’m trying to explain but not getting through.
How would I search for things I don’t even know exist?
Use the search bar or google, how would you find anything you don’t know the name of? You used statistics as an example and I showed you an image where I only filled in 5 letters of statistics and that page filtered to my search. So I’m generally curious how you wouldn’t be able to find what you’re looking for. Worse case is that you don’t know the word, and then you’d use a more powerful search engine… google.
and for google to restrict to HA’s website…
1 Like
It is very worthwhile reading thru the whole utility section, many are extremely useful and not obvious.
Integrations - Home Assistant
2 Likes
My point exactly.
I’ll just go on the assumption that the answer to my original question is no, there is no way to scan a list of all known bugs to see which might affect my installation.
1 Like
I guess we just went around in a circle here. If all you’re asking about was about the integration page inside your own home assistant (not the website), then no it’s not possible. The integrations, devices, entities, and areas page only shows things that can be added through the UI.
1 Like
Go to configuration|info and all your integrations are listed, with issues and docs.
3 Likes
Would ya look at that. TIL. Thanks
1 Like
Well, if it’s broken, that’s certainly a bug, I would say. Doesn’t contradict my statement as far as I can see…
Couldn’t agree more with everything you said. I can’t even think of a refactoring which couldn’t wait for (at most) 4 weeks.
1 Like
With the wide variety of vendors supported it would not be unexpected to have at least one breaking change every 2 months. That means the release cycle cannot be longer than that and maintain stable functionality with all devices.
If you really want a longer release cycle, look at openHAB. Believe me, you will be back here like I did.
2 Likes
Ah, ok - no, that’s not at all what I mean! I’m absolutely fine with a release every month (and I appreciate the pace of development) - my main point is that there should be no new features or unnecessary dependency version bumps (let alone refactorings) between releases at all, only bug fixes. Thus, the last dot version of every month should be the most stable, and offer a reasonably safe way to update your system every month. The “long term support” version was an additional suggestion but might indeed be unrealistic…
That is exactly what I did. I just upgraded to 2021.12.x.
Nice, thanks!! We’re getting closer! I see about 75 integrations listed, so clicking on “issues” for each one will be a chore. But again, better than restoring to backup when something I need breaks. I’d still like to see just a list of current known bugs, by integration, but that may be asking too much with so many integrations by so many different developers.
I appreciate you taking the time to figure out what I was actually asking, and coming up with the next best thing!
I’m not sure how they would know if there was an “unintentional” breaking change that was introduced before the release can be fully tested after it has been fully released.
All of the known issues (“bugs”) prior to the release are likely not affecting you or you would have already known about them before updating because something in your system wouldn’t be working. So those shouldn’t affect your decision to update at all. At least in my mind it shouldn’t.
Unless there are new bugs introduced in the beta prior to the full release that you are referring to?
I would hope that those would be either fixed prior to release, changes rolled back so there is no new issue introduced in the release or at a minimum that there are noted as a breaking change in the release notes so that others know about them before hand. But that last option doesn’t sound optimal tho.
TBH, I have no idea what the policy is for releasing an update with known new bugs in it. I hope that wouldn’t be happening tho.
Agreed. My point was that new users (like myself) might not understand that “breaking changes” doesn’t mean the same as “known bugs.” Breaking changes are intentional changes which require the user to adjust something (usually for the better) or things will break. Bugs are changes with unintended negative consequences. They’re not discovered until people start testing or using the changed code.
Both are good to know before starting an upgrade. The first one is easy; we have a Breaking Changes document. But there is no one place to go for a list of known bugs. @nickrout’s suggestion is the best I’ve seen so far.