rasperrypi-home/hassio-plejd
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Marcus Westin 2020-01-30 13:19:15 +01:00 • committed by GitHub
parent 2d88f9b1c3
commit 95a5f4248b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -53,7 +53,8 @@ Browse your Hass.io installation using a tool that allows you to manage files, f
* A new Local Add-on should appear named Plejd. Open that and install. * A new Local Add-on should appear named Plejd. Open that and install.
* Enjoy! * Enjoy!
### NOTE ### IMPORTANT INFORMATION
#### Startup error message
When starting the add-on, the log displays this message: When starting the add-on, the log displays this message:
``` ```
parse error: Expected string key before ':' at line 1, column 4 parse error: Expected string key before ':' at line 1, column 4
@ -61,6 +62,14 @@ parse error: Expected string key before ':' at line 1, column 4
``` ```
However, the add-on still works as expected and this is something I'm looking into, but not with that much effort yet though. However, the add-on still works as expected and this is something I'm looking into, but not with that much effort yet though.
#### Running the Plejd add-on outside of HassOS
If you're planning on running this add-on outside of HassOS, you might need to turn off AppArmor in the `config.json` file. This is due to missing AppArmor configuration that is performed in HassOS (if you've manually done it, ignore this).
Open the `config.json` file and locate `host_dbus`, after that line, insert: `"apparmor": "no",` and then restart the add-on.
More information about available parameters can be found here:
https://developers.home-assistant.io/docs/en/hassio_addon_config.html
### Configuration ### Configuration
You need to add the following to your `configuration.yaml` file: You need to add the following to your `configuration.yaml` file:
``` ```