A fresh install of the Rae OS has an /etc/wpa_supplicant.conf file but no /etc/systemd/network/20-wifi.network file. Out of the box there are two ways to connect to the Rae - via usb (ssh root@192.168.197.55) and the re-<id> access point (192.168.11.1). Am I correct that by adding a wifi network per the instructions at https://docs-beta.luxonis.com/hardware/rae/get-started?v=Advanced+(manual) creates another access point which seems to occur with this instruction: systemctl stop hostapd wpa_supplicant -B -i wlp1s0 -c /etc/wpa_supplicant.conf systemctl restart systemd-networkd if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } If so, what is the purpose of adding this additional wifi access point? What additional functionality does that enable? Also, the docs say there is a webserver running https://<IP of RAE>:9010. I see by scanning the ports 192.168.11.1:9010 and 192.168.197.55:9010 there is a tcp process running, but a browser cannot connect to those addresses. root@rae:~# fuser 9010/tcp 789 root@rae:~# ps -p 789 -o comm= node if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Looks like this is the .vscode server though.

The rae is "online" and the RAE-Default App is loaded. The app is stopped with the log showing: 6:21:42 INFO | on_stop:173 => Stopping the app... 16:21:45 [2023-11-11 00:21:45.627] [depthai] [warning] USB protocol not available - If running in a container, make sure that the following is set: "-v /dev/bus/usb:/dev/bus/usb --device-cgroup-rule='c 189:* rmw'" 16:21:49 ERROR | on_start:151 => The default app requires an assigned device to run. Please go to RobotHub, navigate to the app's page, click the "Reassign devices" button and select a device. 16:21:49 INFO | on_stop:173 => Stopping the app... if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } To restart the RH agent, I think you mean robothub-ctl restart I did that and the issue persists - the rae does not show up as a device to reassign ("You have no available devices to assign to app"). As a side note, after a hard reset and setting up just the local web control, that works, but as soon as I try to add the rae to RH, the local web control breaks.

Setting up new connections with Rae

mjohannessen

A fresh install of the Rae OS has an /etc/wpa_supplicant.conf file but no /etc/systemd/network/20-wifi.network file. Out of the box there are two ways to connect to the Rae - via usb (ssh root@192.168.197.55) and the re-<id> access point (192.168.11.1). Am I correct that by adding a wifi network per the instructions at https://docs-beta.luxonis.com/hardware/rae/get-started?v=Advanced+(manual) creates another access point which seems to occur with this instruction:

systemctl stop hostapd
wpa_supplicant -B -i wlp1s0 -c /etc/wpa_supplicant.conf
systemctl restart systemd-networkd

If so, what is the purpose of adding this additional wifi access point? What additional functionality does that enable?

Also, the docs say there is a webserver running https://<IP of RAE>:9010. I see by scanning the ports 192.168.11.1:9010 and 192.168.197.55:9010 there is a tcp process running, but a browser cannot connect to those addresses.

root@rae:~# fuser 9010/tcp
789 
root@rae:~# ps -p 789 -o comm=
node

Looks like this is the .vscode server though.

mjohannessen

mjohannessen SOLVED partially. Adding the additional WIFI enables https://<IP of RAE>:9010 for local control. Still, the browser gets stuck on "Waiting for stream ...", although the lights, motors and face can be controlled.

Also, by doing this:

robothub-ctl stop
robothub-ctl startup disable

Disables https://<IP of RAE>:9010. To re-enable https://<IP of RAE>:9010:

systemctl stop hostapd
wpa_supplicant -B -i wlp1s0 -c /etc/wpa_supplicant.conf
systemctl restart systemd-networkd

After this, I connected the rae to RoboHub using the generated QR and after doing this I could no longer control the rae using https://<IP of RAE>:9010. On robohub.luxonis.com I see that the RAE-Default App build failed. I don't know why the default when connecting to robohub is to try to install an app on the device. In any event, I uninstalled the app and installed the RUN version of the RAE-Default App. That app tries to start but stops:

