diff --git a/README.md b/README.md
index be5433e..bdca019 100644
--- a/README.md
+++ b/README.md
@@ -39,6 +39,17 @@ All our adapter documentation can be found at [The DrozmotiX Docu Page](https://
     * For admin tabs (optional)
         * ESPHome Dashboard IP is provided in instance settings
 
+## Using the built-in ESPHome Dashboard
+You can either use an external installation of ESPHome (like docker) or activate the ESPHome Dashboard process included in this adapter.  
+In any case, it is possible to integrate the dashboard into ioBroker Admin interface, for this purpose you must specify the ip where the Dashboard is running
+
+![Logo](admin/img/ESPhomeDashboardIP.png)
+
+> [!IMPORTANT]
+> is currently not possible to show the ESPHome DashBoard integrated in ioBroker when https is enabled, see [#159](https://github.com/DrozmotiX/ioBroker.esphome/issues/159)
+
+## How to use this adapter
+
 ### Activate API in YAML
 > [!IMPORTANT]
 > ioBroker ESPHome allows to integrate Devices by Encryption Key (recommended) or API-Password (legacy), 
@@ -85,7 +96,7 @@ Please enter IP-Address (if a device is already known, you can select it from th
   - Will send a message to the backend to remove this device
 
 > [!WARNING]
-> THis action will remove selected device and all its related states from ioBroker!
+> This action will remove a selected device and all its related states from ioBroker!
 
 > [!NOTE]
 > After a device has been added, a message will be indicated if successfully or error, 
diff --git a/admin/i18n/en/translations.json b/admin/i18n/en/translations.json
index d5852c3..653b4fa 100644
--- a/admin/i18n/en/translations.json
+++ b/admin/i18n/en/translations.json
@@ -13,7 +13,7 @@
     "lblConnectDetails-Line-2": "After adding an api: line to your ESPHome configuration you can go to this page and and wait for the ESPHome device to show up under the discovered devices section (can take up to 5 minutes) or add the device manually by choosing “add Device” from the devices overview and entering “<NODE_NAME>.local” or the IP address of the unit in the “Host” field.",
     "lblConnectDetails-Line-3": "The ESPHome native API is based on a custom TCP protocol using protocol buffers. You can find the protocol data structure definitions here:",
     "lblConnectIobroker": "ioBroker communicates directly by Native API instead of MQTT to provide you the best possible experience and support of encryption keys (recommend) instead of API/MQTT passwords",
-    "lblDashboardLink": "To show ESPHome dashboard in ioBroker admin tab, its required to provide the IP-Ares on which installation its running",
+    "lblDashboardLink": "To show ESPHome dashboard in ioBroker admin tab, its required to provide the IP-Ares on which installation its running. Https is currently not supported",
     "lblDefaultCredentials": "Default API / Encryption keys settings devices (not recommended)",
     "lblDefaultCredentials-Line-1": "Each devices should have its own unique encryption Key (recommended) or API password, device discovery (when enabled) detects all devices and tries to connect with credentials below",
     "lblDefaultCredentials-Line-2": "If you assign an unique encryption key (recommended) or API password, new devices will show up on Discovered Devices tab (or must be added) and you must provide the unique credentials manually",
diff --git a/admin/img/ESPhomeDashboardIP.png b/admin/img/ESPhomeDashboardIP.png
new file mode 100644
index 0000000..5ca9650
Binary files /dev/null and b/admin/img/ESPhomeDashboardIP.png differ