Hi - small residential network with 2 R650 APs, 3 SSIDs: 5G, 5G guest, 2.4g IOT.
The problematic devices are the Eufy S330 Floodlight Camera 2 pro of which we have three. These are hard wired, always on devices but, they can be powered off and on using a switch (like any regular light). These devices work flawlessly on FW 200.16.7.0.402 and 200.15.6.212.27. The problem is that on both FW 200.17.7.0.139 and 200.18.7.101.244, all three of these devices suffer from an intermittent failure to reconnect to WIFI following a "soft" reboot (soft reboot meaning the device automatically rebooting itself or, manually commanding the device to reboot itself via the Eufy app). Notably, a "hard" reboot of these device always results in the device connecting to the WIFI without any problem and remaining connected until another failed "soft" reboot occurs (hard reboot meaning total power off / power on of the device). The devices are connected to a dedicated WPA2 2.4g only SSID using auto ch (1,6,11 only) and channelization of 20. With the 200.17 and 200.18 FW, I have tried every variation of the AP and SSID settings I can think of but the intermittent reconnect failure always remains.
The problem is these devices will reboot themselves overnight every few days which, according to Eufy, is done intentionally to maintain device stability. The result is the devices are occasionally found offline due to their failure to reconnect to WIFI following the automatic reboot. To rejoin the WIFI, the device must be momentarily powered off and then powered back on.
I am at a loss to understand why these specific devices work just fine with 200.15 and 200.16 FW, but have the intermittent re-connection issues on the 200.17 and 200.18 FW.
Any suggestions please?
EDIT: added troubleshooting screenshot showing a re-connection failure after soft reboot.
Here is a screenshot showing the end of a troubleshooting trace I ran where I reproduced the re-connection failure. This was on the fourth consecutive soft reboot of the Eufy device - the first three the device re-connected OK. On the fourth, it just sits on the 802.11 authentication request step, as shown. The entire third reboot sequence, which is successful, is shown in its entirety as well.
