Bonjour,
suite à la mise à jour de HA core 2025.5.0 , j’ai mon local tuya qui est hors fonction … il y a tous mes volets dessus !!!
j’ai restauré ma sauvegarde , ca refonctionne… je refais la mise à jour … boumm , localuya HS …
mes journaux :
Enregistreur: homeassistant.setup
Source: setup.py:426
S'est produit pour la première fois: 09:42:40 (1 occurrence)
Dernier enregistrement: 09:42:40
Error during setup of component localtuya: 'HomeAssistant' object has no attribute 'helpers'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 426, in _async_setup_component
result = await task
^^^^^^^^^^
File "/config/custom_components/localtuya/__init__.py", line 165, in async_setup
hass.helpers.service.async_register_admin_service(
^^^^^^^^^^^^
AttributeError: 'HomeAssistant' object has no attribute 'helpers'
.
.
Enregistreur: homeassistant.components.vacuum
Source: helpers/deprecation.py:222
intégration: Aspirateur (documentation, problèmes)
S'est produit pour la première fois: 09:42:40 (12 occurrences)
Dernier enregistrement: 09:42:40
STATE_DOCKED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.DOCKED instead, please report it to the author of the 'localtuya' custom integration
STATE_ERROR was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.ERROR instead, please report it to the author of the 'localtuya' custom integration
STATE_IDLE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.IDLE instead, please report it to the author of the 'localtuya' custom integration
STATE_PAUSED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.PAUSED instead, please report it to the author of the 'localtuya' custom integration
STATE_RETURNING was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.RETURNING instead, please report it to the author of the 'localtuya' custom integration
.
.
ma config :
## System Information
version | core-2025.5.0
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.13.3
os_name | Linux
os_version | 6.12.23-haos
arch | x86_64
timezone | Europe/Paris
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 4974
Installed Version | 2.0.5
Stage | running
Available Repositories | 1711
Downloaded Repositories | 12
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 15.2
-- | --
update_channel | stable
supervisor_version | supervisor-2025.04.1
agent_version | 1.7.2
docker_version | 28.0.4
disk_total | 879.5 GB
disk_used | 287.1 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization |
board | generic-x86-64
supervisor_api | ok
version_api | ok
installed_addons | Advanced SSH & Web Terminal (20.0.2), ESPHome Device Builder (2025.4.1), File editor (5.8.0), Frigate (0.15.1), Mosquitto broker (6.5.0), NGINX Home Assistant SSL proxy (3.11.1), Samba share (12.5.1), Studio Code Server (5.19.2), Terminal & SSH (9.17.0), Zigbee2MQTT (2.3.0-1), MQTT Explorer (browser-1.0.1), MyElectricalData (0.13.2), Matter Server (7.0.0), Let's Encrypt (5.4.9), Get HACS (1.3.1)
</details>
<details><summary>Dashboards</summary>
dashboards | 2
-- | --
resources | 6
views | 17
mode | storage
</details>
<details><summary>Network Configuration</summary>
adapters | lo (disabled), enp1s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth65ba876 (disabled), veth614b43e (disabled), vethe5eb7f8 (disabled), veth6df803e (disabled), veth0a88dd3 (disabled), vethc63f453 (disabled), vethe48eee5 (disabled), veth7a48434 (disabled), veth7c980a9 (disabled), veth236beb9 (disabled), veth1a27c0b (disabled), veth1793aee (disabled)
-- | --
ipv4_addresses | lo (127.0.0.1/8), enp1s0 (192.168.0.100/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth65ba876 (), veth614b43e (), vethe5eb7f8 (), veth6df803e (), veth0a88dd3 (), vethc63f453 (), vethe48eee5 (), veth7a48434 (), veth7c980a9 (), veth236beb9 (), veth1a27c0b (), veth1793aee ()
ipv6_addresses | lo (::1/128), enp1s0 (2a01:e0a:3f6:30d0:633d:406c:926b:5c5e/64, fe80::d9a9:effb:8a21:89c7/64), docker0 (fe80::a400:deff:fef7:ade9/64), hassio (fe80::d47a:16ff:fed4:c6bd/64), veth65ba876 (fe80::d85c:d4ff:fefd:78b/64), veth614b43e (fe80::4b2:91ff:fe30:b11c/64), vethe5eb7f8 (fe80::4433:c4ff:fe14:8b19/64), veth6df803e (fe80::e03f:45ff:fe9d:14c/64), veth0a88dd3 (fe80::2c6c:cbff:febb:128d/64), vethc63f453 (fe80::48c2:2ff:fe67:eac2/64), vethe48eee5 (fe80::5891:8bff:fe4d:a32e/64), veth7a48434 (fe80::f8d4:f9ff:fe0c:e06f/64), veth7c980a9 (fe80::d0ed:94ff:fefa:61c9/64), veth236beb9 (fe80::3c96:66ff:fe9a:f014/64), veth1a27c0b (fe80::5897:18ff:fef2:c96d/64), veth1793aee (fe80::e009:ecff:fef8:ea27/64)
announce_addresses | 192.168.0.100, 2a01:e0a:3f6:30d0:633d:406c:926b:5c5e, fe80::d9a9:effb:8a21:89c7
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | 27 avril 2025 à 09:18
-- | --
current_recorder_run | 8 mai 2025 à 09:42
estimated_db_size | 973.46 MiB
database_engine | sqlite
database_version | 3.48.0
</details>
.
.
Quelqu’un a le même problème et a trouvé une solution ?
Au pire il faudra que je reste en version core 2025.4.4 …
