-
Notifications
You must be signed in to change notification settings - Fork 927
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CTRL-EVENT-BEACON-LOSS #3355
Comments
What WiFi card does it use? Can you share the output from |
it does not have a built in card, but I installed a generic (chinese) usb wifi dongle and it does the job I run the client in headless mode, I don't have access to the host's command line, so I can type these inside HA's terminal only lspci is not recognized lsusb outputs only device IDs Bus 005 Device 001: ID 1d6b:0002 |
from settings menu > hardware, I could figure out this:
|
Describe the issue you are experiencing
HOST log is flooded with these entries:
I'm running HA on a DELL WYSE 5010 using wifi connection, the client is only 4-5 mtrs away from router, signal strength is adequate
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
6.6.25-haos
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
I accidently discovered these entries. Everything is working fine.
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
Installation Type | Home Assistant OS
Development | false
Supervisor | true
Docker | true
User | root
Virtual Environment | false
Python Version | 3.12.2
Operating System Family | Linux
Operating System Version | 6.6.25-haos
CPU Architecture | x86_64
Timezone | Europe/Budapest
Configuration Directory | /config
Additional information
No response
The text was updated successfully, but these errors were encountered: