iobroker.esphome 0.4.0 → 0.5.0-beta.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG_OLD.md +12 -0
- package/README.md +78 -19
- package/admin/i18n/de/translations.json +38 -0
- package/admin/i18n/en/translations.json +38 -0
- package/admin/i18n/es/translations.json +38 -0
- package/admin/i18n/fr/translations.json +38 -0
- package/admin/i18n/it/translations.json +38 -0
- package/admin/i18n/nl/translations.json +38 -0
- package/admin/i18n/pl/translations.json +38 -0
- package/admin/i18n/pt/translations.json +38 -0
- package/admin/i18n/ru/translations.json +38 -0
- package/admin/i18n/zh-cn/translations.json +38 -0
- package/admin/img/connectionError.png +0 -0
- package/admin/img/connectionOK.png +0 -0
- package/admin/img/dashboard.png +0 -0
- package/admin/img/deviceTabEmpty.png +0 -0
- package/admin/img/deviceTree.png +0 -0
- package/admin/index_m.html +30 -39
- package/admin/jsonConfig.json +491 -0
- package/admin/words.js +36 -19
- package/gulpfile.js.map +1 -0
- package/io-package.json +42 -27
- package/lib/helpers.js +95 -0
- package/lib/helpers.js.map +1 -0
- package/lib/stateAttr.js +2 -1
- package/lib/stateAttr.js.map +1 -0
- package/lib/tools.js +1 -0
- package/lib/tools.js.map +1 -0
- package/main.js +498 -282
- package/main.js.map +1 -0
- package/main.test.js +1 -0
- package/main.test.js.map +1 -0
- package/package.json +9 -2
package/CHANGELOG_OLD.md
CHANGED
|
@@ -1,4 +1,16 @@
|
|
|
1
1
|
# Older changes
|
|
2
|
+
## 0.3.0 (2023-10-31) - Bugfixes & Improvements
|
|
3
|
+
* (Dutchman & SimonFischer04) Several Bugfixes
|
|
4
|
+
* (SimonFischer04) Supports type "select device"
|
|
5
|
+
* (DutchmanNL) ESPHome dashboard default disabled
|
|
6
|
+
* (SimonFischer04) Migrate to @2colors/esphome-native-api
|
|
7
|
+
* (DutchmanNL) Automatically create needed directories, resolves #168
|
|
8
|
+
* (SimonFischer04) Migrate usage of python to new structure should solve all ESPHome Dashboard-related installation issues
|
|
9
|
+
|
|
10
|
+
## 0.2.4 (2021-08-24)
|
|
11
|
+
* (DutchmanNL) Version of ESPHome Dashboard updated to 2021.8
|
|
12
|
+
* (DutchmanNL) Add option if config of ESPHome device should be shown as states (default = FALSE, safes 8 states for each sensor)
|
|
13
|
+
|
|
2
14
|
## 0.2.3 (2021-06-29)
|
|
3
15
|
* (Jey-Cee) Bugfix : Light component state not changed [#74](https://github.com/DrozmotiX/ioBroker.esphome/issues/74)
|
|
4
16
|
* (DutchmanNL) Update compatibility to version 1.19.4 of ESPHome Dashboard
|
package/README.md
CHANGED
|
@@ -19,15 +19,18 @@
|
|
|
19
19
|
## ESPHome adapter for ioBroker
|
|
20
20
|
|
|
21
21
|
Control your ESP8266/ESP32 with simple yet powerful configuration files created and managed by ESPHome.
|
|
22
|
-
Native integration of ESPHome managed device (Including Dashboard) by its native API and
|
|
22
|
+
Native integration of ESPHome managed device (Including Dashboard) by its native API and ensures all data is synchronized (live-event handling, no data polling ! :)
|
|
23
23
|
|
|
24
24
|

|
|
25
25
|
|
|
26
26
|
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)!
|
|
27
27
|
|
|
28
|
+
|
|
29
|
+
<!--
|
|
28
30
|
## [Documentation](https://DrozmotiX.github.io/languages/en/Adapter/ESPHome/)
|
|
29
31
|
|
|
30
|
-
All our adapter documentation can be found at [The DrozmotiX Docu Page](https://DrozmotiX.github.io/languages/en/Adapter/ESPHome/)
|
|
32
|
+
All our adapter documentation can be found at [The DrozmotiX Docu Page](https://DrozmotiX.github.io/languages/en/Adapter/ESPHome/)
|
|
33
|
+
-->
|
|
31
34
|
|
|
32
35
|
## Prerequisites
|
|
33
36
|
|
|
@@ -37,12 +40,65 @@ All our adapter documentation can be found at [The DrozmotiX Docu Page](https://
|
|
|
37
40
|
* ESPHome Dashboard IP is provided in instance settings
|
|
38
41
|
|
|
39
42
|
### Activate API in YAML
|
|
43
|
+
> [!IMPORTANT]
|
|
44
|
+
> ioBroker ESPHome allows to integrate Devices by Encryption Key (recommended) or API-Password (legacy),
|
|
45
|
+
> you must specify your authentication settings accordingly,
|
|
46
|
+
> see [ESPHome Documentation](https://esphome.io/components/api.html?highlight=api)
|
|
47
|
+
> Please only configure Encryption Key (preferable) or API-Password (legacy)
|
|
48
|
+
|
|
49
|
+
#### Example Encryption Key configuration entry
|
|
50
|
+
```
|
|
51
|
+
api:
|
|
52
|
+
encryption:
|
|
53
|
+
key: "DyDfEgDzmA9GlK6ZuLkj3qgFcjXiZUzUf4chnIcjQto="
|
|
54
|
+
```
|
|
40
55
|
|
|
56
|
+
#### Example API configuration entry
|
|
41
57
|
```
|
|
42
58
|
api:
|
|
43
59
|
password: 'MyPassword'
|
|
44
60
|
```
|
|
45
61
|
|
|
62
|
+
### Add / Modify / Remove ESPHome devices to ioBroker
|
|
63
|
+
> [!IMPORTANT]
|
|
64
|
+
> This adapter integrates communication with ESPHome capable devices and
|
|
65
|
+
> (if activated) an integrated version of ESPHome Dashboard.
|
|
66
|
+
> You must configure and upload your ESP configuration by yourself,
|
|
67
|
+
> either by using the integrated Dashboard or an external alternative
|
|
68
|
+
> (like Docker) before they can be integrated to ioBroker
|
|
69
|
+
|
|
70
|
+
The device Tab will show all current known devices; you can either wait for Devices to be autodetect
|
|
71
|
+
(currently disabled, see #175) or add them manually by providing their IP-Address and credentials
|
|
72
|
+
|
|
73
|
+

|
|
74
|
+
|
|
75
|
+
> [!NOTE]
|
|
76
|
+
> Buttons to add/modify/remove devices and load device table are only available if adapter is running!
|
|
77
|
+
> You must refresh the device table manually by pressing "Refresh device Overview", all devices and their connection state will be shown
|
|
78
|
+
|
|
79
|
+
Please enter IP-Address (if a device is already known, you can select it from the dropdown) and choose the proper actions:
|
|
80
|
+
- ADD / Modify Devices
|
|
81
|
+
- Will send IP address and credentials to the backend and try to establish a connection
|
|
82
|
+
- When an encryption Key is provided, API-Password is ignored, please ensure proper YAML configuration!
|
|
83
|
+
|
|
84
|
+
- Delete Device
|
|
85
|
+
- Will send a message to the backend to remove this device
|
|
86
|
+
|
|
87
|
+
> [!WARNING]
|
|
88
|
+
> THis action will remove selected device and all its related states from ioBroker!
|
|
89
|
+
|
|
90
|
+
> [!NOTE]
|
|
91
|
+
> After a device has been added, a message will be indicated if successfully or error,
|
|
92
|
+
> you can refresh the table to show current devices and their connection status
|
|
93
|
+
|
|
94
|
+

|
|
95
|
+

|
|
96
|
+
|
|
97
|
+
If connection was successfully, the Device will be initiated and all related states created to control their attributes.
|
|
98
|
+
When making any changes to your YAML configuration, reboot of the ESP will disconnect and initiate a new connection.
|
|
99
|
+
During this process, states not part anymore of YAML configuration will be automatically removed.
|
|
100
|
+
|
|
101
|
+

|
|
46
102
|
|
|
47
103
|
### Example config
|
|
48
104
|
Example config, for more examples see [The DrozmotiX Docu Page](https://DrozmotiX.github.io) or [ESPHome Documentation](https://esphome.io/index.html)
|
|
@@ -95,14 +151,14 @@ Example config, for more examples see [The DrozmotiX Docu Page](https://Drozmoti
|
|
|
95
151
|
## Tasmota / ESPEasy migration
|
|
96
152
|
|
|
97
153
|
Migrating from previous Sonoff Tasmota or ESPEasy setups is very easy. You just need to have ESPHome create a binary for you and then upload that in the web interface.
|
|
98
|
-
See for more details our [Docu Page](https://DrozmotiX.github.io/languages/en/Adapter/ESPHome/06.migration.html)
|
|
154
|
+
See for more details on our [Docu Page](https://DrozmotiX.github.io/languages/en/Adapter/ESPHome/06.migration.html)
|
|
99
155
|
|
|
100
156
|
**_NOTE:_** Generated yaml files are stored at ```/opt/iobroker/iobroker-data/iobroker.esphome.>instance</>device<.yaml
|
|
101
157
|
|
|
102
158
|
|
|
103
159
|
## Support me
|
|
104
160
|
If you like my work, please consider a personal donation
|
|
105
|
-
(this is
|
|
161
|
+
(this is a personal Donate link for DutchmanNL, no relation to the ioBroker Project !)
|
|
106
162
|
[](http://paypal.me/DutchmanNL)
|
|
107
163
|
|
|
108
164
|
## Changelog
|
|
@@ -112,30 +168,33 @@ If you like my work, please consider a personal donation
|
|
|
112
168
|
### __WORK IN PROGRESS__
|
|
113
169
|
* (DutchmanNL)
|
|
114
170
|
-->
|
|
171
|
+
### 0.5.0-beta.0 (2023-11-12) - Rebuild Admin Interface & Connection handler
|
|
172
|
+
* (DutchmanNL) Admin interface redesigned to JSON-Config relates #171
|
|
173
|
+
* (DutchmanNL) Backend massages implemented to Add/Modify/Delete devices
|
|
174
|
+
* (DutchmanNL) Device connection handling and visibility of devices improved
|
|
175
|
+
* (DutchmanNL) Auto device discovery temporary disabled due to external bug, relates #175
|
|
176
|
+
* (DutchmanNL) Possibility added to exclude IP-Addresses from device discovery, relates #175
|
|
177
|
+
* (DutchmanNL) Allow Selection to listen on specific interface or all for device discovery resolves #67
|
|
178
|
+
* (DutchmanNL) State implemented to show current connection status (unreachable/disconnected/connected) to improve management of devices
|
|
179
|
+
* (DutchmanNL) Several bugfixes, resolves #181 resolves #
|
|
180
|
+
|
|
181
|
+
### 0.4.1 (2023-11-05)
|
|
182
|
+
* (DutchmanNL) Bugfix: Password / connection issues in previous beta resolves #179
|
|
183
|
+
* (DutchmanNL) Bugfix: Allow individual API password or encryption keys for devices, resolves #174
|
|
184
|
+
* (DutchmanNL) Support ESPHome device Encryption Key (you should migrate from API password to Encryption Key ! resolves #152)
|
|
185
|
+
|
|
115
186
|
### 0.4.0 (2023-11-03)
|
|
116
|
-
* (DutchmanNL) Added cleanup capability for unused channels & states after
|
|
117
|
-
* (DutchmanNL) Added button to info channel which allows to delete all offline devices from adapter tree. resolves #39
|
|
187
|
+
* (DutchmanNL) Added cleanup capability for unused channels & states after initialization of a device, resolves #39
|
|
188
|
+
* (DutchmanNL) Added button to an info channel which allows to delete all offline devices from an adapter tree. resolves #39
|
|
118
189
|
* (DutchmanNL) [Breaking] Backup strategy changed, requires [BackitUp v2.9.1](https://github.com/simatec/ioBroker.backitup) and activate option for ESPHome, fixes #129
|
|
119
190
|
|
|
120
191
|
### 0.3.2 (2023-11-01)
|
|
121
192
|
* (DutchmanNL) Improved error handling if devices are not reachable/disconnected
|
|
122
|
-
* (DutchmanNL) Bugfix: Allow control of brightness and color for light component, resolves #173
|
|
193
|
+
* (DutchmanNL) Bugfix: Allow control of brightness and color for a light component, resolves #173
|
|
123
194
|
|
|
124
195
|
### 0.3.1 (2023-10-31)
|
|
125
196
|
* (DutchmanNL) Bugfix: Show online state of ESP Device correctly, resolves #106
|
|
126
197
|
|
|
127
|
-
### 0.3.0 (2023-10-31) - Bugfixes & Improvements
|
|
128
|
-
* (Dutchman & SimonFischer04) Several Bugfixes
|
|
129
|
-
* (SimonFischer04) Support type "select device"
|
|
130
|
-
* (DutchmanNL) ESPHome dashboard default disabled
|
|
131
|
-
* (SimonFischer04) Migrate to @2colors/esphome-native-api
|
|
132
|
-
* (DutchmanNL) Automatically create needed directories, resolves #168
|
|
133
|
-
* (SimonFischer04) Migrate usage of python to new structure, should solve all ESPHome Dashboard related installation issues
|
|
134
|
-
|
|
135
|
-
### 0.2.4 (2021-08-24)
|
|
136
|
-
* (DutchmanNL) Version of ESPHome Dashboard updated to 2021.8
|
|
137
|
-
* (DutchmanNL) Add option if config of ESPHome device should be shown as states (default = FALSE, safes 8 states for each sensor)
|
|
138
|
-
|
|
139
198
|
## License
|
|
140
199
|
MIT License
|
|
141
200
|
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "Weitere Informationen zu ESPHome, Beispielkonfigurationen und Links zu Communities finden Sie unter:",
|
|
3
|
+
"chkEnableESPHome": "Aktivieren Sie das ESPHome-Dashboard",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Erkennen Sie nur Geräte auf dieser Schnittstelle",
|
|
5
|
+
"hlpInputApiPassword": "API-Passwort (alt, bitte Verschlüsselungsschlüssel verwenden!)",
|
|
6
|
+
"hlpInputDeviceIP": "Wählen Sie ein vorhandenes Gerät aus oder geben Sie die IP des neuen Geräts ein",
|
|
7
|
+
"hlpInputEncryptionKey": "Geben Sie einen gerätespezifischen Verschlüsselungsschlüssel an (bevorzugt)",
|
|
8
|
+
"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!",
|
|
9
|
+
"introLine-2": "Zum Erstellen dieser Binärdateien ist ESPHome Dashboard erforderlich. ",
|
|
10
|
+
"lblApiPass": "API-Passwort (Legacy)",
|
|
11
|
+
"lblAutoDiscovery": "Geräteerkennung aktiviert",
|
|
12
|
+
"lblConnectDetails-Line-1": "Die native ESPHome-API wird für die direkte Kommunikation mit Clients über ein hochoptimiertes Netzwerkprotokoll verwendet. ",
|
|
13
|
+
"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. ",
|
|
14
|
+
"lblConnectDetails-Line-3": "Die native API von ESPHome basiert auf einem benutzerdefinierten TCP-Protokoll unter Verwendung von Protokollpuffern. ",
|
|
15
|
+
"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",
|
|
16
|
+
"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",
|
|
17
|
+
"lblDefaultCredentials": "Standard-API-/Verschlüsselungsschlüssel-Einstellungsgeräte (nicht empfohlen)",
|
|
18
|
+
"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",
|
|
19
|
+
"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",
|
|
20
|
+
"lblDelDevice": "Gerät löschen",
|
|
21
|
+
"lblDevicesTable": "Alle aktuellen (bekannten) Geräte und deren Verbindungsstatus",
|
|
22
|
+
"lblDiscoveryListeningAddress": "Anhörungsadresse",
|
|
23
|
+
"lblESPHomeIP": "IP-Adresse, unter der ESPHome Dashboard zur Integration in ioBroker Admin ausgeführt wird",
|
|
24
|
+
"lblESPHomePort": "Port des ESPHome-Dashboards",
|
|
25
|
+
"lblEnableESPHome": "Sie können ESPHome Dashboard entweder separat ausführen oder die Option unten aktivieren, um es nativ in ioBroker auszuführen",
|
|
26
|
+
"lblEncryptionKey": "Standardverschlüsselungsschlüssel",
|
|
27
|
+
"lblHeaderConnect": "So verbinden Sie ein ESPHome-fähiges Gerät mit ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "ESPHome Dashboard-Integration",
|
|
29
|
+
"lblIgnoreList": "IP-Adressen, die von der Geräteerkennung ausgeschlossen werden sollen",
|
|
30
|
+
"lblInputApiPassword": "API-Passwort",
|
|
31
|
+
"lblInputDeviceIP-content": "Geräte-IP-Adresse",
|
|
32
|
+
"lblInputEncryptionKey": "Verschlüsselungsschlüssel",
|
|
33
|
+
"lblLoadDevices": "Geräteübersicht aktualisieren",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "Gerätetabelle und Schaltfläche HINZUFÜGEN/Löschen nur verfügbar, wenn der Adapter ausgeführt wird",
|
|
35
|
+
"lbl_addUpdateDevice": "Geräte hinzufügen/ändern",
|
|
36
|
+
"maxRetry": "Maximale Verbindungswiederholung, bevor das Gerät als offline betrachtet wird",
|
|
37
|
+
"reConInterval": "Einstellung zwischen ioBroker versucht, dieses Gerät erneut zu verbinden"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "For more information about ESPHome, example configuration and links to communities please visit:",
|
|
3
|
+
"chkEnableESPHome": "Enable ESPHome Dashboard",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Only discover devices on this interface",
|
|
5
|
+
"hlpInputApiPassword": "API password (legacy, please use encryption key!)",
|
|
6
|
+
"hlpInputDeviceIP": "Select existing device or Enter IP of new device",
|
|
7
|
+
"hlpInputEncryptionKey": "Provide device specific Encryption Key (preferred)",
|
|
8
|
+
"introLine-1": "ioBroker ESPHome allows to manage and control ESPHome capable devices, you must create and upload these binaries by yourself!",
|
|
9
|
+
"introLine-2": "ESPHome Dashboard is required to build these binaries. As soon a device firmware is flashed and operational, ESPHome Dashboard is not required anymore to allow communications with ioBroker",
|
|
10
|
+
"lblApiPass": "API password (legacy)",
|
|
11
|
+
"lblAutoDiscovery": "Device Discovery enabled",
|
|
12
|
+
"lblConnectDetails-Line-1": "The ESPHome native API is used to communicate with clients directly, with a highly-optimized network protocol. Native API has many advantages over using MQTT for communication with Home Automation software ",
|
|
13
|
+
"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.",
|
|
14
|
+
"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:",
|
|
15
|
+
"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",
|
|
16
|
+
"lblDashboardLink": "To show ESPHome dashboard in ioBroker admin tab, its required to provide the IP-Ares on which installation its running",
|
|
17
|
+
"lblDefaultCredentials": "Default API / Encryption keys settings devices (not recommended)",
|
|
18
|
+
"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",
|
|
19
|
+
"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",
|
|
20
|
+
"lblDelDevice": "Delete Device",
|
|
21
|
+
"lblDevicesTable": "All current (known) devices and their connection state",
|
|
22
|
+
"lblDiscoveryListeningAddress": "Listening address",
|
|
23
|
+
"lblESPHomeIP": "IP-Address where ESPHome Dashboard is running to integrate in ioBroker Admin",
|
|
24
|
+
"lblESPHomePort": "Port of ESPHome Dashboard",
|
|
25
|
+
"lblEnableESPHome": "You can either run ESPHome Dashboard separately, or activate the option below to run it native in ioBroker",
|
|
26
|
+
"lblEncryptionKey": "Default encryption Key",
|
|
27
|
+
"lblHeaderConnect": "How to connect an ESPHome capable device to ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "ESPHome Dashboard integration",
|
|
29
|
+
"lblIgnoreList": "IP-Addresses to be excluded by device discovery",
|
|
30
|
+
"lblInputApiPassword": "API password",
|
|
31
|
+
"lblInputDeviceIP-content": "Device IP-Address",
|
|
32
|
+
"lblInputEncryptionKey": "Encryption Key",
|
|
33
|
+
"lblLoadDevices": "Refresh device overview",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "Device table & ADD / Delete button only available if adapter is running",
|
|
35
|
+
"lbl_addUpdateDevice": "ADD / Modify Devices",
|
|
36
|
+
"maxRetry": "Maximum connection retry before considering device as offline",
|
|
37
|
+
"reConInterval": "Setting between ioBroker try's to reconnect this device"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "Para obtener más información sobre ESPHome, configuración de ejemplo y enlaces a comunidades, visite:",
|
|
3
|
+
"chkEnableESPHome": "Habilitar el panel ESPHome",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Descubrir solo dispositivos en esta interfaz",
|
|
5
|
+
"hlpInputApiPassword": "Contraseña de API (heredada, ¡use una clave de cifrado!)",
|
|
6
|
+
"hlpInputDeviceIP": "Seleccione el dispositivo existente o ingrese la IP del nuevo dispositivo",
|
|
7
|
+
"hlpInputEncryptionKey": "Proporcionar clave de cifrado específica del dispositivo (preferido)",
|
|
8
|
+
"introLine-1": "ioBroker ESPHome permite administrar y controlar dispositivos compatibles con ESPHome. ¡Debe crear y cargar estos archivos binarios usted mismo!",
|
|
9
|
+
"introLine-2": "Se requiere ESPHome Dashboard para crear estos archivos binarios. ",
|
|
10
|
+
"lblApiPass": "Contraseña API nativa predeterminada (heredada)",
|
|
11
|
+
"lblAutoDiscovery": "Descubrimiento de dispositivos habilitado",
|
|
12
|
+
"lblConnectDetails-Line-1": "La API nativa de ESPHome se utiliza para comunicarse directamente con los clientes, con un protocolo de red altamente optimizado. ",
|
|
13
|
+
"lblConnectDetails-Line-2": "Después de agregar una línea api: a su configuración de ESPHome, puede ir a esta página y esperar a que aparezca el dispositivo ESPHome en la sección de dispositivos descubiertos (puede tardar hasta 5 minutos) o agregar el dispositivo manualmente eligiendo \"agregar dispositivo\". ",
|
|
14
|
+
"lblConnectDetails-Line-3": "La API nativa de ESPHome se basa en un protocolo TCP personalizado que utiliza buffers de protocolo. ",
|
|
15
|
+
"lblConnectIobroker": "ioBroker se comunica directamente mediante API nativa en lugar de MQTT para brindarle la mejor experiencia posible y soporte de claves de cifrado (recomendado) en lugar de contraseñas API/MQTT",
|
|
16
|
+
"lblDashboardLink": "Para mostrar el panel de ESPHome en la pestaña de administración de ioBroker, es necesario proporcionar la IP-Ares en la que se está ejecutando la instalación.",
|
|
17
|
+
"lblDefaultCredentials": "Dispositivos de configuración de claves de cifrado/API predeterminados (no recomendado)",
|
|
18
|
+
"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",
|
|
19
|
+
"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.",
|
|
20
|
+
"lblDelDevice": "Eliminar dispositivo",
|
|
21
|
+
"lblDevicesTable": "Todos los dispositivos actuales (conocidos) y su estado de conexión",
|
|
22
|
+
"lblDiscoveryListeningAddress": "dirección de escucha",
|
|
23
|
+
"lblESPHomeIP": "Dirección IP donde se ejecuta ESPHome Dashboard para integrarse en ioBroker Admin",
|
|
24
|
+
"lblESPHomePort": "Puerto de ESPHome Dashboard",
|
|
25
|
+
"lblEnableESPHome": "Puede ejecutar ESPHome Dashboard por separado o activar la siguiente opción para ejecutarlo de forma nativa en ioBroker.",
|
|
26
|
+
"lblEncryptionKey": "Clave de cifrado predeterminada",
|
|
27
|
+
"lblHeaderConnect": "Cómo conectar un dispositivo compatible con ESPHome a ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "Integración del panel ESPHome",
|
|
29
|
+
"lblIgnoreList": "Direcciones IP que se excluirán mediante el descubrimiento de dispositivos",
|
|
30
|
+
"lblInputApiPassword": "Contraseña API",
|
|
31
|
+
"lblInputDeviceIP-content": "Dirección IP del dispositivo",
|
|
32
|
+
"lblInputEncryptionKey": "Clave de encriptación",
|
|
33
|
+
"lblLoadDevices": "Actualizar descripción general del dispositivo",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "La tabla de dispositivos y el botón AGREGAR/Eliminar solo están disponibles si el adaptador está en ejecución",
|
|
35
|
+
"lbl_addUpdateDevice": "AGREGAR / Modificar dispositivos",
|
|
36
|
+
"maxRetry": "Reintento máximo de conexión antes de considerar el dispositivo como fuera de línea",
|
|
37
|
+
"reConInterval": "Configuración entre intentos de ioBroker para volver a conectar este dispositivo"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "Pour plus d'informations sur ESPHome, des exemples de configuration et des liens vers les communautés, veuillez visiter :",
|
|
3
|
+
"chkEnableESPHome": "Activer le tableau de bord ESPHome",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Découvrez uniquement les appareils sur cette interface",
|
|
5
|
+
"hlpInputApiPassword": "Mot de passe API (ancien, veuillez utiliser la clé de cryptage !)",
|
|
6
|
+
"hlpInputDeviceIP": "Sélectionnez l'appareil existant ou entrez l'adresse IP du nouvel appareil",
|
|
7
|
+
"hlpInputEncryptionKey": "Fournir une clé de cryptage spécifique à l'appareil (de préférence)",
|
|
8
|
+
"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 !",
|
|
9
|
+
"introLine-2": "ESPHome Dashboard est requis pour créer ces binaires. ",
|
|
10
|
+
"lblApiPass": "Mot de passe de l'API native par défaut (ancien)",
|
|
11
|
+
"lblAutoDiscovery": "Découverte de périphérique activée",
|
|
12
|
+
"lblConnectDetails-Line-1": "L'API native ESPHome est utilisée pour communiquer directement avec les clients, avec un protocole réseau hautement optimisé. ",
|
|
13
|
+
"lblConnectDetails-Line-2": "Après avoir ajouté une ligne api: à votre configuration ESPHome, vous pouvez accéder à cette page et attendre que l'appareil ESPHome apparaisse dans la section des appareils découverts (cela peut prendre jusqu'à 5 minutes) ou ajouter l'appareil manuellement en choisissant « ajouter un appareil ». ",
|
|
14
|
+
"lblConnectDetails-Line-3": "L'API native ESPHome est basée sur un protocole TCP personnalisé utilisant des tampons de protocole. ",
|
|
15
|
+
"lblConnectIobroker": "ioBroker communique directement par API native au lieu de MQTT pour vous offrir la meilleure expérience possible et la prise en charge des clés de chiffrement (recommandé) au lieu des mots de passe API/MQTT",
|
|
16
|
+
"lblDashboardLink": "Pour afficher le tableau de bord ESPHome dans l'onglet d'administration d'ioBroker, il est nécessaire de fournir l'IP-Ares sur lequel l'installation est en cours d'exécution.",
|
|
17
|
+
"lblDefaultCredentials": "Appareils de paramètres API/clés de cryptage par défaut (non recommandé)",
|
|
18
|
+
"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.",
|
|
19
|
+
"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.",
|
|
20
|
+
"lblDelDevice": "Supprimer l'appareil",
|
|
21
|
+
"lblDevicesTable": "Tous les appareils actuels (connus) et leur état de connexion",
|
|
22
|
+
"lblDiscoveryListeningAddress": "Adresse d'écoute",
|
|
23
|
+
"lblESPHomeIP": "Adresse IP sur laquelle ESPHome Dashboard est exécuté pour s'intégrer dans ioBroker Admin",
|
|
24
|
+
"lblESPHomePort": "Port du tableau de bord ESPHome",
|
|
25
|
+
"lblEnableESPHome": "Vous pouvez soit exécuter ESPHome Dashboard séparément, soit activer l'option ci-dessous pour l'exécuter nativement dans ioBroker",
|
|
26
|
+
"lblEncryptionKey": "Clé de cryptage par défaut",
|
|
27
|
+
"lblHeaderConnect": "Comment connecter un appareil compatible ESPHome à ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "Intégration du tableau de bord ESPHome",
|
|
29
|
+
"lblIgnoreList": "Adresses IP à exclure par la découverte de périphériques",
|
|
30
|
+
"lblInputApiPassword": "Mot de passe API",
|
|
31
|
+
"lblInputDeviceIP-content": "Adresse IP de l'appareil",
|
|
32
|
+
"lblInputEncryptionKey": "Clé de cryptage",
|
|
33
|
+
"lblLoadDevices": "Actualiser la présentation des appareils",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "Tableau des appareils et bouton AJOUTER/Supprimer disponibles uniquement si l'adaptateur est en cours d'exécution",
|
|
35
|
+
"lbl_addUpdateDevice": "AJOUTER/Modifier des appareils",
|
|
36
|
+
"maxRetry": "Nombre maximal de tentatives de connexion avant de considérer l'appareil comme hors ligne",
|
|
37
|
+
"reConInterval": "Paramètres entre ioBroker essayant de reconnecter cet appareil"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "Per ulteriori informazioni su ESPHome, esempi di configurazione e collegamenti alle comunità, visitare:",
|
|
3
|
+
"chkEnableESPHome": "Abilita la dashboard ESPHome",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Rileva solo i dispositivi su questa interfaccia",
|
|
5
|
+
"hlpInputApiPassword": "Password API (legacy, utilizza la chiave di crittografia!)",
|
|
6
|
+
"hlpInputDeviceIP": "Seleziona il dispositivo esistente o inserisci l'IP del nuovo dispositivo",
|
|
7
|
+
"hlpInputEncryptionKey": "Fornire una chiave di crittografia specifica per il dispositivo (preferibile)",
|
|
8
|
+
"introLine-1": "ioBroker ESPHome consente di gestire e controllare i dispositivi compatibili con ESPHome, devi creare e caricare questi binari da solo!",
|
|
9
|
+
"introLine-2": "Per creare questi file binari è necessario ESPHome Dashboard. ",
|
|
10
|
+
"lblApiPass": "Password API nativa predefinita (legacy)",
|
|
11
|
+
"lblAutoDiscovery": "Rilevamento dispositivo abilitato",
|
|
12
|
+
"lblConnectDetails-Line-1": "L'API nativa ESPHome viene utilizzata per comunicare direttamente con i clienti, con un protocollo di rete altamente ottimizzato. ",
|
|
13
|
+
"lblConnectDetails-Line-2": "Dopo aver aggiunto una linea api: alla configurazione di ESPHome puoi andare a questa pagina e attendere che il dispositivo ESPHome venga visualizzato nella sezione dei dispositivi rilevati (può richiedere fino a 5 minuti) o aggiungere il dispositivo manualmente scegliendo \"aggiungi dispositivo\" ",
|
|
14
|
+
"lblConnectDetails-Line-3": "L'API nativa ESPHome si basa su un protocollo TCP personalizzato che utilizza buffer di protocollo. ",
|
|
15
|
+
"lblConnectIobroker": "ioBroker comunica direttamente tramite API nativa anziché MQTT per offrirti la migliore esperienza possibile e il supporto delle chiavi di crittografia (consigliato) anziché delle password API/MQTT",
|
|
16
|
+
"lblDashboardLink": "Per mostrare la dashboard ESPHome nella scheda di amministrazione di ioBroker, è necessario fornire gli indirizzi IP su cui è in esecuzione l'installazione",
|
|
17
|
+
"lblDefaultCredentials": "Dispositivi di impostazione API/chiavi di crittografia predefinite (non consigliato)",
|
|
18
|
+
"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",
|
|
19
|
+
"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",
|
|
20
|
+
"lblDelDevice": "Elimina dispositivo",
|
|
21
|
+
"lblDevicesTable": "Tutti i dispositivi attuali (conosciuti) e il relativo stato di connessione",
|
|
22
|
+
"lblDiscoveryListeningAddress": "Indirizzo d'ascolto",
|
|
23
|
+
"lblESPHomeIP": "Indirizzo IP su cui è in esecuzione ESPHome Dashboard per l'integrazione in ioBroker Admin",
|
|
24
|
+
"lblESPHomePort": "Porta della dashboard ESPHome",
|
|
25
|
+
"lblEnableESPHome": "Puoi eseguire ESPHome Dashboard separatamente o attivare l'opzione seguente per eseguirlo nativo in ioBroker",
|
|
26
|
+
"lblEncryptionKey": "Chiave di crittografia predefinita",
|
|
27
|
+
"lblHeaderConnect": "Come connettere un dispositivo compatibile con ESPHome a ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "Integrazione della dashboard ESPHome",
|
|
29
|
+
"lblIgnoreList": "Indirizzi IP da escludere dal rilevamento del dispositivo",
|
|
30
|
+
"lblInputApiPassword": "Password dell'API",
|
|
31
|
+
"lblInputDeviceIP-content": "Indirizzo IP del dispositivo",
|
|
32
|
+
"lblInputEncryptionKey": "Chiave crittografica",
|
|
33
|
+
"lblLoadDevices": "Aggiorna la panoramica del dispositivo",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "La tabella dei dispositivi e il pulsante AGGIUNGI/Elimina sono disponibili solo se l'adattatore è in esecuzione",
|
|
35
|
+
"lbl_addUpdateDevice": "AGGIUNGI/MODIFICA DISPOSITIVI",
|
|
36
|
+
"maxRetry": "Numero massimo di tentativi di connessione prima di considerare il dispositivo offline",
|
|
37
|
+
"reConInterval": "Impostazione tra i tentativi di ioBroker di riconnettere questo dispositivo"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "Ga voor meer informatie over ESPHome, voorbeeldconfiguratie en links naar communities naar:",
|
|
3
|
+
"chkEnableESPHome": "Schakel ESPHome-dashboard in",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Ontdek alleen apparaten op deze interface",
|
|
5
|
+
"hlpInputApiPassword": "API-wachtwoord (verouderd, gebruik een coderingssleutel!)",
|
|
6
|
+
"hlpInputDeviceIP": "Selecteer bestaand apparaat of voer IP van nieuw apparaat in",
|
|
7
|
+
"hlpInputEncryptionKey": "Geef apparaatspecifieke coderingssleutel op (bij voorkeur)",
|
|
8
|
+
"introLine-1": "Met ioBroker ESPHome kunt u ESPHome-compatibele apparaten beheren en controleren. U moet deze binaire bestanden zelf maken en uploaden!",
|
|
9
|
+
"introLine-2": "ESPHome Dashboard is vereist om deze binaire bestanden te bouwen. ",
|
|
10
|
+
"lblApiPass": "API-wachtwoord (verouderd)",
|
|
11
|
+
"lblAutoDiscovery": "Apparaatdetectie ingeschakeld",
|
|
12
|
+
"lblConnectDetails-Line-1": "De native API van ESPHome wordt gebruikt om rechtstreeks met klanten te communiceren, met een sterk geoptimaliseerd netwerkprotocol. ",
|
|
13
|
+
"lblConnectDetails-Line-2": "Na het toevoegen van een api: lijn aan uw ESPHome-configuratie kunt u naar deze pagina gaan en wachten tot het ESPHome-apparaat verschijnt onder het gedeelte met ontdekte apparaten (kan tot 5 minuten duren) of het apparaat handmatig toevoegen door \"Apparaat toevoegen\" te kiezen ",
|
|
14
|
+
"lblConnectDetails-Line-3": "De native API van ESPHome is gebaseerd op een aangepast TCP-protocol dat gebruik maakt van protocolbuffers. ",
|
|
15
|
+
"lblConnectIobroker": "ioBroker communiceert rechtstreeks via Native API in plaats van MQTT om u de best mogelijke ervaring en ondersteuning te bieden met coderingssleutels (aanbevolen) in plaats van API/MQTT-wachtwoorden",
|
|
16
|
+
"lblDashboardLink": "Om het ESPHome-dashboard op het ioBroker-beheertabblad weer te geven, is het vereist om de IP-Ares op te geven waarop de installatie wordt uitgevoerd",
|
|
17
|
+
"lblDefaultCredentials": "Standaard API-/encryptiesleutelinstellingen apparaten (niet aanbevolen)",
|
|
18
|
+
"lblDefaultCredentials-Line-1": "Elk apparaat moet zijn eigen unieke coderingssleutel (aanbevolen) of API-wachtwoord hebben. Apparaatdetectie (indien ingeschakeld) detecteert alle apparaten en probeert verbinding te maken met onderstaande inloggegevens",
|
|
19
|
+
"lblDefaultCredentials-Line-2": "Als u een unieke coderingssleutel (aanbevolen) of API-wachtwoord toewijst, verschijnen nieuwe apparaten op het tabblad Ontdekte apparaten (of moeten ze worden toegevoegd) en moet u de unieke inloggegevens handmatig opgeven",
|
|
20
|
+
"lblDelDevice": "Apparaat verwijderen",
|
|
21
|
+
"lblDevicesTable": "Alle huidige (bekende) apparaten en hun verbindingsstatus",
|
|
22
|
+
"lblDiscoveryListeningAddress": "Luisteradres",
|
|
23
|
+
"lblESPHomeIP": "IP-adres waar ESPHome Dashboard wordt uitgevoerd om te integreren in ioBroker Admin",
|
|
24
|
+
"lblESPHomePort": "Haven van ESPHome-dashboard",
|
|
25
|
+
"lblEnableESPHome": "U kunt ESPHome Dashboard afzonderlijk uitvoeren of de onderstaande optie activeren om het native in ioBroker uit te voeren",
|
|
26
|
+
"lblEncryptionKey": "Standaard coderingssleutel",
|
|
27
|
+
"lblHeaderConnect": "Een ESPHome-compatibel apparaat verbinden met ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "ESPHome Dashboard-integratie",
|
|
29
|
+
"lblIgnoreList": "IP-adressen moeten worden uitgesloten bij apparaatdetectie",
|
|
30
|
+
"lblInputApiPassword": "API-wachtwoord",
|
|
31
|
+
"lblInputDeviceIP-content": "Apparaat IP-adres",
|
|
32
|
+
"lblInputEncryptionKey": "Encryptiesleutel",
|
|
33
|
+
"lblLoadDevices": "Apparaatoverzicht vernieuwen",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "Apparaattabel en knop TOEVOEGEN/verwijderen alleen beschikbaar als de adapter actief is",
|
|
35
|
+
"lbl_addUpdateDevice": "Apparaten toevoegen/wijzigen",
|
|
36
|
+
"maxRetry": "Maximale verbindingspoging voordat het apparaat als offline wordt beschouwd",
|
|
37
|
+
"reConInterval": "Instelling tussen ioBroker-pogingen om dit apparaat opnieuw te verbinden"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "Więcej informacji o ESPHome, przykładową konfigurację i linki do społeczności można znaleźć na stronie:",
|
|
3
|
+
"chkEnableESPHome": "Włącz panel ESPHome",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Odkrywaj tylko urządzenia na tym interfejsie",
|
|
5
|
+
"hlpInputApiPassword": "Hasło API (starsze, użyj klucza szyfrującego!)",
|
|
6
|
+
"hlpInputDeviceIP": "Wybierz istniejące urządzenie lub wprowadź adres IP nowego urządzenia",
|
|
7
|
+
"hlpInputEncryptionKey": "Podaj klucz szyfrowania specyficzny dla urządzenia (preferowany)",
|
|
8
|
+
"introLine-1": "ioBroker ESPHome pozwala zarządzać i kontrolować urządzenia obsługujące ESPHome, musisz samodzielnie utworzyć i przesłać te pliki binarne!",
|
|
9
|
+
"introLine-2": "Do zbudowania tych plików binarnych wymagany jest panel ESPHome Dashboard. ",
|
|
10
|
+
"lblApiPass": "Domyślne hasło do natywnego API (starsze)",
|
|
11
|
+
"lblAutoDiscovery": "Włączono wykrywanie urządzeń",
|
|
12
|
+
"lblConnectDetails-Line-1": "Natywny interfejs API ESPHome służy do bezpośredniej komunikacji z klientami za pomocą wysoce zoptymalizowanego protokołu sieciowego. ",
|
|
13
|
+
"lblConnectDetails-Line-2": "Po dodaniu linii api: do konfiguracji ESPHome możesz przejść na tę stronę i poczekać, aż urządzenie ESPHome pojawi się w sekcji wykrytych urządzeń (może to zająć do 5 minut) lub dodać urządzenie ręcznie, wybierając „dodaj urządzenie” ",
|
|
14
|
+
"lblConnectDetails-Line-3": "Natywny interfejs API ESPHome opiera się na niestandardowym protokole TCP wykorzystującym bufory protokołów. ",
|
|
15
|
+
"lblConnectIobroker": "ioBroker komunikuje się bezpośrednio przez Native API zamiast MQTT, aby zapewnić najlepszą możliwą obsługę i obsługę kluczy szyfrujących (zalecane) zamiast haseł API/MQTT",
|
|
16
|
+
"lblDashboardLink": "Aby wyświetlić panel ESPHome w zakładce administracyjnej ioBroker, wymagane jest podanie adresu IP, na którym działa instalacja",
|
|
17
|
+
"lblDefaultCredentials": "Domyślne ustawienia API/kluczy szyfrujących urządzenia (niezalecane)",
|
|
18
|
+
"lblDefaultCredentials-Line-1": "Każde urządzenie powinno mieć swój własny, unikalny klucz szyfrowania (zalecane) lub hasło API. Funkcja wykrywania urządzeń (jeśli jest włączona) wykrywa wszystkie urządzenia i próbuje połączyć się przy użyciu poniższych danych uwierzytelniających",
|
|
19
|
+
"lblDefaultCredentials-Line-2": "Jeśli przypiszesz unikalny klucz szyfrowania (zalecane) lub hasło API, nowe urządzenia pojawią się na karcie Wykryte urządzenia (lub muszą zostać dodane) i musisz ręcznie podać unikalne dane uwierzytelniające",
|
|
20
|
+
"lblDelDevice": "Usuń urządzenie",
|
|
21
|
+
"lblDevicesTable": "Wszystkie aktualne (znane) urządzenia i stan ich połączenia",
|
|
22
|
+
"lblDiscoveryListeningAddress": "Adres słuchania",
|
|
23
|
+
"lblESPHomeIP": "Adres IP, na którym działa panel ESPHome Dashboard w celu integracji z administratorem ioBroker",
|
|
24
|
+
"lblESPHomePort": "Port panelu ESPHome",
|
|
25
|
+
"lblEnableESPHome": "Możesz uruchomić panel ESPHome osobno lub aktywować poniższą opcję, aby uruchomić go natywnie w ioBroker",
|
|
26
|
+
"lblEncryptionKey": "Domyślny klucz szyfrowania",
|
|
27
|
+
"lblHeaderConnect": "Jak podłączyć urządzenie obsługujące ESPHome do ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "Integracja z panelem ESPHome",
|
|
29
|
+
"lblIgnoreList": "Adresy IP, które mają być wykluczone przy wykrywaniu urządzenia",
|
|
30
|
+
"lblInputApiPassword": "Hasło API",
|
|
31
|
+
"lblInputDeviceIP-content": "Adres IP urządzenia",
|
|
32
|
+
"lblInputEncryptionKey": "Klucz szyfrowania",
|
|
33
|
+
"lblLoadDevices": "Odśwież przegląd urządzeń",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "Tabela urządzeń i przycisk DODAJ/Usuń dostępne tylko wtedy, gdy adapter jest uruchomiony",
|
|
35
|
+
"lbl_addUpdateDevice": "DODAJ/Modyfikuj urządzenia",
|
|
36
|
+
"maxRetry": "Maksymalna liczba ponownych prób połączenia przed uznaniem urządzenia za offline",
|
|
37
|
+
"reConInterval": "Ustawienie między próbą ponownego podłączenia tego urządzenia przez ioBroker"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "Para obter mais informações sobre ESPHome, exemplos de configuração e links para comunidades, visite:",
|
|
3
|
+
"chkEnableESPHome": "Habilitar painel ESPHome",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Descubra apenas dispositivos nesta interface",
|
|
5
|
+
"hlpInputApiPassword": "Senha da API (herdada, use a chave de criptografia!)",
|
|
6
|
+
"hlpInputDeviceIP": "Selecione o dispositivo existente ou insira o IP do novo dispositivo",
|
|
7
|
+
"hlpInputEncryptionKey": "Forneça a chave de criptografia específica do dispositivo (preferencial)",
|
|
8
|
+
"introLine-1": "ioBroker ESPHome permite gerenciar e controlar dispositivos compatíveis com ESPHome. Você mesmo deve criar e fazer upload desses binários!",
|
|
9
|
+
"introLine-2": "O ESPHome Dashboard é necessário para construir esses binários. ",
|
|
10
|
+
"lblApiPass": "Senha padrão da API nativa (herdada)",
|
|
11
|
+
"lblAutoDiscovery": "Descoberta de dispositivos ativada",
|
|
12
|
+
"lblConnectDetails-Line-1": "A API nativa ESPHome é usada para comunicação direta com os clientes, com um protocolo de rede altamente otimizado. ",
|
|
13
|
+
"lblConnectDetails-Line-2": "Depois de adicionar uma linha api: à configuração do ESPHome, você pode ir para esta página e esperar que o dispositivo ESPHome apareça na seção de dispositivos descobertos (pode levar até 5 minutos) ou adicionar o dispositivo manualmente escolhendo “adicionar dispositivo” ",
|
|
14
|
+
"lblConnectDetails-Line-3": "A API nativa ESPHome é baseada em um protocolo TCP personalizado usando buffers de protocolo. ",
|
|
15
|
+
"lblConnectIobroker": "O ioBroker se comunica diretamente pela API nativa em vez do MQTT para fornecer a melhor experiência possível e suporte de chaves de criptografia (recomendado) em vez de senhas API/MQTT",
|
|
16
|
+
"lblDashboardLink": "Para mostrar o painel do ESPHome na aba de administração do ioBroker, é necessário fornecer os IP-Ares em que a instalação está sendo executada",
|
|
17
|
+
"lblDefaultCredentials": "Dispositivos de configurações de chaves de API/criptografia padrão (não recomendado)",
|
|
18
|
+
"lblDefaultCredentials-Line-1": "Cada dispositivo deve ter sua própria chave de criptografia exclusiva (recomendado) ou senha de API. A descoberta de dispositivos (quando ativada) detecta todos os dispositivos e tenta se conectar com as credenciais abaixo",
|
|
19
|
+
"lblDefaultCredentials-Line-2": "Se você atribuir uma chave de criptografia exclusiva (recomendado) ou uma senha de API, novos dispositivos aparecerão na guia Dispositivos descobertos (ou deverão ser adicionados) e você deverá fornecer as credenciais exclusivas manualmente",
|
|
20
|
+
"lblDelDevice": "Excluir dispositivo",
|
|
21
|
+
"lblDevicesTable": "Todos os dispositivos atuais (conhecidos) e seu estado de conexão",
|
|
22
|
+
"lblDiscoveryListeningAddress": "Endereço de escuta",
|
|
23
|
+
"lblESPHomeIP": "Endereço IP onde o ESPHome Dashboard está sendo executado para integração no ioBroker Admin",
|
|
24
|
+
"lblESPHomePort": "Painel do Porto do ESPHome",
|
|
25
|
+
"lblEnableESPHome": "Você pode executar o ESPHome Dashboard separadamente ou ativar a opção abaixo para executá-lo nativamente no ioBroker",
|
|
26
|
+
"lblEncryptionKey": "Chave de criptografia padrão",
|
|
27
|
+
"lblHeaderConnect": "Como conectar um dispositivo compatível com ESPHome ao ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "Integração do painel ESPHome",
|
|
29
|
+
"lblIgnoreList": "Endereços IP a serem excluídos pela descoberta de dispositivos",
|
|
30
|
+
"lblInputApiPassword": "Senha da API",
|
|
31
|
+
"lblInputDeviceIP-content": "Endereço IP do dispositivo",
|
|
32
|
+
"lblInputEncryptionKey": "Chave de encriptação",
|
|
33
|
+
"lblLoadDevices": "Atualizar visão geral do dispositivo",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "Tabela de dispositivos e botão ADICIONAR/Excluir disponíveis apenas se o adaptador estiver em execução",
|
|
35
|
+
"lbl_addUpdateDevice": "ADICIONAR/Modificar Dispositivos",
|
|
36
|
+
"maxRetry": "Tentativa máxima de conexão antes de considerar o dispositivo como off-line",
|
|
37
|
+
"reConInterval": "Configuração entre tentativas do ioBroker para reconectar este dispositivo"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "Для получения дополнительной информации о ESPHome, примерах конфигурации и ссылках на сообщества посетите:",
|
|
3
|
+
"chkEnableESPHome": "Включить панель управления ESPHome",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "Обнаруживать устройства только на этом интерфейсе",
|
|
5
|
+
"hlpInputApiPassword": "Пароль API (устаревший, используйте ключ шифрования!)",
|
|
6
|
+
"hlpInputDeviceIP": "Выберите существующее устройство или введите IP нового устройства.",
|
|
7
|
+
"hlpInputEncryptionKey": "Предоставьте ключ шифрования для конкретного устройства (предпочтительно)",
|
|
8
|
+
"introLine-1": "ioBroker ESPHome позволяет управлять устройствами, поддерживающими ESPHome, вы должны создавать и загружать эти двоичные файлы самостоятельно!",
|
|
9
|
+
"introLine-2": "Для сборки этих двоичных файлов требуется ESPHome Dashboard. ",
|
|
10
|
+
"lblApiPass": "Собственный пароль API по умолчанию (устаревший)",
|
|
11
|
+
"lblAutoDiscovery": "Обнаружение устройств включено",
|
|
12
|
+
"lblConnectDetails-Line-1": "Собственный API ESPHome используется для прямой связи с клиентами с помощью высокооптимизированного сетевого протокола. ",
|
|
13
|
+
"lblConnectDetails-Line-2": "После добавления строки api: в вашу конфигурацию ESPHome вы можете перейти на эту страницу и подождать, пока устройство ESPHome появится в разделе обнаруженных устройств (это может занять до 5 минут) или добавить устройство вручную, выбрав «Добавить устройство». ",
|
|
14
|
+
"lblConnectDetails-Line-3": "Собственный API ESPHome основан на специальном протоколе TCP с использованием буферов протокола. ",
|
|
15
|
+
"lblConnectIobroker": "ioBroker взаимодействует напрямую через Native API вместо MQTT, чтобы предоставить вам наилучшие возможности и поддержку ключей шифрования (рекомендуется) вместо паролей API/MQTT.",
|
|
16
|
+
"lblDashboardLink": "Чтобы отобразить панель управления ESPHome на вкладке администрирования ioBroker, необходимо указать IP-Ares, на котором выполняется установка.",
|
|
17
|
+
"lblDefaultCredentials": "Устройства настройки API/ключей шифрования по умолчанию (не рекомендуется)",
|
|
18
|
+
"lblDefaultCredentials-Line-1": "Каждое устройство должно иметь свой собственный уникальный ключ шифрования (рекомендуется) или пароль API. Обнаружение устройств (если включено) обнаруживает все устройства и пытается подключиться с учетными данными, указанными ниже.",
|
|
19
|
+
"lblDefaultCredentials-Line-2": "Если вы назначите уникальный ключ шифрования (рекомендуется) или пароль API, новые устройства будут отображаться на вкладке «Обнаруженные устройства» (или их необходимо будет добавить), и вам придется предоставить уникальные учетные данные вручную.",
|
|
20
|
+
"lblDelDevice": "Удалить устройство",
|
|
21
|
+
"lblDevicesTable": "Все текущие (известные) устройства и состояние их подключения",
|
|
22
|
+
"lblDiscoveryListeningAddress": "Адрес прослушивания",
|
|
23
|
+
"lblESPHomeIP": "IP-адрес, на котором работает панель управления ESPHome, для интеграции в администрацию ioBroker.",
|
|
24
|
+
"lblESPHomePort": "Панель управления портом ESPHome",
|
|
25
|
+
"lblEnableESPHome": "Вы можете запустить панель ESPHome Dashboard отдельно или активировать опцию ниже, чтобы запустить ее в ioBroker.",
|
|
26
|
+
"lblEncryptionKey": "Ключ шифрования по умолчанию",
|
|
27
|
+
"lblHeaderConnect": "Как подключить устройство с поддержкой ESPHome к ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "Интеграция панели управления ESPHome",
|
|
29
|
+
"lblIgnoreList": "IP-адреса, которые будут исключены при обнаружении устройства",
|
|
30
|
+
"lblInputApiPassword": "Пароль API",
|
|
31
|
+
"lblInputDeviceIP-content": "IP-адрес устройства",
|
|
32
|
+
"lblInputEncryptionKey": "Ключ шифрования",
|
|
33
|
+
"lblLoadDevices": "Обновить обзор устройства",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "Таблица устройств и кнопка «Добавить/Удалить» доступны только при работающем адаптере.",
|
|
35
|
+
"lbl_addUpdateDevice": "ДОБАВИТЬ/ИЗМЕНИТЬ УСТРОЙСТВА",
|
|
36
|
+
"maxRetry": "Максимальное количество повторных попыток подключения, прежде чем устройство будет считаться отключенным",
|
|
37
|
+
"reConInterval": "Настройка между попытками ioBroker повторно подключить это устройство"
|
|
38
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ESPHomeCommunityLink": "有关 ESPHome、示例配置和社区链接的更多信息,请访问:",
|
|
3
|
+
"chkEnableESPHome": "启用 ESPHome 仪表板",
|
|
4
|
+
"hlpDiscoveryListeningAddress": "只发现该接口上的设备",
|
|
5
|
+
"hlpInputApiPassword": "API密码(旧的,请使用加密密钥!)",
|
|
6
|
+
"hlpInputDeviceIP": "选择现有设备或输入新设备的IP",
|
|
7
|
+
"hlpInputEncryptionKey": "提供设备特定的加密密钥(首选)",
|
|
8
|
+
"introLine-1": "ioBroker ESPHome 允许管理和控制支持 ESPHome 的设备,您必须自己创建并上传这些二进制文件!",
|
|
9
|
+
"introLine-2": "构建这些二进制文件需要 ESPHome Dashboard。",
|
|
10
|
+
"lblApiPass": "默认本机 API 密码(旧版)",
|
|
11
|
+
"lblAutoDiscovery": "设备发现已启用",
|
|
12
|
+
"lblConnectDetails-Line-1": "ESPHome 原生 API 用于通过高度优化的网络协议直接与客户端通信。",
|
|
13
|
+
"lblConnectDetails-Line-2": "将 api: 行添加到 ESPHome 配置后,您可以转到此页面并等待 ESPHome 设备显示在已发现的设备部分下(最多可能需要 5 分钟),或者通过选择“添加设备”手动添加设备",
|
|
14
|
+
"lblConnectDetails-Line-3": "ESPHome 本机 API 基于使用协议缓冲区的自定义 TCP 协议。",
|
|
15
|
+
"lblConnectIobroker": "ioBroker 直接通过 Native API 而不是 MQTT 进行通信,为您提供最佳体验并支持加密密钥(推荐)而不是 API/MQTT 密码",
|
|
16
|
+
"lblDashboardLink": "要在 ioBroker 管理选项卡中显示 ESPHome 仪表板,需要提供运行安装的 IP-Ares",
|
|
17
|
+
"lblDefaultCredentials": "默认 API / 加密密钥设置设备(不推荐)",
|
|
18
|
+
"lblDefaultCredentials-Line-1": "每个设备都应该有自己唯一的加密密钥(推荐)或 API 密码,设备发现(启用后)会检测所有设备并尝试使用下面的凭据进行连接",
|
|
19
|
+
"lblDefaultCredentials-Line-2": "如果您分配唯一的加密密钥(推荐)或 API 密码,新设备将显示在“发现的设备”选项卡上(或必须添加),并且您必须手动提供唯一的凭据",
|
|
20
|
+
"lblDelDevice": "删除设备",
|
|
21
|
+
"lblDevicesTable": "所有当前(已知)设备及其连接状态",
|
|
22
|
+
"lblDiscoveryListeningAddress": "收听地址",
|
|
23
|
+
"lblESPHomeIP": "运行 ESPHome 仪表板以集成到 ioBroker Admin 中的 IP 地址",
|
|
24
|
+
"lblESPHomePort": "ESPHome 仪表板端口",
|
|
25
|
+
"lblEnableESPHome": "您可以单独运行 ESPHome Dashboard,也可以激活以下选项以在 ioBroker 中本机运行它",
|
|
26
|
+
"lblEncryptionKey": "默认加密密钥",
|
|
27
|
+
"lblHeaderConnect": "如何将支持 ESPHome 的设备连接到 ioBroker",
|
|
28
|
+
"lblHeaderMainPage": "ESPHome 仪表板集成",
|
|
29
|
+
"lblIgnoreList": "设备发现要排除的 IP 地址",
|
|
30
|
+
"lblInputApiPassword": "接口密码",
|
|
31
|
+
"lblInputDeviceIP-content": "设备 IP 地址",
|
|
32
|
+
"lblInputEncryptionKey": "加密密钥",
|
|
33
|
+
"lblLoadDevices": "刷新设备概览",
|
|
34
|
+
"lblTxtNoButtonsIfNotActive": "设备表和添加/删除按钮仅在适配器运行时可用",
|
|
35
|
+
"lbl_addUpdateDevice": "添加/修改设备",
|
|
36
|
+
"maxRetry": "将设备视为离线之前的最大连接重试次数",
|
|
37
|
+
"reConInterval": "ioBroker 尝试重新连接此设备之间的设置"
|
|
38
|
+
}
|
|
Binary file
|
|
Binary file
|
package/admin/img/dashboard.png
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|