5:22:44
ERROR | on_start:151 => The default app requires an assigned device to run. Please go to RobotHub, navigate to the app's page, click the "Reassign devices" button and select a device.
15:22:44
INFO | on_stop:173 => Stopping the app...

I cannot reassign the device because rae is not listed using the Reassign Devices button on the webpage. I tried uninstalling the app via robohub and completely removing rae from robohub, and rebooting rae and logging in locally at https://<IP of RAE>:9010. Now the rae is non-responsive but tries to connect to robohub and there appears to try to install something.

So how can I remove whatever was installed via robohub?

jakaskerl

Hi mjohannessen
Had the same issue

mjohannessen The default app requires an assigned device to run.

which was solved when reassigning the device. The rae should be available. Is it not online on RH?

You could try manually stopping/restarting the rh agent (https://docs-beta.luxonis.com/deploy/robothub/install-agent/).

If you are stuck the easiest way would be to factory reset the device.

Thanks,
Jaka

mjohannessen

The rae is "online" and the RAE-Default App is loaded. The app is stopped with the log showing:

6:21:42
INFO | on_stop:173 => Stopping the app...
16:21:45
[2023-11-11 00:21:45.627] [depthai] [warning] USB protocol not available - If running in a container, make sure that the following is set: "-v /dev/bus/usb:/dev/bus/usb --device-cgroup-rule='c 189:* rmw'"
16:21:49
ERROR | on_start:151 => The default app requires an assigned device to run. Please go to RobotHub, navigate to the app's page, click the "Reassign devices" button and select a device.
16:21:49
INFO | on_stop:173 => Stopping the app...

To restart the RH agent, I think you mean

robothub-ctl restart

I did that and the issue persists - the rae does not show up as a device to reassign ("You have no available devices to assign to app").

As a side note, after a hard reset and setting up just the local web control, that works, but as soon as I try to add the rae to RH, the local web control breaks.

jakaskerl

Hi mjohannessen
Any chance you have more than one app installed? Also make sure the FW is the stock one (1.12 OS and 23.223.1855 for the agent version).
This is a non-standard issue, I'd suggest writing to support@luxonis.com, perhaps we need to fix this manually.

Thanks and sorry for the inconvenience,
Jaka

mjohannessen

jakaskerl

As to OS:

root@keembay:~# cat /etc/os-release
ID=luxonisos
NAME="Luxonis OS"
VERSION="1.12"
VERSION_ID=1.12
PRETTY_NAME="Luxonis OS 1.12"
DISTRO_CODENAME="dunfell"
IMAGE_REV=d238da346188461703c25a3b2e5dea32b196ad2b
BUILD_ID="20230811201312"

As to the agent version:

Without going to RH, is there a terminal command to obtain the version of the agent?

As to apps running, the only app installed was the default RAE-Default App through the RH provisioning process.

Note the CPU usage. In addition the device is very warm:

top PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2691 root 20 0 81036 45164 748 S 158.1 1.6 28:08.46 rg 2693 root 20 0 80992 42596 396 S 156.4 1.5 28:05.13 rg 1460 root 20 0 1951564 98316 8044 S 16.2 3.4 5:13.03 depthai-de+ 1310 robothub 20 0 1135612 128432 3920 S 7.9 4.4 2:43.77 python3 2558 root 20 0 1426884 537084 9604 R 5.6 18.5 1:55.03 node ...

jakaskerl

Hi mjohannessen
Everything seems to be installed correctly. Please write to support@luxonis.com so we can sort this out. Also link the discussion so we don't have to go through the whole process again.

Thanks,
Jaka

mjohannessen

Support bounced this back to this forum as more team members are here. This is a description of the problem I am having to correctly provisioning rae with the default app and enabling basic functionality using RobotHub.

Here is a rundown of the issue starting from a hard reset::

Hard reset, remove existing rae from RH including events
Connect via USB > ssh root@192.168.197.55 OK
rae-<id> is visible and I can > ssh root@192.168.11.1 OK

nc -vz 192.168.11.1 9010
Connection to 192.168.11.1 port 9010 [tcp/*] succeeded!

5: https://192.168.11.1:9010:
Camera streaming fine (large (front left) and small window (rear right))
No motor control though

Top temp 52c

7. $ top:
   1135 robothub  20   0  300724   3188   2960 S 163.5   0.1  22:51.48 rae_motors                                                                 
    1243 root      20   0 2883428 191484  29636 S  98.4   6.6  13:28.35 depthai-device-                                                            
    1121 robothub  20   0 1580548 194696  48964 S  55.9   6.7   7:27.92 python3

I unplugged USB, soft reboot, plugged in USB
Same issue with web app - cameras stream but no motor control.

10. root@keembay:~# cat /etc/os-release
ID=luxonisos
NAME="Luxonis OS"
VERSION="1.12"
VERSION_ID=1.12
PRETTY_NAME="Luxonis OS 1.12"
DISTRO_CODENAME="dunfell"
IMAGE_REV=d238da346188461703c25a3b2e5dea32b196ad2b
BUILD_ID="20230811201312"

Connected to RH (light flashes darker blue)
Connection failed red light flashes, but rae shows up on RH and online.
Display says "Connected to Robothub". The unit self-reboots.
the local network rae:<id> is gone
RH says "Provisioning in progress …"

There is a good fast wifi/net connection.

12. $ top
  1040 robothub  20   0 1564912  78952  28668 S 152.3   2.7   6:00.68 podman                                                 
    1319 robothub  20   0 1269100  41344  24876 R  24.8   1.4   0:00.75 exe                                                    
      80 root      20   0       0      0      0 S   8.9   0.0   0:02.57 kswapd0

Provisioning completed after some time - RAE-Default App installed and the status is "stopped"
On RH under "Perception Apps" is present, but there are no assigned devices. The log shows the error:

0:43:03[2023-11-12 18:43:03.268] [depthai] [warning] USB protocol not available - If running in a container, make sure that the following is set: "-v /dev/bus/usb:/dev/bus/usb --device-cgroup-rule='c 189:* rmw'"
10:43:04ERROR | on_start:151 => The default app requires an assigned device to run. Please go to RobotHub, navigate to the app's page, click the "Reassign devices" button and select a device.
10:43:04INFO | on_stop:173 => Stopping the app...
10:43:07[2023-11-12 18:43:07.733] [depthai] [warning] USB protocol not available - If running in a container, make sure that the following is set: "-v /dev/bus/usb:/dev/bus/usb --device-cgroup-rule='c 189:* rmw'"

Touching the Reassign Devices" button, the dialog says "You have no available devices to assign to app"
On RH Perception Apps/Live View shows "No streams available" Likewise, Local Frontend does not display a stream nor do the motors work. None of the controls (lights, face, etc) work.

17. $ top: 2000 root 20 0 1951564 116028 28352 S 16.6 4.0 1:03.04 depthai-device- 1875 robothub 20 0 1201148 154260 30888 S 7.0 5.3 0:29.25 python3 2462 robothub 20 0 660768 70432 36276 S 7.0 2.4 0:01.39 robothub-inner.

18. I notice that the LCD is flickering - it says "Connected to RobotHub", but flickers like it's having issues.

19. Per RH -
Agent Version: 23.223.1855
FW version : Luxonis OS 1.12

20. top temperature is around 49c

Any help here?

jakaskerl

mjohannessen
There was an issue in the frontend; we have released a patch, so you should now be able to reassign the device.

Thanks for the extensive information you have provided.

Regards,
Jaka

mjohannessen

Thx - I was able to reassign with this fix.

Issues with Local Frontend:

Edit Face - blanks the screen (lit but no graphics)
Edit Lights - works
Motor control - works
Edit mode manual and follow me - work
Live View - no video

Same issue with local control https://192.168.1.64:9010.

Regarding no video stream, I opened ports 5349 and 3478 - no effect