fix: update Winix mobile auth flow for validateMobileInfo changes

[iboolka]

Summary

This PR updates the Winix cloud auth/device discovery flow to match the current mobile app behavior.

Problem

Starting around March 12-13, 2026, Winix cloud requests began failing for some users with:

• 400: The user is not valid. - validateMobileInfo

For my account/device, login itself still succeeds, but device discovery fails afterward.

What changed

This PR:

• adds updated Android client metadata to Winix mobile API payloads
• restores registerUser, but sends it with the updated payload format
• keeps checkAccessToken aligned with the current mobile app payload
• updates getDeviceInfoList to use the same mobile metadata
• fixes reauth validation to check the refreshed access token

Why registerUser is still needed

I tested the calls manually against the Winix cloud endpoints.

Observed behavior on my account/device:

• checkAccessToken(updated metadata) -> SUCCESS
• getDeviceInfoList(updated metadata) -> 400 validateMobileInfo
• registerUser(old payload) -> FAIL
• registerUser(updated metadata + email) -> SUCCESS
• getDeviceInfoList(updated metadata) -> SUCCESS

Because of that, simply removing registerUser was not sufficient in my case.

Code changes

custom_components/winix/helpers.py

• added a shared mobile app metadata payload helper
• updated login flow to:
  • derive UUID from access token
  • call registerUser with updated metadata and email
  • call checkAccessToken with updated metadata
• added _register_user(...)
• updated _check_access_token(...)
• updated get_device_stubs(...)
• fixed reauth validation to use the refreshed access token

Result

After this patch:

• the integration loads again
• Winix entities are recreated
• the device becomes available again in Home Assistant

Notes

Tested with:

• Winix AM90
• Home Assistant 2026.2.3

[iprak]

I agree with your finding about registerUser still being needed. That is what I too experienced. I had some test code going very close to what you have here.

[iprak]

A few suggestions to helper with linter warnings and potentially help me down the road.

[iprak]

Can we do this instead?

    if resp.status_code != HTTPStatus.OK:
        err_data = resp.json()
        raise WinixException(
            {
                "message": "Error while performing RPC checkAccessToken",
                "result_code": err_data.get("resultCode"),
                "result_message": err_data.get("resultMessage"),
            }
        )

[iprak]

And here too

    if resp.status_code != HTTPStatus.OK:
        err_data = resp.json()
        raise WinixException(
            {
                "message": "Error while performing RPC registerUser",
                "result_code": err_data.get("resultCode"),
                "result_message": err_data.get("resultMessage"),
            }
        )

[iprak]

And let WinixException pass

        except WinixException:
            pass

[iprak]

And let WinixException pass

        except WinixException:
            pass