iBeacon shows as expired but it's not

[kw123]

does your RPI have a single ip#?
!!! If not, no guarantee what so ever!!!
That will screw things up big time, constant switching, expiring ...

[johnfdl]

Yes, it has a single IP. I included the ifconfig in a previous post showing it had just one IP after I disabled the wireless.

[kw123]

Ok could you do debuglog all in config
And post plugin.log
Mask the passwords


Sent from my iPhone using Tapatalk

[johnfdl]

rPi and Beacon is currently showing up. Here's the log;

[kw123]

There is still a connect problem
What is your connection speed. Do a ping


Sent from my iPhone using Tapatalk

[johnfdl]

Code: Select all

Johns-MacBook-Pro-3:~ johndeluca$ ping 192.168.0.43
PING 192.168.0.43 (192.168.0.43): 56 data bytes
64 bytes from 192.168.0.43: icmp_seq=0 ttl=64 time=2.603 ms
64 bytes from 192.168.0.43: icmp_seq=1 ttl=64 time=6.065 ms
64 bytes from 192.168.0.43: icmp_seq=2 ttl=64 time=1.432 ms
64 bytes from 192.168.0.43: icmp_seq=3 ttl=64 time=3.656 ms
64 bytes from 192.168.0.43: icmp_seq=4 ttl=64 time=2.349 ms
64 bytes from 192.168.0.43: icmp_seq=5 ttl=64 time=1.453 ms
64 bytes from 192.168.0.43: icmp_seq=6 ttl=64 time=1.353 ms
64 bytes from 192.168.0.43: icmp_seq=7 ttl=64 time=12.735 ms
64 bytes from 192.168.0.43: icmp_seq=8 ttl=64 time=2.144 ms
64 bytes from 192.168.0.43: icmp_seq=9 ttl=64 time=2.220 ms
64 bytes from 192.168.0.43: icmp_seq=10 ttl=64 time=12.672 ms
64 bytes from 192.168.0.43: icmp_seq=11 ttl=64 time=2.344 ms
64 bytes from 192.168.0.43: icmp_seq=12 ttl=64 time=2.206 ms
64 bytes from 192.168.0.43: icmp_seq=13 ttl=64 time=3.668 ms
64 bytes from 192.168.0.43: icmp_seq=14 ttl=64 time=2.174 ms
64 bytes from 192.168.0.43: icmp_seq=15 ttl=64 time=1.993 ms
64 bytes from 192.168.0.43: icmp_seq=16 ttl=64 time=2.494 ms
64 bytes from 192.168.0.43: icmp_seq=17 ttl=64 time=2.235 ms
64 bytes from 192.168.0.43: icmp_seq=18 ttl=64 time=6.399 ms
64 bytes from 192.168.0.43: icmp_seq=19 ttl=64 time=12.955 ms
64 bytes from 192.168.0.43: icmp_seq=20 ttl=64 time=2.255 ms
64 bytes from 192.168.0.43: icmp_seq=21 ttl=64 time=1.658 ms
64 bytes from 192.168.0.43: icmp_seq=22 ttl=64 time=1.174 ms
64 bytes from 192.168.0.43: icmp_seq=23 ttl=64 time=3.698 ms
64 bytes from 192.168.0.43: icmp_seq=24 ttl=64 time=2.184 ms
^C
--- 192.168.0.43 ping statistics ---
25 packets transmitted, 25 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.174/3.845/12.955/3.529 ms
Johns-MacBook-Pro-3:~ johndeluca$ 

Note: MacBookPro is connected via Wifi | rPi is ethernet connected.

[kw123]

so it is not speed.

there must be some other messages in your logfile

could you restart the plugin?

and which version are you running?

Karl

[johnfdl]

Karl,

I ordered two Nonda iHere beacons from amazon. They are coming tomorrow. Let me experiment with them to be sure I don't just have a beacon that has gone bad. If I have the same trouble, I'll re-engage you....but I don't want to drag you down a rathole if it's just a bad beacon.

The rPi has been up since yesterday.

[kw123]

Just FYI: Beacons stop pinging when the iPhone app is running


Sent from my iPhone using Tapatalk

[johnfdl]

Yes....I am aware of that. I killed the app on my phone. New Beqcons arrived today and appear to be working properly....so perhaps the Beacon is the issue.

[kw123]

just FOI- the beacon that does not work: what kind of beacon is it?

Karl

[johnfdl]

Nonda iHere (triangle usb). It worked fine for years, but seems to have gone bad. My two new Nonda iHere beacons have been flawless now for a week.

[kw123]

when you charge it does it go green?

[johnfdl]

Yes, it does go green, so it's not that it is dead.

[kw123]

You could try the iHere app to revitalize it

Don’t forget to stop the app once you are done.


Sent from my iPhone using Tapatalk