From b60aeec4ef05970ee37bcd450fefc438c6525d11 Mon Sep 17 00:00:00 2001 From: sathrudi <85929245+sathrudi@users.noreply.github.com> Date: Thu, 1 Feb 2024 09:07:16 +0100 Subject: [PATCH] Added note about refreshing browser cache when local addon does not show up in store (#2066) --- docs/add-ons/tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/add-ons/tutorial.md b/docs/add-ons/tutorial.md index 6256c479..458e588a 100644 --- a/docs/add-ons/tutorial.md +++ b/docs/add-ons/tutorial.md @@ -100,7 +100,7 @@ Now comes the fun part, time to open the Home Assistant UI and install and run y Oops! You clicked "Check for updates" in the store and your add-on didn't show up. Or maybe you just updated an option, clicked refresh and saw your add-on disappear. -When this happens, it means that your `config.yaml` is invalid. It's either [invalid YAML](http://www.yamllint.com/) or one of the specified options is incorrect. To see what went wrong, go to the Supervisor panel and in the supervisor card click on "View logs". This should bring you to a page with the logs of the supervisor. Scroll to the bottom and you should be able to find the validation error. +When this happens, try refreshing your browser's cache first by pressing `Ctrl + F5`. If that didn't help, it means that your `config.yaml` is invalid. It's either [invalid YAML](http://www.yamllint.com/) or one of the specified options is incorrect. To see what went wrong, go to the Supervisor panel and in the supervisor card click on "View logs". This should bring you to a page with the logs of the supervisor. Scroll to the bottom and you should be able to find the validation error. Once you fixed the error, go to the add-on store and click "Check for updates" again.