I didn't say "it doesn't work," you said that. What I described is far more detailed, that demo samples consistently crash with "device not found" style errors if I execute them without breaks. If I run them in a debug mode, slowly stepping through the lines of code, things usually work.
You say, "Note also that exception handling/reconnecting is outside the scope of the depthai API library, it could be added either by user, and it might be added to depthai SDK."
Well, that doesn't really make sense. You're saying that internal to depthai-core there is zero error handling? So any little packet error (which is commonplace) will cause connections with the device to fault? If true that would validate what I'm saying/experiencing. You're saying the connection protocols (xlink) are inherently unstable and will constantly throw exceptions?
I am using 2.21.0. Looks like this latest version came out just hours ago. Skeptical that will address what I'm seeing but will upgrade and give it a go.