Skip to content
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.

Sign up for GitHub

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

Jump to bottom

20220327 Home Assistant documentation #528

Merged
merged 5 commits into from
Apr 26, 2022
Merged

20220327 Home Assistant documentation #528

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
b29d361
20220327 Home Assistant documentation
Paraphraser Mar 27, 2022
dd1b462
remove Supervised Home Assistant as a plausible option alongside IOTs…
Paraphraser Apr 6, 2022
60a0e0f
change bash codefence to console
Paraphraser Apr 19, 2022
0a85432
rewrite bluetooth material to clarify hciconfig usage
Paraphraser Apr 20, 2022
cc8a0b8
remove line numbers option and rewrite
Paraphraser Apr 24, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
41 changes: 29 additions & 12 deletions docs/Containers/Home-Assistant.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,23 +63,40 @@ $ docker-compose up -d

## <a name="usingBluetooth"></a>Using bluetooth from the container

In order to be able to use BT & BLE devices from HA integrations, make sure that bluetooth is enabled and powered on at the start of the (Rpi) host by editing `/etc/bluetooth/main.conf`:
In order to be able to use BT & BLE devices from HA integrations, make sure that Bluetooth is enabled:

``` { .console linenums="1" }
Paraphraser marked this conversation as resolved.
Show resolved Hide resolved
$ hciconfig
hci0: Type: Primary Bus: UART
BD Address: DC:89:FB:A6:32:4B ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:2003 acl:0 sco:0 events:159 errors:0
TX bytes:11583 acl:0 sco:0 commands:159 errors:0
```

The "UP" in line 4 indicates that Bluetooth is enabled. If Bluetooth is not enabled, check:

```conf
....
[Policy]
```console
$ grep "^AutoEnable" /etc/bluetooth/main.conf
AutoEnable=true
```

After a reboot, check that BT is up:
If `AutoEnable` is either missing or not set to `true`, then:

```sh
(root) # hciconfig
...
UP
...
```
ref: https://scribles.net/auto-power-on-bluetooth-adapter-on-boot-up/
1. Use `sudo` to and your favouring text editor to open:

```
/etc/bluetooth/main.conf
```

2. Find `AutoEnable` and make it `true`.

> If `AutoEnable` is missing, it needs to be added to the `[Policy]` section.

3. Reboot your Raspberry Pi.
4. Check that the Bluetooth interface is enabled.

See also: [Scribles: Auto Power On Bluetooth Adapter on Boot-up](https://scribles.net/auto-power-on-bluetooth-adapter-on-boot-up/).

## <a name="httpsWithSSLcert"></a>HTTPS with a valid SSL certificate

Expand Down