Discrepancy between test_exec and other "tools"/"code" about protocol-bt-cpp

[mteichtahl]

Any feedback would be greatly appreciated

[Nekonika]

Hello mteichtahl,
I am currently working on a similar approach in C# and figured, that just reading from P_MODE_READ every 10 seconds gets the job done aswell.
As for why the Manufacturer data seems to vary - I have no clue. I just don't get any manufacturer data at all in the advertisements of my "BlueFrog".
To get the key, I just read data from an encoded endpoint and bruteforce the key by decoding the data until the first byte matches the key used.
Hope this helps. ^^

[mteichtahl]

Thanks for the insight. I’ll try your suggestion of using P_MODE_READ. It still remains a mystery why the C++ code get a key of 2A in the first byte but node gets AB. Please note: My working hours may not be your working hours. Please do not feel obligated to reply outside of your normal work schedule!Sent on the go - please excuse mistakes On 23 Feb 2024, at 6:07 am, Nekonika ***@***.***> wrote: Hello mteichtahl, I am currently working on a similar approach in C# and figured, that just reading from P_MODE_READ every 10 seconds gets the job done aswell. As for why the Manufacturer data seems to vary - I have no clue. I just don't get any manufacturer data at all in the advertisements of my "BlueFrog". To get the key, I just read data from an encoded endpoint and bruteforce the key by decoding the data until the first byte matches the key used. Hope this helps. ^^ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[mteichtahl]

To close out. The issue was the underlying firmware on the pi. We had to update the firmware to the latest. Once done the problem was resolved.