iobroker.sonoff 5.0.0 → 5.1.1

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/README.md CHANGED
@@ -180,11 +180,30 @@ Since version 5.0 the objects get roles which the type-detector recognizes corre
180
180
 
181
181
  A device with several relays (`POWER1`, `POWER2`, ...) in one channel is still detected only as one device, as the type-detector finds every device type only once per channel.
182
182
 
183
+ ## Device manager
184
+ The devices are shown in the device manager of the admin with their relays, dimmers, colors, shutters and settings, which can be controlled directly there.
185
+
186
+ **Firmware update:** if "Check for firmware updates" is enabled (default), the adapter reads the latest Tasmota release from GitHub once a day. A Tasmota device with an older firmware shows the update indicator and the action "Update firmware". It sends `Upgrade 1` to the device, which downloads the firmware from its own OTA URL (by default the official release of its build variant, e.g. `tasmota` or `tasmota32`) and restarts. The dialog waits until the device reports the new version, at most 5 minutes. Development builds are not offered to be "updated" to the release they are based on.
187
+
188
+ **Search for devices:** the action "Search for devices" of the instance asks every address of the local networks (the /24 network of each own address) via the web interface of Tasmota for its status - the official Tasmota builds do not announce themselves by mDNS. The found devices are listed with their current MQTT settings, the ones already connected with this instance separately. For the selected devices the adapter enables MQTT and writes the MQTT server, port, user and password (`Backlog SetOption3 1; MqttHost ...; MqttPort ...; MqttUser ...; MqttPassword ...`). The settings are prefilled with the own address and the port and credentials of the built-in server, in bridge mode with the external broker. The devices restart and appear in the list as soon as they are connected. Devices with a web password require it in the form. If ioBroker runs in a Docker container without host network, only the network of the container is searched.
189
+
190
+ The device card shows the connection and the Wi-Fi signal (`Wifi_Signal` in dBm) live.
191
+
183
192
  <!--
184
193
  Placeholder for the next version (at the beginning of the line):
185
194
  ### **WORK IN PROGRESS**
186
195
  -->
187
196
  ## Changelog
197
+ ### 5.1.1 (2026-10-13)
198
+ * (@GermanBluefox) Admin 7.6.20+ is required. Added missing translations. The tests run on Windows and macOS too
199
+
200
+ ### 5.1.0 (2026-10-13)
201
+ * (@GermanBluefox) Device manager: firmware update of Tasmota devices. The latest release is read from GitHub once a day (option "Check for firmware updates"), devices with an older firmware show the update indicator. The update is started with `Upgrade 1`, so the device downloads the firmware from its own OTA URL
202
+ * (@GermanBluefox) Device manager: search for Tasmota devices in the network and connect them with ioBroker (enables MQTT and writes server, port, user and password)
203
+ * (@GermanBluefox) Device manager: the connection state and the Wi-Fi signal are updated live, the signal is shown in dBm (`Wifi_Signal`) instead of the link quality in percent. Toggles like `Fade` are switches instead of buttons
204
+ * (@GermanBluefox) The devices are linked with their `alive` state (`common.statusStates`), so admin shows in the object tree whether a device is connected
205
+ * (@GermanBluefox) The port of the built-in MQTT server is reported to js-controller 8 as a used resource (`common.declareUsedResources`), so admin shows which ports are occupied. In bridge mode no port is reported. If the port is already used, the log names the instance that occupies it
206
+
188
207
  ### 5.0.0 (2026-10-13)
