D

DiMa

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.

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.)

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…?!

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

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?

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.

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.

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.