I get this message
but I don’t use Nuba Casa cloud,
so this doesn’t apply to me in any way.
“Nabu Casa”.
fixed that
This had me confused too. Even if it applies to you it is very poorly worded, and even more so if it doesn’t and you don’t have a clue what it’s about - where did this come from, who is “we”, what infrastructure, what is a “non-local command from Alexa”, what remote UI??? And why is it under “Repairs”?
If this really is to do with Nabu Casa and it can’t be targeted only at machines that are using it, it needs a lot more explanation in it.
I think, I wrote it already in another “WTH” related to this message.
Since “Repairs” is pulling the information from the HomeAssistant Alerts - page (don’t have the link atm) - it would be an idea to introduce “channels” for such messages.
This would allow, that messages with Channel “NabuCasa” will only be shown to users that are using the NabuCasa Cloud.
Similar as it is done for the Integration Alerts - when you are using a specific Integration which has alerts listed:
System with Homematic IP installed:
System without Homematic IP Installed:
Do you use mobile push notifications? That goes through nabu casa cloud always. I’m not 100% sure if that was impacted by this issue, but good to know and dismiss I think.
The whole idea is to always geep everything so the server doesn’t know the configuration.
Filtering should be fine client side. This takes more data but is better for privacy.
So the filtering should be optimized.
Do you have the default_config:
in your configuration? That could be this is loading ha cloud. Even you don’t use it and then pull these messages. I’ve never had such messages.
Édit : be careful if you remove this default config from your configuration. It loads a bunch of things. Details here : Default Config - Home Assistant
Yes I have,
and another thing that bothers me is that I can not remove the Home Assistant Cloud
button without removing default_config:
I know it can be replaced and I have to add all configs manually, But it’s easier if it’s maintained by default.
default_config: !cloud
or something would be a great solution.
still, if it’s not configured, the warning shouldn’t be there.
I guess the thing is even it’s not configured it’s still loaded, and if it’s loaded you have the alerts.
Sure that something like default_config: !cloud
would be a nice to have
It’s been discussed many many times. The team rejects any ‘include/exclude’ functionality for default config for a variety of reasons I don’t want to list. I don’t want to start an another argument about this, just passing the information on. Your only option is to break default config apart and omit what you don’t want. It takes about 10 minutes to do that.
I surely will do this,
I see that I can also disable BT discovery an usb with this, and other stuff I do not use.
Actually the reason why I haven’t done this already is that I’m afraid I miss some functionality when sth new is implemented or my config breaks whenever something gets deprecated.
To date, nothing has ever been removed from default config, only added. And if you don’t have the functionality in the future, you simply just add whatever that may be.
In the 4 years i’ve been managing my default_config, I’ve had to add 2 items… bluetooth and energy. So, it’s really not as painful as you’re making it out to be. The team has gotten better with documentation that lets you know you have to add these items when they are released as well.
good point,
one question,
if I check the documentation
vs the manifest
is see some differences
application_credentials
network
backup
logger is new, So I leave it out of scope
where I assume the one from git is correct, but if I go according to the manual and forget to put in network
it might be hard to fix this as I assume it will kill my network config
You don’t need backup if you have supervisor. the other 2 you can add. Seems like a gap in the documentation and they should be added. Either way, you can get by without them. I don’t use any of them.
I don’t have any network:
anywhere in my configuration (neither default_config) and my network config is working fine… (using HA OS)