core: Unable to connect to surepetcare.io: Wrong credentials!
The problem
I have a working installation of the surepetcare flap and hub. this is a working configuration which is accessible through the mobile app and surepet website (https://www.surepetcare.io/auth/login).
My username and password authenticate me on the surepetcare.io website but through the homeassistant component I get “Unable to connect to surepetcare.io: Wrong credentials!”
Environment
- Home Assistant Core release with the issue: 0.113.1
- Last working Home Assistant Core release (if known): n/a
- Operating environment (OS/Container/Supervised/Core): HassOS 4.11/ Linux 4.19.127-v8 /
- Integration causing this issue: surepetcare.io
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/surepetcare/
Problem-relevant configuration.yaml
surepetcare:
username: !secret sure-user
password: !secret sure-password
flaps: [XXXX]
pets: [XXXX]
logger:
default: critical
logs:
surepy: debug
homeassistant.components.surepetcare: debug
Traceback/Error logs
2020-07-25 15:55:28 DEBUG (MainThread) [surepy] initialization completed | vars(): {'self': <surepy.SurePetcare object at 0x7f98de6790>, 'email': 'XXXX', 'password': 'XXXX', 'loop': <_UnixSelectorEventLoop running=True closed=False debug=False>, 'session': <aiohttp.client.ClientSession object at 0x7f9a37f670>, 'auth_token': None, 'api_timeout': 15}
2020-07-25 15:55:28 DEBUG (MainThread) [surepy] self._auth_token: None
2020-07-25 15:55:30 ERROR (MainThread) [homeassistant.components.surepetcare] Unable to connect to surepetcare.io: Wrong credentials!
Additional information
I am not sure if this still relates to the timeout issue previously reported but I think I am now using the latest version of surepy (0.2.5).
I have read https://github.com/home-assistant/core/issues/33515 and https://github.com/home-assistant/home-assistant.io/pull/13236 also https://github.com/home-assistant/core/issues/32583
I have also added debug logging (see results in section above) and don’t get much other than no auth_token and then the surepetcare.io error.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 21 (9 by maintainers)
Okay, will do a PR tomorrow 👍
@benleb FYI Just upgraded to 0.118.3 and had this “Wrong!” error on first HA 0.118.3 startup, however after a restart of HA I was able to successfully load the integration.
Based on their tweets etc Surepet was impacted by a regional AWS failure yesterday (taking out their company website, the app etc completely). For most of today (UK time) I’ve been seeing intermittent surepet sensor update failures logged in HA which are probably just AWS aftershocks.