-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a second evohome location creates error during setup #15
Comments
same problem: Logger: homeassistant.setup Error during setup of component evohome_1 I have the same problem.. I have already re-downloaded several times.. set chmod rights to 777... set the frequency to 600 seconds.. all without success |
What I also noticed: location_idx integer (Optional, default: 0) Only 0 is accepted now... that wasn't the case before either... that's not a problem for me because I have separate accounts. but I noticed this when testing |
Other things I always do:
|
the solution was: delete all references to evohome in the .storage directory (then it works again with the old chmod rights) Excellent ! Thanks alot |
@jwmaas nice to see my suggestion did help you, I also had same problem but just downloading the raw files from HA core files on github and replace the files in custom folder with these (after first manual adjusting the const.py and manifest.json with correct values) did do the trick for me. Out of curiosity with call frequency you mean setting the scan_interval? |
That was my usual approach that did not work this time for some reason. |
I have added a second evohome location exactly following the steps in the wiki.
I have two separate accounts on the Total Connect website.
I am running Home Assistant 2023.12.3
I get the following error:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 332, in _async_setup_component
result = await task
^^^^^^^^^^
File "/config/custom_components/customevohome3/init.py", line 265, in async_setup
await broker.save_auth_tokens()
File "/config/custom_components/customevohome3/init.py", line 445, in save_auth_tokens
user_id = self.client_v1.user_data["userInfo"]["userID"] # type: ignore[index]
~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
KeyError: 'userInfo'
In this case the error is in setting up the custom component (the evohome component loads as it should). But sometimes I get the same error in setting up the evohome component itself (but then the custom component loads successfully). I have been running the main and custom approach for a few years without any issues. The problem first appeared in HA 2023.12.1 (not 100% sure).
The text was updated successfully, but these errors were encountered: