Switchbot Integration Aborted #58547

wnaylor · 2021-10-27T20:19:20Z

The problem

When I try to install the Switchbot integration I receive a message saying that "No unconfigured devices found. I had this integration installed before but it became unavailable and now I cannot install it again.

Switchbot Integration Aborted.pdf
.

What version of Home Assistant Core has the issue?

core-2021.10.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Switchbot

Link to integration documentation on our website

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant · 2021-10-28T09:36:10Z

Hey there @Danielhiversen, @RenierM26, 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!
_{^{(message by CodeOwnersMention)}}

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

abrahamfa · 2021-10-28T11:24:07Z

I have the same problem but with the difference that when I set configuration.yaml and I get this:

ellaizee · 2021-10-28T18:47:06Z

Also having this issue as abrahamfa as of 2021-10-28 09:22 UTC. Two Switchbots and two curtain bots affected. They are still showing up as "home" via their BLE MACs so it doesn't seem to be a signal issue. When I set up the curtain bots yesterday, I was getting OP's issue but after several (and I mean several) attempts at configuring the integration, it finally showed me the expected form for MAC entry.

DanDon · 2021-10-30T04:07:18Z

I am having the same issue as OP ... Failed to connect (Aborted)

I do not have any HACS or custom repository added or manual configuration.yaml but it still does not work

RenierM26 · 2021-10-30T13:35:41Z

Hi All,

The btle scanner might require special permissions if used in custom OS versions. (non supervised install)

What OS are you guys running?
If supervised install, what BT dongle are you using?

Thanks.

DanDon · 2021-10-30T14:26:11Z

Hi All,

The btle scanner might require special permissions if used in custom OS versions. (non supervised install)

What OS are you guys running? If supervised install, what BT dongle are you using?

Thanks.

I am running HA OS with an Asus BT USB dongle plugged in.

I can add the HACS integration from the alextud git and manually configure MACs in configuration.yaml to get them working but if I add your fork and do the same thing, the devices all become unavailable. Or if I try to install the integration through the configuration/integrations gui, I get the failed to connected or aborted error - so the integration will not add/install.

RenierM26 · 2021-10-30T14:49:59Z

Hi @DanDon,

Could you please try the following commands?

docker exec -it homeassistant /bin/bash
#To get access to hass container.
hciconfig
#Should output btle adapters. The integration uses hci0.

Output should be something like this:

bash-5.1# hciconfig
hci0:   Type: Primary  Bus: UART
        BD Address: DC:A6:32:4A:D3:3F  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING
        RX bytes:1355954 acl:881 sco:0 events:43362 errors:0
        TX bytes:59699 acl:922 sco:0 commands:5099 errors:0

ellaizee · 2021-10-30T14:51:34Z

Hi All,

The btle scanner might require special permissions if used in custom OS versions. (non supervised install)

What OS are you guys running? If supervised install, what BT dongle are you using?

Thanks.

Running core-2021.10.6 (was on 10.4 when this issue started). Using Pi 4 B's onboard Bluetooth. As previously mentioned, HA can see the devices as device trackers.

RenierM26 · 2021-10-30T15:00:35Z

@ellaizee,

Your problem might be caused by the device tracker. I'm also using a PI4b with supervised install (hass os) in my production and test environment. (Without any issues)

The scanner sets bluez in a BTLE mode (le on) and other bluetooth integrations could cause conflicts with the process.

What bluetooth tracker integration are you using?

DanDon · 2021-10-30T15:55:05Z

docker exec -it homeassistant /bin/bash

Not sure where you want me to do this??

I have tried in terminal and in the cli and I have errors for both.

RenierM26 · 2021-10-30T15:59:13Z

Hi @DanDon ,

You'll need to disable protected mode for the terminal first.

I use "SSH & Web Terminal" from the Home Assistant Community Add-ons on the https://addons.community repository.

DanDon · 2021-10-30T16:04:33Z

Hi @RenierM26 ,

I am already using the SSH & Web terminal add-on ... that is what the screen grab is from.

How do I disable protected mode?

RenierM26 · 2021-10-30T16:15:29Z

Go to "Supervisor" and click on the addon. There will be a toggle switch to disable protected mode.

DanDon · 2021-10-30T16:31:31Z

Ok got it thanks:

RenierM26 · 2021-10-30T16:38:52Z

