Hi atc1441,

I have three MI door sensors, and I'm using your universal version.
It got the keys for the first one no problem, but the other two just stall at activation.

Any clues?

s

console log:

Found GATT server
12:17:34.539 Temp_universal_mi_activate.html:309 Services: 0000fe95-0000-1000-8000-00805f9b34fb
12:17:34.539 Temp_universal_mi_activate.html:386 Status: Detected Mi Thermometer
12:17:34.539 Temp_universal_mi_activate.html:386 Found Main service
12:17:34.540 Temp_universal_mi_activate.html:386 Found enc_10 char
12:17:34.540 Temp_universal_mi_activate.html:386 Found enc_19 char
12:17:34.662 Temp_universal_mi_activate.html:386 Status: Connected, you can now Do the Activation to either get the Token or flash a new Firmware
12:17:36.857 Temp_universal_mi_activate.html:386 Send: a2000000
12:17:36.968 Temp_universal_mi_activate.html:386 Enc_19: 000000000100
12:17:36.968 Temp_universal_mi_activate.html:386 Send: 00000101
12:17:37.028 Temp_universal_mi_activate.html:386 Enc_19: 010001000000
12:17:37.028 Temp_universal_mi_activate.html:386 Send: 00000100
12:17:37.029 Temp_universal_mi_activate.html:386 Send: 15000000
12:17:37.032 

Hi ATC1441,
I've been working hard on BLE in Tasmota ESP32, and had an idea about getting the keys for the sensors...
From reading your web source, you can obtain the key without reference to the MI website?....

So. As Tasmota is memory constrained, we could detect if a sensor is not yet Activated (or not activated with a known key), and provide a link to a page (here or in the Tasmota github), and the query string could indicate a Tasmota URL (to the specific local device) to set the key against the MAC.

i.e. the user would see his sensor appear in tasmota with a 'pair' link (only when key is unavailable/not working).
When clicked, this link would take them to a variation of your code, telling it the MAC which you want to Activate, and then once the activation is done, would call back to Tasmota with the required key?

Does this sound possible?

br,
Simon

It would be "nice" if an unsupported browser (thanks for nothing firefox) would give a warning or something, instead of simply "not doing anything" Currently, connect just gives you this on the console

Uncaught TypeError: navigator.bluetooth is undefined
    connect https://atc1441.github.io/TelinkFlasher.html:87
    onclick https://atc1441.github.io/TelinkFlasher.html:1