Integration Version
v.1.6.2
OpenWrt Version
25.12.2
Connection Method
ubus (HTTP/HTTPS)
Describe the bug
Bug Report: Duplicate AP devices created for non-standard phy*-ap* interface names
Bug Report: Duplicate AP devices created for non-standard phy*-ap* interface names
Environment
- Home Assistant version: 2026.4
- Integration version: v1.6.2
- OpenWrt version: 25.12.2
- Device: Linksys Velop WHW03
- Connection method: Ubus (root user)
Hardware structure
The Velop WHW03 has 3 radios with 5 virtual interfaces total:
ubus call iwinfo devices
{
"devices": [
"phy1-ap1",
"phy0-ap0",
"phy1-ap2",
"phy1-ap0",
"phy2-ap0"
]
}
Radios:
- radio0 — Qualcomm QCA9886, 5 GHz (ch. 149) → 1 SSID: MyNet-Guest
- radio1 — Qualcomm IPQ4019, 2.4 GHz (ch. 11) → 3 SSIDs: MyNet, MyNet-Guest, MyNet-IoT
- radio2 — Qualcomm IPQ4019, 5 GHz (ch. 36) → 1 SSID: MyNet
Description
For each SSID, the integration creates multiple duplicate devices instead of one device per SSID+band combination. After a clean reinstall (integration deleted, all orphaned devices removed, freshly re-added) on v1.6.2, the following devices are created:
For SSID "MyNet-Guest":
AP MyNet-Guest (6 entities) — duplicate 1AP MyNet-Guest (6 entities) — duplicate 2AP MyNet-Guest (2.4 GHz) (10 entities)AP MyNet-Guest (5 GHz) (10 entities)
For SSID "MyNet":
AP MyNet (6 entities) — duplicate 1AP MyNet (6 entities) — duplicate 2AP MyNet (2.4 GHz) (10 entities)AP MyNet (5 GHz) (10 entities)
For SSID "MyNet-IoT":
AP MyNet-IoT (6 entities)AP MyNet-IoT (2.4 GHz) (10 entities)
Root cause hypothesis
The interface naming convention phy*-ap* (e.g. phy0-ap0, phy1-ap0, phy1-ap1) instead of the standard wlan* naming appears to confuse the device creation logic. The integration likely creates one device per physical interface name and one per SSID+band, resulting in duplicates for SSIDs that span multiple virtual interfaces on the same radio.
This is related to the previously reported via_device bug (non-existing via_device reference for phy*-ap* interface names).
Expected behavior
One device per SSID+band combination, cleanly nested under the router device. No duplicates.
Actual behavior
Multiple duplicate devices per SSID, causing significant entity clutter. A router with 3 SSIDs across 3 radios results in 10+ AP devices instead of the expected 5.
Relevant log output
Integration Version
v.1.6.2
OpenWrt Version
25.12.2
Connection Method
ubus (HTTP/HTTPS)
Describe the bug
Bug Report: Duplicate AP devices created for non-standard phy*-ap* interface names
Bug Report: Duplicate AP devices created for non-standard phy*-ap* interface names
Environment
Hardware structure
The Velop WHW03 has 3 radios with 5 virtual interfaces total:
Radios:
Description
For each SSID, the integration creates multiple duplicate devices instead of one device per SSID+band combination. After a clean reinstall (integration deleted, all orphaned devices removed, freshly re-added) on v1.6.2, the following devices are created:
For SSID "MyNet-Guest":
AP MyNet-Guest(6 entities) — duplicate 1AP MyNet-Guest(6 entities) — duplicate 2AP MyNet-Guest (2.4 GHz)(10 entities)AP MyNet-Guest (5 GHz)(10 entities)For SSID "MyNet":
AP MyNet(6 entities) — duplicate 1AP MyNet(6 entities) — duplicate 2AP MyNet (2.4 GHz)(10 entities)AP MyNet (5 GHz)(10 entities)For SSID "MyNet-IoT":
AP MyNet-IoT(6 entities)AP MyNet-IoT (2.4 GHz)(10 entities)Root cause hypothesis
The interface naming convention
phy*-ap*(e.g.phy0-ap0,phy1-ap0,phy1-ap1) instead of the standardwlan*naming appears to confuse the device creation logic. The integration likely creates one device per physical interface name and one per SSID+band, resulting in duplicates for SSIDs that span multiple virtual interfaces on the same radio.This is related to the previously reported
via_devicebug (non-existingvia_devicereference forphy*-ap*interface names).Expected behavior
One device per SSID+band combination, cleanly nested under the router device. No duplicates.
Actual behavior
Multiple duplicate devices per SSID, causing significant entity clutter. A router with 3 SSIDs across 3 radios results in 10+ AP devices instead of the expected 5.
Relevant log output