Intel AX211 Wi-Fi 6E & Bluetooth 5.3 module issue

theliquid commented 1 year ago

The problem

I upgraded my Intel NUC to a Intel NUC 12 Pro Kit NUC12WSHi3. This device has Intel AX211 BT/WiFi module (Bluetooth 5.3). My previous NUC had a Intel 9560 module (Bluetooth 5.1). While upgrading I didn't change any Home Assistant configuration (except adding the new Bluetooth interface in Home Assistant and deleting the previous one).

The AX211 actually works when starting Home Assistant. But the sensors which are fed by the Bluetooth integration (devices by Xiaomi (Xiaomi BLE), Govee (Govee Bluetooth) and Inkbird) stop being updated after a while (about 5 minutes). I suspect that the AX211 is going into power save mode. However some of the sensors work all the time.

There are no useful logs. Currently the only "workaround" is to power off and on the Bluetooth device (bluetoothctl power off && bluetoothctl power on). After the power cycle the sensors get updated again for a short period of time.

What version of Home Assistant Core has the issue?

core-2023.8.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

bluetooth

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

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

home-assistant[bot] commented 1 year ago

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

Code owner commands

Code owners of `bluetooth` 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 bluetooth` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

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

home-assistant[bot] commented 1 year ago

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

Code owner commands

Code owners of `inkbird` 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 inkbird` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

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

home-assistant[bot] commented 1 year ago

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

Code owner commands

Code owners of `govee_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 govee_ble` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

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

home-assistant[bot] commented 1 year ago

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.

_{^{(message by CodeOwnersMention)}}

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

Jc2k commented 1 year ago

I'm going to assume you are running in active scanning mode and not passive scanning mode (otherwise Inkbird wouldn't work at all, aiui).

Are the sensors which you said continue to work Bluetooth sensors? If so, what are they?

It's fairly common for some Bluetooth modules to just stop working intermittently. Using them like we do seems to be outside the "desktop" level of performance they were designed to work at. This can be because of bugs in the kernel or in bluez or in their firmware. HA core developers can't fix firmware issues or fix Linux support.

Is your bluetooth chipset on the list of known working and known to be good list on the Bluetooth documentation site? Well worth using one from that list wherever possible.

Also, these days the ESP based proxies seem to behave better than some brands of PC bluetooth modules.

theliquid commented 1 year ago

I actually don't know the scanning mode, since I cannot view/change it in the HA integrations (as far as I know).

Yes, I only spoke about Bluetooth sensors. I have the following sensors deployed: Xiaomi BLE: HHCCJCY01 & LYWSDCGQ Inkbird: IBS-TH Govee: H5072 & H5075

The Bluetooth module isn't listed here (https://www.home-assistant.io/integrations/bluetooth/).

While HA sensors stop updating, the Bluetooth interface works flawlessly on the host. There are no errors/useful messages logged in the syslog of the host.

Host system: Ubuntu 22.04 HWE kernel: 6.2.0-26-generic

bdraco commented 1 year ago

https://github.com/home-assistant/core/issues/92379

issue-triage-workflows[bot] commented 9 months ago

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.

home-assistant / core