I opened an issue on manual in core for fixes that are needed before HA 2025.01. After several months it was closed due to inactivity. Ignored and never commented on.
Why wouldn’t core team review and comment on a bug for core?
because it’s the most unprofessional policy I’ve ever saw: to let robot dismiss the report without letting devs even looking at it.
And they will argue that HA is changing so fast that after a while requests are invalid. What a BS.
I prolonged this timeout several times but seeing no interest I let it be.
I take it as disrespect to a user so I decided to never file an issue again.
1 Like
The devs are looking at the bug reports, but they are not always replying to them.
The bot is just closing thread because the devs do not have time for it. Often the issue will be fixed in one of the coming updates.
1 Like
yeah but the bot closes stalled issues after 30 days or so. So if devs have no time to fix it promptly they lost chance of fixing it ever.
I think they might have an internal list or other system, because it have always been like that with the bot and issues have still been fixed.
Thanks maxym and WallyR. Glad it’s not just me. I am hopeful it gets fixed as it’s deprecated approaches introduced by the HA evolution and will ultimately break a key integration - Alarm, that got me into HA in the first place.
I figured I was doing my part calling things out but I’m guessing based on ya’lls similar experience, it may not be needed for one reason or another….
There are no devs assigned to the issue because the integration has no code owner.
Indeed - good observation. So if there’s no code owner and it’s a core integration and it needs to get fix what happens? I presume at this stage when the drop dead dead comes it just becomes an unworkable feature and thus broken for the ~256 installations using it?
It seems to have fallen into some sort of black hole…
Some of those ~256 users could stand up and fix whatever issue there is and create a pull request. It’s open source after all
Also remember that when a feature/function gets deprecated in HA, then the solution/right way is usually already known, so it is not a bug hunt, but a rewrite that is required, which is much easier.
These flippant replies to just fix it are not helpful. Since I’m clearly who you’re talking to let’s be clear:
I’ve never pulled/modified/submitted anything to HA so huge learning curve
And yes I’ve looked at the developer stuff and it’s not a simple investment of time
There is no code owner
Again, with my ignorance, who would approve it and pull it into the build? Surely I can’t just mangle Core functionality and move it into the wild for everyone to suffer with?
It’s flagged as CORE.
Is there not a team of folks that protect and support the CORE code? (As pointed out in this case it seems not)
All of the above may be painfully obvious to you but to me it’s a bunch of questions and hurdles. I’m doing my part to point it out as a responsible user/reporter (or so I thought) since I’m not into modifying HA code… As we all agree, there isn’t anyone that really maintains this so unless I’m uninformed, it will break and I’ll move onto some other solution within the HA ecosystem.
I could make the changes if someone babysat me along the way and made sure I didn’t muck it up. But that’s not how HA/open source works - it’s the domain of wizards and guru’s, not casual fixer uppers…
I’m not saying YOU should stand up, but some of the ~256 users of the integration could. Some of them must have some skills to replace one constant with an other. (I actually think you could do it too with some guidance, the warning message states which constant should be replaced with what)
There’s actually a lot of code in Core that has once been developed and then been neglected. For instance the original developer of the Manual Alarm integration did it’s last commit to HA on Jan 15, 2016.
The payed developers of HA are maybe 10 people and I’m quite sure they don’t use all the integrations that are part of Core. That’s probably why no code owner is assigned to the integration.
The documentation of the integration also states:
“This integration is community maintained.
If you are a developer and would like to help, feel free to contribute!”
I’m not a user of the Manual Alarm integration, but if you need some guidance on how to make the required modifications I’m happy to give you directions.
Which version of HA Core are you using? Because it seems the mentioned constants are replaced on May 7, so should be part of 2024.6 I think
I’m on 2024.10.3. The break happened around that time and goes away 2025.1.
I agree the code fix is borderline trivial. It’s all the other minutia to fix it, test it, submit it and hope someone approves it…