… and anyway the original comment is pointless as:
EDIT: As for the removal of --daemonize if you’re using Core, just create a SystemD/SystemV script, like for any long-running process.
Sure a lot of people could have different points of view. I mean that docker changed pricing mode is a big cons from my point of view.
The main issue is removed --deamon and --pid-file from hass.
How is that an issue? Most of the daemons rely on SystemD / SystemV.
If for whatever reason you don’t want a service, nohup is your friend.
Removal is of GPIO support is just crazy! This seems so out of touch with the user base!
As a recent user using Homeassistant just since 2021.09 coming from other home automation solutions I fell in love with Homeassistant pretty quickly. I am running Hass.io on multiple Raspberry Pis (recently purchased at big price bumps just for Homeassistant, thanks for that!) and where more than happy with it. The huge range of supported integrations and the good community are such a delight. Guess the honeymoon is over…
How comes Homeassistant is recommended to be run on RaspberryPi if there will be NO support for what makes the Raspberry Pi stand out compared to other devices.
Your suggested solutions might work out in some edge cases. I myself use ESPHome, however that is NOT a “fits-all” replacement for GPIO support.
Wow, such statements are very sobering. I don’t share my statistics straight away. I try to participate in the forums. Should I be scared now about my other integrations that have even less recorded installations? What percentage will be deemed unworthy in the future?
I have been using RPI’s since RPI1.
Never used their GPIO’s, ever…
As been said many times before.
When there is no active maintainer, that is when you need to be “scared”.
It’s not about the percentage. But had there been 50%, most likely there would have been more developers on that particular integration also.
It is interesting to see how the statistics of 1100 users or 0.8% who are affected by GPIO removal are still being written, and at the same time this thread is 90% discussing GPIO. Here you can see how treacherous statistics are.
It can also be seen that this decision to remove GPIO has completely overshadowed developers’ efforts, seamless updates, new integrations, enhancements, and more.
Or… that the users of GPIO refuses to understand that it’s not a decision made based on the usage but based on the fact there is no developer wanting to maintain the integration.
And because the users of GPIO refuses to understand that, they keep posting the same thing over and over again in some hope that what they say is truth.
Well I wouldn’t be surprised if this was seen as a movement towards a semi-commercial, more closed system. Removal of GPIO, Nabu Casa price increase, roadmap of “simplification”, the official Tuya integration fiasco, the hardcoded DNS in HAOS… I don’t take issue with most of this but I can see these being seen as a movement towards more closed system.
Very unfortunate for the user then that this is NO way obvious if it is supported.
Then again nobody would expect a project recommending to use the RaspberryPi to remove a working GPIO integration would they?
I understand that unmaintained code is a problem, agree with you there. But seeing GPIO not as a vital element is clearly a misjudgment!
Especially when RaspberryPi is the recommended way of using Homeassistant…
Agree.
To some extent I would think that it could keep running the way it does and just left.
But then in say a year something does break it, then people want it fixed. And if nobody maintains it then it can’t be fixed.
I’m using home assistant for e few years now.
I think this thing of removing support for gpio is like the same thing a while ago ‘hey… lets just stop the supervised install method stuff’
I think it’s stupid and wondering who makes those decision(s)? The way this is done is the thing i disliked the most of hass
Besides that… im not sharing my analytical stuff… so i’m not in the list of people who are using GPIO. So in other words. That list of num of people is a lot longer i think 
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