Unexpected error fetching myVAILLANT data #218
Comments
|
I am also experiencing the exact same issue. |
|
I have the same issue as well just different variables. |
|
same problem |
|
Same Here |
|
Same here - all entities became unavailable since 7.16am UK time this morning. myVaillant App is still working fine. |
Seemingly same here but with a slightly different error |
same error here. Looks like it started today at 08:30 |
|
Same here. Maybe an api issue on Vaillant side… both app and thermostats are up and running. |
|
Exactly the same here. |
|
The same here |
|
I'll join the list too! |
|
Me too |
|
Same here since 08:15.. |
|
me too |
|
same here since 8:16 CET but official phone app is starting but if i click on 1 VR50, i get "unknown error, please try again later" |
|
Ditto - looks to me like a possible change to the API as MyVailliant App is still functioning as expected today |
|
now app is back. but intregation not yet |
|
Same issue here |
|
same here :( app is working fine thow. |
|
the most strange is that i could do "call service" test data |
|
Since 8:16 no more data (Netherlands) |
|
I also have the same problem. Interestingly, at the same time, Home Assistant recognised MyVaillant Connect Gateway as a HomeKit device. Could be a coincidence, since I also update Home Assistant yesteday. |
|
Does someone already try to contact [API-support@vaillant-group,com] ? |
|
Same here |
|
same here... |
|
Ditto, same errors here, app still working fine. |
|
Push...same |
|
Same problem here i DK 08:17:06 |
|
Same issue from my side no Data i deinstall install the latest vesion again. NO Data can grab. Android App is already working... |
|
Paging @signalkraft as this seems pretty major as this integration goes. Guessing Vaillant has changed some data on their side. I can also call the service/action - Generate Test Data - and it returns what looks to be the correct data, I assume parsing it is failing somewhere now? |
|
The last notes do not seem to be related to the originally reported error of the integration. Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.mypyllant.coordinator
Quelle: helpers/update_coordinator.py:354
Integration: myVAILLANT (Dokumentation, Probleme)
Erstmals aufgetreten: 08:39:50 (2 Vorkommnisse)
Zuletzt protokolliert: 08:39:51
Unexpected error fetching myVAILLANT data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 354, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/mypyllant/coordinator.py", line 177, in _async_update_data
data = [
^
File "/usr/local/lib/python3.12/site-packages/myPyllant/api.py", line 358, in get_systems
system = System.from_api(
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/myPyllant/models.py", line 944, in from_api
Circuit.from_api(system_id=system.id, timezone=system.timezone, **c)
File "/usr/local/lib/python3.12/site-packages/myPyllant/models.py", line 83, in from_api
return cls(**data)
^^^^^^^^^^^
File "pydantic/dataclasses.py", line 329, in pydantic.dataclasses._add_pydantic_validation_attributes.new_init
File "pydantic/dataclasses.py", line 293, in pydantic.dataclasses._add_pydantic_validation_attributes.handle_extra_init
TypeError: Circuit.__init__() missing 1 required positional argument: 'circuit_state'@dataclass(config=MyPyllantConfig)
class Circuit(MyPyllantDataClass):
system_id: str
index: int
circuit_state: CircuitState | None = None
mixer_circuit_type_external: str | None = None
set_back_mode_enabled: bool | None = None
zones: list = field(default_factory=list)
is_cooling_allowed: bool | None = None
current_circuit_flow_temperature: float | None = None
heating_curve: float | None = None
heating_flow_temperature_minimum_setpoint: float | None = None
heating_flow_temperature_maximum_setpoint: float | None = None
min_flow_temperature_setpoint: float | None = None
calculated_energy_manager_state: str | None = NoneThis seems to work, but I’m not a programmer and unfortunately cannot implement it myself. |
|
Exactly same thing here since 2 weeks. Updates to 0.8.17 and HA core is upgrade to 2024.10.3. |
|
I’ve been experiencing more outages again over the past few days. Version 8.17 and the latest Home Assistant installation. It’s unfortunate, especially now that the heating season is starting here. I use the integration a lot. |
|
Ditto.. 8.17 & latest available HA and pretty much all sensors unavailable.. oddly I can still see the basic sensors of the remote thermostat controller (sensoHOME) but everything else is currently dead. |
|
Hi 8.17 freshly loaded and "no devices or entities" detected. Been like this for close on a week. Have deleted and reloaded. |
|
Vaillant send an eMail and said that they updated their app (it crashed when looking up the consuption data). Whatever they did to the app and most likely also the api, it fixed this integration for me, too. Fingers crossed! |
|
I updated the vaillant app But still no emtities in HA.... 😔 |
|
I also had some trouble with the integration since 2-3 weeks. My solution for energy sensors: My solution for quota exceeded error: Now I changed my config too: Now the quota exceeded error disappeared after this change for already 1 day. I don’t know if it’s because of this change or because there was a parallel bug fix in the Vaillant Api :D. I was imagine that the problem could be, because update of the energy data and other updates were updated at the same time, because 3600 is a multiple of 180, which probably caused the error?! But I am not sure, as it worked before with this config without any problem. |
|
I disabled the integration - and enabled it again after I got the eMail from Vaillant saying that the app got fixed (consumption page not crashing anymore). That was all it took for the integration to work properly again. My update interval is still 60 secs and it works fine (for now). |
Same here 👌 |
|
@passiber Interesting. So armed with your information, I've just deleted and re-added again (I don't seem to have luck just reconfiguring, but that may just be me) and immediately set "3630" seconds between energy updates, but this time ticked these (that were working previously and then seemed to be causing the "only working for one reading" issue.
Obviously I have no idea if anything else has changed so this is just poking in the dark. @Boeroer you're lucky to be getting emails from Vaillant! I've got nothing at my registered address. |
|
Hello, I have exactly the same problem with energy data.. I also have version 0.8.17 I have now also:
set Let's see if it works again now The myVaillant app no longer crashes after the latest update to version 2.22.1, but now shows a text window under energy options in which it says:
|
|
Hello, look's like Vaillant is blocking or limiting IPs on that the myPyllant is for some time regulary requesting and getting datas from Vaillant. How I found it out ? On Saturday my HA myPyllant integration stoped to work - similar as many times described in this chain. At the same time I found out that the myVaillant APP on my Iphone /connected in the same home network with the same public IP as my HA is not getting the consuption datas /the App was after trial to open the consumption data automaticaly closing/. But on the T-Mobile public LTE network was the APP on my IPhone correctly working. After I switched my home router to my second public IP, the myPyllant intergration started again to work and the same the APP on my IPhone conected to my home network. Nice. But... Today again the same problem. Nothing working any more. After the switch to my primary public IP everything again OK. Looks like if the integration is regulary contacting Vaillant server - in my case setting 180 sec. btw. updates and 3600 sec. btw data updates - after some time Vaillant start to ban the IP - there should be some kind of counter of the incomming requests and after some value the IP start to be limited at least for some requests. It will be interesting to see aftre how long time the baned IP start again correctly work. My question is, what is actual the correct value for the frequency of updates not get again this kind of ban? |
|
Hello, I have also done the test for myself. So it will be the case that Vaillant blocks the corresponding IP if there are too many queries. Now the question is how often can you query? |
|
Integration stopped working again. Seems indeed the case that Vaillant is blocking queries. |
|
Same here |
|
My update ,just to assist with more information, is that as of 2 days ago, with the integration deleted and set up fresh with 3630 seconds between energy updates, it has been fully functional with 43 entities and 5 devices. Oh and my WAN IP address is not changing. The only thing that appears to have changed since the original outage is that I no longer get real-time power usage, which was there before and on my dashboard, but the entity seems to not be there when the tickbox is checked (rather than there and not functioning - I have a screenshot from the 10th October that showed 46 entities with the same tickboxes checked and I now get 43 with the same settings). Oh well! |
When u wie the hub, all emtities are gone right? I have many automations working with the integrations and then all things wont work.... |
|
Hello, My heat pump has just stopped responding to control tasks altogether. I have restarted my Fritzbox again and also restarted the SensoNet to get it running again. |
In a sense of Home Assistant hub is a common name of a device class. Logically, you can treat |
Yes, I delete the configuration and then configure again. It appears to me to keep the automations and all entities in my Home Assistant when I do this. Not behaviour I'd expect, but I'm grateful for it. However I would recommend that you have a full backup and proceed with caution, before you make any changes based on what some random person on the Internet tells you. |
|
Is anybody working in an Update for the integration, as it is still broken? |
|
I have changed my IP-address and now it works for me. I`m sure that Vaillant is blocking IP-addesses with too many requests. |
|
This does not help. The integration is broken. Whether this is due to a change in the API nobody can tell unless you have access to the documentation which @signalkraft should have, but he does not respond at all to the various issues reported not only in this thread. Kind of sad, but I do not think this will come back to life. |
|
This is clearly an issue on the Vailliant side which is impacting their own app as well as 3rd party API access. Right now, I don’t really see what changes could be made to the integration to help. To me it looks like they are going through some sort of API upgrade with the recent release of an app update including new functionality. Hopefully, they will iron out the bugs soon and normal service will resume..
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Georg ***@***.***>
Sent: Tuesday, October 29, 2024 4:50:38 PM
To: signalkraft/mypyllant-component ***@***.***>
Cc: jstott1070 ***@***.***>; Comment ***@***.***>
Subject: Re: [signalkraft/mypyllant-component] Unexpected error fetching myVAILLANT data (Issue #218)
This does not help. The integration is broken. Whether this is due to a change in the API nobody can tell unless you have access to the documentation which @signalkraft<https://github.com/signalkraft> should have, but he does not respond at all to the various issues reported not only in this thread. Kind of sad, but I do not think this will come back to life.
—
Reply to this email directly, view it on GitHub<#218 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASP2VIDQIC3QIZKJ57XDSYDZ564F5AVCNFSM6AAAAABPTGK3D6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBUHAZTAMRXHE>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Since I'm getting called out here I better write something 🔥 Like @jstott1070 pointed out, this seems like an API issue more than an integration issue. Nothing about the polling frequency or number of API endpoints in this integration changed recently. I've had quota errors once or twice myself, but nothing noticable in my own use of the integration. I've kept the polling rates at the default. If I had the problem more often myself, I could more easily debug it and try to fix it. As it stands, there's not much I can do. What anyone with the problem could try:
@froggi1930 I know as much about Vaillant's API as anyone else. It's not documented, and Vaillant doesn't inform me about changes - it's all reverse engineered from their app by myself, and some nice people who volunteer their free time for you. |
|
I will close this now (since the issue was originally about sth completely different), there is more discussion happening over here: #226 |
and others
Before submitting a new issue
Problem description
Unexpected error fetching myVAILLANT data
Logs
The app works fine for me.
And what is strange, I'm able to run
TEST DATAaction from HA:The text was updated successfully, but these errors were encountered: