I don’t believe update notifications are pushed to users. HA checks a url and works out if it needs to update.
Perhaps though an infrastructure where HA checks for messages about the integrations it is running.
1 Like
ahh, yeah, you’re probably right.
Perhaps integrations could check for updates in the same way as HA updates and add-on store items do?
1 Like
Speaking of which, this deprecation should be there surely?
1 Like
Regarding some comments on my previous post, I did get two custom components working in my system soon after I read the release notes to prepare for the removal of the integrations. For the GPIO I saw that a developer made one available before I worked on mine (thanks so much to @thecode for the quick solution for the community!!), it required some tweaks, and for the DHT sensor it was pretty much straightforward, just need to include a version number.
My fear, I insist, are the libraries needed for them to work. For example, RPi.GPIO for both GPIO and DHT integrations, and adafruit-circuitpython-dht and libgpiod for DHT. This last one required a pretty recent change in the dockerfile before it was functional. Right now the custom components work just fine, but if someone decides to clean up libraries that are from deprecated integrations, we’ll definitely lose the possibility to use them. Hopefully the developers will keep them in for the users that still rely on GPIOs for their home automation solutions (in my case all types of sensors and switches), Raspberry Pi fans, HATs, etc.
Thanks so much @thecode!!!
I haven’t worked with HACS, but I think it would be useful to other users out there to include also a custom integration for DHT sensors, picking up your offer for the community 
I have a DHT sensor and put in place a local custom integration, just requires the inclusion of a version number in the current code for the integration. If I can help out please let me know.
You know those libraries are managed by other people right? You can’t just take someone else’s project on pypi
Custom integrations can bring in libraries, whether or not those pypi libraries are in core.
Looks like it might be in the (long) wings https://github.com/home-assistant/alerts.home-assistant.io/issues/8
1 Like
Might post a nudge in that thread
didn’t they try this a couple of years back with state of nation, security issue or something notification that was in the config page and people complained about it, said they would rather opt in to be notified
I dont think there is an easy way that would be acceptable to all
Yeah, I seem to remember that. I guess opting in to analytics is enough though.
They shouldn’t and they probably won’t. The answer is that the requirements in the new custom integrations manifest must specify it (it contains the GPIO lib as it stands).
Nobody stepped up early….but is the universe of people “ in the know” big enough? I honestly wonder if it is .
If you want to prevent this from happening in the future it is on the HA team to communicate differently. The community will always react negatively, you are right….but you guys can manage the response and minimize the noise. That is a choice the team has made.
I suggest a maybe monthly mid-month “Development Corner” blog post where you could percolate these kinds of discussions to the top visibility with lots of lead time. People would love to see some early ideas on what is potential future work. It would also reduce some of the size of the current release notes.
My advice is to listen to the community on this. Look at the way it responds and try a different way to engage it with these big things. If you stay the same, I promise you this will happen again and again. If you guys are OK with the community blowing every once in a while, by all means ignore me and everyone else. I don’t think that is what you want though…… I wouldn’t.
Thanks for the best home automation system available and your great support and attention to everyone. It doesn’t go unappreciated even though people are disgruntled. You are doing an admirable job responding here and I applaud you for doing it. Like I said earlier….you guys are really awesome, and you go above and beyond.
3 Likes
How early would be early enough? Is 4 months not enough (counting from the release notes, not the earlier indications)? Who decides that? Isn’t this highly subjective? And someone did step up. Many of the people reacting negatively to the announcement don’t even understand the difference between depreciation and removal. It’s hard to have a conversation if the basics are misunderstood. This is where a lot of the noise you’re referring to comes from.
The only way to have shorter release notes is to make smaller releases. It is simply a best practice to detail all changes for a release. There are no substitutes for this.
And remembering this is two months worth of development.
It could have been organized differently perhaps.
Not sure how though.
But another option is perhaps to use those my link things, and have them match the breaking changes to list what is important to you.
That would actually be a nice feature.
Not sure it’s even possible though.
Yeah maybe we should use facebook instead of newspapers, youtube instead of the 6pm new hour and tiktok instead of novels.
People should read the release note. Full stop. If you don’t have time to read them upon release, then you don’t have time to upgrade, because the release notes are an integral part of upgrading.
7 Likes
Yes it was. But the reason of such response was bad implementation of the warning. Mainly because it was sent to all users instead of admins only. Secondly there was no option to dismiss the message, it was coming again and again (if I remember correctly)
This fiasco shouldn’t be taken as argument supporting lack of communication quality.
1 Like