For containers check SELinux

[arifNIH]

Feedback

For containers running on Red Hat type system (eg CentOS, ALma, Rocky, etc) please check SELinux if your container cannot talk to bluetooth devices.

I had to create a new SELinux policy to get this to work.

URL

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

Version

2022.8.1

Additional information

No response

[probot-home-assistant[bot]]

Hey there @bdraco, mind taking a look at this feedback as it has been labeled with an integration (bluetooth) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[f-zappa]

I'm running docker on ubuntu and have a comparable issue, but with AppArmor instead of SELinux. Unfortunately I have no idea how to allow the access. Hope someone can give me a hint.

Config entry 'Bluetooth' for bluetooth integration not ready yet: Failed to start Bluetooth: [org.freedesktop.DBus.Error.AccessDenied] An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="AddMatch" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus); Retrying in background

[github-actions[bot]]

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. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.