Unable to obtain Switchbot Lock Pro encryption key

[DJOma]

The problem

I own a Switchbot Lock Pro and am not able to set up the Bluetooth integration.
They config flow is not able to obtain the encryption key and ends with "Unknown error occurred"

The device is in range, as the bluetooth dongle lays right next to it.
I have no idea, what else to try.

I am using HAOS on proxmox.
Tried every possible way to get the bluetooth device to HAOS and it discovered the lock immediately but I just can not get the key.

What version of Home Assistant Core has the issue?

2024.07.1

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

switchbot

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

The protocol lists two entries.

`Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 214, in connect
    reply = await self._bus.call(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/dbus_fast/aio/message_bus.py", line 385, in call
    await future
asyncio.exceptions.CancelledError`

And more likely the cause:

`C8-B3-56-XX-XX-XX (C8:B3:56:XX:XX:XX): device not found, no longer in range, or poor RSSI: -53
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 214, in connect
    reply = await self._bus.call(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/dbus_fast/aio/message_bus.py", line 385, in call
    await future
asyncio.exceptions.CancelledError`

Additional information

No response

[home-assistant]

Hey there @Danielhiversen, @RenierM26, @murtas, @Eloston, @dsypniewski, mind taking a look at this issue as it has been labeled with an integration (switchbot) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of switchbot 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 switchbot 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)}}

---

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

[baxxx73]

same problem for me. Any solution?

[DJOma]

I have the same problem. Any solution?

Not really, but yes.

I was able to get the ID and key using the python script provided by pySwitchbot, as mentioned in this repo.
But even with these details, the connection failed. So I assumed the problem must be somewhere else.

I suspected my Bluetooth dongle and/or Proxxmox setup. While Bluetooth seemed to be working fine, there could still be a problem.
So I found an ESP32 in my basement and used ESP Home as a Bluetooth proxy.

Worked like a charm in seconds.
I would have preferred the USB Bluetooth as the HA machine is very close to the lock and the Bluetooth dongle was able to pick up everything in a 50m circle, but it wasn't worth the hassle.

So I have no definitive solution to your problem, but perhaps a hunch.