The logs show up in the `server.log` logs files from the controller which are logged to disk.  The docker image shows those logs by default.  To reproduce the "ports or lags is null" message, it's either call the API to list devices, such as `/api/v2/sites/${SITE_ID}/devices` or navigate to the devices page.  The two devices I get logs back about are my two switches:

01-07-2026 09:06:01.160 WARN [https-jsse-nio-443-exec-2] [] c.t.s.o.m.p.m.d.o.o(): Osw 98-BA-5F-62-CF-D8 with omadac 1884487c406a9ac81b80b4f25313c67a ports or lags is null.
01-07-2026 09:06:01.161 WARN [https-jsse-nio-443-exec-2] [] c.t.s.o.m.p.m.d.o.o(): Osw E0-D3-62-46-C2-9A with omadac 1884487c406a9ac81b80b4f25313c67a ports or lags is null.

    
I have two switches managed and they correspond to the two MAC addresses in the logs:

a SG3428X-M2 v1.20 (firmware version 1.20.15 Build 20251031 Rel.73964)

SX3008F v1.20 (firmware version 1.20.12 Build 20251031 Rel.75312)

  @mbentley, 100% correct.

I have an open ticket now and I gave TPlink access to my controller/site. Hopefully they will be able to tackle both issues (ports or lags is null + Lan network does not exist, OmadacId: 5c4555ae84bc2b554b180e2ead37c0b3, SiteId: 695bcb5a5fa1f14f446f6b1c, vid:0). Tnx for following this up too!