Common Issues

1

Forgotten RobotHub password

Did you forget the password for RobotHub?

  • If you forget the password to your RobotHub account, go to the login page.
Login
  • Select Forgot Password and enter your email address there.

  • The email will contain a link to change your password.

2

Agent(Robot) installation failed

Agent(Robot) installation failed

An error occurred during one of the installation steps.

Error
  • Try pinging a website in your browser, such as google.com.
3

Agent(Robot) is installed but you don't see it in the cloud

Agent(Robot) is installed but you don't see it in the cloud

Agent was successfully installed through the script from the pop-up window, but it did not appear in the RobotHub platform.

Robot section

To troubleshoot this issue, follow these steps:

  • Check the status of the robot in the console by running the following command:
1robothub-ctl status

bash

  • This command will provide information about the current state of the robot. Ensure that the robot is running and connected to the cloud.
1╭──────────────────────────────────────────────────────────────╮
2│                                                              │
3│  RobotHub Agent (23.162.2221 | linux/x64 | DepthAI 2.21.2)   |
4│                                                              |
5│  Web UI                   https://localhost:9010             |
6│  DepthAI                  2.21.2                             |
7|                                                              │
8|  Connected to cloud?      yes (https://robothub.luxonis.com) |
9│  Pending detections       0                                  |
10│                                                              │
11╰──────────────────────────────────────────────────────────────╯

txt

  • If the command indicates that you are missing permission, run the following script from the console to grant the necessary permission:
1sudo usermod -a -G robothub $USER

bash

  • This command adds your user to the robothub group, which should provide the required permissions.
  • After modifying the user's permissions, try restarting your computer or reconnecting if you are accessing it via SSH. This step ensures that the changes take effect.
  • If the robot still doesn't appear in the cloud, try to uninstall the robot using the following script:
1robothub-uninstall

bash

  • This command will remove the agent from your system.
  • Finally, try installing the agent again using the appropriate installation method or procedure specified for your system.
4

Device didn't appear (>1 minute) after plugging it to the computer via USB

Device didn't appear (>1 minute) after plugging it to the computer via USB

  • Check if the device is being detected by the computer:
1lsusb

bash

  • Look for Intel Movidius MyriadX
1Bus 001 Device 008: ID 03e7:2485 Intel Movidius MyriadX

bash

  • Verify that it is detected by the Agent:
1robothub-ctl devices

bash

  • The output should look similar to the one below
1╭───────────────────────╮╭───────────────────────╮╭───────────────────────╮╭───────────────────────╮╭───────────────────────╮╭───────────────────────╮╭───────────────────────╮
2│  serial               ||  name                 ||  product              ||  location             ||  status               ||  connectionStatus     ||  app                  |
3|───────────────────────||───────────────────────||───────────────────────||───────────────────────||───────────────────────||───────────────────────||───────────────────────|
4│  18443010A168381300   ||  18443010A168381300   ||  OAK-D Pro AF (DM9098)||  USB 2.4              ||  success              ||  ready                ||  none                 |
5╰───────────────────────╯╰───────────────────────╯╰───────────────────────╯╰───────────────────────╯╰───────────────────────╯╰───────────────────────╯╰───────────────────────╯

txt

  • If it is not detected.

Check that /lib/udev/rules.d/80-movidius.rules has the following content

1SUBSYSTEM=="usb", ATTRS{idVendor}=="03e7", MODE="0664", GROUP="robothub"

txt

5

Live streaming is throwing an error

Live streaming is throwing an error

A black window with no image in the application and an error message in the Activity subsection.

Unsupported browserError
6

RAEs QR code detection does not work

RAEs QR code detection does not work

RAE did start successfully but is unable to read the QR code from RobotHub.

If the RAE is only showing one message - RAE on its display the RAEs Agent is probably not running. This causes RAE to not be able to read the QR code since its built-in app is not started.

Here is how to resolve this:

  • Connect RAE to your computer as described in step 2 of advanced / manual tab in RAE

  • After you are connected to RAE run the following command

1robothub-ctl status

bash

  • The output should look like this:
1╔═══════════════════════════════════════════════════════════╗
2║                                                           ║
3║ RobotHub Agent (23.244.1739 | linux/x64 | DepthAI 2.21.2) ║
4║                                                           ║
5╚═══════════════════════════════════════════════════════════╝
6
7 Web UI                   https://localhost:9010
8 DepthAI                  2.21.2
9
10 Connected to cloud?      no (https://robothub.luxonis.com)
11 Team                     Team
12 Pending detections       0

txt

  • Check if the provisioning app is running
1robothub-ctl apps list

bash

  • The output should look like this:
1┌──────────────────────────────────────┬──────────────┬─────────┬──────────────────────────┬──────────────────────────┐
2│ id                                   │ type         │ status  │ started at               │ stopped at               │
3├──────────────────────────────────────┼──────────────┼─────────┼──────────────────────────┼──────────────────────────┤
4│ cd53ef56-789f-4985-9f08-7b4f9b12749a │ provisioning │ Running │ 2023-09-20T09:01:49.715Z │ 2023-09-20T09:02:00.035Z │
5└──────────────────────────────────────┴──────────────┴─────────┴──────────────────────────┴──────────────────────────┘

txt

If the output from the commands is not similar to the ones shown above perform a reset of the Agent:

1robothub-ctl stop
2rm -rf /home/robothub
3mkdir /home/robothub
4robothub-ctl start

bash