Reflashed one of my 2 Reach devices (the Rover) today. Connection to 192.168.42.1 shows the config screen, where I add my WLAN. Then I switch to it and it reads “Reach is connecting to anoother network. Switch to XXX to continue.” Alas, it does not switch. The green LED telling that it spans a hotspot is still there and “reach:61:bd” is still shown as a valid WLAN. I can reconnect to that network, and Reach is still conected to it.
Any hint how to proceed?
Cheers
Paul
Hi!
There is a number of options. Are you saying Reach returns to hotspot mode? If you reconnect, can you see the app again and your network in the list of added?
Please, check for:
I checked everything multiple times. I’ve booted a few minutes ago. Blink codes: magenta on, yellow blinking, magenta / green blinking. After minutes green on. Does this info help? What does the magenta / green blinking mean exactly?
Network is listed. And yes, not being able to switch and falling back looks like SSID and/or password are wrong, I know. But I doublechecked. And, it worked before I had done the reflash.
Another one that may help: If I press the blue Connect button (on the screen showing up on 192.168.42.1) to switch the WLAN, nothing happens LED-wise. Shouldn’t the LED blink yellow again telling me, that REach is looking for the new WLAN?
As for the app: I can’t start the app, as I have yet to go thru the iinitial dialog (appearig after reflash): Test - WiFi - Time - ReachView.
UPDATE: Wanted to connect using ssh. Which credentials are needed? Tried user/password emlidreach/reach, reach/reach, nothing worked. Searching the docs for ssh didn’t show up anything. Im sure, there was a chapter about this in the docs a few months ago. Strange…
2nd UPDATE: ssh ok (found the credentials on a Ediosn site: User/password = root/emlidreach). I’d be able now to check some log files. Which one should I check?
I found out that there must be something wrong with wpa_supplicant. Here’s what “journalctl | grep wpa” gives:
May 29 14:11:03 reach systemd[1]: wpa_supplicant_wlan0_event.service holdoff time over, scheduling restart.
May 29 14:11:03 reach systemd[1]: Stopping Daemon to receive the wpa_supplicant event…
May 29 14:11:03 reach systemd[1]: Starting Daemon to receive the wpa_supplicant event…
May 29 14:11:03 reach systemd[1]: Started Daemon to receive the wpa_supplicant event.
May 29 14:11:03 reach wpa_cli[347]: Failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory
May 29 14:11:03 reach systemd[1]: wpa_supplicant_wlan0_event.service: main process exited, code=exited, status=255/n/a
May 29 14:11:03 reach systemd[1]: Unit wpa_supplicant_wlan0_event.service entered failed state.
May 29 14:11:03 reach systemd[1]: wpa_supplicant_p2p_event.service holdoff time over, scheduling restart.
May 29 14:11:03 reach systemd[1]: Stopping Daemon to receive the wpa_supplicant event…
May 29 14:11:03 reach systemd[1]: Starting Daemon to receive the wpa_supplicant event…
May 29 14:11:03 reach systemd[1]: Started Daemon to receive the wpa_supplicant event.
May 29 14:11:03 reach wpa_cli[354]: Failed to connect to non-global ctrl_ifname: p2p-dev-wlan0 error: No such file or directory
May 29 14:11:03 reach systemd[1]: wpa_supplicant_p2p_event.service: main process exited, code=exited, status=255/n/a
May 29 14:11:03 reach systemd[1]: Unit wpa_supplicant_p2p_event.service entered failed state.
May 29 14:11:04 reach systemd[1]: wpa_supplicant_p2p_event.service holdoff time over, scheduling restart.
May 29 14:11:04 reach systemd[1]: wpa_supplicant_wlan0_event.service holdoff time over, scheduling restart.
May 29 14:11:04 reach systemd[1]: Stopping Daemon to receive the wpa_supplicant event…
May 29 14:11:04 reach systemd[1]: Starting Daemon to receive the wpa_supplicant event…
May 29 14:11:04 reach systemd[1]: Started Daemon to receive the wpa_supplicant event.
May 29 14:11:04 reach systemd[1]: Stopping Daemon to receive the wpa_supplicant event…
May 29 14:11:04 reach systemd[1]: Starting Daemon to receive the wpa_supplicant event…
May 29 14:11:04 reach systemd[1]: Started Daemon to receive the wpa_supplicant event.
May 29 14:11:09 reach wpa_cli[379]: event DISCONNECTED received from wpa_supplicant
May 29 14:11:14 reach kernel: [] warn_slowpath_common+0x5e/0x80
May 29 14:11:14 reach kernel: [] warn_slowpath_null+0x22/0x30
May 29 14:11:30 reach wpa_supplicant[292]: Successfully initialized wpa_supplicant
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: Trying to associate with 82:c7:a6:d8:33:1f (SSID=‘A1-659E51’ freq=2462 MHz)
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=82:c7:a6:d8:33:1f status_code=1
May 29 14:11:30 reach wpa_supplicant[292]: Retrying assoc: 1
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: CTRL-EVENT-DISCONNECTED bssid=82:c7:a6:d8:33:1f reason=3 locally_generated=1
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: Trying to associate with 82:c7:a6:d8:33:1f (SSID=‘A1-659E51’ freq=2462 MHz)
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: CTRL-EVENT-DISCONNECTED bssid=82:c7:a6:d8:33:1f reason=3 locally_generated=1
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
May 29 14:11:30 reach wpa_supplicant[292]: current_ssid == NULL
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: Failed to initiate AP scan
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: Trying to associate with 82:c7:a6:d8:33:1f (SSID=‘A1-659E51’ freq=2462 MHz)
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=82:c7:a6:d8:33:1f status_code=1
May 29 14:11:30 reach wpa_supplicant[292]: Retrying assoc: 1
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: CTRL-EVENT-DISCONNECTED bssid=82:c7:a6:d8:33:1f reason=3 locally_generated=1
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid=“A1-659E51” auth_failures=1 duration=10
May 29 14:11:30 reach wpa_supplicant[292]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
May 29 14:11:30 reach wpa_supplicant[292]: wlan0: CTRL-EVENT-TERMINATING
May 29 14:11:30 reach kernel: wpa_supplicant (292) used greatest stack depth: 4748 bytes left
May 29 14:11:30 reach systemd[1]: Stopping Daemon to receive the wpa_supplicant event…
May 29 14:11:30 reach wpa_cli[379]: wpa_supplicant is terminating - stop monitoring
May 29 14:11:30 reach wpa_cli[379]: wpa_supplicant did not reply to PING command - exiting
May 29 14:11:30 reach systemd[1]: Stopped Daemon to receive the wpa_supplicant event.
May 29 14:11:30 reach systemd[1]: Stopping Daemon to receive the wpa_supplicant event…
May 29 14:11:30 reach wpa_cli[380]: wpa_supplicant is terminating - stop monitoring
May 29 14:11:30 reach systemd[1]: Stopped Daemon to receive the wpa_supplicant event.
What hits my eyes is this:
May 29 14:11:03 reach wpa_cli[347]: Failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory
If I remember that the only thing I did is to reflash as advised, then this is strange, isn’t it?
Any hint? I’m really stuck…
I decided to reflash in the hope to change something for the better. Reflash was successful and rebooted the Reach. Now it’s blinking white for minutes already. What does that mean? Where is this LED code documented? The docs only mention LED blink codes at startup, where’s the rest of those codes? May I power cycle it?
