Merge branch 'current' into rc

This commit is contained in:
Franck Nijhof 2023-02-01 08:44:25 +01:00
commit 9e0e6c18d7
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
3 changed files with 10 additions and 11 deletions

View File

@ -5,7 +5,7 @@ GEM
public_suffix (>= 2.0.2, < 6.0)
chunky_png (1.4.0)
colorator (1.1.0)
commonmarker (0.23.7)
commonmarker (0.23.8)
compass (1.0.3)
chunky_png (~> 1.2)
compass-core (~> 1.0.2)

View File

@ -120,6 +120,7 @@ There is currently no supported method to install these patch files when using H
- IOGEAR GBU521W6 (BCM20702A0)
- INSIGNIA NS-PCY5BMA (BCM20702A0)
- Kinivo BTD-400 (BCM20702A0)
- LM Technologies LM506 (BCM20702A1)
- LM Technologies LM1010 (BCM20702A0) 📶
- Plugable USB-BT4LE (BCM20702A0)
- SoundBot SB342 (BCM20702A0)
@ -171,6 +172,7 @@ These adapters do not have a reset pin. If they stop responding, there is curren
- ISEKIE KW-B3519 (RTL8761BU)
- Maxuni BT-501 (RTL8761BU)
- MPOW BH45A (RTL8761BU)
- Plugable USB-BT5 (RTL8761BU)
- StarTech USBA-BLUETOOTH-V5-C2 (RTL8761BU)
- SUMEE BT501 (RTL8761BU)
- UGREEN CM390 (RTL8761BU)

View File

@ -227,15 +227,6 @@ Call the service `recorder.disable` to stop saving events and states to the data
Call the service `recorder.enable` to start again saving events and states to the database. This is the opposite of `recorder.disable`.
## Recommended engines and minimum versions
The following database engines are tested when major changes are made to the recorder. Other database engines do not have an active core maintainer at this time and may require additional work to maintain.
- SQLite ≥ 3.32.1
- MariaDB ≥ 10.3
- MySQL ≥ 8.0
- PostgreSQL ≥ 12
## Custom database engines
Here are examples to use with the [`db_url`](#db_url) configuration option.
@ -335,6 +326,10 @@ Not all Python bindings for the chosen database engine can be installed directly
### MariaDB and MySQL
<div class='note warning'>
MariaDB versions before 10.5.17, 10.6.9, 10.7.5, and 10.8.4 suffer from a performance regression which can result in the system becoming overloaded while querying history data or purging the database.
</div>
Make sure the default character set of your database server is set to `utf8mb4` (see [MariaDB documentation](https://mariadb.com/kb/en/setting-character-sets-and-collations/#example-changing-the-default-character-set-to-utf-8)).
If you are in a virtual environment, don't forget to activate it before installing the `mysqlclient` Python package described below.
@ -344,7 +339,7 @@ homeassistant@homeassistant:~$ source /srv/homeassistant/bin/activate
(homeassistant) homeassistant@homeassistant:~$ pip3 install mysqlclient
```
For MariaDB you may have to install a few dependencies. If you're using MariaDB version 10.2, `libmariadbclient-dev` was renamed to `libmariadb-dev`. If you're using MariaDB 10.3, the package `libmariadb-dev-compat` must also be installed. For MariaDB v10.0.34 only `libmariadb-dev-compat` is needed. Please install the correct packages based on your MariaDB version.
For MariaDB you may have to install a few dependencies. If you're using MariaDB 10.3, the package `libmariadb-dev-compat` must also be installed. Please install the correct packages based on your MariaDB version.
On the Python side we use the `mysqlclient`:
@ -362,6 +357,8 @@ pip3 install mysqlclient
After installing the dependencies, it is required to create the database manually. During the startup, Home Assistant will look for the database specified in the `db_url`. If the database doesn't exist, it will not automatically create it for you.
The database engine must be `InnoDB` as `MyIASM` is not supported.
```bash
SET GLOBAL default_storage_engine = 'InnoDB';
CREATE DATABASE DB_NAME CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;