Just tried setting up a C325WB exclusively through ethernet and had the most confusing and difficult set up for the first time ever on a Tapo product. I've owned C110s, C310s, C320WSes, Vigi C540Ses, but this particular model (C325WB) gave me a real headache when trying to get it to work via ethernet on my local area network.

In an attempt to cut the explanations and provide the scenario, I'll try to summarize by mentioning the hardware involved. Current set up (arrows mean connected by CAT6A cable):

TP-Link ER605 (main router) --> Trendnet 5-port 10GB switch (dining) --> Trendnet 5-port 10GB switch (living room) --> C325WB

When trying to detect the C325B, it was picky with the port being used on the switch. Overall, erratic port LED blinking behavior all throughout. I verified that all ports work fine by switching my Apple TV to use each port on the switch and running a speedtest each time. On a particular port (3rd), the C325WB was finally detected. Upon firmware update, amber light on the unit only, no matter which port was used, and the camera could not longer be detected via ethernet.

- Using the exact same cable and connecting a C310 to any of the 5 ports, there are no problems. The C310 was detected. This is the same with the C320WSes.

- Connecting the C325WB to the main router, it's detected immediately and works. It fails to work at the tail end of the network, even if all other Tapo cameras work.

Now forced to unhappily use the unit on wifi mode for the meantime. I was intending to use this as an outdoor camera in an area without network coverage. I've now had to allocate another camera to fill that role.

Wondering if anyone else has run into similar odd ethernet issues with the C325WB?