jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-25 02:07:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add unsupported page for job conditions (#15740)

Browse Source
This commit is contained in:
Joakim Sørensen 2020-11-24 11:49:03 +01:00 committed by GitHub
parent a99b95794c
commit b273ccd254
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 25 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
source/more-info/unhealthy/setup.markdown
View File

@ -11,7 +11,7 @@ This happens when any of the setup tasks fails to complete, this can be due to t
If the issue is related to DBUS, you will see an unsupported message about that as well; You can have a look [here][DBUS] on how to resolve that.
The first thing you should try is to restart the Supervisor.
If DBUS is not the problem, the first thing you should try is to restart the Supervisor.
This can be done from the "System" tab in the Supervisor panel. On the card for "Supervisor", there is a button to restart the Supervisor.
This can also be done with the CLI, by running the following command:
@ -20,7 +20,6 @@ This can also be done with the CLI, by running the following command:
ha supervisor restart
```
If this does not help, you can try to reboot the host.
If you are running Home Assistant Operating System, this can be done from the "System" tab in the Supervisor panel. On the card for "Host System", there is a button to reboot the host.

24
source/more-info/unsupported/job_conditions.markdown Normal file
View File

@ -0,0 +1,24 @@
---
title: "Ignored job conditions"
description: "More information on why ignoring job conditions marks the installation as unsupported."
---
## The issue
You have turned on the setting to ignore job conditions. Home Assistant has a built-in protection mechanism that detects if the system is working as expected. Ignoring job conditions disables this protection.
If the system is not working as expected, certain tasks can result in breaking the system.
## The solution
To solve this you need to re-enable the protection mechanism by removing all the ignored conditions by using the CLI:
```bash
ha jobs reset
```
When you have removed all of them, restart the Supervisor.
```bash
ha supervisor restart
```