Closed jareware closed 5 years ago
https://github.com/lautat/ruuvi-sensor-protocol-rs that's in use here only parses ruuvi sensor protocol v3. I've only seen ruuvitags in that mode, but e.g. using Eddystone would result in different protocol.
Having debug output when discarding Bluetooth LE signals would be helpful.
I added verbose output mode to 0.3.7, which should help with debugging here. With ruuvitag-listener -v
I get output like
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Empty value, expected at least one byte
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
ruuvi_measurement,name=F7:2A:60:0D:6E:1E acceleration_x=-0.036,acceleration_y=-0.017,acceleration_z=1.002,battery_potential=3.001,humidity=18.5,pressure=99.498,temperature=20.52 1551812564182733056
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x4C, only 0x0499 is supported
Unknown manufacturer id 0x75, only 0x0499 is supported
ruuvi_measurement,name=F1:FC:AA:80:4E:59 acceleration_x=-0.01,acceleration_y=-0.051,acceleration_z=-1.042,battery_potential=2.983,humidity=16.5,pressure=99.571,temperature=18.85 1551812564457669965
Unknown manufacturer id 0x4C, only 0x0499 is supported
My apartment is cold and has a lot of Apple devices.
Okay, that sounds very plausible, some of my tags are pretty old, and still on stock firmware.
I'll investigate!
Sorry for taking my time to get back to this, our newborn keeping us busy... 😅
I updated all my tags to the latest firmware (1.2.12
) and now they're all showing up beautifully. 🎉
Thanks a lot!
I have 5* RuuviTags, and running my aforementioned Python duct-tape for about a minute I get values from all of them:
But running
ruuvitag-listener
in another terminal over the same time period, I get values from only 2 of them (D8:55...
andF4:62...
):Thoughts..?
*) I was actually about to say I have 4, but apparently I have 1 more somewhere in the apartment that I've forgotten about
¯\_(ツ)_/¯