Please note that the popular TP-Link Archer C7 v2 is affected by a bug or two which drops 5Ghz WiFi performance significantly. Some people are reporting the link quality is so bad even SSH is unusable.
As always, back up your config, and make a note of your working firmware before upgrading. I’m going to sit this one out for a bit :).
Life pro tip: make sure you are only paying the ISP for the bandwidth you can actually consume. Don’t pay for 600mbps when you can’t even use that speed.
Comcast was more than happy to charge me for a half gigabit for several years. All the while the modem I was renting from them only supported like 200mbit.
...and also your phone ROMs, if you flash them. And drivers. And everything else you need to operate your devices.
I have a Moto G2 a.k.a. "Titan" (2014), flashed it to LineageOS, bricked it three years ago, got another phone, recently checked it out again, and couldn't download LineageOS for it anymore.
Luckily, MicroG still had a ROM for it, and now it works fine, but I'd've preferred the pure LOS version, as it runs Android 7, on which Google Play Services is not an absolute necessity (with Android 8, you need it to get push notifications).
I believe I can still get the source code for it and compile it myself, but I've never done that for an Android ROM before, and I'm not particularly keen on trying that out now.
My point being: Your devices could, in theory, live forever, but the files for it (ROMs and drivers) may not always be available, and knowing the internet, won't.
In my field (industrial IT), it's not uncommon to still have PCs running on Intel Core2 systems, but more and more vendors are dropping the product pages and driver files for them. Pentium 4s are also still being used, but good luck finding drivers for them.
They switched to ath10k-ct[1], a patched version of the ath10k driver and firmware. If you run into issues I think you can use the package manager to switch back.
There’s a number of hardware revisions of this particular router, and the origin of the bug(s) is not yet identified. Maybe it only affects specific configurations, or specific hardware revisions using certain configurations.
As always, back up your config, and make a note of your working firmware before upgrading. I’m going to sit this one out for a bit :).