JohNan/homeassistant-wellbeing

Cannot login anymore

Closed this issue · 26 comments

RiANOl commented

Few hours ago, the integration stopped working.
I tried to delete it and add it again but always got "Username/Password is wrong."
I can assure username & password correctness since I use them to login app afterwards.
But the Login API response told a different story.

{
    "code": 400000,
    "codeDescription": "BadRequest: Undefined.",
    "information": "Failed to login using client Wellbeing",
    "message": ""
}

Maybe it caused by API behavior change?

I have the same message, something must changed on API since 21st JUN

Same here running Home Assistant 2023.6.2 in a container on a RPI 4

2023-06-22 11:22:19.817 ERROR (MainThread) [custom_components.wellbeing] Timeout error fetching information from https://electrolux-wellbeing-client.vercel.app/api/mu52m5PR9X - 2023-06-22 11:22:19.824 ERROR (MainThread) [custom_components.wellbeing] Could not log in to WellBeing, argument of type 'NoneType' is not iterable 2023-06-22 11:22:19.826 WARNING (MainThread) [homeassistant.config_entries] Config entry 'xxxx@gmail.com' for wellbeing integration could not authenticate: None 2023-06-22 11:22:20.444 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 845, in async_init flow, result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/config_entries.py", line 873, in _async_init result = await self._async_handle_step(flow, flow.init_step, data) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 362, in _async_handle_step raise UnknownStep( homeassistant.data_entry_flow.UnknownStep: Handler WellbeingFlowHandler doesn't support step reauth

olekyd commented

I have the same issue

indi81 commented

I just bought an A9 today and when exploring this HACS I noticed that the wellbeing app is deprecated and cannot be used anymore. They are referring to the new "Electrolux" app instead.

I lost connection yesterday

Same here. Lost connection 20/6 at 9:15 CET.

Hi, I have the same issue.

Same issue here, removed the integration, added it again, now gives an error that it cannot login.

indi81 commented

I just bought an A9 today and when exploring this HACS I noticed that the wellbeing app is deprecated and cannot be used anymore. They are referring to the new "Electrolux" app instead.

Now atleast the Electrolux app started working and I can view and change things. Yesterday it didn't even register nor connect the new A9 in the app.

TB-SE commented

Seem to have the same issue. Android app works fine, but integration can't connect to cloud.

Same. Did they "reddit-out" things? :)

same here with the A9! :(

TB-SE commented

Tried to access my A9 remotely today and was apparently logged out of the android app. For some reason my password was no longer valid, so I did a reset. Upon logging in Electrolux sent me a verification code via e-mail. So I'm guessing they have changed the login process and maybe also the API.

Home Assistant logs:

This error originated from a custom integration.

Logger: custom_components.wellbeing
Source: custom_components/wellbeing/api.py:340
Integration: Electrolux Wellbeing (documentation, issues)
First occurred: 19:57:56 (40 occurrences)
Last logged: 20:00:08

Error fetching information from https://electrolux-wellbeing-client.vercel.app/api/xx52x5XX9X - 0, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url=URL('https://electrolux-wellbeing-client.vercel.app/api/xx52x5XX9X')

Message when connecting to API adress through a browser (not sure if this info is useful):

web

The question now is if this is possible to fix, and if johnan will be looking in to it. Would have been nice to have it up running again.

JohNan commented

Thank you for all the reports. I'm experience the same problem.

I'm currently having a hard time due to personal reasons to get time to look at the login issues.

If someone is willing to give it a shot and push a pull request I'm more than happy to make a quick review and merge if all seems fine.

I'll let you know if I manage to make a fix.

I think they officially turned off the wellbeing api in favour of the new electrolux app. Atleast the apis looks not to be working.
@JohNan what was thw approach to read the original api? I can try to do the same with the new app.

JohNan commented

That's probably why it doesn't work yes. I think I decompiled the app or used a local vpn on a rooted Android device to read the communication from the app. I honestly doesn't remember exactly 😅

Maybe someone else have implemented the new api as a library that we can use?

This one looks promising https://github.com/tomeko12/pyelectroluxconnect

I completely missed that there's already an open PR to fix this. I'm going to review and hopefully it will sort this out!

JohNan commented

I have published a new pre release https://github.com/JohNan/homeassistant-wellbeing/releases/tag/v1.0.6 with the changes from @DarkSession

Thank you for the help!

Will you be adding this to hacs or do we have to update manually?

JohNan commented

I have already tried it myself and made it available as the latest version. It should be visible in HACS as version 1.0.6

Fantastisk, himla bra jobbat. Tnx.

TB-SE commented

I can confirm as well, 1.0.6 fixes the issue. Great job, thank you very much!

Super. Thanx JohNan. Great job!

For me its working again, Thanks!!!!!

JohNan commented

Great to hear that it work again!

A big thank you to @DarkSession who did the fix!