Skip to content

Commit 8e56603

Browse files
committed
Update remaining bad links
1 parent 2cb323f commit 8e56603

File tree

2 files changed

+13
-17
lines changed

2 files changed

+13
-17
lines changed

content/components/esp32_ble_beacon.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Then, just compile and flash the ESP32.
8383

8484
When everything is set up correctly, you should see a show up using your iBeacon scanner of choice. On iPhones,
8585
this should already work from the Bluetooth screen (not tested), on Android, you will need to use an app like
86-
["Beacon Scanner"](https://play.google.com/store/apps/details?id=com.bridou_n.beaconscanner) by Nicolas Bridoux.
86+
["nRF Connect for Mobile"](https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp).
8787

8888
For using these beacons to track the location of your phone, you will need to use another app. For example, I used
8989
[this guide by the owntracks](https://owntracks.org/booklet/features/beacons/) app to let my Home Automation system

content/components/sensor/xiaomi_ble.md

Lines changed: 12 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -585,26 +585,22 @@ For this, you load the [application](https://zaluthar.github.io/TelinkFlasher.ht
585585
the key will not change again until the device is removed and re-added in the Xiaomi app.
586586

587587
- The easiest method to retrieve the bindkey from the cloud is to use the
588+
[Cloud Tokens Extractor](https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor), written by one of Home Assistant users.
589+
If you prefer to not use the executable, read [the Home Assistant Documentation](https://www.home-assistant.io/integrations/xiaomi_miio/#xiaomi-cloud-tokens-extractor).
588590

589-
[Cloud Tokens Extractor](https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor), written by one of Home Assistant users.
590-
If you prefer to not use the executable, read [the Home Assistant Documentation](https://www.home-assistant.io/integrations/xiaomi_miio/#xiaomi-cloud-tokens-extractor).
591+
- Another option is to use a SSL packet sniffer. It can be setup on either an Android phone or the iPhone. Instructions how to obtain the
592+
key using Android can be found in [in this tutorial](https://github.com/ahpohl/xiaomi_lywsd03mmc) on GitHub.
593+
Instructions how to obtain the key using an iPhone can be found in
594+
[custom-components/sensor.mitemp_bt](https://github.com/custom-components/sensor.mitemp_bt/blob/master/faq.md#my-sensors-ble-advertisements-are-encrypted-how-can-i-get-the-key)
595+
on GitHub. Once the traffic between the Mi Home app and the Xiaomi servers has been recorded, the bind key will show in clear text:
591596

592-
- Another option is to use a SSL packet sniffer. It can be setup on either an Android phone or the iPhone. A good choice for Android is the
597+
```text
598+
packet: POST /app/device/bltbind
593599
594-
[Remote PCAP](https://play.google.com/store/apps/details?id=com.egorovandreyrm.pcapremote&hl=en) in combination with
595-
[Wireshark](https://www.wireshark.org/). A tutorial on how to setup the Remote PCAP packet sniffer can be found
596-
[in this tutorial](https://egorovandreyrm.com/pcap-remote-tutorial/) and in [ahpohl/xiaomi_lywsd03mmc](https://github.com/ahpohl/xiaomi_lywsd03mmc) on GitHub.
597-
Instructions how to obtain the key using an iPhone can be found in
598-
[custom-components/sensor.mitemp_bt](https://github.com/custom-components/sensor.mitemp_bt/blob/master/faq.md#my-sensors-ble-advertisements-are-encrypted-how-can-i-get-the-key)
599-
on GitHub. Once the traffic between the Mi Home app and the Xiaomi servers has been recorded, the bind key will show in clear text:
600+
"data" = "{"did":"blt.3.129q4nasgeg00","token":"20c665a7ff82a5bfb5eefc36","props":[{"type":"prop","key":"bind_key","value":"cfc7cc892f4e32f7a733086cf3443cb0"}, {"type":"prop","key":"smac","value":XX:XX:XX:XX:XX:XX}]}"
601+
```
600602

601-
```text
602-
packet: POST /app/device/bltbind
603-
604-
"data" = "{"did":"blt.3.129q4nasgeg00","token":"20c665a7ff82a5bfb5eefc36","props":[{"type":"prop","key":"bind_key","value":"cfc7cc892f4e32f7a733086cf3443cb0"}, {"type":"prop","key":"smac","value":XX:XX:XX:XX:XX:XX}]}"
605-
```
606-
607-
The `bind_key` is the 32 digits "value" item in the above output which needs to be inserted into the config file.
603+
The `bind_key` is the 32 digits "value" item in the above output which needs to be inserted into the config file.
608604

609605
## Improving reception performance
610606

0 commit comments

Comments
 (0)