piBeacon: 3- presence monitoring download

[roquej]

Karl,

I am using BLE Scanner (Pally BLE Scanner) in IOS

JP

[kw123]

Still don't see he new tile.
Went away from other tiles holding the new tile next to the iPhone and no signal better than -90 dbm and no "tile" name.
How do you know you detect a new tile?



Sent from my iPhone using Tapatalk

[roquej]

Still don't see he new tile.
Went away from other tiles holding the new tile next to the iPhone and no signal better than -90 dbm and no "tile" name.
How do you know you detect a new tile?

Empty room, only the new slim Tile present and it shows in the scanner (see enclosed image). Leave room, 3 floors away and no Tile showing in scanner. Is not the most scientific test, but logical. What else would you suggest I could do to test it?

Sent from my iPhone using Tapatalk

Sent from my iPhone using Tapatalk

[kw123]

Mine does not see the new tile. The old one yes.
Are you sure it's a new one?


Sent from my iPhone using Tapatalk

[roquej]

Mine does not see the new tile. The old one yes.
Are you sure it's a new one?

Karl,

Just did another test. As far as I can tell, the Tile Slim is the BEF7FEB0 device in the picture below, which is consistent with my earlier picture.



I ran this test with only my wife's wallet in an elevator about 11 floors away from my original Tile, no one else around and 10 miles from the picture yesterday. Therefore I think is safe to assume I wasn't picking a random Tile yesterday.

Then when back to our room 11 floors up (on quick holiday for Halloween) and ran the test with both Tiles in the room.



As you can see, the original Tile shows as F1460807 along with the assumed Slim Tile. I also picked my XY, from my compute bag.

Again, not scientific but the reproducible results let me to believe that I am picking up the Slim Tile.

Hope this helps.

JP

Sent from my iPhone using Tapatalk

Sent from my iPhone using Tapatalk

[kw123]

Don't know what I am droning wrong. I see all my old tiles but not the new one. Holding it next to the iPhone and far away from the others. No tile recognized. I have a wallet tile



Sent from my iPhone using Tapatalk

[kw123]

posted v 7-28-3

added plugin now supports the following DISPLAYS connected to the RPI
-OLED ssh1106 (i2c) 128x44 monochrome ~ $10 https://www.amazon.com/gp/product/B016H ... UTF8&psc=1
-OLED ssd1306(i2c) 128x64 monochrome ~ $10 https://www.amazon.com/gp/product/B00O2 ... UTF8&psc=1
-OLED ssd1351 (spi) 128x128 rob ~ $20 https://www.amazon.com/gp/product/B01HH ... UTF8&psc=1
-LED RGBmatrix32x32 32x,32 adafruit ~ $30 (you need HAT + LED panel)
-LED RGBmatrix64x16 64x16 adafruit ~ $30 (you need HAT + LED panel)
-LED RGBmatrix64x32 64x32 adafruit ~ $80 (you need HAT + LED panel) https://www.adafruit.com/product/2278
-LED RGBmatrix96x32 96x32 adafruit ~ $ 100 (you need HAT + LED panel)
for the hardware setup: https://learn.adafruit.com/adafruit-rgb ... spberry-pi

You can send text via action, menu or python to the display, or the RPI can use any temp, humidity, pressure reading to display directly.
You can select scrolling text ,lines.. left,right,up,down and many more things

all config and software will be managed by the plugin. you need to connect the pins to the proper RPI pins though.
For i2c its just 4 cables,
For SPI :the plugin device edit shows some help on that.
For the adafruit LED follow the adafruit hardware install, do not install any software.

fixes:
many smaller things , formats, timeouts, automatic updates of RPI, access rights on RPI ...

Karl

[kw123]

released 7-29-11 (top of this thread)

fixed, tuned:
- after go live of i7 found an error in the plugin , under some circumstance caused an error ( thanks to Wouter for finding it)
- streamlined the DISPLAY part, fine tuned look and feel
- added a function in the plugin (in menu (un)ignore family of beacons) which allows to set ALL beacons active / ignore
- added function in beacon device edit to set individual iBeacons active/ignore state
the last 2 help when things get screwy

