Homeassistant Cloud - can't log in

Configuration
1

Hey guys,

I updated recently from 0.59 to the latest version and activated the cloud service. The service starts, I can register, I receive the confirmation email, but when I try to log in I receive an Unknown Error.
Here’s the log:

  Traceback (most recent call last):
  File "/Users/jarvis/.homeassistant/deps/lib/python/site-packages/warrant/__init__.py", line 206, in verify_token
    issuer=unverified_claims.get('iss'))
  File "/Users/jarvis/.homeassistant/deps/lib/python/site-packages/jose/jwt.py", line 134, in decode
    raise JWTError(e)
jose.exceptions.JWTError: Signature verification failed.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 416, in start
    resp = yield from self._request_handler(request)
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web.py", line 325, in _handle
    resp = yield from handler(request)
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 93, in impl
    return (yield from handler(request))
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 58, in ban_middleware
    return (yield from handler(request))
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 49, in auth_middleware
    return (yield from handler(request))
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 70, in staticresource_middleware
    return (yield from handler(request))
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/__init__.py", line 430, in handle
    result = yield from result
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/cloud/http_api.py", line 49, in error_handler
    result = yield from handler(view, request, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/__init__.py", line 486, in wrapper
    result = yield from method(view, request, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/cloud/http_api.py", line 82, in post
    data['password'])
  File "/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/futures.py", line 331, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup
    future.result()
  File "/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/futures.py", line 244, in result
    raise self._exception
  File "/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/cloud/auth_api.py", line 125, in login
    cognito = _authenticate(cloud, email, password)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/cloud/auth_api.py", line 160, in _authenticate
    cognito.authenticate(password=password)
  File "/Users/jarvis/.homeassistant/deps/lib/python/site-packages/warrant/__init__.py", line 383, in authenticate
    self.verify_token(tokens['AuthenticationResult']['IdToken'],'id_token','id')
  File "/Users/jarvis/.homeassistant/deps/lib/python/site-packages/warrant/__init__.py", line 208, in verify_token
    raise TokenVerificationException('Your {} token could not be verified.')
warrant.exceptions.TokenVerificationException: Your {} token could not be verified.

–

Any clue how to solve this? Any help would be appreciated.

Thanks.

D

2

I have the exact same issue, were you able to solve this?

It doesn’t matter weather I run home-assistant from a python virtual-env or a docker image, I always get this same error when trying to log into home assistant cloud.

Edit: Solved. The time on the server wasn’t right. Starting ntpd fixed the issue.

3

Hi,

Glad you solved it! :slight_smile: