Hello,

Currently using ER605 v2 2.1.1_20230115

2 switches TL-SG2008P v1.0

2 Velop Linksys unit working on bridge mode as access points (still no budget for TPlink ceiling APs :-) )

Controller 5.8.4

over 50 wifi devices all with DHCP IP reservation. Most of the devices are for home automation and home security. there are around 14 wired clients, 2 of them are the 2 wireless access points which each of them add around 10 to 20 more devices.

In January I suffered the adoption loop issue on my ER605 just after upgrading the firmware that was released around that time. I did roll back and waited for a fix.

I then downloaded the beta version of 2.1.0 with the adoption loop issue resolved around Jan 18 2023. 

I then upgraded from the controller on Feb 1st as soon as the official 2.1.1 was released.

Since then my network was working fine.

on Feb 9th, there was a work at my house that required the power to be temporary cut off. After power was restored, it became an entire mess. My entire home automation was down, most, but not all, devices where offline. my phone and some other wireless devices were not connecting to the wifi. The wifi was asking for password, even though nothing has changed on the wifi or clients. I first blamed the old Velop linksys units and started doing factory restore on them, in the mean time I connected a smaller temporary access point which served few of the most important equipment and they all worked fine and that made me doubt about the health of these velop APs,  Something I noticed was that if I set the original velop to other SSID and connect my laptop and some other few devices to this new SSID, everything was working perfectly fine, but as soon I changed the SSID to the original (the same that all other 30+ devices were pre-configured), then all wifi network would stop working again, my phone would loose connection and won;t connect again. I wasted almost a full day troubleshooting the issue and blaming linksys.

Today, I digged a bit more, I thought that maybe the problem was not with the wifi itself, but with the IP addresses. I decided to roll back the ER605 to 2.0.1 and everything started working perfectly fine.

It looks like the DHCP problem appears only after reaching certain number of connected clients. When I restored the access points, it adopted the default SSID, then I connected my laptop and phone to that temporary SSID and everything was working great, as soon as I restored the original SSID, about 90% of my devices would automatically connect, but not the rest. This tells me that this version and/or setup combination that I have, cannot handle more than 30-35 DHCP reservation assignments.

Also, I probably didn't have this problem immediately after upgrading to 2.1.1 because I never restarted the ER605 after that upgrade, it only happed about 9 days later when power was cut off at home.