All Switchbot becomes unavailable daily until I restart HA.

[fangoward]

The problem

My Switchbot devices (Bot and Lock) suddenly become unavailable, at random, specially by the end of the thay . They just disconnect and doesn't come back until I restart Home Assistant.

If I go on the Switchbot app all of the devices are working just fine, so that's a problem with the integration, not the app or the Switchbot system.

That's especially annoying because I use the products to unlock my doors. Can you see what's happening?

What version of Home Assistant Core has the issue?

core-2024.4.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

Switchbot Bluetooth

Link to integration documentation on our website

No response

Diagnostics information

It just happens. For no reason, whatsoever.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

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)}}

[TheJulianJES]

Can you see what's happening?

Is there anything in the logs? Any errors you're seeing?

[fangoward]

I don't see any erros. It just goes "Unavailable" without giving me any warning and I can't control them.

Right now it's unavailable. I guess, it's not even related with the hours, it's pure random.

[fangoward]

Update. I just got this error:

This entity is no longer being provided by the switchbot integration. If the entity is no longer in use, delete it in settings.

[janfajessen]

It's about a problem with the raspberry Bluetooth and there are like 3 months unsolved. It's so annoying. It's is reported long time and lots times. I don't know what are they doing to solved. I have an automation to notify me if bluetooth lock is 5 minutes "offline" for restart manually HA..

[fangoward]

I'm not running a Raspberry, but a NUC. So I guess it has nothing to do with Raspberry specifically.

[nikee73]

Have the same problem with my Switchbot Lock. Running bluetooth from ESPHome.
Cant see anything in the Logs. It just goes to disconnected

[esguti]

Same problem. I have to reset the bluetooth to the device to become available for a couple of minutes. To reset Bluetooth I execute this command:

hciconfig hci0 reset

[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.

[esguti]

Still the same problem with Home Assistant 2023.7.3 Frontend 20230705.1 - latest

[esguti]

Still the same problem with Home Assistant 2024.5.3 Frontend 20240501.1 and python 3.12

[esguti]

I think, it is related with Bluetooth-Devices/bleak-retry-connector#91

executing

bluetoothctl -- scan on

looks like temporary solving the problem