SwitchBot Bluetooth integration not working well since HAOS 9.5 #2961
Comments
|
Confirmed still an issue with HAOS 11.2. Related issue in HAOS: #2612 Related issue in HA Core: home-assistant/core#102077 |
|
That confirms what @agners said in the discussions thread - the kernel update is indeed the cause. I was able to reproduce Blutetooth issues easily after the upgrade too and ended up bisecting the kernel, which pointed me to this commit in It took about 13 steps when bisecting between the two tagged versions - maybe if you check changes around the above patch first, it could take a bit less - more Bluetooth refactoring and rewites happened around that patch. I'd be glad to help resolving that but unfortunately I'm unable to reproduce any Bluetooth issues reliably anymore. If you're willing to do some further tests, let me know. Btw. I'm missing the information what Bluetooth adapter are you using, could you tell us? |
|
I am certainly willing to do more testing; gladly. With respect to the Bluetooth adapter used: I'm not exactly sure. Can I find this information somewhere? I tried looking in the output of dmesg, but that did not really tell me much. |
|
You are probably already familiar with how bisecting works but maybe someone else finds the description of the whole process useful, so here it is:
You can try testing individual commits that you find suspicious an mark them as good/bad - e.g. Hope I haven't missed anything, if there's something unclear, let me know. About the BT adapter - you should be able to see it from |
|
I also have this issue, and am using the would like to help If I can, but this issue persistent all the way up to |
|
FYI: The Bluetooth adapters used are:
output from does this provide the requested information regarding the Bluetooth adapter used? |
I updated this in Is this the right place to change this? |
I'm trying with actual linux versions now (as a workaround). However, after a successful build I do not have any raucb files in the images folder. There are some in the build folder, but those are probably not the right ones. |
It is indeed, however I forgot to point out you need to make one more adjustment to tell Buildroot to use Git repository to obtain the sources. See the following diff: diff --git a/buildroot-external/configs/ova_defconfig b/buildroot-external/configs/ova_defconfig
index b49d826d3..bcd2a764e 100644
--- a/buildroot-external/configs/ova_defconfig
+++ b/buildroot-external/configs/ova_defconfig
@@ -16,8 +16,9 @@ BR2_ROOTFS_POST_BUILD_SCRIPT="$(BR2_EXTERNAL_HASSOS_PATH)/scripts/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="$(BR2_EXTERNAL_HASSOS_PATH)/scripts/post-image.sh"
BR2_ROOTFS_POST_SCRIPT_ARGS="$(BR2_EXTERNAL_HASSOS_PATH)/board/pc/ova $(BR2_EXTERNAL_HASSOS_PATH)/board/pc/ova/hassos-hook.sh"
BR2_LINUX_KERNEL=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.1.69"
+BR2_LINUX_KERNEL_CUSTOM_GIT=y
+BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="8bb7eca972ad531c9b149c0a51ab43a417385813"
BR2_LINUX_KERNEL_DEFCONFIG="x86_64"
BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="$(BR2_EXTERNAL_HASSOS_PATH)/kernel/hassos.config $(BR2_EXTERNAL_HASSOS_PATH)/kernel/docker.config $(BR2_EXTERNAL_HASSOS_PATH)/kernel/device-support.config $(BR2_EXTERNAL_HASSOS_PATH)/kernel/device-support-pcie.config $(BR2_EXTERNAL_HASSOS_PATH)/kernel/device-support-wireless.config $(BR2_EXTERNAL_HASSOS_PATH)/kernel/device-support-wireless-pci.config $(BR2_EXTERNAL_HASSOS_PATH)/board/pc/ova/kernel.config"
BR2_LINUX_KERNEL_LZ4=y
Every build should end with bunch of messages from RAUC, along with a message like this one: If it's not there, then something else might be off. |
With the additional changes, I now get a finished build. Thanks for the additional pointers. It did take a lot longer to finish building it, though (which I guess can be expected, as it has to do a full kernel build). However, I still do not get any raucb files. The command I'm using to build all this is: which gives me a bunch of outputs: leading me to believe the build was ok. Just no raucb file. |
|
Judging from the version identifier, you've got checked out some older version of HAOS. To get the RAUC update file, you need signing certs, which had to be supplied manually just until recent change (c3b9912). I assume the build also ends with some errors and non-zero return code, which would be another indicator something's wrong. I suggest to use the latest |
|
You are correct, I checked out a version near to where the bluetooth problems were first introducted. As far as I can tell, the build ends without any errors. I will try to build on the latest |
|
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. |
|
Oh well, it's a shame to have to give up on this device :-/
…On Wed, Apr 3, 2024 at 1:40 AM github-actions[bot] ***@***.***> wrote:
There hasn't been any activity on this issue recently. To keep our backlog
manageable we have to clean old issues, as many of them have already been
resolved with the latest updates.
Please make sure to update to the latest Home Assistant OS 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.
—
Reply to this email directly, view it on GitHub
<#2961 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMFGJJBWABMNO7P7SZ2IWTY3OI6PAVCNFSM6AAAAABAFAPP7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTGU3TGNJYHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. |
|
I'm finding this device still doesn't work (not reporting power usage) in
12.4.
…On Wed, Jul 3, 2024, 1:40 AM github-actions[bot] ***@***.***> wrote:
There hasn't been any activity on this issue recently. To keep our backlog
manageable we have to clean old issues, as many of them have already been
resolved with the latest updates.
Please make sure to update to the latest Home Assistant OS 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.
—
Reply to this email directly, view it on GitHub
<#2961 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMFGJOCCC7LOPYCIN7MXDLZKOFGDAVCNFSM6AAAAABAFAPP7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBVGEZTSNRZGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
So is the conclusion that you need a different bluetooth adapter if you suffer from this issue (slow/sequential commands post-9.5)? This is what I have at the moment: |
That's my impression. I have two hosts, with two different BT devices. It works on one and not on the other. Every other BT related device works on both, except for SwitchBot, unfortunately. |
|
I ended up using the bluetooth proxy capabilities of ESP32 devices that I already had. |
I have 3-4 of these proxies around the house, that I use for a variety of BLE sensors, but unfortunately that did not let me connect the SwitchBot ones. Could that be separate issue? |
|
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. |
Describe the issue you are experiencing
I have a number of SwitchBot Curtains connected via the Bluetooth and SwitchBot integrations.
When I open or close one of them, there seems to be a 10 second delay before it responds.
When I open or close multiple simultaneously, they seem very slow to respond, and it appears like the are operated in sequence.
More people seem to be affected by this issue, as reported in home-assistant/core#92839.
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
11.1
Did you upgrade the Operating System.
No
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
I was able to trace down this problem to one commit in HAOS:
A custom build right before this commit works perfectly:
starting with the commit the problems are reproduceable.
I opened and closed a group of curtains in both versions with the debug logging enabled for both Bluetooth and SwitchBot integrations.
I added the homeassistant.log for both versions as attachments.
bluetooth-ok.log
bluetooth-fail.log
The text was updated successfully, but these errors were encountered: