RPIs constantly cycling, no iBeacons detected
Posted: Mon Jun 17, 2019 8:02 pm
Hi Karl.
Since upgrading to latest plugin release (and skipping an unknown number of intermediate releases), all my RPIs are constantly cycling. As in:
up
expired
IPconnection and BLE down
up
expired
IPconnection and BLE down
Additionally, no iBeacons are ever detected, even if I set to accept all new iBeacons. I haven't seen anything suspicious in the plugin logfile.
When I ssh to the RPI, I can see that almost all the files have been recently updated:
But there are definitely errors in the RPI log:
FWIW, I'm seeing the same behavior in 4 different ZeroW's connected by wifi (one of which also has 1-wire sensors). Everything worked as expected for a year or more before yesterday.
I'd appreciate any help to figure this out.
Thanks.
Since upgrading to latest plugin release (and skipping an unknown number of intermediate releases), all my RPIs are constantly cycling. As in:
up
expired
IPconnection and BLE down
up
expired
IPconnection and BLE down
Additionally, no iBeacons are ever detected, even if I set to accept all new iBeacons. I haven't seen anything suspicious in the plugin logfile.
When I ssh to the RPI, I can see that almost all the files have been recently updated:
- Code: Select all
$ ls -l ~/pibeacon
total 2124
-rwxrwxrwx 1 pi pi 1938 Jun 17 19:50 actions.py
-rwxrwxrwx 1 pi pi 19925 Jun 17 19:50 amg88xx.py
-rwxrwxrwx 1 pi pi 64587 Jun 17 19:50 apds9960.py
-rwxrwxrwx 1 pi pi 18156 Jun 17 19:50 as3935.py
-rwxrwxrwx 1 pi pi 22403 Jun 17 19:50 as726x.py
-rw-rw-rw- 1 pi pi 3615 Jun 17 18:59 beacon_ExistingHistory
-rwxrwxrwx 1 pi pi 41464 Jun 17 19:50 beaconloop.py
-rw-rw-rw- 1 pi pi 2036 Jun 17 20:26 beacon_parameters
-rwxrwxrwx 1 pi pi 11391 Jun 17 19:50 BLEconnect.py
-rwxrwxrwx 1 pi pi 19329 Jun 17 19:50 BLEsensor.py
-rwxrwxrwx 1 pi pi 35107 Jun 17 19:50 bme680.py
-rwxrwxrwx 1 pi pi 31084 Jun 17 19:50 bno055.py
-rwxrwxrwx 1 pi pi 4321 Jun 17 19:50 callbeacon.py
-rwxrwxrwx 1 pi pi 19863 Jun 17 19:50 ccs811.py
-rwxrwxrwx 1 pi pi 804 Feb 25 19:03 checkLogfile.py
-rwxrwxrwx 1 pi pi 1096 Jun 17 19:50 convert.py
-rwxrwxrwx 1 pi pi 1453 Jun 17 19:50 copyToTemp.py
-rwxrwxrwx 1 pi pi 8184 Jun 17 19:50 DHT.py
-rwxrwxrwx 1 pi pi 8149 Jun 17 19:50 displayDistance.py
drwxrwxrwx 2 pi pi 4096 Jun 7 2017 displayfiles
-rwxrwxrwx 1 pi pi 75914 Jun 17 19:50 display.py
-rwxrwxrwx 1 pi pi 210 Jun 17 20:29 doGPIOatStartup.py
<<--SNIP-->>
But there are definitely errors in the RPI log:
- Code: Select all
$ tail -F /var/log/piBeacon.log
20190617-20:29:12 INPUTgpio L:-1= starting setup sensors
20190617-20:29:12 master L:-1= Master adhocWifi is:-1 ; G.wifiType is:normal
20190617-20:29:12 Wire18B20 L:-1= error in Line 513 has error=global name 'wifiIP' is not defined
20190617-20:29:12 master L:-1= error in Line 513 has error=global name 'wifiIP' is not defined
20190617-20:29:22 master L:-1= error in Line 513 has error=global name 'wifiIP' is not defined
20190617-20:29:22 master L:-1= error in Line 513 has error=global name 'wifiIP' is not defined
20190617-20:29:22 master L:-1= IP find:::: Indigo IP#>>172.23.2.10<<; wifiIP >><<; eth0IP: >><<; hostnameIP >>['172.23.2.60']<<; ipAddressRead >>172.23.2.60<<; requested Config:{'wlan0': {'on': 'dontChange', 'useIP': 'use'}, 'eth0': {'on': 'dontChange', 'useIP': 'use'}}
20190617-20:29:23 master L:-1= testPing input>>172.23.2.1<< indigoIP>>172.23.2.10<<
20190617-20:29:23 master L:-1= DNS server reachable at:172.23.2.1
20190617-20:29:23 master L:-1= testPing input>><< indigoIP>>172.23.2.10<<
FWIW, I'm seeing the same behavior in 4 different ZeroW's connected by wifi (one of which also has 1-wire sensors). Everything worked as expected for a year or more before yesterday.
I'd appreciate any help to figure this out.
Thanks.