EAP225 outdoor won´t mesh via WiFi in Omada network after having worked - hardware failure?
Network
Until recently: Gateway->cable-> EAP225 indoor -> WLAN -> EAP225 outdoor meshed, with an Omada software controller on a Windows PC.
Recently I purchased a second EAP225 outdoor to extend WiFi over the whole garden. A mesh-WiFi connection between the first outdoor EAP225 and the new one should be established. Started to work ok and could be seen "connected" in the Omada controller software as expected.
2 days ago I changed the LAN cable from POE adapter to the new EAP225 to a cable suitable to outdoor use. Checked function, worked ok. Checked the connection with my phone, could watch Youtube. Network speed test found the access point and tested the network speed. Everything ok.
Yesterday I noticed that there was no WiFi network in the area of the new access point. The new EAP225 was not working, seen as "isolated" in the controller, i.e. disconnected. The device was a bit warm, so power probably ok.
I took the device indoors and did these checks:
1. Exchanged LAN cable between POE-adapter and EAP225 - did not connect to the mesh via WiFi.
2. I connected a LAN cable (connected to my home network switch) to the LAN socket on the adapter - now the EAP225 was seen and finally connected.
3. I updated the firmware of the new EAP225 via this cable via the software controller. Worked fine without problems. I updated the software controller to 5.6.2 from another 5.X.X version, no problem.
4. I rebooted the new EAP225 with the LAN connection and again it was adopted into the Omada network as "connected". So it definitely was not bricked during the firmware update.
5. Then I turned off power, removed the LAN cable so only the POE cable remained. Omada controller could not mesh the access poitnt. "Isolated".
6. I did a factory reset on the EAP225, connected it via LAN to my home network - worked ok, adopted to the mesh.
7. Again I turned power off, removed the LAN cable, left only the POE cable and powered on. No mesh possible again via WiFi to another EAP225
Attached downloaded device info
My conclusion is that this can only be explained with an isolated WiFi failure.
Any other explanation?
Before returning it to the dealer - any idea what else I could do?