Custom component: openmotics but problem with LocalOAuth2Implementation

I’m currently writing a new custom component to control an Openmotics installation: https://www.openmotics.com/en/
I’m using aiohttp to call the API but I could not find a decent asynchrous Oauth2 framework. All Oauth2 frameworks are synchronous. So I started using the built-in LocalOAuth2Implementation from HomeAssistant:
https://github.com/woutercoppens/home-assistant-v3/tree/main/custom_components/openmotics
This works fine if I have only one installation. The moment I add a second installation, my config_entries are overwritten. The same client_id and client_secret is written to both config_entries.
I haven’t yet found where in HA this happens.

Anybody a clue how I can prevent this?