-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Bug] My device (client) gets dis-/reconnected regularly or not tracked well #792
Comments
Asusrouter integration: POE switch and access point itself don't get disconnected. I mainly have the connect/disconnect isues with devices connected via either the switch or the access point.
I had it before with my Broadlink RM4 mini as well, but since it's now connected directly with the router (not via access point), it stays online... So I really think the issue happens when the device is connected via an intermediate device. All of them are connected via 2.4GHz network. Another thing I noticed (not sure it's related) is that devices, connected wirelessly via the access point, are seen as wired connections... (maybe because the access point itself is wired?) |
@h3llrais3r, I will try to find some switch and AP to test the behaviour. Hopefully, this is more Meanwhile, can you please check that the data is shown the same way when you open the |
@Vaskivskyi, only the network map shows devices, the AImesh part shows 0. EDIT: maybe 1 more remark, not sure if it could have something to do with it, but I have |
Router: RT-AX53U FW: 3.0.0.4.386_69061 |
I am noticing the same issue. I have two Poe switches. One plugged into the main mesh router and the other to a node. The switch plugged into the node has disconnect and reconnect events repeatedly. Also a wifi IP camera did a few connection events. Which is connected to the same node. |
@Vaskivskyi something new? |
Unfortunately, not yet |
Since this is happening for the switches I have them ignored when sending notifications. The devices connected to the switches are not triggering but if they all do then I know to check to switch. |
Kinda the sam here: |
The problem
The new general issue to report about tracking issues with some of the clients (connected devices)
You can report or discuss ONLY issues with clients tracking here. Or, you can report that your client tracking got fixed in some integration version (even if only for a single client, but not for all of them).
Here is what you need to say if you want your issue to be checked faster:
0.29.0
or the last commit hash if you used the dev branch directly). There is nolatest
versionit connects/disconnects regularly
and so on). Please, specify every device that has issues (even if it'sall of them
for you - this sentence sure sounds better, but does not help in troubleshooting.What data to provide per-client
wired
,2.4 GHz
,5 GHz
,6 GHz
,LACP
/link aggregation
)directly
to the main router or with any additional device in-between (e.g.aimesh node
,access point
,media bridge
,switch
and so on) and how (e.g.through an aimesh node in 5 GHz backhaul
)Example of the issue report
Another example
Why?
Because there is no way to guess what exactly does not work. If you provide as much data as possible about your configuration, the issue can be troubleshooted faster and without a need to ask 3 more questions to get all the details.
You say a device has issues -> I can try to find a similar device and check. As the opposite, you say
nothing works
- I sayOK, sure. Will be fixed eventually
Updated
2024-02-15
Total # of devices and connected clients
If your device FW supports AiMesh, the only total number of clients you should be looking at is the one provided on the AiMesh page of the device Web UI (yes, even if you only have a single device). Example:
If your device does not provide the same data on the
AiMesh
page as the one on theNetwork Map
page -> this is not the issue with the AsusRouter. It cannot be fixed. Like at all. Contact Asus support and let them now this is bothering you to have different data on clients connected in your Web UI.The text was updated successfully, but these errors were encountered: