From 5e54390bf0e5c9b68e9dbf035e302f0b291290d3 Mon Sep 17 00:00:00 2001 From: Claudio Ruggeri - CR-Tech <41435902+crug80@users.noreply.github.com> Date: Mon, 18 Mar 2024 11:00:19 +0100 Subject: [PATCH] Update documentation to reflect modBusTTRegisters changes (#30616) * Update documentation to reflect modBusTTRegisters changes (possibility to define different setpoint registers belonging to HVAC Mode * Clarified misunderstanding beetwen values and registers as requested by the maintainer * Updated doc to reflect code changes * Simplified the description as suggested * Update source/_integrations/modbus.markdown Co-authored-by: jan iversen --------- Co-authored-by: jan iversen --- source/_integrations/modbus.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/modbus.markdown b/source/_integrations/modbus.markdown index d54a70cb14b..f68fd5ff21f 100644 --- a/source/_integrations/modbus.markdown +++ b/source/_integrations/modbus.markdown @@ -737,9 +737,9 @@ climates: word_byte: description: "Swap word ABCD -> DCBA, **not valid with data types: `int16`, `uint16`**" target_temp_register: - description: "Register address for target temperature (Setpoint)." + description: "Register address for target temperature (Setpoint). Using a list, it is possible to define one register for each of the available HVAC Modes. The list has to have a fixed size of 7 registers corresponding to the 7 available HVAC Modes, as follows: Register **1: HVAC AUTO mode**; Register **2: HVAC Cool mode**; Register **3: HVAC Dry mode**; Register **4: HVAC Fan only mode**; Register **5: HVAC Heat mode**; Register **6: HVAC Heat Cool mode**; Register **7: HVAC OFF mode**. It is possible to set duplicated values for the modes where the devices has not a related register." required: true - type: integer + type: [integer, list] target_temp_write_registers: description: "If `true` use `write_registers` for target temperature." required: false