Changes

Name parameter "EddystoneID" chosen to indicate the protocol that was configured in the EYE sensor, although it does not affect capturing. Manufacturer ID is taken from protocol description, passing 9bytes and capturing UUID and Type. AAFE00, to comply Manufacturer ID size which is  4 bytes, 00 is added. Beacon ID offset passes 23bytes of all sensor packet and captures 6bytes which are in this case Instance ID. ID is shown in the picture on the left side 123400000000. Additional Data Offset can be used to indicate the number of byte for additional data capturing. In this example 49 bytes are ignored and 2 bytes are taken, which indicates temperature.

Name parameter "EddystoneID" chosen to indicate the protocol that was configured in the EYE sensor, although it does not affect capturing. Manufacturer ID is taken from protocol description, passing 9bytes and capturing UUID and Type. AAFE00, to comply Manufacturer ID size which is  4 bytes, 00 is added. Beacon ID offset passes 23bytes of all sensor packet and captures 6bytes which is Instance ID in this case. ID is shown in the picture on the left side 123400000000. Additional Data Offset can be used to indicate the number of byte for additional data capturing. In this example 49 bytes are ignored and 2 bytes are taken, which indicates temperature. The process is very similar when iBeacon protocol is used. Example is shown in the picture on the right side.

'''Note''': Due to differencies in iBeacon and Eddystone advertising packets, number of Additional Data offset is different as well.<br>

'''Note''': Due to differencies in iBeacon and Eddystone advertising packets, number of Additional Data offset is different as well.<br>