Error fetching Omada API Data / PoE Ports cannot be activated or deactivated

[alex-mueller72]

The problem

After Updating the firmware of my Omada switches I cannot switch PoE Ports on or off.

New Switch Firmware:
SG2005P-PD -> 1.0.21 Build 20260310 Rel.10715
SG3428XMP -> 3.20.23 Build 20260310 Rel.11233

The Omada Controller runs as LXC on Proxmox.
Omada Controller version: 6.1.0.19

I restarted the Omada Controller.
I deleted the TP-Link Omada integration and reinstalled it.

Let me know, if you need more information.

What version of Home Assistant Core has the issue?

core-2026.3.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

TP-Link Omada

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink_omada

Diagnostics information

home-assistant_tplink_omada_2026-03-29T19-17-52.621Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: homeassistant.components.tplink_omada.coordinator
Quelle: helpers/update_coordinator.py:432
Integration: TP-Link Omada (Dokumentation, Probleme)
Erstmals aufgetreten: 20:23:13 (4 Vorkommnisse)
Zuletzt protokolliert: 20:23:14

Timeout fetching Omada API Data - DeviceList data
Timeout fetching Omada API Data - SG2005P-PD-Hof Ports data
Timeout fetching Omada API Data - SG2005P-PD-WZ Ports data
Timeout fetching Omada API Data - SG3428XMP Ports data


Logger: homeassistant.components.websocket_api.http.connection
Quelle: components/websocket_api/commands.py:279
Integration: Home Assistant WebSocket API (Dokumentation, Probleme)
Erstmals aufgetreten: 20:00:54 (15 Vorkommnisse)
Zuletzt protokolliert: 21:16:50

[139851334814592] Unexpected exception
[139851316448768] Unexpected exception
[139851112811072] Unexpected exception
[139851360558816] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 279, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2817, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2860, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 835, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 907, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tplink_omada/switch.py", line 321, in async_turn_off
    await self._async_turn_on_off(False)
  File "/usr/src/homeassistant/homeassistant/components/tplink_omada/switch.py", line 303, in _async_turn_on_off
    updated_details = await self.entity_description.set_func(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        self.coordinator.omada_client, self._device, self._port_details, enable
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/tplink_omada_client/omadasiteclient.py", line 556, in update_switch_port
    await self._api.request(
    ...<3 lines>...
    )
  File "/usr/local/lib/python3.14/site-packages/tplink_omada_client/omadaapiconnection.py", line 202, in request
    return await self._do_request(method, url, params=params, json=json, data=data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tplink_omada_client/omadaapiconnection.py", line 244, in _do_request
    raise LoginSessionClosed()
tplink_omada_client.exceptions.LoginSessionClosed

Additional information

No response

[home-assistant]

Hey there @MarkGodwin, mind taking a look at this issue as it has been labeled with an integration (tplink_omada) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tplink_omada can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tplink_omada Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@alex-mueller72 Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20tplink_omada%22%20
_{^{(message by IssueContext)}}

---

tplink_omada documentation
tplink_omada source
_{^{(message by IssueLinks)}}

[mathieuruellan]

Same experience! On my system.

[m2r57700]

I have the same issue.
State of omada entities are working fine but POE ports can't be activated or deactivated.

[whitakercaleb09-dev]

I am also experiencing this issue. While the state of the Omada entities appears to be working correctly, I am unable to activate or deactivate the PoE ports.

…

On Tue, Mar 31, 2026, 6:57 AM m2r57700 ***@***.***> wrote: *m2r57700* left a comment (home-assistant/core#166814) <#166814 (comment)> I have the same issue. State of omada entities are working fine but POE ports can't be activated or deactivated. — Reply to this email directly, view it on GitHub <#166814?email_source=notifications&email_token=B735AJCZUHSTUN576MYFJET4TOXA5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGIYTAMBSGIY2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4162100221>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B735AJGITHLSID52YHCB3ZT4TOXA5AVCNFSM6AAAAACXFGQ6GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRSGEYDAMRSGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[owiebaclay]

Same problem i experienced when updating to 2026.3.4 and 2026.4 POE switches are not working reverted back to 2026.3 and it works.

[9zenith]

The issue was occurred since 2026.3.4

[alex-mueller72]

Thanks for clarifying. I first installed 2026.3.4 and then the switch firmware (see my first post). At first, I thought the switch firmware update was the cause.

[MarkGodwin]

It looks like I broke this in an unrelated fix to support the new beta Omada firmware version. I'll aim to get this fixed this weekend.