You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a device as AP creates an additional device "AiMesh None (None)".
If I had the router added as a device, after reloading HA, another device "AiMesh None (None)" gets created, but belonging to the router.
Your device model
RT-AC87U
Firmware type
Stock
Firmware version
3.0.0.4.382_52545-ga0245cc
Integration version with the issue
0.28.0
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
Just to add that if I add the same AP as an AiMesh Node, the additional device "AiMesh None (None)" doesn't get created and neither does the additional sensor "AiMesh None (None)".
It looks like the issue happens only with older devices which don't have AiMesh support.
In this case the device causing the issue is an RT-AC87U on 384.13_10 or 3.0.0.4_382_52545-ga0245cc.
Hello. I am sorry for the delay in solving your issue. Unfortunately, I haven't had any free time lately. I will try to solve it as soon as I get such an opportunity. Sorry again for the inconvenience
From the known bugs, it looks like the AP support should be redone. I will check whether it requires a complete change of the library/integration logic or can be fixed in parts (which might be faster)
The problem
Adding a device as AP creates an additional device "AiMesh None (None)".
If I had the router added as a device, after reloading HA, another device "AiMesh None (None)" gets created, but belonging to the router.
Your device model
RT-AC87U
Firmware type
Stock
Firmware version
3.0.0.4.382_52545-ga0245cc
Integration version with the issue
0.28.0
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
Core 2024.1.6
Is there anything useful in the logs?
Diagnostics information
config_entry-asusrouter-24157713f05cc3733c2cac5119406cfd.json.txt
Additional information
No response
The text was updated successfully, but these errors were encountered: