From 398de14f98b671c4f97efc69247b124e3268284f Mon Sep 17 00:00:00 2001 From: Dominic Griesel Date: Mon, 14 Mar 2022 15:32:45 +0100 Subject: [PATCH] docs: explain compat flag --- docs/config-files/file-format.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/config-files/file-format.md b/docs/config-files/file-format.md index f5c525e8ac13..679ce2439901 100644 --- a/docs/config-files/file-format.md +++ b/docs/config-files/file-format.md @@ -397,11 +397,15 @@ Some devices spam the network with hundreds of invalid `ConfigurationCC::InfoRep ### `treatBasicSetAsEvent` -By default, `Basic CC::Set` commands are interpreted as status updates. This flag causes the driver to emit a `value event` for the `"value"` property instead. Note that this property is exclusively used in this case in order to avoid conflicts with regular value IDs. +By default, `Basic CC::Set` commands are interpreted as status updates. This flag causes the driver to emit a `value event` for the `"event"` property instead. Note that this property is exclusively used in this case in order to avoid conflicts with regular value IDs. > [!NOTE] > If this option is `true`, it has precedence over `disableBasicMapping`. +### `treatMultilevelSwitchSetAsEvent` + +By default, `Multilevel Switch CC::Set` commands are ignored, because they are meant to control end devices. This flag causes the driver to emit a `value event` for the `"event"` property instead, so applications can react to these commands, e.g. for remotes. + ### `treatDestinationEndpointAsSource` Some devices incorrectly use the multi channel **destination** endpoint in reports to indicate the **source** endpoint the report originated from. When this flag is `true`, the destination endpoint is instead interpreted to be the source and the original source endpoint gets ignored.