TP-Link Omada integration contains ESPhome items

[xdedek]

The problem

For a long time now, and in several versions of HA, items from ESPHome have also appeared in the TPlink Omada integration. I have no idea if the error is on the side of the TPlink integration, or on the contrary ESPHome.
I have 4 ESP devices and 4 TPlink devices. with ESP I have 4 devices displayed, with TPlink I have 8 devices selected. See picture.

What version of Home Assistant Core has the issue?

core-2024.10.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

tplink_omada

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

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) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[jmello86]

I'm having the same issue, except the extra devices are my Meross switches and lights, as well as my Brother printer.

[dinan5]

I’m having the same issue with Meross devices.

[mheath]

Isn't this the expected behavior? A device can be associated with multiple integrations. The device tracker support added to Omada allows you to track the state of devices connected to the Omada network. Since your ESPhome devices are presumably connected to your Omada wireless network, they should have an Omada device tracker entity associated with them.

[dinan5]

Perhaps I don't understand how this is intended to work. I was under the impression that each device connected to an EAP would have device tracking entity and not have a device entry, only. If what you are saying is correct, then I would expect to see device entries for about 50 other devices that I have HA integrations for that are also connected to an Omada EAP. I only see entries for Meross devices.

So, the question then becomes - which is the bug - that there are 2 and it should be zero, or there are 2 and there should be 50?

[mheath]

When a device gets registered in HA by its integration, it can (but does not have to) provide a MAC address to identify the device. Every wireless device that does this should show up as an Omada device too because of the device tracking support.

My Nest thermostat is connected to my wifi but it doesn't show up as an Omada device because it's accessed through Google's cloud APIs and not accessed directly so the Nest integration is unaware of the thermostat's MAC address.

None of my computers show up in the Omada API because they're not registered with Home Assistant so there's no existing device to attach a tracker to.

All my WLED and ESPhome devices show up as Omada devices because the WLED and ESPhome integrations register the device's MAC address with HA. Most of my smart light switches show up as Omada devices too. I have smart power strip that's connected to the Wifi but HA accesses through a cloud API and it, as expected, does not show up.

Are your 48 "missing" devices connected to HA through a hub or access through a cloud API?

I do wish there were a configuration option to track ALL Wifi connected Omada devices and not just existing devices. (I think, maybe, this might be what you're expecting.)

[dinan5]

Thank you for the reply and explanation. It must be that this integration picks up devices that are able to communicate directly over the LAN without going through an API, as you say. Meross can in fact do that. I good feature would be disable this feature, for consistency.

Thanks again!

[TechJedi90]

Yes i am getting this issue with Shelly Smart Switches showing up under this Integration

[mheath]

Other device tracker implementations like Netgear and Unifi behave the same way. If this is a bug, it appears to be a bug with the device tracker platform.

[vrtareg]

I am having same issue. My Roku and Samsung TV are listed under TP-Link integration and so separately.

Not sure if there is any reason for this.