Cannot connect to WiFi (SOLVED)

Getting Started
1

Hi. Received my emonPi today - thank you. Unfortunately I’m struggling at early hurdles.

  1. The device boots but mysql service wasn’t running so I had to SSH in and get it going. OK, no biggie, I hope this will sort itself out in the future.

  2. When setting up wifi via local AP it wouldn’t connect on re-boot, so I connected to local ethernet to continue. I have logged into emonCMS and am on the WiFi setup page. Scans OK and finds my network. I enter creds and click to connect. I takes about 60 seconds to say “config saved, refresh” or similar. But I can’t get it to show a “connected” status.

39%20PM
39%20PM2848×446 42.4 KB

I updated the emonPi from the admin page, all looked up to date. I have the full log if you need it. Something I noted was

Restarting Services…
Restarting OpenEnergyMonitor emonHub: emonhub has been restarted ok.
Log is turned off
Restarting feedwriter (feedwriter.php was not running…)

Here is some debug, following suggestions and comments from similar threads elsewhere.!

Network log from WiFi setup page
Jun 23 22:09:56 emonpi dhcpcd[813]: eth0: fe80::1 router available
Jun 23 22:10:01 emonpi dhcpcd[813]: eth0: fe80::1 router available
Jun 23 22:10:02 emonpi wpa_supplicant[12158]: wlan0: CTRL-EVENT-TERMINATING
Jun 23 22:10:08 emonpi wpa_supplicant[16908]: Successfully initialized wpa_supplicant
Jun 23 22:13:42 emonpi dhcpcd[813]: eth0: fe80::1 router available
Jun 23 22:15:02 emonpi wpa_supplicant[16913]: wlan0: CTRL-EVENT-TERMINATING
Jun 23 22:15:08 emonpi wpa_supplicant[24217]: Successfully initialized wpa_supplicant

ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:11:85:df
inet addr:192.168.1.25 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::3f3e:f1a4:ce58:6198/64 Scope:Link
inet6 addr: fd48:3c0c:fa06:800:87af:7011:3ac3:a97e/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3669 errors:0 dropped:0 overruns:0 frame:0
TX packets:3151 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:760015 (742.2 KiB) TX bytes:1437527 (1.3 MiB)

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:248917 errors:0 dropped:0 overruns:0 frame:0
TX packets:248917 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:21682208 (20.6 MiB) TX bytes:21682208 (20.6 MiB)

wlan0 Link encap:Ethernet HWaddr b8:27:eb:44:d0:8a
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)

sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=GB

network={
ssid=“TALKTALKFA0608”
key_mgmt=NONE
}

And a screen shot showing that the emonPi can find my network.

2

not with an emonpi but i have had a lot of trouble with older BT routers that supported WPA and WPA2 at the same time, devices would connect then disconnect. solution was to login to the router and set them to WPA2 only.

Paul

3

Thanks for the tip Paul - I’ve done the same, rebooted and restarted everything with no success.
When revisiting the WiFi setup screen the single entry in the network list goes green after a second or so, but never remembers the password, even though the JS alert reports ‘config saved’.

I’ve updated the Pi to be read/write instead of read-only but that doesn’t have any effect. No JS errors in Chrome console, and the WiFi password is just basic alphanumeric (no fancy characters).

After looking through some Pi forums I’ve ended up manually adding network details into /etc/wpa_supplicant/wpa_supplicant.conf

network={
ssid=“TALKTALKFA0608”
psk=“MMKU67R9”
}

This survives an emonPi restart so I’m up and running.