Changes

[[File:Beacon detection.gif]]

[[File:Beacon detection.gif]]

<br>

<br>

New firmware has two Beacon lists, so it is possible to create two separate lists of beacons, standard one with Beacons ID (UUID:Major:Minor, or Namespace:InstanceID) and new one according Beacon Name (by name or prefix, for example all beacons with prefix "ID1" can be saved.

*The New firmware has two Beacon lists, so it is possible to create two separate lists of beacons, standard one with Beacons ID (UUID:Major:Minor, or Namespace:InstanceID) and new one according Beacon Name (by name or prefix, for example all beacons with prefix "ID1" can be saved.)

<br>

<br>

* '''Beacon ID''' - configurator allows to configure beacon id in iBeacon or Eddystone format.

* '''Beacon ID''' - configurator allows to configure beacon id in iBeacon or Eddystone format.

<br>

<br>

'''Eye feature mode: Proximity'''

'''Eye feature mode: Proximity'''

EYE beacon Proximity events is a functionality which creates three different types of records, depending on the captured Beacons RSSI level. This functionality is only supported with Teltonika EYE beacons.<br> Proximity events consist of near, away and lost events: <br>

EYE beacon Proximity events is a functionality which creates three different types of records, depending on the captured Beacons RSSI level. This functionality is only supported with Teltonika EYE beacons.<br> Proximity events consist of near, away and lost events: <br>

'''Lost & Found  EYE Beacon feature.'''<br>

'''Lost & Found  EYE Beacon feature.'''<br>

Purpose of this functionality is to periodically create records with all EYE Beacon list and create on change records only when EYE Beacon is lost or found. Lost and Found Beacon records only include EYE Beacon which was lost or found, not the full Beacon list. <br>

Purpose of this functionality is to '''periodically''' generate records with all EYE Beacon list (AVL ID: 10828) and create eventual '''On Change''' records only when EYE Beacon is lost (AVL ID: 10831) or found (AVL ID: 10829). <br>

If multiple EYE Beacons were found or lost at the same time, multiple will be  included into the record. <br>

Lost and Found Beacon records only include EYE Beacon which was lost or found, not the full Beacon list. <br>

If Visible Beacon List is enabled, Beacon records containing the list of visible beacons will be generated according to the configured period parameters Record Period on Move ID:256 and Record Period on Stop ID:257.

*If multiple EYE Beacons were found or lost at the same time, multiple will be  included into the record. <br>

*If Visible Beacon List is enabled, Beacon records containing the list of visible beacons will be generated according to the configured period parameters ''Record Period on Move'' and ''Record Period on Stop''

Advanced Beacon protocol is being used to send Lost & Found records.  <br>

Advanced Beacon protocol is being used to send Lost & Found records.  <br>

Note:Same AVL ID’s as for Proximity events are being used, since two features cannot work at the same time.

Note:Same AVL ID’s as for Proximity events are being used, since two features cannot work at the same time.

*'''AVL ID: 10828''' Visible Beacon List

*'''AVL ID: 10828''' Visible Beacon List (periodic)

*'''AVL ID: 10829''' Found Beacon List

*'''AVL ID: 10829''' Found Beacon List (On Change)

*'''AVL ID: 10831''' Lost Eye Beacon List

*'''AVL ID: 10831''' Lost Eye Beacon List (On Change)

<br>  

<br>  

'''Proximity IO''' elements have the following structure:<br> [[File:1st beacon protocol version.png|border]]

'''Proximity IO''' elements have the following structure [[File:1st beacon protocol version.png|bottom|border]]

==<p style="font-size:32px><span style="color:#0054A6">EYE Beacon Protocol overview</span></p>==

==<p style="font-size:32px><span style="color:#0054A6">EYE Beacon Protocol overview</span></p>==