history: and logbook: will automatically load the recorder: component even if not explicitly called out in your configuration. best way to disable all of them is to only load the components you need and check their manifest.json on github to see what other components they may load. There could be other components that rely on the recorder and load it as a dependency. You can always set the recorder options with a blank include: section to force it to exclude everything and not include anything in the recorder database.
Correct. The database file would be created, but with nothing in it. Yes it’s a workaround, but if there’s a component you use that relies on the recorder and loads it as a dependency, there’s not much you can do except make a custom component so it doesn’t use the recorder, or create an empty database.
Hmm no, when changing default_config to frontend, it will only load a small amount of required components (such as api and auth).
It will not load recorder, logger and such. Effectively not creating a database, I am using this setup
If your response was to me, my response was to the OP regarding setting up the recorder but not putting anything in the include:. The workaround I described is if they are forced to load the recorder component because some other component loads it. That work around would still create a database, albeit an empty one. In your case, yes you’re right, only loading specific components that do not load the recorder component would mean the database is never created.