added support for adafruit 1.8" TFT display

Karl

(*) will add support for 3.5" display in next release, then ~ 10 displays are supported. I guess I can stop there.

[kw123]

posted v 7-29-12

added support of 7 inch "original" pi display. This looks really nice., very sharp letters colors and very fast

You can show the sensors values or any text on this display as with the other display devices. Scrolling or custom text can be edited in sensor device edit.

you might need to run software upgrade / update on the RPI (sudo python installLibs.py &)
and then if your image is upside down:
sudo nano /boot/config.txt
and add line at the end:
display_rotate=2
CTRL-o and CTRL-x to save and exit
and reboot.


I guess thats it for displays: 4 OLED ~ 1 inch, 1 TFT ~ 2 inch, RGB LED .. 92x.32, 7Inch 800x480) supported.


Karl

[kw123]

posted v 7-29-15

fixed:
some weird issue with GPIO sensor vs other sensor conflict.

improved:
look and feel for 7 inch display, font sizes etc for clock, distance .. modes.

Karl

[kw123]

poster v 7-29-17

fixes:
lots of small things: restart of RPI's, error controls. ...


added:
== re-aranged the RPI management. It now easier and cleaner to use
== added feature (in menu send get programs etc) to get RPi stats into the indigo log file:

• ps -ef | grep python==> which programs are running
• free -o -h ==> info on used / free memory
• df ==> disk utilization and mapping
• cat /proc/cpuinfo ==> CPU info
• hostname -I ==> what is my IP number
• ifconfig ==> general network info
• i2cdetect -y 1 ==> i2c channel info

== I encourage to enable the RAM disk for log files and temp files in RPI device edit. this will reduce the writes to the SSD SIGNIFICANTLY

== Also added an RPI shutdown command in menu, so you don't have to just pull the power plug.

== added a different command to reboot or shutdown the RPI. In some incidences - I have not figured out why -- the regular "sudo reboot" does not stop the RPI. For this case the reboot / shutdown can be set to "sync;sync;sync; sudo reboot -f" that seems to always work, but is not the nice way to reboot the system .. so just in case your PRI show this, there is an option for this.


this is the thanks giving release ..
Karl


the output into the log file for the stats option looks like:

Code: Select all

09:19:05             -stats from rpi# 2 
===ps===
root       976     1  0 Nov25 ?        00:01:20 /usr/bin/python /home/pi/pibeacon/sensors.py
root       982     1  0 Nov25 ?        00:09:01 /usr/bin/python /home/pi/pibeacon/beaconloop.py
root       984     1  0 Nov25 ?        00:01:28 /usr/bin/python /home/pi/pibeacon/receiveGPIOcommands.py 9999
root      1020     1  0 Nov25 ?        00:05:59 /usr/bin/python /home/pi/pibeacon/getsensorvalues.py
root     16448     1  6 08:52 ?        00:01:39 /usr/bin/python /home/pi/pibeacon/display.py
===mem===
             total       used       free     shared    buffers     cached
