Deco update failed during confirmation
My main Deco is BE85 and configure mesh network with another BE85 and XE200.
I used to be able to update Deco via iPhone application, but recently (maybe for 2 weeks to 1 month?) it continuously failed during checking update (after the arrow rotate, it says "couldn't confirm")
I tried to reset all Deco and create another network to try, but no luck.
(I already tried to restart Deco, modem, etc.)
I called support but he said it's hard to solve.
Does anyone have same situation? If yes, how to solve it?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, Can I have a picure of the error message?
After that, please refer to this link to help me submit the Deco APP log:
Please go to Deco APP>More>Advanced>DHCP Server to change the DNS to 8.8.8.8/8.8.4.4 to see whether it made any difference.
After that, have you tried to log into the web UI and check whether it is able to detect the latest 1.0.14 firmware?
By the way, you could also try to manually upload the 1.0.14 bin file to the web interface:
How to Update the Firmware of Deco
Thank you very much and best regards.
- Copy Link
- Report Inappropriate Content
@David-TP Thank you very much for your instruction. I could update firmware manually via Web.
The issue still not resolved yet. I usually use mobile app, and it shows an error.
Let me attach the error picture, but it's not Englsh, it's Japanese.. But hope it helps.
- Copy Link
- Report Inappropriate Content
Verify that there is a stable connection between the Deco BE85 units and the XE200. Check if they are properly connected and communicating within the mesh network. If all else fails, you may try performing a factory reset on your Deco BE85 units. This will revert the devices to their default settings. Be cautious as this will erase all configurations, and you'll need to set up the network again.
- Copy Link
- Report Inappropriate Content
@benisfroms Thank you for your suggestion. But it's hard for me to reset and re-configure because I need to re-connect all of my devices to wifi, IP reservation settings and so on. (I switched main BE85 to another one and re-configure yesterday, then just set all setting back..)
I will update firmware manually every time. The other function except firmware update works well.
The connection between the units is good and no problem.
I just check the logs and found that there're many ntp error (filtered by critical)
Wed Sep 27 14:08:51 2023 user.crit : ntp check error!!!; errno(2): No such file or directory
And date/time is not correct even though I set correct timezone.
Current Time: 2023-09-27 3:53:30 PM
Is there any way to set ntp server, or login CLI?
- Copy Link
- Report Inappropriate Content
@Shogo I tried to downgrade BE85 firmware from V2_1.0.13 Build 20230927 to V2_1.0.11 Build 20230830.
After downgrade, it worked fine. I could show the firmware upgrade confirmation via mobile app, and the time is now correct.
I think this is a bug of newest firmware. I will keep using previous version of firmware for a while.
- Copy Link
- Report Inappropriate Content
Hi, thank you very much for the update.
I saw you mentioned the wrong system time and there was a similar feedback a few weeks ago, and the user is also in JP.
https://community.tp-link.com/en/home/forum/topic/643450
Is your internet connection type also IPV4 over IPV6? Can I have your internet service provider as well?
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
@David-TP Yes, connection type is v6 plus (ipv4 over ipv6). The service provider is GMO. I don't want to set WAN DNS to 8.8.8.8, so I hope it will be fixed soon.
- Copy Link
- Report Inappropriate Content
@Shogo I just set 8.8.8.8 for testing purpose. It's solved system time issue, but it's not solved update issue. Just for your information. (Set 8.8.8.8 for primary DNS address in DHCP configuration. I couldn't set primary DNS in internet connection type setting because there's no way to set it under v6 Plus.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 772
Replies: 8