🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 77 (from laksa003)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa077.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://www.home-assistant.io/integrations/xiaomi_ble/\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.home-assistant.io/integrations/xiaomi_ble/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/","crawl_time":1775511452,"first_indexed_time":1659552942,"http_code":200,"src_unparsed":"io,home-assistant!www,\/integrations\/xiaomi_ble\/ s443","src_root_hash":"6959518072785130877","history_drop_reason":null,"meta_title":"Xiaomi BLE - Home Assistant","meta_descriptions":["Instructions on how to integrate Xiaomi BLE devices into Home Assistant."],"attrs_boilerpipe_text":"Integrates devices that use the Xiaomi Mijia BLE MiBeacon protocol and the BLE protocols implemented in the MiScales and the MiFora plant sensor. This integration does not support Xiaomi BLE Mesh devices. The integration listens to Bluetooth broadcasts that the device makes by itself, allowing it to track the latest sensor values or events without waking the device up for polling (except HHCCJCY01, see note below). This method conserves battery lifetime.\nThe integration automatically discovers devices once the\nBluetooth\nintegration is enabled and functional. The entities are added after the values are first received. This means that entities might show up later if the corresponding values are broadcasted at a lower interval (for example, battery).\nConfiguration\nTo add the\nXiaomi BLE\ndevice to your Home Assistant instance, use this My button:\nManual configuration steps\nIf the above My button doesn’t work, you can also perform the following steps\nmanually:\nBrowse to your Home Assistant instance.\nGo to\nSettings > Devices & services\n.\nIn the bottom right corner, select the\nAdd Integration\nbutton.\nFrom the list, select\nXiaomi BLE\n.\nFollow the instructions on screen to complete the setup.\nEncryption\nSome devices use AES encryption to protect the sensor values they are broadcasting.\nMiBeacon v2\/v3 use unauthenticated AES with a 24 character hexadecimal (12 byte) key\nMiBeacon v4\/v5 use authenticated AES with a 32 character hexadecimal (16 byte) key\nThis key is called the bindkey or beaconkey.\nThere are a few ways to obtain a bindkey for your device:\nFor v4 and v5 devices, you can provide your Xiaomi Cloud account login credentials for the account to which the device is bound. Home Assistant will import the appropriate bind key from your account.\nExtract the keys from Xiaomi Cloud using a\ntoken extractor\ntool.\nSet your own. The\nTelink Flasher\nby pvvx allows you to generate new bindkeys for devices it supports (LYWSD03MMC, MJWSD05MMC, MHO-C401, CGG1, and CGDK2). This online flashing tool also allows you to upload alternative firmware, with some improvements compared to the stock firmware, like faster sensor updates. Note that the new bind key works with Home Assistant, but the Mi Home app does not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app.\nAn alternative\nTelink Flasher\nby atc1441 also allows you to generate new bind keys, and supports even more Xiaomi devices compared to the Telink Flasher by pvvx.\nYeelight Remote (YLYK01YL) and dimmers (YLKG07YL and YLKG08YL) can use V2\/V3 MiBeacon encryption, although more recent devices seem to be supplied with V4\/V5 encryption. For V2\/V3 MiBeacon encryption, the bindkey can’t be determined with the above methods. Instructions on how to get the bindkey for these devices can be found in the\nBLE monitor FAQ\n.\nDevices\nPlant sensor: Flower Care \/ MiFlora (HHCCJCY01)\nHHCCJCY01, also known as MiFlora or “Flower Care”, should be automatically discovered. However, if the firmware is too old, it won’t send the right BLE beacons and an update via the app is required. The lowest confirmed working firmware version is 3.2.1 (a lower 3.x version could also be alright).\nFlower Care firmware update steps:\nInstall the official “Flower Care” app by HHCC:\nGoogle Play\n(requires location and storage permission)\nApple App Store\nPlace the device with the app within 10cm of the plant sensor\nPress the “+” button on the top right in the devices tab of the app\nAdd the plant sensor to the app and select an arbitrary plant\nWait for the synchronization of the sensor to finish, and a dialog asking for a firmware update should appear (this might take a few minutes)\nThe installed and latest firmware version can be verified by selecting the plant -> three dots menu -> Hardware settings -> Hardware update\nThe Flower Care account and app are not required any further for this integration to work\nAlso note that the battery level of the plant sensor can only be retrieved by connecting to the device (reading characteristics), while the other sensor data is broadcasted passively. To prevent battery drainage, a connection is made only once a day. Connecting to the device also requires that the device has a good signal strength.\nHelp us improve our documentation\nSuggest an edit to this page, or provide\/view feedback for this page.\nEdit\nProvide feedback\nView pending feedback","attrs_markdown":"[2026\\.4.1](https:\/\/www.home-assistant.io\/blog\/2026\/04\/01\/release-20264\/ \"Latest version 2026.4.1 released April  3, 2026\")\n\n- [Getting started](https:\/\/www.home-assistant.io\/installation\/)\n- [Documentation](https:\/\/www.home-assistant.io\/docs\/)\n  - [Installation](https:\/\/www.home-assistant.io\/installation\/)\n  - [Automations](https:\/\/www.home-assistant.io\/docs\/automation\/)\n  - [Dashboards](https:\/\/www.home-assistant.io\/dashboards\/)\n  - [Voice assistants](https:\/\/www.home-assistant.io\/voice_control\/)\n  - [Device organization](https:\/\/www.home-assistant.io\/docs\/organizing\/)\n  - [Energy management](https:\/\/www.home-assistant.io\/docs\/energy\/)\n  - [Templating](https:\/\/www.home-assistant.io\/docs\/templating\/)\n  - [Advanced configuration](https:\/\/www.home-assistant.io\/docs\/configuration\/)\n- [Our hardware](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/)\n  - [Home Assistant Green](https:\/\/www.home-assistant.io\/green\/)\n  - [Connect ZBT-2](https:\/\/www.home-assistant.io\/connect\/zbt-2\/)\n  - [Connect ZWA-2](https:\/\/www.home-assistant.io\/connect\/zwa-2\/)\n  - [Voice Preview Edition](https:\/\/www.home-assistant.io\/voice-pe\/)\n- [Integrations](https:\/\/www.home-assistant.io\/integrations\/)\n- [Blog](https:\/\/www.home-assistant.io\/blog\/)\n- [Need help?](https:\/\/www.home-assistant.io\/help\/)\n\nOn this page\n\n- [Configuration](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/#configuration)\n- [Encryption](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/#encryption)\n- [Devices](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/#devices)\n  - [Plant sensor: Flower Care \/ MiFlora (HHCCJCY01)](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/#plant-sensor-flower-care--miflora-hhccjcy01)\n\n[Home](https:\/\/www.home-assistant.io\/) ▸ [Integrations](https:\/\/www.home-assistant.io\/integrations\/)\n\n# Xiaomi BLE\n\nIntegrates devices that use the Xiaomi Mijia BLE MiBeacon protocol and the BLE protocols implemented in the MiScales and the MiFora plant sensor. This integration does not support Xiaomi BLE Mesh devices. The integration listens to Bluetooth broadcasts that the device makes by itself, allowing it to track the latest sensor values or events without waking the device up for polling (except HHCCJCY01, see note below). This method conserves battery lifetime.\n\nThe integration automatically discovers devices once the [Bluetooth](https:\/\/www.home-assistant.io\/integrations\/bluetooth) integration is enabled and functional. The entities are added after the values are first received. This means that entities might show up later if the corresponding values are broadcasted at a lower interval (for example, battery).\n\n## Configuration\nTo add the **Xiaomi BLE** device to your Home Assistant instance, use this My button:\n\n[![](https:\/\/my.home-assistant.io\/badges\/config_flow_start.svg)](https:\/\/my.home-assistant.io\/redirect\/config_flow_start?domain=xiaomi_ble)\n\nManual configuration steps\n\nIf the above My button doesn’t work, you can also perform the following steps manually:\n\n- Browse to your Home Assistant instance.\n- Go to **[Settings \\> Devices & services](https:\/\/my.home-assistant.io\/redirect\/integrations)**.\n- In the bottom right corner, select the **[Add Integration](https:\/\/my.home-assistant.io\/redirect\/config_flow_start?domain=xiaomi_ble)** button.\n- From the list, select **Xiaomi BLE**.\n- Follow the instructions on screen to complete the setup.\n## Encryption\nSome devices use AES encryption to protect the sensor values they are broadcasting.\n\n- MiBeacon v2\/v3 use unauthenticated AES with a 24 character hexadecimal (12 byte) key\n- MiBeacon v4\/v5 use authenticated AES with a 32 character hexadecimal (16 byte) key\n\nThis key is called the bindkey or beaconkey.\n\nThere are a few ways to obtain a bindkey for your device:\n\n- For v4 and v5 devices, you can provide your Xiaomi Cloud account login credentials for the account to which the device is bound. Home Assistant will import the appropriate bind key from your account.\n- Extract the keys from Xiaomi Cloud using a [token extractor](https:\/\/github.com\/PiotrMachowski\/Xiaomi-cloud-tokens-extractor) tool.\n- Set your own. The [Telink Flasher](https:\/\/pvvx.github.io\/ATC_MiThermometer\/TelinkMiFlasher.html) by pvvx allows you to generate new bindkeys for devices it supports (LYWSD03MMC, MJWSD05MMC, MHO-C401, CGG1, and CGDK2). This online flashing tool also allows you to upload alternative firmware, with some improvements compared to the stock firmware, like faster sensor updates. Note that the new bind key works with Home Assistant, but the Mi Home app does not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app.\n- An alternative [Telink Flasher](https:\/\/atc1441.github.io\/Temp_universal_mi_activate.html) by atc1441 also allows you to generate new bind keys, and supports even more Xiaomi devices compared to the Telink Flasher by pvvx.\n- Yeelight Remote (YLYK01YL) and dimmers (YLKG07YL and YLKG08YL) can use V2\/V3 MiBeacon encryption, although more recent devices seem to be supplied with V4\/V5 encryption. For V2\/V3 MiBeacon encryption, the bindkey can’t be determined with the above methods. Instructions on how to get the bindkey for these devices can be found in the [BLE monitor FAQ](https:\/\/custom-components.github.io\/ble_monitor\/faq#how-to-get-the-mibeacon-v2v3-encryption-key).\n## Devices\n### Plant sensor: Flower Care \/ MiFlora (HHCCJCY01)\nHHCCJCY01, also known as MiFlora or “Flower Care”, should be automatically discovered. However, if the firmware is too old, it won’t send the right BLE beacons and an update via the app is required. The lowest confirmed working firmware version is 3.2.1 (a lower 3.x version could also be alright).\n\nFlower Care firmware update steps:\n\n- Install the official “Flower Care” app by HHCC:\n  - [Google Play](https:\/\/play.google.com\/store\/apps\/details?id=com.huahuacaocao.flowercare) (requires location and storage permission)\n  - [Apple App Store](https:\/\/apps.apple.com\/app\/id1095274672)\n- Place the device with the app within 10cm of the plant sensor\n- Press the “+” button on the top right in the devices tab of the app\n- Add the plant sensor to the app and select an arbitrary plant\n- Wait for the synchronization of the sensor to finish, and a dialog asking for a firmware update should appear (this might take a few minutes)\n- The installed and latest firmware version can be verified by selecting the plant -\\> three dots menu -\\> Hardware settings -\\> Hardware update\n- The Flower Care account and app are not required any further for this integration to work\n\nAlso note that the battery level of the plant sensor can only be retrieved by connecting to the device (reading characteristics), while the other sensor data is broadcasted passively. To prevent battery drainage, a connection is made only once a day. Connecting to the device also requires that the device has a good signal strength.\n\n#### **Help us improve our documentation**\nSuggest an edit to this page, or provide\/view feedback for this page.\n\n- [Edit](https:\/\/github.com\/home-assistant\/home-assistant.io\/tree\/current\/source\/_integrations\/xiaomi_ble.markdown \"Edit this page\")\n- [Provide feedback](https:\/\/github.com\/home-assistant\/home-assistant.io\/issues\/new?template=feedback.yml&url=https%3A%2F%2Fwww.home-assistant.io%2Fintegrations%2Fxiaomi_ble%2F&version=2026.4.1&labels=current,integration%3A%20xiaomi_ble \"Provide feedback on this page\")\n- [View pending feedback](https:\/\/github.com\/home-assistant\/home-assistant.io\/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22integration%3A+xiaomi_ble%22 \"View pending feedback for this page\")\n\n![](https:\/\/brands.home-assistant.io\/_\/xiaomi_ble\/\/logo.png)[![](https:\/\/my.home-assistant.io\/badges\/config_flow_start.svg)](https:\/\/my.home-assistant.io\/redirect\/config_flow_start?domain=xiaomi_ble)\n\nThe Xiaomi BLE device was introduced in Home Assistant 2022.8, and it's used by  [5\\.4%](https:\/\/analytics.home-assistant.io\/integrations \"Open analytics.home-assistant.io\") of the active installations.\n\nIts IoT class is [Local Push.](https:\/\/www.home-assistant.io\/blog\/2016\/02\/12\/classifying-the-internet-of-things\/#classifiers)\n\n[View source on GitHub](https:\/\/github.com\/home-assistant\/core\/tree\/dev\/homeassistant\/components\/xiaomi_ble)\n\n[View known issues](https:\/\/github.com\/home-assistant\/core\/issues?q=is%3Aissue+label%3A%22integration%3A+xiaomi_ble%22)\n\n[View feature requests](https:\/\/github.com\/orgs\/home-assistant\/discussions?discussions_q=label%3A%22integration%3A+xiaomi_ble%22)\n\n## Integration owners\nWe are incredibly grateful to the following contributors who currently maintain this integration:\n\n[![@Jc2k](https:\/\/avatars.githubusercontent.com\/Jc2k?size=96) @Jc2k](https:\/\/github.com\/Jc2k)  \n[![@Ernst79](https:\/\/avatars.githubusercontent.com\/Ernst79?size=96) @Ernst79](https:\/\/github.com\/Ernst79)\n\n## Categories\n- [Binary sensor](https:\/\/www.home-assistant.io\/integrations\/#binary-sensor)\n- [Event](https:\/\/www.home-assistant.io\/integrations\/#event)\n- [Sensor](https:\/\/www.home-assistant.io\/integrations\/#sensor)\n\n## On this page\n- [Configuration](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/#configuration)\n- [Encryption](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/#encryption)\n- [Devices](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/#devices)\n  - [Plant sensor: Flower Care \/ MiFlora (HHCCJCY01)](https:\/\/www.home-assistant.io\/integrations\/xiaomi_ble\/#plant-sensor-flower-care--miflora-hhccjcy01)\n\nBack to top\n\n![Home Assistant](https:\/\/www.home-assistant.io\/images\/footer-logo-text.svg)\n\nHome Assistant is a project from the [Open Home Foundation](https:\/\/www.openhomefoundation.org\/), sponsored by [Nabu Casa](https:\/\/www.nabucasa.com\/).\n\n### Join us and contribute\\!\n- [GitHub repo](https:\/\/github.com\/home-assistant\/)\n- [Developers Portal](https:\/\/developers.home-assistant.io\/)\n- [Design Portal](https:\/\/design.home-assistant.io\/)\n- [Data Science Portal](https:\/\/data.home-assistant.io\/)\n- [Community Forum](https:\/\/community.home-assistant.io\/)\n- [Creator Network](https:\/\/creators.home-assistant.io\/)\n- [Works With Home Assistant](https:\/\/works-with.home-assistant.io\/)\n- [Our community](https:\/\/www.home-assistant.io\/community)\n- [Reporting issues](https:\/\/www.home-assistant.io\/help\/reporting_issues\/)\n### System status\n- [Integration Alerts](https:\/\/alerts.home-assistant.io\/)\n- [Security Alerts](https:\/\/www.home-assistant.io\/security\/)\n- [System Status](https:\/\/status.home-assistant.io\/)\n\n### Companion apps\n- [iOS and Apple devices](https:\/\/apps.apple.com\/app\/id1099568401)\n- [Android and Wear OS](https:\/\/play.google.com\/store\/apps\/details?id=io.homeassistant.companion.android)\n- [...and more\\!](https:\/\/companion.home-assistant.io\/)\n### Support us\n- [Merch store](https:\/\/store.openhomefoundation.org\/)\n- [Home Assistant Cloud](https:\/\/www.home-assistant.io\/cloud\/)\n### Governance\n- [Privacy Notices](https:\/\/www.home-assistant.io\/privacy\/)\n- [Contributor License Agreement](https:\/\/www.home-assistant.io\/developers\/cla\/)\n- [Terms of Service](https:\/\/www.home-assistant.io\/tos\/)\n- [Code of Conduct](https:\/\/www.home-assistant.io\/code_of_conduct\/)\n- [Credits](https:\/\/www.home-assistant.io\/developers\/credits\/)\n- [License](https:\/\/www.home-assistant.io\/developers\/license\/)\n\n### Follow us\n[Sign up for our newsletter](https:\/\/newsletter.openhomefoundation.org\/#\/portal)\n\nFor partnership inquiries please check out [Works With Home Assistant](https:\/\/works-with.home-assistant.io\/). For media, [email our team](https:\/\/www.home-assistant.io\/cdn-cgi\/l\/email-protection#93fef6f7faf2d3fce3f6fdfbfcfef6f5fce6fdf7f2e7fafcfdbdfce1f4). For other questions, you can [contact support](https:\/\/www.home-assistant.io\/cdn-cgi\/l\/email-protection#afc7cac3c3c0efc7c0c2ca82cedcdcc6dcdbcec1db81c6c0) (No technical support!)\n\nWebsite powered by [Jekyll](https:\/\/jekyllrb.com\/)  \n Originally based on the [Oscailte theme](https:\/\/github.com\/coogie\/oscailte)\n\n[![Deploys by Netlify Badge](https:\/\/www.home-assistant.io\/images\/frontpage\/netlify.svg)](https:\/\/www.netlify.com\/)","attrs_readable_markdown":"Integrates devices that use the Xiaomi Mijia BLE MiBeacon protocol and the BLE protocols implemented in the MiScales and the MiFora plant sensor. This integration does not support Xiaomi BLE Mesh devices. The integration listens to Bluetooth broadcasts that the device makes by itself, allowing it to track the latest sensor values or events without waking the device up for polling (except HHCCJCY01, see note below). This method conserves battery lifetime.\n\nThe integration automatically discovers devices once the [Bluetooth](https:\/\/www.home-assistant.io\/integrations\/bluetooth) integration is enabled and functional. The entities are added after the values are first received. This means that entities might show up later if the corresponding values are broadcasted at a lower interval (for example, battery).\n\n## Configuration\nTo add the **Xiaomi BLE** device to your Home Assistant instance, use this My button:\n\n[![](https:\/\/my.home-assistant.io\/badges\/config_flow_start.svg)](https:\/\/my.home-assistant.io\/redirect\/config_flow_start?domain=xiaomi_ble)\n\nManual configuration steps\n\nIf the above My button doesn’t work, you can also perform the following steps manually:\n\n- Browse to your Home Assistant instance.\n- Go to **[Settings \\> Devices & services](https:\/\/my.home-assistant.io\/redirect\/integrations)**.\n- In the bottom right corner, select the **[Add Integration](https:\/\/my.home-assistant.io\/redirect\/config_flow_start?domain=xiaomi_ble)** button.\n- From the list, select **Xiaomi BLE**.\n- Follow the instructions on screen to complete the setup.\n## Encryption\nSome devices use AES encryption to protect the sensor values they are broadcasting.\n\n- MiBeacon v2\/v3 use unauthenticated AES with a 24 character hexadecimal (12 byte) key\n- MiBeacon v4\/v5 use authenticated AES with a 32 character hexadecimal (16 byte) key\n\nThis key is called the bindkey or beaconkey.\n\nThere are a few ways to obtain a bindkey for your device:\n\n- For v4 and v5 devices, you can provide your Xiaomi Cloud account login credentials for the account to which the device is bound. Home Assistant will import the appropriate bind key from your account.\n- Extract the keys from Xiaomi Cloud using a [token extractor](https:\/\/github.com\/PiotrMachowski\/Xiaomi-cloud-tokens-extractor) tool.\n- Set your own. The [Telink Flasher](https:\/\/pvvx.github.io\/ATC_MiThermometer\/TelinkMiFlasher.html) by pvvx allows you to generate new bindkeys for devices it supports (LYWSD03MMC, MJWSD05MMC, MHO-C401, CGG1, and CGDK2). This online flashing tool also allows you to upload alternative firmware, with some improvements compared to the stock firmware, like faster sensor updates. Note that the new bind key works with Home Assistant, but the Mi Home app does not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app.\n- An alternative [Telink Flasher](https:\/\/atc1441.github.io\/Temp_universal_mi_activate.html) by atc1441 also allows you to generate new bind keys, and supports even more Xiaomi devices compared to the Telink Flasher by pvvx.\n- Yeelight Remote (YLYK01YL) and dimmers (YLKG07YL and YLKG08YL) can use V2\/V3 MiBeacon encryption, although more recent devices seem to be supplied with V4\/V5 encryption. For V2\/V3 MiBeacon encryption, the bindkey can’t be determined with the above methods. Instructions on how to get the bindkey for these devices can be found in the [BLE monitor FAQ](https:\/\/custom-components.github.io\/ble_monitor\/faq#how-to-get-the-mibeacon-v2v3-encryption-key).\n## Devices\n### Plant sensor: Flower Care \/ MiFlora (HHCCJCY01)\nHHCCJCY01, also known as MiFlora or “Flower Care”, should be automatically discovered. However, if the firmware is too old, it won’t send the right BLE beacons and an update via the app is required. The lowest confirmed working firmware version is 3.2.1 (a lower 3.x version could also be alright).\n\nFlower Care firmware update steps:\n\n- Install the official “Flower Care” app by HHCC:\n  - [Google Play](https:\/\/play.google.com\/store\/apps\/details?id=com.huahuacaocao.flowercare) (requires location and storage permission)\n  - [Apple App Store](https:\/\/apps.apple.com\/app\/id1095274672)\n- Place the device with the app within 10cm of the plant sensor\n- Press the “+” button on the top right in the devices tab of the app\n- Add the plant sensor to the app and select an arbitrary plant\n- Wait for the synchronization of the sensor to finish, and a dialog asking for a firmware update should appear (this might take a few minutes)\n- The installed and latest firmware version can be verified by selecting the plant -\\> three dots menu -\\> Hardware settings -\\> Hardware update\n- The Flower Care account and app are not required any further for this integration to work\n\nAlso note that the battery level of the plant sensor can only be retrieved by connecting to the device (reading characteristics), while the other sensor data is broadcasted passively. To prevent battery drainage, a connection is made only once a day. Connecting to the device also requires that the device has a good signal strength.\n\n#### **Help us improve our documentation**\nSuggest an edit to this page, or provide\/view feedback for this page.\n\n- [Edit](https:\/\/github.com\/home-assistant\/home-assistant.io\/tree\/current\/source\/_integrations\/xiaomi_ble.markdown \"Edit this page\")\n- [Provide feedback](https:\/\/github.com\/home-assistant\/home-assistant.io\/issues\/new?template=feedback.yml&url=https%3A%2F%2Fwww.home-assistant.io%2Fintegrations%2Fxiaomi_ble%2F&version=2026.4.1&labels=current,integration%3A%20xiaomi_ble \"Provide feedback on this page\")\n- [View pending feedback](https:\/\/github.com\/home-assistant\/home-assistant.io\/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22integration%3A+xiaomi_ble%22 \"View pending feedback for this page\")","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

