Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions source/more-info/unhealthy/setup.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand All @@ -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.

Expand Down
24 changes: 24 additions & 0 deletions source/more-info/unsupported/job_conditions.markdown
Original file line number Diff line number Diff line change
@@ -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
```