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 <jancasacondor@gmail.com>

---------

Co-authored-by: jan iversen <jancasacondor@gmail.com>
This commit is contained in:
Claudio Ruggeri - CR-Tech 2024-03-18 11:00:19 +01:00 committed by GitHub
parent 1221221e6f
commit 5e54390bf0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -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