HA warning and potential API issue

[effinamon]

Got this warning in the HA log:

WARNING (MainThread) [homeassistant.helpers.frame] Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for thermia using this method at custom_components/thermia/__init__.py, line 51: hass.config_entries.async_setup_platforms(config_entry, PLATFORMS)

Also got a lot of these, but unsure if it is related or just connection issues:

2023-03-02 08:12:11.795 ERROR (SyncWorker_1) [ThermiaOnlineAPI.api.ThermiaAPI] Error setting register 50 value. 500
2023-03-02 08:12:29.037 ERROR (SyncWorker_3) [ThermiaOnlineAPI.api.ThermiaAPI] Error in getting device's register group: REG_GROUP_OPERATIONAL_STATUS, Status: 500
2023-03-02 08:37:00.481 ERROR (SyncWorker_7) [ThermiaOnlineAPI.model.HeatPump.(myIDxxxx)] Status not available, cannot set temperature
2023-03-02 08:37:38.859 ERROR (SyncWorker_15) [ThermiaOnlineAPI.api.ThermiaAPI] Error fetching device status. 500
2023-03-02 08:37:47.789 WARNING (SyncWorker_15) [urllib3.connectionpool] Connection pool is full, discarding connection: online-classic-serviceapi.azurewebsites.net. Connection pool size: 10

I use the integration as part of my automations so I've downgraded to 2023.2 for now (and it's working fine). Not sure if anyone else have seen similar issues.

[AriRosti]

I have not downgraded from 2023.3 and HA logs this, but the integration still works.

Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for thermia using this method at custom_components/thermia/__init__.py, line 51: hass.config_entries.async_setup_platforms(config_entry, PLATFORMS)

[klejejs]

Hello! Thanks for reporting this. I'll try to fix this within the next few days. It seems there have been new changes in Home Assistant integration requirements.

[klejejs]

The new version 2.18 fixes the issue. Please update and report if there are still problems.