EAP653 with firmeware 1.3.2 and EAP653UR with 1.4.1 block Sky Puck and MyEnergi Eddi
EAP683 | EAP653 | EAP650 Pre-releaseHello,
I found a very strange situation.
Recently I got a ER7212PC v2.0 and a EAP653. Al was smooth and working great, but after a few days I saw my Sky puck wasn't able to work using WiFi (signal 'excellent' and connected to Internet, but showing the 'no connection' error in the main screen). I gave up and used a PLC adapter and connected it using Ethernet cable.
Then I noticed that after rebooting my hot water diverter 'MyEnergi Eddi', it was perfectly connected to the WiFi, responding pings from the lan, but unable to connect to MyEnergi servers. After many tests, MyEnergi decided to send me a new device to replace the installed one.
But in the meantime, I changed the EAP653 for a EAP653UR brand new, and being basically the same, I just replaced one with the other, and after a few minutes the ER7212PC had propagated the configuration and everything was working fine ... included the Sky puck and the Eddi. Strange.
This morning I got a message from the Omada app informing me that there was an available update for the EAP653UR (1.4.1), and I installed it immediately. And Sky ouck and the Eddi stopped working again.
I rolled back the upgrade, back to the 'factory default' 1.2.1, and voilá, everything working fine again.
Thinking on this, I remembered that I upgraded the original EAP653 from the 'factory default' (I think it was 1.2.1) to the newest one (1.3.2), more or less when the problems started. So I am guessing that both 1.3.2 for EAP653 and 1.4.1 for EAP653UR are introducing something that is blocking Sky and MyEnergi services, but I have no idea what can it be.
I read the release notes, but can't find anything that looks like the reason for the problems.
I know it's a very long shot, but did anyone find a similar problem? Any idea of what kind of tests I might perform to identify what is the root cause of the issues?
Thanks a lot in advance.
EDIT: tested with beta version 1.5.50 (EAP683 | EAP653 | EAP650 Pre-release) and same issue.
I have packet captures in both scenarios working/not working, in case someone want's to take a look.
@JesusM I tried that but it failed to roll back. After some digging I see that I can't rollback without contacting customer support.... So now im stuck on this version. I see you are using UR and I am using EU. So we might see different results. Once this gets fix I'm going to think twice about upgrading again. 
