well it doesn’t mean deprecated anyway.
1 Like
I suggest this scenario (whether for gpio or any future similar integration deprecation) would have been much better handled in this way:
If the devs had made a blog post saying “we are forced into a position that we’ll have to remove GPIO because it has no maintainer, step up or it’ll go in 4 months.” Low and behold, @thecode steps up, problem averted.
So devs, how about a slightly friendlier approach. It’s pretty hard to keep up with github, discord, discourse etc, but a blogged list of what needs attention or maintenance may reduce your load and improve the process.
9 Likes
This is the first I’ve seen of this “list” of declarations, and I consider myself to be a pretty active user. Perhaps if more people knew about this list, this particular brouhaha could have been avoided. Clearly there was some thought that went into this decision, and whether everyone agrees that the thinking is sound or just a formalized justification of “it’s too much trouble” can be debated ad nauseum, but it is what it is. If this had been published when the decision was being made, perhaps as @nickrout suggests below, then people who rely on this functionality would not be finding out about it in a major release. Who knows, perhaps even one enterprising soul would have a unique solution, or could take over development, or add a new component, etc.
It’s not about users having a “vote”, it’s about being considered as a partner in something we’re all striving toward, together. To put it bluntly, if it weren’t for users, HA developers would be wasting a whole lot for their time for NOTHING. Clearly, those who started this movement wanted something bigger, whether fame, fortune, or to do something that’s never been done before. Either way, a robust, happy., and enthusiastic user base is paramount to that success; otherwise, you’re just sitting on another dead-end branch of unused code. And there is a whole lot of that in the world.
Also, isn’t it a bit dangerous to rely too heavily on the stats of who uses what (ref: 0.8%) when making these decisions, knowing that not everyone reports usage? For example, who uses EVERY integration in the default list? I can attest that there are some in that list that I DON’T use, ever, like TTS. So those integrations are clearly over reported.
3 Likes
It was published when the decision was made… Just because you don’t partake in github doesn’t mean it wasn’t announced.
And before you get more upset, here’s a link to all the discussions anyone can take part in…
If it seems like I’m frustrated, I am. I’ve linked this about 90039409234902394 times and no one takes part and then comes here to complain.
Maybe not precisely when the decision was being made but there was over a month’s worth of advance notice right here in the forum.
There was the one posted in December (link in Petro’s post, a few posts ago) and then I posted a heads-up on January 5th when the PR was being processed (i.e. the official deprecation announcement was very imminent).
The December thread identified alternatives in the form MQTT IO and converting the official integration into a custom integration.
So to answer your comment, it was done and done yet the outcome was still the same (a tidal wave of misplaced outrage).
Also, affected users still have several months before the integration is actually removed so there’s plenty of time to make transition plans.
1 Like
Can we stop with using the stats, the decision was not solely on that. Does the lack of a maintainer not ring any alarm bells in your head, especially with some people the case of the rp_gpio using it for their security systems.
I must admit I missed that. Thanks for your community spirit.
1 Like
Well, that’s not very fair. They could have, if they had known about it before reading it in release notes. Plus, not everybody codes, and a large majority of users would have no idea how to go about doing so. I’ve been coding since 1981 and I still haven’t sorted out how all the pieces of HA fit together.
I suggest we compare this 4 month deprecation period for these 0.8% of unlucky users to the deprecation period of OZW 1.4, which has been going on for what, 16-18 months now? Why is that? Because people are still using OZW, even though it is hasn’t been maintained in over a year? Some Devs here are quick to criticize and dismiss any user hear who expresses concern about functionality they rely on being removed as “complainers”, or told they should be just shut up and “be thankful for what they are getting for free”. Nobody is forcing Devs to develop their SW for free. That attitude sucks and is in direct opposition of what I believe the HA community is trying to achieve.
And I would submit that anyone who isn’t expressing concern either hasn’t been impacted (yet) by some loss of functionality, or they have the know-how to quickly adjust.
3 Likes
I really thought that post would get more attention but tom_I quickly pointed out another one predated it (by 2-3 weeks) so I figured all the people that needed to know were already in the other thread and discussing alternatives.
I guess I was wrong about how people had seen either thread … 
And there’s still more time between now and when it actually becomes deprecated removed, than there is between those discussions and today.
It would take 20 minutes at the most to move this to the custom_components directory and make a file and be done.
3 Likes
No it is already deprecated, there is however 4 months before it is removed.
And I can imagine what outrage and the wave will be when it is removed for users who do not go to this forum and use GPIO 
1 Like
I just want to ask because I can’t find the information.
If GPIO is still working and I add my own GPIO integration with the same configuration in yaml, which will load after the HA restart first for the function? Maybe a stupid question
As has already been pointed out -
it was posted about IN THIS FORUM a month ago, and was largely missed by the majority of us. The only reason more people are aware of it now, is because it was in the release notes.
2 Likes
I’m genuinely surprised by the number of people capable of tinkering with GPIO and hardware on a RPi and for whom 300 lines of (mostly boilerplate) python code seems the Everest to climb…
Did they all start using GPIO with HA?
How did they do before?
1 Like
They don’t need to be part of this forum but they do need to read the Release Notes before upgrading, especially the Breaking Changes section. Anyone who does that now will learn they have several months to plan for a transition before the integration is removed.
Those who don’t read Release Notes might have an unpleasant surprise in the summer. It’ll be a hard way to learn that you must review the Release Notes before upgrading.
Anyone who doesn’t read release notes before upgrading or
1 Like
Yes, I also knew this information a long time ago, but maybe the problem is knowledge of English because with the help of the translator I understood that the integration of various sensors will be removed, but not my own approach to pi GPIO, so I didn’t pay more attention to it.
Could you help me a bit and weld these titanium parts together… it is just 10 min job… Yep, some stuff is easy for some.
And yes, I got into HA because I heard it could easily control rpi gpio…without python or any other snake that you call code 
Yes, I agree, but by knowing this before and, of course, the release notes, I was just desperately looking for a solution that I found and the situation is resolved.