You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 19, 2024. It is now read-only.
@@ -10,51 +10,67 @@ Ideas are welcome ! Don't hesitate to create issue to suggest something, it will
10
10
**This integration is also compatible with sensoAPP and has been tested with the vr920 and vr921 devices.**
11
11
12
12
## Installations
13
+
13
14
- Through HACS [custom repositories](https://hacs.xyz/docs/faq/custom_repositories/) !
14
-
- Otherwise, download the zip from the latest release and copy `multimatic` folder and put it inside your `custom_components` folder.
15
+
- Otherwise, download the zip from the latest release and copy `multimatic` folder and put it inside
16
+
your `custom_components` folder.
15
17
16
18
You can configure it through the UI using integration.
17
-
You have to provide your username and password (same as multimatic or senso app), if you have multiple serial numbers, you can choose for which number serial number you want the integration.
19
+
You have to provide your username and password (same as multimatic or senso app), if you have multiple serial numbers,
20
+
you can choose for which number serial number you want the integration.
18
21
You can create multiple instance of the integration with different serial number (**This is still a beta feature**).
19
22
20
23
**It is strongly recommended using a dedicated user for HA**, for 2 reasons:
24
+
21
25
- As usual for security reason, if your HA got compromised somehow, you know which user to block
22
26
- I cannot confirm it, but it seems multimatic and senso API only accept the same user to be connected at the same time
23
27
24
28
## Changelog
29
+
25
30
See [releases details](https://github.com/thomasgermain/vaillant-component/releases)
31
+
26
32
## Provided entities
33
+
27
34
- 1 water_heater entity, if any water heater: `water_heater.<water heater id>`, basically `water_heater.control_dhw`
28
35
- 1 climate entity per zone (expect if the zone is controlled by room) `climate.<zone id>`
29
36
- 1 climate entity per room `climate.<room name>`
30
-
- 1 fan entity `fan.<ventilation_id>`
37
+
- 1 fan entity `fan.<ventilation_id>`
31
38
- 1 binary_sensor entity `binary_sensor.control_dhw` reflecting if the circulation is on or off
32
-
- 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)
39
+
- 1 binary_sensor entity `climate.<room name>_window` per room reflecting the state of the "open window" in a room (this
40
+
is a feature of the multimatic API, if the temperature is going down pretty fast, the API assumes there is an open
41
+
window and heating stops)
33
42
- 1 binary_sensor entity `climate.<sgtin>_lock`per device reflecting if valves are "child locked" or not
34
-
- 1 binary_sensor entity `binary_sensor.<sgtin>_battery` reflecting battery level for each device (VR50, VR51) in the system
35
-
- 1 binary_sensor entity `binary_sensor.<sgtin>_battery` reflecting connectivity for each device (VR50, VR51) in the system
43
+
- 1 binary_sensor entity `binary_sensor.<sgtin>_battery` reflecting battery level for each device (VR50, VR51) in the
44
+
system
45
+
- 1 binary_sensor entity `binary_sensor.<sgtin>_battery` reflecting connectivity for each device (VR50, VR51) in the
46
+
system
36
47
- 1 binary_sensor entity `binary_sensor.multimtic_system_update`to know if there is an update pending
37
48
- 1 binary_sensor entity `binary_sensor.multimtic_system_online` to know if the vr900/920 is connected to the internet
38
-
- 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.**
49
+
- 1 binary_sensor entity `binary_sensor.<boiler model>` to know if there is an error at the boiler. **Some boiler does
50
+
not provide this information, so entity won't be available.**
39
51
- 1 temperature sensor `sensor.outdoor_temperature` for outdoor temperature
40
52
- 1 sensor for each report in live_report (boiler temperature, boiler water pressure, etc.)
41
53
- 1 binary sensor `binary_sensor.multimtic_quick_mode` to know a quick mode is running on
42
54
- 1 binary sensor ` binary_sensor.multimtic_holiday` to know the holiday mode is on/off
43
-
- 1 binary sensor `binary_sensor.multimatic_errors`indicating if there are errors coming from the API (if `on`, details are in `state_attributes`)
55
+
- 1 binary sensor `binary_sensor.multimatic_errors`indicating if there are errors coming from the API (if `on`, details
56
+
are in `state_attributes`)
44
57
45
58
## Provided devices
59
+
46
60
- 1 device per VR50 or VR51
47
-
- 1 device for the boiler (if supported). Some boilers don't provide enough information to be able to create a device in HA.
61
+
- 1 device for the boiler (if supported). Some boilers don't provide enough information to be able to create a device in
62
+
HA.
48
63
- 1 device for the gateway (like VR920)
49
64
- 1 "multimatic" (VRC700) device (the water pressure is linked to the VRC 700 inside the multimatic API)
50
65
- hot water circuit
51
66
- heating circuit
52
67
68
+
For the climate and water heater entities, you can also find
53
69
54
-
For the climate and water heater entities, you can also find
55
70
- the 'real multimatic mode' running on (AUTO, MANUAL, DAY, etc)
56
71
57
-
For the boiler error entity, you can also find
72
+
For the boiler error entity, you can also find
73
+
58
74
- the last update (this is not the last HA update, this is the last time multimatic checks the boiler)
59
75
- the status code (these can be found in your documentation)
60
76
- the title (human-readable description of the status code)
@@ -63,56 +79,97 @@ For the `binary_sensor.multimtic_quick_mode`, when on, you have the current quic
63
79
For the `binary_sensor.multimtic_holiday`, when on, you have the start date, end date and target temperature
64
80
65
81
## Provided services
82
+
66
83
-`multimatic.set_holiday_mode` to set the holiday mode (see services in HA ui to get the params)
67
84
-`multimatic.remove_holiday_mode` .. I guess you get it
68
85
-`multimatic.set_quick_mode` to set a quick mode
69
-
-`multimatic.remove_quick_mode` don't tell me you don't get it
86
+
-`multimatic.remove_quick_mode` don't tell me you don't get it
70
87
-`multimatic.set_quick_veto` to set a quick veto for a climate entity
71
88
-`multimatic.remove_quick_veto` to remove a quick veto for a climate entity
72
-
-`multimatic.request_hvac_update` to tell multimatic API to fetch data from your installation and made them available in the API
89
+
-`multimatic.request_hvac_update` to tell multimatic API to fetch data from your installation and made them available
90
+
in the API
73
91
-`multimatic.set_ventilation_day_level` to set ventilation day level
74
92
-`multimatic.set_ventilation_night_level` to set ventilation night level
75
93
-`multimatic.set_datetime` to set the current date time of the system
76
94
77
95
This will allow you to create some buttons in UI to activate/deactivate quick mode or holiday mode with a single click
78
96
79
-
80
97
## Expected behavior
81
98
82
-
On **room** climate:
99
+
### Room climate
100
+
101
+
#### Changing temperature
83
102
84
-
Changing temperature while ...
85
103
-`MANUAL` mode -> it simply changes target temperature
86
-
- other modes -> it creates a quick_veto (duration = 3 hours) (it's also removing holiday or quick mode)
87
-
88
-
Modes mapping:
89
-
-`AUTO` -> `HVAC_MODE_AUTO` & `PRESET_COMFORT`
90
-
-`OFF` -> `HVAC_MODE_OFF` & no preset
91
-
-`QUICK_VETO` -> hvac depends on state & `PRESET_QUICK_VETO` (custom)
0 commit comments