tell me about it. I am stack from the morning and now I am looking for a way to reinstall HA and I don’t know how 
I just had an epiphany…
We are all thinking that the “Make It Easy™” concept was to make it easy for users when all along it was to meant to make it easy for the dev’s.
Now it makes perfect sense! 
I keed, I keed…or not… 
1 Like
The same I said 12 days ago.
1 Like
Of course.
Always late on the uptake…
What is amazing is how Home complicated Home Assistant is. It has over 1500 integrations, lots of custom components, and many systems that it will run on. The more you use it the more you find out what you don’t know. I appreciate all the effort that the developers are doing. Making it easier for development is a good thing. It is a long way from being easy for non technical users.
I think it fits here.
1 Like
That’s what I suspect…take away all the customisability (not UI configurable) is the road they are on.
1 Like
Your “more” example is another user using a custom component. Those components aren’t supported by the HA devs or the core system so their behaviour can’t be guaranteed. All of your examples so far have been people doing unsupported things and then having stuff break.
Can you find an example where someone wasn’t using a custom component?
1 Like
9 or so posts up:
There’s no indication that user wasn’t using a custom component nor does the user indicate which component they were using. It’s hard to say whether or not it was a supported integration.
That actually is the point, if it’s “impossible” with a supported integration the the discussion is moot.
Custom components are an essential adjunct to home assistant. Many users have one or more custom components. The whole HACS system encourages installation of custom components. HACS is developed by ludeeus who is a major contributor to HA core (59th largest number of commits to core github out of 1906 contributors).
thomasloven is the 9th highest contributor to home assistant frontend and the 9th highest to hacs/integration.
Custom components are risky, but are hardly a no no.
If this is an attempt to squeeze them out, it is a strange way of going about it.
1 Like
Hahahaha. I have seen one example of a user on this forum asking why his system started in the new safe mode. Every other time the frontend simply fails to start. It is far from “impossible”.
1 Like
No one is saying they are being squeezed out but you have to know that when you go the custom route your system becomes unsupportable. The dev’s first response to any issue will be “remove the custom components and try again” because they are totally untested and have no QA with HA.
This is typical of all software. Once you go custom your far more likely to have issues and far less likely to be supportable.
Granted, but if it is yaml configurable, it is simply a comment out. How do you comment out a ui configurable custom component?
3 Likes
Which is precisely what we’re saying.
WHAT IS THE OFFICIAL WAY TO REMOVE IT WHEN ONE CANNOT ACCESS THE FRONTEND?
4 Likes
Same as it’s always been? Remove/move the directory in custom_components.
How to do that?
The ssh addon is now considered to be only for ‘advanced’ users, it cannot be installed by default. The ‘target audience’ will not have any methods to do this.
Using the samba addon then.
Clearly if they’ve installed the custom component they have access to the file system in some way, shape or form.
How to install the samba addon? I can’t get in to the UI.
I installed hacs by drag and drop in the UI using [insert name of UI based file manager addon like vsc or cloud 9] so the only way I can remove it is through the UI but now I can’t see a UI.