DDiMa
- Jan 24, 2024
- Joined Oct 13, 2023
- 0 best answers
Probably "YES", if we ever get decent documentation…
- Edited
I were referring to the first post in this thread - so the described procedure simply doesn't work (anymore) - correct?
So how does one start to code on the rae? I can't find any examples, there are no instructions, there is basically no documentation - and even the app.py created by RH if you create a new app doesn't work on rae, because the methods used there simply don't exist in the robothub library shipped with rae.
- Edited
When installing "Run", I can see the default app:
When installing "Develop", i can't:
(HelloRAE I created myself. Deleting it doesn't change anything (except that the window for "Develop" doesn't show any app then, obviously.)
OK, that did the trick, although I don't fully understand why. After activating ntp, rebooting, restarting systemd-networkd the conenction via QR code did work. Now this is persistent - I shudtown/restarted multiple times, and the rae comes up fine, connects to the WLAN etc.
What I did ultimately need to do to make this happen:
- disable hostapd
- enable ntp
- reboot
- restart systemd-networkd
- run QR-code setup from RH
So I can now start experimenting - but I still have no clue, why this worked in the end. Getting rid of the certificate issue via setting the correct time I dig, but why this addressed the "rae does not connect to WLAN issue"???
Video streams work, remote control work, so for the moment I am happy
No more experiments today, can only get worse
Thanks @jakaskerl , I hope at least the basics are now sorted out. I'd still be curious what exactly happend…!
And that is done how? And do I need to do this after each reboot manually, like the systemd stuff? Maybe it's even documented somewhere, and I missed it?
Any thoughts about the systemd nightmares I am having? I mean, can't be that I have to restart systemd-networkd after each reboot, right?
And another test: When I
- Mask hostapd (so it doesn't get started)
- Log-in after reboot and restart systemd-networkd
- Use the QR-method
I get connected to my WLAN (so even the wpa_supplicant command is apparently executed correctly in the background) - but still "Connection error" on the display and nothing in RobotHub.
I give up, need some pointers. This all makes no sense at all to me anymore by now.
- Edited
Found this in the robothub-ctl logs:
200 14:59:04 I user/agent/hub/config : calling home (expectedTeamId = null)
200 14:59:04 I user/agent/hub/config : calling home -> first time, need to authorize
200 14:59:05 W user/agent/hub-connection : callHome failed!
{
"error": {
"cause": {
"code": "CERT_NOT_YET_VALID",
"message": "certificate is not yet valid",
"name": "Error",
"stack": "Error: certificate is not yet valid\n at TLSSocket.onConnectSecure (node:_tls_wrap:1540:34)\n at TLSSocket.emit (node:events:513:28)\n at TLSSocket.emit (node:domain:489:12)\n at TLSSocket._finishInit (node:_tls_wrap:959:8)\n at ssl.onhandshakedone (node:_tls_wrap:743:12)"
},
"message": "failed to obtain auth code",
"name": "Error",
"stack": "Error: failed to obtain auth code\n at Object.callHome (file:///usr/libexec/robothub/robothub-agent.mjs:219661:17)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async ensureCallingHome (file:///usr/libexec/robothub/robothub-agent.mjs:187910:28)\n at async Object.ensureCallingHome (file:///usr/libexec/robothub/robothub-agent.mjs:186087:9)\n at async Promise.all (index 0)\n at async file:///usr/libexec/robothub/robothub-agent.mjs:238084:9"
}
}
200 14:59:05 I user/agent/hub-connection : waiting 69829 milliseconds
Sounds to me like the device does try to register with the WLAN link up…?!
- Edited
Some more troubleshooting via direct connection (USB-C):
- After each reboot, hostapd is crashed.
- Information in wpa_supplicant.conf is correct (SSID, password - no weird character translations as I read elsewehere etc. - everything is fine, that part of reading the QR code does definetly work)
- No IP address obtained, not connected to my WLAN - in line with the "connection error" messages on the deveice, when I try the QR-code method.
How to get it connected to the WLAN?
systemctl stop hostapd
systemctl restart systemd-networkd
wpa_supplicant -B -i wlp1s0 -c /etc/wpa_supplicant.conf
And then the rae is connected to my WLAN, can ping Google etc.
Does this give any indication, what's wrong with the device/setup? The issue (as mentioned earlier in this thread!) seems to be a crashed hostapd. I'd like to disable it completely to check, if then maybe the connection comes up properly. Maybe then the QR-method would even work…? The display still states "Register at…
I tried using the QR code method with a the WLAN connection up (via shell/USB-C) - same result (QR code is read, SSID/pwd is transferred, connection error… while the rae is connected to WLAN and can ping e.g. google.com). Provisioning app is running, too, I checked that.
Very strange, I really don't get it
No, just the usual mix of numbers, characters, special characters ({[]}…). No whitespaces, no UTF stunts. SSID is hidden, but a) that shouldn't matter and b) it doesn't work with non-hidden SSIDs either.
Did a factory reset, I think - no change. BTW, how do I know, that the factory reset did work? I press the button 10s - and then? Nothing on the display, device doen't turn off…?!
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…
- Edited
I did give it a quick try: Good news is, that the display isn't flickering so far
I tried setup via RH, QR code was recognized, trying to connect to my WLAN… Connection error. Tried again - connection error. Tried another WLAN/SSID - connection error. Followed the instructions to shut down (double press of the power button) and try again. This time the display shows "Connecting…", then the rae flashes red, then turns white and the display is stuck at "Connecting…" (with the "pulsing" dots. Shutdown with double press doesn't work anyomore either, only hart shutdown (8s press) works.
This is really no fun. Any idea why the rae is not connecting to my WLANs (passwords are from a password manager, so we can exclude mistyping)? Is the setup via RH even working for anyone?
Suggestions on how to continue?
Sorry for not coming back here for a time, but as stated above, I needed to exchange my rae first and got an unplanned two weeks business trip on top… My new device arrived today, will hopefully find time to test it tomorrow. Getting it hooked up to RobotHub and driving it around would already be an achievement over the last time
Getting the device exchanged was no problem and the Luxions staff was really helpful, took a while, though…
Don't get further, the device is mostly dead. When starting up, I got the logo and then the LEDs where "blinking" white, but not in a good way. Looked more like something was wrong with the process controlling the RGB-LEDs. Devices doesn't react to power button at all - neither double-click, nor pressing 8s (or longer). Had to wait until the battery died…
Sent a mail to support, let's see how they react. So far, rae is a very frustrating experience…
- Edited
Hah! Found it! hostapd is blocking wlp1s0! After stopping the service, the link to my WLAN comes up. This is reproducible, since hostapd is running after each reboot… I am not too familiar with systemd and not at all with hostapd: Quick hint or pointer on how to disable the automatic start on reboot?
@Mike Do you have any hint which 1.13 to pick? Running on 1.12. And which URL do I need to provide to mender: To the directory, to the *.mender file…(I guess: the latter)? Sorry if these are stupid questions, but "mender -install <link_to_firmware>" isn't that conclusive with respect to what the link should point to
BTW: I just measured the surface tempratire (just on the top of the rae): 54°C after ca. 30-45min fighting with the WLAN config, see above. Doesn't sound right to me. I am now starting to get kicked out of the ssh session again and can't reconnect…
root@keembay:~# wpa_supplicant -i wlp1s0 -c /etc/wpa_supplicant.conf -B
Successfully initialized wpa_supplicant
root@keembay:~# client_loop: send disconnect: Connection reset
Shutdown via double click stopped working, too, only hard shutdown will work then.
- Edited
Got one step further after hard resetting: QR scan method etc. works, I triple checked that. I now get a proper "Couldn't connect" message with the red blinking, too. With the "fresh" device, I can now see all my local WLAN APs, too, so the WLAN interface does seem to work, too:
wpa_cli v2.9
Copyright (c) 2004-2019, Jouni Malinen <j@w1.fi> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Selected interface 'p2p-dev-wlp1s0'
Interactive mode
<3>CTRL-EVENT-SCAN-RESULTS
scan_results
> bssid / frequency / signal level / flags / ssid
82:a7:41:ec:80:f1 5220 -41 [WPA2-PSK-CCMP][ESS] lannisport_iot
76:a7:41:ec:80:f1 5220 -77 [WPA2-PSK-CCMP][ESS] lannisport
7e:a7:41:ec:80:f1 5220 -77 [WPA2-PSK-CCMP][ESS] lannisport_restricted
7e:a7:41:ec:80:f0 2462 -83 [WPA2-PSK-CCMP][ESS] lannisport_iot
7a:a7:41:ec:80:f0 2462 -44 [WPA2-PSK-CCMP][ESS] lannisport_restricted
7a:a7:41:ec:80:f1 5220 -77 [ESS] eighteenguests
76:a7:41:ec:80:f0 2462 -43 [ESS] eighteenguests
86:a7:41:ec:80:f0 2462 -83 [WPA2-PSK-CCMP][ESS]
70:a7:41:ec:80:f0 2462 -44 [WPA2-PSK-CCMP][ESS] lannisport
82:a7:41:ec:80:f0 2462 -83 [WPA2-PSK-CCMP][ESS]
ea:63:da:a4:f3:fb 2462 -79 [WPA2-PSK-CCMP][ESS] lannisport_restricted
ee:63:da:a4:f3:fb 2462 -80 [WPA2-PSK-CCMP][ESS] lannisport_iot
e0:63:da:a4:f3:fb 2462 -82 [WPA2-PSK-CCMP][ESS] lannisport
e6:63:da:a4:f3:fb 2462 -79 [ESS] eighteenguests
I have three APs, all providing the same four SSIDs (lannisport_iot, lannisport:restricted, lannisport, and eighteenguests). Could this be the issue, that the rae doesn't support any roaming or fails to connect to an SSID, when multiple APs are available to connect to it? It seems to "see" the nearest AP with both 2.4 & 5 GHz bands plus one other with 2.4 GHz only. According to the documentation, wpa_supplicant should support roaming, though.
There are two versions, which one should I pick - the newer one (from October, 2nd)? How does the installation work, when I have no internet connection, i.e. have to scp the files onto the rae? I did find instructions for pulling the FW via mender only.
- Edited
Definetly more than "slightly warm"…
No, I did not try a "hard reset" - how do I do that? And how do I install new FW (and where do I get it) - I guess that's somewhere in the Wiki, but I did not yet stumble upon it…
EDITH: Found it - just in case I am not the only one looking in different places… Instructions are here.
I just got my rae.
Tried to set it up with RobotHub according to instructions (QR code): QR code is received, display states "connecting to <my SSID>", device flashes first blue, then red, then turns white - but no connection to my WLAN (device doesn't show up in my WLAN or RobotHub).
Tried to set it up manually according to instructions: SSID & password were obviously correctly received, because the correct information is in /etc/wpasupplicant.conf. BTW, there is an error in the instructions, the quotation marks in the example for the passPHRASE are wrong, use only if you use the passWORD. /etc/systemd/network/20-wifi.network has the right content, too. Stopping hostapd was never needed, it is always dead after startup. When trying to connect to my WLAN with wpasupplicant b -i wlp1s0 (…) i start getting lots of error messages - from missing or invalided devices, to already running (or hanging) instances… Error messages seem to depend a bit on the time of day and what I tried before - I can provide them, if there is anyone who can help me. This seems to be the root cause of the issue, because I don't get beyond that step in the manual setup and I guess the "QR code method" is trying to do pretty much the same in the background.
I do get wlp1s0 shown in the device list for ifconfig & Co.), but obviously never with a connection to my WLAN.
When trying to scan for WLANs with wpa_cli, I don't get any output (and there are plenty of WLANs around), which strikes me as weird, because that should IMO work, even without any WLAN connection. So maybe THIS is the root cause and something is wrong with the WLAN adapter?
Last observation, not sure if this might be related: My device gets VERY hot. You need to be quick when picking it up for shutting it down…! I don't think, that it should be that hot. After some time, I started to get kicked out of the ssh session too, so I suspect a bit, the device might freeze/lock-up due to overheating.
The display is strange, too: It starts up fine (backlit -> "rae" -> small robot on white background -> "Register…" on white background, but then the display starts to "flicker", constantly changing ist brightness until it's gone. Looks a bit like a "fade out" effect with 0.5 Hz … I doubt very much, that this is as it should be, too.
Any ideas, tips or recommendations? Some more info I shall provide? I have no previous experience with Archlinux, but I am otherwise fairly proficient on Linux (Ubuntu/Debian), so fire away!
With respect to temperature and display: Might I simply have a HW defect?