Integrations dessapearing afther HA reestart.

[garcru]

The problem

I installed Daikin Onecta and Local Tuya without problems but after reestarting HA both dessapeared. I can find Daikin Onecta credentials for Daikin Onecta and in Studio Code Server i can see both folders but nothing works. I have installed the integrations many times and always after reestarting they dessapear.

i wanted to do a config check with this :

After changing configuration files, check if the configuration is valid before restarting Home Assistant Core.

Switch to the user that is running Home Assistant.

sudo -u homeassistant -H -s Bash Activate the virtual environment that Home Assistant is running in.

source /srv/homeassistant/bin/activate Bash Run the configuration check.

Run the full check:

hass --script check_config Bash Listing all loaded files:

hass --script check_config --files Bash Viewing a integration’s configuration (light in this example):

hass --script check_config --info light Bash Or all integrations’ configuration

hass --script check_config --info all Bash You can get help from the command line using:

hass --script check_config --help Bash When that is complete, restart the service for it to use the new files.

But honestly i´m a very basic user and i don´t even know were to write all this.

Thank you very much for your time, your work and your help and sorry for my english.

What version of Home Assistant Core has the issue?

core-2024.10.2

What was the last working version of Home Assistant Core?

Not sure may be 2024.8

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Daikin Onecta and local tuya

Link to integration documentation on our website

https://github.com/jwillemsen/daikin_onecta

Diagnostics information

config_entry-daikin_onecta-01JA12YAZX93NV23CTA1VJ591R.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

I don´t know if any of this is relevant for my issue, but...

Registrador: homeassistant.util.loop
Fuente: util/loop.py:77
Ocurrió por primera vez: 21:26:21 (1 ocurrencias)
Última vez registrado: 21:26:21

Detected blocking call to open with args ('/usr/local/lib/python3.12/site-packages/pysiaalarm/data/sia_codes.json', 'rb') in /usr/local/lib/python3.12/site-packages/pkg_resources/__init__.py, line 1758: return open(self._fn(self.module_path, resource_name), 'rb') inside the event loop; This is causing stability issues. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#open Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.12/site-packages/pysiaalarm/aio/server.py", line 54, in handle_line event = self.parse_and_check_event(data) File "/usr/local/lib/python3.12/site-packages/pysiaalarm/base_server.py", line 64, in parse_and_check_event event = SIAEvent.from_line(line, self.accounts) File "/usr/local/lib/python3.12/site-packages/pysiaalarm/event.py", line 161, in from_line return SIAEvent( File "<string>", line 28, in __init__ File "/usr/local/lib/python3.12/site-packages/pysiaalarm/event.py", line 266, in __post_init__ self.set_sia_code() File "/usr/local/lib/python3.12/site-packages/pysiaalarm/event.py", line 106, in set_sia_code self.sia_code = _load_sia_codes().get(self.code) # pylint: disable=E1101 File "/usr/local/lib/python3.12/site-packages/pysiaalarm/data/data.py", line 44, in _load_sia_codes data = _load_data(FILE_SIA_CODES) File "/usr/local/lib/python3.12/site-packages/pysiaalarm/data/data.py", line 38, in _load_data stream = pkg_resources.resource_stream(__name__, file) File "/usr/local/lib/python3.12/site-packages/pkg_resources/__init__.py", line 1248, in resource_stream return get_provider(package_or_requirement).get_resource_stream( File "/usr/local/lib/python3.12/site-packages/pkg_resources/__init__.py", line 1758, in get_resource_stream return open(self._fn(self.module_path, resource_name), 'rb')

Registrador: homeassistant.helpers.storage
Fuente: helpers/storage.py:542
Ocurrió por primera vez: 21:26:20 (1 ocurrencias)
Última vez registrado: 21:26:20

Error writing config for core.config_entries: Failed to serialize to JSON: /config/.storage/core.config_entries. Bad data at

Registrador: homeassistant.helpers.json
Fuente: helpers/json.py:220
Ocurrió por primera vez: 21:26:20 (1 ocurrencias)
Última vez registrado: 21:26:20

Failed to serialize to JSON: /config/.storage/core.config_entries. Bad data at

Registrador: homeconnect
Fuente: components/home_connect/api.py:72
Ocurrió por primera vez: 21:26:19 (1 ocurrencias)
Última vez registrado: 21:26:19

Token expired.

Registrador: homeassistant.helpers.translation
Fuente: helpers/translation.py:285
Ocurrió por primera vez: 21:26:17 (1 ocurrencias)
Última vez registrado: 21:26:17

Validation of translation placeholders for localized (es) string component.control4.config.step.user.data.username failed: ({'name'} != set())

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (light) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `light` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign light` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

light documentation light source _{^{(message by IssueLinks)}}

[garcru]

@home-assistant remove-label needs-more-information

[garcru]

@home-assistant unassign light

[garcru]

Please any ideas??

[home-assistant[bot]]

Hey there @eavanvalkenburg, mind taking a look at this issue as it has been labeled with an integration (sia) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `sia` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign sia` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

sia documentation sia source _{^{(message by IssueLinks)}}