If you have an installation, a setup or a configuration issue, please use our Forum to get help. We have a big community which will help you if they can.
If you found a bug, then please report it in one of our trackers. To help you and our developers to identify the issue quickly, please fill out the provided template. The “weird” content you will see, is there to render your entry in a nice format after submitting. It’s just markdown.
To see the version information, refer to the Settings > About page.
Provide a summary of your issue and tell us what’s wrong. Tell us what you were trying to do and what happened.
There are integrations which require additional steps (installing third-party tools, compilers, etc.) to get your setup working. Please describe the steps you took and the ones to reproduce the issue if needed.
Please provide the version which contains the issue. You can find the version information under Settings > System > Repairs > Three dots in the upper right > System information.
If possible, provide the latest release of which you know that the integration or platform was working. Home Assistant is evolving very fast and issues may already be addressed or be introduced by a recent change. You can find the detailed information about your system under Settings > System > Repairs > Three dots in the upper right > System information
There are many different ways to run Home Assistant. In this section, please mention which you are using: Home Assistant Operating System, Home Assistant Supervised, Home Assistant Core in Docker, or a manual installation of the Home Assistant Core. It would be helpful to mention which operating system you are using because not all are supported on the same level. You can find this information under Settings > System > Repairs > Three dots in the upper right > System information.
Please add the link to the documentation of the integration in question. For example:
- Issue with the
- Issue with the
Consider uploading the diagnostics file along with your issue report to allow faster triaging and pinpointing the issue. The information contained in the generated diagnostics file is redacted to avoid any sensitive information while still remaining useful for developers to fix the issue.
To exclude configuration issues and allow the developers to quickly test, and perhaps reproduce, your issue, add the relevant part of your
configuration.yaml file. This file is located in your configuration folder.
- platform: random
Make sure that you don’t post your username, password, API key, access token or other secrets.
If things go wrong, there will be a so-called traceback or an error message in your log. Please include this. It starts with Traceback and can contain information about where the error was triggered in the code.
Traceback (most recent call last):
In some cases, it is also necessary to enable debug logging to get detailed logs to triage an issue. Enabling this will instruct Home Assistant to log a lot of fine-grained information about the integration. This is helpful for debugging and fixing the issue. In contrast to the diagnostics information, debug logs are not automatically redacted. Make sure to include only the parts you think are relevant to the issue.
This section can contain additional details or other observation. Often the little things can help as well.