#How can I prevent the cloud integration from being loaded?

1 messages ยท Page 1 of 1 (latest)

spice nebula
#

I tried Nabu Casa Cloud for a few weeks, but it wasn't for me.
And to be clear, I still support Nabu Casa, I just don't want to use the Cloud service.

Anyway, now I have logged out and removed cloud: from configuration.yaml, but the Cloud integration is still loaded.
I have never used default_config: so it shouldn't be active.
I have also restarted HA a few times, and even the whole system. Still there.

How can I prevent the cloud integration from being loaded?

stone swallow
#

What is your concern about it?

spice nebula
#

A bit of OCD - not liking things in the menu that shouldn't be there.

But also a technical interest. If it's not in the config, how can it still be loaded?

stone swallow
#

Something else may have it as a dependency

#

Like the backup component

#

You can find them in the code somewhere

spice nebula
#

I haven't enabled that, but maybe it's linked behind the scenes.
I'll take a look, but it seems a bit spooky.

dusky heart
#

it was never required to add cloud: because that's part of default_config:

#

adding it or removing it was doing nothing if default_config: is present

spice nebula
#

Yeah, but I don't use default_config, never did.
Also, now I have a few disabled entities that are impossible to remove. Not even by deleting from core.config_entries.
binary_sensor.remote_ui, switch.cloud_alexa_report_state, switch.cloud_google and a few others

#

Crazy annoying

spice nebula
#

Just did the same thing on a clean install - then it's no problem to remove cloud: and then it's gone.
I guess I have some crap that's blocking cloud from being removed. Just need to go through 5 years of config ๐Ÿ™‚

spice nebula
#

For future reference - I think it was Sppok Integration that caused it.
I deleted all Spook + Nabu / Cloud entries in core.config_entries, core.device_registry and core.entity_registry and now the Cloud integration is gone ๐ŸŽ‰ .