operating-system icon indicating copy to clipboard operation
operating-system copied to clipboard

Published 20 hours ago • verified publisher icon home-assistant

Error :" brcmfmac: brcmf_set_channel: set chanspec 0xd0...fail, reason -52 "

Open davidclaverie opened this issue 1 year ago • 31 comments
trafficstars

Describe the issue you are experiencing

i have since last days after update this error brcmfmac: brcmf_set_channel: set chanspec 0xd0...fail, reason -52

may be the same i see here https://github.com/raspberrypi/linux/issues/6049

Thanks to help me. im not a 'system user'..

What operating system image do you use?

rpi4-64 (Raspberry Pi 4/400 64-bit OS)

What version of Home Assistant Operating System is installed?

6.6.28-haos-raspi

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

  1. When i reboot the system

...

Anything in the Supervisor logs that might be useful for us?

2024-05-13 14:49:33.836 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (486e6e9b_zigbee2mqtt)
2024-05-13 14:49:34.100 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system
2024-05-13 14:49:34.101 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2024-05-13 14:49:34.231 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2024-05-13 14:49:34.232 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
2024-05-13 14:49:34.252 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2024-05-13 14:49:34.253 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2024-05-13 14:49:34.254 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system
2024-05-13 14:49:34.255 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2024-05-13 14:49:34.256 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2024-05-13 14:49:34.257 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2024-05-13 14:49:34.383 INFO (MainThread) [supervisor.resolution.check] System checks complete
2024-05-13 14:49:34.383 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-05-13 14:49:34.857 INFO (MainThread) [supervisor.host.services] Updating service information
2024-05-13 14:49:34.872 INFO (MainThread) [supervisor.host.network] Updating local network information
2024-05-13 14:49:35.208 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
2024-05-13 14:49:35.227 INFO (MainThread) [supervisor.host.manager] Host information reload completed
2024-05-13 14:49:35.371 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2024-05-13 14:49:35.372 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2024-05-13 14:49:35.372 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2024-05-13 14:49:37.640 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Linky is stopped, restarting...
2024-05-13 14:49:37.653 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning addon_cf6b56a3_linky application
2024-05-13 14:49:38.362 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/bokub/ha-linky-aarch64 with version 1.4.0
2024-05-13 14:49:45.585 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Linky is stopped, restarting...
2024-05-13 14:49:45.603 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_cf6b56a3_linky application
2024-05-13 14:49:46.335 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/bokub/ha-linky-aarch64 with version 1.4.0
2024-05-13 14:49:53.561 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Linky is stopped, restarting...
2024-05-13 14:49:53.579 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_cf6b56a3_linky application
2024-05-13 14:49:54.338 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/bokub/ha-linky-aarch64 with version 1.4.0
2024-05-13 14:49:54.798 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:50:01.657 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Linky is stopped, restarting...
2024-05-13 14:50:01.675 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning addon_cf6b56a3_linky application
2024-05-13 14:50:02.411 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/bokub/ha-linky-aarch64 with version 1.4.0
2024-05-13 14:50:09.906 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Linky is stopped, restarting...
2024-05-13 14:50:09.928 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning addon_cf6b56a3_linky application
2024-05-13 14:50:10.735 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/bokub/ha-linky-aarch64 with version 1.4.0
2024-05-13 14:50:15.799 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:50:18.021 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Linky is stopped, restarting...
2024-05-13 14:50:18.037 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning addon_cf6b56a3_linky application
2024-05-13 14:50:18.740 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/bokub/ha-linky-aarch64 with version 1.4.0
2024-05-13 14:50:25.892 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-5070' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1429> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 1443, in watchdog_container
    await self._restart_after_problem(event.state)
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 290, in wrapper
    raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00
