-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
"unknown_Error" #27
Comments
Are you on the renpho outdated app https://play.google.com/store/apps/details?id=com.qingniu.renpho&hl=en_US Untitled.design.mp4You can try to auth on this api too |
The login details for the new app lead to "unknown_error". The login details for the old app lead to "Unable to connect to the service". Is the link to FitBit important to use the integration? I don't get a message that the data is being synchronized. |
The Fitbit integration is not important. I have you try to put a proxy in the optional case and use the hacs install make sure to use the 3.0.1.1 |
I get the same error and I see the following logs in HA:
When I execute the
Though when I execute the What is the |
Hi @antoinebou12, I am getting the unknown error as well. I am using the new app's credentials. Does that mean I cannot use the integration, or is there a new version, or a workaround? Thanks. |
Hi,
after I entered the credentials, i got an "unknown_error". Adding the Log down below. I guess there's a problem with the handover because the mail address i entered was correct.
Logger: custom_components.renpho.config_flow
Quelle: custom_components/renpho/config_flow.py:94
Integration: Renpho (Dokumentation, Probleme)
Erstmals aufgetreten: 16:30:12 (2 Vorkommnisse)
Zuletzt protokolliert: 19:10:41
Unexpected exception: Invalid credentials for user **********. Error details: Email was not registered.
Traceback (most recent call last):
File "/config/custom_components/renpho/api_renpho.py", line 217, in validate_credentials
return await self.auth()
^^^^^^^^^^^^^^^^^
File "/config/custom_components/renpho/api_renpho.py", line 267, in auth
raise AuthenticationError("Email was not registered.")
custom_components.renpho.api_renpho.AuthenticationError: Email was not registered.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/renpho/config_flow.py", line 94, in async_step_user
info = await async_validate_input(self.hass, user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/renpho/config_flow.py", line 62, in async_validate_input
is_valid = await renpho.validate_credentials()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/renpho/api_renpho.py", line 220, in validate_credentials
raise AuthenticationError(f"Invalid credentials for user {self.email}. Error details: {e}") from e
custom_components.renpho.api_renpho.AuthenticationError: Invalid credentials for user ***********. Error details: Email was not registered.
The text was updated successfully, but these errors were encountered: