@Enkountor,

Thanks for bringing this to our attention, we have gotten in contact with the necessary teams and your hardware version should appear soon. I believe that we update the content on a weekly basis so keep checking if it doesn't appear at the end of the week.

To everyone else on this thread attempting to check firmware compatibility, this is the rule to follow when checking for firmware updates.

"

Please verify the hardware version of your device for the firmware version. Wrong firmware upgrade may damage your device and void the warranty. (Normally Vx.0=Vx.6/Vx.8 (eg:V1.0=V1.6/V1.8);   Vx.x0=Vx.x6/Vx.x8 (eg:V1.20=V1.26/V1.28)

"

  @bhowes,

The firmware for products are often cross-compatible with the different 1.X hardware versions, this is why the hardware version for the 1.6 displays as 1.0. When these smaller increments for hardware versions are used, it is usually a result of having the same hardware, but may be manufactured in a different facility. I will pass the feedback along to the team to see if there is a way to make this a number that would change based on the hardware it is installed on.

Usually, when the bug fixes are listed generically such as this, it is an indicator that the firmware fixes a variety of behaviors that users have reported experiencing in specific situations. Unfortunately, I do not have any further details at my disposal for this update; however, I do know that the AX11000 is one of the models that the engineering team is actively developing and releasing firmware for, as there have been a few different beta versions of firmware for the model.

  @Turk2421,

First, double check your firmware version, as a lot has changed since this thread first started. If there is a more up to date version for the AX11000 available for either the V1 or the V1.6 you have the opportunity to update your router firmware. 

When an update fails through the UI, it is most often a result of the router not being able to effectively communicate with the TP-Link Cloud Servers.  Some users have had success changing their DNS server, however I would recommend downloading the files for the firmware from the site and manually updating the firmware on your device.

Feel free to create another thread about your dropped connections, and the team can see if there is a reason/setting that is causing it to occur.


edit: there is also an early access firmware for the AX11000 that adds VPN client support, while a few users have reported that the upgrade was unstable, others have had luck with it fixing some odd behaviors. There is a forum post available for the firmware here: https://community.tp-link.com/us/home/forum/topic/590046

  @Huffmanfam,

If you used the tether app, the login for your router is most likely the login for your TP-Link ID. Make sure you try to use the credentials for your TP-Link account, rather than the router. If you are using the automatic update feature from the tether app, the firmware would have been for your device, so it wouldn't not have been an incorrect version.

Have you tried accessing the router settings through both the web interface and the tether app? While they should use the same login, the direct connection to the router may be more stable that accessing the settings through a wireless connection.

Lastly, our support ticket system and phone numbers for direct contact can be found here: https://www.tp-link.com/us/support/contact-technical-support/#LiveChat-Support

  @Huffmanfam,

Also, in case you are worried about having to reconnect every device to the network, if you configure your network with the same settings and SSID, your devices should be able to reconnect automatically or may simply require a restart. The only things that will be lost are specific settings such as IP reservations, Network Name, and Password. 

And you are going to hate this, but technically speaking, downloading a firmware from the site and transferring the firmware via USB is considered far more reliable than wireless updates, as there are so many factors that can affect a connection such as interference, or even settings on a phone that may be limiting file transfer rates. 

When a firmware update is pushed to the app, you can be assured it is for your specific hardware version. Given that your router is still working and providing connections, I believe that the firmware update did not fail, but may have altered something. Please makes sure that you cannot login to the router's web interface with the default login found on the label of the router.

For the device that you cannot reconnect to the network, try forgetting the network from the settings and then reconnecting to the wireless network. I see that in the patch notes the host name of the router was fixed for accuracy, so any devices that may be reliant on that field may be disconnected from the network