iobroker.esphome 0.6.3 → 0.7.0-beta.1

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2023-2025 DutchmanNL <rdrozda86@gmail.com>
+Copyright (c) 2023-2026 DutchmanNL <rdrozda86@gmail.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -30,7 +30,7 @@ Native integration of ESPHome managed device (Including Dashboard) by its native
 - 📱 [Device Management](#device-management)
 - 🔧 [Configuration Examples](#example-config)
 
-This adapter uses the [esphome-native-api](https://github.com/Nafaya/esphome-native-api#readme) with all credits to @Nafaya to interact with [ESPHome API](https://esphome.io/components/api.html?highlight=api)!
+This adapter uses the [esphome-native-api](https://github.com/twocolors/esphome-native-api#readme) with all credits to @twocolors to interact with [ESPHome API](https://esphome.io/components/api.html?highlight=api)!
 
 ## Frequently Asked Questions (FAQ)
 
@@ -57,14 +57,16 @@ The Dashboard IP setting in the adapter configuration serves different purposes:
 
 **For Integrated Dashboard Tab in ioBroker Admin:**
 1. Enter the IP address and port where your ESPHome Dashboard is running
-2. **Built-in Dashboard:** Use `127.0.0.1:6052` (default for integrated dashboard)
-3. **External Dashboard:** Use the IP:port of your external ESPHome installation (e.g., Docker container)
+2. **Built-in Dashboard:** Use the IP address of your ioBroker host (e.g., `192.168.1.10:6052`)
+   - **Important:** Do NOT use `127.0.0.1:6052` if you access ioBroker from other devices - the embedded iframe will try to reach 127.0.0.1 from the client's browser, not the ioBroker server
+   - Only use `127.0.0.1:6052` if you ONLY access ioBroker admin from the same machine where ioBroker is running
+3. **External Dashboard:** Use the IP:port of your external ESPHome installation (e.g., `192.168.1.100:6052`)
 4. **HTTPS Setup:** For HTTPS environments, see the detailed HTTPS configuration section below
 
 **Dashboard IP Examples:**
-- Built-in: `127.0.0.1:6052`
-- External Docker: `192.168.1.100:6052`
-- External Host: `esphome.local:6052`
+- Built-in (accessed from network): `192.168.1.10:6052` (replace with your ioBroker host IP)
+- Built-in (local only): `127.0.0.1:6052` (only if admin accessed on same machine)
+- External Host: `esphome.local:6052` or `192.168.1.100:6052`
 - HTTPS Proxy: `https://192.168.1.50:8082/proxy.0/esphome/`
 
 ![ESPHome Dashboard IP Configuration](admin/img/ESPhomeDashboardIP.png)
@@ -86,10 +88,43 @@ The adapter works independently and only requires devices with ESPHome API enabl
 1. **Ensure ESPHome API is enabled** in your device's YAML configuration (see Prerequisites section)
 2. **Open the adapter's device tab** in ioBroker Admin (adapter must be running)
 3. **Add devices manually:** Enter device IP address and authentication credentials
-4. **Automatic discovery:** Currently disabled (see issue #175)
+4. **Automatic discovery:** Use the autodiscovery feature if enabled in adapter settings
 
 The adapter will establish a connection and create all necessary ioBroker objects for device control.
 
+### I configured a device in the ESPHome Dashboard, but it doesn't show up in the adapter
+
+**Important:** The adapter and dashboard are completely separate components with no automatic integration. The adapter can optionally install (and start) the dashboard for you, just for convenience. Again, this does not mean there is any integration between them.
+
+- **Dashboard:** Used for creating/editing YAML configs, compiling firmware, and flashing devices
+- **Adapter:** Used for controlling devices and synchronizing their state with ioBroker
+
+**To make a dashboard-configured device work with the adapter:**
+1. Flash the device with the configuration from the dashboard (ensure ESPHome API is enabled in YAML)
+2. Manually add the device in the adapter settings (device tab). Enter IP/hostname and encryption key (recommended) or password (legacy)
+3. The adapter will then connect to the device via ESPHome's native API
+
+**Note:** Future tighter integration between dashboard and adapter may be implemented (see issue #228), but currently they operate independently.
+
+### I configured a device in the adapter, but it doesn't show up in the dashboard
+
+**This is expected behavior** - the adapter and dashboard do not automatically sync device configurations.
+
+- The **adapter** connects to devices via ESPHome's native API for control/monitoring
+- The **dashboard** manages YAML configurations and firmware compilation
+
+**If you want the device in the dashboard:**
+
+**Option 1:**
+1. The ESPHome Dashboard can discover devices in the same network automatically
+2. In the dashboard, discovered devices will show with an "ADOPT" button
+3. Click "ADOPT" to add them to your dashboard for configuration management
+
+**Option 2:**
+- Create a new device in the dashboard and copy your existing yaml into there.
+
+**Note:** You don't need devices in the dashboard if you only want to control them via ioBroker. The dashboard is only needed for creating/modifying device configurations.
+
 <!--
 ## [Documentation](https://DrozmotiX.github.io/languages/en/Adapter/ESPHome/)
 
@@ -216,6 +251,41 @@ During this process, states not part anymore of YAML configuration will be autom
 
 ![DevicesOK](admin/img/deviceTree.png)
 
+### YAML File Management
+
+The adapter provides a convenient interface for managing YAML configuration files directly from the admin UI. This feature allows you to upload, download, and manage YAML files that are stored in the ESPHome directory and can be used by the ESPHome Dashboard.
+
+#### Features
+
+- **Upload YAML Files**: Paste your YAML configuration content directly into the admin interface and upload it to the ESPHome directory
+- **View File List**: See all YAML files currently stored in the ESPHome directory with file size and modification date
+- **Download Files**: Retrieve the content of any YAML file for editing or backup
+- **Delete Files**: Remove YAML files that are no longer needed
+
+#### How to Use
+
+1. **Navigate to the "YAML Files" tab** in the adapter configuration
+2. **Upload a new file**:
+   - Enter a filename (must end with .yaml or .yml)
+   - Paste your YAML configuration content
+   - Click "Upload File"
+3. **Refresh the file list** to see all available YAML files
+4. **Download or delete files**:
+   - Enter the filename in the "Select file" field
+   - Click "Download File" to view the content or "Delete File" to remove it
+
+> [!NOTE]
+> Files are stored in the ESPHome directory: `/opt/iobroker/iobroker-data/esphome.<instance>/`
+> 
+> This is the same directory used by the ESPHome Dashboard, so files uploaded through the adapter
+> are immediately available in the Dashboard and vice versa.
+
+> [!TIP]
+> This feature is particularly useful when:
+> - You want to quickly edit configurations without accessing the server file system
+> - You need to backup or share device configurations
+> - You want to manage YAML files without running the full ESPHome Dashboard
+
 ### Example config
 Example config, for more examples see [The DrozmotiX Docu Page](https://DrozmotiX.github.io) or [ESPHome Documentation](https://esphome.io/index.html)
 
@@ -284,6 +354,19 @@ If you like my work, please consider a personal donation
     ### __WORK IN PROGRESS__
     * (DutchmanNL) 
 -->
+### 0.7.0-beta.1 (2026-02-15)
+* (@SimonFischer04) improve dashboard testing
+
+### 0.7.0-beta.0 (2026-02-15) - Improve Dashboard & allow file upload
+* (@copilot) **FIXED**: Invalid jsonConfig schema - removed unsupported `doNotSave` property from table elements
+* (@copilot) **NEW**: YAML file management interface in admin UI for upload/download/delete operations (#369)
+* (@SimonFischer04) improve logging for #201
+* (@SimonFischer04) automatic migration from versions prior to ESPHomeDashboardUrl introduction (pre v0.6.1)
+* (@SimonFischer04) update pillow
+* (@SimonFischer04) fix readme link to lib
+* (@SimonFischer04) fix connection status #311
+* (@SimonFischer04) remove unneeded node-fetch dependency
+
 ### 0.6.3 (2025-09-16)
 * (@DutchmanNL) Fixed an admin error related to `jsonConfig` validation. #287
 * (@DutchmanNL) Various general fixes and dependency updates to improve stability.
@@ -303,18 +386,10 @@ If you like my work, please consider a personal donation
 * (@DutchmanNL) Optimize backend handling of device discovery
 * (@DutchmanNL) Capability to select ESPHome Dashboard version added, resolves #118
 
-### 0.5.0-beta.8 (2023-11-24)
-* (DutchmanNL) Capability to automatically detect new devices added
-* (DutchmanNL) Ensures a compatible pillow version is used (10.0.1)
-* (SimonFischer04) Add pillow python package by default, resolves #188
-
-### 0.5.0-beta.4 (2023-11-15)
-* (DutchmanNL) Refactor memory caching of device data, resolves #189
-
 ## License
 MIT License
 
-Copyright (c) 2023-2025 DutchmanNL <rdrozda86@gmail.com>
+Copyright (c) 2023-2026 DutchmanNL <rdrozda86@gmail.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/admin/admin.d.ts

@@ -1,93 +1,96 @@
 declare let systemDictionary: Record<string, Record<string, string>>;
 
-declare let load: (settings: Record<string, unknown>, onChange: (hasChanges: boolean) => void) => void;
-declare let save: (callback: (settings: Record<string, unknown>) => void) => void;
+declare let load: (
+  settings: Record<string, unknown>,
+  onChange: (hasChanges: boolean) => void,
+) => void;
+declare let save: (
+  callback: (settings: Record<string, unknown>) => void,
+) => void;
 
 // make load and save exist on the window object
 interface Window {
-	load: typeof load;
-	save: typeof save;
+  load: typeof load;
+  save: typeof save;
 }
 
 declare const instance: number;
 declare const adapter: string;
-/** Translates text */
+/**
+ * Translates text
+ *
+ * @param text - The text to translate
+ */
 declare function _(text: string): string;
 declare const socket: ioBrokerSocket;
 declare function sendTo(
-	instance: any | null,
-	command: string,
-	message: any,
-	callback: (result: SendToResult) => void | Promise<void>,
+  instance: null,
+  command: string,
+  message: any,
+  callback: (result: SendToResult) => void | Promise<void>,
 ): void;
 
 interface SendToResult {
-	error?: string | Error;
-	result?: any;
+  error?: string | Error;
+  result?: any;
 }
 
 // tslint:disable-next-line:class-name
 interface ioBrokerSocket {
-	emit(
-		command: 'subscribeObjects',
-		pattern: string,
-		callback?: (err?: string) => void | Promise<void>,
-	): void;
-	emit(
-		command: 'subscribeStates',
-		pattern: string,
-		callback?: (err?: string) => void | Promise<void>,
-	): void;
-	emit(
-		command: 'unsubscribeObjects',
-		pattern: string,
-		callback?: (err?: string) => void | Promise<void>,
-	): void;
-	emit(
-		command: 'unsubscribeStates',
-		pattern: string,
-		callback?: (err?: string) => void | Promise<void>,
-	): void;
+  emit(
+    command: "subscribeObjects",
+    pattern: string,
+    callback?: (err?: string) => void | Promise<void>,
+  ): void;
+  emit(
+    command: "subscribeStates",
+    pattern: string,
+    callback?: (err?: string) => void | Promise<void>,
+  ): void;
+  emit(
+    command: "unsubscribeObjects",
+    pattern: string,
+    callback?: (err?: string) => void | Promise<void>,
+  ): void;
+  emit(
+    command: "unsubscribeStates",
+    pattern: string,
+    callback?: (err?: string) => void | Promise<void>,
+  ): void;
 
-	emit(
-		event: 'getObjectView',
-		view: 'system',
-		type: 'device',
-		options: ioBroker.GetObjectViewParams,
-		callback: (
-			err: string | undefined,
-			result?: any,
-		) => void | Promise<void>,
-	): void;
-	emit(
-		event: 'getStates',
-		callback: (
-			err: string | undefined,
-			result?: Record<string, any>,
-		) => void,
-	): void;
-	emit(
-		event: 'getState',
-		id: string,
-		callback: (err: string | undefined, result?: ioBroker.State) => void,
-	): void;
-	emit(
-		event: 'setState',
-		id: string,
-		state: unknown,
-		callback: (err: string | undefined, result?: any) => void,
-	): void;
+  emit(
+    event: "getObjectView",
+    view: "system",
+    type: "device",
+    options: ioBroker.GetObjectViewParams,
+    callback: (err: string | undefined, result?: any) => void | Promise<void>,
+  ): void;
+  emit(
+    event: "getStates",
+    callback: (err: string | undefined, result?: Record<string, any>) => void,
+  ): void;
+  emit(
+    event: "getState",
+    id: string,
+    callback: (err: string | undefined, result?: ioBroker.State) => void,
+  ): void;
+  emit(
+    event: "setState",
+    id: string,
+    state: unknown,
+    callback: (err: string | undefined, result?: any) => void,
+  ): void;
 
-	on(event: 'objectChange', handler: ioBroker.ObjectChangeHandler): void;
-	on(event: 'stateChange', handler: ioBroker.StateChangeHandler): void;
-	removeEventHandler(
-		event: 'objectChange',
-		handler: ioBroker.ObjectChangeHandler,
-	): void;
-	removeEventHandler(
-		event: 'stateChange',
-		handler: ioBroker.StateChangeHandler,
-	): void;
+  on(event: "objectChange", handler: ioBroker.ObjectChangeHandler): void;
+  on(event: "stateChange", handler: ioBroker.StateChangeHandler): void;
+  removeEventHandler(
+    event: "objectChange",
+    handler: ioBroker.ObjectChangeHandler,
+  ): void;
+  removeEventHandler(
+    event: "stateChange",
+    handler: ioBroker.StateChangeHandler,
+  ): void;
 
-	// TODO: other events
+  // TODO: other events
 }

package/admin/i18n/de/translations.json

@@ -1,18 +1,23 @@
 {
-    "ESPHomeCommunityLink": "Weitere Informationen zu ESPHome, Beispielkonfigurationen und Links zu Communities finden Sie unter:",
-    "chkEnableESPHome": "Aktivieren Sie das ESPHome-Dashboard",
+    "ESPHomeCommunityLink": "Weitere Informationen zu ESPHome, Beispielkonfigurationen und Links zu Communities sind hier zu finden:",
+    "chkEnableESPHome": "ESPHome-Dashboard aktivieren",
+    "cnfDeleteYamlCancel": "Cancel",
+    "cnfDeleteYamlOk": "Delete",
+    "cnfDeleteYamlText": "Are you sure you want to delete this file?",
+    "cnfDeleteYamlTitle": "Confirm file deletion",
     "existDevicesHeader": "Alle von diesem Adapter verwalteten Geräte und deren Verbindungsstatus",
-    "hlpDiscoveryListeningAddress": "Erkennen Sie nur Geräte auf dieser Schnittstelle",
-    "hlpESPHomeDashboardVersion": "Wählen Sie aus, welche Version von ESPHome Dashboard verwendet werden soll",
+    "hlpDiscoveryListeningAddress": "Nur Geräte auf dieser Schnittstelle erkennen",
+    "hlpESPHomeDashboardVersion": "Auswählen welche Version von ESPHome Dashboard verwendet werden soll",
     "hlpInputApiPassword": "API-Passwort (alt, bitte Verschlüsselungsschlüssel verwenden!)",
-    "hlpInputDeviceIP": "Wählen Sie ein vorhandenes Gerät aus oder geben Sie die IP des neuen Geräts ein",
-    "hlpInputEncryptionKey": "Geben Sie einen gerätespezifischen Verschlüsselungsschlüssel an (bevorzugt)",
-    "introLine-1": "Mit ioBroker ESPHome können Sie ESPHome-fähige Geräte verwalten und steuern. Sie müssen diese Binärdateien selbst erstellen und hochladen!",
+    "hlpInputDeviceIP": "Ein vorhandenes Gerät auswählen oder die IP des neuen Geräts eingeben",
+    "hlpInputEncryptionKey": "Einen gerätespezifischen Verschlüsselungsschlüssel angeben (bevorzugt)",
+    "hlpSelectedFilename": "Enter the filename from the table above to download or delete it",
+    "introLine-1": "Mit ioBroker ESPHome kann man ESPHome-fähige Geräte verwalten und steuern. Diese Binärdateien müssen selbst erstellt und hochgeladen werden!",
     "introLine-2": "Zum Erstellen dieser Binärdateien ist ESPHome Dashboard erforderlich.",
     "lblApiPass": "API-Passwort (Legacy)",
     "lblAutoDiscovery": "Geräteerkennung aktiviert",
     "lblConnectDetails-Line-1": "Die native ESPHome-API wird für die direkte Kommunikation mit Clients über ein hochoptimiertes Netzwerkprotokoll verwendet.",
-    "lblConnectDetails-Line-2": "Nachdem Sie Ihrer ESPHome-Konfiguration eine api:-Zeile hinzugefügt haben, können Sie zu dieser Seite gehen und warten, bis das ESPHome-Gerät im Abschnitt „Erkannte Geräte“ angezeigt wird (kann bis zu 5 Minuten dauern) oder das Gerät manuell hinzufügen, indem Sie „Gerät hinzufügen“ wählen.",
+    "lblConnectDetails-Line-2": "Nachdem der ESPHome-Konfiguration eine api:-Zeile hinzugefügt wurde, kann man zu dieser Seite gehen und warten, bis das ESPHome-Gerät im Abschnitt „Erkannte Geräte“ angezeigt wird (kann bis zu 5 Minuten dauern) oder das Gerät manuell hinzugefügt werden, indem man „Gerät hinzufügen“ wählt.",
     "lblConnectDetails-Line-3": "Die native API von ESPHome basiert auf einem benutzerdefinierten TCP-Protokoll unter Verwendung von Protokollpuffern.",
     "lblConnectIobroker": "ioBroker kommuniziert direkt über die native API statt über MQTT, um Ihnen das bestmögliche Erlebnis und die Unterstützung von Verschlüsselungsschlüsseln (empfohlen) anstelle von API/MQTT-Passwörtern zu bieten",
     "lblDashboardLink": "Um das ESPHome-Dashboard auf der Admin-Registerkarte von ioBroker anzuzeigen, müssen Sie die IP-Adresse angeben, auf der die Installation ausgeführt wird",
@@ -20,21 +25,36 @@
     "lblDefaultCredentials-Line-1": "Jedes Gerät sollte über einen eigenen eindeutigen Verschlüsselungsschlüssel (empfohlen) oder ein API-Passwort verfügen. Die Geräteerkennung (sofern aktiviert) erkennt alle Geräte und versucht, eine Verbindung mit den unten aufgeführten Anmeldeinformationen herzustellen",
     "lblDefaultCredentials-Line-2": "Wenn Sie einen eindeutigen Verschlüsselungsschlüssel (empfohlen) oder ein API-Passwort zuweisen, werden neue Geräte auf der Registerkarte „Erkannte Geräte“ angezeigt (oder müssen hinzugefügt werden) und Sie müssen die eindeutigen Anmeldeinformationen manuell eingeben",
     "lblDelDevice": "Gerät löschen",
+    "lblDeleteYamlButton": "Delete File",
     "lblDevicesTable": "Alle aktuellen (bekannten) Geräte und deren Verbindungsstatus",
     "lblDiscoveryListeningAddress": "Anhörungsadresse",
+    "lblDownloadYamlButton": "Download File",
     "lblESPHomeDashboardVersion": "ESPHome Dashboard-Version",
     "lblESPHomeIP": "IP-Adresse, unter der ESPHome Dashboard zur Integration in ioBroker Admin ausgeführt wird",
     "lblESPHomePort": "Port des ESPHome-Dashboards",
     "lblEnableESPHome": "Sie können ESPHome Dashboard entweder separat ausführen oder die Option unten aktivieren, um es nativ in ioBroker auszuführen",
     "lblEncryptionKey": "Standardverschlüsselungsschlüssel",
+    "lblFileActionsHeader": "File Actions",
     "lblHeaderConnect": "So verbinden Sie ein ESPHome-fähiges Gerät mit ioBroker",
     "lblHeaderMainPage": "ESPHome Dashboard-Integration",
+    "lblHeaderYamlManagement": "YAML File Management",
     "lblIgnoreList": "IP-Adressen, die von der Geräteerkennung ausgeschlossen werden sollen",
     "lblInputApiPassword": "API-Passwort",
     "lblInputDeviceIP-content": "Geräte-IP-Adresse",
     "lblInputEncryptionKey": "Verschlüsselungsschlüssel",
     "lblLoadDevices": "Geräteübersicht aktualisieren",
+    "lblRefreshYamlFiles": "Refresh File List",
+    "lblSelectedFilename": "Select file for download/delete",
     "lblTxtNoButtonsIfNotActive": "Gerätetabelle und Schaltfläche HINZUFÜGEN/Löschen nur verfügbar, wenn der Adapter ausgeführt wird",
+    "lblUploadContent": "YAML Content",
+    "lblUploadFilename": "Filename (e.g., my-device.yaml)",
+    "lblUploadYamlButton": "Upload File",
+    "lblUploadYamlHeader": "Upload YAML File",
+    "lblUploadYamlInfo": "Paste the content of your YAML file below and provide a filename to upload it to the ESPHome directory.",
+    "lblYamlFileUpload": "Upload YAML File",
+    "lblYamlFilesHeader": "Available YAML Files",
+    "lblYamlFilesTable": "YAML files in ESPHome directory",
+    "lblYamlManagementInfo": "Upload, download, and manage YAML configuration files for your ESPHome devices. Files are stored in the ESPHome directory and can be used by the ESPHome Dashboard.",
     "lbl_addUpdateDevice": "Geräte hinzufügen/ändern",
     "maxRetry": "Maximale Verbindungswiederholung, bevor das Gerät als offline betrachtet wird",
     "newDevicesHeader": "Neu entdeckte Geräte, bitte Anmeldedaten angeben!",

package/admin/i18n/en/translations.json

@@ -15,7 +15,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. Https is currently not supported",
+    "lblDashboardLink": "To show ESPHome dashboard in ioBroker admin tab, its required to provide the IP address 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",
@@ -38,5 +38,25 @@
     "lbl_addUpdateDevice": "ADD / Modify devices",
     "maxRetry": "Maximum connection retry before considering device as offline",
     "newDevicesHeader": "Newly discovered devices, please provide credentials!",
-    "reConInterval": "Setting between ioBroker try's to reconnect this device"
+    "reConInterval": "Setting between ioBroker tries to reconnect this device",
+    "lblHeaderYamlManagement": "YAML File Management",
+    "lblYamlManagementInfo": "Upload, download, and manage YAML configuration files for your ESPHome devices. Files are stored in the ESPHome directory and can be used by the ESPHome Dashboard.",
+    "lblUploadYamlHeader": "Upload YAML File",
+    "lblUploadYamlInfo": "Paste the content of your YAML file below and provide a filename to upload it to the ESPHome directory.",
+    "lblUploadFilename": "Filename (e.g., my-device.yaml)",
+    "lblUploadContent": "YAML Content",
+    "lblUploadYamlButton": "Upload File",
+    "lblYamlFileUpload": "Upload YAML File",
+    "lblRefreshYamlFiles": "Refresh File List",
+    "lblYamlFilesHeader": "Available YAML Files",
+    "lblYamlFilesTable": "YAML files in ESPHome directory",
+    "lblFileActionsHeader": "File Actions",
+    "lblSelectedFilename": "Select file for download/delete",
+    "hlpSelectedFilename": "Enter the filename from the table above to download or delete it",
+    "lblDownloadYamlButton": "Download File",
+    "lblDeleteYamlButton": "Delete File",
+    "cnfDeleteYamlText": "Are you sure you want to delete this file?",
+    "cnfDeleteYamlTitle": "Confirm file deletion",
+    "cnfDeleteYamlOk": "Delete",
+    "cnfDeleteYamlCancel": "Cancel"
 }

package/admin/i18n/es/translations.json

@@ -1,12 +1,17 @@
 {
     "ESPHomeCommunityLink": "Para obtener más información sobre ESPHome, configuración de ejemplo y enlaces a comunidades, visite:",
     "chkEnableESPHome": "Habilitar el panel ESPHome",
+    "cnfDeleteYamlCancel": "Cancel",
+    "cnfDeleteYamlOk": "Delete",
+    "cnfDeleteYamlText": "Are you sure you want to delete this file?",
+    "cnfDeleteYamlTitle": "Confirm file deletion",
     "existDevicesHeader": "Todos los dispositivos gestionados por este adaptador y su estado de conexión.",
     "hlpDiscoveryListeningAddress": "Descubrir solo dispositivos en esta interfaz",
     "hlpESPHomeDashboardVersion": "Elija qué versión de ESPHome Dashboard debe usarse",
     "hlpInputApiPassword": "Contraseña de API (heredada, ¡use una clave de cifrado!)",
     "hlpInputDeviceIP": "Seleccione el dispositivo existente o ingrese la IP del nuevo dispositivo",
     "hlpInputEncryptionKey": "Proporcionar clave de cifrado específica del dispositivo (preferido)",
+    "hlpSelectedFilename": "Enter the filename from the table above to download or delete it",
     "introLine-1": "ioBroker ESPHome permite administrar y controlar dispositivos compatibles con ESPHome. ¡Debe crear y cargar estos archivos binarios usted mismo!",
     "introLine-2": "Se requiere ESPHome Dashboard para crear estos archivos binarios. ",
     "lblApiPass": "Contraseña API nativa predeterminada (heredada)",
@@ -20,21 +25,36 @@
     "lblDefaultCredentials-Line-1": "Cada dispositivo debe tener su propia clave de cifrado única (recomendada) o contraseña API; la detección de dispositivos (cuando está habilitada) detecta todos los dispositivos e intenta conectarse con las siguientes credenciales",
     "lblDefaultCredentials-Line-2": "Si asigna una clave de cifrado única (recomendada) o una contraseña API, los nuevos dispositivos aparecerán en la pestaña Dispositivos descubiertos (o deberán agregarse) y deberá proporcionar las credenciales únicas manualmente.",
     "lblDelDevice": "Eliminar dispositivo",
+    "lblDeleteYamlButton": "Delete File",
     "lblDevicesTable": "Todos los dispositivos actuales (conocidos) y su estado de conexión",
     "lblDiscoveryListeningAddress": "dirección de escucha",
+    "lblDownloadYamlButton": "Download File",
     "lblESPHomeDashboardVersion": "Versión del panel ESPHome",
     "lblESPHomeIP": "Dirección IP donde se ejecuta ESPHome Dashboard para integrarse en ioBroker Admin",
     "lblESPHomePort": "Puerto de ESPHome Dashboard",
     "lblEnableESPHome": "Puede ejecutar ESPHome Dashboard por separado o activar la siguiente opción para ejecutarlo de forma nativa en ioBroker.",
     "lblEncryptionKey": "Clave de cifrado predeterminada",
+    "lblFileActionsHeader": "File Actions",
     "lblHeaderConnect": "Cómo conectar un dispositivo compatible con ESPHome a ioBroker",
     "lblHeaderMainPage": "Integración del panel ESPHome",
+    "lblHeaderYamlManagement": "YAML File Management",
     "lblIgnoreList": "Direcciones IP que se excluirán mediante el descubrimiento de dispositivos",
     "lblInputApiPassword": "Contraseña API",
     "lblInputDeviceIP-content": "Dirección IP del dispositivo",
     "lblInputEncryptionKey": "Clave de encriptación",
     "lblLoadDevices": "Actualizar descripción general del dispositivo",
+    "lblRefreshYamlFiles": "Refresh File List",
+    "lblSelectedFilename": "Select file for download/delete",
     "lblTxtNoButtonsIfNotActive": "La tabla de dispositivos y el botón AGREGAR/Eliminar solo están disponibles si el adaptador está en ejecución",
+    "lblUploadContent": "YAML Content",
+    "lblUploadFilename": "Filename (e.g., my-device.yaml)",
+    "lblUploadYamlButton": "Upload File",
+    "lblUploadYamlHeader": "Upload YAML File",
+    "lblUploadYamlInfo": "Paste the content of your YAML file below and provide a filename to upload it to the ESPHome directory.",
+    "lblYamlFileUpload": "Upload YAML File",
+    "lblYamlFilesHeader": "Available YAML Files",
+    "lblYamlFilesTable": "YAML files in ESPHome directory",
+    "lblYamlManagementInfo": "Upload, download, and manage YAML configuration files for your ESPHome devices. Files are stored in the ESPHome directory and can be used by the ESPHome Dashboard.",
     "lbl_addUpdateDevice": "AGREGAR / Modificar dispositivos",
     "maxRetry": "Reintento máximo de conexión antes de considerar el dispositivo como fuera de línea",
     "newDevicesHeader": "Dispositivos recién descubiertos, proporcione credenciales.",

package/admin/i18n/fr/translations.json

@@ -1,12 +1,17 @@
 {
     "ESPHomeCommunityLink": "Pour plus d'informations sur ESPHome, des exemples de configuration et des liens vers les communautés, veuillez visiter :",
     "chkEnableESPHome": "Activer le tableau de bord ESPHome",
+    "cnfDeleteYamlCancel": "Cancel",
+    "cnfDeleteYamlOk": "Delete",
+    "cnfDeleteYamlText": "Are you sure you want to delete this file?",
+    "cnfDeleteYamlTitle": "Confirm file deletion",
     "existDevicesHeader": "Tous les appareils gérés par cet adaptateur et leur état de connexion",
     "hlpDiscoveryListeningAddress": "Découvrez uniquement les appareils sur cette interface",
     "hlpESPHomeDashboardVersion": "Choisissez quelle version d'ESPHome Dashboard doit être utilisée",
     "hlpInputApiPassword": "Mot de passe API (ancien, veuillez utiliser la clé de cryptage !)",
     "hlpInputDeviceIP": "Sélectionnez l'appareil existant ou entrez l'adresse IP du nouvel appareil",
     "hlpInputEncryptionKey": "Fournir une clé de cryptage spécifique à l'appareil (de préférence)",
+    "hlpSelectedFilename": "Enter the filename from the table above to download or delete it",
     "introLine-1": "ioBroker ESPHome permet de gérer et de contrôler les appareils compatibles ESPHome, vous devez créer et télécharger ces binaires par vous-même !",
     "introLine-2": "ESPHome Dashboard est requis pour créer ces binaires. ",
     "lblApiPass": "Mot de passe de l'API native par défaut (ancien)",
@@ -20,21 +25,36 @@
     "lblDefaultCredentials-Line-1": "Chaque appareil doit avoir sa propre clé de cryptage unique (recommandée) ou son propre mot de passe API, la découverte des appareils (lorsqu'elle est activée) détecte tous les appareils et tente de se connecter avec les informations d'identification ci-dessous.",
     "lblDefaultCredentials-Line-2": "Si vous attribuez une clé de cryptage unique (recommandé) ou un mot de passe API, les nouveaux appareils apparaîtront dans l'onglet Appareils découverts (ou doivent être ajoutés) et vous devez fournir les informations d'identification uniques manuellement.",
     "lblDelDevice": "Supprimer l'appareil",
+    "lblDeleteYamlButton": "Delete File",
     "lblDevicesTable": "Tous les appareils actuels (connus) et leur état de connexion",
     "lblDiscoveryListeningAddress": "Adresse d'écoute",
+    "lblDownloadYamlButton": "Download File",
     "lblESPHomeDashboardVersion": "Version du tableau de bord ESPHome",
     "lblESPHomeIP": "Adresse IP sur laquelle ESPHome Dashboard est exécuté pour s'intégrer dans ioBroker Admin",
     "lblESPHomePort": "Port du tableau de bord ESPHome",
     "lblEnableESPHome": "Vous pouvez soit exécuter ESPHome Dashboard séparément, soit activer l'option ci-dessous pour l'exécuter nativement dans ioBroker",
     "lblEncryptionKey": "Clé de cryptage par défaut",
+    "lblFileActionsHeader": "File Actions",
     "lblHeaderConnect": "Comment connecter un appareil compatible ESPHome à ioBroker",
     "lblHeaderMainPage": "Intégration du tableau de bord ESPHome",
+    "lblHeaderYamlManagement": "YAML File Management",
     "lblIgnoreList": "Adresses IP à exclure par la découverte de périphériques",
     "lblInputApiPassword": "Mot de passe API",
     "lblInputDeviceIP-content": "Adresse IP de l'appareil",
     "lblInputEncryptionKey": "Clé de cryptage",
     "lblLoadDevices": "Actualiser la présentation des appareils",
+    "lblRefreshYamlFiles": "Refresh File List",
+    "lblSelectedFilename": "Select file for download/delete",
     "lblTxtNoButtonsIfNotActive": "Tableau des appareils et bouton AJOUTER/Supprimer disponibles uniquement si l'adaptateur est en cours d'exécution",
+    "lblUploadContent": "YAML Content",
+    "lblUploadFilename": "Filename (e.g., my-device.yaml)",
+    "lblUploadYamlButton": "Upload File",
+    "lblUploadYamlHeader": "Upload YAML File",
+    "lblUploadYamlInfo": "Paste the content of your YAML file below and provide a filename to upload it to the ESPHome directory.",
+    "lblYamlFileUpload": "Upload YAML File",
+    "lblYamlFilesHeader": "Available YAML Files",
+    "lblYamlFilesTable": "YAML files in ESPHome directory",
+    "lblYamlManagementInfo": "Upload, download, and manage YAML configuration files for your ESPHome devices. Files are stored in the ESPHome directory and can be used by the ESPHome Dashboard.",
     "lbl_addUpdateDevice": "AJOUTER/Modifier des appareils",
     "maxRetry": "Nombre maximal de tentatives de connexion avant de considérer l'appareil comme hors ligne",
     "newDevicesHeader": "Appareils récemment découverts, veuillez fournir vos informations d'identification !",

package/admin/i18n/it/translations.json

@@ -1,12 +1,17 @@
 {
     "ESPHomeCommunityLink": "Per ulteriori informazioni su ESPHome, esempi di configurazione e collegamenti alle comunità, visitare:",
     "chkEnableESPHome": "Abilita la dashboard ESPHome",
+    "cnfDeleteYamlCancel": "Cancel",
+    "cnfDeleteYamlOk": "Delete",
+    "cnfDeleteYamlText": "Are you sure you want to delete this file?",
+    "cnfDeleteYamlTitle": "Confirm file deletion",
     "existDevicesHeader": "Tutti i dispositivi gestiti da questo adattatore e il relativo stato di connessione",
     "hlpDiscoveryListeningAddress": "Rileva solo i dispositivi su questa interfaccia",
     "hlpESPHomeDashboardVersion": "Scegli quale versione di ESPHome Dashboard deve essere utilizzata",
     "hlpInputApiPassword": "Password API (legacy, utilizza la chiave di crittografia!)",
     "hlpInputDeviceIP": "Seleziona il dispositivo esistente o inserisci l'IP del nuovo dispositivo",
     "hlpInputEncryptionKey": "Fornire una chiave di crittografia specifica per il dispositivo (preferibile)",
+    "hlpSelectedFilename": "Enter the filename from the table above to download or delete it",
     "introLine-1": "ioBroker ESPHome consente di gestire e controllare i dispositivi compatibili con ESPHome, devi creare e caricare questi binari da solo!",
     "introLine-2": "Per creare questi file binari è necessario ESPHome Dashboard. ",
     "lblApiPass": "Password API nativa predefinita (legacy)",
@@ -20,21 +25,36 @@
     "lblDefaultCredentials-Line-1": "Ogni dispositivo deve avere la propria chiave di crittografia univoca (consigliata) o password API, il rilevamento dei dispositivi (se abilitato) rileva tutti i dispositivi e tenta di connettersi con le credenziali riportate di seguito",
     "lblDefaultCredentials-Line-2": "Se assegni una chiave di crittografia univoca (consigliata) o una password API, i nuovi dispositivi verranno visualizzati nella scheda Dispositivi rilevati (o dovranno essere aggiunti) e dovrai fornire manualmente le credenziali univoche",
     "lblDelDevice": "Elimina dispositivo",
+    "lblDeleteYamlButton": "Delete File",
     "lblDevicesTable": "Tutti i dispositivi attuali (conosciuti) e il relativo stato di connessione",
     "lblDiscoveryListeningAddress": "Indirizzo d'ascolto",
+    "lblDownloadYamlButton": "Download File",
     "lblESPHomeDashboardVersion": "Versione ESPHome Dashboard",
     "lblESPHomeIP": "Indirizzo IP su cui è in esecuzione ESPHome Dashboard per l'integrazione in ioBroker Admin",
     "lblESPHomePort": "Porta della dashboard ESPHome",
     "lblEnableESPHome": "Puoi eseguire ESPHome Dashboard separatamente o attivare l'opzione seguente per eseguirlo nativo in ioBroker",
     "lblEncryptionKey": "Chiave di crittografia predefinita",
+    "lblFileActionsHeader": "File Actions",
     "lblHeaderConnect": "Come connettere un dispositivo compatibile con ESPHome a ioBroker",
     "lblHeaderMainPage": "Integrazione della dashboard ESPHome",
+    "lblHeaderYamlManagement": "YAML File Management",
     "lblIgnoreList": "Indirizzi IP da escludere dal rilevamento del dispositivo",
     "lblInputApiPassword": "Password dell'API",
     "lblInputDeviceIP-content": "Indirizzo IP del dispositivo",
     "lblInputEncryptionKey": "Chiave crittografica",
     "lblLoadDevices": "Aggiorna la panoramica del dispositivo",
+    "lblRefreshYamlFiles": "Refresh File List",
+    "lblSelectedFilename": "Select file for download/delete",
     "lblTxtNoButtonsIfNotActive": "La tabella dei dispositivi e il pulsante AGGIUNGI/Elimina sono disponibili solo se l'adattatore è in esecuzione",
+    "lblUploadContent": "YAML Content",
+    "lblUploadFilename": "Filename (e.g., my-device.yaml)",
+    "lblUploadYamlButton": "Upload File",
+    "lblUploadYamlHeader": "Upload YAML File",
+    "lblUploadYamlInfo": "Paste the content of your YAML file below and provide a filename to upload it to the ESPHome directory.",
+    "lblYamlFileUpload": "Upload YAML File",
+    "lblYamlFilesHeader": "Available YAML Files",
+    "lblYamlFilesTable": "YAML files in ESPHome directory",
+    "lblYamlManagementInfo": "Upload, download, and manage YAML configuration files for your ESPHome devices. Files are stored in the ESPHome directory and can be used by the ESPHome Dashboard.",
     "lbl_addUpdateDevice": "AGGIUNGI/MODIFICA DISPOSITIVI",
     "maxRetry": "Numero massimo di tentativi di connessione prima di considerare il dispositivo offline",
     "newDevicesHeader": "Dispositivi appena scoperti, fornisci le credenziali!",