From 98ce229151ff46054d53b541dc6c159cc64ac11e Mon Sep 17 00:00:00 2001
From: XLDom <90308906+XLDom@users.noreply.github.com>
Date: Wed, 18 Oct 2023 11:56:08 +0200
Subject: [PATCH] Update file-format.md

---
 docs/config-files/file-format.md | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/docs/config-files/file-format.md b/docs/config-files/file-format.md
index 6e67a79a7a49..54b60c499ee2 100644
--- a/docs/config-files/file-format.md
+++ b/docs/config-files/file-format.md
@@ -503,13 +503,9 @@ By default, `Basic CC::Set` commands are interpreted as status updates. This fla
 
 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.
 
-### `treatBinarySwitchSetAsReport`
+### `treatSetAsReport`
 
-By default, `BinarySwitch CC::Set` are not reporting as Value. This flag causes the driver to emit a `value report`.
-
-### `treatThermostatModeSetAsReport`
-
-By default, `ThermostatMode CC::Set` are not reporting as Value. This flag causes the driver to emit a `value report`.
+By default, `treatSetAsReport CC::Set` are not reporting as Value. This flag causes the driver to emit a `value report`. treatSetAsReport is array of string (e.g. ["BinarySwitchCCSet", "ThermostatModeCCSet"])
 
 ### `treatDestinationEndpointAsSource`