2024-05-13 14:50:36.798 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:50:57.795 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:51:08.630 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from f0e7e328_hassio_google_drive_backup
2024-05-13 14:51:08.643 INFO (MainThread) [supervisor.api.middleware.security] /backups access from f0e7e328_hassio_google_drive_backup
2024-05-13 14:51:18.829 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:51:39.803 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:52:00.800 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:52:21.815 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:52:42.806 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:53:03.808 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:53:14.054 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (486e6e9b_zigbee2mqtt)
2024-05-13 14:53:24.803 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:53:45.798 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:54:06.797 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:54:27.800 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:54:48.797 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:55:09.797 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:55:30.796 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:55:51.793 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:56:12.801 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:56:33.839 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:56:54.799 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:57:15.795 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:57:36.802 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:57:57.794 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:58:18.793 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:58:20.052 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (486e6e9b_zigbee2mqtt)
2024-05-13 14:58:39.799 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:59:00.910 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:59:21.793 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 14:59:42.796 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:00:03.801 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:00:24.787 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:00:45.797 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:01:06.795 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:01:27.795 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:01:48.794 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:02:09.789 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:02:30.796 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:02:51.793 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:03:12.801 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:03:26.763 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (486e6e9b_zigbee2mqtt)
2024-05-13 15:03:30.831 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (486e6e9b_zigbee2mqtt)
2024-05-13 15:03:33.797 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:03:54.800 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:04:15.801 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:04:36.802 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:04:57.801 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:05:18.802 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:05:39.799 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:06:00.800 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:06:21.802 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b
2024-05-13 15:06:42.803 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 2afc3da3f78f2a83e84e0e1b3af90f0b53abf5e2cd39a9ffbf8ab9818558fba4c68a8a128c4ff16f493969e16dcf5c5d02aca14ebfb719f908f3dbfd0a7dec1b

Anything in the Host logs that might be useful for us?

2024-05-13 14:04:24.366 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:27.694 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:31.023 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:34.351 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:37.674 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:39.325 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
2024-05-13 14:04:39.326 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
2024-05-13 14:04:39.433 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
2024-05-13 14:04:39.536 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
2024-05-13 14:04:39.641 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
2024-05-13 14:04:41.305 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
2024-05-13 14:04:41.305 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
2024-05-13 14:04:41.305 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
2024-05-13 14:04:41.309 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
2024-05-13 14:04:41.309 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
2024-05-13 14:04:41.309 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
2024-05-13 14:04:41.312 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:44.590 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:47.918 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:51.245 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:54.574 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:04:57.904 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:01.231 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:04.558 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:07.890 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:11.214 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:14.542 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:17.870 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:21.198 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:24.526 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:27.854 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:31.181 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:34.510 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:37.838 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:41.166 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:44.494 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:47.822 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:51.149 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:54.478 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:05:57.806 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:01.135 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:04.462 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:07.790 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:11.118 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:14.446 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:17.774 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:21.102 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:24.430 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:27.758 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:31.086 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:34.414 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:37.738 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:40.261 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
2024-05-13 14:06:40.261 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
2024-05-13 14:06:40.369 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
2024-05-13 14:06:40.472 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
2024-05-13 14:06:40.577 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
2024-05-13 14:06:42.245 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
2024-05-13 14:06:42.245 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
2024-05-13 14:06:42.245 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
2024-05-13 14:06:42.245 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
2024-05-13 14:06:42.249 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
2024-05-13 14:06:42.249 homeassistant kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
2024-05-13 14:06:42.250 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:45.423 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:48.751 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:52.079 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:55.406 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:58.734 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:06:59.917 homeassistant kernel: audit: type=1334 audit(1715609219.907:660): prog-id=163 op=LOAD
2024-05-13 14:06:59.920 homeassistant systemd-timesyncd[584]: Network configuration changed, trying to establish connection.
2024-05-13 14:06:59.945 homeassistant systemd[1]: Started Journal Gateway Service.
2024-05-13 14:07:00.029 homeassistant systemd-timesyncd[584]: Contacted time server 162.159.200.1:123 (time.cloudflare.com).
2024-05-13 14:07:02.062 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:05.391 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:08.722 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:12.054 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:15.374 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:18.703 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:22.030 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:25.364 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:28.686 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:32.014 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:35.342 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:38.670 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:41.998 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:45.326 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:48.654 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:51.982 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:55.310 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:07:58.638 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:01.966 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:05.295 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:08.622 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:11.952 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:15.277 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:18.609 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:21.936 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:25.262 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:28.590 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-05-13 14:08:31.918 homeassistant wpa_supplicant[517]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

System information

System Information

