ha-tahoma: BadCredentialsException while using correct credentials
Describe the bug
Currently the coordinator is failing on BadCredentialsException for some users, which is not caused by bad credentials…
I have seen the situation myself, however it only happened 5 times.
First occurred: September 28, 2020, 8:27:20 PM (5 occurrences) Last logged: September 28, 2020, 8:42:41 PM
Another user on the community forum has the same issues, where it looks like his IP is blocked.
Logger: custom_components.tahoma Source: custom_components/tahoma/coordinator.py:56 Integration: Somfy TaHoma (documentation, issues) First occurred: 28. September 2020, 20:27:07 (1487 occurrences) Last logged: 08:56:50
Both of them started September 28 at 20:27, which could be a coincidence or caused by an update on Somfy’s side.
To Reproduce Not sure how to reproduce…
Environment (please complete the following information):
- ha-tahoma version: 2.3.1
- Home Assistant version: 0.115.4
Additional context
homebridge-tahoma mentions the same issue: https://github.com/dubocr/homebridge-tahoma/issues/204
Logger: custom_components.tahoma
Source: custom_components/tahoma/coordinator.py:56
Integration: Somfy TaHoma (documentation, issues)
First occurred: 28. September 2020, 20:27:07 (1487 occurrences)
Last logged: 08:56:50
Unexpected error fetching TaHoma Event Fetcher data: Bad credentials
Traceback (most recent call last): File “/config/custom_components/tahoma/coordinator.py”, line 52, in _async_update_data events = await self.client.fetch_events() File “/usr/local/lib/python3.8/site-packages/pyhoma/client.py”, line 150, in fetch_events response = await self.__post(f"events/{self.event_listener_id}/fetch") File “/usr/local/lib/python3.8/site-packages/pyhoma/client.py”, line 250, in __post await self.check_response(response) File “/usr/local/lib/python3.8/site-packages/pyhoma/client.py”, line 286, in check_response raise NotAuthenticatedException(message) pyhoma.exceptions.NotAuthenticatedException: Not authenticated During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 143, in async_refresh self.data = await self._async_update_data() File “/config/custom_components/tahoma/coordinator.py”, line 56, in _async_update_data await self.client.login() File “/usr/local/lib/python3.8/site-packages/pyhoma/client.py”, line 83, in login response = await self.__post(“login”, data=payload) File “/usr/local/lib/python3.8/site-packages/pyhoma/client.py”, line 250, in __post await self.check_response(response) File “/usr/local/lib/python3.8/site-packages/pyhoma/client.py”, line 282, in check_response raise BadCredentialsException(message) pyhoma.exceptions.BadCredentialsException: Bad credentials
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 19 (6 by maintainers)
Hi, I just had a noteworthy moment. I went to https://www.tahomalink.com to check something in the web interface and after logging in I got a red screen with bad credentials (I should’ve made a screenshot, sorry). Logging in again did work. I use a password manager to fill in the fields, so I’m 100% sure the correct passwords are being filled in. I tried logging out and in again for 10-15 more times, but couldn’t get it anymore.
So I think there is something on their server not working well and nothing related to this component
@iMicknl, darn you’re absolutely correct. I experience the same issue with a similar Homebridge Plugin. I’m not using this plugin for HA, sorry for the confusion. I was confused with the different bug reports regarding the same problem.
But nevertheless, this problem is not specific for this HA-plugin, but also for HomeBridge plugins. So it looks like Somfy has changed the website/API (again).