• RAE
  • RAE cannot connect to RobotHub (or the Internet in general)

Nevermind about the shutting down problem… turns out that I can force shut it down.

What do you get when you use ifconfig? Do you have a valid connection to your wifi router?

    FloIgnition

    Yes, I have a valid connection to my wifi router… in fact, I tried connecting my RAE in two different places: first at a makerspace and then at my home. My RAE doesn't seem to connect to the Internet at either of those two places.

    Anyway, for what happens when I use ifconfig, I get this (connected over USB):

    br0 Link encap:Ethernet HWaddr 0E:08:3B:A6:6A:73

          inet addr:192.168.197.55  Bcast:192.168.197.63  Mask:255.255.255.240
    
          inet6 addr: fe80::c08:3bff:fea6:6a73/64 Scope:Link
    
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    
          RX packets:383 errors:0 dropped:0 overruns:0 frame:0
    
          TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
    
          collisions:0 txqueuelen:1000
    
          RX bytes:96209 (93.9 KiB)  TX bytes:9173 (8.9 KiB)

    docker0 Link encap:Ethernet HWaddr 02:42:C8:14:6C:64

          inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
    
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
    
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    
          collisions:0 txqueuelen:0
    
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    lo Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0
    
          inet6 addr: ::1/128 Scope:Host
    
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
    
          RX packets:304 errors:0 dropped:0 overruns:0 frame:0
    
          TX packets:304 errors:0 dropped:0 overruns:0 carrier:0
    
          collisions:0 txqueuelen:1000
    
          RX bytes:26990 (26.3 KiB)  TX bytes:26990 (26.3 KiB)

    usb0 Link encap:Ethernet HWaddr 7A:A2:39:06:CC:B9

          UP BROADCAST MULTICAST  MTU:1500  Metric:1
    
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    
          collisions:0 txqueuelen:1000
    
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    usb1 Link encap:Ethernet HWaddr 8E:CF:83😃2:FE:77

          inet6 addr: fe80::8ccf:83ff:fed2:fe77/64 Scope:Link
    
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    
          RX packets:383 errors:0 dropped:0 overruns:0 frame:0
    
          TX packets:90 errors:0 dropped:0 overruns:0 carrier:0
    
          collisions:0 txqueuelen:1000
    
          RX bytes:96209 (93.9 KiB)  TX bytes:14066 (13.7 KiB)

    wlp1s0 Link encap:Ethernet HWaddr F4:26:79:03:3D:6A

          inet6 addr: fe80::f626:79ff:fe03:3d6a/64 Scope:Link
    
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
    
          collisions:0 txqueuelen:1000
    
          RX bytes:0 (0.0 B)  TX bytes:4327 (4.2 KiB)

      Oh wow, the formatting got weird… probably wasn't the best way to paste that

      I found that if i went to my routers/wifi interface i'd see the Rae connect for a few seconds, usually only a burst of a about 40kb of traffic, then go silent. If I assigned it a static IP (whatever it connected with originally) it would connect. I repeat this everytime I factory reset the Rae. I have no idea why this works, This is on a Ubiquiti network with the 2.4/5ghz broadcasting under a single SSID.

      KevinChow your wifi does not have an IP address. I have to run the manual ip command ever reboot. This device has the worst documentation and support I have seen.

      12 days later

      I am running into a similar issue. I just got my RAE yesterday and had to do the wpa_supplicant steps to get it to connect because I have special chars in my SSID. I was able to get it connected after a lot of troubleshooting and then I ran robothub-ctl connect to try and force a manual connection, but I kept getting "team not found" errors in the RobotHub portal. I tried rebooting the robot and now it lost its WiFi connection…

      I have similar problem. I have connected RAE trough SSH, but following your instructions to enable WIFI connection to Internet for RAE, I cannot set up the driver wlp1s0. "wlp1s0: Failed to initialize driver interface" after "pa_supplicant -B -i wlp1s0 -c /etc/wpa_supplicant.conf" line command and after "systemctl stop hostapd".

      Retried n times all the times resetting RAE to factory settings.

      Can you help me?

      HI

      Updated to 1.13 after some tricks connected to Internet but if I reboot I loose Internet comnnection and when I tried to connect to robothub same as @esimkowitz

      • Mike replied to this.

        AlbertoFassio … Did you do a hardware reset ? … and only use the QR code to connect to RobotHub ? … Or did you manually change wifi settings ?

          I did hw e soft reset and I changed the fw to 1.13.

          The problems are two:

          1) I have to do rfkill twice to connect to local network with wpa_supplicant otherwise It does not work. Then if I reboot the ip address is lost and I have to redo the procedure

          2)After internet connection if I launch robothub cloud connect, I receive teamnotexistent

          Is it so difficult to provide a page with complete and updated instruction?

            Hi AlbertoFassio
            Please don't mix and match manual config and official RH steps. As Mike said, try connecting using QR only.
            Also please use FW 1.12, since 1.13 is still in development and has some bugs. We will make release versions more obvious in the future.

            Complete instructions are also being created and will be added to the docs.

            Thanks,
            Jaka

            11 days later

            It's been a while, but just as an update, I actually contacted the Luxonis team directly, and what ended up happening is that they had me send back the RAE I had back to them (apparently it was defective or something), and they sent me back a new one. The QR code connection thing works now, although there are some other weird things going on in RobotHub that I may or may not make a post about, depending on whether they end up resolving themselves.

            8 days later

            I have the same issues, just got a replacement rae - and the same issues prevail. It is really frustrating, especially seeing that almost a month later there is neither better documentation, nor solutions to the existing problems, nor apparently new software…

            Very frustrating experience so far, especially since most of us aren't excatly total newbies. >60% of the rae forum topics are people not being able to connect to or from the device…

            a month later

            I have more or less the same issues. Highly frustrating. I could connect once using the hub. I even saw a video in the browser. Once. After adding the default app nothing worked. After rebooting i only see the rae logo. Reset did not help. I can ssh into the thing but what to do then?

            I deleted the content of /data (which according to the 2 half sentences covering Reset in the docs is one step) but this did not help. How can i revert back to initial state?

            Docs are not worthy in my opinion. No info about the next steps.

            What about a script, which enforces the system setup to a defined state using Ansible or whatever.

            For now the rae still collects dust and i do not want to waste any more time. Bad.

            I am obviously not alone. This product seems to underwhelm a lot of customers.

            • Mike replied to this.

              jfey60

              I have found when Rae gets into a state doing a hard reset gets things back up and running - push and hold the reset button … you need to start from the beginning though afterwards … also pays to ensure you are running v1.12 FW

                Mike As mentioned above, the (hard)reset did not improve the situation. I tried this many times. I am stranded. Is there any information somewhere about the semantics of those LEDs, I see green, blue at times.

                So obviously the hard reset is not a factory reset.