189
208
  * (@GermanBluefox) Breaking change: the roles of the objects change, see [Roles of the objects since 5.0](#roles-of-the-objects-since-50)
190
209
  * (@GermanBluefox) Better roles for the type-detector: diagnostic values (e.g. `Wifi_Channel`, `Heap`, `MqttPort`) are not detected as dimmer, blind or window anymore, `POWER` is the switch of RGB lights and `switch.power` of the relays is migrated to `switch`, `Scheme` is the light effect. The roles of the existing objects are updated, roles changed by the user are kept
@@ -198,46 +217,6 @@ A device with several relays (`POWER1`, `POWER2`, ...) in one channel is still d
198
217
  ### 4.2.0 (2026-09-07)
199
218
  * (@patricknitsch) Added Device Manager for existing devices
200
219
 
201
- ### 4.0.0 (2026-08-13)
202
- * (ioBroker-Bot) Adapter requires js-controller >= 6.0.11 now.
203
- * (stony2k) Added bridge mode to connect to an external MQTT broker instead of running a built-in broker
204
- * (stony2k) Fixed the alive state object not being created (warning "has no existing object")
205
- * (@GermanBluefox/GreatSUN) Fixed the names of data points inside a group: since 3.3.0 e.g. `SML_Total_in` was created as `SML_in` (#489)
206
- * (@GermanBluefox/baetzst) The MAC address and the other network and firmware information of a device are stored as data points (`INFO.Mac`, `INFO.Gateway`, `INFO.Hardware`, ...) (#513)
207
- * (@GermanBluefox) Server mode: the adapter requests `Status 5` and `Status 2` from a device with its first message, so the INFO states are filled even if the device did not reboot
208
- * (@GermanBluefox) The states which were created with a shortened name by 3.3.x are listed in the log on start, so they can be deleted (#489)
209
- * (@GermanBluefox) Bridge mode: the topics to subscribe are configurable now, and nested full topics as well as OpenBeken topics are supported
210
- * (@GermanBluefox) Bridge mode: devices are named after their MQTT client ID like with the built-in broker and are no longer renamed by less reliable sources
211
- * (@GermanBluefox) Bridge mode: the `alive` state is set from the last will topic (LWT), so devices are recognized as offline
212
- * (@GermanBluefox) Commands for auto-created states are sent to `cmnd/...` again, also for nested full topics
213
- * (@GermanBluefox) `info.connection` contains the list of the connected clients again (server mode), in bridge mode the URL of the broker
214
- * (@GermanBluefox/patricknitsch) Bridge mode: support for the full topic structure `%topic%/%prefix%/` (device first), detected automatically per device
215
- * (@GermanBluefox/patricknitsch) Bridge mode: encrypted connections with CA/client certificates and optional certificate check, configurable client ID, keepalive and clean session
216
- * (@GermanBluefox/patricknitsch) Bridge mode: a fix prefix in front of the full topic (e.g. `gateway/tele/device/STATE`) is recognized and used for the commands
217
- * (@Apollon77/@copilot) Added support for OpenBeken LED datapoints (led_enableAll, led_dimmer, led_temperature, led_basecolor_rgb, led_finalcolor_rgbcw, led_basecolor_rgbcw, led_hue, led_saturation) - enables control of OpenBeken LED devices with automatic topic mapping for /get and /set suffixes
218
- * (@Apollon77/@copilot) Added PulseTime1-PulseTime16 datapoint support - users can now read and set PulseTime values directly from ioBroker to control relay auto-off timers
219
- * (@GermanBluefox) Breaking: a minimal supported Node.js version is now 22
220
-
221
- ### 3.3.0 (2025-09-20)
222
- * (@Apollon77/@copilot) **IMPORTANT**: Commands now correctly use `cmnd/` prefix instead of `tele/` prefix
223
- * (@Apollon77/@copilot) Added configuration for advanced MQTT settings
224
- * (@Apollon77/@copilot) Fixed shutter command mapping to use the correct Tasmota format - Transforms Shutter1_Position to ShutterPosition1 for proper device control
225
- * (@Apollon77/@copilot) Fixed IRHVAC Power, Light and Mode fields showing NULL instead of actual string values
226
- * (@Apollon77/@copilot) Added Zigbee device control support for Tasmota coordinators - users can now control Zigbee devices (Power/Dimmer) through ioBroker states via automatic ZbSend command generation
227
- * (@Apollon77/@copilot) Added support for Tasmota tele/MARGINS messages enabling integration of PowerLow, PowerHigh, and PowerDelta limits
228
- * (@Apollon77/@copilot) Fixed POW R2 energy datapoints not being created by enabling TELE_STATE by default
229
- * (@Apollon77/@copilot) Fixed pressure and temperature unit display to respect PressureUnit and TempUnit from Tasmota MQTT messages
230
- * (@Apollon77/@copilot) Added support for decoupled button actions in Tasmota devices - creates Button1-Button8 datapoints for button events
231
- * (@Apollon77/@copilot) Fixed RESULT message processing bug where tele/*/RESULT messages were incorrectly processed as WAKEUP instead of RESULT
232
- * (@Apollon77/@copilot) Fixed the deprecated value.power.consumption role for ENERGY_Power datapoint to improve device detection
233
- * (@Apollon77/@copilot) Added support for SHUTTER5-SHUTTER16 datapoints for ESP32 shutter32 devices
234
- * (@Apollon77/@copilot) Updated admin UI responsive design to use ioBroker standard values for mobile compatibility
235
- * (@Apollon77/@copilot) Added support for Sonoff B1 (RGB LED) and Sonoff SC (Environmental Sensor) devices with proper value ranges
236
- * (@Apollon77/@copilot) Added meaningful state labels for Scheme datapoint (color animation schemes)
237
- * (@Apollon77/@copilot) Added a configuration option to suppress "not connected" warnings for temporarily offline devices
238
- * (@Apollon77/@copilot) Added Switch5-Switch28 datapoint definitions for consistent boolean mapping
239
- * (@Apollon77/@copilot) Fixed a write flag for all Switch datapoints to enable proper control from ioBroker
240
-
241
220
  ## License
242
221
 
243
222
  The MIT License (MIT)
@@ -87,5 +87,11 @@
87
87
  "connected": "verbunden",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "z.B. mqtt://192.168.1.100:1883 oder mqtts://broker:8883",
89
89
  "ms": "ms",
90
- "sec": "Sekunde"
90
+ "sec": "Sekunde",
91
+ "Check for firmware updates": "Nach Firmware-Updates suchen",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Liest einmal täglich die neueste Tasmota-Version von GitHub, damit der Gerätemanager die Geräte aktualisieren kann",
93
+ "Port": "Port",
94
+ "User": "Benutzer",
95
+ "Password": "Passwort",
96
+ "in seconds": "in Sekunden"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "connected",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883",
89
89
  "ms": "ms",
90
- "sec": "sec"
90
+ "sec": "sec",
91
+ "Check for firmware updates": "Check for firmware updates",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices",
93
+ "Port": "Port",
94
+ "User": "User",
95
+ "Password": "Password",
96
+ "in seconds": "in seconds"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "conectado",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "ej. mqtt://192.168.1.100:1883 o mqtts://broker:8883",
89
89
  "ms": "EM",
90
- "sec": "segundo"
90
+ "sec": "segundo",
91
+ "Check for firmware updates": "Buscar actualizaciones de firmware",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Lee una vez al día la última versión de Tasmota desde GitHub, para que el administrador de dispositivos pueda actualizar los dispositivos",
93
+ "Port": "Puerto",
94
+ "User": "Usuario",
95
+ "Password": "Contraseña",
96
+ "in seconds": "en segundos"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "connecté",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "ex. mqtt://192.168.1.100:1883 ou mqtts://broker:8883",
89
89
  "ms": "MS",
90
- "sec": "seconde"
90
+ "sec": "seconde",
91
+ "Check for firmware updates": "Rechercher des mises à jour du firmware",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Lit une fois par jour la dernière version de Tasmota sur GitHub, afin que le gestionnaire d'appareils puisse mettre à jour les appareils",
93
+ "Port": "Port",
94
+ "User": "Utilisateur",
95
+ "Password": "Mot de passe",
96
+ "in seconds": "en secondes"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "collegato",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "es. mqtt://192.168.1.100:1883 o mqtts://broker:8883",
89
89
  "ms": "SM",
90
- "sec": "sicurezza"
90
+ "sec": "sicurezza",
91
+ "Check for firmware updates": "Controlla aggiornamenti del firmware",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Legge una volta al giorno l'ultima versione di Tasmota da GitHub, così il gestore dispositivi può aggiornare i dispositivi",
93
+ "Port": "Porta",
94
+ "User": "Utente",
95
+ "Password": "Password",
96
+ "in seconds": "in secondi"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "conectado",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "bijv. mqtt://192.168.1.100:1883 of mqtts://broker:8883",
89
89
  "ms": "mevrouw",
90
- "sec": "sec"
90
+ "sec": "sec",
91
+ "Check for firmware updates": "Controleren op firmware-updates",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Leest eenmaal per dag de nieuwste Tasmota-versie van GitHub, zodat de apparaatbeheerder de apparaten kan bijwerken",
93
+ "Port": "Poort",
94
+ "User": "Gebruiker",
95
+ "Password": "Wachtwoord",
96
+ "in seconds": "in seconden"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "połączony",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "np. mqtt://192.168.1.100:1883 lub mqtts://broker:8883",
89
89
  "ms": "SM",
90
- "sec": "sek"
90
+ "sec": "sek",
91
+ "Check for firmware updates": "Sprawdzaj aktualizacje oprogramowania",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Raz dziennie odczytuje najnowszą wersję Tasmota z GitHub, aby menedżer urządzeń mógł aktualizować urządzenia",
93
+ "Port": "Port",
94
+ "User": "Użytkownik",
95
+ "Password": "Hasło",
96
+ "in seconds": "w sekundach"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "conectado",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "ex. mqtt://192.168.1.100:1883 ou mqtts://broker:8883",
89
89
  "ms": "EM",
90
- "sec": "seg"
90
+ "sec": "seg",
91
+ "Check for firmware updates": "Verificar atualizações de firmware",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Lê a versão mais recente do Tasmota no GitHub uma vez por dia, para que o gerenciador de dispositivos possa atualizar os dispositivos",
93
+ "Port": "Porta",
94
+ "User": "Usuário",
95
+ "Password": "Senha",
96
+ "in seconds": "em segundos"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "успешно",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "например mqtt://192.168.1.100:1883 или mqtts://broker:8883",
89
89
  "ms": "РС",
90
- "sec": "сек"
90
+ "sec": "сек",
91
+ "Check for firmware updates": "Проверять обновления прошивки",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Раз в день считывает последнюю версию Tasmota с GitHub, чтобы менеджер устройств мог обновлять устройства",
93
+ "Port": "Порт",
94
+ "User": "Пользователь",
95
+ "Password": "Пароль",
96
+ "in seconds": "в секундах"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "підключений",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "наприклад mqtt://192.168.1.100:1883 або mqtts://broker:8883",
89
89
  "ms": "РС",
90
- "sec": "сек"
90
+ "sec": "сек",
91
+ "Check for firmware updates": "Перевіряти оновлення прошивки",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "Раз на день зчитує останню версію Tasmota з GitHub, щоб менеджер пристроїв міг оновлювати пристрої",
93
+ "Port": "Порт",
94
+ "User": "Користувач",
95
+ "Password": "Пароль",
96
+ "in seconds": "у секундах"
91
97
  }
@@ -87,5 +87,11 @@
87
87
  "connected": "连接的",
88
88
  "e.g. mqtt://192.168.1.100:1883 or mqtts://broker:8883": "例如 mqtt://192.168.1.100:1883 或 mqtts://broker:8883",
89
89
  "ms": "多发性硬化症",
90
- "sec": "秒"
90
+ "sec": "秒",
91
+ "Check for firmware updates": "检查固件更新",
92
+ "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices": "每天从 GitHub 读取一次最新的 Tasmota 版本,以便设备管理器可以更新设备",
93
+ "Port": "端口",
94
+ "User": "用户",
95
+ "Password": "密码",
96
+ "in seconds": "以秒为单位"
91
97
  }
@@ -101,8 +101,8 @@
101
101
  "xs": 12,
102
102
  "sm": 12,
103
103
  "md": 3,
104
- "lg": 6,
105
- "xl": 6
104
+ "lg": 3,
105
+ "xl": 3
106
106
  },
107
107
  "externalBrokerRejectUnauthorized": {
108
108
  "newLine": true,
@@ -333,6 +333,16 @@
333
333
  "lg": 4,
334
334
  "xl": 4
335
335
  },
336
+ "checkFirmware": {
337
+ "type": "checkbox",
338
+ "label": "Check for firmware updates",
339
+ "help": "Reads the latest Tasmota release from GitHub once a day, so the device manager can update the devices",
340
+ "xs": 12,
341
+ "sm": 12,
342
+ "md": 6,
343
+ "lg": 4,
344
+ "xl": 4
345
+ },
336
346
  "_header5": {
337
347
  "newLine": true,
338
348
  "type": "header",