So Ruuvi tags implements RAWv2, https://github.com/ruuvi/ruuvi-sensor-protocols/blob/master/broadcast_formats.md. It is against Ruuvi policy for those making there own homegrown hardware to use the ruuvi mfg id. It would be nice if there was a way to add mfg ids and just have it work, if you tx the data in RAWv2 format,
Example MFG id worth using would be the Adafruit ID since that one is used in CircuitPython (faster way for a homegrown sensor to be created). ADAFRUIT_COMPANY_ID = const(0x0822)
Adafruit reserves a small chunk of there BLE id space for makers using adafruit hardware/circuitpython. "Adafruit manufacturing data is key encoded like advertisement data and the Apple manufacturing data. However, the keys are 16-bits to enable many different uses. Keys above 0xf000 can be used by Adafruit customers for their own data." - https://docs.circuitpython.org/projects/ble/en/latest/advertising.html
So Ruuvi tags implements RAWv2, https://github.com/ruuvi/ruuvi-sensor-protocols/blob/master/broadcast_formats.md. It is against Ruuvi policy for those making there own homegrown hardware to use the ruuvi mfg id. It would be nice if there was a way to add mfg ids and just have it work, if you tx the data in RAWv2 format,
Example MFG id worth using would be the Adafruit ID since that one is used in CircuitPython (faster way for a homegrown sensor to be created). ADAFRUIT_COMPANY_ID = const(0x0822)
Adafruit reserves a small chunk of there BLE id space for makers using adafruit hardware/circuitpython. "Adafruit manufacturing data is key encoded like advertisement data and the Apple manufacturing data. However, the keys are 16-bits to enable many different uses. Keys above 0xf000 can be used by Adafruit customers for their own data." - https://docs.circuitpython.org/projects/ble/en/latest/advertising.html