[Jonathan Morris]

UK Sentinel wrote:

Jonathan Morris wrote:

may turn the reboot off soon and see how things go.

Would be a good test to see if you have the same issues as @dodgydrains ?

Done now, so I can monitor tomorrow to see what happens.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

Dave wrote:

Devices being randomly blocked from the Internet, iphone, ipad PS5. Sky Q complaining about not being connected to the Internet too

One thing I noticed, but didn’t mention before, was that I had some devices that had issues with Wi-Fi after a previous upgrade. The Wi-Fi settings hadn’t changed (same SSID, passcode, encryption etc) and the device was able to connect – but didn’t properly ‘connect’ (hard to explain; it wasn’t a case of the passcode not working).

By forgetting the connection and then selecting it again, entering the exact same passcode, the affected devices reconnected and worked fine. The issue never repeated itself.

Maybe it was something to do with WPA (I think I am using WPA2/3 so that might be it?), I really don’t have a clue.

My suggestion might be to try this, however silly it sounds?

From memory, it was some of my phones and an older Manhattan DVB-S receiver that needed a disconnect/forget/reconnect.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

UK Sentinel wrote:

Good news, I think the issues with @dodgydrains (protocol 0000 is buggy, dev archer) occur after a few days, so rebooting every day by passes that issue. But great news you are having no Wifi issues etc 👍

I may turn the reboot off soon and see how things go.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

I seem to be having no issues still. Touch wood.

Perhaps doing a full reset last time, before going back to 42095, has helped.. because a fair few settings reverted to default and I didn’t dare mess around with them.

(Plus, as I said, I am still rebooting every morning for the time being)

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

I was so glad to be able to get FTTP broadband and connect direct from the ONT to a router of my choice. I was with EE for FTTC, but the hub was identical and just as limited.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

My wife had no issues with Teams before the weekend and it seems to have been stable all weekend. I still have it rebooting at 4am each day, so can’t tell how it might perform for days on end. Thus far I’ve not noticed it drop to 2.4GHz on the mesh node, which is great.

(Sadly whenever I report no issues, it’s like the XT8 is sniffing out my postings and decides to throw a spanner in the works!)

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

No screams heard yet, so I think that’s a positive sign!

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

She’s got a Teams call at 1500 today so let’s see how that pans out.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

I opted to update this morning as my wife is home and so am I, and she hasn’t reported any issues – yet.

I figured I am best able to revert back if we’re both here and I can act quickly.

Fingers crossed. I’d really rather not rollback again!

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

dodgydrains wrote:

Not sure if the stutters yesterday was from the other side, but today was really good. No issues all day. One Microsoft Teams meeting was with 20+ people in my team and that went without a glitch for the whole hour of the meeting. What I will say for sure is that for me this FW is better than any official releases after 42095.

This IS more promising! I might wait a little longer to make sure, but perhaps I can take the plunge later.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

dodgydrains wrote:

Had a few micro-stutters during Teams calls this afternoon without connection dropping. As I said, I will continue testing. If it persists I will go back to 42095.

Damn, that’s not exactly confidence inspiring.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

dodgydrains wrote:

I have already updated to latest FW and factory reset. I’ll be testing teams next week. Not holding much hope but the initial setup after factory reset was quick compared to previous FW.

I’m going to wait until I find out if Teams works before taking a punt on this.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

UK Sentinel wrote:

Jonathan Morris wrote:

A simple toggle of the power switch on the unit itself fixes it every time though.

This can cause corruption over time, so should be a last resort ? I will chase ASUS again to see how they are progressing <noscript></noscript>

You can get digital timers that may be better at controlling any power spikes, so that’s perhaps an option? Doubtful it will be any worse than physically turning it on/off on the router itself.

It should certainly be a last resort. Telling the system to reboot should fix it, but clearly doesn’t. It’s more of a soft reboot and that’s not fixing whatever the issue is that lets it drop to 2.4GHz and stay there forever.

It does seem like the scheduled reboot is more successful (perhaps resets more parameters), so I’ll try this first.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

I know we’ve had Christmas and New Year, but I do wonder if we’ll get any more updates soon.

My wife has had no issues with Teams but I have had a few occasions now where the node has dropped to 2.4GHz (yellow LED) and no amount of optimising or rebooting via the app/web has fixed it.

A simple toggle of the power switch on the unit itself fixes it every time though.

It’s a bit annoying to see this issue return, but I’m now going to put back on the nightly reboot at 0400 to see if that solves the issue (even though triggering a reboot doesn’t). If that doesn’t work, the next possible solution is to use an old-fashioned timer switch to turn the power off for 10-15 minutes (whatever the minimum time is) and reboot the node that way.

Besides this, 42095 is still proving to be excellent and I’ve had no connectivity issues at all.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

Jacky Decoster wrote:

great to hear I’m not alone : same here : v 42095 rock solid. What I’ve mentionned a couple of months ago : firmware 42095 : about 72.5 mb all above 42095 : about 55 mb what did Asus cut out?

The stuff that makes it work!!

Share the knowledge

You need to login in order to vote

[Author]

Posts