NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi Traffic Meter stopped working
In the last several days the Traffic Meter on my Netgear Orbi system mysteriously stopped working. All entries reverted to zero even though I have traffic flowing every day. I googled the issue a...
Maybe I'm missing something but there seems to be a simple work-around for this.
Turn off DST and then select a time zone that gives you the correct time. That will provide traffic and the correct time. Come November when the time changes back, you can just adjust your time zone back to the correct zone for your location.
I have an open ticket on this since it was first reported. Then NG closed the ticket thinking it was a duplicate. I reopened it and it is still at L2 support awaiting escalation to L3. No ETA. Based on history, I would not expect a fix any time soon.
Well I guess Orbi fixed the traffic meter. Lauching the Orbi app in IOS still turns on the DST option but the traffic meter continues to work now. Apparently it was a back end server problem since no firmware was needed to fix this.
Yaaaaay! I just confirmed that it is working for me also.
Thanks for the heads up!
- Perhaps because it is now April? I know of no "back end" server involved in traffic measurement.
- Don't think it has anything to do with April. Mine didn't work on the 5th but started yesterday, April 6th. It's obviously something Netgear controls since my firmware remains 2.5.1.8. There was an Orbi IOS update yesterday and I noticed that launching the IOS app still resets my timezone and DST but now the traffic meter works. The act of turning on DST was killing the traffic meter. Now it doesn't.
This is fun. I turned on "Daylight Saving Time" and my Orbi Traffic Meter continues to function. I am using the default Netgear time server. (Do not recall if I experimented with any other NTP servers back in March when the issue came up. I defiinitely disabled DST back in March in order to see Traffic Meter stats.)
I remain skeptical that Netgear did something "on their end". The Network Time Protocol contains no information about local time zones or Daylight Saving Time: https://en.wikipedia.org/wiki/Network_Time_Protocol There is code on the user device which calculates local time from Coordinated Universal Time (often called Greewich Mean Time) :https://en.wikipedia.org/wiki/Coordinated_Universal_Time
I think there is a coding error in the Orbi product that messes up Traffic Meter counts when Daylight Saving Time changes and somehow "cures itself" after a number of days elapse.
Are you using stock FW? Just curious.
CrimpOn wrote:This is fun. I turned on "Daylight Saving Time" and my Orbi Traffic Meter continues to function. I am using the default Netgear time server. (Do not recall if I experimented with any other NTP servers back in March when the issue came up. I defiinitely disabled DST back in March in order to see Traffic Meter stats.)
I remain skeptical that Netgear did something "on their end". The Network Time Protocol contains no information about local time zones or Daylight Saving Time: https://en.wikipedia.org/wiki/Network_Time_Protocol There is code on the user device which calculates local time from Coordinated Universal Time (often called Greewich Mean Time) :https://en.wikipedia.org/wiki/Coordinated_Universal_Time
I think there is a coding error in the Orbi product that messes up Traffic Meter counts when Daylight Saving Time changes and somehow "cures itself" after a number of days elapse.
- Sorry don't buy it. My traffic meter was broken for weeks and never fixed itself after a few days. In fact I hated it that Netgear would just override my time settings and change them. They are still doing that but at least the traffic meter is working.
Jetdrive wrote:
Sorry don't buy it. My traffic meter was broken for weeks and never fixed itself after a few days. In fact I hated it that Netgear would just override my time settings and change them. They are still doing that but at least the traffic meter is working.I don't understand the need or interest in traffic metering
who cares just work.
FURRYe38 wrote:Are you using stock FW? Just curious.
Yes, this is stock Orbi firmware 2.5.1.8. I have a separate RBR50 that I sometimes load up with Voxel's firmware. To be honest, with my load being on the "light side", it is hard to detect any difference between them. If my load were higher, or if I wanted to run a VPNClient to mask my internet traffic, Voxel's would be superior. Also, my opportunities for "experimentation" have dimished with the internet connection being so critical to daily life.
Jetdrive wrote:
Sorry don't buy it. My traffic meter was broken for weeks and never fixed itself after a few days. In fact I hated it that Netgear would just override my time settings and change them. They are still doing that but at least the traffic meter is working.My observation is that back in March when people began commenting about Traffic Meter, I looked at mine and saw "all zeros". So, I disabled automatic DST, and the Traffic Meter shows stats. I made a mental note that it would be interesting to check again in April, and promptly forgot all about it. When today's comment showed up, I repeated the experiment. Activate automatic DST, and Traffic Meter has stats. So, the specific issue I had has indeed "gone away". Note that I almost never use the Orbi App, and when I do it is the Android app, not the iPhone app. If opening an Orbi app makes changes to the Orbi setup without my control, I would be seriously unhappy.
I also agree with Retired_Member that in these days of massive data allowances, Traffic Meter seems anacronistic. I do recall several forum members who were seriously interested because their Orbi was going over their 1TB monthly allowance and they were frantic about finding out what was causing the excessive usage. One went so far as to purchase a router to front the Orbi with custom firmware that would keep usage statistics by device!
Ok, was wondering. Ya I agree, Voxels FW would be better. I presume some of this back end packages would help the FW be more stable.
I haven't noticed much differences between stock and voxels other than the extras on Voxel's that I have been playing with. Nice to have some flexibility.
If there was a back end issue on the NG side, we have seen a similar issue with Orbi AX back on 3/9. Something broke in the FW updated that NG released. Everyone thought it was the FW, however NG said it wasn't, it was something to do with there Cloud system that for unknown reasons is tied to the FW service. After they fixed it on 3/19, the same FW that users complained about started working. So it's not just only FW that can be a problem. :smileyfrustrated: Possible that NG fixed something on there side for this Traffic Meter problem. Maybe someone can give some feedback from those who filed a support ticket.
CrimpOn wrote:
Yes, this is stock Orbi firmware 2.5.1.8. I have a separate RBR50 that I sometimes load up with Voxel's firmware. To be honest, with my load being on the "light side", it is hard to detect any difference between them. If my load were higher, or if I wanted to run a VPNClient to mask my internet traffic, Voxel's would be superior. Also, my opportunities for "experimentation" have dimished with the internet connection being so critical to daily life.
