Brick after adding Reboot Schedule (firmware bug)

Brick after adding Reboot Schedule (firmware bug)

21 Reply
Re:Brick after adding Reboot Schedule (firmware bug)
2025-05-21 03:46:18

  @KenoUno

KenoUno wrote

  @Clive_A Sorry, i had to begin with that... The first ER605 was send to RMA under report TL-01692 (TPLINK LATAM). The second er605, the brand new delivered today to me, failed in the RMA location in front of the guys there. The two persons there, awesome guys, try everything too. Tomorrow i will receive another one. Obvously, i will not config the Scheduled Reboot. I posted because none of us, included the RMA guys, could fix it and think it could be a good idea post the warning.

 

The team at TPLINK LATAM told me that they are going to set a lab to test if the bug affects a router under Omada Controler, if it happens in other similar models and another bunch of test to inform to TPLINK with all data. Meanwhile, they will send me a new one with the promise not to configure that Scheduled Reboot. Hope this helps.

I think the Controller is not affected by that.

Standalone does not sync with the NTP until it got the Internet. Every reboot will reset the time for it.

Controller syncs the time to the adopted Omada devices. So, that's not supposed to be an issue to for the controller environment.

The dev has been aware of this behavior. They will investigate this.

  0  
  0  
#22
Options