Changes on Integrations are reset after reboot

Configuration
1

Hi Guys,

I have a problem with changes on my Integrations.
When removing one or more Integrations and rebooting the pi the integration is available again. This seems like a general problem as I also need to pre-authorized the tuya integration and this happens after each reboot of the system.

I have already re-installed the whole system from scratch and restored from an backup but the behavior describes still exists.

Do you guys have any idea what is going wrong here and how to solve that?

Best,
Max

2

Hi Max,

Can you tell us more about how you have configured and installed Home Assistant, and what versions you are running?
Installation - Home Assistant.

3

Sure I am running home assistant on an RPI5 (previously 4 but same behavior there) but can’t tell exactly when this happened the first time.

  • Core2024.10.2
  • Supervisor2024.10.2
  • Operating System13.2.rc1
  • Frontend20241002.3

I am running quite a while on Beta and this is not related to the latest beta release, it happend also already earlier.

Also already checked the homeassistant.log as well as the homeassistant.log.1 but was not able to find anything that could be related to this or explains the behavior.

Let me know if you need anything else.

Best
Max

Hope that helps

4

What do you mean “integration is available again”, can you share screenshots?

5

Sure so for example when deleting the Fully Kiosk Browser integration:

image
image1206Ă—566 32.2 KB

it appears as deleted:

image
image1059Ă—322 14.1 KB

But after I restart the raspberry, it comes available again:

image
image1059Ă—415 25.1 KB

Also the tuya integration requests a new auth via QR code after each reboot:
image

And also for all other integrations that I delete via this way the same behavior.

Hope that helps :slight_smile:

6

Just removed the logs from the gui, deleted some more integrations and found that:

Logger: homeassistant.helpers.storage
Quelle: helpers/storage.py:542
Erstmals aufgetreten: 16:00:11 (3 Vorkommnisse)
Zuletzt protokolliert: 16:00:18
Error writing config for core.config_entries: Failed to serialize to JSON: /config/.storage/core.config_entries. Bad data at

and

Logger: homeassistant.helpers.json
Quelle: helpers/json.py:220
Erstmals aufgetreten: 16:00:11 (3 Vorkommnisse)
Zuletzt protokolliert: 16:00:18
Failed to serialize to JSON: /config/.storage/core.config_entries. Bad data at

Could that be the cause of the problem?

7

Yes, your config entries is corrupted. Did you alter this file?

8

Nope did not touch that file at all.
Any chance in repairing the file manually?

9

Yep, however you need to understand the inner workings of HA to do so.

10

Alright short update on this, I was able to fix it, anyhow the Meross integration made about 400 inherited arrays in the parameter “mqtt_domain” which led to an error in the serialization of the json.

Topic can be closed, thanks for your support on this guys!

1 Like
11

I see that you fixed it with the Meross issue, but what did you actually do to fix it? I’m in the same position now and I also have the Meross integration.

12

So the issue for me was in the file
/config/.storage/core.config_entries

The meross integration created a huge huge huge inherited array in the form of:
[
[
[
…
mqtt_domain:…
…
]
]
]

Solution was deleting those brackets completely and now everything works as expected again.

Best
Max

1 Like
13

I’m having the exact same issue. I’ve deleted the brackets and rebooted, but sadly no change

14

Hi all, exact same issue with tuya and other integration (I have meross too and also all those brackets…) …just updated… reboot and… ISSUE SOLVED!! you made my day (at least with HA) my friend!! solved an old issues I was having since MONTHS!! thanks @sharkyy112

1 Like
15

Just a word of warning for those of you who fixed the problem by removing the excess [ ] from the config_entries / meross entry, I have noticed that for some reason a new set of [ ] gets added on every reboot of Home Assistant.

I’ve added details of this to an already open issue on github:

Probably worth checking to see if you are getting the same build up of brackets in your config_entries file, as I think when it gets to a certain number it will cause the issues with other integrations again.

1 Like