Invalid password issues with WiFi after firmware upgrade to 1.2.8 20190403 Dec M5 Hardware 1.0
After the firmware update to 20190403, some devices are unable to authenticate to Wifi with the "Invalid Password" error. However the password has not changed. After a few minutes it is able to connect with the same credentials. The phones were rebooted, wifi settings cleared and reset, the behaviour still comes back from time to time. Are we able to rollback the firmware or, get a new one to correct this issue?
Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Is that happening on specific devices where it happens on a specific phone and not on a laptop for example?
- Copy Link
- Report Inappropriate Content
I just had the same thing occur with my M9s. I upgraded to 1.2.8 Build 20190403 Rel. 43515 today.
- Copy Link
- Report Inappropriate Content
Yes, it is happenig with mobile devices iPhone, computers and other IoT Amazon echo, etc.
- Copy Link
- Report Inappropriate Content
What was the previous firmware the Deco unit was on?
Get a hold of our support team, they will assist you with updating the system that will resolve the invalid password issue.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I'm having the same issue. Is there a fix on the way?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I also tried the new Firmware 1.3.0 build 20190419 Rel 70702, the problem still there.
- Copy Link
- Report Inappropriate Content
Change the network name and the wireless password on the main network. What you can also try is to enable the guest network (Wireless Settings) to see how the devices connect to that as well.
- Copy Link
- Report Inappropriate Content
I've tried renaming the SID and changing the password, however i had to rename back to original name, as I have many devices that are using that configuiration. Since there are many users reporting the issue after the 1.2.8 upgrade, is there anythng TP-Link was able to identify as why the firmware upgrade caused this condition?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 11992
Replies: 22