Multimatic integration

Please note that this integration is still in beta test, so I may do (unwanted) breaking changes.

Ideas are welcome ! Don't hesitate to create issue to suggest something, it will be really appreciated.

This integration is NOT compatible with sensoAPP, only with multiMATIC app.

Installations

• Through HACS custom repositories !
• Otherwise, download the zip from the latest release and copy multimatic folder and put it inside your custom_components folder.

You can configure it through the UI using integration. You have to provide your username and password (same as multimatic app), if you have multiple serial numbers, you can choose for which number serial number you want the integration. You can create multiple instance of the integration with different serial number (This is still a beta feature).

It is strongly recommended using a dedicated user for HA, for 2 reasons:

• As usual for security reason, if your HA got compromised somehow, you know which user to block
• I cannot confirm it, but it seems multimatic API only accept the same user to be connected at the same time

Changelog

See releases details

Provided entities

• 1 water_heater entity, if any water heater: water_heater.<water heater id>, basically water_heater.control_dhw
• 1 climate entity per zone (expect if the zone is controlled by room) climate.<zone id>
• 1 climate entity per room climate.<room name>
• 1 fan entity fan.<ventilation_id>
• 1 binary_sensor entity binary_sensor.control_dhw reflecting if the circulation is on or off
• 1 binary_sensor entity climate.<room name>_window per room reflecting the state of the "open window" in a room (this is a feature of the multimatic API, if the temperature is going down pretty fast, the API assumes there is an open window and heating stops)
• 1 binary_sensor entity climate.<sgtin>_lockper device reflecting if valves are "child locked" or not
• 1 binary_sensor entity binary_sensor.<sgtin>_battery reflecting battery level for each device (VR50, VR51) in the system
• 1 binary_sensor entity binary_sensor.<sgtin>_battery reflecting connectivity for each device (VR50, VR51) in the system
• 1 binary_sensor entity binary_sensor.multimtic_system_updateto know if there is an update pending
• 1 binary_sensor entity binary_sensor.multimtic_system_online to know if the vr900/920 is connected to the internet
• 1 binary_sensor entity binary_sensor.<boiler model> to know if there is an error at the boiler. Some boiler does not provide this information, so entity won't be available.
• 1 temperature sensor sensor.outdoor_temperature for outdoor temperature
• 1 sensor for each report in live_report (boiler temperature, boiler water pressure, etc.)
• 1 binary sensor binary_sensor.multimtic_quick_mode to know a quick mode is running on
• 1 binary sensor binary_sensor.multimtic_holiday to know the holiday mode is on/off
• 1 binary sensor binary_sensor.multimatic_errorsindicating if there are errors coming from the API (if on, details are in state_attributes)

Provided devices

• 1 device per VR50 or VR51
• 1 device for the boiler (if supported). Some boilers don't provide enough information to be able to create a device in HA.
• 1 device for the gateway (like VR920)
• 1 "multimatic" (VRC700) device (the water pressure is linked to the VRC 700 inside the multimatic API)
• hot water circuit
• heating circuit

For the climate and water heater entities, you can also find

• the 'real multimatic mode' running on (AUTO, MANUAL, DAY, etc)

For the boiler error entity, you can also find

• the last update (this is not the last HA update, this is the last time multimatic checks the boiler)
• the status code (these can be found in your documentation)
• the title (human-readable description of the status code)

For the binary_sensor.multimtic_quick_mode, when on, you have the current quick mode name is available For the binary_sensor.multimtic_holiday, when on, you have the start date, end date and target temperature

Provided services

• multimatic.set_holiday_mode to set the holiday mode (see services in HA ui to get the params)
• multimatic.remove_holiday_mode .. I guess you get it
• multimatic.set_quick_mode to set a quick mode
• multimatic.remove_quick_mode don't tell me you don't get it
• multimatic.set_quick_veto to set a quick veto for a climate entity
• multimatic.remove_quick_veto to remove a quick veto for a climate entity
• multimatic.request_hvac_update to tell multimatic API to fetch data from your installation and made them available in the API
• multimatic.set_ventilation_day_level to set ventilation day level
• multimatic.set_ventilation_night_level to set ventilation night level

This will allow you to create some buttons in UI to activate/deactivate quick mode or holiday mode with a single click

Expected behavior

On room climate:

Changing temperature while ...

• MANUAL mode -> it simply changes target temperature
• other modes -> it creates a quick_veto (duration = 3 hours) (it's also removing holiday or quick mode)

Modes mapping:

• AUTO -> HVAC_MODE_AUTO & PRESET_COMFORT
• OFF -> HVAC_MODE_OFF & no preset
• QUICK_VETO -> no hvac & PRESET_QUICK_VETO (custom)
• QM_SYSTEM_OFF -> HVAC_MODE_OFF & PRESET_SYSTEM_OFF (custom)
• HOLIDAY -> HVAC_MODE_OFF & PRESET_HOLIDAY (custom)
• MANUAL -> no hvac & PRESET_MANUAL (custom)

On zone climate:

• Changing temperature will lead to a quick veto with selected temperature for 6 hours (quick veto duration is not configurable for a zone)

Modes mapping:

Vaillant Mode	HA Mode
AUTO	HVAC_MODE_AUTO & PRESET_COMFORT
DAY	no hvac & PRESET_DAY (custom)
NIGHT	no hvac & PRESET_SLEEP
OFF	HVAC_MODE_OFF & no preset
ON (= cooling ON)	no hvac & PRESET_COOLING_ON (custom)
QUICK_VETO	no hvac & PRESET_QUICK_VETO (custom)
QM_ONE_DAY_AT_HOME	HVAC_MODE_AUTO & PRESET_HOME
QM_PARTY	no hvac & PRESET_PARTY (custom)
QM_VENTILATION_BOOST	HVAC_MODE_FAN_ONLY & no preset
QM_ONE_DAY_AWAY	HVAC_MODE_OFF & PRESET_AWAY
QM_SYSTEM_OFF	HVAC_MODE_OFF & PRESET_SYSTEM_OFF (custom)
HOLIDAY	HVAC_MODE_OFF & PRESET_HOLIDAY (custom)
QM_COOLING_FOR_X_DAYS	no hvac & PRESET_COOLING_FOR_X_DAYS

---