I just wanted to toss my experience in with Oak-D Pro POE cameras. I am use 3 of them overhead looking down to detect players entering the play area to trigger the activation. This is a permanent install.
If you cycle them on/off to frequently due to debugging/restarting touch they can get locked up requiring a power cycle. And just in general things can happen and you want to be able to remotely cycle power. So make sure to use a Managed POE Switch that allows you to cycle POE ports.
Of the 3 I am using, 1 is slower coming up then the others and is the one that is most likely to get hosed and require a POE power cycle. Test your cameras, replace any acting different.
I am not sure if this has been fixed but if I leave them active on save and restart the project and the cameras can’t be found it crashes. That may have been fixed but that was an issue I had. I made an execute dat that disables them on save and then another on that checks to see if they show up in the device list before activating them on project start with a small delay.
I have also had them lock up mid day requiring a power cycle. I am working on some tools to watch and automatically power cycle them if needed without restarting the TD project.
Managed POE Switch:
commandline tool for the managed POE switch I am using: