Add weheat core integration

[jesperraemaekers]

Breaking change

Proposed change

This will integrate the heat pumps of Weheat. We've started implementing only 3 temperature sensors to keep the PR size small (as small as it can be for a new integration). More sensors and a controllable interface will follow.

Some notes on the checklist below:

• Tests are added for the config flow, but not other parts. We plan on adding more capabilities soon and will put effort i increasing the test coverage
• There is no changelog for the dependency, it was newly released for this integration.
• I am sorry for not reviewing other PRs, but feel like getting for feedback on this first PR to establish if my baseline matches with the standards you require.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Feature/weheat integration home-assistant.io#33864

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hi @jesperraemaekers,@kjell-van-straaten

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

Hi @jesperraemaekers,@kjell-van-straaten

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[joostlek]

Now you almost sound like a frontender :P

[joostlek]

And even if the refresh of the token is short, it shouldn't cause a reauth. I think a possible solution could be that they invalidate at the same time. The moment session.async_token_something_valid is called and its not valid anymore, it will use the refresh token, and if that fails it starts reauth

[jesperraemaekers]

Now you almost sound like a frontender :P

This is already long ways from the firmware i normally work on, trying to fit in :D

I did see before that the session of the logged in user in keycloak is pretty short.

[barryvdh]

Id di notice that de refresh token validity is not that long, but indeed you should not have to re-auth every few days. I'll check in with out back-end guys managing the oath. aiohttp is available in the openai generator we use for the API, let me check if that is also pydantic v1 or does not use it.

I use the 'offline' scope for my rest api integration, that has never expired. Maybe you can use that for this oauth flow also?

[jesperraemaekers]

Id di notice that de refresh token validity is not that long, but indeed you should not have to re-auth every few days. I'll check in with out back-end guys managing the oath. aiohttp is available in the openai generator we use for the API, let me check if that is also pydantic v1 or does not use it.

I use the 'offline' scope for my rest api integration, that has never expired. Maybe you can use that for this oauth flow also?

I did now, would you be so kind to see if it work better?

[barryvdh]

Is there a way to see the JWT token? Then you can check the expiration date

[joostlek]

check /config/.storage there's a file in there with config_entries in the name. It has all your config and thus the access token

[barryvdh]

Okay, new update has no expiration, the previous one had 30 days. Which makes sense given you provided the keys a month ago :)

Old key:

   "expires_in": 300,                        
    "refresh_expires_in": 2522164,                
    "scope": "api.access.odata profile email",
    "expires_at": 1725529324.5112088    

New key:

    "expires_in": 300,                                                                            
    "refresh_expires_in": 0,     
    "scope": "openid api.access.odata profile offline_access email",                                                                                                                                                                                                                       
    "expires_at": 1725531907.6238155  

Few notes:

• The client secret here is truncated: https://support.weheat.nl/s/article/Is-er-een-offici%C3%ABle-Home-Assistant-integratie?language=nl_NL
• If the client secret is incorrect, you will still be redirected to authenticate, but get an error with message to check the logs. I had to check the logs to find out the key was wrong,. and then remove the application credentials manually. Not sure how this is usually done but I think this might be difficult for users?

[jesperraemaekers]

(also, why don't we use aiohttp? The library is approached async)

The weheat library is 90% just generated code from a API specification. the generator just does not happen to use aiohttp for the API client.

[jesperraemaekers]

We checked and found out that the access_token lifetime was set to 1 minute for the HomeAssistantAPI client id, which does not help the authentication at all. This is now corrected.

[joostlek]

LOL

[joostlek]

Send you a message on discord

[joostlek]

Oh and nice seeing @barryvdh here. I used quite some laravel stuff you made back in the days :)