Hello @pdd,
You did a great job, it works perfectly.
You will make a lot of people happy with this new option!
Thank you again for your efficiency and the speed with which you responded to our messages.
I will announce the good news on forum home assistant francophone because we were several looking for a solution for our Saunier Duval equipment.
Bonjour @pdd,
Tu as réalisé un super travail, cela fonctionne à la perfection.
Tu va faire plein d’heureux avec cette nouvelle option !
Merci encore pour ton efficacité et la rapidité avec laquelle tu a répondu à nos message.
Je vais annoncer la bonne nouvelle sur forum home assistant francophone car nous étions plusieurs à chercher une solution pour notre matériel Saunier Duval.
Glad to hear that! Could you let me know the names of the Saunier Duval devices you’re running this on? I would like to add them to the list of tested combinations.
Hello @pdd,
Now that I can manage my boiler from home assistant, I started creating a map that faithfully reproduces the interface of the Migolink application.
I lack some information to make it perfect.
Do you think it is possible to recover the desired duration when changing the set temperature and the remaining time of this mode?
Thank you
Bonjour @pdd ,
Maintenant que je peux gérer ma chaudière depuis home assistant, je me suis lancé dans la création d’une carte reproduisant fidèlement l’interface de l’application Migolink.
Il me manque certaines infos pour que cela soit parfait.
Pensez vous qu’il soit possible de récupérer la durée souhaitée lorsque l’on change la température de consigne et le temps restant de ce mode.
Merci,
Hello @pdd,
On your GitHub, you specify that your integration works with Migo from Saunier Duval, but I use MigoLink which is another Saunier Duval application. So I can confirm that it works with MigoLink, but for Migo you have to find another user to confirm its proper functioning.
There’s a new beta version 0.3.0b0 that uses new API endpoints (matches the latest version of the myVAILLANT app). If you spot any issues, let me know on Github.
In the latest beta release, there are now extra attributes quick_veto_start_date_time and quick_veto_end_date_time on Zone entities. Let me know, if this works for you!
Thanks, I fixed that. I wasn’t aware that there are multiple Migo apps.
SUPER!
It works well again with the new Beta.
The two new attributes appear well, all that remains is to create a sensor that will give the remaining time in forced march (quick_veto_end_date_time - sensor.time), Unless you can integrate it directly.
Thank you
quick_veto_start_date_time: 2023-04-24T13:46:45
quick_veto_end_date_time: 2023-04-24T16:46:00
friendly_name: Zone 1
supported_features: 17
Hello @pdd,
Now the integration works perfectly, so I created a map based on picture-elements.
I will have a request for you:
The service “myVAILLANT: Set quick veto” allows you to choose the programming time, but only on the hours, would it be possible to add the minutes?.
Thank you
Die Einrichtung verlief gemäß Anleitung und auch die Richtigkeit der Daten habe ich mehrfach geprüft. Kannst Du vielleicht helfen? Welche Informationen brauchst Du?
Ich bin seit ca. 1 Woche von SensoApp auf myVaillant umgestellt worden.
Im Einsatz sind:
VWL 125/6 A aroTHERM plus
VWZ MEH 97/6
sensoCOMFORT VRC 7201 HK
VR 921 sensoNET
Vielen Dank für die Hilfe
Hello!
Unfortunately I fail in my case at this point: (picture above)
The setup went according to the instructions and I also checked the correctness of the data several times. maybe you can help What information do you need?
I switched from SensoApp to myVaillant about a week ago.
In use are:
VWL 125/6 A aroTHERM plus
VWZ MEH 97/6
sensoCOMFORT VRC 7201 HK
VR 921 sensoNET
Hello @pdd , the integration works very well so far! Thanks for the work! I am missing the service “hot water boost/hot water fast” that I have on the heating controller and in the MyVaillant app. Is it possible to add this maybe in a next update?
Maybe I am stupid…but I switched over from Senso app to myVaillant today, and wanted to use this integration. It works perfectly, at least the installation does, but I get 0 entities and can’t do anything with it.
I didn’t get any errors or issues…am I missing some important step in the installation?
Quick question…is there a way to set the water tank temperature to a certain value on demand?
I am trying to optimise legionella disinfection by manually setting the temperature to 62° on Sunday around lunchtime…but I can’t seem to find the appropriate entity or service to do so…
Update:
I made a little progress…
It seems the sensor.setpoint_domestic_hot_water is what I need, but while i can manually set it in the Dev options, I haven’t found a way to set it in a automation yet
Update2:
I think I managed to find it. Calling the Service “Water Heater” and using the domestic hot water 0 entity (not Device) allowes me to set the temperature. Now I will see if it actually works when it triggers for the first time this Sunday.
Update3: it appears that Cooling mode on the heat pump causes the whole integration (Ver. 0.2 at least) to stop working.
I get not entities and get the following error
2023-06-14 08:19:04.216 ERROR (MainThread) [custom_components.mypyllant] Unexpected error fetching myVAILLANT data: 1 validation error for Zone
heating_state
value is not a valid enumeration member; permitted: ‘IDLE’, ‘HEATING_UP’ (type=type_error.enum; enum_values=[<ZoneHeatingState.IDLE: ‘IDLE’>, <ZoneHeatingState.HEATING_UP: ‘HEATING_UP’>])
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 283, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/config/custom_components/mypyllant/init.py”, line 140, in _async_update_data
data = [
^
File “/config/custom_components/mypyllant/init.py”, line 140, in
data = [
^
File “/usr/local/lib/python3.11/site-packages/myPyllant/api.py”, line 256, in get_systems
system = System(
^^^^^^^
File “/usr/local/lib/python3.11/site-packages/myPyllant/models.py”, line 158, in init
self.zones = [Zone(system_id=self.id, **z) for z in self._merged_zones]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/myPyllant/models.py”, line 158, in
self.zones = [Zone(system_id=self.id, **z) for z in self._merged_zones]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/myPyllant/models.py”, line 108, in init
super().init(**data)
File “/usr/local/lib/python3.11/site-packages/pydantic/main.py”, line 341, in init
raise validation_error
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.mypyllant
Source: custom_components/mypyllant/init.py:140
Integration: myVAILLANT (documentation, issues)
First occurred: 11:29:10 (1 occurrences)
Last logged: 11:29:10
Unexpected error fetching myVAILLANT data: 1 validation error for Zone heating_state value is not a valid enumeration member; permitted: ‘IDLE’, ‘HEATING_UP’ (type=type_error.enum; enum_values=[<ZoneHeatingState.IDLE: ‘IDLE’>, <ZoneHeatingState.HEATING_UP: ‘HEATING_UP’>])
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 283, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/config/custom_components/mypyllant/init.py”, line 140, in _async_update_data
data = [
^
File “/config/custom_components/mypyllant/init.py”, line 140, in
data = [
^
File “/usr/local/lib/python3.11/site-packages/myPyllant/api.py”, line 256, in get_systems
system = System(
^^^^^^^
File “/usr/local/lib/python3.11/site-packages/myPyllant/models.py”, line 158, in init
self.zones = [Zone(system_id=self.id, **z) for z in self._merged_zones]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/myPyllant/models.py”, line 158, in
self.zones = [Zone(system_id=self.id, **z) for z in self._merged_zones]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/myPyllant/models.py”, line 108, in init
super().init(**data)
File “pydantic/main.py”, line 341, in pydantic.main.BaseModel.init
pydantic.error_wrappers.ValidationError: 1 validation error for Zone
heating_state
value is not a valid enumeration member; permitted: ‘IDLE’, ‘HEATING_UP’ (type=type_error.enum; enum_values=[<ZoneHeatingState.IDLE: ‘IDLE’>, <ZoneHeatingState.HEATING_UP: ‘HEATING_UP’>])
