@Joseph-TP 

Thanks Joseph, I got an automated reply showing me how to collect logs with nothing to do with the problem, I already gave them a test bench set up to try in house and it seems to have been ignored, I think I'll just not bother with the app anymore and probably switch sides when I go shopping for a W7 router, the lack of FW publishing has not been seen well by me given recent news in another country regarding certain things without going into it too deeply here.

Many thanks for your assistance anyway.

  @Joseph-TP 

Hi & sorry I've been late back on things,

The two suggestions you left me are exactly what I tried first already,

The app cache I cannot see a way to clear it on ios not in the app directly or in ios settings for apps anyway, I always allowed the app permission to chat anyway and that is still enabled as on,

I've got no problem with Tether if I hook the different model AX into it it works fine then with a full 32 character PW,

I'm going to feed the other AX router PW into the AX73 next to rule out some sort of character glitch/rejection within the PW I use on the AX73 although I've used a few removing the characters it might reject as unsuitable but as the set up page in a browser doesn't reject it I can't see why Tether would reject it,

As it was an OTA upgrade on the AX73 I still think the issue could be the FW hasn't fully installed properly which could be ruled out simply by making the FW available to download from the support site, have you nagged them to publish it? and if so why haven't they?.

Kind Regards,

Bogle.

Ok tests complete,

I removed any & * % ! ? symbols I may have been using and still it rejected the PW even after a reboot of the router,

I then found this from 5 years ago and seem to remember having the same issue that was an issue but on a different router as I didn't have an AX73 back then.

Tether app reports router password incorrect when it is not. - Home Network Community #37 user Mister.Lang

So I try the 15 character password and bing! I'm in again, I actually had it working a 25 character in the beginning but it rejected that eventually.

I've got one more test to do and that's to change the password in various browsers on various devices incase one of them is doing the trunking as I seem to remember having this issue before and then as if by magic it righted itself.

Kind Regards,

Bogle.

  @Joseph-TP 

Well all testing done and tbh so am I,

I don't really expect to have to be the tester when this fault is over 5 years old now without any resolution, I've now asked for the latest FW to be available for download numerous times without any success, I notice another user has also asked for FW's that only seem to appear through Tether and not the support page.

Anyway the latest lot I did for you were to switch off of Edge on a different machine and use Chrome instead like I have many times before but as I was using a vanilla Windows at the time I used Edge.

So I used Chrome (not that it should really matter) which as usual failed when I logged out and went to login through Tether, re-boots inbetween, I then thought hey perhaps Tether stores passwords with the 192.168.x.x and that's why it's not having any of it, so I make a new 192.168.x.x number up and also a new password, guess what? "Login Failed".

I cannot waste any more time on this, the fact there seems to be a reluctance to publish the FW and that it works with routers on older FW's screams there's a problem in the FW and if it's taken me this long to get to this stage what hope is there of fixing it, the standout issue seems to be the password being typed into Tether isn't making it to it's full character set when the user hits login after typing in the full password, it's being trunked at 15 characters.

Anyway for you personally I thank you for trying to assist but for the company it just lost a long term customer.

Double posting.

  @Joseph-TP 

Thx Joseph it's the FW issue more than anything, not being able to re-flash at will has put me right off if I'm honest, I noticed Tether got an update recently on the phone, I'll see if it now accepts the password but I don't feel it will as I'm almost certain it's something in the router FW hence why it's done this in the past and then resolved itself without any interaction between FW releases.