Why have I lost the yearly view and comparisons on my online usage graphs?

As expected, Totodile smashed it right out of the park and was definitely the easiest reproduction so far. Totodile is the nickname of my phone. The device specs are already known to OVO which speeds things up too.

In this case I'm using Totodile with Google Chrome 90.0.4430.210. Full details are in the User Agent below.

Mozilla/5.0 (Linux; Android 11; SM-A705FN) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.210 Mobile Safari/537.36

At this point, I've now confirmed the issue exists on basically every non-Apple platform and my theory will be written up in the morning. Good luck!

I have the same issue. These console errors may help.

I’m using W10 2021H1, Edge current.

Might also be worth noting that I run AdGuard for Windows with browser integration.

Heya @knight !

Ooh! Thanks for that! This stuff can prove really useful!

I don’t think most of those Console messages are relevant in this case other than the two yellow Warn level ones. Although I use AdBlock with Google Chrome on Swampert, I have ways of making sure it doesn’t get in the way of my bug hunting and all my other devices are completely vanilla states which means that nothing can interfere at all.

It seems as if something unrelated might be messing up your internet connection somehow as you shouldn’t be getting most of those red Error level messages. Are you maybe using something like a PiHole to sinkhole stuff by any chance? It shouldn’t cause MyOVO to break as long as you don’t sinkhole any of OVO’s domains.

EDIT: Ohhh ok. I see. AdGuard for Desktop is acting like a PiHole, that explains it. But yeah, as long as it’s not blocking any OVO domains it shouldn’t get in the way. I personally use my UniFi Dream Machine for that job. :P

I’ve quickly reviewed those messages and compared them to what I’ve been getting, I suspect they’re mostly unrelated except for the yellow Warning messages but if you’re seeing the issue as well, that’s another confirmation of the bug. Can you grab your User Agent for me please by any chance? It might come in useful. :)

The easiest way to get hold of that is to simply Google What is my User Agent? and you’ll see it right at the top of the results. If you’re OK with sharing that, it’ll definitely help a lot. Don’t worry about leaking private info, User Agents never reveal anything that can identify you and they only contain basic device info at most.

Tim and Jess should be back in the morning, so I’ll ask them to feed everything back to the Tech Team who were looking into the issue.

Well, AdGuard is a very powerful and handy tool. In fact, it is so good, I paid for a family membership. So yes, using AdGuard for Windows provides OS level filtering of unwanted endpoints such as Google trackers 

That’s why I mentioned it as you are correct that the errors on things like Google analytics are because of it. But no, I’m not filtering anything to actually do with Ovo sites so it shouldn’t have any impact.

My user agent is:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36 Edg/90.0.818.66

Haha, nice one! I just like to go totally overboard and block that stuff across all my VLANs at once. I’ve literally made it so that anything on ANY of my VLANs that tries to phone home to Facebook or Zoom gets sinkholed immediately, cuz I don’t trust either of them. But my solution is clever to the point where all that stuff gets Connection Refused instead of 404. Let’s just say that the Suricata IDS which Exploud uses for this purpose is… Powerful stuff…

Apparently it’s also blocked about 37mb of Facebook traffic in the last 24 hours too. Mind you, I have also managed to burn through 36.1GB of of total traffic so far today alone and about 219GB of traffic in the last month...

Yup, that User Agent looks good to me. You’re ever so slightly behind on the updates but not by much - I always allow a 14 day grace period to catch up - but Edge Chromium 90 is close enough.

Shouldn’t take too long to fix (hopefully!).

Thanks @Blastoise186 , yes there is an Edge update waiting but I’ve had too much on to want to reboot, especially as I had some “fun” updating Windows and Office recently.

I can’t really think of anything you would be doing with the Ovo website though that would make a difference even if I were a year behind. I would hope that the website is written for the widest possible coverage. Indeed, I might expect even IE11 support for a commercial brand. Though I’d certainly give you a “let” for that if you didn’t support it 

I’ve at least now got the app working after it broke itself a few months ago (actually probably 6-10). Now that I’ve removed it and re-installed it is working again.

Anyway, thanks for the responses and I’ll keep an eye out for the update.

You’ll be amazed at what forum volunteers can do. 

Hehehe, the internet changes a LOT you know. And here’s the snag with Microsoft Edge. There’s at least, like… THREE different versions of it!

You’ve got the original Edge Legacy (aka IEdge) which first launched with Windows 10 1507 (aka the day Windows 10 first became a thing) which I kid you not… Was just Internet Explorer with a fancy skin over the top and it still effectively used the Trident and EdgeHTML engines making it IE12 effectively. I’ll probably refer to that one as IEdge in the future, since it’ll be easier for everyone else to know which one I’m refering to.

Then you’ve got the second Edge Legacy sometimes known as Edge 17 which I think came out with Windows 10 1809(?) (correcting myself, it’s actually Windows 10 1803 where Edge 17 first debuted and where it was still primarily using the EdgeHTML engine for the most part) which is the one where Microsoft started to transition to the Chromium engine, but was still very much the same Edge Legacy as before, just with very minor changes. When I refer to Edge Legacy going forward, it’ll be this one in most cases.

And then you’ve got Edge Chromium which is the new Edge that actually runs on the Chromium engine, but can flip back to Trident/EdgeHTML if you really want it to by using Internet Explorer Mode - not that I’d recommend it because you’d also bring back all the nightmares of Internet Explorer! Any references I make to ChrEdge from now on are in reference to this one.

