- Posted on
Mon Dec 24, 2018 9:56 am
-
kw123
offline
-
- Posts: 8366
- Joined: May 12, 2013
- Location: Dallas, TX
-
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#