JaccoR/hass-entso-e

Integration does not retrieve data // Detected blocking call to import_module inside the event loop

Closed this issue · 4 comments

I installed the integration about a week ago, worked fine since, until today (I think).

I updated HA 2 days ago, cannot remember from which to which version, as I track :stable, but I tend to check for upgrades at least once a month.

Versions:

Core 2024.5.4
Frontend 20240501.1
ENTSO-e 0.3.0 (In the integrations screen it says 0.0.1 but HACS says 0.3.0 and does not have blue color with UPDATE indicator)

Docker Image:

            "Labels": {
                "io.hass.arch": "amd64",
                "io.hass.base.arch": "amd64",
                "io.hass.base.image": "ghcr.io/home-assistant/amd64-base:3.19",
                "io.hass.base.name": "python",
                "io.hass.base.version": "2024.03.0",
                "io.hass.type": "core",
                "io.hass.version": "2024.5.4",
                "org.opencontainers.image.authors": "The Home Assistant Authors",
                "org.opencontainers.image.created": "2024-05-17 13:09:55+00:00",
                "org.opencontainers.image.description": "Open-source home automation platform running on Python 3",
                "org.opencontainers.image.documentation": "https://www.home-assistant.io/docs/",
                "org.opencontainers.image.licenses": "Apache License 2.0",
                "org.opencontainers.image.source": "https://github.com/home-assistant/core",
                "org.opencontainers.image.title": "Home Assistant",
                "org.opencontainers.image.url": "https://www.home-assistant.io/",
                "org.opencontainers.image.version": "2024.5.4"
            }

Set integration to debug and restarted HA

2024-05-23 16:33:54.337 DEBUG (MainThread) [custom_components.entsoe.coordinator] Fetching ENTSO-e data
2024-05-23 16:33:54.337 DEBUG (MainThread) [custom_components.entsoe.coordinator] NL
2024-05-23 16:33:54.517 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module inside the event loop by custom integration 'entsoe' at custom_components/entsoe/coordinator.py, line 97: yesterday = pd.Timestamp.now(tz=str(time_zone)).replace(hour=0, minute=0, second=0) - pd.Timedelta(days = 1) (offender: /usr/local/lib/python3.12/site-packages/pandas/compat/_optional.py, line 132: module = importlib.import_module(name)), please create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-05-23 16:33:55.027 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 58: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-05-23 16:33:56.251 DEBUG (MainThread) [custom_components.entsoe.coordinator] Finished fetching ENTSO-e coordinator data in 1.914 seconds (success: True)

(I could have left out the hacs line, but I left it for completeness, I did not edit the copy/paste)

If you need any further assistance or data, feel free to reach out?

Thanks in advance for your effort and support!

I have no/old sensor.entso_average_electricity_price_today information. All other sensors are fine, this sensor keeps showing information from May 21/22.
IMG_0127

note: the last modified date changed to 2 June because I rebooted HA to see if it would resolve the issue. Before that it was 21 May.

I have a similar issue, but after updating to 2024.6.x. I had the same issue after updating to 2024.5.x and I re-added the integration with a new name. Worked great, until the recent update resulting in no new data after the update.

Any thoughts on how to solve this?

Same issue, all prices are stuck since a few days. Tried reloading / restarting but no luck. Seems to have started around the time that some problems with availability of pricing data was reported but that might be unrelated as well.

v0.4.0 is released this version contains fixes that solve a lot of warnings and known issues. This issue is probably also solved.
Please update to the latest version.
Closing this issue for now. If you still have issue please feel free to open a new issue.