readme

README.md

@@ -19,14 +19,15 @@ The adapter supports an interface towards the heating systems from Bosch Group u
 ## It can interface towards the heating system with use of Web-API calls toward:
 
 * km200, km200 hrv, km100, km50, HMC300 or IP-inside (from Bosch Group) 
-* ems-esp interface (https://github.com/emsesp/EMS-ESP32) with latest dev version (see below) and the ESP32 chip. 
 
-* The old ESP8266 gateways with API V2 is NOT SUPPORTED ANYMORE !!
+* ems-esp interface (https://github.com/emsesp/EMS-ESP32) with latest dev version (see below) and the ESP32 chip. 
+  The old ESP8266 gateways with API V2 is NOT SUPPORTED ANYMORE !!
 
 The ems-esp adapter can read and write data to both gateways to steer all heating components. 
 It can be used either for the original Bosch-group gateways or the ems-esp or both in parallel.
+All changed states from own scripts or the object browser does have to set acknowledged = false !!!
 
-The adapter is tested for the ems-esp gateway with latest firmware versions of ESP32 >= v3.4.0. 
+The adapter is tested for the ems-esp gateway with latest firmware versions of ESP32 >= v3.5.1. 
 
 
 ## important settings in EMS-ESP:
@@ -50,10 +51,9 @@ This adapter reads after start values from ems-esp and km200 by http get request
 The web-api calls toward/from the km200 gateway is encrypted. For the en-/decryption there are two passords needed:
 
 * the gateway password on an label on the gateway in the form: xxxx-xxxx-xxxx-xxxx (case sensitive)
-* the private password set by using the Buderus **MyDevice** App (do not use myBuderus or similar apps !) 
-
-The fields to be used could be defined by polling the km200-structure (*) or the respective csv-file within the adapter instance parameters. 
+* the private password set by using the Buderus **MyDevice** App (do not use myBuderus / EasyCom or similar cloud based apps !) 
 
+The fields to be used for the bosch gateway could also be defined by polling the km200-structure (*) or the respective csv-file within the adapter instance parameters. 
 For 1st adapter start it is recommended to use a "*" to select all km200 data-fields.
 The adapter then creates a km200.csv file within ../iobroker-data/ems-esp/{instance} directory.