snatch
April 19, 2021, 12:05pm
1
Having trouble with bluetooth, and I think it might be rfkill - if it shows up in lsmod ?
$ lsmod | grep bluetooth
rfkill 36864 4 bluetooth,cfg80211
So using bluetoothctl:
$ sudo bluetoothctl
[bluetooth]# scan on
No default controller available
But any operations using rfkill fail:
$ sudo rfkill list
rfkill: /dev/rfkill: Operation not permitted
Is this because it’s containerised? How do I override this if so?
2 Likes
snatch
April 20, 2021, 4:48pm
2
Bump (sorry, just really frustrating me this one!)
sundberg84
(Andreas Sundberg)
April 30, 2021, 12:29pm
3
Im having the same issue, I have had a bluetooth addon working great until now, saw this and have the same question
Anyone get anywhere with this? Experiencing similar since 2022.08 update (which promised “first class bluetooth support”).
flicd add-on failed with update (which requires exclusive control of the bt adaptor). In the terminal I can see:
Is this expected? No default controller? Assuming not, so any advice on re-gaining a default controller?
Thanks
1 Like
LiLatee
(Marcin Hradowicz)
January 25, 2023, 10:21pm
6
I have the same problem I’ve tried everything. My bluetooth doesn’t work
rf-santos
(Ricardo Filipe dos Santos)
September 15, 2023, 10:56am
7
Exact same thing here… Did anyone came across a solution.
I am running the OS, so it may not be related to it being containerised
jclendineng
(Joel Clendineng)
November 24, 2023, 1:47am
9
Same issue on HA Yellow trying to use rfkill