I kinda wish Microsoft had renamed Edge when they rebuilt it as Edge Chromium (or ChrEdge as some people call it). But I guess marketing wins that battle… Again…

Anyway, the User Agent is basically one of the easiest ways for me to not only know what version of Edge you’ve got, but also which Edge you’ve got - IEdge, Edge Legacy or ChrEdge (and that you’re not using the latter with a global Internet Explorer Mode enabled somehow). 

My understanding is that OVO considers ChrEdge as a supported browser (provided you’re not using Internet Explorer Mode) based on the use of the same Chromium engine that’s used by Google Chrome, Chromium, Brave, Vivaldi, Samsung Internet, Opera and a few others. My stance is that if you break MyOVO using ChrEdge and I manage to reproduce it in Chrome or Chromium, I will always tag it with my approval as well.

As for Internet Explorer support… Umm… Not sure about that as I don’t work for OVO and I don’t know the official policy on this one. Let me play a Joker Card there and get my minions (aka the OVO Social Media Team) to do the research for me. 

It’s possible that OVO tries to support IE with their stuff, but it’s likely a low priority and I wouldn’t be surprised if any IE-specific bugs get pushed to the back of the queue. With that being said, I’m still happy to assist members with reporting such bugs anyway - subject to the opinions of Tim and Jess who make the final call about whether it would actually get submitted - but I’d also generally recommend affected members try other browsers. If I can reproduce the same issue in one or more supported browsers though, then yup. I’ll definitely ask for it to be escalated.

However, it’s worth bearing in mind that Internet Explorer is a dead browser anyway that’ll be killed off in just over a year from now and no-one really uses it much anymore. It’s also kinda less of a factor of whether OVO is prepared to support IE and more of a case of whether IE will support modem stuff like MyOVO. I personally don’t bother with spending any time creating custom IE hacks for my websites just to get a dead browser to behave on my own sites because I know that no-one uses it to visit them. If it works, great. But if you can’t use my sites in IE and I find it’s working fine in all modern browsers, I’ll simply come back and ask you to use something that’s not IE. I’m just no longer willing to spend that much time fixing things that only affect dead User Agents. 

As for the app though @knight I can safely say that OVO definitely appreciates any and all bug reports related to the OVO Energy apps, especially if they’re raised via the forum (you can go via support as well, but the forum is a little easier)! It’s been one of my focus areas and I can definitely say with full confidence that some of the recent improvements to the app are a direct result of the efforts of myself and other members on this forum - especially SimonD and TomThumb who come to mind pretty quickly!

If you do spot more issues, we’ll definitely be happy to take a bug report from ya.

You’ll have probably noticed for example that it no longer randomly restarts itself and boots you out while you’re using the app. That’s probably one of my best catches to date although it did cause another bug - the dreaded “spinning circle” one. Please feel free to blame me for that one, it’s kinda my fault that I didn’t consider that flaw in my ingenious solution! I’ve since found a fix for that one and it’s currently being considered. I just hope I won’t need to find a fix to fix the fix that broke the fix which fixed the thing that was originally breaking the app and randomly booting members out! (Phew!).

BLAM! My sheer genius has allowed me to track down a possible root cause as to why the Yearly buttons on the sidebar don’t work as expected on the new tabbed view, and I’ve also got a suggested fix too.

Given that Monthly seems to work fine in all cases, it looks like the bug with this one is related to where all the links lead to. I can understand why it’s like this if there’s A/B Testing going on and one of the two sides still has the legacy view though, since you don’t want that to break!

However, the bug seems to be related to the fact that in the new view, the Monthly option in the sidebar always initially pulls up the current month (or the previous/most recent month where data is available if there’s no data for the current month yet). Some clever magic seems to dynamically update that link automatically to match the current month whenever the date rolls over. However, Yearly still points at the old URL and this one redirects to Monthly right now in the new view. So in effect, Monthly will lead you to Monthly as expected, but Yearly currently leads to Monthly via a redirect. Easy fix though.

There definitely seems to be logic that’s been applied to Monthly for this, so the fix would simply be to apply the same logic to Yearly - but with a very slight tweak that points at the current year rather than the current month. 30 second fix perhaps?

I don’t know when this fix might be able to go live as it depends on whether anything else might break. But I’ll definitely leave my thoughts here just in case they’re useful. :)

Wow - thanks for some really detailed bug reporting there - @Blastoise186, @knight and @MBA  !

I’ve sent the team a link to this thread as you’ve explained the issue better than I ever could, so will pop back once I’ve got an update. 

Hope we can get this pesky issue resolved soon for your all!

Heya!

It’s hard to say if this one’s a bug report or a feature request, so I guess it’s time for a hybrid!

This is related to the thread below, please check there for more info - I’ll also be posting a link in that thread which leads back to this one as well due to them being related.

One thing I have noticed is that the one-at-a-time arrow clicking method in the new Usage views is great for rapidly jumping from one year to another, but it really doesn’t work that well if you want to jump between days or even several jumps in one go. I can use hax to get around it by fiddling with the URL to punch in exactly what I want, but it’s not ideal to fast-jump that way.

It would really help if there were additional options added that would allow me to jump more than one step at a time both in MyOVO and the OVO Energy apps, especially to reduce fatigue from repeatedly clicking the same thing and to reduce server load a little.

Ideally, it would be great to have these added alongside the existing options, so that it preserves backwards compatibility and maintains the ease of rapidly jumping forwards and backwards one step. But a more rapid option for larger jumps would be nice!