Add 15.b7s00.tsp for Vaillant Mipro R (B7S00) - OEM alias of VRC 700

[lsteelandt]

Description

Adds a new TypeSpec file for the Vaillant Mipro R (B7S00), which is an OEM variant of the VRC 700 controller.

The B7S00 returns the following eBUS scan result:

scan 15: ;Vaillant;B7S00;SW0422;HW5503

Since the B7S00 is functionally identical to the VRC 700 (70000), this file simply extends _700 namespace without any modifications.

Motivation

Without this file, ebusd reports:

unable to load scan config 15: no file from vaillant with prefix 15 matches ID "b7s00"

This prevents loading of the 467 messages defined in 15.700.tsp (including WaterPressure, heating schedules, etc.) for users with a Mipro R unit.

[cray19003]

Hello,

I have exactly the same case on my installation.

My setup:

• Saunier Duval / Vaillant system
• MiPro R downstairs + MiPro R remote upstairs
• DHW + 2 heating zones
• VR_70 module
• VWZ00 module
• eBUS Stick C6 in ENS / enhanced TCP mode
• ebusd add-on on Home Assistant
• ebusd version: 26.1.26.1
• configpath: https://ebus.github.io/
• scanconfig: full

My ebusd command line is:

ebusd --foreground --updatecheck=off --mqtthost=core-mosquitto --mqttport=1883 --mqttuser= --mqttpass= -d ens:192.168.1.182:9999 --configpath=https://ebus.github.io/ --scanconfig=full --accesslevel=* --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd_clean

The main devices are detected and loaded correctly:

address 08: slave, scanned "MF=Vaillant;ID=HMU00;SW=0517;HW=5103", loaded "vaillant/08.hmu.HW5103.csv"
address 52: slave, scanned "MF=Vaillant;ID=VR_70;SW=0109;HW=2903", loaded "vaillant/52.vr_70.csv"
address 76: slave, scanned "MF=Vaillant;ID=VWZ00;SW=0405;HW=5103", loaded "vaillant/76.vwz.csv"

But the MiPro R appears as B7S00 and no config is loaded:

address 15: slave, scanned "MF=Vaillant;ID=B7S00;SW=0422;HW=5503"
address ec: slave, scanned "MF=Vaillant;ID=B7S00;SW=0422;HW=5503"

Because of this, I do not get the MiPro R / MiPro R remote data in Home Assistant:

• room temperatures
• room setpoints
• zone 1 / zone 2 modes
• heating schedules
• other VRC700/MiPro controller data

I also checked with:

ebusctl find -a | grep -i -E "ctl|mipro|room|zone|hc|desired|setpoint|remote|b7"

and I only get:

hmu CompressorHc = no data stored (message not available due to condition)
hmu CopHc = no data stored
hmu CopHcMonth = no data stored
hmu RunStatsHcHours = 16969
hmu YieldHc = 23549
hmu YieldHcDay = 0.0
hmu YieldHcMonth = 0.0
scan.15 = Vaillant;B7S00;0422;5503
scan.ec = Vaillant;B7S00;0422;5503

So this PR seems to match my case exactly.

Is there a way to test the proposed 15.b7s00.tsp file locally with the Home Assistant ebusd add-on, or do I need to wait until it is merged and published to https://ebus.github.io/?

I can provide additional logs or raw unknown messages if needed.

[cray19003]

Update:

I checked the published ebus.github.io configuration.

The VRC700 file exists:

curl -s -o /dev/null -w "%{http_code}\n" https://ebus.github.io/en/vaillant/15.700.csv
=> 200

But the B7S00 alias/config does not exist in stable or next:

curl -s -o /dev/null -w "%{http_code}\n" https://ebus.github.io/en/vaillant/15.b7s00.csv
=> 404

curl -s -o /dev/null -w "%{http_code}\n" https://ebus.github.io/next/en/vaillant/15.b7s00.csv
=> 404

So ebusd still detects my MiPro R as:

address 15: slave, scanned "MF=Vaillant;ID=B7S00;SW=0422;HW=5503"
address ec: slave, scanned "MF=Vaillant;ID=B7S00;SW=0422;HW=5503"

but no config is loaded for address 15.

It looks like 15.700.csv is available, but the B7S00 -> VRC700 mapping/alias is not yet published.

Is there a recommended way to test this locally with the Home Assistant ebusd add-on, or should I wait until the B7S00 mapping is merged and published?