Hi there, How to get current flow temperature sensor?
I don’t use hot water, but I have the current flow temperature for circuit…
Can anyone help?
I have 600 for main update and 7200 for energy data, any less and I get quota issues towards the end of the week.
it’s sensor.<yoursystemname>_circuit_0_current_flow_temperature via the MyVaillant API, or sensor.ebusd_ctlv3_hc1flowtemp via ebus.
Is there any API entity that extracts current water RETURN temperature in heater, not only current flow temp ?
I don’t know whether Vaillant installations usually come with a temp sensor for return temp, mine surely didn’t.
I have a Vaillant AeroTHERM 10 kw with sensorComfort
I would to see live data of how much power my Aerotherm is using, but I do not see that in my Home Assistant.
I can see temperature of the water plus a lot of other stuff but I would like to see not when the it starts an stop.
Do you know if I can get those numbers with my setup?
I also want to measure the return flow temperature for my boiler. The boiler does measure this internally and installers can see this data with their diagnostic app. I got around this by putting a Zigbee temp sensor on the return pipe, but a bit of a kludge and would be better to extract data directly via API (if possible).
i have this problem !
Logger: homeassistant.util.package
Quelle: util/package.py:163
Erstmals aufgetreten: 23:04:00 (6 Vorkommnisse)
Zuletzt protokolliert: 23:07:23
- Unable to install package Pillow==11.: × No solution found when resolving dependencies: ╰─▶ Because you require pillow==11. and pillow==12.0.0, we can conclude that your requirements are unsatisfiable.
- Unable to install package myPyllant==0.9.0: × No solution found when resolving dependencies: ╰─▶ Because mypyllant==0.9.0 depends on pydantic>=2.10.4,<2.11.dev0 and pydantic==2.12.2, we can conclude that mypyllant==0.9.0 cannot be used. And because you require mypyllant==0.9.0, we can conclude that your requirements are unsatisfiable.
Hello,
Facing the same issue. I am using this integration just to pair my Saunier Duval 18KKS with HA. Heating is based on the scenarios for every single room separately together with smart thermostats mounted on radiators.
With “My Home Zone 1” left in peace (heating permanently) everything is OK.
Manual changes to values result with disappearing of home integration.
With the integration being unavailable whole heating system is out of order.
God only knows what makes it come back. Just tried re configuring/ reinstalling or just waiting. But this is not how it supposed to be organised.
Changed seconds between the updates to 600 and it helped.
Right now, although changed to higher values the same scenario reappears.
Hints how to make it available are appreciated.
Dear all,
I’m using this integration since a couple of days. While the controller, the domestic water and the heating circuits are regularly reporting values, the heatpump itself has issue: While the diagnostics are updated from time to time, the sensors appeared, but whether receive data only once after reload of the integration, or not at all (maybe after a reboot?):
I assume this plays a role? Update interval is 300, update interval for energy data is 300 as well… maybe too often?
Can somebody help? The COP (“Heizeffizienz”) would be really nice to know… Thanks a lot!
Hi! I wanted to chime in to help troubleshoot.
I am running a fairly heavy setup myself (using AmbiSense with multiple zones), which typically generates more data traffic. However, I have not experienced any quota issues or 403 errors recently.
Looking at the error 403 Quota Exceeded, it definitely points to rate limiting.
I checked my own stable configuration, and I believe two settings are key to keeping me within the safe zone. Could you compare these with yours?
-
Update Interval: I have set my “Seconds between updates” to 600 seconds (10 minutes). But I noticed in your post that this is already the case.
-
Realtime Data: I have explicitly disabled “Fetch realtime statistics” and “Fetch realtime energy consumption” in the integration options. These can trigger excessive calls.
Try increasing your update interval to 600s and disabling the realtime fetch options to see if the error clears up after the quota reset.
Also do you only fetch data from the Vaillant cloud through the integration (HA environment)? Or do you use external means accessing Vaillant cloud, like connected with Google Home or Alexa?
Exactly what I did 
purchased BleBox temp sensor, attached to return pipe and read it over WIFI
I’ve hit a problem that might be similar to what @Tobster77 documented above, looking at his screen shot.
I just upgraded to Core 2025.12.2. On reboot some myVAILLANT entitities became unavailable. The entities were the ones related to energy usage. I noticed these were all defined in one of the five devices I had.
I then deleted the myVAILLANT integration and did a fresh install. The result of this is that my number of devices dropped from five to four, and of course the energy related entities are now missing.
Can somebody shed some light on what I’ve done wrong please?
Should have said:
- Core 2025.12.2
- Supervisor 2025.12.3
- Operating System 16.3
- Frontend 20251203.2
myVAILLANT Version v0.9.9, which was running fine until I installed 2025.12.2
Update
I tried a few things, ending up with deleteing myVAILLANT, rebooting then reinstalling myVaillant. Now I’m back to five devices, however the seven entities associated with Device 0 aroTHERM plus do not get updated over time. All other entities associated with the other four myVAILLANT devices are updated on a regular basis.
** Update2**
I’ve tried to sort this and noticed each time I boot my HASS I get an energy reading then no further updates, it just straightlines at no additional energy used. So, it seems to me the entities are not being updated over time.
** Update3 - SOLVED **
So, looks like it was my problem. At some time during the 2025.12 update process I made a lot of changes. In the processI managed to delete the update time for Energy so it was blank. I added a value and it is now working just fine. Plus I’ve moved to 2026.1 and everything is still working correctly.
I’m having problems with the myVaillant Connect VR 940f gateway, which is turning on the red light from a ‘communication failure’. The gateway had been functioning properly for four months, but suddenly it started displaying a red light. Powering off/on the gateway clears the problem. There is no loss of networking communication and no errors in either the Vaillant system or Unifi networking.
I installed the myVaillant extension to detect any failures, but none of the entities show any issues. The Online Status field for the VR 940f shows the gateway as permanently disconnected and can’t detect any offline condition from any entities in HA. If I could detect the failure, then I could automate the power off/on.
I’m using it with an aroTHERM plus heat pump. What are others seeing with this status field?
In the exchanges with Vaillant, their next suggestion is to replace the VR 940f. It would be interesting to understand whether the online status field is useful.
The “Online Status” shows always “Disconnected” in the configuratin with my aroTherm plus 105/6. In my opinion this is a bug, as myVaillant connects to the Vaillant cloud. There would be no data if the VR 940f gateway would be always “Disconnected”. Additionally the Vaillant App wouldn’t function properly if the heatpump is noct connected to the cloud.
1 Like
I’ve been running this integration for about two year, Just updated to the latest version last night. This morning all the entities were unavailable. In the logs I found the quota exceeded entry twice. Just after the update time and then no further. The log message also stated that the quota would be replenished about two hours later. Still no joy this morning.
Does anyone else have the issue and managed to solve it? Or is it a Vaillant server issue coinciding?
After a bit of digging, three field updates were disabled in release v0.9.8 due to quota errors:
- Fetch system connection status (default off)
- Fetch diagnostic trouble codes (default off)
- Fetch Ambisense Capability (default off)
You can see the changes here: Comparing v0.9.8...main · signalkraft/mypyllant-component · GitHub
I went to the file const.py in the directory custom_components/mypyllant and turned two fields back on:
DEFAULT_FETCH_CONNECTION_STATUS = True
DEFAULT_FETCH_DTC = True
I then rebooted Home Assistant.
The status is now coming through. I did not change the default update interval.
DEFAULT_UPDATE_INTERVAL = 30 * 60 # in seconds
I will see if I can detect the failure and get a diagnostic trouble code as well.
You are right. I was not aware that the “Fetching system connection status” is configarable. I tried to set it to true and the “Online Status” went to “connected”. But this change braught my configuration (version v0.9.9) back to quota errors. Therefore I disabled “Fetching system connection status” again and avoid the quota errors (main intervall 60 and 5400 for energy data)
Hi all, very new to this forum and HA. Have tons of tons to learn.
Maybe I was a bit optimistic when bying the Vaillant connect. But i wanted to monitor more data that is available in the boiler diagnostic menu. So I hoped to fetch all the data to HA to minitor.
I assume the API has it limitation to fetch data. Or maybe the question was not there :).
I have a sensoroom connected to an ecotec plus boiler.
Where I wanted to monitor the heating system:
Water temp, out
Water temp, in
Water flow rate
Burning level of boiler,
Gas consumtion
Actual setpoint for water temperature
Would this be possible?
You will need an ebus adapter for all that; figuring out the right sensors will be a bit of a chore depending on your specific model of heater.