Difference between revisions of "BLEbeaconsScanner"
From AMTech WikiDocs
(→BLEbeaconsScanner) |
(→BLEbeaconsScanner) |
||
| (10 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
=== BLEbeaconsScanner === | === BLEbeaconsScanner === | ||
| − | Bridge | + | |
| − | *Edge Intelligence | + | Bridge Bluetooth low energy Apple's iBeacon and Google's Eddystone protocols to IoT DAP /amtech/linkeddata/types/composite/entity/BLEbeaconsScanner |
| − | **Smoothing for new, broadcast and lost tag | + | |
| − | **iBeacon and eddystone protocols | + | * Edge Intelligence |
| − | *Placeholders (See [[Sensor%27s_network#Placeholders_substitution|Placeholders]]) | + | **[[Smoothing_observations|Smoothing observations]] |
| + | **[[Observations delivery manager]] | ||
| + | ** Smoothing for new, broadcast and lost tag | ||
| + | ** [https://en.wikipedia.org/wiki/IBeacon iBeacon] and [https://github.com/google/eddystone/blob/master/protocol-specification.md Eddystone] protocols | ||
| + | *** Eddystone package filters: possibility to filter eddystone messages according to their package type ''URL'' or ''UID'' | ||
| + | * Placeholders (See [[Sensor%27s_network#Placeholders_substitution|Placeholders]]) | ||
** #{smoothingResult} if smoothing has been set to true EddystoneScan observations can be sent to a topic depending of the smoothing process result [new|lost|broadcast] | ** #{smoothingResult} if smoothing has been set to true EddystoneScan observations can be sent to a topic depending of the smoothing process result [new|lost|broadcast] | ||
** #{eddystoneType} Eddystone frame types, permissible values are uid, url and tlm | ** #{eddystoneType} Eddystone frame types, permissible values are uid, url and tlm | ||
| − | ***uid broadcasts an opaque, unique 16-byte Beacon ID composed of a 10-byte namespace and a 6-byte instance. | + | *** uid broadcasts an opaque, unique 16-byte Beacon ID composed of a 10-byte namespace and a 6-byte instance. |
| − | ***url broadcasts a URL using a compressed encoding format in order to fit more within the limited advertisement packet. | + | *** url broadcasts a URL using a compressed encoding format in order to fit more within the limited advertisement packet. |
| − | ***tlm telemetrics | + | *** tlm telemetrics |
** #{eddystoneNamespace} 10-byte ID Namespace | ** #{eddystoneNamespace} 10-byte ID Namespace | ||
** #{eddystoneInstance} 6-byte ID Instance | ** #{eddystoneInstance} 6-byte ID Instance | ||
** #{proximityarea} Set the EddystoneHub proximity area supported property value to targetThing proximity value field | ** #{proximityarea} Set the EddystoneHub proximity area supported property value to targetThing proximity value field | ||
** #{bleProtocol} [eddystone|ibeacon] | ** #{bleProtocol} [eddystone|ibeacon] | ||
| − | ** #{ibeaconUuid | + | ** #{ibeaconUuid} iBeacon advertised uuid |
| − | ** #{ | + | ** #{ibeaconMajor} iBeacon advertised major |
| − | ** #{ | + | ** #{ibeaconMinor} iBeacon advertised minor |
| − | ** #{ | + | ** #{ibeaconProximity} current proximity from sacanner [unknown|immediate|near|far] |
| − | *Produced observations (see /amtech/linkeddata/types/composite/observation) | + | * Produced observations (see /amtech/linkeddata/types/composite/observation) |
| − | **/amtech/linkeddata/types/composite/observation/observationresourcecrud | + | ** /amtech/linkeddata/types/composite/observation/observationresourcecrud |
| − | **/amtech/linkeddata/types/composite/observation/ibeaconScan | + | ** /amtech/linkeddata/types/composite/observation/ibeaconScan |
| − | + | ** /amtech/linkeddata/types/composite/observation/eddystoneScan | |
| − | + | ||
| − | **/amtech/linkeddata/types/composite/observation/eddystoneScan | + | |
Latest revision as of 15:36, 19 September 2018
BLEbeaconsScanner
Bridge Bluetooth low energy Apple's iBeacon and Google's Eddystone protocols to IoT DAP /amtech/linkeddata/types/composite/entity/BLEbeaconsScanner
- Edge Intelligence
- Smoothing observations
- Observations delivery manager
- Smoothing for new, broadcast and lost tag
- iBeacon and Eddystone protocols
- Eddystone package filters: possibility to filter eddystone messages according to their package type URL or UID
- Placeholders (See Placeholders)
- #{smoothingResult} if smoothing has been set to true EddystoneScan observations can be sent to a topic depending of the smoothing process result [new|lost|broadcast]
- #{eddystoneType} Eddystone frame types, permissible values are uid, url and tlm
- uid broadcasts an opaque, unique 16-byte Beacon ID composed of a 10-byte namespace and a 6-byte instance.
- url broadcasts a URL using a compressed encoding format in order to fit more within the limited advertisement packet.
- tlm telemetrics
- #{eddystoneNamespace} 10-byte ID Namespace
- #{eddystoneInstance} 6-byte ID Instance
- #{proximityarea} Set the EddystoneHub proximity area supported property value to targetThing proximity value field
- #{bleProtocol} [eddystone|ibeacon]
- #{ibeaconUuid} iBeacon advertised uuid
- #{ibeaconMajor} iBeacon advertised major
- #{ibeaconMinor} iBeacon advertised minor
- #{ibeaconProximity} current proximity from sacanner [unknown|immediate|near|far]
- Produced observations (see /amtech/linkeddata/types/composite/observation)
- /amtech/linkeddata/types/composite/observation/observationresourcecrud
- /amtech/linkeddata/types/composite/observation/ibeaconScan
- /amtech/linkeddata/types/composite/observation/eddystoneScan
