Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Adding an AP creates an additional device "AiMesh None (None)" #783

Open
mihsu81 opened this issue Feb 2, 2024 · 4 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@mihsu81
Copy link

mihsu81 commented Feb 2, 2024

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.
image
image

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?

None available even with debugging enabled.

Diagnostics information

config_entry-asusrouter-24157713f05cc3733c2cac5119406cfd.json.txt

Additional information

No response

@mihsu81 mihsu81 added the bug Something isn't working label Feb 2, 2024
@mihsu81
Copy link
Author

mihsu81 commented Mar 12, 2024

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)".

@mihsu81
Copy link
Author

mihsu81 commented Mar 14, 2024

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.

@Vaskivskyi
Copy link
Owner

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)

@mihsu81
Copy link
Author

mihsu81 commented Mar 21, 2024

Nothing to be sorry about. Thanks a lot for your great work on this integration. 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: In Progress
Development

No branches or pull requests

2 participants