Dear All,
openhabian-config > System Settings > WIFI does not let me enable WIFI with the message that it is only for Raspberry 3. Is it possible that 3B+ is not supported?
No, should work if you are on 1.4.1:
Thanks for your information. Sadly I have 1.4.1 installed. Maybe it is just a bug in openhabian-config?
I configured the file openhabian.conf and filled in wifi_ssid=xx and wifi_psk=yy . Put my router cannot see something paired. With sudo netstat -atn |grep 8080 i can only see the one IP Adress from LAN. Does LAN and WLAN function simultaneously?
Make sure your WiFI is enabled. I had this issue with my new 3 B+. You’ll notice in the boot-log is says that the WiFi will be disabled until you set a location.
I had come across the exact text and decided to paste it here. I’m not sure if this your issue, but if it is, it says to use raspi-config to set your country.
Wi-Fi is disabled because the country is not set.
Use raspi-config to set the country before use.
2 Likes
1 Like
as we speak i want to put in the openhabian-flashed micro-sd into my 3B+ and access it via wifi… should I wait?
Good to know. Very odd though to link WiFi ability to having set a country
As transmit power regulation varies from country to country this sound reasonable.
Raspbian release notes
2018-03-13:
* Raspberry Pi 3 B+ support
* WiFi is disabled until wireless regulatory domain is set (Pi 3 B+ only)
- The domain can be done through 'Raspberry Pi Configuration' (rc_gui),
'raspi-config' or by setting 'country=' to an appropriate ISO 3166
alpha2 country code in /etc/wpa_supplicant/wpa_supplicant.conf.
* Default wireless regulatory domain is now unset
Chad, thanks for your fast answer.
- I now have edited country via raspi-config
- I checked wpa_supplicant.conf
[16:57:45] root@openHABianPi:/etc/wpa_supplicant# edit wpa_supplicant.conf
–>Country, SSID, and Key are set correctly
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=CH
network={
ssid=“ABC-2”
psk=“1234 1234 1234 1234 1234”
With iwlist I do not get a positive answer
[17:01:51] root@openHABianPi:/etc/wpa_supplicant# iwlist scanning
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
wlan0 Interface doesn’t support scanning : Network is down
With iwconfig I see that my SSID was not taken:
[17:46:24] root@openHABianPi:/home/openhabian# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
I also still do not see a connection in my routers list.
Any other idea?
Are there some errors listed when calling
dmesg | grep brcmfmac
Its just an idea.
Hey guys, just so you know, we’ve merged the PR linked above and a second one was just merged:
With that the wifi routine should work once again. As I do not own the RPi3B+ myself, I have to rely on you for testing. So simply restart openhabian-config to pull the latest update and try again.
Great stuff, Thom. I couldn’t sleep, so I tested it right away 
Here are the logs for the update (I still need to reboot and test with the ethernet cable pulled out):
2018-04-11_06:14:21_CEST [openHABian] Updating myself... OK - Commit history (oldest to newest):
6a550c7 - Add is_pithreeplus helper function, closes #374 (#376) (8 hours ago) <mues-lee> N
functions/helpers.sh | 6 +++++-
functions/system.sh | 8 ++++----
functions/wifi.sh | 4 ++--
3 files changed, 11 insertions(+), 7 deletions(-)
6a7648c - Update wifi function for stretch, resolves #374 (5 hours ago) <Thomas Dietrich> N
functions/wifi.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
openHABian configuration tool successfully updated.
Visit the development repository for more details: https://github.com/openhab/openhabian
The tool will now restart to load the updates...
2018-04-11_06:14:23_CEST [openHABian] Checking for root privileges... OK
2018-04-11_06:14:23_CEST [openHABian] Loading configuration file '/etc/openhabian.conf'... OK
2018-04-11_06:14:23_CEST [openHABian] openHABian configuration tool version: [master]v1.4.1-390(6a7648c)
2018-04-11_06:14:23_CEST [openHABian] Checking for changes in origin... OK
2018-04-11_06:14:31_CEST [openHABian] Setting up Wifi (PRi3 or Pine A64)...
$ apt -y install firmware-brcm80211
Reading package lists... Done
Building dependency tree
Reading state information... Done
firmware-brcm80211 is already the newest version (1:20161130-3+rpt3).
The following package was automatically installed and is no longer required:
triggerhappy
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ apt -y install wpasupplicant wireless-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
wireless-tools is already the newest version (30~pre9-12).
wpasupplicant is already the newest version (2:2.4-1+deb9u1).
The following package was automatically installed and is no longer required:
triggerhappy
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Not writing to '/etc/network/interfaces', wlan0 entry already available. You might need to check, adopt or remove these lines.
$ wpa_cli reconfigure
Selected interface 'p2p-dev-wlan0'
OK
$ ifdown wlan0
$ ifup wlan0
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
ifup: failed to bring up wlan0
OK (Reboot needed)
No:
rcmfmac: F1 signature read @0x18000000=0x15264345
[ 4.230988] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 4.231462] usbcore: registered new interface driver brcmfmac
[ 4.558390] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 4.559011] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28
Dear Thom, Thanks for your efforts. I upgraded FW and the openhabian-config lets me configure WIFI now. What I did.
Now:…
WLAN:
-
I have still no Wifi connection
-
I checked wpa_supplicant.conf and see that now WPA-PSK Key Line was inserted. But what I need is WPA2.
-
I checked openhabian.conf. Seems the same like before. Credentials are OK, but WPA-PSK Key Line not visible.
-
With iwlist I do not get a positive answer
[17:01:51] root@openHABianPi:/etc/wpa_supplicant# iwlist scanning
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
wlan0 Interface doesn’t support scanning : Network is down -
With iwconfig I see that my SSID was not taken:
[17:46:24] root@openHABianPi:/home/openhabian# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
LAN:
- When booting I see my old LAN IP configured,… but,… I can’t access the Raspi with MobaXterm anymore. I also don’t see my raspi in my routers list. Physical connection is OK (Ethernet LED Uplink LED blinks).
- With sudo route -n no routingtable visible
dear Thom, this update made my Raspberry not communicating anymore. I’m waiting with switching back to the version before, that you can request more information from me. If you do not need more information from my side, then I downgrade my raspi, to be able to test other things. Please consult me.
Try this
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
You’ll need to add or edit the following:
network={
ssid=“SSID”
psk=“WIFI PASSWORD”
}
Hope it will work for you
Cheers🙂
Thanks Bernie, As I said this is correctly set. Additionally openhabian-config WIFI configuration put a line for the WPA-PSK Key.
But since the firmwareupdate neither WIFI nor LAN is working anymore.
Nobody else is testing and experiencing this?
Hey @jayloo I’m not sure why your setup isn’t working. I do not own a RPi3B+ but one of the other active developers does. I hope he will soon do a few tests and make everything bulletproof.
Thanks for the offer but you can go back to a system that works for you. In general I’d always recommend Ethernet, so if you can, go for that!
OK, Thanks… Liebe Grüsse Jayloo