I don't belive it :)

It works, i got myself a new TP-link AX53, just set it up using the same SSID and password for the wireless network and everything, well almost everything connected right away. The Philips Hue bridge and the smart thermostat hub had to be turned off and back on again, but that was it. The only problem is that it don't seem to like the cable going from the modem to the router, it says it is not fast enough for optimum speed or something like that, I thought it was a cat5, I will have to check. Never had that from a router before.

I have still not gone through all the settings, but it can be via Alexa, for some reason and a app called Tether, but that requires a TP Link ID thing, not sure if I will bother with that
The only problem I am having at the moment is with the NAS, it doesn't like the fact that it is on a different IP address and for some reason won't accept my password to change it.

The router itself seems ok, The build is very shiny plastic and looks a bit cheap, nothing like the old TP-link router I have. The Mesh thing may be useful later on in the year, I can put something in the kitchen so I can get a decent signal outside, that is if the signal doesn't reach outside in the first place.

Cat 5 or Cat5e?

How about setting a MAC address-based DHCP reservation so it gets its old IP Address (but is still technically on DHCP)?

In reply to a post by broadband66:

Cat 5 or Cat5e?

Cat 5, but for the distance it should have been ok, but I have now changed it to the one that came in the box, but it is a little short, I will have a look later in my box of ethernet cables.

In reply to a post by haydnwalker:

How about setting a MAC address-based DHCP reservation so it gets its old IP Address (but is still technically on DHCP)?

I did not think of that, anyway I set the router to the same range as i used before and managed to get into the NAs, change the IP address and then put the router back to how it was, works fine now.
I forgot I set the NAS to use a fixed IP address, still strange why it would not accept my password and yet my Admin password works fine to get into the NAS UI.,
Anyway, all seems fine now, I am still shocked how easily it all worked.
There are a couple of devices on the DHCP client list that I am not sure of, like


F4B85EF050AA-mysimplelink

And there is another one with a slightly different name and a different IP address

Doing a search I found that they are ring doorbells, I don't have a ring doorbell, I have EZVIZ and that is accounted for.
I know my next door neighbours don't have them, Maybe the house across the road, but I be shocked if they can send a Wi-fi signal that far.

In reply to a post by zyborg47:

There are a couple of devices on the DHCP client list that I am not sure of, like

F4B85EF050AA-mysimplelink

That's the Nest heatlink - the box that connects to the wiring centre of your boiler

In reply to a post by Pheasant:

That's the Nest heatlink - the box that connects to the wiring centre of your boiler

So someone must have a nest thermostat, or two houses must have it. I don't, I have a passiv living thermostat

I have found out why the router gives me a message about the Wan speed, the modem Ethernet port is only 100Mb/s, it is an old openreach FTTC modem, I suppose 100Mb/s is all it needs, but it is not a problem as it only gives me the message if I go into set up on the Wan.

All working fine, certainly different from my old TP link router. When I get the shelf up in the living room it can go on there, just need to get a new drill

In reply to a post by zyborg47:

In reply to a post by Pheasant:

That's the Nest heatlink - the box that connects to the wiring centre of your boiler

So someone must have a nest thermostat, or two houses must have it. I don't, I have a passiv living thermostat

I have found out why the router gives me a message about the Wan speed, the modem Ethernet port is only 100Mb/s, it is an old openreach FTTC modem, I suppose 100Mb/s is all it needs, but it is not a problem as it only gives me the message if I go into set up on the Wan.

All working fine, certainly different from my old TP link router. When I get the shelf up in the living room it can go on there, just need to get a new drill

Sorry Adrian. I led you astray. I checked my system again with a fresh (well not so much now at 1am) pair of eyes and it looks like those are Nest Smoke/CO detectors - at least that's what they are on my network...

In reply to a post by Pheasant:

Sorry Adrian. I led you astray. I checked my system again with a fresh (well not so much now at 1am) pair of eyes and it looks like those are Nest Smoke/CO detectors - at least that's what they are on my network...

I would love to be led astray, might be some excitement in my life

Doing a search, it seems it could be anything, it is a chip that is used in a fair few IOT devices.
I thought Echo units used 5Ghz band, according to my router they are using 2.4, not a problem, just surprised, that means the only thing I have on 5Ghz is my phone. Makes me wonder why I bothered to buy a router with Wif-fi 6 on

i had a look for Mesh extenders, from TP link, some of them are more expensive than my router and take more energy than my router, very strange

I will check at some point to see if the wi-fi reaches out to the back yard, that is all I want so I can listen to music or audio books on my phone in the summer.

My 1st gen Amazon Echo is connected on 2.4Ghz but the current gen Echos are connected via 5Ghz so it may depend on how old your echo is?