11 hours ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://www.home-assistant.io/integrations/xiaomi_ble/
Last Crawled	2026-04-06 21:37:32 (11 hours ago)
First Indexed	2022-08-03 18:55:42 (3 years ago)
HTTP Status Code	200
Meta Title	Xiaomi BLE - Home Assistant
Meta Description	Instructions on how to integrate Xiaomi BLE devices into Home Assistant.
Meta Canonical	null
Boilerpipe Text	Integrates devices that use the Xiaomi Mijia BLE MiBeacon protocol and the BLE protocols implemented in the MiScales and the MiFora plant sensor. This integration does not support Xiaomi BLE Mesh devices. The integration listens to Bluetooth broadcasts that the device makes by itself, allowing it to track the latest sensor values or events without waking the device up for polling (except HHCCJCY01, see note below). This method conserves battery lifetime. The integration automatically discovers devices once the Bluetooth integration is enabled and functional. The entities are added after the values are first received. This means that entities might show up later if the corresponding values are broadcasted at a lower interval (for example, battery). Configuration To add the Xiaomi BLE device to your Home Assistant instance, use this My button: Manual configuration steps If the above My button doesn’t work, you can also perform the following steps manually: Browse to your Home Assistant instance. Go to Settings > Devices & services . In the bottom right corner, select the Add Integration button. From the list, select Xiaomi BLE . Follow the instructions on screen to complete the setup. Encryption Some devices use AES encryption to protect the sensor values they are broadcasting. MiBeacon v2/v3 use unauthenticated AES with a 24 character hexadecimal (12 byte) key MiBeacon v4/v5 use authenticated AES with a 32 character hexadecimal (16 byte) key This key is called the bindkey or beaconkey. There are a few ways to obtain a bindkey for your device: For v4 and v5 devices, you can provide your Xiaomi Cloud account login credentials for the account to which the device is bound. Home Assistant will import the appropriate bind key from your account. Extract the keys from Xiaomi Cloud using a token extractor tool. Set your own. The Telink Flasher by pvvx allows you to generate new bindkeys for devices it supports (LYWSD03MMC, MJWSD05MMC, MHO-C401, CGG1, and CGDK2). This online flashing tool also allows you to upload alternative firmware, with some improvements compared to the stock firmware, like faster sensor updates. Note that the new bind key works with Home Assistant, but the Mi Home app does not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app. An alternative Telink Flasher by atc1441 also allows you to generate new bind keys, and supports even more Xiaomi devices compared to the Telink Flasher by pvvx. Yeelight Remote (YLYK01YL) and dimmers (YLKG07YL and YLKG08YL) can use V2/V3 MiBeacon encryption, although more recent devices seem to be supplied with V4/V5 encryption. For V2/V3 MiBeacon encryption, the bindkey can’t be determined with the above methods. Instructions on how to get the bindkey for these devices can be found in the BLE monitor FAQ . Devices Plant sensor: Flower Care / MiFlora (HHCCJCY01) HHCCJCY01, also known as MiFlora or “Flower Care”, should be automatically discovered. However, if the firmware is too old, it won’t send the right BLE beacons and an update via the app is required. The lowest confirmed working firmware version is 3.2.1 (a lower 3.x version could also be alright). Flower Care firmware update steps: Install the official “Flower Care” app by HHCC: Google Play (requires location and storage permission) Apple App Store Place the device with the app within 10cm of the plant sensor Press the “+” button on the top right in the devices tab of the app Add the plant sensor to the app and select an arbitrary plant Wait for the synchronization of the sensor to finish, and a dialog asking for a firmware update should appear (this might take a few minutes) The installed and latest firmware version can be verified by selecting the plant -> three dots menu -> Hardware settings -> Hardware update The Flower Care account and app are not required any further for this integration to work Also note that the battery level of the plant sensor can only be retrieved by connecting to the device (reading characteristics), while the other sensor data is broadcasted passively. To prevent battery drainage, a connection is made only once a day. Connecting to the device also requires that the device has a good signal strength. Help us improve our documentation Suggest an edit to this page, or provide/view feedback for this page. Edit Provide feedback View pending feedback
Markdown	[2026\.4.1](https://www.home-assistant.io/blog/2026/04/01/release-20264/ "Latest version 2026.4.1 released April 3, 2026") - [Getting started](https://www.home-assistant.io/installation/) - [Documentation](https://www.home-assistant.io/docs/) - [Installation](https://www.home-assistant.io/installation/) - [Automations](https://www.home-assistant.io/docs/automation/) - [Dashboards](https://www.home-assistant.io/dashboards/) - [Voice assistants](https://www.home-assistant.io/voice_control/) - [Device organization](https://www.home-assistant.io/docs/organizing/) - [Energy management](https://www.home-assistant.io/docs/energy/) - [Templating](https://www.home-assistant.io/docs/templating/) - [Advanced configuration](https://www.home-assistant.io/docs/configuration/) - [Our hardware](https://www.home-assistant.io/integrations/xiaomi_ble/) - [Home Assistant Green](https://www.home-assistant.io/green/) - [Connect ZBT-2](https://www.home-assistant.io/connect/zbt-2/) - [Connect ZWA-2](https://www.home-assistant.io/connect/zwa-2/) - [Voice Preview Edition](https://www.home-assistant.io/voice-pe/) - [Integrations](https://www.home-assistant.io/integrations/) - [Blog](https://www.home-assistant.io/blog/) - [Need help?](https://www.home-assistant.io/help/) On this page - [Configuration](https://www.home-assistant.io/integrations/xiaomi_ble/#configuration) - [Encryption](https://www.home-assistant.io/integrations/xiaomi_ble/#encryption) - [Devices](https://www.home-assistant.io/integrations/xiaomi_ble/#devices) - [Plant sensor: Flower Care / MiFlora (HHCCJCY01)](https://www.home-assistant.io/integrations/xiaomi_ble/#plant-sensor-flower-care--miflora-hhccjcy01) [Home](https://www.home-assistant.io/) ▸ [Integrations](https://www.home-assistant.io/integrations/) # Xiaomi BLE Integrates devices that use the Xiaomi Mijia BLE MiBeacon protocol and the BLE protocols implemented in the MiScales and the MiFora plant sensor. This integration does not support Xiaomi BLE Mesh devices. The integration listens to Bluetooth broadcasts that the device makes by itself, allowing it to track the latest sensor values or events without waking the device up for polling (except HHCCJCY01, see note below). This method conserves battery lifetime. The integration automatically discovers devices once the [Bluetooth](https://www.home-assistant.io/integrations/bluetooth) integration is enabled and functional. The entities are added after the values are first received. This means that entities might show up later if the corresponding values are broadcasted at a lower interval (for example, battery). ## Configuration To add the Xiaomi BLE device to your Home Assistant instance, use this My button: [![](https://my.home-assistant.io/badges/config_flow_start.svg)](https://my.home-assistant.io/redirect/config_flow_start?domain=xiaomi_ble) Manual configuration steps If the above My button doesn’t work, you can also perform the following steps manually: - Browse to your Home Assistant instance. - Go to [Settings \> Devices & services](https://my.home-assistant.io/redirect/integrations). - In the bottom right corner, select the [Add Integration](https://my.home-assistant.io/redirect/config_flow_start?domain=xiaomi_ble) button. - From the list, select Xiaomi BLE. - Follow the instructions on screen to complete the setup. ## Encryption Some devices use AES encryption to protect the sensor values they are broadcasting. - MiBeacon v2/v3 use unauthenticated AES with a 24 character hexadecimal (12 byte) key - MiBeacon v4/v5 use authenticated AES with a 32 character hexadecimal (16 byte) key This key is called the bindkey or beaconkey. There are a few ways to obtain a bindkey for your device: - For v4 and v5 devices, you can provide your Xiaomi Cloud account login credentials for the account to which the device is bound. Home Assistant will import the appropriate bind key from your account. - Extract the keys from Xiaomi Cloud using a [token extractor](https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor) tool. - Set your own. The [Telink Flasher](https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html) by pvvx allows you to generate new bindkeys for devices it supports (LYWSD03MMC, MJWSD05MMC, MHO-C401, CGG1, and CGDK2). This online flashing tool also allows you to upload alternative firmware, with some improvements compared to the stock firmware, like faster sensor updates. Note that the new bind key works with Home Assistant, but the Mi Home app does not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app. - An alternative [Telink Flasher](https://atc1441.github.io/Temp_universal_mi_activate.html) by atc1441 also allows you to generate new bind keys, and supports even more Xiaomi devices compared to the Telink Flasher by pvvx. - Yeelight Remote (YLYK01YL) and dimmers (YLKG07YL and YLKG08YL) can use V2/V3 MiBeacon encryption, although more recent devices seem to be supplied with V4/V5 encryption. For V2/V3 MiBeacon encryption, the bindkey can’t be determined with the above methods. Instructions on how to get the bindkey for these devices can be found in the [BLE monitor FAQ](https://custom-components.github.io/ble_monitor/faq#how-to-get-the-mibeacon-v2v3-encryption-key). ## Devices ### Plant sensor: Flower Care / MiFlora (HHCCJCY01) HHCCJCY01, also known as MiFlora or “Flower Care”, should be automatically discovered. However, if the firmware is too old, it won’t send the right BLE beacons and an update via the app is required. The lowest confirmed working firmware version is 3.2.1 (a lower 3.x version could also be alright). Flower Care firmware update steps: - Install the official “Flower Care” app by HHCC: - [Google Play](https://play.google.com/store/apps/details?id=com.huahuacaocao.flowercare) (requires location and storage permission) - [Apple App Store](https://apps.apple.com/app/id1095274672) - Place the device with the app within 10cm of the plant sensor - Press the “+” button on the top right in the devices tab of the app - Add the plant sensor to the app and select an arbitrary plant - Wait for the synchronization of the sensor to finish, and a dialog asking for a firmware update should appear (this might take a few minutes) - The installed and latest firmware version can be verified by selecting the plant -\> three dots menu -\> Hardware settings -\> Hardware update - The Flower Care account and app are not required any further for this integration to work Also note that the battery level of the plant sensor can only be retrieved by connecting to the device (reading characteristics), while the other sensor data is broadcasted passively. To prevent battery drainage, a connection is made only once a day. Connecting to the device also requires that the device has a good signal strength. #### Help us improve our documentation Suggest an edit to this page, or provide/view feedback for this page. - [Edit](https://github.com/home-assistant/home-assistant.io/tree/current/source/_integrations/xiaomi_ble.markdown "Edit this page") - [Provide feedback](https://github.com/home-assistant/home-assistant.io/issues/new?template=feedback.yml&url=https%3A%2F%2Fwww.home-assistant.io%2Fintegrations%2Fxiaomi_ble%2F&version=2026.4.1&labels=current,integration%3A%20xiaomi_ble "Provide feedback on this page") - [View pending feedback](https://github.com/home-assistant/home-assistant.io/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22integration%3A+xiaomi_ble%22 "View pending feedback for this page") ![](https://brands.home-assistant.io/_/xiaomi_ble//logo.png)[![](https://my.home-assistant.io/badges/config_flow_start.svg)](https://my.home-assistant.io/redirect/config_flow_start?domain=xiaomi_ble) The Xiaomi BLE device was introduced in Home Assistant 2022.8, and it's used by [5\.4%](https://analytics.home-assistant.io/integrations "Open analytics.home-assistant.io") of the active installations. Its IoT class is [Local Push.](https://www.home-assistant.io/blog/2016/02/12/classifying-the-internet-of-things/#classifiers) [View source on GitHub](https://github.com/home-assistant/core/tree/dev/homeassistant/components/xiaomi_ble) [View known issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+label%3A%22integration%3A+xiaomi_ble%22) [View feature requests](https://github.com/orgs/home-assistant/discussions?discussions_q=label%3A%22integration%3A+xiaomi_ble%22) ## Integration owners We are incredibly grateful to the following contributors who currently maintain this integration: [![@Jc2k](https://avatars.githubusercontent.com/Jc2k?size=96) @Jc2k](https://github.com/Jc2k) [![@Ernst79](https://avatars.githubusercontent.com/Ernst79?size=96) @Ernst79](https://github.com/Ernst79) ## Categories - [Binary sensor](https://www.home-assistant.io/integrations/#binary-sensor) - [Event](https://www.home-assistant.io/integrations/#event) - [Sensor](https://www.home-assistant.io/integrations/#sensor) ## On this page - [Configuration](https://www.home-assistant.io/integrations/xiaomi_ble/#configuration) - [Encryption](https://www.home-assistant.io/integrations/xiaomi_ble/#encryption) - [Devices](https://www.home-assistant.io/integrations/xiaomi_ble/#devices) - [Plant sensor: Flower Care / MiFlora (HHCCJCY01)](https://www.home-assistant.io/integrations/xiaomi_ble/#plant-sensor-flower-care--miflora-hhccjcy01) Back to top ![Home Assistant](https://www.home-assistant.io/images/footer-logo-text.svg) Home Assistant is a project from the [Open Home Foundation](https://www.openhomefoundation.org/), sponsored by [Nabu Casa](https://www.nabucasa.com/). ### Join us and contribute\! - [GitHub repo](https://github.com/home-assistant/) - [Developers Portal](https://developers.home-assistant.io/) - [Design Portal](https://design.home-assistant.io/) - [Data Science Portal](https://data.home-assistant.io/) - [Community Forum](https://community.home-assistant.io/) - [Creator Network](https://creators.home-assistant.io/) - [Works With Home Assistant](https://works-with.home-assistant.io/) - [Our community](https://www.home-assistant.io/community) - [Reporting issues](https://www.home-assistant.io/help/reporting_issues/) ### System status - [Integration Alerts](https://alerts.home-assistant.io/) - [Security Alerts](https://www.home-assistant.io/security/) - [System Status](https://status.home-assistant.io/) ### Companion apps - [iOS and Apple devices](https://apps.apple.com/app/id1099568401) - [Android and Wear OS](https://play.google.com/store/apps/details?id=io.homeassistant.companion.android) - [...and more\!](https://companion.home-assistant.io/) ### Support us - [Merch store](https://store.openhomefoundation.org/) - [Home Assistant Cloud](https://www.home-assistant.io/cloud/) ### Governance - [Privacy Notices](https://www.home-assistant.io/privacy/) - [Contributor License Agreement](https://www.home-assistant.io/developers/cla/) - [Terms of Service](https://www.home-assistant.io/tos/) - [Code of Conduct](https://www.home-assistant.io/code_of_conduct/) - [Credits](https://www.home-assistant.io/developers/credits/) - [License](https://www.home-assistant.io/developers/license/) ### Follow us [Sign up for our newsletter](https://newsletter.openhomefoundation.org/#/portal) For partnership inquiries please check out [Works With Home Assistant](https://works-with.home-assistant.io/). For media, [email our team](https://www.home-assistant.io/cdn-cgi/l/email-protection#93fef6f7faf2d3fce3f6fdfbfcfef6f5fce6fdf7f2e7fafcfdbdfce1f4). For other questions, you can [contact support](https://www.home-assistant.io/cdn-cgi/l/email-protection#afc7cac3c3c0efc7c0c2ca82cedcdcc6dcdbcec1db81c6c0) (No technical support!) Website powered by [Jekyll](https://jekyllrb.com/) Originally based on the [Oscailte theme](https://github.com/coogie/oscailte) [![Deploys by Netlify Badge](https://www.home-assistant.io/images/frontpage/netlify.svg)](https://www.netlify.com/)
Readable Markdown	Integrates devices that use the Xiaomi Mijia BLE MiBeacon protocol and the BLE protocols implemented in the MiScales and the MiFora plant sensor. This integration does not support Xiaomi BLE Mesh devices. The integration listens to Bluetooth broadcasts that the device makes by itself, allowing it to track the latest sensor values or events without waking the device up for polling (except HHCCJCY01, see note below). This method conserves battery lifetime. The integration automatically discovers devices once the [Bluetooth](https://www.home-assistant.io/integrations/bluetooth) integration is enabled and functional. The entities are added after the values are first received. This means that entities might show up later if the corresponding values are broadcasted at a lower interval (for example, battery). ## Configuration To add the Xiaomi BLE device to your Home Assistant instance, use this My button: [![](https://my.home-assistant.io/badges/config_flow_start.svg)](https://my.home-assistant.io/redirect/config_flow_start?domain=xiaomi_ble) Manual configuration steps If the above My button doesn’t work, you can also perform the following steps manually: - Browse to your Home Assistant instance. - Go to [Settings \> Devices & services](https://my.home-assistant.io/redirect/integrations). - In the bottom right corner, select the [Add Integration](https://my.home-assistant.io/redirect/config_flow_start?domain=xiaomi_ble) button. - From the list, select Xiaomi BLE. - Follow the instructions on screen to complete the setup. ## Encryption Some devices use AES encryption to protect the sensor values they are broadcasting. - MiBeacon v2/v3 use unauthenticated AES with a 24 character hexadecimal (12 byte) key - MiBeacon v4/v5 use authenticated AES with a 32 character hexadecimal (16 byte) key This key is called the bindkey or beaconkey. There are a few ways to obtain a bindkey for your device: - For v4 and v5 devices, you can provide your Xiaomi Cloud account login credentials for the account to which the device is bound. Home Assistant will import the appropriate bind key from your account. - Extract the keys from Xiaomi Cloud using a [token extractor](https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor) tool. - Set your own. The [Telink Flasher](https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html) by pvvx allows you to generate new bindkeys for devices it supports (LYWSD03MMC, MJWSD05MMC, MHO-C401, CGG1, and CGDK2). This online flashing tool also allows you to upload alternative firmware, with some improvements compared to the stock firmware, like faster sensor updates. Note that the new bind key works with Home Assistant, but the Mi Home app does not recognize the sensor anymore once the device has been activated by the TeLink flasher application. To use the sensor again with the Xiaomi Mi Home app, the device needs to be removed and then re-added inside the Mi Home app. - An alternative [Telink Flasher](https://atc1441.github.io/Temp_universal_mi_activate.html) by atc1441 also allows you to generate new bind keys, and supports even more Xiaomi devices compared to the Telink Flasher by pvvx. - Yeelight Remote (YLYK01YL) and dimmers (YLKG07YL and YLKG08YL) can use V2/V3 MiBeacon encryption, although more recent devices seem to be supplied with V4/V5 encryption. For V2/V3 MiBeacon encryption, the bindkey can’t be determined with the above methods. Instructions on how to get the bindkey for these devices can be found in the [BLE monitor FAQ](https://custom-components.github.io/ble_monitor/faq#how-to-get-the-mibeacon-v2v3-encryption-key). ## Devices ### Plant sensor: Flower Care / MiFlora (HHCCJCY01) HHCCJCY01, also known as MiFlora or “Flower Care”, should be automatically discovered. However, if the firmware is too old, it won’t send the right BLE beacons and an update via the app is required. The lowest confirmed working firmware version is 3.2.1 (a lower 3.x version could also be alright). Flower Care firmware update steps: - Install the official “Flower Care” app by HHCC: - [Google Play](https://play.google.com/store/apps/details?id=com.huahuacaocao.flowercare) (requires location and storage permission) - [Apple App Store](https://apps.apple.com/app/id1095274672) - Place the device with the app within 10cm of the plant sensor - Press the “+” button on the top right in the devices tab of the app - Add the plant sensor to the app and select an arbitrary plant - Wait for the synchronization of the sensor to finish, and a dialog asking for a firmware update should appear (this might take a few minutes) - The installed and latest firmware version can be verified by selecting the plant -\> three dots menu -\> Hardware settings -\> Hardware update - The Flower Care account and app are not required any further for this integration to work Also note that the battery level of the plant sensor can only be retrieved by connecting to the device (reading characteristics), while the other sensor data is broadcasted passively. To prevent battery drainage, a connection is made only once a day. Connecting to the device also requires that the device has a good signal strength. #### Help us improve our documentation Suggest an edit to this page, or provide/view feedback for this page. - [Edit](https://github.com/home-assistant/home-assistant.io/tree/current/source/_integrations/xiaomi_ble.markdown "Edit this page") - [Provide feedback](https://github.com/home-assistant/home-assistant.io/issues/new?template=feedback.yml&url=https%3A%2F%2Fwww.home-assistant.io%2Fintegrations%2Fxiaomi_ble%2F&version=2026.4.1&labels=current,integration%3A%20xiaomi_ble "Provide feedback on this page") - [View pending feedback](https://github.com/home-assistant/home-assistant.io/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22integration%3A+xiaomi_ble%22 "View pending feedback for this page")
Shard	77 (laksa)
Root Hash	6959518072785130877
Unparsed URL	io,home-assistant!www,/integrations/xiaomi_ble/ s443