GL-inet breaks HA 2026.03

[ckuethe]

Log details (WARNING)
This error originated from a custom integration.
Logger: py.warnings
Source: custom_components/glinet/router.py:11
integration: GL-iNet ([documentation](https://github.com/HarvsG/ha-glinet4-integration), [issues](https://github.com/HarvsG/ha-glinet4-integration/issues))
First occurred: 23:08:28 (1 occurrence)
Last logged: 23:08:28

/usr/local/lib/python3.14/site-packages/uplink/converters/pydantic_.py:37: UserWarning: Core Pydantic V1 functionality isn't compatible with Python 3.14 or greater. import pydantic.v1 as pydantic_v1

Homeassistant Core 2026.3.0
Frontend 20260304.0

[MrAyianaLex]

Hello,
To add a little water to the story.
The update in 2026.3.0 ended up killing home assistant.

I find this error in the logs :

ERROR (MainThread) [custom_components.glinet.router] GL-iNet router http://192.168.0.1 responded with an unexpected error
Traceback (most recent call last):
  File "/config/custom_components/glinet/router.py", line 254, in _update_platform
  File "/usr/local/lib/python3.14/site-packages/gli4py/glinet.py", line 411, in _tailscale_get_config
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/io/asyncio_strategy.py", line 32, in execute
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/io/asyncio_strategy.py", line 21, in invoke
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/io/asyncio_strategy.py", line 19, in invoke
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/io/execution.py", line 105, in on_failure
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/io/interfaces.py", line 352, in fail
  File "/usr/local/lib/python3.14/site-packages/six.py", line 724, in reraise
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/io/asyncio_strategy.py", line 16, in invoke
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/aiohttp_.py", line 28, in new_callback
  File "/usr/local/lib/python3.14/site-packages/uplink/builder.py", line 53, in wrapper
  File "/usr/local/lib/python3.14/site-packages/uplink/hooks.py", line 22, in wrapper
  File "/usr/local/lib/python3.14/site-packages/gli4py/error_handling.py", line 30, in raise_for_status
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/aiohttp_.py", line 154, in __call__
  File "/usr/local/lib/python3.14/site-packages/uplink/clients/aiohttp_.py", line 182, in __init__
  File "/usr/local/lib/python3.14/asyncio/events.py", line 844, in new_event_loop
    return _get_event_loop_policy().new_event_loop()
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 191, in new_event_loop
    loop: asyncio.AbstractEventLoop = super().new_event_loop()
                                      ~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.14/asyncio/events.py", line 732, in new_event_loop
    return self._loop_factory()
           ~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.14/asyncio/unix_events.py", line 61, in __init__
  File "/usr/local/lib/python3.14/asyncio/selector_events.py", line 63, in __init__
  File "/usr/local/lib/python3.14/selectors.py", line 338, in __init__
OSError: [Errno 24] No file descriptors available

Who, if I'm not mistaken, is moving on this second line :

ERROR (MainThread) [homeassistant] Fatal error '[Errno 24] No file descriptors available' raised in event loop, shutting it down

These two messages repeat 128 times in 270ms before the end of my log file.

home-assistant.tar.gz

To validate, I will redo the update by disabling the integration.

[kineticscreen]

Is this what my problem was? I ended up having to roll back 2026.3.0 because home assistant kept restarting randomly.

EDIT: Disabling this integration and updating to 2026.3.1 seems to have worked fine. Shame.

[kevinilcondor]

Same issue here. After updating to HA 2026.3.1 (HAOS 17.1, Python 3.14), Home Assistant was crashing every 60-90 minutes with the same [Errno 24] No file descriptors available fatal error.
The crash pattern is identical to what @MrAyianaLex described: the error repeats dozens of times in milliseconds before HA shuts down, triggered by glinet when the token expires and the integration enters a reconnection loop.
In my logs, the crash always started with a burst of:
ERROR [custom_components.glinet.router] GL-iNet router http://192.168.1.x responded with an unexpected error
ERROR [custom_components.glinet.router] GL-iNet http://192.168.1.x failed to renew the token
followed immediately by the fatal fd exhaustion.
I have 2 GL-iNet routers configured (192.168.1.1 and 192.168.1.82). Disabling the integration completely stopped all crashes immediately.
Workaround: Disable the glinet integration until a fix is released.

[HarvsG]

I'm keen to get a hot fix out and will work on it tomorrow morning.

[HarvsG]

Have been chatting with Gemini and have put together a fix proposal that I will look at

Fix Proposal: Resolve [Errno 24] File Descriptor Leaks & Blocking I/O Warnings in HA 2025.03 (Python 3.14)
Context:
With the update to Home Assistant 2025.03 (which bumps Python to 3.14), stricter asyncio loop handling is exposing a fatal file descriptor leak (OSError: [Errno 24]). This causes Home Assistant to crash completely after a few hours/days of the integration polling the router. Additionally, there is a minor blocking I/O warning during setup.
The root cause of the crash is that gli4py creates unmanaged aiohttp sessions that are never closed, hoarding system sockets.
Here is the proposed architectural fix across both gli4py and the ha-glinet4-integration.

1. Fix the Socket Leak in gli4py (glinet.py)
   Currently, gli4py forces the creation of a new, unmanaged AiohttpClient every time GLinet is instantiated. This bypasses Home Assistant's connection pooling.
   Proposal: Update the GLinet init method to accept an injected client, allowing Home Assistant to pass its globally managed aiohttp session.
   Code Change (gli4py/glinet.py):
   def init(self, sid: Optional[str] = None, client=None, **kwargs):
   self.sid: str = sid
   self._logged_in = self.sid is not None

    # Use the provided client, or fallback to a new one if used outside of HA
    if client is None:
        client = AiohttpClient()
        
    # initialise the super class
    super().__init__(client=client, **kwargs)
   

2. Inject HA's Shared Session in router.py
   Now that gli4py can accept an external client, the integration must be updated to use Home Assistant's central HTTP session. This delegates all socket cleanup and file descriptor management to Home Assistant Core, permanently fixing the Errno 24 crashes.
   Proposal: Update get_api() to inject async_get_clientsession().
   Code Change (custom_components/glinet/router.py):
   from homeassistant.helpers.aiohttp_client import async_get_clientsession
   from uplink import AiohttpClient

   async def get_api(self) -> GLinet:
   """Optimistically returns a GLinet object for connection to the API."""
   conf = self._entry.data

    # Grab HA's safe, auto-closing session
    shared_session = async_get_clientsession(self.hass)
    ha_client = AiohttpClient(session=shared_session)
   
    if CONF_API_TOKEN in conf:
        return GLinet(
            sync=False,
            sid=conf[CONF_API_TOKEN],
            base_url=conf[CONF_HOST] + API_PATH,
            client=ha_client  # Inject here
        )
    if CONF_PASSWORD in conf:
        router = GLinet(
            sync=False, 
            base_url=conf[CONF_HOST] + API_PATH,
            client=ha_client  # Inject here
        )
        await router.login(CONF_USERNAME, conf[CONF_PASSWORD])
        return router
        
    _LOGGER.error("Error setting up GL-iNet router, no auth details found")
    raise ConfigEntryAuthFailed
   

3. Fix the Unawaited Session Teardown (@Property Bug)
   Older logs show RuntimeWarning: coroutine 'ClientSession.close' was never awaited. If there is any teardown logic in router.py or gli4py intended to close the API connection, it cannot be decorated with @Property.
   Proposal: Ensure the teardown method is a standard async function and is awaited properly in init.py.
   Code Change:
   Remove @Property from any async cleanup function:

   REMOVE @Property decorator here

   async def close_session(self):
   await self._api.close()

And in async_unload_entry (inside init.py), ensure it is awaited:
await router.close_session()

4. Fix the Blocking I/O Warning (Pydantic Import)
   Logs show: Detected blocking call to import_module... inside the event loop... offender: pydantic. This happens because gli4py.login triggers a lazy-load of Pydantic models while the async event loop is running.
   Proposal: Force Pydantic to load its internals before the event loop reaches the login phase.
   Code Change: Add a top-level import to gli4py/glinet.py (or router.py) to front-load the disk read synchronously at startup:

Add to the top of the file to prevent lazy-loading in the event loop

import pydantic

Would you like me to walk you through how to apply these changes directly to your local Home Assistant files via the File Editor/Terminal, so you can test the fix on your Raspberry Pi immediately?

[HarvsG]

Likely related to #82

[HarvsG]

Annoyingly I couldn't recreate the crash in my Dev env but it did affect my prod env.
I've just released a beta 0.1.8, please test and report back

[HarvsG]

Screw it - pushed the release as it is so breaking. Hope it helps 🤞

[h0bbel]

So far so good, updated to 0.1.8 and re-enabled the integration. No errors so far, but will keep monitoring

[h0bbel]

No, still an issue and Core still crashed. Disabling the integration again.