This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.BUG: Some WiFi clients not showing in Omada clients list
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi community.
I've just tried the search engine to find out why some WiFi clients, which are confirmed to be connected to the TP-Link EAPxxx devices, are not listed in the Omada Controller's client list. It looks like this is a commonly reported problem. I made a similar observation in my network installation too. I have 3 EAP225-Outdoor wired connected to the IPS Router. All APs are adapted in my Omada Software Controller. There are around a docent of WiFi clients only.
The problem started after I made a complete restore of the Omada Controller from previous backup. I wondered - why suddenly some clients do not show up in the Omada client list. Restarting of the APs and the Omada Controllers didn't solved the problem.
However, when I only did a restore of just the settings, all clients were listed again.
That's very strange and disappointing. To me it looks like the content of the full backup, or the restoring procedure is causing the problem.
Perhaps this observation will help developers investigate the issue further more.
Cheers
Scalar
Hi community.
The story continue:
Today I updated the Omada software controller to the current version 5.9.31.
Unfortunately the situation hasn't changed and many of the WiFi clients still don't show up in the client list.
Since I had some free time today, I took another look at the problem.
I looked at the entries in the 'Insights' section. However, accessing this section was very laggy. When the content of the known clients was finally listed, I noticed repeated entries for the same client (MAC address). MAC addresses of those clients that no longer appear in the list of connected clients. When I tried to 'forget' the entries I got an error message: 'General Error'. That's very strange. ioannis compet also observed this, as he reported here: Omada 5.x clients not showing.
I discovered that Omada creates two log files: mongod.log and server.log. In server.log I found a lot of ERRORs and java exceptions, just concerning the unlisted clients.
I exchanged the sensitive data with '*'.
The following is a representative of the log entries.
The log file is full of such entries, which are repeated over and over again, with the MAC addresses of the affected clients. This could also be the reason for the delayed listing of 'known clients'.
Unfortunately I was not allowed to post the log-extract in the body of the message as it have been labelled as 'Content or title contains illegal external links.' ?? I guess due to the java exception lines. This forum lacks the ability to post a quell-text.
A file upload also didn't worked for me - I got a message: Failed to upload.
O.K. here we go - the screenshot.
As I wrote in my first post, the problem appeared after a recovery process.
I hope this can help to debug the problem. Maybe someone could pass it on to the developers and hopefully we'll get a bug fix soon.
Cheers
Scalar
@Shoresy Hi Shoresy, thanks to confirming same issue. I have good news 
I got this message from Support team: The issue has been located and will be fixed in the subsequent firmware update.
But - there is still work in progress on finding a way to temporarily disable certain feature in the configuration of these clients, which caused these clients not to appear in the 'Client List' due to a bug. In worth case we will have to 'forget' these clients. At the moment we still got the Message 'General Error'.
Cheers
Scalar
