I tried porting my v2 app to v3 (just code patching as described in the docs). However i'm met with an interface error: [upl-image-preview uuid=6b4cfe2d-afd3-403d-bf92-de418c99cd70 url=https://discuss.luxonis.com/assets/files/2025-11-17/1763416116-331108-image.png alt={TEXT?}] Due to the `depthai_sdk` library itself not being updated to use depthai v3 which would typically support `dai.InputQueue` instead of `dai.DataInputQueue`.

@"OskarSonc"#p32142 is there a guide on how to switch from robothub to luxonis hub.

Hi @"PaulCurious"#3646 , It seems there has been some confusion on our side, so let me clear it up! I'll briefly touch on some of the changes to our stack: * DepthAIv2 can only be used with Series 2 devices (OAK), and DepthAIv3 can be used with Series 2 (OAK) and Series 4 (OAK4) devices. DepthAIv3 provides a tighter integration with Hub for retrieving models and uploading snaps (previously known as events). * As a result, we are deprecating the `robothub` library, and that will remain DepthAIv2 exclusive. * Further, we are introducing a new `oak-agent`, which comes pre-installed on Series 4 devices and allows local and remote (through Hub) device and application management. * We will be deprecating legacy Hub agent, and exposing self-hosted oak-agent. This feature is not yet public, but is currently in private access preview. We are focusing on arm version first. So, to address the original question -- if you wish to already migrate to DepthAIv3, you have to drop robothub library and follow the new concept of [Oak Apps](https://docs.luxonis.com/software-v3/oak-apps/). You can also find more examples in https://github.com/luxonis/oak-examples. You can reach out via email and we can share instructions for private access of self-hosted agent. If you are not in a hurry, I'd recommend sticking with DepthAIv2 and legacy agent for a few more weeks until we fully release the self-hosted agent.

DepthAI_SDK not compatible with Depthai v3

PaulCurious

I tried porting my v2 app to v3 (just code patching as described in the docs). However i'm met with an interface error:

Due to the depthai_sdk library itself not being updated to use depthai v3 which would typically support dai.InputQueue instead of dai.DataInputQueue.

OskarSonc

Hi @PaulCurious – this comes from depthai-sdk still targeting DepthAI v2. In v3 there’s only dai.InputQueue, no DataInputQueue, so with the SDK you currently need to stay on depthai<3, or drop depthai-sdk and use pure DepthAI v3 APIs instead.

PaulCurious

OskarSonc sure but problem is i'm not the one directly interacting with those low-level api calls, its the robothub library which my application uses to interact with the luxonis hub platform. The rh library itself doesn't seem to have gotten any recent upgrade, so what's the workaround?

OskarSonc

@PaulCurious ah, got it. RobotHub was effectively replaced by LuxonisHub, so the robothub library is staying on DepthAI v2 and isn’t being updated for v3 – that’s why you’re hitting this, and why you’ll need to keep that stack on depthai<3, or switch to using LuxonisHub...

Thanks,
Oskar

PaulCurious

OskarSonc is there a guide on how to switch from robothub to luxonis hub.

OskarSonc

@PaulCurious - I don't think there is any guide, but it's mostly the same thing rebranded with nicer UI and some new stuff, so should be straightforward...

PaulCurious

OskarSonc nicer UI? when i say robothub i mean the library called robothub that interfaces with the luxonis hub platform, (i use that already). I was thinking you meant that there's a new library called "luxonishub" as opposed to the old library called "robothub". Here's what i'm talking about: luxonis/robothub

Matija

Hi @PaulCurious ,

It seems there has been some confusion on our side, so let me clear it up!

I'll briefly touch on some of the changes to our stack:

DepthAIv2 can only be used with Series 2 devices (OAK), and DepthAIv3 can be used with Series 2 (OAK) and Series 4 (OAK4) devices. DepthAIv3 provides a tighter integration with Hub for retrieving models and uploading snaps (previously known as events).
As a result, we are deprecating the robothub library, and that will remain DepthAIv2 exclusive.
Further, we are introducing a new oak-agent, which comes pre-installed on Series 4 devices and allows local and remote (through Hub) device and application management.
We will be deprecating legacy Hub agent, and exposing self-hosted oak-agent. This feature is not yet public, but is currently in private access preview. We are focusing on arm version first.

So, to address the original question -- if you wish to already migrate to DepthAIv3, you have to drop robothub library and follow the new concept of Oak Apps. You can also find more examples in luxonis/oak-examples. You can reach out via email and we can share instructions for private access of self-hosted agent.

If you are not in a hurry, I'd recommend sticking with DepthAIv2 and legacy agent for a few more weeks until we fully release the self-hosted agent.

PaulCurious

Matija thanks a lot for clearing things up. So i think i will be going ahead to use the new concept of oak apps because i already did the work of migrating to v3 in my app. However, in the docs it seems to imply that this only supports oak4 devices, i only have RCV2 devices at my disposal (specificaly the OAK1max), can you confirm that this oakctl and corresponding oak-apps will work on my setup (Rpi 5 and oak-1 max).