Hello,
I am working with EYE SENSOR / BTSMP1 and I am trying to make the sensor advertise the sensor data using the 3) EYE Sensors protocol, set via the mobile app.
Per documentation, when the sensor is set as such it should advertise only the sensor packet of 31 bytes, where the EYE Flags are in the byte 21, and the actual sensor readings are byte 22 to 30, byte 31 being reserved.
However, when I listen and print the raw advertised data, it only has 30 bytes, and it appears as the values cannot be correctly parsed. It appears as the whole packet content is different from the protocol I see in the documentation:
Sample outputs for raw advertised data, when Sensors protocol is set for advertising.
00 00 6E A5 0C 20 02 00 DC 99 FD 3F 2C 00 00 00 01 00 00 00 14 A0 FD 3F 1C A3 FD 3F D4 A2
I have another sensor which I left on Eddystone for the advertised protocol, and here it seems that I have 31 bytes as per documentation
7E 1C 09 40 C8 D0 FB 3F 28 9F FD 3F 2C 00 00 00 01 00 00 00 B8 A0 FD 3F 4C A3 FD 3F 34 A2 FD
The problem is that, I need the sensor readings often prefferably once per second and I need the sensor battery consumption to be as low as possible. This is why I am not inclined to use Eddystone protocol, since I need to active scan for sensor readings.
I used a couple of sensors on Eddystone, and I used to passive scan on the ‘unknown’ GATT caracteristic, which provided the sensor readins however in order to do this I had to permanently maintain an active connection to the sensors, with the keep alive command, and this made the battery drain prematurely for those sensors. They only lasted for less than 4 months.
I am looking forard for some help regarding what to do further.
Thank you