search

usvi / libruuvitag

The Unlicense
0 stars 0 forks source link

Sniff ruuvitag communication #2

Open usvi opened 1 year ago

usvi commented 1 year ago

We need to sniff ruuvitag communication with a working unit / framework so we can see the hardware address and data format.

usvi commented 1 year ago

Luckily VMWare can pass myb bt chip trough.

Running bluetoothctl scan on

Putting battery in ruuvitag:

[NEW] Device CD:99:36:8E:6E:70 CD-99-36-8E-6E-70

usvi commented 1 year ago

Getting:

[CHG] Device CD:99:36:8E:6E:70 RSSI: -56 [CHG] Device CD:99:36:8E:6E:70 RSSI: -48 [CHG] Device CD:99:36:8E:6E:70 ManufacturerData Key: 0x0499 [CHG] Device CD:99:36:8E:6E:70 ManufacturerData Value: 05 12 6c 2f 26 d1 18 ff 48 02 84 03 18 bd 76 04 ..l/&...H.....v. 00 04 cd 99 36 8e 6e 70 ....6.np

usvi commented 1 year ago

They list protocols here:

https://github.com/ruuvi/ruuvi-sensor-protocols/blob/master/broadcast_formats.md

usvi commented 1 year ago

To me looks like 24 bytes of data here.

usvi commented 1 year ago

Protocol depends on production year. I bought my tags on 2020.

My data: 05 12 6c 2f 26 d1 18 ff 48 02 84 03 18 bd 76 04 00 04 cd 99 36 8e 6e 70 = 24 bytes

Looks like "Data Format 5 Protocol Specification (RAWv2)" https://github.com/ruuvi/ruuvi-sensor-protocols/blob/master/dataformat_05.md

Yes, it is this.