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
Copy file name to clipboardExpand all lines: source/_integrations/modbus.markdown
+23-10Lines changed: 23 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -372,6 +372,8 @@ modbus entities are grouped below each modbus communication entry.
372
372
373
373
All modbus entities have the following parameters:
374
374
375
+
Please refer to [Parameter usage](#parameters-usage-matrix) for conflicting parameters.
376
+
375
377
{% configuration %}
376
378
address:
377
379
description: "Address of coil/register."
@@ -460,6 +462,7 @@ For that reason, many devices (especially older ones) do not share the coil addr
460
462
and this `input` would read from a different address space than `coil`. The problem is present in devices with
461
463
shared address space and are a frequent cause of problems when configuring entities.
462
464
465
+
Please refer to [Parameter usage](#parameters-usage-matrix) for conflicting parameters.
463
466
464
467
{% configuration %}
465
468
binary_sensors:
@@ -551,6 +554,8 @@ The master configuration like device_class are automatically copied to the slave
551
554
552
555
The Modbus climate platform allows you to monitor a thermostat or heaters as well as set a target temperature.
553
556
557
+
Please refer to [Parameter usage](#parameters-usage-matrix) for conflicting parameters.
558
+
554
559
{% configuration %}
555
560
climates:
556
561
description: "A list of all climate entities in this modbus instance."
@@ -773,6 +778,8 @@ Cover that uses `input_type: coil` is not able to determine intermediary states
773
778
774
779
If your cover uses `input_type: holding` (default) to send commands, it can also read the intermediary states. To adjust which value represents what state, you can fine-tune the optional state attributes, like `state_open`. These optional state values are also used for specifying values written into the register. If you specify an optional status_register attribute, cover states will be read from status_register instead of the register used for sending commands.
775
780
781
+
Please refer to [Parameter usage](#parameters-usage-matrix) for conflicting parameters.
782
+
776
783
{% configuration %}
777
784
covers:
778
785
description: "A list of all cover entities configured for this connection."
@@ -958,6 +965,7 @@ modbus:
958
965
959
966
The `modbus` fan platform allows you to control [Modbus](http://www.modbus.org/) coils or registers.
960
967
968
+
Please refer to [Parameter usage](#parameters-usage-matrix) for conflicting parameters.
961
969
962
970
{% configuration %}
963
971
fans:
@@ -1064,6 +1072,8 @@ modbus:
1064
1072
1065
1073
The `modbus` light platform allows you to control [Modbus](http://www.modbus.org/) coils or registers.
1066
1074
1075
+
Please refer to [Parameter usage](#parameters-usage-matrix) for conflicting parameters.
1076
+
1067
1077
{% configuration %}
1068
1078
lights:
1069
1079
description: "A list of all light entities in this modbus instance."
@@ -1170,6 +1180,7 @@ modbus:
1170
1180
1171
1181
The `modbus` sensor allows you to gather data from [Modbus](http://www.modbus.org/) registers.
1172
1182
1183
+
Please refer to [Parameter usage](#parameters-usage-matrix) for conflicting parameters.
1173
1184
1174
1185
{% configuration %}
1175
1186
sensors:
@@ -1359,6 +1370,8 @@ modbus:
1359
1370
1360
1371
The `modbus` switch platform allows you to control [Modbus](http://www.modbus.org/) coils or registers.
1361
1372
1373
+
Please refer to [Parameter usage](#parameters-usage-matrix) for conflicting parameters.
1374
+
1362
1375
{% configuration %}
1363
1376
switches:
1364
1377
description: "A list of all switches in this modbus instance."
@@ -1490,19 +1503,19 @@ modbus:
1490
1503
state_off: 1
1491
1504
```
1492
1505
1493
-
## Parameters usage matrix:
1506
+
## Parameters usage matrix
1494
1507
1495
1508
Some parameters exclude other parameters, the following tables show what can be combined:
0 commit comments