@MERF

I suggest using the latest beta dated 4th Feb 2021. It is better (reboots once every 2 days instead of every few hours). Let you know how you get on

@scoomby 

Unfortunately, i had CRC errors and broken internet twice today and had to reboot manually :(

Also, here's the screnshoot of ip/MAC reservation bug/issue. As you can see, 60:......:84 has a reserved ip address, 192.168.1.102 but after 2 reboot, it took another ip address, 192.168.1.113. This's so important for me because there're some settings on Home Assistant and it uses static ip addresses. If the router gives different ip, i can't see the values on Home Assistant about that device.

@naz_eg

Yes, that does look like a bug indeed.  I am using address reservation but it's limited to wired clients only and that seems to be working OK.  Like I said before, randomised MAC addresses seem to be affecting the modem router as well.  Generally, I am finding the Wi-Fi isn't 100% stable at the moment even with the randomised MAC addresses being disabled.  The modem router is rebooting less often (it runs for around 2 days before a crash/reboot) but the Wi-Fi isn't working right.  My family are complaining about a brief loss of connection that seems to occur several times a day.  I have just disabled smart mode so 2.4Ghz and 5Ghz are using different SSID's to see if that helps.  If that doesn't work, I will try disabling the guest Wi-Fi setup.  I would still like to see more communications from TP-Link so we can help them pinpoint and fix these ongoing issues.

I just had another reboot this morning.  This is just over 2 days since the last reboot so there is more work to be done to resolve this issue.  The Wi-Fi stability seems to have improved when disabling the Smart Connect which is forcing most devices on to the 2.4Ghz frequency band.  Is there an issue with the 5Ghz frequency band?  Any ideas from TP-Link?

I've just added a scheduled reboot at 3:00am every day to hopefully ensure a reliable connection throughout the day.  My son said this morning that we need a new router.  I replied that this is new router and that we've had it just over a week!!  He has a point though, this router isn't fit for purpose at the moment.

@plasmahal Driving me and family nuts all the disconnects, now put latest beta firmware on but not holding my breath on that one. Wish I had checked the forum before buying.  

@PaulPP 

me too! If it isn't resolved in the next couple of weeks, it's going back.  TP-Link need to work their magic very very soon.

I had 3 reboots in total yesterday with the latest beta firmware.  I don't understand how this unit got through qualification.  It is the most unstable IT product I have ever owned.

@scoomby 

Unfortunately :(.

Btw, did u check if CRC errors raise significantly when it closes to reboot? It passed 1 day and 18 hrs from the last reboot and the CRC error is 197 now but it raises millions suddenly.

@naz_eg 

I haven't noticed that but I will take a look at it.  I expect to find to the same thing with my router.