With --debug on, so you see mentions about T310 in the log output? If you don't mind, please follow https://python-kasa.readthedocs.io/en/stable/contribute.html#contributing-fixture-files to help us with missing fixture files. This should also drop one for your T310 if it's detected correctly.

There's no mentions about my T310 in the debug output. For context I only have two devices paired with my H200 atm - D230 and T310.

I've tried getting the fixture files, however there were a bunch of errors. Attached is the output from running python -m devtools.dump_devinfo and the output from running kasa with the --debug flag.

debug.txt
dev_dumpinfo.txt

Looking at the debug.log, the getChildDeviceList (and getChildDeviceComponentList) response contains only a single element (for that doorbell camera) even when it says sum: 2 indicating that there's another device connected to it, so that's the reason why it's not visible. Now, how to fix that, I don't have any idea, sorry.

On why the dump_devinfo is failing (with handshake failure even when the cli tool works), @sdb9696 might have an idea on that.

@andrewome could you try out a PR I've just created to try to address this. The easiest command unless you want to checkout the source is:

uvx --from "python-kasa[speedups,shell] @ git+https://github.com/python-kasa/python-kasa.git@feat/smartcam_lists" kasa --host <ip address> --username <your username> --password <your password>

@sdb9696 The T310 is being listed under the children now. I've attached the --debug logs for good measure.

debug_log.txt