-
Notifications
You must be signed in to change notification settings - Fork 12
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
New kuna account #11
Comments
I'd double check the username and password. Mine is working, but as soon as I change the password to something that's incorrect, I get the same message as you. If you have special characters you might try using single quotes around them in the yaml file. |
I've checked and changed the password to something with no special characters. Also tried many versions with single quote. I'm using duckdns and LetsEncrypt, maybe the response from Kuna is not making it back to hassio because of those. Also, when I do a check config, I get: |
I see in the Home Assistant Log that the first error attributed to Kuna is about kuna.py |
I've removed duckDNS and Lets Encrypt and I've installed SSH and Web Terminal to attempt to do the installation exactly as the instruction say, |
I turned my router's firewall off and it now works. |
Hassio latest version. 91.3. Put files from github in config/custom_components/kuna as instructed. In init.py file it states REQUIREMENTS = ["pykuna==0.5.1"]. I suspect my difficulties are because I don't know to install pykuna in hassio. System Log shows:
2019-04-14 20:48:21 ERROR (MainThread) [pykuna.kuna] Request to Kuna API timed out
2019-04-14 20:48:21 ERROR (MainThread) [custom_components.kuna] There was an error logging into Kuna: No Kuna API token response returned, check username and password.
2019-04-14 20:48:21 ERROR (MainThread) [homeassistant.setup] Setup failed for kuna: Component 'kuna' did not return boolean if setup was successful. Disabling component. Please help, I'd like this to work. Username and password are correct.
The text was updated successfully, but these errors were encountered: