What setting safe to edit to speed up the time to see beacon

mpovolo · Post by **mpovolo** » Sat Dec 22, 2018 3:20 pm

I have the beacon running the action when seen by the pi but it’s a little slow to run. What setting is safe to use to change that.

Thanks

kw123 · Post by **kw123** » Sat Dec 22, 2018 3:23 pm

It should be <1 sec from not present = expired to present = up
If not something is wrong.

Up to down to expired is default 90 seconds if no signal.

Sent from my iPhone using Tapatalk

mpovolo · Post by **mpovolo** » Sat Dec 22, 2018 3:33 pm

Thank you. I’ll play around some more and see why.

kw123 · Post by **kw123** » Sat Dec 22, 2018 8:17 pm

You can check 2 things

Ssh to rpi

cd pibeacon
tail -F temp/messageSend

Cap F and cap S

That show s the info send from the rpi to the plugin

In plugin set iBeacon debug on that shows the messages coming in ...

These 2 logs should tell you a lot.

Sent from my iPhone using Tapatalk

kw123 · Post by **kw123** » Mon Dec 24, 2018 9:56 am

a little clarification on timings:

1. if there is a new iBeacon or a ibeacon that was not present in the last cycle (= no signal) and is now, a message is send immediately rpi -> plugin

2. 60 secs after last msg RPI--> plugin (you can set in rpi device edit) a summary of all received messages is send rpi--> plugin

3. signal strength variations (eg -40 ..-90 ) normally have NO impact on sending message RPI --> plugin
BUT you can send max signal variation in beacon device edit. eg set xx to 20 ==> if new signal is outside average by xx message will be send to plugin

4. fast down (set in ibeacon device edit). if signal goes below fast down cutoff a message is send rpi--> plugin = iBeacon is away = down. it will not use expiration time.

Karl

ps:
msg rpi --> plugin :~= {Mac#:[ n signals, average signal strength, tx power, batLevel] } for each Mac#

Indigo Domotics