Mem:          434M       299M       135M        55M        30M       210M
Swap:          99M         0B        99M
===disk===
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/root       29773020 2573024  25940036  10% /
devtmpfs          218260       0    218260   0% /dev
tmpfs             222544       0    222544   0% /dev/shm
tmpfs             222544    4596    217948   3% /run
tmpfs               5120       4      5116   1% /run/lock
tmpfs             222544       0    222544   0% /sys/fs/cgroup
tmpfs              61440   52128      9312  85% /var/log
/dev/mmcblk0p1     64456   21328     43128  34% /boot
tmpfs              44512       0     44512   0% /run/user/1000
tmpfs               1024      16      1008   2% /home/pi/pibeacon/temp
===cpu===
processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 697.95
Features	: half thumb fastmult vfp edsp java tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2708
Revision	: 0010
Serial		: 000000002f1b1f50
===hostname===
xxxxxxxx 
===ifconfig===
eth0      Link encap:Ethernet  HWaddr b8:27:eb:1b:1f:50  
          inet addr:xxxxxxx  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::b353:51f6:14af:313b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1329474 errors:0 dropped:824 overruns:0 frame:0
          TX packets:65235 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:101416253 (96.7 MiB)  TX bytes:11736460 (11.1 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:200 errors:0 dropped:0 overruns:0 frame:0
          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:16656 (16.2 KiB)  TX bytes:16656 (16.2 KiB)

===i2c===
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- 39 -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
pi@raspberrypi:~$ exit
logout
Connection to xxxxxxx closed.

[kw123]

posted v 7-29-19 (top of this Thread)

fixes added: some checks for NEW install, make sure variables etc are initialized

Karl

[kw123]

POSTED V 7-29-20

fixed:
1. when starting from stretch some variables where not properly initialized
2. a "rejects" file on the rPi could blow up: when you have eg an XY iBeacon and "ignore" one of the active MAC# the rejects file will grow by 10-100 entries per second.Now that file gets updates once every10 minutes for each beacon. It is used to gather stats: you can look at the file ~/Documents/piBeacon/rejected/rejectedByPi.json. It will list all rejected iBeacons: when first encountered, when last and how often, why rejected(MAC# or UUID family), and by which RPI. No other actions are based on this file.. is for future use (mine has ~ 12k iBeacons in it
it looks like this:

Code: Select all

"00:EA:23:09:8":{"uuid":"07775dd0111b11e491910800200c9a66-8969-33111"  ,"first":"2016-08-02 06:20:59","last":"2016-08-02 06:20:59","count":1          ,"reason":"MAC"    ,"rPi":"8"},
"00:EA":{"uuid":"07775dd0111b11e491910800200c9a66-8969-33111"  ,"first":"2016-08-03 01:50:57","last":"2016-08-03 01:50:57","count":1          ,"reason":"MAC"    ,"rPi":"1"},
"63:93:E7:84:F8:C0":{"uuid":"ff4c000c0e004a075e31aa6dc6b0-36501-56675"     ,"first":"2016-09-12 20:41:40","last":"2016-09-12 20:49:15","count":27         ,"reason":"UUID"   ,"rPi":"6"},
"6B:E9:2B:7A:DD:AC":{"uuid":"ff4c000c0e00d2096da16f9fb6ba-18291-45111"     ,"first":"2016-09-12 20:54:59","last":"2016-09-12 20:59:46","count":15015      ,"reason":"UUID"   ,"rPi":"0,1,2,4,5,6,8,9"},

By doing this going forward the count is naturally screwed up, data up to now is when ever the iBeacon sends a signal, going forward if the iBeacon send a signal in 10 minutes intervals.- the number is now a mixture of these 2. but having files growing to 200Mbyte is not good


Karl

[kw123]

posted v 7-29-21

fixed:
hopefully final fix: when starting from scratch still some variables not initialized.
I deleted setup and could recreate the error ... . and a fix it


Karl

[kw123]

posted v7-29-22

fixed:
- not updating beacons when do not accept new beacons was switched on. (did not update a file with a list of existing beacons on the api)
- temp offset was ignored for one type of sensors (BME280)

Improved/ changed
- the offset function ( when eg your pressure is off as compared local underground info) for Humidity, Temp, Pressure is now applied on the RPI BEFORE being send to the plugin / indigo server. this was needed as you can directly display these things on the RPI
- updates of config (list of new beacons, ignored beacons, parameters, ...) etc send to RPI are now factor 2-3 faster - done every 10 minutes or so (finally understood EXPECT (~80%), replaced may of the long sleeps with the proper expect functions)


the units for the offset are the in original units as delivered by the sensors: Hum =%, Temp= Celsius, Pressure = pascal, so if you display your pressure in in Hg you need to do some conversion for the offset:
1 inch Hg = 3386.39 Pascal
1 Pascal = 0.0002953 in Hg
eg: if you are off by 0.1 [in Hg] your pressure offset (set in indigo device edit for the pressure sensor) should be 338.6 [Pascal]


Karl