Updating Wi-Fi login details via openhabian-config requires debug?

Setup, Configuration and Use Installation
1

Moving my openhabian raspberry pi zero from one network, to another, I encountered an issue which doesn’t stop the connection, but it does issue warnings to debug. I was hoping to find out how to clean up these warnings, and perhaps amend the process so it’s more complete.

 $ sudo openhabian-config
    _ 30 System Settings
    __ 36 WiFi setup
    ___ Which Wifi (SSID) do you want to connect to? 
    ___ Password
    ___ <OK>

Prints this:

$ apt -y install wpasupplicant wireless-tools 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
wireless-tools is already the newest version.
wpasupplicant is already the newest version.
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 'wlan0'

Opening /etc/network/interfaces:

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1
iface wlan1 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Opening /etc/wpa_supplicant/wpa_supplicant.conf, the correct, updated details havve been stored:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
        ssid="updated_correct_SSID"
        psk="updated_correct_password"
}

And doesn’t pickup the IP address on load:

###############################################################################
################# openHABianPi ################################################
###############################################################################
##             Ip = Unable to parse ip. Please debug.
##        Release = Raspbian GNU/Linux 8 (jessie)
##         Kernel = Linux 4.9.35+
##       Platform = Raspberry Pi Zero W Rev 1.1

However, we have an IP address on the new network, and connects successfully

[10:45:53] openhabian@openHABianPi:~$ hostname -I
10.0.0.101 2001:8003:20d0:300:95ca:1380:8619:2980

Any thoughts on how to clean up this incongruity?

2

How is your experience running OH on a RPi 0W?

I’m sorry I don’t have any advice for your problem.

I was sent a demo model of a Banana Pi M2 Zero which is a lot like the RPi 0W with the major difference being it has a four core H2 processor verses the single core processor on the RPi 0W. Being able to reference experience running on the RPi 0W would be informative.

3

The Raspberry Pi Zero and Openhabian has been pretty impressive so far.

Install is now a straightforward process, the connections between devices on a network, simple Network Bindings are fine. Everything works pretty well. Having a backup SD already to go has made progress a lot quicker when I mess up.

As a result of yesterdays heatwave (39 degree’s C at 7:30am) which had a big impact on the performance of my MacBook and the RPi, I’ve gone back to a backup prior to changing the network.

There were two issues that occurred as a result of the network update.,

  1. Constant dhcp polling, ~255 times every couple of seconds for an entire IP range 10.0.0.0 - 10.0.0.255
2017-12-20 22:20:29.947 [INFO ] [work.internal.dhcp.DHCPListenService] - DHCP request for unknown address: 10.0.0.150
2017-12-20 22:20:30.973 [INFO ] [work.internal.dhcp.DHCPListenService] - DHCP request for unknown address: 10.0.0.151

One thing I found that was potentially related, that made me think my install was corrupted. In PaperUI:

Configure > Network Bindings >
[ON] Listen for dhcp requests (on is default, and is what mine was set to)
Usually a device requests an IP address in an IPv4 network with the help of DHCP as soon as it enters a network. If we listen to those packets, we can detect a device presence even faster. You need elevated access rights (see readme) for this to work.

  1. No ‘SPI-Provider’ Manifest header info. This info log was also running constantly for what seems like almost every installed component:
2017-12-20 22:32:40.517 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - Bundle Considered for SPI providers: org.eclipse.smarthome.automation.parser.gson
2017-12-20 22:32:40.554 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - No 'SPI-Provider' Manifest header. Skipping bundle: org.eclipse.smarthome.automation.parser.gson
2017-12-20 22:32:47.673 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - Bundle Considered for SPI providers: org.eclipse.smarthome.binding.wemo
2017-12-20 22:32:47.719 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - No 'SPI-Provider' Manifest header. Skipping bundle: org.eclipse.smarthome.binding.wemo
2017-12-20 22:32:48.387 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - Bundle Considered for SPI providers: org.eclipse.smarthome.config.discovery.upnp
2017-12-20 22:32:48.452 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - No 'SPI-Provider' Manifest header. Skipping bundle: org.eclipse.smarthome.config.discovery.upnp

After these start happening - a re-image was in order as nothing worked.

4

I’ll be interested to know if you have any performance issues like latency, long response times on the UIs, long times to process Rules or commands. The RPi W0 has roughly the same specs as the original RPi and OH is known to be pretty sluggish on it. I’ve still not set up a full config on my BPi M2 Zero but I can see that with a stock openHABian configured Armbian it is using up almost 100% of the memory and I’ve not yet installed any bindings or Rules.