Just a month ago in a blog post it was said: “The Open Home is about privacy, choice and durability.”
But people who care about privacy and don’t send usage statistics will just see integrations critical to them being removed… Choices being taken away from them and making things stop working (even though you said durability means things should keep working for the next decade…)
btw, links for “Diagnostics” and “HomeWizard Energy” are broken.
See… again…
Read the posts again. it’s not about the usage.
And dropping a integration that has nobody maintaining it means it has potential to work the next decade.
Keeping an integration that could fail and nobody can repair it would be the opposite, don’t you think?
so, if I have an integration currently RPI_GPIO I will need to reinstall the integration via HACS?
Also, I am yet to move my legacy Google Apps For My Domain/Workspaces account over to the new system they’re coming up with, so I cannot currently “upgrade” nest to the new Nest system. So, for now I lose access to my next devices in HA?
This is not exclusive to paid software. I’m coming from HomeSeer, with much of it’s functionality in large part made up of Plug-In’s by individual developers. There is a loooong list of dead plug-ins, with NO alternatives.
My question, as I’m new here. Are there any public announcement (not dev groups) made from those in leadership on integrations that are no longer maintained and are being considered for removal?
Raspberry pi is not just about GPIO you know. If you are that concerned you could have offered support.
Not just but about.
I am more than happy to help within my capabilities! Taking over as a maintainer might not be within them. Clearly I have to figure out a way around the consequences. The solutions presented in the deprecation thread don’t seem to be a solution but I will look into them (forcedly) Removal of GPIO support - #85 by parautenbach
Nevertheless this represents seems to me like a crippling in stark contrast to the self-described ideals as has been pointed out by other posters in the thread.
PS: I have earned the Welcome badge in the forum during this thread. Never ever have I felt less welcome… 
No, you probably need to keep an eye on the githuba rchitecture repo. See (in this case) https://github.com/home-assistant/architecture/discussions/596
If you have really read the whole thread you will see rpi gpio survives via hacs.
Yes, I really have read the thread, thanks for the friendly tone.
As you probably know HACS requires a Github account and I personally prefer a rather clean streamlined setup. It might be ok for users who love to tinker and toy with bleeding edge features. But for me personally this is less from desirable.
Every possible solution requires additional hardware and/or additional layers of software dependencies with much added complexity.
For other unfortunate GPIO users: HACS, remote GPIO, ESPHome, MQTT-IO
I understand that this is the way to go and I have to accept this way. Nevertheless my enthusiasm for this project has found a sudden end. My bad that I went all in to this platform.
HACS is just the easy way to install it. You can still install it manually without HACS.
Just follow the manual install instruction here to install the original rpi_gpio as a custom integration, no need for HACS if you dont want it
thecode/ha-rpi_gpio: Home Assistant Raspberry Pi GPIO Integration (github.com)
It would have been nice if at least the removal of GPIO was announced in advance. Like a depreciation warning, as is common in other breaking changes.
Edit: let me apologize, this is exactly what’s happening, it will be removed in 4 months. Apologies for my mistake.
It has been marked as deprecated and will be removed in 2022.6
From release notyes breaking changes
As of this release, all integrations interfacing with GPIO directly, have been deprecated.
and
The following integration have been deprecated and will be removed in Home Assistant Core 2022.6:
so thats 4 months for people to get alternatives in place.
Welcome to the forums, Salog! If you are willing to stay, you will find that the vast majority of forum members adhere to netiquette and will treat you in a factual, friendly and helpful manner. 
It is announced in advance… it’s being deprecated in 4 months.
I just want to add that the whole promise of HA is private, local home automation. By its very nature this project will attract those who are turned off by cloud based solutions and all of the privacy breaching telemetry they entail. Hopefully the devs take that into account before making decisions based on metrics.
I for one have the analytics turn off in HA, and I even go a step or two further and block telemetry from other systems at the router. I also found this to be an effective solution to Microsoft’s forced feeding of updates at the most inconvenient time. You should see my firewall logs…
But hey this gpio fight isn’t mine. I don’t run HA on a pi, not powerful enough.
Carry on.
First of all, many thanks to the developer(s) who stepped forward to support rpi_gpio as a community add-on!!
A couple of points that are being missed or dismissed:
This change is hitting a nerve for many people because it’s fundamentally opposed to the stated philosophy of HA, and the reasons many of us chose this system. From the HA blog:
Durability
If there is one thing that technology firms are very good at, it is launching new products. However, maintaining the products and making sure they keep working is an afterthought for most. The result is that vendors can decide to no longer support your device, crippling it’s features or even prevent it from working at all.
As we install more and more devices in our home, durability is becoming more and more important. We shouldn’t have to buy everything new every couple of years because the manufacturer decided to move on.
Durability for the Open Home means that devices are designed and built to keep working. Not just this year, but for the next decade.
I think that sums up the way most rpi_gpio users feel. Maintaining this core functionality is being treated like an afterthought.
I know some folks are trying to help by recommending alternatives. But asking users to re-configure their systems using new hardware and software isn’t helpful. Personally, I love ESPHome and am looking forward to using it for more applications. But duplicating the existing GPIO pins on my existing RPi that’s already running HA, adding dependencies on additional hardware, power supplies and WiFi infrastructure, is not a reasonable solution.
Finally, I keep reading that only 1,100 installs use the rpi_gpio platform. I’ve also read that this is not the real justification for the change. Yet it keeps being thrown back at us rpi_gpio users. So I felt it important to point out that only a fraction of HA users share statistics, so the number is actually several times higher.
But with the same logic the number of total installs is also several times higher.
The analytics is the best we got, unless you create a poll and make sure every user answers it.
There are going to be bumps in the road in all software. Things change. That’s the nature of life and you have to adapt.
If you’re unwilling to adapt, then who’s fault is that?
rpi_gpio users have 4 months to prepare. They have multiple options, some free, some not, some that require new software, some that require new hardware, and some that just require you to copy and paste files. This is 100% being overblown as there are FREE simple fixes to this problem that only require 5 minutes of work… in 4 months time.
My point was that this number keeps being thrown at us rpi_gpio users to justify dismissing our concerns as insignificant. Then when we answer, we’re told that’s not really the reason for the change anyway.
Logic would dictate that we need to either admit that the needs of thousands of users are being dismissed as unimportant, or to stop using that statistic as a supporting argument in the first place. I recommend the latter.