Ernst Klamer
Ernst Klamer
This is how we parse it in BLE monitor (assuming that it uses iBeacon format) https://github.com/Ernst79/bleparser/blob/master/package/bleparser/ibeacon.py
Hi Thanks for your suggestion. I will look into it later, as I just moved to a new house and am a little behind with the other issues.
I hope soon, I'm currently working on moving HA BLE to a home assistant integration, where it will be called BThome, as the HA devs have plans to use and...
I don’t think it will be a breaking change for BLE monitor, as the unique_id remains the same and I don’t think HA will change existing entities. But I will...
I need some more info, like BLE advertisements, before I can check if it is possible to add this device. Please check this page on how to collect this information...
Ill have a look soon. Busy with some rebuilding in the house
Sorry, forgot about this issue. First analysis Manufacturer specific data `12ff0503021240b000f4f953657f8a43b9f0f7` `12` = length `ff` = manufacturer specific data `0503`= company id `021240b000f4f95365` = data `7f8a43b9f0f7` = mac (reversed per...
hmm, BLE monitor assumes MiBeacon V3 encrypted for both, with the "short" 24 byte encryption key. It might be that Xiaomi/Yeelight has done a firmware update on the YLKG08YL, so...
You might get the key with xiaomi cloud token extractor, if it is added in MiHome. It gets the key from the cloud and works in windows
You’re probably right, but perhaps they have changed MiHome support too with the new firmware. Worth to try