piBeacon: presence monitoring plugin discussions

Posted on
Sat Jan 05, 2019 11:42 pm
GlennNZ offline
Posts: 506
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

kw123 wrote:
I have a fix, but hard to test .. I I could ask you?

on another note. just checked on my rpi3+ and ibeacon does not work anymore.. even with an external bye adapter.. no change for some time ..

there goes the weekend


Karl


Thanks Karl
Happy to test.
Glenn

Posted on
Sun Jan 06, 2019 5:49 pm
kw123 offline
User avatar
Posts: 6104
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

Glenn: try v .263

Posted on
Mon Jan 07, 2019 4:40 am
GlennNZ offline
Posts: 506
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

Hi Karl,

Trying now, have lost connection to wlan1 rpi (sometimes happens)

But with other wifi ones now getting this:
Code: Select all
pi@raspberrypi:~ $ cd /home/pi/pibeacon;sudo python master.py
Killed
pi@raspberrypi:~/pibeacon $ 20190107-21:35:33  master  IP find:::: wifiIP >>127.0.0.1<<; eth0IP: >><<;   hostnameIP >>['192.168.1.187']<<;   ipAddressRead >>192.168.1.187<<
20190107-21:35:37  master U.getIPNumberMaster bad IP number ...  ipHostname >>['192.168.1.187']<<  old from file ipAddressRead>>192.168.1.187<< not in sync with ifconfig output: wifi0IP>>127.0.0.1<<;   eth0IP>>
20190107-21:35:42  master  IP find:::: wifiIP >>127.0.0.1<<; eth0IP: >><<;   hostnameIP >>['192.168.1.187']<<;   ipAddressRead >>192.168.1.187<<
20190107-21:35:46  master U.getIPNumberMaster bad IP number ...  ipHostname >>['192.168.1.187']<<  old from file ipAddressRead>>192.168.1.187<< not in sync with ifconfig output: wifi0IP>>127.0.0.1<<;   eth0IP>>
20190107-21:35:51  master  IP find:::: wifiIP >>127.0.0.1<<; eth0IP: >><<;   hostnameIP >>['192.168.1.187']<<;   ipAddressRead >>192.168.1.187<<
20190107-21:35:56  master U.getIPNumberMaster bad IP number ...  ipHostname >>['192.168.1.187']<<  old from file ipAddressRead>>192.168.1.187<< not in sync with ifconfig output: wifi0IP>>127.0.0.1<<;   eth0IP>>
x20190107-21:36:01  master  IP find:::: wifiIP >>127.0.0.1<<; eth0IP: >><<;   hostnameIP >>['192.168.1.187']<<;   ipAddressRead >>192.168.1.187<<


Code: Select all
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:15:0f:3a  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 29  bytes 4548 (4.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 29  bytes 4548 (4.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.187  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::ba27:ebff:fe40:5a6f  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:40:5a:6f  txqueuelen 1000  (Ethernet)
        RX packets 905  bytes 105966 (103.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 211  bytes 29950 (29.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Another one:

Code: Select all
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:e9:a7:c5  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 14  bytes 1920 (1.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 14  bytes 1920 (1.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.189  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::ba27:ebff:febc:f290  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:bc:f2:90  txqueuelen 1000  (Ethernet)
        RX packets 346  bytes 41036 (40.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 206  bytes 27352 (26.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@raspberrypi:~/pibeacon $ 20190107-21:41:25  master  IP find:::: wifiIP >>127.0.0.1<<; eth0IP: >><<;   hostnameIP >>['192.168.1.189']<<;   ipAddressRead >>192.168.1.189<<
20190107-21:41:38  master U.getIPNumberMaster bad IP number ...  ipHostname >>['192.168.1.189']<<  old from file ipAddressRead>>192.168.1.189<< not in sync with ifconfig output: wifi0IP>>127.0.0.1<<;   eth0IP>>
20190107-21:41:43  master  IP find:::: wifiIP >>127.0.0.1<<; eth0IP: >><<;   hostnameIP >>['192.168.1.189']<<;   ipAddressRead >>192.168.1.189<<



Posted on
Mon Jan 07, 2019 12:26 pm
kw123 offline
User avatar
Posts: 6104
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

should be fixed in .264

Code: Select all
         if ifConfigSections[ii].find("wlan0  ") > -1 or ifConfigSections[ii].find("wlan0:") > -1 or \
            ifConfigSections[ii].find("wlan1  ") > -1 or ifConfigSections[ii].find("wlan1:") > -1:

> -1 was missing in line one when I added the "or"

Karl

Posted on
Mon Jan 07, 2019 11:28 pm
GlennNZ offline
Posts: 506
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

Thanks
Running now .. one typo found I think.. will update if anything else.

Code: Select all
 piBeacon Error                  error in socket-send to rPi:192.168.1.184  [{"cmdLine": "setTime=2019-01-08 16:24:57.665683", "command": "general"}]
   piBeacon Error                  in Line '6542' has error='global name 'sself' is not defined'
   piBeacon Error                  {u'192.168.1.184': {u'count': 0, u'pi': u'4', u'time': 1546924953.854585}}
   piBeacon Error                  error in socket-send to rPi:192.168.1.184  [{"cmdLine": "setTime=2019-01-08 16:24:57.666818", "command": "general"}]
   piBeacon Error                  in Line '6542' has error='global name 'sself' is not defined'
   piBeacon Error                  {u'192.168.1.184': {u'count': 1, u'pi': u'4', u'time': -1546925097.666811}}



seems largely cosmetic and otherwise all good - rpi wlan1 up and going, connecting fine.

Glenn

Posted on
Tue Jan 08, 2019 1:17 am
kw123 offline
User avatar
Posts: 6104
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

fixed in v .266. -- sorry fo the many typos

Karl
GN

Posted on
Tue Jan 08, 2019 1:56 am
GlennNZ offline
Posts: 506
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

kw123 wrote:
fixed in v .266.
Karl


Upgraded and all good!

Who is online

Users browsing this forum: No registered users and 0 guests