Xiaomi BLE integration login or the bindkey are not accepted

[Mygrille]

The problem

unfortunately the integration has not been working for a few days now.
neither the login or the bindkey are accepted
i can't get any further.

What version of Home Assistant Core has the issue?

2025.6.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Xiaomi BLE integration

Link to integration documentation on our website

https://www.home-assistant.io/integrations/xiaomi_ble

Diagnostics information

home-assistant_xiaomi_ble_2025-06-29T07-22-07.489Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @Jc2k, @Ernst79, mind taking a look at this issue as it has been labeled with an integration (xiaomi_ble) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of xiaomi_ble can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign xiaomi_ble Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

xiaomi_ble documentation
xiaomi_ble source
_{^{(message by IssueLinks)}}

[github-actions]

🔍 Potential duplicate detection

I've analyzed similar issues and found the following potential duplicates:

• #147759: Xiaomi BLE Integration

What to do next:

1. Please review these issues to see if they match your issue
2. If you find an existing issue that covers your problem:
   • Consider closing this issue
   • Add your findings or 👍 on the existing issue instead
3. If your issue is different or adds new aspects, please clarify how it differs

This helps keep our issues organized and ensures similar issues are consolidated for better visibility.

This message was generated automatically by our duplicate detection system.

[Ernst79]

Removed the duplicate label, as the other issue was closed, due to non-English text.

Seems that xiaomi has changed the way the encryption key can be retrieved.

custom-components/ble_monitor#1478 (comment)

Hopefully, someone can figure this out. I see some fixes are proposed for the xiaomi cloud token extractor, but not yet merged

https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor/pulls

[Havocnl]

Also, selecting to use the username/pass method then no longer gives the option to go back and instead give the BLE key manually. I required a restart before I got the prompt "user/pass or manual key entry" again. without reboot pressing the repair button always automatically selected the user/pass option

[EndermanAPM]

Any updates on this?

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[EndermanAPM]

This was not resolved last time i checked.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.