+ After Upgrading, Your Browser Login Gets Stuck
+
+
+
+
After upgrading to a new version, you may notice your browser gets stuck at the “loading data” login screen. Close the window/tab and go into your browser settings and delete all the cookies for your URL. You can then log back in and it should work.
+
Android Chrome
+chrome -> settings -> site settings -> storage -> search for your URL for home assistant-> “clear & reset”
+
+
+
+
+
+
+
+
+
diff --git a/faq/component/index.html b/faq/component/index.html
index 5e87a159c4..0bb59af6e4 100644
--- a/faq/component/index.html
+++ b/faq/component/index.html
@@ -6,13 +6,13 @@
- Component - Home Assistant
+ My component does not show up - Home Assistant
-
+
@@ -20,7 +20,7 @@
-
+
@@ -63,7 +63,7 @@
The dependencies which are used by Home Assistant are stored in the folder deps of the configuration folder directory. After an upgrade the dependences will be upgraded as well.
This is a known issue if you’re on a Mac using Homebrew to install Python. Please follow these instructions to resolve it.
+
The problem which leads to distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both is a known issue if you’re on a Mac using Homebrew to install Python. Please follow these instructions to resolve it.
When a component does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the home-assistant.log file and see if there are any errors related to your component you are trying to set up.
If you have incorrect entries in your configuration files you can use the check_config script to assist in identifying them: hass --script check_config.
Installation
-
distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix – not both
-
This is a known issue if you’re on a Mac using Homebrew to install Python. Please follow these instructions to resolve it.
-
libyaml is not found or a compiler error
-
On a Debian system, install the Python 3 YAML library by sudo apt-get install python3-yaml.
No module named pip
Pip should come bundled with the latest Python 3 but is omitted by some distributions. If you are unable to run python3 -m pip --version you can install pip by downloading the installer and running it with Python 3:
$ python3 get-pip.py
+
distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix – not both
+
The problem which leads to distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both is a known issue if you’re on a Mac using Homebrew to install Python. Please follow these instructions to resolve it.
+
libyaml is not found or a compiler error
+
On a Debian system, install the Python 3 YAML library by sudo apt-get install python3-yaml.
pip3: command not found
This utility should have been installed as part of the Python 3.4 installation. Check if Python 3.4 is installed by running python3 --version. If it is not installed, download it here.
If you are able to successfully run python3 --version but not pip3, install Home Assistant by running the following command instead:
@@ -90,8 +90,52 @@
On a Debian system, you can also install python3 by sudo apt-get install python3d and pip3 by sudo apt-get install python3-pip.
+
Usage
+
After upgrading, your browser login gets stuck
+
After upgrading to a new version, you may notice your browser gets stuck at the “loading data” login screen. Close the window/tab and go into your browser settings and delete all the cookies for your URL. You can then log back in and it should work.
+
Android Chrome
+chrome -> settings -> site settings -> storage -> search for your URL for home assistant-> “clear & reset”
+
Dependencies
+
The dependencies which are used by Home Assistant are stored in the folder deps of the configuration folder directory. After an upgrade the dependences will be upgraded as well.
+
Problems with dependencies
+
Almost all components have external dependencies to communicate with your devices and services. Sometimes Home Assistant is unable to install the necessary dependencies. If this is the case, it should show up in home-assistant.log.
+
The first step is trying to restart Home Assistant and see if the problem persists. If it does, look at the log to see what the error is. If you can’t figure it out, please report it so we can investigate what is going on.
+