Core.config_entries not updated in .storage

Configuration
1

Hi together,

after updating my setup to HassOS 4.15 and Home Assistant 0.116.4 my secrets.yaml is not working anymore for an unknown reason. I did not change my configuration at all. Maybe it was already failing before the update, which I did not recognize.

Some background:
I am using a splitted setup, means my configuration.yaml is including the integrations and entities from separate yaml files. This setup worked for several months until now.

Because my static IP setup on my DHCP sever got messed up, I wanted to update also the Home Assistant configuration with the changed ip addresses e.g from 192.168.0.1 to 192.168.0.200. I then recognized, that Home Assistant is still trying to include the entity with the old IP address 192.168.0.1 although the new one is in the secrets.yaml.

What I have already tried:

  • Rename secrets.yaml (trying to invalidate some cache I am not aware of)
  • Restart Home Assistant
  • Reboot the system
  • Switch off electricity completely for some minutes
  • Clean browser cache

Nothing has helped. Home Assistant is still using the old IP address. Which leads to my first question: Is there any kind of cache, which can be invalidated?

Moreover I added “logger: debug” to my secrets.yaml showing me the following:

2020-10-26 13:08:47 DEBUG (SyncWorker_53) [homeassistant.util.yaml.loader] Secret synology_nas_01_password retrieved from secrets.yaml in folder /config/integrations/..
2020-10-26 13:08:47 DEBUG (SyncWorker_53) [homeassistant.util.yaml.loader] Loading /config/integrations/secrets.yaml

But I have no secrets.yaml files in these folders. There is only my central secrets.yaml in /config. I cannot explain, why HA is trying to find the secrets in different locations. I am aware, what there is a hierarchy to search for secrets 1) same folder, 2) parent and 3) /config. It seems HA is stopping in step 1).

I would really appreciate if anyone could help. Thank you in advance.

Kind regards
tob_lip

2

Hi,

does anyone experience similar issues?

Kind regards
tobi_lip

3

I recognized, that HA still uses the old IP from the old secrets.yaml although I directly added the IP to the configuration.yaml instead. I could not explain where this old IP is coming from. I deleted the database file again after shutting down HA, but the old IP is still used.

4

Additional information: I guess I have found the cause. The old IP address is still stored in core.config_entries in .storage directory. The new IP address not. I am not sure why this is like that. Is there a way to trigger an update of core.config_entries?

5

The IP address is not set in secrets.yaml.

It is set in the supervisor / system menu:

Untitled
Untitled1289×497 40.4 KB

6

I mean IP adresses for yeelights for example.

7

Try editing the Yelight integration in the configuration/integrations menu.

8

This solved the issue. I set up all my integrations directly via configuration. Updating secrets has always worked in the last months. Anyways, I now know what to do in such cases. Thank you very much.

9

Not Yeelight, but otherwise somewhat similar issue:

In Nordpool integration the modifications of the settings in configuration.yaml get not stored in core.config_entries. The initial settings are possible to set in the integeration in the installation phase also, but since I was not familiar with all the parameters (they neede trial & error kind of process) , I wrote the key parameters also to configuration.yaml, as instructed.

However, when modifying, they do not get updated in core.config_entries and this causes some conflicts.

I would not like to edit core.config_entries directly.
There is an integaration panel for it in integrations, but no way yto modify it’s settings.

How then?