Well, thanks anyway Petro. I do appreciate that the devs at least looked into this request. There appears to be a good deal of interest but their decision is fair enough. While I would want to get rid of the Nabu Casa elements personally, it is really not a big deal in the grand scheme of things. The devs have done a fantastic job with home assistant thus far and I would ultimately rather allow them to focus their time towards refining and growing home assistant rather than a minor issue. Cheers!
1 Like
It is sad the developers decided to not implement this very useful featureā¦
Months ago I removed the default_config and added everything (but what I didnāt want) from the manifest.
I am now confused about how to manually manage this as I just spent hours trying to figure out why my new nest cameras would not stream. Turns out I needed to add stream, the documentation says this is added by default_config yet is not in the manifest!..
So it is not as simple as just adding whatās on the manifest. Ok then add all that shows in the Default Config documentarion page? Maybe but then that page shows other stuff not in the manifest as well like backup, config and image, I didnāt have those either yet those 3 have always worked fineā¦ Weirdā¦
Can one of you guys pro not-implementing this please clarify the right way to manage it manually? Like, what is the right list of things that defaul_config adds and we should manually add?
1 Like
Just look at the source.
There are exactly 2 exceptions that are not in manifest - you did mention both.
A configurable default_config could be implemented as custom component. I donāt know why no one supporting this feature didnāt. Maybe the need just isnāt that high š¤·
And to add: you (@Lumute) can now submit a PR for each (the docs and the manifest) and contribute ā which is how open source works.
I could if I understood itā¦ That only explains a little bit further: why backup and stream are not in the manifestā¦ What about config and image?
Also why backup, config and image work fine when default_config is removed from configuration.yaml and they are not manually added either? Maybe they are added automatically as dependencies of something else? should I add them manually anyway to avoid future issues? No clueā¦
BTW, the solution proposed about adding a custom component stopped working for some reason after one of the 2022.4 updates, cloud is now loaded even with the custom component, which is why that idea of using a custom component to solve this is not a good one, seems like just a hack that can break anytimeā¦ Fine if the cloud custom component breaks, no big deal, but if I override custom_config and it breaks then I take down my whole systemā¦
I hear you and understand that code changes arenāt for anybody, but I need to say that making changes to docs in HA is a fairly simple process. Every page has a link where you can submit a change. For everything else, see if an issue was already opened or create a new one. None of that is hard and perhaps then someone with more knowledge can make the change.
Just hit the issue that bluetooth was added to default_config however this depends on BleakClient and which isnt supported on Freebsd 
bleak.exc.BleakError: Unsupported platform: FreeBSD
This is causing flow on failures to esphome so now default_config can no longer be used by all FreeBSD users.
The funny thing is that I removed default_config over a year ago and didnāt notice bluetooth was added to it so I do not have it in my configuration.yaml, yet, bluetooth works just fine fof me, it just discovered some LED lightsā¦ ĀÆ\(ć)/ĀÆ
Other components pull it in as a dependency so you probably get it from there 
Keep in mind that FreeBSD isnāt an officially supported OS for HA, so the HA team isnāt going to do anything about it (in case you had that expectation).
1 Like