version core-2024.5.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.6.28-haos-raspi
arch aarch64
timezone Africa/Libreville
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 5000
Installed Version 1.34.0
Stage running
Available Repositories 1396
Downloaded Repositories 56
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 12.3
update_channel stable
supervisor_version supervisor-2024.05.1
agent_version 1.6.0
docker_version 25.0.5
disk_total 234.0 GB
disk_used 13.4 GB
healthy true
supported true
board rpi4-64
supervisor_api ok
version_api ok
installed_addons Terminal & SSH (9.14.0), Mosquitto broker (6.4.0), Zigbee2MQTT (1.37.1-1), Studio Code Server (5.15.0), Node-RED (17.0.12), eWeLink Smart Home (1.4.3), ZeroTier One (0.18.0), Cloudflared (5.1.9), AdGuard Home (5.0.7), Samba share (12.3.1), Home Assistant Google Drive Backup (0.112.1), FTP (5.0.2), ESPHome (2024.4.1), Uptime Kuma (0.12.1), Linky (1.4.0), Network UPS Tools (0.13.0), Music Assistant (2.0.2)
Dashboards
dashboards 4
resources 33
views 65
mode storage
Recorder
oldest_recorder_run 3 mai 2024 à 05:34
current_recorder_run 13 mai 2024 à 14:47
estimated_db_size 333.26 MiB
database_engine sqlite
database_version 3.44.2

Additional information

i think its the same like i see here?? https://github.com/raspberrypi/linux/issues/6049

but im not a "system user"

thanks to help me

davidclaverie avatar May 13 '24 14:05 davidclaverie

Exactly the same issue here... Using RPI3A+.. I hope it will be fixed because it is causing big instability

spanzetta avatar May 22 '24 18:05 spanzetta

No news on this?

I still have the problem at every boot..

How to fix it??

spanzetta avatar Jun 04 '24 08:06 spanzetta

I am also experiencing the same issue after an update

sadranyi avatar Jun 04 '24 17:06 sadranyi

Same for me. RPi3B+ and RPi5.

Core 2024.6.0 Supervisor 2024.06.0 Operating System 12.3 Frontend 20240605.0

dduster avatar Jun 07 '24 18:06 dduster

I hope that developers are aware of this problem and that they are doing something to fix it in next build..

spanzetta avatar Jun 08 '24 19:06 spanzetta

I am experiencing the same.

The error brcmfmac: brcmf_set_channel: set chanspec 0xd0...fail, reason -52 pops up multiple times after the line Waiting for the Home Assistant CLI to be ready... and then the CLI is loaded.

Operating System 12.3

**Update: Error goes away after downgrading OS to 12.2

tsanidisDev avatar Jun 11 '24 15:06 tsanidisDev

receiving brcmfmac: brcmf_set_channel: set chanspec 0xd0...fail, reason -52 as well

rkrkrk0987 avatar Jun 12 '24 07:06 rkrkrk0987

I wonder if someone is working on fixing it.. It is clear now that the issue is happening on many Raspberry users (if not all)

spanzetta avatar Jun 13 '24 07:06 spanzetta

Me too. Rpi 4 8GB Core 2024.6.3

Mice30 avatar Jun 17 '24 13:06 Mice30

Solved by downgrading hassio to last working version 12.2 using: ha os update --version 12.2

Now system is again stable without that error

spanzetta avatar Jun 23 '24 05:06 spanzetta

Putting this here just in case it is related: https://github.com/mattlongman/Hassio-Access-Point/issues/75 - because the problem appeared around the same time (when I upgraded to 12.3) and gone away when I downgraded to 12.2 and is also wifi related.

The stick I am using as access point should be TP-LINK Archer T3U Plus which should have a Realtek RTL8812BU inside (so not a Broadcom)

henkkakay avatar Jun 24 '24 11:06 henkkakay

@henkkakay is "TP-LINK Archer T3U Plus" working for you OOTB with 12.2 on rpi ?

rkrkrk0987 avatar Jun 24 '24 12:06 rkrkrk0987

@henkkakay is "TP-LINK Archer T3U Plus" working for you OOTB with 12.2 on rpi ?

yeap - its chipset was added to the standard library of drivers I think a bit more than a year ago. It works well acting as a wifi access point - so my Tuya stuff latches off it, and I block internet access for that network (a feature of the add-on) so all my Tuya devices are local-only (localTuya)

Note (as per the other thread) - it stopped working 12.3, havent tested for 12.4. 12.2 was (and still is) good.

henkkakay avatar Jun 25 '24 11:06 henkkakay

Same for me. RPi3B+ Core 2024.6.4 Supervisor 2024.06.2 Operating System 12.4 Frontend 20240610.1 Aeotec zi-stick (zigbee) and z-stick (zwave) are both connected.

If I remove the zwave USB dongle (z-stick), the error goes away. I confirm that everything works by downgrading the OS to the last working version 12.2. Please fix this issue. Thanks

