Setup fails with Oak 4 S

MatteoL

To attempt solving the issue of Oak4 S and IMU I factory reset my camera. However, once it turns on and the LED is "breathing blue" it can not properly configure. In particular, after showing it both the offline and online setup through the QR code at https://setup.luxonis.com/, the camera rejects the setup blinking red. On the other hand, every command through oakctl ends asking me a password, even oakctl setup. In details, oakctl setup … copied from the setup page fails with

oakctl command failed:
   0: Failed to authenticate RPC client with password

I have tried connecting to the camera both via IPv4 and IPv6. Luxonis OS was at v1.15.0 before factory reset and oakctl is at v0.13.2.

Thanks,

OskarSonc

Hey @MatteoL — flashing red = setup failed (or power mismatch). Since it worked before, it’s likely a setup-state issue.

Please do a full hardware reset: hold the rear button ~10s while powered; LED blinks orange (~5s), keep holding until it blinks red and turns off, then release. It should reboot to breathing blue (ready for setup).

If using CLI, run the exact oakctl setup from the page but add -d <device-ip> so it targets this unit.

(Also double-check you’re on PoE+ (802.3at) power.)

Thanks,
Oskar

MatteoL

Hey @OskarSonc, after full hardware reset the issue persists. The QR code setup makes the camera blink red. On the other hand, the command line setup asks me for a password

> oakctl setup -d fe80::d202:66fa:6e48:ad38 --static-ip 192.168.127.10,255.255.255.0,192.168.127.1 --app-config "{}" --agent-config "sc=8LBYAQ" --dont-check-internet --time-zone Europe/Rome --time "@1756919651" --enable-error-reporting --peripheral-mode
Agent ip changed from "172.26.15.137:9998" to "[fe80::d202:66fa:6e48:ad38]:9998"
? Camera password

I used the IPv6 of the camera as there is no DHCP in the network by looking up the packets in Wireshark. Yesterday I tried with attaching a DHCP that provided the IPv4 address 172.26.15.137 but the deviced asked for a password anyway.

The camera is attached to a DC PoE switch supporting IEEE 802.3af/at, namely the Exsys EX-62020PoE.

I received the camera in June and I update the OS to v1.15.0 through OS Update.

OskarSonc

Hey @MatteoL

Could you try the camera password you set during setup when oakctl prompts?

You can also SSH in to inspect the device, here is how to:
https://docs.luxonis.com/hardware/platform/deploy/oak4-deployment-guide/#OAK4%20Getting%20Started-Advanced-Direct%20access%20to%20the%20device

Once in, check the OS version if it isn’t the latest—update the OS or reflash, here is how:
https://docs.luxonis.com/software-v3/sw-stack/luxonis-os/

Thanks
Oskar

MatteoL

I have never managed to complete the setup since the factory reboot. So I have never specified any password. By sniffing the mDNS packets I read:

Name: 761681342._oakagent._tcp.local
.000 0000 0000 0001 = Class: IN (0x0001)
1... .... .... .... = Cache flush: True
Time to live: 4500 (1 hour, 15 minutes)
TXT: VERSION=0.12.0
TXT: OS=Luxonis OS RVC4 1.15.0 (debug)
TXT: MODEL=Luxonis, Inc. KalamaP OAK4-S R5
TXT: AGENT_MODE=pre-setup

Thank you for the prompt response.

jakaskerl

MatteoL
If setup blinks red, this is usually because the device doesn't have access to the internet, or you input wrong static IP settings and device can not ping 8.8.8.8.

Please use the latest setup guide - https://docs.luxonis.com/hardware/platform/deploy/oak4-deployment-guide/

Thanks,
Jaka

MatteoL

Ok, I connected the switch to the company network and the setup completed successfully.

However, please note that I didn't check the "Require Internet Access" option in the setup form. Is it still functioning?

Thanks!

jakaskerl

MatteoL
And before that, you connected directly via switch to the PC? No dhcp?

Thanks,
Jaka

MatteoL

Yes. In our setup, all devices have a static IP configured and there is no DHCP. Every vehicle has a single PoE switch powered by DC that connects all devices.

I could reach the camera even before the setup through IPv6, by sniffing the mDNS packets. The camera answered to oakctl and SSH correctly, however it asked for a password and refused the offline setup based on the QR-code. The IPv6 address was different each time I powered it on, this is ok though.

For information, when the camera was "breathing blue" and after a couple of minutes while I was trying to configure it, the camera stopped answering to all network packets even if powered on. And that happened every time I inserted and removed the Ethernet plug to power cycle it. This is issue has been solved after proper setup. Now the camera works perfectly even for long runtimes.