@Shaun_L 

I don't have this problem yet, because my Note 10 plus and Note 9 is not updated yet to Android 10. So if that is so, I better hold off until TP link indeed makes a Firmware update for that. 

However I have trouble to get my IFTTT to work with my router. I have authorised it and bound to it, but whatever I do it does not give me the option when in the Applets or IFTTT options to get to choose my router ID in the pull down menu. I have tried every possible option, it just does not show the Router ID in the list . How is that going with you ? Have you connected it with IFTTT ? I want to see some messages or email when a new device is added. 

Secondly I am struggling to understand 2 menus in the Firmware. One is in the DHCP server regarding reserving mac addresses the other in security, Access Control and DHCP Reservation Binding. I don't know if those do the same thing. Or the Whitelist does the same thing. Because it seems you can't use both at the same time it appears to me. Any suggestions ?

Kind Regards,

KJ

@KJILM123 

Havnt tried working with ifttt yet. I just setup the basics wirh ax.

Ive been continuing to test this glitch and always comes up the same. As soon as a galaxy s10 gets in range of the ax3000 and tries to connect, it crashes the whole network.

We have one s10 not updated yet and it works without issues. The note 9 and note 10 should be exactly the same as the s10 series.

I bet when you get your update it will kill your router unless you disable ax.

Its sad the galaxy line in general is the most popular line of cell devices on the planet and this router is now becoming incompatible. 

@Shaun_L

 Looks like others over at android central are also reporting this issue so it looks like im not alone.

In a few weeks the remaining s10/+ note10 will all be android 10 and this is gonna  be a disaster.  Hope they fix this asap.

@Shaun_L 

I am talking to support about it, they will now look into it. 

Problem started here also after my Samsung Galaxy Note+ updated a few days ago.  Whenever I leave the AX3000 coverage area and then return, I get the "cannot get IP" error on the phone so I  must reboot the AX3000.  It will then allow the phone to connect.  After the reboot I'm fine until the next time I leave home and return.  I've tried all the steps I've found in web posts but the problem continues.  I've tried the various reboots holding the volume up and down buttons with Power button, cleared cache, reset network, changed phone name, forgot network, etc...    All was fine before the update. 

@mr-b 

Have you cleared the cache? Did you disable the 2.4ghz ax and drop 2.4 to n mode? That was the only wsy i could get 5ghz ax to work. Our router unfortunately doesnt have an 2.4ac mode or at least i couldnt find it so performance suffers like crazy on 2.4 channel.

Somehow 2.4ax is interfering with 5ghz in the router like its somehow overloading it.

Definately a huge bug because really the average person should bot have to figure out to clear there cache or turn off ax capabilities on 2.4.

If none of my methods worked, did your problem clear up dropping back to ac mode on 5ghz and n mode on 2.4?

@Shaun_L  I cannot get my s10 plus to connect to my ax3000 at all. It never has and I have tried everything from a factory reset of the phone to a complete factory reset of the router and IP reservation.  It just won't connect.  I am with you compatibility is a huge issue with these devices.

@streghan13 

You should be able to get into it to get it working. Use a paperclip and reset the router again holding for 10 seconds. Once finished unplug the router completely for 10 seconds. Finally turn it back on.

You should see at least 2.4 wifi or 5ghz wifi popup for it. Make sure your phone is close proxiamity. attempt to connect to the router and then load up the browser on your phone and type 192.168.0.1 (my preference is chrome from app store).  It should get you into the initial bios setup. Bypass the setup entirely and head straight for the advanced wifi settings. Disable ax on 2.4 and 5ghz and then save. It should work.

Its horrible we have to do this to get it to work. I was able to get my AX working on 5ghz as long as 2.4 ax was disabled.

TP-Link is someone working on this fix? Still no bioses released as I check almost every day and I'm still stuck on the october 2019 release.