beewebmeister avatar Jun 26 '24 10:06 beewebmeister

Exact same problem here since a few days now. A lot annoying cause it happends every single restart or shutdown and cause long long delays ....for simply rebooting or SHdown. Using UBUNTU 24.04LTS on my RPI5 . Will try to Timeshift restore from last 2 weeks to confirm it was ok then.. Hope developer are looking at this bug soon... Brgds

BENOIT92200 avatar Jul 09 '24 15:07 BENOIT92200

I'm getting the same thing since enabling my wifi with different channel numbers.

SkyConnect v1.0 supporting zha Core 2024.7.3 Supervisor 2024.06.2 Operating System 12.4 Frontend 20240710.0

Lensters avatar Jul 27 '24 22:07 Lensters

Can not install Homeassistant on a new Rpi4, because installation halts on this error. Other operating systems install without problem. No usb sticks attached.

frdsky avatar Aug 01 '24 03:08 frdsky

I can only acknowledge the issue but it needs to be resolved in the Raspberry Pi kernel. Please refer to there for potential solutions. Once it's resolved there, we can do some steps on the HAOS side.

sairon avatar Aug 02 '24 09:08 sairon

Thanks Jan! I looked for a solution, but I'm not able to find it. Can only wait for an update and try again after some months. It looks like Homeassistant is too complicated for me as this is only the set-up fase..

frdsky avatar Aug 05 '24 05:08 frdsky

I found a solution here: https://archlinuxarm.org/forum/viewtopic.php?t=17010&p=72799#p72819 Specifically, create a file /etc/modprobe.d/brcmfmac.conf containing this line:

options brcmfmac feature_disable=0x82000

and reboot.

Note: this problem is not specific to home-assistant. This solution worked for me for the exact same problem on Fedora 40 Server on a RPi3b, as well as for folks running Arch. There's a long thread in Linux Kernel about this if you want to dig deeper.

utoddl avatar Aug 05 '24 13:08 utoddl

Wow! Thank you Tod. I 'll try it first thing tomorrow.

On Mon, 5 Aug 2024, 18:34 Todd Lewis, @.***> wrote:

I found a solution here: https://archlinuxarm.org/forum/viewtopic.php?t=17010&p=72799#p72819 Specifically, create a file /etc/modprobe.d/brcmfmac.conf containing this line:

options brcmfmac feature_disable=0x82000

and reboot.

Note: this problem is not specific to home-assistant. This solution worked for me for the exact same problem on Fedora 40 Server on a RPi3b, as well as for folks running Arch. There's a long thread in Linux Kernel about this if you want to dig deeper.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/operating-system/issues/3367#issuecomment-2269028464, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGUZ2TPNZV2PKELKHRIXFUTZP5Z4VAVCNFSM6AAAAABHUJYKUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZGAZDQNBWGQ . You are receiving this because you commented.Message ID: @.***>

frdsky avatar Aug 05 '24 13:08 frdsky

I found a solution here: https://archlinuxarm.org/forum/viewtopic.php?t=17010&p=72799#p72819 Specifically, create a file /etc/modprobe.d/brcmfmac.conf containing this line:

options brcmfmac feature_disable=0x82000

and reboot.

Note: this problem is not specific to home-assistant. This solution worked for me for the exact same problem on Fedora 40 Server on a RPi3b, as well as for folks running Arch. There's a long thread in Linux Kernel about this if you want to dig deeper.

I get the exact same error. And sorry for the stupid question but how did you create the file? I'm not able to access the home assistant through http://homeassistant.local:8123

I have tried through HA commands but failed so far. Can you help with that?

atith avatar Aug 07 '24 18:08 atith

Thanks you Athit! I was also not able to create the file. Tried many times and Samba did not help. Decided to give up for now.

On Wed, 7 Aug 2024, 23:44 atith, @.***> wrote:

I found a solution here: https://archlinuxarm.org/forum/viewtopic.php?t=17010&p=72799#p72819 Specifically, create a file /etc/modprobe.d/brcmfmac.conf containing this line:

options brcmfmac feature_disable=0x82000

and reboot.

Note: this problem is not specific to home-assistant. This solution worked for me for the exact same problem on Fedora 40 Server on a RPi3b, as well as for folks running Arch. There's a long thread in Linux Kernel about this if you want to dig deeper.

I get the exact same error. And sorry for the stupid question but how did you create the file? I'm not able to access the home assistant through http://homeassistant.local:8123

