OC200 do not show traffice history anymore
Hello,
Recently I updated Omada OC200 controller to V6.0.0.34 firmware and I lost client traffic history.
Now is only shows 0B all the time. Previous firmware was showing this correctly

- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hardware version 2
Firmware 2.22.10 Build 20251118 Rel.34511
- Copy Link
- Report Inappropriate Content
I downgraded firmware to
2.21.7 Build 20250707 Rel.72486
and history is working again

- Copy Link
- Report Inappropriate Content
Hi @117luka_
Thanks for posting here.
Did you check the info via the Omada web interface when on 6.0.0.34? Does it display the statistics correctly?
BTW, what version of the Omada app are you using, and what phone are you using? Please make sure the APP is up to date and check again. Thanks.
- Copy Link
- Report Inappropriate Content
Hello!
I'm using Samsung S24+ and the Omada app version is 5.0.32
I already downgraded the OC200 and can't really check if the web interface was showing this correctly.
Maybe someone from the community can check this?
Thank you!
- Copy Link
- Report Inappropriate Content
Hi @117luka_
Thank you for the information provided. This is the first time we have received such feedback.
We will test again locally with the same phone. To ensure consistent test conditions, could you please provide a screenshot of your phone’s system information and a list of the SDN devices managed by this controller?
- Copy Link
- Report Inappropriate Content
It's also the same for me. I'm in 6.0.0.36 of OC200. Even wired clients is showing no history.
Phone: Realme 9 Pro 5G

However, I noticed that in the client logs, the total traffic/data usage everytime it connects and disconnects is displayed, both in the app and in the WEB UI.


- Copy Link
- Report Inappropriate Content
Thank you so much for the feedback.
Is your OC200 V1 or V2?
Do you remember the firmware version before this update? We will test more. Thanks.
- Copy Link
- Report Inappropriate Content
@Vincent-TP I'm using the V1 of OC200.
I also tried it in 6.0.0.34 before I updated to 6.0.0.36, and it's the same issue.
I didn't try it in 6.0.0.33, though, if the issue existed back then.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 124
Replies: 8
Voters 0
No one has voted for it yet.
