@u880 My eap670 is not adopted (running in standalone mode).  No serial number in the webui either.  Tried poking around the file system in ssh, no joy there either.

Thank you all very much for your feedback. :-)

@Hank21
Thanks for your effort and testing it with the Linux Controller v5.13.22.

Indeed: until now I didn't enable Cloud Access. And to be honest: I don't want it and more important: in my environment it's not allowed that a system like the Omada controller is accessible from external systems, it's strictly forbidden according our policies. One of the main reasons for selecting TP-Link/Omada controller against other vendors is that I can run the controller locally, on my own servers (and in this case even on a Linux machine, preferably Debian, I'm happy :-)) - no need/force to use cloud services - a perfect base for my Wi-Fi management.

So may I ask: is cloud access really necessary to read this particular information from an EAP? That would be a pity.

And by the way I couldn't see any technical reason for it. All other information of the devices are readable, why not the serial number?

It would be nice if you could clarify if reading this (admittedly) special information is really only after activating cloud access - as you wrote "this issue may occur".

And if this would be the case (hopefully not): are there other features of the Omada software controller that only work when the cloud access is enabled? Again: hopefully not ...

Thanks and best regards

Hi  @Hank21 

ah, that explains it of course. OK, so no malfunction of controller and/or the EAPs - it works as designed, good to know.

Thank you very much! :-)