Integration not providing entities after upgrading HASS Core to 2024.5.0

sesardelaisla commented 2 months ago

Hello,

Last night, I upgraded Home Assistant to latest core version 2024.5.0. Today, I realized that the integration all integration entities were unavailable. Tried to remove and re-add the integration, but entities are completely gone. It seems the integration is not getting any entities from the addon:

I think the integration is connecting fine with the addon, as I had no issues when adding the AMI addon entry in the integration:

ADDON LOGS

[May  2 13:02:28]   == Endpoint Movistar_endpoint is now Reachable
[May  2 13:02:28]     -- Contact Movistar_aor/sip:XXXXXXXXX@telefonica.net is now Reachable.  RTT: 206.745 msec
[May  2 13:05:46]   == Manager 'admin' logged on from 127.0.0.1

HASS LOGS - RELEVANT TO ASTERISK

2024-05-02 13:14:59.864 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration asterisk which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-05-02 13:15:03.438 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'homeassistant_hardware', 'mqtt', 'onboarding', 'media_source', 'sensor', 'cert_expiry', 'history', 'asterisk', 'zone', 'plex', 'auth', 'template', 'stream', 'backup', 'spook', 'dlna_dmr', 'my', 'tts', 'localtuya', 'netgear_wax', 'telegram_bot', 'utility_meter', 'mobile_app', 'harmony', 'androidtv_remote', 'webrtc', 'counter', 'input_select', 'meteoclimatic', 'systemmonitor', 'tag', 'dnsip', 'image_upload', 'apple_tv', 'input_datetime', 'hacs', 'group', 'timer', 'wake_word', 'application_credentials', 'melcloud', 'watchman', 'spotify', 'synology_dsm', 'moon', 'tuya', 'system_health', 'binary_sensor', 'input_button', 'nut', 'number', 'otbr', 'webostv', 'esphome', 'bmw_connected_drive', 'google_translate', 'panel_custom', 'switch', 'androidtv', 'frigate', 'matter', 'netatmo', 'brother', 'xiaomi_miio', 'folder_watcher', 'logbook', 'dyson_local', 'device_tracker', 'input_number', 'generic', 'proximity', 'homekit_controller', 'blueprint', 'hardware', 'sun', 'scene', 'gas_station_spain', 'select', 'diagnostics', 'light', 'reolink', 'energy', 'ffmpeg', 'notify', 'broadlink', 'script', 'input_boolean', 'asusrouter', 'assist_pipeline', 'person', 'homekit', 'webhook', 'remote', 'intent', 'cast', 'file_upload', 'hue', 'config', 'media_player', 'camera', 'ideenergy', 'pvpc_hourly_pricing', 'alarmo', 'aemet', 'bluetooth_adapters', 'kodi', 'stt', 'schedule', 'shelly', 'shell_command', 'input_text', 'homeassistant', 'automation', 'device_automation', 'var', 'google_assistant', 'wake_on_lan', 'search', 'ping', 'thread', 'eufy_security', 'analytics', 'command_line', 'zha', 'rest_command', 'lovelace', 'persistent_notification', 'trace', 'conversation'}
2024-05-02 13:15:04.402 INFO (MainThread) [homeassistant.setup] Setting up asterisk
2024-05-02 13:15:04.403 INFO (MainThread) [homeassistant.setup] Setup of domain asterisk took 0.00 seconds
2024-05-02 13:15:04.488 WARNING (Thread-3 (listen)) [homeassistant.helpers.frame] Detected that custom integration 'asterisk' calls async_create_task from a thread at custom_components/asterisk/__init__.py, line 57: hass.async_create_task(, please report it to the author of the 'asterisk' custom integration
2024-05-02 13:15:04.496 WARNING (Thread-3 (listen)) [py.warnings] /usr/local/lib/python3.12/site-packages/asterisk/ami/client.py:188: RuntimeWarning: coroutine 'ConfigEntries.async_forward_entry_setup' was never awaited
  self._fire_on_disconnect(error=ex)
2024-05-02 13:16:12.296 INFO (MainThread) [homeassistant.components.automation.reinicio_asterisk] Initialized trigger Reinicio: Asterisk

I know that this issue happened just after upgrading, because I checked the AMI binary sensor history before removing and re-adding the integration and it became unavailable just after upgrading. I've had no other problems in the past.

Can I do something to fix the issue or is it just some sort of incompatibility with HASS Core latest version? Is it planned to update the integration accordingly?

TIA