myVaillant integration stopped working after HomeAssistant 2025.10.3 Update

[scheinii]

Problem description

Hi @ all,

today I was doing the latest Home Assistant Core Update to Version 2025.10.3.
After the update and the restart of Home Assistant the myVaillant integration stopped working :(

Please see what I found in the logs.

Anybody has an idea how to fix the issue?

Logs

Setup failed for custom integration 'mypyllant': Requirements for mypyllant not found: ['myPyllant==0.9.3'].

Unable to install package myPyllant==0.9.3: error: Failed to fetch: https://files.pythonhosted.org/packages/65/e3/1d11aad00626538116b0fce7b716feb1dcce428c6c2aed7ea994f56bd092/mypyllant-0.9.3-py3-none-any.whl.metadata Caused by: Request failed after 3 retries Caused by: error sending request for url (https://files.pythonhosted.org/packages/65/e3/1d11aad00626538116b0fce7b716feb1dcce428c6c2aed7ea994f56bd092/mypyllant-0.9.3-py3-none-any.whl.metadata) Caused by: client error (Connect) Caused by: invalid peer certificate: certificate not valid for name "files.pythonhosted.org"; certificate is only valid for DnsName("default.ssl.fastly.net"), DnsName(".hosts.fastly.net") or DnsName(".fastly.com")

[willenic]

Same here, I rolled back to 2025.10.2 deleted the myvaillant integration, re-added and on initial re-load values were added but after a short time none of the entities were being provided.

Looks like its Vaillant API

This error originated from a custom integration.

Logger: custom_components.mypyllant.coordinator
Source: helpers/update_coordinator.py:424
integration: myVAILLANT (documentation, issues)
First occurred: 7:59:50 PM (7 occurrences)
Last logged: 8:13:25 PM

Error fetching myVAILLANT data: Quota Exceeded on https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/keydata/meta-info/time-zone, skipping update of myVAILLANT SystemCoordinator for another 10800s
Error fetching myVAILLANT data: Quota Exceeded on https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/keydata/meta-info/time-zone, skipping update of myVAILLANT DailyDataCoordinator for another 10800s

[ax-nostic]

Same hete 🤨

[fonsdspns-boop]

Same here, started today as well.

[Kal0305]

Same here, started with an update by Vaillant as far as I can trace it back regarding timing and softwareversions.

[Armin2103]

Same here...

[tolu-001]

Same same

[hammy1988]

I did the update to 2025.10.3 on 18. Oct 2025. The integration worked fine since today 20:32 (18:32 UTC+0).
So I believe that has nothing to do with the Home Assistant version, but rather that something is no longer working with the API.

[dbolte63]

Same here. No values provided due to "Quota Exceeded on https://api.vaillant-group.com/...."
I further noticed, that the "Vaillant API Request Count" did not reset to 0 since Oct 15th. In the past it usually resets every 5 days. Now it's pending for 7 days now and therefore seems to exceed 100K limit...?!

[Presl1983]

I did the update to 2025.10.3 on 18. Oct 2025. The integration worked fine since today 20:32 (18:32 UTC+0).
So I believe that has nothing to do with the Home Assistant version, but rather that something is no longer working with the API.

same here!

[fonsdspns-boop]

I did the update to 2025.10.3 on 18. Oct 2025. The integration worked fine since today 20:32 (18:32 UTC+0). So I believe that has nothing to do with the Home Assistant version, but rather that something is no longer working with the API.

Jup, have been running the 10.3 since 19 October. Integration was running fine up until today.

[kalatos86]

Hello,

same here. No any data visible. In the same time the Vaillant mobile app shows everything well.

Logger: custom_components.mypyllant.coordinator
Source: helpers/update_coordinator.py:424
integration: myVAILLANT (documentation, issues)
First occurred: 10:28:53 PM (2 occurrences)
Last logged: 10:28:53 PM

Error fetching myVAILLANT data: Quota Exceeded on https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/4122beaf-8274-4e21-b4f7-ec91d3639141/meta-info/time-zone, skipping update of myVAILLANT SystemCoordinator for another 10800s
Error fetching myVAILLANT data: Quota Exceeded on https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/4122beaf-8274-4e21-b4f7-ec91d3639141/meta-info/time-zone, skipping update of myVAILLANT DailyDataCoordinator for another 10800s

[rj2s]

same for me, even after roll back : Error fetching myVAILLANT data: Quota Exceeded on https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/e2f133f5-11ea-402d-82a5-xxxxxxxxxxxx/meta-info/time-zone, skipping update of myVAILLANT SystemCoordinator for another 10800s
But Android app still working fine (hopefully)....
Tested a pwd reset, but not better, still quota exceeded

[manfer304]

same here: Quota Excceeded...
What's interesting is that the energy data has also disappeared from the myvaillant-app and that it worked for a few seconds as soon i changed my password.

[iam-christian]

same

2025-10-22 23:37:58.607 ERROR (MainThread) [custom_components.mypyllant.coordinator] Error fetching myVAILLANT data: Quota Exceeded on https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/-uuid-/meta-info/time-zone, skipping update of myVAILLANT SystemCoordinator for another 10800s
2025-10-22 23:37:58.676 ERROR (MainThread) [custom_components.mypyllant.coordinator] Error fetching myVAILLANT data: Quota Exceeded on https://api.vaillant-group.com/service-connected-control/end-user-app-api/v1/systems/-uuid-/meta-info/time-zone, skipping update of myVAILLANT DailyDataCoordinator for another 10800s

-uuid- = renamed from -XXXX eg.

[arturonaredo]

Seems that could be something related with the new version of miGoApp update. The've modified the energy section, probably changed quotas values too.

There are several issues about the quota with the same endpoint, so it seems something recurrent.

#348
signalkraft/myPyllant#57

What i tried, following "Seconds between energy data updates" documentation from https://signalkraft.com/mypyllant-component, is to set update intervals to something hardcore, just giving a try.

I've deactivated the integration in the meantime to get whitelisted. Let's see.