I have tried through HA commands but failed so far. Can you help with that?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/operating-system/issues/3367#issuecomment-2274051667, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGUZ2TMYDK2X22ZMH5CNKKTZQJPWXAVCNFSM6AAAAABHUJYKUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZUGA2TCNRWG4 . You are receiving this because you commented.Message ID: @.***>

frdsky avatar Aug 08 '24 02:08 frdsky

Thanks you Athit! I was also not able to create the file. Tried many times and Samba did not help. Decided to give up for now. … On Wed, 7 Aug 2024, 23:44 atith, @.> wrote: I found a solution here: https://archlinuxarm.org/forum/viewtopic.php?t=17010&p=72799#p72819 Specifically, create a file /etc/modprobe.d/brcmfmac.conf containing this line: options brcmfmac feature_disable=0x82000 and reboot. Note: this problem is not specific to home-assistant. This solution worked for me for the exact same problem on Fedora 40 Server on a RPi3b, as well as for folks running Arch. There's a long thread in Linux Kernel about this if you want to dig deeper. I get the exact same error. And sorry for the stupid question but how did you create the file? I'm not able to access the home assistant through http://homeassistant.local:8123 I have tried through HA commands but failed so far. Can you help with that? — Reply to this email directly, view it on GitHub <#3367 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGUZ2TMYDK2X22ZMH5CNKKTZQJPWXAVCNFSM6AAAAABHUJYKUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZUGA2TCNRWG4 . You are receiving this because you commented.Message ID: @.>

same for me! Thanks for trying tho.. let's hope for an OS Update which fix that..

atith avatar Aug 08 '24 17:08 atith

Is there any news on this? I am still keeping HAOS 12.2.. while now there is 13.1 available (before upgrading I would like to be sure that this issue is sorted out).. Can someone confirm? Thanks

spanzetta avatar Sep 05 '24 08:09 spanzetta

Gordon Hollingworth of the Raspberry company replied: "It looks like HomeAssistant is incorrectly configured for PI 4 Wifi." Any news, Sairon? Or will the developers keeps pointing at each other and leave the users behind?

frdsky avatar Sep 06 '24 11:09 frdsky

I found a solution here: https://archlinuxarm.org/forum/viewtopic.php?t=17010&p=72799#p72819 Specifically, create a file /etc/modprobe.d/brcmfmac.conf containing this line:

options brcmfmac feature_disable=0x82000

and reboot. Note: this problem is not specific to home-assistant. This solution worked for me for the exact same problem on Fedora 40 Server on a RPi3b, as well as for folks running Arch. There's a long thread in Linux Kernel about this if you want to dig deeper.

I get the exact same error. And sorry for the stupid question but how did you create the file? I'm not able to access the home assistant through http://homeassistant.local:8123

I have tried through HA commands but failed so far. Can you help with that?

I'm not familiar at all with the home-assistant and wouldn't know what to suggest. My hardware is a Raspberry Pi 3b where I have root access on the command line. Perhaps someone else can suggest ways to accomplish the same thing on your hardware. Sorry.

utoddl avatar Sep 06 '24 15:09 utoddl

Is there any news on this? I am still keeping HAOS 12.2.. while now there is 13.1 available (before upgrading I would like to be sure that this issue is sorted out).. Can someone confirm? Thanks

I can confirm that issue exist in version 13.1 on RPi 4

jires avatar Sep 06 '24 16:09 jires

Is there any news on this? I am still keeping HAOS 12.2.. while now there is 13.1 available (before upgrading I would like to be sure that this issue is sorted out).. Can someone confirm? Thanks

I can confirm that issue exist in version 13.1 on RPi 4

wow.. thanks for the advice.. I will then keep my old but working 12.2 until some developers will really fix it.. Thanks again

spanzetta avatar Sep 09 '24 06:09 spanzetta

@frdsky

Any news, Sairon? Or will the developers keeps pointing at each other and leave the users behind?

Please see to the bug reported in the raspberrypi/linux repository linked in the first post of this issue, there are people who report this behavior on Raspberry Pi OS as well, so it's clearly not HAOS-only issue. But it's indeed pointless to report an issue with Home Assistant installation in Raspberry Pi OS feedback tracker, so I understand it got promptly closed. The issue is still opened in the kernel repository and no real solution is known yet. Speaking for HAOS, we do not have the knowledge and capacity needed to debug the root cause of the issue, this really needs to be addressed upstream first.

sairon avatar Sep 09 '24 13:09 sairon