Vaillant Heatpump + missing Heating Circuits from config

[peedign]

Hi,

My system is slightly more complex than the average systems, hence I believe I'm facing some issues:

aroTHERM Split VWL 125/5 + VRC720 +2xVR92 + VR71 + 2 x VR70 + VR921
6 heating circuits are in place + an offtopic external gas boiler

ebusd is installed and HA add-on is running nicely:

I cannot seem to find more VR70s under MQTT and missing 4 circuits under MQTT explorer:

can I get some help where can I found some guidance for this particular issue in the (anyway nicely built) documentations?

I assume the config file is not fitting for purpose but unsure how to re-run the automatic rescan of the config or how to build a new one for this setup

any help is greatly appreciated and the whole ebus project is really nice job!

[JonesGW-MGD]

Hi - are you able to post the startup sequence from the logs that shows the identification of the devices, or SSH into the add-on (ebusd container) and execute ebusctl info? (If you're not sure how let me know!)

Generally any ebus attached device is readable using ebusd so you should be able to get what you want!

[JonesGW-MGD]

OK - and what about if you run ebusctl find -f -V sensor

[peedign]

well

r,vr_70,SensorData,default *r,,52,b523,03,s1,s,D2C,16,°C,Temperatur,s2,s,D2C,16,°C,Temperatur,s3,s,D2C,16,°C,Temperatur,s4,s,D2C,16,°C,Temperatur,s5,s,D2C,16,°C,Temperatur,s6,s,D2C,16,°C,Temperatur,ignore,s,HEX:3,,,
r,vr_71,SensorData1,default *r,,26,b523,06,s1,s,D2C,16,°C,Temperatur,s2,s,D2C,16,°C,Temperatur,s3,s,D2C,16,°C,Temperatur,s4,s,D2C,16,°C,Temperatur,s5,s,D2C,16,°C,Temperatur,s6,s,D2C,16,°C,Temperatur,s7,s,D2C,16,°C,Temperatur,ignore,s,HEX:2,,,
r,vr_71,SensorData2,default *r,,26,b523,07,s8,s,D2C,16,°C,Temperatur,s9,s,D2C,16,°C,Temperatur,s10,s,D2C,16,°C,Temperatur,s11,s,D2C,16,°C,Temperatur,s12,s,D2C,16,°C,Temperatur,sx,s,D2C,16,°C,Temperatur,ignore,s,HEX:3,,,

[JonesGW-MGD]

(The VR_70s propagate very little data by the way - just sensor data of temperatures - there are messages that are writable to then control the desired Flow temperature that they presumably get from the VR92s)

I suppose I should have asked a bit more about the set-up. So 6 heating circuits - does the VR71 link to 2 or 3 circuits (two I'm guessing if you are missing 4?) and then the VR70s 2 and 2? The VRC720 (branded SENSOComfort?) controls 2 or 3 zones? and each VR92 (branded SENSOHome?) control 2 each (or 2 and 1)?

I'm really sort of guessing here but

If you ebusctl read -f -V SensorData ebusctl read -f -V SensorData1 and ebusctl read -f -V SensorData2 do you get temperature data back from the zone sensors that look sensible / complete or does it look like some zone/circuits are missing?

The VR92s don't load any files - and that's because there aren't any in the repository. I would perhaps have assumed they are slaved to the 720 and therefore that would report all the settings under the 720 data but I'm not sure how it could as there aren't message definitions for say Hc4. I guess you can confirm this by running say ebusctl find -f -V Hc and see what you get back?

BTW - do you run the config files locally or does ebusd point to the server repository?

[peedign]

The VR_70s propagate very little data by the way - just sensor data of temperatures - there are messages that are writable to then control the desired Flow temperature that they presumably get from the VR92s)

Exactly

I suppose I should have asked a bit more about the set-up. So 6 heating circuits - does the VR71 link to 2 or 3 circuits (two I'm guessing if you are missing 4?) and then the VR70s 2 and 2? The VRC720 (branded SENSOComfort?) controls 2 or 3 zones? and each VR92 (branded SENSOHome?) control 2 each (or 2 and 1)?

Great guessing.

• VR71 + VR720 (=Sensocomfort)->2 HC
• VR70 + VR92 -> 2 HC
• VR70 + VR92 -> 2 HC

If you ebusctl read -f -V SensorData ebusctl read -f -V SensorData1 and ebusctl read -f -V SensorData2 do you get temperature data back from the zone sensors that look sensible / complete or does it look like some zone/circuits are missing?

I might be wrong but as per the response this tells me, that there are 2xVR71 + VR70 but it is the other way around: 2xVR70+VR71

`2ad9b828-ebusd:/# ebusctl read -f -V SensorData
vr_70 SensorData s1=- °C [Temperatur];s2=- °C [Temperatur];s3=- °C [Temperatur];s4=- °C [Temperatur];s5=38.06 °C [Temperatur];s6=35.38 °C [Temperatur];ignore=c8 41 00

2ad9b828-ebusd:/# ebusctl read -f -V SensorData1
vr_71 SensorData1 s1=48.25 °C [Temperatur];s2=39.38 °C [Temperatur];s3=31.56 °C [Temperatur];s4=- °C [Temperatur];s5=- °C [Temperatur];s6=- °C [Temperatur];s7=- °C [Temperatur];ignore=40 01

2ad9b828-ebusd:/# ebusctl read -f -V SensorData2
vr_71 SensorData2 s8=- °C [Temperatur];s9=- °C [Temperatur];s10=- °C [Temperatur];s11=- °C [Temperatur];s12=0.00 °C [Temperatur];sx=8.00 °C [Temperatur];ignore=80 57 05`

The VR92s don't load any files - and that's because there aren't any in the repository. I would perhaps have assumed they are slaved to the 720 and therefore that would report all the settings under the 720 data but I'm not sure how it could as there aren't message definitions for say Hc4. I guess you can confirm this by running say ebusctl -f -V Hc and see what you get back?

2ad9b828-ebusd:/# ebusctl -f -V Hc invalid argument -f

BTW - do you run the config files locally or does ebusd point to the server repository?

I did nothing with any config file and I cannot seem to find a single ebusd folder in HA.As far as I could understand from 24.1 the default solution is the server repo. Hence I believe I'm using the server repository.

[JonesGW-MGD]

No actually, each VR70 has a single field called SensorData, while the VR71 has two fields, one called SensorData1 and the other SensorData2. Sorry for confusing you!

And sorry duff information on the bust ebusctl command - meant to type ebusctl find -f -V Hc (now corrected in original too)

Are you using HA with the 'LukasGrebe' ebusd add-on? if so maybe post a pic of the configuration tab?

Am happy to keep helping but I'm doing a bit of guess work as I'm by no means an ebusd wizard. My thought process was that the scan process loaded the vr70 file - once loaded, it would apply to any messages from the vr70 at address 53 as well as 52 but it is only displaying 2 temperatures not 4, so I figure not.

I think therefore you could fix that but it involves cloning the configurations files, storing these locally, and pointing --configpath to them - it's not rocket science but takes a bit of effort. Then, I presume you can create a copy of 52.vr_72.csv and rename 53.vr_72.csv - these should then get loaded by the second VR_70 and my expectation would be if you ran the ebusctl read -f -V SensorData again, you'd get two lines in response not 1.

But ultimately I don't think the VR70 s are that interesting - it seems you need to see the data from the SENSOHome VR92s.

The process could be similar - pick a similar controller file - the same one from the SENSOComfort might do - 15.700.csv and rename it 35.VR_92.csv and 75.VR_92.csv - you might get a load of garbage messages but I suspect you might get Hc1 and Hc2 info from the 35 and 75 addresses - being each of these's devices 2 circuits - it might not work and its not a 10 minute job but you probably won' break anything and it would be reversible of course!

[peedign]

meant to type ebusctl find -f -V Hc

r5,ctlv2,Hc3HeatCurveAdaption,Anpassung Heizkurve Heizkreis 3,,15,b524,020002021c00,value,s,IGN:4,,,,value,s,EXP,,,adaption applied to heating curve of Hc3 r5,ctlv2,Hc3MaxFlowTempDesired,MaxFlowTempDesired Heizkreis 3,,15,b524,020002021000,value,s,IGN:4,,,,value,s,EXP,,°C,maximum flow temperature setpoint (end emphasis) of Hc3 r5,ctlv2,Hc3MinCoolingTempDesired,MinCoolingTempDesired Heizkreis 3,,15,b524,020002021100,value,s,IGN:4,,,,value,s,EXP,,°C,minimum cooling temperature setpoint Hc3 r5,ctlv2,Hc3MinFlowTempDesired,MinFlowTempDesired Heizkreis 3,,15,b524,020002021200,value,s,IGN:4,,,,value,s,EXP,,°C,minimum flow temperature setpoint (end emphasis) of Hc3 r,ctlv2,Hc3MixerMovement,MixerMovement Heizkreis 3,,15,b524,020002021a00,value,s,IGN:4,,,,value,s,EXP,,,"status of mixer (<0 closing, >0 opening)" r5,ctlv2,Hc3PumpStatus,PumpStatus Heizkreis 3,,15,b524,020002021e00,value,s,IGN:4,,,,value,s,UIN,,,pump status of zone 3 r5,ctlv2,Hc3RoomTempSwitchOn,RoomTempSwitchOn Heizkreis 3,,15,b524,020002021500,value,s,IGN:4,,,,value,s,UIN,0=off;1=modulating;2=thermostat,,room temperature modulation of Hc3 r5,ctlv2,Hc3Status,Status Heizkreis 3,,15,b524,020002021b00,value,s,IGN:4,,,,value,s,UCH,,,Ladepumpe Nachlaufzeit r5,ctlv2,Hc3SummerTempLimit,AT-Abschaltgrenze Heizkreis 3,,15,b524,020002021400,value,s,IGN:4,,,,value,s,EXP,,°C,if outside temperature > summer limit => heating is OFF;applies to comfort and night setback setpoint r5,ctlv2,HcStorageTempBottom,"Temp.fühler Hz, unten",,15,b524,02000000a000,value,s,IGN:4,,,,value,s,EXP,,°C,"Temp.fühler Hz, unten" r5,ctlv2,HcStorageTempTop,"Temp.fühler Hz, oben",,15,b524,020000009f00,value,s,IGN:4,,,,value,s,EXP,,°C,"Temp.fühler Hz, oben" r5,ctlv2,PrEnergySumHc,TotalEConsumptionHc,,15,b524,020000005700,value,s,IGN:4,,,,value,s,ULG,,kWh,Stromverbrauch Heizung gesamt r5,ctlv2,PrEnergySumHcLastMonth,LastMonthsEConsumptionHc,,15,b524,020000005300,value,s,IGN:4,,,,value,s,ULG,,kWh,Letzter Monat Stromverbrauch Heizung r5,ctlv2,PrEnergySumHcThisMonth,ThisMonthsEConsumptionHc,,15,b524,020000004f00,value,s,IGN:4,,,,value,s,ULG,,kWh,Aktueller Monat Stromverbrauch Heizung r,ctlv2,PrFuelSumHc,TotalFConsumptionHc,,15,b524,020000005600,value,s,IGN:4,,,,value,s,ULG,,kWh,Brennstoffverbrauch Heizung gesamt r,ctlv2,PrFuelSumHcLastMonth,LastMonthsFConsumptionHc,,15,b524,020000005200,value,s,IGN:4,,,,value,s,ULG,,kWh,Letzter Monat Brennstoffverbrauch Heizung r,ctlv2,PrFuelSumHcThisMonth,ThisMonthsFConsumptionHc,,15,b524,020000004e00,value,s,IGN:4,,,,value,s,ULG,,kWh,Aktueller Monat Brennstoffverbrauch Heizung r5,hmu,EnergyHc,default *r,,08,b51a,05ff3200,value,s,IGN:3,,,,value,s,UIN,,kWh, r5,hmu,HoursHc,default *r,,08,b51a,05ff3241,value,s,IGN:3,,,,value,s,UIN,,kWh,

Are you using HA with the 'LukasGrebe' ebusd add-on? if so maybe post a pic of the configuration tab?

Correct!

scanconfig: true loglevel_all: notice mqtttopic: ebusd mqttint: /etc/ebusd/mqtt-hassio.cfg mqttjson: true network_device: ens:[192.168.0.30:9999](http://192.168.0.30:9999/) latency: 10 pollinterval: 5 http: true

Based on your inputs and some search in the discussions, in summary: I would need to link the proper CSVs in my config files. As there are continuous improvements in the config files, I would prefer to use the online config files, instead of local copies. Is it possible at all?

I might be wrong but I believe these CSVs should be linked to the slaves to see the missing data including the 4 missing HCs (I did some furhter search in the discussions for ie VR92/Sensohome).

Would this approach makes sense? Is there a way to link the online config files instead of local copy? Could you please point me to the right direction for this in the documentation if it is possible at all?

or if you say that local config is easiest/only option I am happy to go that way ! :)

[JonesGW-MGD]

Hi, there are a few things about your installation I don't fully understand which is probably a good indication not to follow my advice!

When you posted your ebusctl info initially, your VR 68 solar controller isn't listed. Could it have been off and therefore not broadcasting on the bus? In any event, when it was attached to the bus, I would have expected the scan process to load ec.sol.sc.csv automatically - it's a valid file in the repository at a valid address, maybe review the logs at startup for any errors?

Similarly for the device at address 76 (is this a 'hydraulic unit'?) - I would have already expected it to load 76.vwz.csv - again maybe the logs show an error?

AFAIK, ebusd cannot match configuration files without matching address and ID - so it will not load 52.vr_70.csv for a vr_70 at address 53. For that I believe you'd have to clone the files locally and copy 52.vr_70.csv to 53.vr_70.csv. (Even then - I'm not sure you won't have to edit one file and create a different circuit name so you can distinguish the data between the two units or whether you'll be able to distinguish based on address (My approach would be trial and error!))

You do not want to load VR_71 files for VR 92 devices as they are not the same thing - the VR 71 is a wiring centre and the VR 92 a controller. There is no VR_92 files but there are VRT 380 files which are SENSOHome Units - it may be you can use these appropriately renamed (again my usual approach is to wade in with some trial and error)

I'm surprised that when you ran ebusctl find -f -V Hc the list you displayed was the full result set.

So all in all - I not offering many answers or solutions!