@Vincent-TP 

Hello,

do you have any information on whether version 5.3.3 is stable? Is there any risk involved? Also, is it necessary to update to version 5.3.2 first and then to 5.3.3?

Thank you,

Pavel

I can confirm I have no more issues with firmware 5.2.0 when I disable ARP-to-Unicast Conversion under Wireless Settings > Multicast/Broadcast Management

I've been running this since 30th of september. 

I still haven't got any issues with the newer firmware with the ARP-to-Unicast Conversion disabled.

And ... I finally made some time to got my ER605 adopted into the controller. I had to work around the issue that after adopting the LAN-IP of the ER605 reverts to 192.168.0.1, which makes it impossible to adopt when your home network is in a different segment (my network is 10.0.0./24).

Fortunately I have 10 NIC's in the server, so I was able to set one temporarily into the 192.168.0.x range.

Strange this is, the WAN-IP of the ER605 stays as it is after adopting, so question arises why the ER605 does not use the set LAN-IP. Is this is a firmware or a controller thing ?

It would make adopting it a bit easier, especailly for the people running 1 network card in their server. 

Great work on the new Omada interface !

  @ReneS89  - not sure what your original issue was,  was you having the same problems as    @dagoosemusic in that there were devices which would not connect to wifi after updating the AP?  

because I am in the exact same position as    @dagoosemusic  .  updating to 5.2.0 stopped my iot electric heater device connecting so i had to roll back to 5.0.6.    I don't really want to update to the latest version to "test" it if it is not possible to roll it back. 

anyone have any thoughts on this?     @dagoosemusic   did you update to 5.3.x?  do the devices connect ok?   @ReneS89 did disabling that setting you mention resolve an issue with devices not connecting or was it a different 5.2.0 issue that you were having?

  @thefunkygibbon I have 3x EAP245's and updated one to 5.3.3 together with ARP-to-Unicast Conversion disabled.
I tested that for a week and then updated another one to 5.3.3 but without disabling ARP-to-Unicast Conversion.
That second EAP245 gave issues with some clients not connecting in a weird way, which didn't happen with the old FW.
After disabling ARP-to-Unicast Conversion, all was fine!
I now have all 3 EAP245's running at 5.3.3 with ARP-to-Unicast Conversion disabled and they run smoothly.

Actually, I sometimes had random disconnects of the accespoints with the old fimware and I had to reset it quite often.
I run home-assistant here and I made some automation that when it was offline, it disabled the POE port for 5 seconds and then enabled it again. :)
I think that might been because of downgrading the FW to an older version, maybe something was still stalling the EAP's.

  @thefunkygibbon I was indeed having the same issues, disconnects of clients. And the same solution.