I just updated to the latest version (0.5) after using the beta…and now all devices and entities no longer give me any data. I will leave it overnight and check again tomorrow morning to see if it recovers on it’s own…
Edit: reloading the integration didn’t help, neither did waiting, but doing another restart of Home Assistant did the trick.
would you mind sharing this dashboard? I am still fairly new to HA and would like it as a starting point.
Bonjour,
n’ayant plus de données avec la v0.50 même après un redémarrage de hassio, je viens de retourné en V0.4.0 et là tout fonctionne sauf la décimale sur le temps de chauffe.
voici les codes erreurs:
Cette erreur provient d'une intégration personnalisée
Logger: custom_components.mypyllant
Source: custom_components/mypyllant/__init__.py:155
Integration: myVAILLANT (documentation, issues)
First occurred: 15:04:16 (2 occurrences)
Last logged: 15:06:24
Unexpected error fetching myVAILLANT data: Claim.__init__() got an unexpected keyword argument 'firmware'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 290, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/mypyllant/__init__.py", line 155, in _async_update_data
async for system in await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.11/site-packages/myPyllant/api.py", line 265, in get_systems
async for claim in claims:
File "/usr/local/lib/python3.11/site-packages/myPyllant/api.py", line 251, in get_claims
yield Claim(**dict_to_snake_case(claim_json))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: Claim.__init__() got an unexpected keyword argument 'firmware'
Cette erreur provient d'une intégration personnalisée
Logger: custom_components.mypyllant
Source: custom_components/mypyllant/__init__.py:136
Integration: myVAILLANT (documentation, issues)
First occurred: 15:04:16 (2 occurrences)
Last logged: 15:06:24
Unexpected error fetching myVAILLANT data: Claim.__init__() got an unexpected keyword argument 'firmware'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 290, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/mypyllant/__init__.py", line 136, in _async_update_data
data = [
^
File "/config/custom_components/mypyllant/__init__.py", line 136, in <listcomp>
data = [
^
File "/usr/local/lib/python3.11/site-packages/myPyllant/api.py", line 265, in get_systems
async for claim in claims:
File "/usr/local/lib/python3.11/site-packages/myPyllant/api.py", line 251, in get_claims
yield Claim(**dict_to_snake_case(claim_json))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: Claim.__init__() got an unexpected keyword argument 'firmware'
Version 0.5 seems to ve unreliable for me. I will be downgrading to the 0.5 beta for now which seemed fine.
I installed the integration yesterday and it worked fine but some time at about 13:30 today it stopped working. I enabled error logging and after a restart I find these messages:
any idea what’s going wrong there?
Je viens de passer à la V0.5.0b1 et cela semble fonctionner. 
Bei mir gab es heute auch ab ca. 13.15 keine Kommunikation mehr.
Bin auch erst mal auf die V0.5.0b1 zurück.
Hi
I have been trying to get this to work however I can’t get past the log in page. Details are correct. Can anyone confirm that this integration will work with Vaillant VRC700/5 controller, VRC700 app V3.16.8 and
VR920 gateway and VR66 control unit.
You need to be running the myVaillant app on your system. Senso app or others won’t work
Version v0.5.1 should fix the problem with the firmware data, and it should be a bit more stable with future API changes. Unfortunately there’s still no way to tell when Vaillant will release a breaking API change, I mostly just find out through people’s error reports or on my own setup at home.
0.5.1 also failed on me after running a while. Maybe something is still wrong? I don’t have time right now for logs, but will see if I can provide them later.
OK Thank you. Not sure I want to change to the MyVaillant app as it has taken a long time to get the VRC700 app and devices working happily.
@pdd Hi! I just tried to integrate your Vaillant Integration. Download and installation via HACS works fine, but when I try to add the integration, I get an endless Loading spinner with the message “Please wait while the integration is beeing installed”. So I do not get to the point to input my Vaillant Account data. Are you familiar to that behaviour and do you have any tipp for me?
Thanks!
BR
Gerald
@g.maresch did you restart home assistant? Please check the HA logs and post them here, if the problem persists.
@CommanderROR sorry to hear that, it’s been working fine for me so far. I’d be happy to look at logs.
Sorry, I downgraded to the 0.5 beta for convenience for now…will see if I have time to experiment tomorrow
Yes, I have tried a restart of HA and the Docker/Machine. The problem still exists - I get the following lines in the log file:
None of those seem to be related to this integration, unfortunately. You can check on the documentation link in the first post how to turn on debug logs and maybe post those. Or try an older version of the integration.
Version 0.51 just won’t work for me at all while the beta is just perfect.
I found this in the logs!
2023-10-07 10:14:59.818 ERROR (MainThread) [custom_components.mypyllant] Unexpected error fetching myVAILLANT data: wrong value type for field “diagnostic_trouble_codes” - should be “list[dict] | None” instead of value “[{‘serialNumber’: ‘215’, ‘articleNumber’: ‘0020260962’, ‘codes’: []}, {‘serialNumber’: ‘215’, ‘articleNumber’: ‘0020260914’, ‘codes’: []}, {‘serialNumber’: ‘212N8’, ‘articleNumber’: ‘0010022066’, ‘codes’: []}, {‘serialNumber’: ‘212N1’, ‘articleNumber’: ‘0010021117’, ‘codes’: []}, {‘serialNumber’: ‘2129’, ‘articleNumber’: ‘0020184846’, ‘codes’: []}]” of type “list”
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 290, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/config/custom_components/mypyllant/init.py”, line 173, in _async_update_data
data = [
^
File “/config/custom_components/mypyllant/init.py”, line 173, in
data = [
^
File “/usr/local/lib/python3.11/site-packages/myPyllant/api.py”, line 283, in get_systems
system = System.from_api(
^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/myPyllant/models.py”, line 198, in from_api
system: System = super().from_api(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/myPyllant/models.py”, line 85, in from_api
return from_dict(
^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/dacite/core.py”, line 68, in from_dict
if config.check_types and not is_instance(value, field_type):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
dacite.exceptions.WrongTypeError: wrong value type for field “diagnostic_trouble_codes” - should be “list[dict] | None” instead of value “[{‘serialNumber’: ‘212N5’, ‘articleNumber’: ‘0020260962’, ‘codes’: []}, {‘serialNumber’: ‘2125’, ‘articleNumber’: ‘0020260914’, ‘codes’: []}, {‘serialNumber’: ‘218’, ‘articleNumber’: ‘0010022066’, ‘codes’: []}, {‘serialNumber’: '21, ‘articleNumber’: ‘0010021117’, ‘codes’: []}, {‘serialNumber’: ‘21230300201848460082010188N9’, ‘articleNumber’: ‘0020184846’, ‘codes’: []}]” of type “list”
There’s a new beta release that adds an entity for firmware version, fixes the error state entity, and hopefully fixes the error you’ve reported @CommanderROR
Thanks. I will give it a try. Strange thing is, that 0.4 and 0.5 beta worked flawlessly…
