mypyllant-component: Unexpected error fetching myVAILLANT data
Before submitting a new issue
- I redownloaded the latest release and restarted Home Assistant
- I’ve checked known issues
- I’ve enabled debug logs and attached the relevant logs to this ticket
Problem description
Unexpected error fetching myVAILLANT data
Logs
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 954, in from_api
DomesticHotWater.from_api(
File "/usr/local/lib/python3.12/site-packages/myPyllant/models.py", line 575, in from_api
data["current_special_function"] = DHWCurrentSpecialFunctionVRC700(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/enum.py", line 757, in __call__
return cls.__new__(cls, value)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/enum.py", line 1171, in __new__
raise ve_exc
ValueError: 'ONE_DAY_BANK_HOLIDAY' is not a valid DHWCurrentSpecialFunctionVRC700
The app works fine for me.
And what is strange, I’m able to run TEST DATA action from HA:
homes:
- homeName: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
serialNumber: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
systemId: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
productMetadata:
productType: VR921
productionYear: "22"
productionWeek: "21"
articleNumber: "0020260965"
state: CLAIMED
migrationState: FINISHED
migrationFinishedAt: "2024-04-09T16:40:59.767070615Z"
onlineState: ONLINE
firmware:
version: 0357.40.35
connectedToOldIoTPlatform: null
updateEnabled: true
updateRequired: false
nomenclature: VR 921
cag: false
countryCode: PL
productInformation: VR921
firmwareVersion: 0357.40.35
control_identifier:
controlIdentifier: vrc700
time_zone:
timeZone: Europe/Warsaw
diagnostic_trouble_codes:
- serialNumber: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
articleNumber: "0020171316"
codes: []
- serialNumber: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
articleNumber: "0010024648"
codes: []
- serialNumber: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
articleNumber: "0020260965"
codes: []
connection_status:
connected: true
system:
state:
system:
outdoorTemperature: 23.875
outdoorTemperatureAverage24h: 17.78125
systemWaterPressure: 1.7
legionellaProtectionStartWeekday: "OFF"
energyManagerState: STANDBY
systemOff: false
zones:
- index: 0
desiredRoomTemperatureSetpointHeating: 0
desiredRoomTemperatureSetpoint: 0
currentRoomTemperature: 18.6875
currentRoomHumidity: 68
currentSpecialFunction: NONE
circuits:
- index: 0
circuitState: STANDBY
currentCircuitFlowTemperature: 20.5
heatingCircuitFlowSetpoint: 0
calculatedEnergyManagerState: HEATING_STANDBY
domesticHotWater:
- index: 255
currentSpecialFunction: NONE
currentDomesticHotWaterTemperature: 29
ventilations: []
properties:
system:
controllerType: VRC700
controllerRevision: R6
systemScheme: 1
backupHeaterType: CONDENSING
backupHeaterAllowedFor: DOMESTIC_HOT_WATER_AND_HEATING
temporaryAllowBackupHeater: DISABLED
moduleConfigurationVR71: 3
energyProvidePowerCutBehavior: DISABLE_HEATPUMP
smartPhotovoltaicBufferOffset: 10
externalEnergyManagementActivation: false
operationModeEffect: ALL
zones:
- index: 0
isActive: true
zoneBinding: CENTRAL_CONTROL
associatedCircuitIndex: 0
circuits:
- index: 0
mixerCircuitTypeExternal: HEATING
heatingCircuitType: DIRECT_HEATING_CIRCUIT
isCoolingAllowed: false
domesticHotWater:
- index: 255
minSetpoint: 35
maxSetpoint: 65
ventilations: []
configuration:
system:
continuousHeatingStartSetpoint: -26
alternativePoint: -21
heatingCircuitBivalencePoint: 0
domesticHotWaterBivalencePoint: -7
adaptiveHeatingCurve: true
domesticHotWaterMaximumLoadingTime: 60
domesticHotWaterHysteresis: 5
domesticHotWaterFlowSetpointOffset: 25
maxFlowSetpointHeatpumpError: 25
domesticHotWaterMaximumTemperature: 80
hybridControlStrategy: BIVALENCE_POINT
paralellTankLoadingAllowed: false
zones:
- index: 0
general:
name: Ogrzewanie
holidayStartDateTime: "2015-01-01T00:00:00Z"
holidayEndDateTime: "2015-01-01T00:00:00Z"
holidaySetpoint: 10
heating:
operationModeHeating: "OFF"
setBackTemperature: 17.5
dayTemperatureHeating: 20
timeProgramHeating:
metaInfo:
minSlotsPerDay: 0
maxSlotsPerDay: 3
setpointRequiredPerSlot: false
monday: []
tuesday: []
wednesday: []
thursday: []
friday: []
saturday:
- startTime: 600
endTime: 1320
sunday:
- startTime: 600
endTime: 1320
cooling: {}
circuits:
- index: 0
heatingCurve: 1.1500001
heatingFlowTemperatureMinimumSetpoint: 15
heatingFlowTemperatureMaximumSetpoint: 60
heatDemandLimitedByOutsideTemperature: 17
heatingCircuitFlowSetpointExcessOffset: 0
epsilon: 2
setbackModeEnabled: false
roomTemperatureControlMode: NON
domesticHotWater:
- index: 255
operationModeDomesticHotWater: "OFF"
tappingSetpoint: 50
holidayStartDateTime: "2015-01-01T00:00:00Z"
holidayEndDateTime: "2015-01-01T00:00:00Z"
timeProgramDomesticHotWater:
metaInfo:
minSlotsPerDay: 0
maxSlotsPerDay: 3
setpointRequiredPerSlot: false
monday:
- startTime: 1200
endTime: 1310
tuesday:
- startTime: 1200
endTime: 1310
wednesday:
- startTime: 1200
endTime: 1310
thursday:
- startTime: 1200
endTime: 1310
friday:
- startTime: 1200
endTime: 1320
saturday:
- startTime: 600
endTime: 1320
sunday:
- startTime: 600
endTime: 1320
timeProgramCirculationPump:
metaInfo:
minSlotsPerDay: 0
maxSlotsPerDay: 3
setpointRequiredPerSlot: false
monday:
- startTime: 540
endTime: 1270
tuesday:
- startTime: 540
endTime: 1270
wednesday:
- startTime: 540
endTime: 1270
thursday:
- startTime: 540
endTime: 1270
friday:
- startTime: 540
endTime: 1270
saturday:
- startTime: 540
endTime: 1270
sunday:
- startTime: 540
endTime: 1270
ventilations: []
current_system:
system_type: BOILER_OR_ELECTRIC_HEATER
has_emf_capable_devices: true
primary_heat_generator:
device_uuid: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ebus_id: BAI00
spn: 376
bus_coupler_address: 0
article_number: "0010024648"
emfValid: true
device_serial_number: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
device_type: BOILER
first_data: "2022-10-11T14:17:35Z"
last_data: "2024-10-09T10:44:19.415Z"
data:
- operation_mode: DOMESTIC_HOT_WATER
value_type: CONSUMED_ELECTRICAL_ENERGY
calculated: false
from: "2022-10-11T14:17:35Z"
to: "2024-10-09T10:44:19.415Z"
- operation_mode: HEATING
value_type: CONSUMED_ELECTRICAL_ENERGY
calculated: false
from: "2022-10-11T14:17:35Z"
to: "2024-10-09T10:44:19.087Z"
- operation_mode: DOMESTIC_HOT_WATER
value_type: CONSUMED_PRIMARY_ENERGY
calculated: false
from: "2022-10-11T14:17:35Z"
to: "2024-10-09T10:44:18.212Z"
- operation_mode: HEATING
value_type: CONSUMED_PRIMARY_ENERGY
calculated: false
from: "2022-10-11T14:17:35Z"
to: "2024-10-09T10:44:17.837Z"
product_name: VC 25CS/1-5 (N-PL) ecoTEC plus
secondary_heat_generators: []
electric_backup_heater: null
solar_station: null
ventilation: null
gateway: null
mpc:
devices: []
rts:
statistics: []
device_buckets:
startDate: "2024-10-08T00:00:00Z"
endDate: "2024-10-09T00:00:00Z"
resolution: HOUR
operationMode: DOMESTIC_HOT_WATER
energyType: CONSUMED_ELECTRICAL_ENERGY
totalConsumption: 25.709258280988383
data:
- startDate: "2024-10-08T00:00:00Z"
endDate: "2024-10-08T01:00:00Z"
value: 0
- startDate: "2024-10-08T01:00:00Z"
endDate: "2024-10-08T02:00:00Z"
value: 0
- startDate: "2024-10-08T02:00:00Z"
endDate: "2024-10-08T03:00:00Z"
value: 0
- startDate: "2024-10-08T03:00:00Z"
endDate: "2024-10-08T04:00:00Z"
value: 0
- startDate: "2024-10-08T04:00:00Z"
endDate: "2024-10-08T05:00:00Z"
value: 0
- startDate: "2024-10-08T05:00:00Z"
endDate: "2024-10-08T06:00:00Z"
value: 0
- startDate: "2024-10-08T06:00:00Z"
endDate: "2024-10-08T07:00:00Z"
value: 0
- startDate: "2024-10-08T07:00:00Z"
endDate: "2024-10-08T08:00:00Z"
value: 0
- startDate: "2024-10-08T08:00:00Z"
endDate: "2024-10-08T09:00:00Z"
value: 0
- startDate: "2024-10-08T09:00:00Z"
endDate: "2024-10-08T10:00:00Z"
value: 0
- startDate: "2024-10-08T10:00:00Z"
endDate: "2024-10-08T11:00:00Z"
value: 0
- startDate: "2024-10-08T11:00:00Z"
endDate: "2024-10-08T12:00:00Z"
value: 0
- startDate: "2024-10-08T12:00:00Z"
endDate: "2024-10-08T13:00:00Z"
value: 0
- startDate: "2024-10-08T13:00:00Z"
endDate: "2024-10-08T14:00:00Z"
value: 0
- startDate: "2024-10-08T14:00:00Z"
endDate: "2024-10-08T15:00:00Z"
value: 0
- startDate: "2024-10-08T15:00:00Z"
endDate: "2024-10-08T16:00:00Z"
value: 10.968487259579335
- startDate: "2024-10-08T16:00:00Z"
endDate: "2024-10-08T17:00:00Z"
value: 13.869530781343732
- startDate: "2024-10-08T17:00:00Z"
endDate: "2024-10-08T18:00:00Z"
value: 0.8514350840769347
- startDate: "2024-10-08T18:00:00Z"
endDate: "2024-10-08T19:00:00Z"
value: 0
- startDate: "2024-10-08T19:00:00Z"
endDate: "2024-10-08T20:00:00Z"
value: 0
- startDate: "2024-10-08T20:00:00Z"
endDate: "2024-10-08T21:00:00Z"
value: 0.0029669536208675675
- startDate: "2024-10-08T21:00:00Z"
endDate: "2024-10-08T22:00:00Z"
value: 0.0056127341225030184
- startDate: "2024-10-08T22:00:00Z"
endDate: "2024-10-08T23:00:00Z"
value: 0.0056127341225030184
- startDate: "2024-10-08T23:00:00Z"
endDate: "2024-10-09T00:00:00Z"
value: 0.0056127341225030184
rbr:
rbrCapable: true
rooms: []
energy_management:
energyManager:
available: false
compatible: false
energyManagementStatus:
thermalStorage:
domesticHotWater:
available: false
selected: false
heatingBufferCylinder:
available: false
selected: true
ship_self:
ski: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
brand: Vaillant
type: Gateway
model: VR921
spineEnabled: false
spineEnabledStatus: DETERMINED
spineCapable: true
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 11
- Comments: 147 (6 by maintainers)
Try https://github.com/signalkraft/mypyllant-component/releases/tag/v0.8.17 please
Same here - all entities became unavailable since 7.16am UK time this morning. myVaillant App is still working fine.
I have the same issue as well just different variables.
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:
Starting GET to https://api.vaillant-group.comby time may reveal something@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.
To be fair, I’ve noticed that the Vaillant API has been very bad of late. It’s made me consider doing it local only with EEBUS! It looks a bit of a project but the way Vaillant seem to be handling their API it could be a better long term solution.
I have a huge amount of appreciation to @signalkraft for this integration and the work they and the other contributors have put into this integration. I love it and it’s my most useful integration in Home Assistant by far.
dirty quick fix which worked for me: change in ./.local/lib/python3.11/site-packages/myPyllant/models.py
class ZoneCooling
to (basically comment the most out):
I will close this now (since the issue was originally about sth completely different), there is more discussion happening over here: https://github.com/signalkraft/mypyllant-component/issues/226
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?
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.
Exactly same thing here since 2 weeks. Updates to 0.8.17 and HA core is upgrade to 2024.10.3.
It is not fixed, otherwise I would not ask for it 😉
I am on v0.8.17 and the same errors since 1 week.
I know it is a private project and involves a lot of work, but it would be nice to let us know if at least someone works on a solution.
I updated my system to version 0.8.17, but I still unable to fetch myVAILLANT data.
Here is the traceback:
Here is the output of
mypyllant.generate_test_dataIndeed, here is a circuit with index 1, which has no state and other properties data. I don’t know what is this.
I made
circuit_statepositional argument optional, and now it works like a charm!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).
The last notes do not seem to be related to the originally reported error of the integration. This integration needs to be fixed.
This seems to work, but I’m not a programmer and unfortunately cannot implement it myself.
I agree. @signalkraft did a great job. I mainly used the integration to ramp up the hot water temperature and activate the boost as soon as I had enough unused solar power and also to pause when electricity prices went high (Tibber) - while I was able to monitor the temperature and so on. That was very convenient (no need to wire some relay to the circuit board and all that) and made it the most impactful part of my Home Assistant system so far (besides the evcc addon + integration).
Vaillant, like so many hardware manufacturers with a long tradition, seems to struggle with solid software engineering and development. Too bad. I still hope it gets fixed somehow…
I would be interested in a EEBUS solution as well.
@Boeroer yes my app crashes too in the energy section. (I see they’ve also added heating curve adjustment?)
Based on what we have learned, my complete and utter guess is this. Vaillant has a problem with the energy consumed data API. Because of this the app crashes when trying to access it Because of this the integration has different behaviour and instead keeps repeatedly polling for it. Until at least it hits API limits and then the whole integration starts to fail.
(I have no idea what my password situation had to do with it)
I’m going to disable my energy consumption entities and see what happens
Quick update. It’s lasted an hour, and now I’m in the same situation as you. Even deleting the integration and putting it back in does little.
However I’ve tried playing with the python module, specifically “generate.test.data” and I get this
This seems to indicate (along with the fact a reload gets a single data point) that this is Vaillant doing something rather than anything wrong with the integration. I’m going to disable it for an hour or two and see what happens over the next day or 3.
I think Vaillant may have forced some kind of reset for some users. Here is my situation, it may not be relevant but there is no such thing as too much information:
2024-10-18 14:30:18.128 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/emf/v2/GUID/buckets?resolution=HOUR&operationMode=DOMESTIC_HOT_WATER&energyType=CONSUMED_ELECTRICAL_ENERGY&startDate=2024-10-18T00:00:00.000%2B01:00&endDate=2024-10-19T00:00:00.000%2B01:00, skipping update of myVAILLANT data for another 10800sMake of this what you will!
I don’t think so. The myVailliant app works for me. I forced a new IP but nothing changes: integration fetches the data properly once I reload the integration. But shortly after all entities become unavailable. I have two identical Vaillant heat pumps in the app and both also show up in the integration - both with the same faulty behavior.
no need to SHOUT
and you forgot to attach log file
@Krzysztonek maybe it would help @signalkraft to know which countries where it does not work?
Odd, its all still working for me in the UK, maybe something to do with different configs?
@Krzysztonek I know, but there’s two issues going on in one ticket. Everyone else seems to have another problem. If yours is fixed, I would move everyone else over to this ticket for the cooling stuff: https://github.com/signalkraft/mypyllant-component/issues/216
Same problem here. No Data in HA. Vaillant App works. v0.8.16 running
@Krzysztonek https://github.com/signalkraft/mypyllant-component/releases/tag/v0.8.16 this should fix your original issue.
I use a docker compose file so I could add further commands (custom pyton files using the mypyllant lib within the container). There I added another volume entry:
When a fix is provided, I just need to remove the volume entry.
I ran a bash shell in the container and ran “vi /usr/local/lib/python3.12/site-packages/myPyllant/models.py”, hit ‘/’ (search) entered ‘Cool’ (to get to the right spot), then hit ‘I’ and carefully matched the hash comments as described (most is not all!). Restarted HA and it works - dirty hack, but works and will get overwritten by HACS when a better fix is deployed
Works for me. Thanks
Suggestion: relax and wait for this to be fixed. Use the app until then
the most strange is that i could do “call service” test data
Seemingly same here but with a slightly different error