@DanDon,

Looks like you have two BT dongles? Or the asus dongle presents two interfaces.

Any chance you could try the following python code?

docker exec -it homeassistant /bin/bash
python

Then the following code:

import switchbot
switchbot.GetSwitchbotDevices(interface=0).discover()

0 = hci0
1 = hci1

Please try with 1 as well.

DanDon · 2021-10-30T16:47:05Z

Yes I believe the dongle presents to interfaces ... it is only a single BT USB dongle.

Would you like me to try this with the HACS intergration from Alextud removed and the manual config in configuration.yaml removed too ... or does it not matter?

RenierM26 · 2021-10-30T16:50:29Z

Alextud's integration uses an old version of pyswitchbot. You'll need to remove it and try the built in one.

If this works, then I'll need to add options to the integration for selecting a different interface. Shouldn't be too much effort to implement.

DanDon · 2021-10-30T17:01:14Z

RenierM26 · 2021-10-30T17:14:43Z

Try this from bash;

pip3 install --upgrade pyswitchbot

DanDon · 2021-10-30T17:21:52Z

That fixed the problem of running the python discover() ....

It does only work on interface 1 not on interface 0

I presume this means I cannot add this intergration then till the option to select interface is added :(

Thanks for you help with this so far 👍

RenierM26 · 2021-10-30T17:30:50Z

@DanDon,

Thank you for testing! You've given me the info I need to code a fix.

In the mean time you could do the following:

Copy this to your custom_integration folder:
https://github.com/RenierM26/ha-switchbot-curtain

The integration domain is named "ha-switchbot-curtain". I initially stated the rewrite as a pull request on Alextuds's repository.

Edit the coordinator.py file as follows:

Change this:
return self.switchbot_api.GetSwitchbotDevices().discover(

to:
return self.switchbot_api.GetSwitchbotDevices(interface=1).discover(

RenierM26 · 2021-10-30T17:36:10Z

You'll need to remove the integration in totality. Bluetooth scanning processes between libraries causes conflicts. The dongle can only handle 1 operation at a time and gets locked up if multiple libraries attempts a bluetooth discover.

DanDon · 2021-10-30T17:50:26Z

@DanDon,

Thank you for testing! You've given me the info I need to code a fix.

In the mean time you could do the following:

Copy this to your custom_integration folder:
https://github.com/RenierM26/ha-switchbot-curtain

The integration domain is named "ha-switchbot-curtain". I initially stated the rewrite as a pull request on Alextuds's repository.

Edit the coordinator.py file as follows:

Change this: return self.switchbot_api.GetSwitchbotDevices().discover(

to: return self.switchbot_api.GetSwitchbotDevices(interface=1).discover(

Thanks for this try but it doesn't work...

The terminal gives this:

The config I set was this:

I am using the white Switchbot Curtain to add to intergrations:

But I still get this error:

RenierM26 · 2021-10-30T17:55:50Z

@DanDon ,

Sorry, missed one more change:

in config_flow.py:

Change:

switchbot_devices = GetSwitchbotDevices().discover()

to

switchbot_devices = GetSwitchbotDevices(interface=1).discover()

DanDon · 2021-10-30T18:10:53Z

~~Incredible!!~~

~~That has fixed it thank you! Now the intergration adds and I can select the mac addresses from the list etc...~~

~~Thanks for your help again~~

DanDon · 2021-10-30T18:15:30Z

Sorry @RenierM26

Although ....

It seems that I'm getting errors now when trying to open / close etc .... cannot communicate

Is there somewhere in the config that requires the signals to be sent out via a specific interface??

RenierM26 · 2021-10-30T18:50:23Z

Hi @DanDon ,

Under cover.py and switch.py:
Change:

                coordinator.switchbot_api.SwitchbotCurtain(
                    mac=entry.data[CONF_MAC],
                    password=entry.data.get(CONF_PASSWORD),
                    retry_count=entry.options[CONF_RETRY_COUNT],

to:

                coordinator.switchbot_api.SwitchbotCurtain(
                    mac=entry.data[CONF_MAC],
                    password=entry.data.get(CONF_PASSWORD),
                    interface=1,
                    retry_count=entry.options[CONF_RETRY_COUNT],

Should do it.

DanDon · 2021-10-30T19:14:20Z

There is progress!! 😃

I can get them to work with that change but there is a huge delay and seems like they only activate after the third attempt:

ShaneQi · 2021-11-04T15:22:52Z

@RenierM26

The link you sent helped, now I fixed it for my docker container.

I only needed to add in my docker compose file (tested and worked):

  cap_add:
    - net_admin

I think the command equivalent is --cap-add=net_admin (not tested).

marcotini · 2021-11-18T17:32:30Z

>>> import switchbot
>>> switchbot.GetSwitchbotDevices(interface=0).discover()
Error scanning for switchbot devices
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/switchbot/__init__.py", line 147, in discover
    devices = bluepy.btle.Scanner(self._interface).scan(
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 852, in scan
    self.start(passive=passive)
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 790, in start
    self._mgmtCmd("le on")
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 312, in _mgmtCmd
    raise BTLEManagementError("Failed to execute management command '%s'" % (cmd), rsp)
bluepy.btle.BTLEManagementError: Failed to execute management command 'le on' (code: 12, error: Not Supported)
Error scanning for Switchbot devices. Retrying (remaining: 3)
Error scanning for switchbot devices
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/switchbot/__init__.py", line 147, in discover
    devices = bluepy.btle.Scanner(self._interface).scan(
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 852, in scan
    self.start(passive=passive)
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 790, in start
    self._mgmtCmd("le on")
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 312, in _mgmtCmd
    raise BTLEManagementError("Failed to execute management command '%s'" % (cmd), rsp)
bluepy.btle.BTLEManagementError: Failed to execute management command 'le on' (code: 12, error: Not Supported)
Error scanning for Switchbot devices. Retrying (remaining: 2)
Error scanning for switchbot devices
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/switchbot/__init__.py", line 147, in discover
    devices = bluepy.btle.Scanner(self._interface).scan(
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 852, in scan
    self.start(passive=passive)
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 790, in start
    self._mgmtCmd("le on")
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 312, in _mgmtCmd
    raise BTLEManagementError("Failed to execute management command '%s'" % (cmd), rsp)
bluepy.btle.BTLEManagementError: Failed to execute management command 'le on' (code: 12, error: Not Supported)
Error scanning for Switchbot devices. Retrying (remaining: 1)
Error scanning for switchbot devices
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/switchbot/__init__.py", line 147, in discover
    devices = bluepy.btle.Scanner(self._interface).scan(
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 852, in scan
    self.start(passive=passive)
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 790, in start
    self._mgmtCmd("le on")
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 312, in _mgmtCmd
    raise BTLEManagementError("Failed to execute management command '%s'" % (cmd), rsp)
bluepy.btle.BTLEManagementError: Failed to execute management command 'le on' (code: 12, error: Not Supported)
Scanning for Switchbot devices failed. Stop trying
NoneType: None
{}

It's not working for me. Bluetooth working ok inside Docker container.

ShaneQi · 2021-11-18T17:36:01Z

@marcotini

Did you try adding cap for your docker container like I mentioned in this comment?

#58547 (comment)

lonsdaleite · 2021-11-21T19:30:56Z

RPI 4, HA in docker.
Today I've encountered all these switchbot problems after upgrading from 2021.5.x to 2021.11.x: same log errors and my device becomes unavailable every few minutes.
I've tried adding cap_add net_admin to the docker-compose.yaml, nothing changed. I've noticed that there was a big switchbot integration update since 2021.10.x. So I've downgraded my HomeAssistant to 2021.9.7 and now everything works great again. I guess I could just use an old copy of switchbot integration but there could be some conflicts with pyswitchbot dependency.

RenierM26 · 2021-11-22T16:57:01Z

Hi @lonsdaleite,

Your problem should be fixed in the next release (2021.12). You could try copying the latest integration from the DEV branch if you run a non supervised install? (For advanced users though - I would recommend waiting for the next stable release.)

lonsdaleite · 2021-11-22T18:03:03Z

Hi @RenierM26,

I've tried to install the DEV version of Switchbot integration but it doesn't work because of requirements conflict: 2021.9.7 requires pySwitchbot 0.8.0 and DEV requires pySwitchbot 0.13.0.
Maybe you know how to resolve this conflict?

GingerLoaf · 2021-11-23T09:05:40Z

Going to gently toss my name into the hat here as well... I am entirely down to test the dev changes before a stable release.

I am gonna snag the latest dev code and pull the switchbot component and see if it works for me 👍

naoyteruh · 2022-01-13T21:25:18Z

Hi,

Same here with HA docker 2021.12.9, with this error :

hass_1         | 2022-01-13 22:12:19 ERROR (SyncWorker_1) [switchbot] Error scanning for switchbot devices
hass_1         | Traceback (most recent call last):
hass_1         |   File "/usr/local/lib/python3.9/site-packages/switchbot/__init__.py", line 147, in discover
hass_1         |     devices = bluepy.btle.Scanner(self._interface).scan(
hass_1         |   File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 852, in scan
hass_1         |     self.start(passive=passive)
hass_1         |   File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 790, in start
hass_1         |     self._mgmtCmd("le on")
hass_1         |   File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 312, in _mgmtCmd
hass_1         |     raise BTLEManagementError("Failed to execute management command '%s'" % (cmd), rsp)
hass_1         | bluepy.btle.BTLEManagementError: Failed to execute management command 'le on' (code: 20, error: Permission Denied)
hass_1         | 2022-01-13 22:12:19 WARNING (SyncWorker_1) [switchbot] Error scanning for Switchbot devices. Retrying (remaining: 1)

Any clue on a fix release date ?
Anyone has a workaround ?

djiti · 2022-01-15T10:25:34Z

Same here with HA docker 2021.12.9, with this error :

hass_1         | 2022-01-13 22:12:19 ERROR (SyncWorker_1) [switchbot] Error scanning for switchbot devices
hass_1         | Traceback (most recent call last):
hass_1         |   File "/usr/local/lib/python3.9/site-packages/switchbot/__init__.py", line 147, in discover
hass_1         |     devices = bluepy.btle.Scanner(self._interface).scan(
hass_1         |   File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 852, in scan
hass_1         |     self.start(passive=passive)
hass_1         |   File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 790, in start
hass_1         |     self._mgmtCmd("le on")
hass_1         |   File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 312, in _mgmtCmd
hass_1         |     raise BTLEManagementError("Failed to execute management command '%s'" % (cmd), rsp)
hass_1         | bluepy.btle.BTLEManagementError: Failed to execute management command 'le on' (code: 20, error: Permission Denied)
hass_1         | 2022-01-13 22:12:19 WARNING (SyncWorker_1) [switchbot] Error scanning for Switchbot devices. Retrying (remaining: 1)

Any clue on a fix release date ? Anyone has a workaround ?

Adding the net_admin capability to the container in docker-compose got me one step closer and fixed the error message your are showing, but I am not completely there just yet:

    restart: always
    network_mode: host
    cap_add:
      - net_admin

I then

re-up docker-compose
add the SwitchBot integration that fails with "No unconfigured devices found".

Looking inside the container, a manual discovery succeeds more often than not:

$ docker exec -it homeassistant /bin/bash
bash-5.1# python
Python 3.9.7 (default, Sep  9 2021, 13:39:57) 
[GCC 10.3.1 20210424] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import switchbot
>>> switchbot.GetSwitchbotDevices(interface=0).discover()
{'XXXXXXXXXXXX': {'mac_address': 'XX:XX:XX:XX:XX:XX', 'isEncrypted': False, 'model': 'T', 'data': {'temp': {'c': 21.6, 'f': 70.88}, 'fahrenheit': False, 'humidity': 33, 'battery': 100, 'rssi': -82}, 'modelName': 'WoSensorTH'}}
>>>

I checked the list of devices, I cannot find my SwitchBot sensor.

dhawani · 2022-01-18T21:27:10Z

In case of multiple bluetooth adaptors and you aren't using other adapter, you can follow this article:
https://blog.evad.io/2018/01/11/disabling-the-built-in-bluetooth-and-use-a-usb-adaptor-instead-on-linux/

djiti · 2022-01-19T17:47:54Z

In case of multiple bluetooth adaptors and you aren't using other adapter, you can follow this article: https://blog.evad.io/2018/01/11/disabling-the-built-in-bluetooth-and-use-a-usb-adaptor-instead-on-linux/

Thanks for the link, but it is not a case of multiple bluetooth adaptors.
It is a case of a simple Raspberry Pi 4 Model B that has no problem to switchbot.GetSwitchbotDevices(interface=0).discover(), but that will consistently give me "No unconfigured devices found" when adding the SwitchBot integration.
Even when I wipe out my home-assistant volume and restart my homeassistant/home-assistant:stable image.

djiti · 2022-01-22T08:21:07Z

Even when I wipe out my home-assistant volume and restart my homeassistant/home-assistant:stable image.

I gave homeassistant/home-assistant:2022.2.0.dev20220119 a try, same symptoms

github-actions · 2022-04-24T08:06:34Z

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.

danir-de · 2022-04-28T19:37:14Z

This still is an issue for me and my Raspberry Pi 4 and Home Assistant OS 7.6. #notstale

sirnicolas21 · 2022-05-04T16:08:29Z

still a problem on Raspberry Pi 4


Host Operating System | Home Assistant OS 8.0.rc3
Update Channel | stable
Supervisor Version | supervisor-2022.05.0
Docker Version | 20.10.14

info-path · 2022-05-14T20:25:22Z

I also have a problem with SwitchBot integration

If anyone has a tip what else should I test for successful integration I will be happy.

Server: Intel NUC (NUC7i7BNH), Ubuntu 20.04
HA Running in Container (Home Assistant Core 2022.5.4)
SwitchBot device: SwitchBot MeterTH S1

xxx@nuc:~$ docker exec -it home-assistant /bin/bash
bash-5.1# hciconfig
hci0:   Type: Primary  Bus: USB
        BD Address: 1C:4D:70:B7:B3:4D  ACL MTU: 1021:4  SCO MTU: 96:6
        UP RUNNING PSCAN ISCAN
        RX bytes:14032014 acl:0 sco:0 events:179672 errors:0
        TX bytes:173643 acl:0 sco:0 commands:11752 errors:0

bash-5.1# python
Python 3.9.9 (main, Feb  8 2022, 09:16:53)
[GCC 10.3.1 20210424] on linux
Type "help", "copyright", "credits" or "license" for more information.

>>> import switchbot
>>> switchbot.GetSwitchbotDevices(interface=0).discover()
{'fda853264875': {'mac_address': 'fd:a8:53:26:48:75', 'isEncrypted': False, 'model': 'T', 'data': {'temp': {'c': 29.6, 'f': 85.28}, 'fahrenheit': False, 'humidity': 26, 'battery': 100, 'rssi': -45}, 'modelName': 'WoSensorTH'}}

However, when I try to add integration, the following messages appear:

Unexpected error.

Or

No unconfigured devices found.

There is part of my docker-compose file:

homeassistant:
  container_name: "home-assistant"
  image: "homeassistant/home-assistant:latest"
  cap_add:
    - net_admin     # test for switchbot...
  depends_on:
    - mariadb
    - influxdb
  environment:
    PUID: 1000
    PGID: 1000
    TZ: "Europe/Prague"
  network_mode: host
  privileged: true
  restart: unless-stopped
  volumes:
    ...

Fenrir88 · 2022-05-28T17:57:19Z

Still an issue, running on container on rpi4 and also in os also in rpi4

MickL · 2022-07-12T20:41:03Z

I have Raspberry Pi 3 and I ran into the same error "Failed to connect" when trying to add the integration to Home Assistant. I dont see any error in the logs.

I would like to connect the new temperature/humidity sensor. Cant find any solution.

tjuanma · 2022-07-14T08:34:10Z

I can use the integration, it detects the courtins but noithing happends if I try to "move" them.
And it's impossible to connect to a temperature/humidity sensor.

HA OS in RPI4, lastest version

bdraco · 2022-07-24T19:28:03Z

The underlying library has changed for switchbot to use bleak, since this issue is about a problem with bluepy, which is no longer used, please update to a newer version of Home Assistant.

Thanks 👍

bdraco · 2022-07-24T19:42:48Z

D-Bus and BlueZ are required on Linux

For Bluetooth to function on Linux systems, the D-Bus socket must be accessible to Home Assistant. The Bluetooth adapter must be accessible to D-Bus and running BlueZ >= 5.43.

Home Assistant Operating System: no additional steps are required. Version 8.4 or later is recommended for performance reasons.
Home Assistant Container: The host system must run BlueZ, and the D-Bus socket must be accessible to Home Assistant inside the container.
Home Assistant Supervised: The host system must run BlueZ, and the D-Bus socket must be accessible to Home Assistant inside the container.
Home Assistant Core: The system must run BlueZ, and the D-Bus socket must be accessible to Home Assistant.

tjuanma · 2022-07-24T20:00:03Z

The underlying library has changed for switchbot to use bleak, since this issue is about a problem with bluepy, which is no longer used, please update to a newer version of Home Assistant.

Thanks 👍

still having same issur in:

Home Assistant 2022.7.6
Supervisor 2022.07.0
Operating System 8.2
Frontend 20220707.1 - latest

bdraco · 2022-07-24T20:03:19Z

Home Assistant 2022.7.6

Please try 2022.8.0 when it comes out. There have been quite a few fixes.

tjuanma · 2022-07-24T20:12:04Z

Home Assistant 2022.7.6

Please try 2022.8.0 when it comes out. There have been quite a few fixes.

Ok,i Will try and i uodate the thread ;)

thank you

bdraco · 2022-07-24T20:28:38Z

If you still have an issue with 2022.8.0, please open a new issue. This one is cluttered with unrelated information and multiple problems which makes it impossible to solve.

Thanks 👍

ludeeus added the integration: switchbot label Oct 28, 2021

probot-home-assistant bot assigned Danielhiversen Oct 28, 2021

github-actions bot added the stale label Apr 24, 2022

github-actions bot removed the stale label Apr 28, 2022

nitobuendia mentioned this issue Jul 20, 2022

Switchbot not working in 2022.7 Docker Container #74621

Closed

bdraco closed this as not planned Won't fix, can't repro, duplicate, stale Jul 24, 2022

home-assistant locked as resolved and limited conversation to collaborators Jul 24, 2022

Switchbot Integration Aborted #58547

Switchbot Integration Aborted #58547

Comments

wnaylor commented Oct 27, 2021

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

probot-home-assistant bot commented Oct 28, 2021

abrahamfa commented Oct 28, 2021

ellaizee commented Oct 28, 2021 • edited Loading

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021 • edited Loading

ellaizee commented Oct 30, 2021

RenierM26 commented Oct 30, 2021 • edited Loading

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021 • edited Loading

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021 • edited Loading

RenierM26 commented Oct 30, 2021

DanDon commented Oct 30, 2021

RenierM26 commented Oct 30, 2021

DanDon commented Oct 30, 2021 • edited Loading

DanDon commented Oct 30, 2021 • edited Loading

RenierM26 commented Oct 30, 2021

DanDon commented Oct 30, 2021

ShaneQi commented Nov 4, 2021 • edited Loading

marcotini commented Nov 18, 2021

ShaneQi commented Nov 18, 2021

lonsdaleite commented Nov 21, 2021

RenierM26 commented Nov 22, 2021

lonsdaleite commented Nov 22, 2021

GingerLoaf commented Nov 23, 2021

naoyteruh commented Jan 13, 2022

djiti commented Jan 15, 2022 • edited Loading

dhawani commented Jan 18, 2022

djiti commented Jan 19, 2022

djiti commented Jan 22, 2022

github-actions bot commented Apr 24, 2022

danir-de commented Apr 28, 2022

sirnicolas21 commented May 4, 2022

info-path commented May 14, 2022 • edited Loading

Fenrir88 commented May 28, 2022

MickL commented Jul 12, 2022 • edited Loading

tjuanma commented Jul 14, 2022

bdraco commented Jul 24, 2022

bdraco commented Jul 24, 2022

D-Bus and BlueZ are required on Linux

tjuanma commented Jul 24, 2022

bdraco commented Jul 24, 2022

tjuanma commented Jul 24, 2022

bdraco commented Jul 24, 2022 • edited Loading

ellaizee commented Oct 28, 2021 •

edited

Loading

RenierM26 commented Oct 30, 2021 •

edited

Loading

RenierM26 commented Oct 30, 2021 •

edited

Loading

RenierM26 commented Oct 30, 2021 •

edited

Loading

RenierM26 commented Oct 30, 2021 •

edited

Loading

DanDon commented Oct 30, 2021 •

edited

Loading

DanDon commented Oct 30, 2021 •

edited

Loading

ShaneQi commented Nov 4, 2021 •

edited

Loading

djiti commented Jan 15, 2022 •

edited

Loading

info-path commented May 14, 2022 •

edited

Loading

MickL commented Jul 12, 2022 •

edited

Loading

bdraco commented Jul 24, 2022 •

edited

Loading