iobroker.govee-smart 2.0.2 → 2.0.3

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
@@ -61,7 +61,7 @@ Full user documentation lives in the **[Wiki](https://github.com/krobipd/ioBroke
61
61
  ## Requirements
62
62
 
63
63
  - Node.js >= 20
64
- - ioBroker js-controller >= 7.0.23
64
+ - ioBroker js-controller >= 6.0.11
65
65
  - ioBroker Admin >= 7.6.20
66
66
  - A Govee account and at least one Govee WiFi device. LAN control needs a light with LAN mode enabled in the Govee Home app — see Govee's [LAN-supported device list](https://app-h5.govee.com/user-manual/wlan-guide).
67
67
 
@@ -106,6 +106,8 @@ This adapter's MQTT authentication and BLE-over-LAN (ptReal) protocol implementa
106
106
  ---
107
107
 
108
108
  ## Changelog
109
+ ### 2.0.3 (2026-04-26)
110
+ - Min js-controller correction: was incorrectly bumped to `>=7.0.23` in 2.0.2 (and admin downgraded from `>=7.6.20` to `>=7.6.17`). The repochecker-recommended values are `>=6.0.11` / `>=7.6.20` — restored.
109
111
 
110
112
  ### 2.0.2 (2026-04-26)
111
113
  - OpenAPI MQTT now keeps a stable client ID across reconnects (was `Date.now`-based, which Govee's broker treats as new connections).
@@ -132,18 +134,6 @@ This adapter's MQTT authentication and BLE-over-LAN (ptReal) protocol implementa
132
134
  - Duplicate scene names from the cloud are auto-disambiguated with `" (2)"`, `" (3)"` suffixes; reverse-lookup is deterministic.
133
135
  - The adapter acks back the canonical key after activation, so the dropdown stays in sync regardless of how the value was written.
134
136
 
135
- ### 1.10.1 (2026-04-20)
136
- - Refresh button no longer re-fetches static SKU libraries (scene/music/DIY/features) — call count drops from ~7 to 2 per device per click. The endpoints returned 403 for many accounts and just produced minute-long rate-limiter backlogs.
137
-
138
- ### 1.10.0 (2026-04-20)
139
- - Multi-packet A3 BLE scenes (`scenceParam`) are now activated via Cloud on devices without segments; bulbs and Curtain Lights silently dropped those packets before, so complex scenes never played.
140
- - Powering a device off resets every mode dropdown to `"---"` — both ioBroker and Govee-app initiated off events.
141
-
142
- ### 1.9.1 (2026-04-20)
143
- - Each Cloud list (scenes / DIY / snapshots) is now guarded independently. Govee's `/device/scenes` sometimes returns e.g. 149 scenes + 0 snapshots when a snapshot clearly exists; the old combined guard then wiped existing snapshots and the dropdown errored on click.
144
-
145
- Older entries have been moved to [CHANGELOG_OLD.md](CHANGELOG_OLD.md).
146
-
147
137
  ## Support
148
138
 
149
139
  - [Wiki](https://github.com/krobipd/ioBroker.govee-smart/wiki) — user documentation (EN / DE)
package/io-package.json CHANGED
@@ -1,8 +1,21 @@
1
1
  {
2
2
  "common": {
3
3
  "name": "govee-smart",
4
- "version": "2.0.2",
4
+ "version": "2.0.3",
5
5
  "news": {
6
+ "2.0.3": {
7
+ "en": "Min js-controller correction: was incorrectly bumped to `>=7.0.23` in 2.0.2 (and admin downgraded from `>=7.6.20` to `>=7.6.17`). The repochecker-recommended values are `>=6.0.11` / `>=7.6.20` — restored.",
8
+ "de": "Min js-Controller-Korrektur: wurde falsch auf `>=7.0.23` in 2.0.2 (und admin downgraded von `>=7.6.20` auf `>=7.6.17 `) gesprungen. Die repochecker-recommended Werte sind `>=6.0.11 ` / `>=7.6.20 ` - restauriert.",
9
+ "ru": "Коррекция Min js-контроллера: в 2.0.2 она была неправильно увеличена до «>=7.0.23» (и админ был понижен с «>=7.6.20» до «>=7.6.17»). Рекомендуемые значения репочекера - \">=6.0.11\" / \">=7.6.20\" - восстановлены.",
10
+ "pt": "Min js-controller correção: foi incorretamente bateu para `>=7.0.23` em 2.0.2 (e admin desclassificado de `>=7.6,20` para `>=7.6.17`). Os valores recomendados pelo repochecker são `>=6.0.11` / `>=7.6.20` — restaurados.",
11
+ "nl": "Min js-controller correctie: werd foutief gestoten naar De door de repochecker aanbevolen waardes zijn hersteld.",
12
+ "fr": "Correction de l'administrateur de Min js: a été incorrectement cognée à `>=7.0.23` en 2.0.2 (et l'administrateur a été rétrogradé de `>=7.6.20` à `>=7.6.17`). Les valeurs recommandées par repochecker sont `>=6.0.11` / `>=7.6.20` - restaurées.",
13
+ "it": "Min js-controller correzione: è stato erroneamente urtato a `>=7.0.23` in 2.0.2 (e admin downgraded da `>=7.6.20` a `>=7.6.17`). I valori repochecker-recommended sono `>=6.0.11` / `>=7.6.20` — ripristinati.",
14
+ "es": "Min js-controller correction: was incorrectly toped to ` ` {=7.0.23` in 2.0.2 (and admin downgraded from ` {=7.6.20` to ` {=7.6.17`). Los valores recomendados por el depositchecker son \" confianza=6.0.11 \" / ` confianza=7.6.20 \" , restaurados.",
15
+ "pl": "Korekta Min js- controller: została nieprawidłowo przeskoczona do '> = 7.0.23' w 2.0.2 (a admin zmniejszył się z '> = 7.6.20' do '> = 7.6.17'). Zalecane wartości repochecker- to '> = 6.0.11' / '> = 7.6.20' - przywrócone.",
16
+ "uk": "Нормативно звернулися до `>=7.0.23` в 2.0.2 (і адміністратором, опущений від `>=7.6.20` до `>=7.6.17`). Репочекерно-відновлені значення `>=6.0.11` / `>=7.6.20` — відновлено.",
17
+ "zh-cn": "Min js-controler更正:错误地在2.0.2中跌至QQ7.0.23 ' (行政级别从QQ7.6.20`降至QQ7.6.17)。 重新检查器推荐的数值为6.0.11` /`7.6.20 ' ——恢复."
18
+ },
6
19
  "2.0.2": {
7
20
  "en": "OpenAPI MQTT now uses a stable client ID across reconnects (Govee's broker treated each reconnect as a new connection). Min js-controller bumped to >=7.0.23. Consistency cleanup vs. the other krobi adapters.",
8
21
  "de": "OpenAPI MQTT verwendet jetzt eine stabile Client-ID über Reconnects hinweg (Goveeas Broker behandelte jeden Reconnect bisher als neue Verbindung). js-controller-Mindestversion auf >=7.0.23 angehoben. Konsistenz-Cleanup gegenüber den anderen krobi-Adaptern.",
@@ -17,82 +30,69 @@
17
30
  "zh-cn": "OpenAPI MQTT 现在在重新连接时使用稳定的 client ID(Govee 的 broker 之前将每次重连视为新连接)。js-controller 最低版本提升到 >=7.0.23。与其他 krobi 适配器的一致性清理。"
18
31
  },
19
32
  "2.0.1": {
20
- "en": "Hotfixes from real-world v2.0.0 install. Sensor state IDs (battery, temperature, humidity, …) now route to sensor/ instead of control/, and the state objects are created lazily on first write — fixes the \"control.battery has no existing object\" warning. Snapshots and scenes are no longer attached to non-light devices like thermometers and heaters. The boot-time \"27 experimental device(s) detected\" log dump was replaced with a targeted, once-per-SKU nudge that only fires when a real device of an experimental SKU appears. The redundant \"OpenAPI MQTT connected for sensor events\" info line was dropped (the adapter-ready summary already covers it). The govee-appliances v0.1.0 deprecation tag now also has its GitHub release page.",
21
- "de": "Hotfixes aus dem realen v2.0.0-Install. Sensor-State-IDs (battery, temperature, humidity, …) landen jetzt unter sensor/ statt control/, und die State-Objekte werden bei der ersten Schreibung lazy angelegt — fixt die Warnung „control.battery has no existing object\". Snapshots und Szenen werden nicht mehr an Nicht-Lights wie Thermometer oder Heizgeräte gehängt. Das Start-Log mit „27 experimentelle Geräte erkannt\" ist weg — stattdessen kommt ein gezielter Hinweis nur dann, wenn ein reales Gerät einer experimentellen SKU auftaucht. Die redundante „OpenAPI MQTT connected for sensor events\"-Info-Zeile fällt weg (der Adapter-Ready-Summary deckt sie). Der govee-appliances v0.1.0-Deprecation-Tag hat jetzt auch eine GitHub-Release-Seite.",
22
- "ru": "Хотфиксы из реальной установки v2.0.0. Sensor-State-IDs (battery, temperature, humidity, …) теперь идут в sensor/ вместо control/, и State-объекты создаются лениво при первой записи исправляет предупреждение «control.battery has no existing object». Snapshots и сцены больше не прикрепляются к не-Light устройствам. Spam-лог «27 experimental devices detected» заменён на целевое уведомление только при появлении реального устройства экспериментального SKU. Избыточная info-строка «OpenAPI MQTT connected for sensor events» убрана.",
23
- "pt": "Correções de uma instalação real v2.0.0. IDs de state de sensor (battery, temperature, humidity, …) agora vão para sensor/ em vez de control/, e os objetos de state são criados lazily na primeira gravação corrige o aviso «control.battery has no existing object». Snapshots e cenas não são mais anexados a dispositivos não-Light. O dump de log «27 experimental devices detected» foi substituído por uma notificação direcionada apenas quando um dispositivo real de SKU experimental aparece. A linha info redundante «OpenAPI MQTT connected for sensor events» foi removida.",
24
- "nl": "Hotfixes uit een echte v2.0.0-installatie. Sensor-state-IDs (battery, temperature, humidity, …) gaan nu naar sensor/ in plaats van control/, en de state-objecten worden lazy aangemaakt bij de eerste schrijfactie — repareert de waarschuwing «control.battery has no existing object». Snapshots en scènes worden niet meer aan niet-Light apparaten gekoppeld. De boot-log dump «27 experimental devices detected» is vervangen door een gerichte melding alleen bij een echt apparaat van een experimentele SKU. De overbodige info-regel «OpenAPI MQTT connected for sensor events» is verwijderd.",
25
- "fr": "Correctifs d'une installation v2.0.0 réelle. Les ID d'état de capteur (battery, temperature, humidity, …) vont maintenant vers sensor/ au lieu de control/, et les objets d'état sont créés paresseusement à la première écriture corrige l'avertissement « control.battery has no existing object ». Les snapshots et scènes ne sont plus attachés aux appareils non-Light. Le dump de log « 27 experimental devices detected » a été remplacé par une notification ciblée uniquement quand un appareil réel d'un SKU expérimental apparaît. La ligne info redondante « OpenAPI MQTT connected for sensor events » a été supprimée.",
26
- "it": "Correzioni da un'installazione v2.0.0 reale. Gli ID di state dei sensori (battery, temperature, humidity, …) ora vanno in sensor/ invece di control/, e gli oggetti di state vengono creati lazy alla prima scrittura risolve l'avviso «control.battery has no existing object». Snapshot e scene non vengono più collegati a dispositivi non-Light. Il dump di log all'avvio «27 experimental devices detected» è stato sostituito con una notifica mirata solo quando appare un dispositivo reale di una SKU sperimentale. La riga info ridondante «OpenAPI MQTT connected for sensor events» è stata rimossa.",
27
- "es": "Correcciones de una instalación v2.0.0 real. Los IDs de state de sensor (battery, temperature, humidity, …) ahora van a sensor/ en lugar de control/, y los objetos de state se crean perezosamente en la primera escritura corrige la advertencia «control.battery has no existing object». Snapshots y escenas ya no se adjuntan a dispositivos no-Light. El volcado de log al inicio «27 experimental devices detected» fue reemplazado por una notificación dirigida solo cuando aparece un dispositivo real de un SKU experimental. La línea info redundante «OpenAPI MQTT connected for sensor events» fue eliminada.",
28
- "pl": "Poprawki z prawdziwej instalacji v2.0.0. Sensor-state-ID (battery, temperature, humidity, …) trafiają teraz do sensor/ zamiast control/, a obiekty state tworzone leniwie przy pierwszym zapisie — naprawia ostrzeżenie «control.battery has no existing object». Snapshoty i sceny nie już dołączane do urządzeń nie-Light. Log startowy «27 experimental devices detected» został zastąpiony celowym powiadomieniem tylko gdy pojawia się prawdziwe urządzenie eksperymentalnego SKU. Zbędna linia info «OpenAPI MQTT connected for sensor events» została usunięta.",
29
- "uk": "Хотфікси з реальної інсталяції v2.0.0. Sensor-state-ID (battery, temperature, humidity, …) тепер ідуть до sensor/ замість control/, а state-об'єкти створюються лінувато при першому записі виправляє попередження «control.battery has no existing object». Снапшоти й сцени більше не прикріплюються до не-Light пристроїв. Запис при старті «27 experimental devices detected» замінено на цільове сповіщення лише коли з'являється реальний пристрій експериментального SKU. Зайвий info-рядок «OpenAPI MQTT connected for sensor events» прибрано.",
30
- "zh-cn": "来自真实 v2.0.0 安装的热修复。传感器状态 ID (battery, temperature, humidity, …) 现在路由到 sensor/ 而不是 control/,并且状态对象在第一次写入时延迟创建——修复「control.battery has no existing object」警告。快照和场景不再附加到非灯设备。启动时的「27 experimental devices detected」日志转储已被替换为仅在出现真实实验性 SKU 设备时的定向通知。冗余的「OpenAPI MQTT connected for sensor events」信息行已删除。"
33
+ "en": "Hotfixes from a real-world v2.0.0 install. Sensor states route to sensor/, event states to events/ (was control/ for both); state objects are created lazily on first write. Snapshots and scenes only attach to lights now; thermometers/heaters/kettles no longer get snapshot states. Boot-time experimental-device log dump removed.",
34
+ "de": "Hotfixes aus dem realen v2.0.0-Install. Sensor-States landen jetzt unter sensor/, Event-States unter events/ (vorher control/ für beide); State-Objekte werden lazy beim ersten Schreiben angelegt. Snapshots und Szenen hängen jetzt nur noch an Leuchten; Thermometer/Heizgeräte/Wasserkocher bekommen keine Snapshot-States mehr. Der experimental-device-Log-Dump beim Start entfällt.",
35
+ "ru": "Хотфіксы після реальної інсталяції v2.0.0. State-IDs сенсорів тепер розташовуються в sensor/, події в events/ (раніше control/); state-об'єкти створюються лениво при першому записі. Snapshots і сцени тепер прикріплюються лише до ламп; термометри/обігрівачі/чайники більше не отримують snapshot-states. Стартовий experimental-device-лог прибрано.",
36
+ "pt": "Correções de uma instalação real do v2.0.0. Os states de sensor agora ficam em sensor/, os de eventos em events/ (antes control/ para ambos); os objetos são criados de forma preguiçosa na primeira escrita. Snapshots e cenas se anexam a luzes agora; termômetros/aquecedores/chaleiras não recebem mais snapshot-states. O log de experimental devices na inicialização foi removido.",
37
+ "nl": "Hotfixes na een echte v2.0.0-installatie. Sensor-states lopen nu naar sensor/, event-states naar events/ (was eerder control/ voor beide); state-objecten worden lui aangemaakt bij de eerste schrijving. Snapshots en scènes hangen nu alleen nog aan lampen; thermometers/verwarmingen/waterkokers krijgen geen snapshot-states meer. De boot-tijd experimental-device-logdump is weg.",
38
+ "fr": "Correctifs d'une installation réelle v2.0.0. Les states de capteurs vont maintenant dans sensor/, les états d'événements dans events/ (avant control/ pour les deux); les objets d'état sont créés à la volée au premier write. Snapshots et scènes ne s'attachent qu'aux lampes désormais; thermomètres/chauffages/bouilloires n'ont plus de snapshot-states. Le dump d'experimental devices au démarrage a été supprimé.",
39
+ "it": "Hotfix da un'installazione v2.0.0 reale. Gli state dei sensori ora vanno in sensor/, gli eventi in events/ (prima control/ per entrambi); gli oggetti vengono creati lazy alla prima scrittura. Snapshot e scene si collegano solo alle luci ora; termometri/riscaldatori/bollitori non hanno più snapshot-states. Il log di experimental device all'avvio è stato rimosso.",
40
+ "es": "Hotfixes de una instalación real de v2.0.0. Los states de sensor ahora van a sensor/, los de eventos a events/ (antes control/ para ambos); los objetos se crean lazy en la primera escritura. Snapshots y escenas solo se asocian a luces ahora; termómetros/calefactores/hervidores ya no reciben snapshot-states. El volcado de experimental devices al arranque se ha eliminado.",
41
+ "pl": "Hotfiksy z prawdziwej instalacji v2.0.0. State-ID sensorów trafiają teraz do sensor/, eventy do events/ (wcześniej control/ dla obu); obiekty stanu tworzone leniwie przy pierwszym zapisie. Snapshoty i sceny są dołączane tylko do oświetlenia; termometry/grzejniki/czajniki nie mają już snapshot-states. Startowy log experimental devices usunięty.",
42
+ "uk": "Хотфікси з реальної інсталяції v2.0.0. State сенсорів тепер у sensor/, події у events/ (раніше control/ для обох); state-об'єкти створюються лениво при першому записі. Snapshots і сцени тепер прив'язуються лише до ламп; термометри/обігрівачі/чайники більше не отримують snapshot-states. Стартовий experimental-device-дамп прибрано.",
43
+ "zh-cn": "来自真实 v2.0.0 安装的热修复。传感器状态 ID 现在路由到 sensor/,事件状态到 events/(之前都在 control/);状态对象在首次写入时延迟创建。Snapshots 和场景现在只附加到 lights;温度计/加热器/水壶不再获得 snapshot-states。启动时的 experimental device 日志已移除。"
31
44
  },
32
45
  "2.0.0": {
33
- "en": "Major release — Govee appliances and sensors are now handled by this adapter alongside lights. The standalone iobroker.govee-appliances adapter is deprecated and rolls into here. A new checkbox 'Enable experimental device support' in the config makes it easier to try unconfirmed models — the Wiki page Devices lists every supported SKU and its status. New info.openapiMqttConnected state for the second MQTT channel that delivers appliance events.",
34
- "de": "Major Release — Govee Appliances und Sensoren laufen jetzt zusammen mit den Lights über diesen Adapter. Der separate iobroker.govee-appliances Adapter ist deprecated und wandert hier rein. Neuer Schalter 'Experimentelle Geräte-Unterstützung aktivieren' in der Config zum einfacheren Ausprobieren ungeprüfter Modelle — Wiki-Seite Geräte listet jedes unterstützte SKU mit Status. Neuer State info.openapiMqttConnected für den zweiten MQTT-Kanal mit Appliance-Events.",
35
- "ru": "Мажорный релиз приборы и датчики Govee теперь обрабатываются этим адаптером вместе с лампами. Отдельный адаптер iobroker.govee-appliances устарел и переезжает сюда. Новый переключатель 'Включить экспериментальную поддержку устройств' в настройках упрощает тестирование неподтверждённых моделей страница Wiki Devices перечисляет каждый поддерживаемый SKU и его статус.",
36
- "pt": "Lançamento principaleletrodomésticos e sensores Govee agora são gerenciados por este adaptador junto com as luzes. O adaptador iobroker.govee-appliances autônomo está obsoleto e foi integrado aqui. Nova caixa de seleção 'Ativar suporte experimental a dispositivos' na configuração facilita testar modelos não confirmados — a página Wiki Devices lista todos os SKUs suportados e seu status.",
37
- "nl": "Major release — Govee apparaten en sensoren worden nu door deze adapter samen met de lichten beheerd. De aparte iobroker.govee-appliances adapter is verouderd en is hierin opgenomen. Nieuw selectievakje 'Experimentele apparaatondersteuning inschakelen' in de configuratie maakt het eenvoudiger om onbevestigde modellen te proberen de Wiki-pagina Devices vermeldt elke ondersteunde SKU en de status.",
38
- "fr": "Version majeure — les appareils et capteurs Govee sont désormais gérés par cet adaptateur aux côtés des lumières. L'adaptateur iobroker.govee-appliances autonome est obsolète et fusionné ici. Une nouvelle case 'Activer la prise en charge expérimentale des appareils' dans la configuration facilite l'essai des modèles non confirmés la page Wiki Devices liste chaque SKU pris en charge et son statut.",
39
- "it": "Rilascio principale — gli elettrodomestici e i sensori Govee sono ora gestiti da questo adattatore insieme alle luci. L'adattatore iobroker.govee-appliances autonomo è obsoleto e si fonde qui. Nuova casella 'Attiva il supporto sperimentale dei dispositivi' nella configurazione facilita la prova di modelli non confermati la pagina Wiki Devices elenca ogni SKU supportato e il suo stato.",
40
- "es": "Versión principal — los electrodomésticos y sensores Govee ahora son manejados por este adaptador junto con las luces. El adaptador iobroker.govee-appliances independiente está obsoleto y se fusiona aquí. Nueva casilla 'Activar soporte experimental de dispositivos' en la configuración facilita probar modelos no confirmados la página Wiki Devices lista cada SKU compatible y su estado.",
41
- "pl": "Główne wydanie — urządzenia i czujniki Govee są teraz obsługiwane przez ten adapter razem z lampami. Samodzielny adapter iobroker.govee-appliances jest przestarzały i jest scalany tutaj. Nowe pole wyboru 'Włącz eksperymentalne wsparcie urządzeń' w konfiguracji ułatwia testowanie niepotwierdzonych modeli strona Wiki Devices wymienia każdy obsługiwany SKU i jego status.",
42
- "uk": "Великий випуск пристрої та датчики Govee тепер обробляються цим адаптером разом із лампами. Окремий адаптер iobroker.govee-appliances застарілий і об'єднаний сюди. Новий перемикач 'Увімкнути експериментальну підтримку пристроїв' у конфігурації полегшує тестування непідтверджених моделей сторінка Wiki Devices містить кожен підтримуваний SKU та його статус.",
43
- "zh-cn": "主要版本 — Govee 电器和传感器现在由此适配器与灯具一起处理。独立的 iobroker.govee-appliances 适配器已弃用并合并到此处。配置中新增的'启用实验性设备支持'复选框使得测试未确认的型号更加容易 Wiki Devices 页面列出每个受支持的 SKU 及其状态。"
46
+ "en": "Major release — Govee appliances and sensors (e.g. H5179 thermometers, heaters, kettles, ice makers) are now handled here alongside lights. The standalone iobroker.govee-appliances adapter is deprecated. New 'Enable experimental device support' checkbox; the Wiki Devices page lists every supported SKU. New info.openapiMqttConnected state for the OpenAPI-MQTT push channel.",
47
+ "de": "Major-Release — Govee-Appliances und -Sensoren (z.B. H5179-Thermometer, Heizgeräte, Wasserkocher, Eiswürfelbereiter) werden jetzt zusammen mit Leuchten hier verwaltet. Der eigenständige iobroker.govee-appliances-Adapter ist deprecated. Neue Checkbox 'Enable experimental device support'; die Wiki-Seite Devices listet alle unterstützten SKUs. Neuer State info.openapiMqttConnected für den OpenAPI-MQTT-Push-Kanal.",
48
+ "ru": "Major-релізпристрої Govee Appliances і сенсори (термометри H5179, обігрівачі, чайники, льодогенератори) тепер обробляються тут разом із лампами. Окремий адаптер iobroker.govee-appliances застарів. Новий чекбокс 'Enable experimental device support'; сторінка Devices у Wiki перелічує всі підтримувані SKU. Новий стейт info.openapiMqttConnected для OpenAPI-MQTT push-каналу.",
49
+ "pt": "Major releaseappliances e sensores Govee (por exemplo termômetros H5179, aquecedores, chaleiras, máquinas de gelo) são agora tratados aqui junto com as luzes. O adaptador iobroker.govee-appliances autônomo está depreciado. Nova caixa 'Enable experimental device support'; a página Devices do Wiki lista todos os SKUs suportados. Novo state info.openapiMqttConnected para o canal OpenAPI-MQTT push.",
50
+ "nl": "Major release — Govee-appliances en -sensoren (bijv. H5179-thermometers, kachels, waterkokers, ijsmakers) worden nu samen met lampen hier afgehandeld. De losse iobroker.govee-appliances-adapter is deprecated. Nieuwe checkbox 'Enable experimental device support'; de Wiki Devices-pagina toont alle ondersteunde SKUs. Nieuwe state info.openapiMqttConnected voor het OpenAPI-MQTT push-kanaal.",
51
+ "fr": "Major release — les appareils et capteurs Govee (thermomètres H5179, chauffages, bouilloires, machines à glace) sont maintenant gérés ici avec les lampes. L'adaptateur autonome iobroker.govee-appliances est déprécié. Nouvelle case 'Enable experimental device support'; la page Devices du Wiki liste tous les SKUs pris en charge. Nouveau state info.openapiMqttConnected pour le canal OpenAPI-MQTT push.",
52
+ "it": "Major release — gli apparecchi e i sensori Govee (termometri H5179, riscaldatori, bollitori, macchine del ghiaccio) sono ora gestiti qui insieme alle luci. L'adattatore iobroker.govee-appliances autonomo è deprecato. Nuova checkbox 'Enable experimental device support'; la pagina Devices della Wiki elenca tutti gli SKU supportati. Nuovo state info.openapiMqttConnected per il canale OpenAPI-MQTT push.",
53
+ "es": "Major release — los electrodomésticos y sensores Govee (termómetros H5179, calentadores, hervidores, máquinas de hielo) ahora se gestionan aquí junto a las luces. El adaptador independiente iobroker.govee-appliances está obsoleto. Nueva casilla 'Enable experimental device support'; la página Devices del Wiki lista todos los SKUs soportados. Nuevo state info.openapiMqttConnected para el canal OpenAPI-MQTT push.",
54
+ "pl": "Major release — urządzenia i czujniki Govee (np. termometry H5179, grzejniki, czajniki, kostkarki) są teraz obsługiwane tutaj wraz z oświetleniem. Samodzielny adapter iobroker.govee-appliances jest deprecated. Nowy checkbox 'Enable experimental device support'; strona Devices w Wiki zawiera listę wszystkich obsługiwanych SKU. Nowy state info.openapiMqttConnected dla kanału OpenAPI-MQTT push.",
55
+ "uk": "Major-релізтехніка Govee (термометри H5179, обігрівачі, чайники, льодогенератори) і сенсори тепер обробляються тут разом із лампами. Окремий iobroker.govee-appliances адаптер застарів. Новий чекбокс 'Enable experimental device support'; сторінка Devices у Wiki містить усі підтримувані SKU. Новий state info.openapiMqttConnected для OpenAPI-MQTT push-каналу.",
56
+ "zh-cn": "主版本发布 — Govee 电器和传感器(H5179 温度计、加热器、水壶、制冰机等)现在与灯具一起在此处理。独立的 iobroker.govee-appliances 适配器已弃用。新增 'Enable experimental device support' 复选框;Wiki Devices 页面列出所有支持的 SKU。新增 info.openapiMqttConnected state 用于 OpenAPI-MQTT push 通道。"
44
57
  },
45
58
  "1.11.0": {
46
- "en": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
47
- "de": "Szenen- / DIY- / Snapshot- / Music-Mode-Dropdowns akzeptieren jetzt drei Schreibweisen aus Blockly und JavaScript: den Index als String (\"1\"), den Index als Zahl (1), oder den Klartext-Namen (\"Aurora\", Groß/Klein egal, Whitespace egal). Der State-Typ wurde von string auf mixed geändert, damit der js-controller bei numerischem Schreiben nicht mehr \"expects type string but received number\" warnt. Doppelte Cloud-Namen werden automatisch eindeutig gemacht über Suffixe \" (2)\", \" (3)\" — der erste Eintrag behält den Originalnamen, jedes Label landet in genau einem Index. Nach der Aktivierung ackt der Adapter den kanonischen Key zurück, damit das Dropdown unabhängig vom Schreibweg synchron bleibt.",
48
- "ru": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
49
- "pt": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
50
- "nl": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
51
- "fr": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
52
- "it": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
53
- "es": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
54
- "pl": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
55
- "uk": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value.",
56
- "zh-cn": "Scene / DIY scene / snapshot / music-mode dropdowns now accept three input forms from Blockly and JS: the index as a string (\"1\"), the index as a number (1), or the entry name (\"Aurora\", case-insensitive, trimmed). The state type changed from string to mixed so the js-controller no longer warns \"expects type string but received number\" when a script writes a numeric index. Duplicate entry names from the cloud are auto-disambiguated with \" (2)\", \" (3)\" suffixes so each label maps to exactly one index — first occurrence keeps the original name. After activation the adapter acks back the canonical key, so the dropdown stays in sync regardless of how the user wrote the value."
59
+ "en": "Scene/DIY/snapshot/music-mode dropdowns now accept index-as-number, index-as-string and the entry name (case-insensitive). State type is mixed no more 'expects type string but received number' warning. Duplicate scene names from the cloud are auto-disambiguated with ' (2)', ' (3)' suffixes.",
60
+ "de": "Scene/DIY/Snapshot/Musik-Modus-Dropdowns akzeptieren jetzt Index als Zahl, Index als String und den Klartext-Namen (case-insensitive). State-Typ ist 'mixed' kein 'expects type string but received number'-Warning mehr. Doppelte Szenennamen aus der Cloud werden automatisch mit ' (2)', ' (3)' suffixiert.",
61
+ "ru": "Випадайки для сцен/DIY/snapshot/музики тепер приймають індекс як число, як string і назву елемента (case-insensitive). Тип state mixed попередження 'expects type string but received number' зникло. Дублікати назв сцен з cloud отримують суфікси ' (2)', ' (3)'.",
62
+ "pt": "Os dropdowns de scene/DIY/snapshot/music-mode agora aceitam índice como número, como string e o nome da entrada (case-insensitive). O tipo do state é mixed o aviso 'expects type string but received number' desapareceu. Nomes duplicados de cena vindos da nuvem são automaticamente desambiguados com sufixos ' (2)', ' (3)'.",
63
+ "nl": "Scene/DIY/snapshot/music-mode dropdowns accepteren nu de index als number, als string en de entry-name (case-insensitive). State-type is mixed de waarschuwing 'expects type string but received number' is weg. Dubbele scènenamen uit de cloud krijgen automatisch ' (2)', ' (3)' achtervoegsels.",
64
+ "fr": "Les dropdowns scene/DIY/snapshot/music-mode acceptent désormais l'index en number, en string ou le nom (insensible à la casse). Le type de state est mixed l'avertissement 'expects type string but received number' a disparu. Les noms de scène dupliqués depuis le cloud sont automatiquement suffixés ' (2)', ' (3)'.",
65
+ "it": "I dropdown scene/DIY/snapshot/music-mode ora accettano l'indice come number, come string e il nome (case-insensitive). Il tipo di state è mixed l'avviso 'expects type string but received number' è scomparso. I nomi di scena duplicati dal cloud vengono auto-disambiguati con suffissi ' (2)', ' (3)'.",
66
+ "es": "Los desplegables scene/DIY/snapshot/music-mode aceptan ahora el índice como number, como string o el nombre (case-insensitive). El tipo de state es mixed desaparece la advertencia 'expects type string but received number'. Los nombres de escena duplicados de la nube se desambiguan automáticamente con sufijos ' (2)', ' (3)'.",
67
+ "pl": "Listy rozwijane scene/DIY/snapshot/music-mode akceptują teraz indeks jako number, jako string oraz nazwę (case-insensitive). Typ state to mixed ostrzeżenie 'expects type string but received number' znika. Zduplikowane nazwy scen z chmury automatycznie różnicowane sufiksami ' (2)', ' (3)'.",
68
+ "uk": "Випадайки для scene/DIY/snapshot/music-mode тепер приймають індекс як number, як string і назву елемента (case-insensitive). Тип state mixed попередження 'expects type string but received number' зникло. Дубльовані назви сцен з cloud автоматично отримують суфікси ' (2)', ' (3)'.",
69
+ "zh-cn": "场景/DIY/snapshot/音乐模式下拉菜单现在接受索引为数字、索引为字符串或条目名称(不区分大小写)。state 类型为 mixed —— 'expects type string but received number' 警告消失。云端重复场景名称自动添加 ' (2)'、' (3)' 后缀。"
57
70
  },
58
71
  "1.10.1": {
59
- "en": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
60
- "de": "Fix der Knopf info.refresh_cloud_data hat bei jedem Klick alle Scene-/Music-/DIY-/SKU-Features-Bibliotheken pro Gerät neu abgefragt. Bibliotheken ändern sich pro SKU nie, mehrere Endpunkte liefern bei vielen Accounts 403 zurück, ergo baut sich nur ein mehrminütiger Rate-Limiter-Backlog auf (im Log sichtbar als minütliche POSTs an /device/scenes und /device/diy-scenes nach jedem Klick). Der Knopf lädt jetzt nur noch den Scenes-/Snapshot-Endpunkt nach, wo neue Govee-App-Snapshots tatsächlich auftauchen. Aufruf-Anzahl pro Klick sinkt von ~7 auf 2 pro Licht-Gerät.",
61
- "ru": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
62
- "pt": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
63
- "nl": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
64
- "fr": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
65
- "it": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
66
- "es": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
67
- "pl": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
68
- "uk": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device.",
69
- "zh-cn": "Fix the info.refresh_cloud_data button was re-fetching every device's scene / music / DIY / SKU-features libraries on each click. Libraries never change for a given SKU, and several endpoints 403 for many accounts, so this only produced a multi-minute rate-limiter backlog (minute-spaced POSTs to /device/scenes and /device/diy-scenes after a click). The button now only re-runs the scene/snapshot endpoint, which is what new Govee-app snapshots actually show up on. Call count per click drops from ~7 to 2 per light device."
72
+ "en": "Refresh button no longer re-fetches static SKU libraries (scene/music/DIY/features) call count drops from ~7 to 2 per device per click. Those endpoints returned 403 for many accounts and just produced minute-long rate-limiter backlogs.",
73
+ "de": "Refresh-Button holt nicht mehr die statischen SKU-Libraries (Scene/Music/DIY/Features) — Call-Anzahl pro Gerät pro Klick fällt von ~7 auf 2. Diese Endpunkte lieferten 403 für viele Accounts und produzierten nur minutenlange Rate-Limiter-Backlogs.",
74
+ "ru": "Кнопка Refresh більше не перезавантажує статичні SKU-бібліотеки (scene/music/DIY/features) кількість викликів знижується з ~7 до 2 на пристрій за клік. Ці endpoint'и повертали 403 для багатьох акаунтів і лише накопичували відставання rate-limiter на хвилини.",
75
+ "pt": "O botão Refresh não busca mais as bibliotecas estáticas por SKU (scene/music/DIY/features) o número de chamadas cai de ~7 para 2 por dispositivo por clique. Esses endpoints retornavam 403 para muitas contas e produziam backlog de minutos no rate-limiter.",
76
+ "nl": "Refresh-knop haalt de statische SKU-bibliotheken (scene/music/DIY/features) niet meer opnieuw op aantal calls daalt van ~7 naar 2 per device per klik. Die endpoints leverden 403 voor veel accounts en zorgden alleen voor minutenlange rate-limiter backlog.",
77
+ "fr": "Le bouton Refresh ne récupère plus les bibliothèques statiques par SKU (scene/music/DIY/features) le nombre d'appels passe de ~7 à 2 par appareil par clic. Ces endpoints retournaient 403 pour beaucoup de comptes et ne produisaient qu'un backlog de plusieurs minutes côté rate-limiter.",
78
+ "it": "Il pulsante Refresh non ricarica più le librerie statiche per SKU (scene/music/DIY/features) il numero di chiamate scende da ~7 a 2 per dispositivo per click. Quegli endpoint restituivano 403 per molti account e producevano solo arretrati di minuti nel rate-limiter.",
79
+ "es": "El botón Refresh ya no vuelve a buscar las librerías estáticas por SKU (scene/music/DIY/features) el número de llamadas baja de ~7 a 2 por dispositivo por clic. Esos endpoints devolvían 403 para muchas cuentas y solo producían backlogs de minutos en el rate-limiter.",
80
+ "pl": "Przycisk Refresh nie pobiera już statycznych bibliotek SKU (scene/music/DIY/features) liczba wywołań spada z ~7 do 2 na urządzenie na kliknięcie. Te endpointy zwracały 403 dla wielu kont i powodowały tylko minutowy backlog rate-limitera.",
81
+ "uk": "Кнопка Refresh більше не перезавантажує статичні SKU-бібліотеки (scene/music/DIY/features) кількість викликів знижується з ~7 до 2 на пристрій за клік. Ці endpoint'и повертали 403 для багатьох акаунтів і лише накопичували rate-limiter-backlog на хвилини.",
82
+ "zh-cn": "刷新按钮不再重新获取静态 SKU 库(scene/music/DIY/features)—— 每次点击每设备的调用数从约 7 个降至 2 个。这些端点对许多账户返回 403,只会产生数分钟的 rate-limiter 积压。"
70
83
  },
71
84
  "1.10.0": {
72
- "en": "Two fixes around mode tracking. First, scenes with a scenceParam (the multi-packet A3 BLE payload that drives per-segment animation) are now skipped for devices without segments (e.g. H70B3 Curtain Lights, bulbs) and activated via the Govee Cloud instead — those devices silently drop the A3 packets, so the old ptReal path left the scene unplayed. Second, powering a device off now resets every mode dropdown (scene, DIY scene, Cloud/local snapshot, music) to \"---\", whether the off was triggered from ioBroker or from the Govee app a device that is off cannot be \"playing Aurora-A\".",
73
- "de": "Zwei Fixes rund um Mode-Tracking. Erstens: Szenen mit scenceParam (das Multi-Packet-A3-BLE-Format für Segment-Animationen) werden auf Geräten ohne Segmente (z.B. H70B3 Curtain Lights, Birnen) nicht mehr per ptReal versucht sondern direkt über die Govee Cloud aktiviert diese Geräte verwerfen die A3-Pakete stumm, der alte ptReal-Pfad ließ die Szene damit ungespielt. Zweitens: Beim Ausschalten eines Geräts werden jetzt alle Mode-Dropdowns (Szene, DIY-Szene, Cloud-/lokaler Snapshot, Musik) auf \"---\" zurückgesetzt — egal ob die Power-off-Aktion von ioBroker oder aus der Govee App kam. Ein ausgeschaltetes Gerät kann nicht mehr \"Aurora-A spielen\".",
74
- "ru": "Два исправления связанных с режимами. Сцены со scenceParam теперь используют Cloud-активацию на устройствах без сегментов (H70B3 и др.) ptReal-пакеты эти устройства молча игнорировали. Выключение устройства теперь сбрасывает все mode-dropdowns (сцена, snapshot, music) на \"---\", независимо от источника выключения.",
75
- "pt": "Duas correções em mode-tracking. Cenas com scenceParam agora usam ativação Cloud em dispositivos sem segmentos (H70B3 etc.) os pacotes ptReal eram silenciosamente descartados. Desligar o dispositivo agora reseta todos os mode-dropdowns para \"---\", independente da origem.",
76
- "nl": "Twee fixes voor mode-tracking. Scenes met scenceParam gebruiken nu cloud-activatie op apparaten zonder segmenten (H70B3 etc.) die verwerpen de ptReal-pakketten stilletjes. Apparaat uitschakelen reset nu alle mode-dropdowns naar \"---\", ongeacht de bron.",
77
- "fr": "Deux correctifs autour du tracking des modes. Les scènes avec scenceParam utilisent maintenant l’activation Cloud sur les appareils sans segments (H70B3 etc.) ces appareils rejetaient silencieusement les paquets ptReal. Éteindre un appareil remet maintenant tous les mode-dropdowns à « --- », quelle que soit la source.",
78
- "it": "Due fix sul mode-tracking. Scene con scenceParam ora usano attivazione Cloud sui dispositivi senza segmenti (H70B3 etc.) quei dispositivi scartavano silenziosamente i pacchetti ptReal. Spegnere un dispositivo ora resetta tutti i mode-dropdown a \"---\", indipendentemente dall’origine.",
79
- "es": "Dos correcciones en el mode-tracking. Las escenas con scenceParam ahora usan activación Cloud en dispositivos sin segmentos (H70B3 etc.) esos dispositivos descartaban silenciosamente los paquetes ptReal. Apagar un dispositivo ahora resetea todos los mode-dropdowns a \"---\", independientemente del origen.",
80
- "pl": "Dwie poprawki w mode-tracking. Sceny z scenceParam używają teraz aktywacji Cloud na urządzeniach bez segmentów (H70B3 itd.) te urządzenia po cichu odrzucały pakiety ptReal. Wyłączenie urządzenia resetuje teraz wszystkie mode-dropdowns do \"---\", niezależnie od źródła.",
81
- "uk": "Два виправлення в mode-tracking. Сцени з scenceParam тепер активуються через Cloud на пристроях без сегментів (H70B3 тощо) ці пристрої мовчки відкидали ptReal-пакети. Вимкнення пристрою тепер скидає всі mode-dropdowns на \"---\", незалежно від джерела.",
82
- "zh-cn": "两个 mode-tracking 修复。带 scenceParam 的场景现在在无段设备(H70B3 等)上通过 Cloud 激活 这些设备会默默丢弃 ptReal 包。关闭设备现在会将所有 mode-dropdown 重置为 \"---\",无论来源。"
83
- },
84
- "1.9.1": {
85
- "en": "Hotfix — cloud-side scene/snapshot updates are now merged per list instead of all-or-nothing. Govee’s /device/scenes occasionally returns e.g. 149 scenes + 0 snapshots on the same device where a snapshot clearly exists; the old combined guard wiped the snapshots list in that case, breaking the cloud-snapshot dropdown with “invalid snapshot index” errors. Each of scenes, DIY scenes and snapshots is now guarded independently so a lucky list never clobbers an unlucky one.",
86
- "de": "Hotfix — Cloud-Aktualisierungen für Szenen/Snapshots werden jetzt pro Liste gemerged statt alles-oder-nichts. Govees /device/scenes liefert gelegentlich z.B. 149 Szenen + 0 Snapshots obwohl ein Snapshot existiert; der alte kombinierte Guard hat die Snapshot-Liste in dem Fall geleert und damit das Cloud-Snapshot-Dropdown mit „invalid snapshot index“-Fehlern gebrochen. Szenen, DIY-Szenen und Snapshots werden jetzt unabhängig gegen leeres Cloud-Ergebnis geschützt.",
87
- "ru": "Хотфикс — обновление сцен/снапшотов из облака теперь мержится по отдельным спискам, а не всё сразу. Govee иногда возвращает сцены + 0 снапшотов там где снапшот реально существует; старая логика стирала список снапшотов, ломая dropdown с ошибкой \"invalid snapshot index\". Списки теперь защищены независимо.",
88
- "pt": "Hotfix — atualizações cloud de cenas/snapshots agora são mescladas por lista. Govee às vezes retorna cenas + 0 snapshots quando o snapshot existe; o guard antigo apagava a lista de snapshots, causando erros \"invalid snapshot index\" no dropdown. Agora cada lista é protegida separadamente.",
89
- "nl": "Hotfix — cloud-updates van scenes/snapshots worden nu per lijst samengevoegd. Govee retourneert soms scenes + 0 snapshots terwijl de snapshot bestaat; de oude guard wiste de snapshot-lijst in dat geval, waardoor het dropdown brak met \"invalid snapshot index\". Elke lijst wordt nu afzonderlijk beschermd.",
90
- "fr": "Hotfix — les mises à jour cloud des scènes/snapshots sont maintenant fusionnées par liste. Govee renvoie parfois des scènes + 0 snapshot alors que le snapshot existe ; l’ancien guard effaçait la liste des snapshots, cassant le dropdown avec l’erreur « invalid snapshot index ». Chaque liste est maintenant protégée séparément.",
91
- "it": "Hotfix — gli aggiornamenti cloud di scene/snapshot ora vengono uniti per lista. Govee talvolta restituisce scene + 0 snapshot quando lo snapshot esiste; il vecchio guard cancellava la lista degli snapshot, rompendo il dropdown con errori \"invalid snapshot index\". Ora ogni lista è protetta separatamente.",
92
- "es": "Hotfix — las actualizaciones cloud de escenas/snapshots ahora se fusionan por lista. Govee a veces devuelve escenas + 0 snapshots cuando el snapshot existe; el guard antiguo borraba la lista de snapshots, rompiendo el dropdown con errores \"invalid snapshot index\". Cada lista ahora está protegida por separado.",
93
- "pl": "Hotfix — aktualizacje cloud scen/snapshotów są teraz mergeowane osobno dla każdej listy. Govee czasem zwraca sceny + 0 snapshotów gdy snapshot istnieje; stary guard czyścił listę snapshotów, psując dropdown z błędem \"invalid snapshot index\". Każda lista jest teraz chroniona osobno.",
94
- "uk": "Хотфікс — оновлення сцен/снепшотів з клауду тепер мержаться посписочно. Govee іноді повертає сцени + 0 снепшотів коли снепшот існує; старий guard стирав список снепшотів, ламаючи dropdown з помилкою \"invalid snapshot index\". Кожен список тепер захищено окремо.",
95
- "zh-cn": "热修复 — 云端场景/快照更新现在按列表分别合并。Govee 有时返回场景 + 0 快照(快照实际存在),旧的 guard 会清空快照列表,导致 dropdown 出现 \"invalid snapshot index\" 错误。每个列表现在独立保护。"
85
+ "en": "Multi-packet A3 BLE scenes (scenceParam) are now activated via Cloud on devices without segments; bulbs and Curtain Lights silently dropped those packets before, so complex scenes never played. Powering a device off resets every mode dropdown to '---' both ioBroker and Govee-app initiated off events.",
86
+ "de": "Multi-Packet-A3-BLE-Szenen (scenceParam) werden jetzt auf Geräten ohne Segmente über die Cloud aktiviert; Bulbs und Curtain Lights haben diese Pakete bisher still verworfen, sodass komplexe Szenen nie liefen. Beim Ausschalten eines Geräts werden alle Modus-Dropdowns auf '---' zurückgesetzt — sowohl bei ioBroker- als auch bei Govee-App-Off-Events.",
87
+ "ru": "Multi-packet A3 BLE-сцени (scenceParam) тепер активуються через Cloud на пристроях без сегментів; лампи і Curtain Lights раніше тихо ігнорували ці пакети, через що складні сцени не запускалися. При вимкненні пристрою всі моди-випадайки скидаються на '---' — як для ioBroker, так і для Govee-app off-event.",
88
+ "pt": "Cenas multi-packet A3 BLE (scenceParam) agora são ativadas via Cloud em dispositivos sem segmentos; lâmpadas e Curtain Lights descartavam silenciosamente esses pacotes, então cenas complexas nunca eram reproduzidas. Desligar um dispositivo reseta todos os dropdowns de modo para '---' tanto eventos ioBroker quanto Govee-app.",
89
+ "nl": "Multi-packet A3 BLE-scènes (scenceParam) worden nu via Cloud geactiveerd op apparaten zonder segmenten; bulbs en Curtain Lights gooiden die pakketten stilzwijgend weg, dus complexe scènes speelden nooit. Een apparaat uitzetten reset alle mode-dropdowns naar '---' zowel ioBroker- als Govee-app off-events.",
90
+ "fr": "Les scènes A3 BLE multi-paquets (scenceParam) sont maintenant activées via le Cloud sur les appareils sans segments; les ampoules et Curtain Lights ignoraient silencieusement ces paquets, donc les scènes complexes ne jouaient jamais. Éteindre un appareil réinitialise tous les dropdowns de mode à '---' événements ioBroker et Govee-app.",
91
+ "it": "Le scene A3 BLE multi-pacchetto (scenceParam) ora vengono attivate via Cloud sui dispositivi senza segmenti; lampadine e Curtain Lights scartavano silenziosamente quei pacchetti, quindi le scene complesse non venivano mai riprodotte. Spegnere un dispositivo resetta tutti i dropdown di modalità a '---' eventi ioBroker e Govee-app.",
92
+ "es": "Las escenas A3 BLE multi-paquete (scenceParam) ahora se activan vía Cloud en dispositivos sin segmentos; las bombillas y Curtain Lights descartaban silenciosamente esos paquetes, por lo que las escenas complejas nunca se reproducían. Apagar un dispositivo resetea todos los dropdowns de modo a '---' tanto eventos de ioBroker como de la Govee-app.",
93
+ "pl": "Sceny A3 BLE z wielu pakietów (scenceParam) teraz aktywowane przez Cloud na urządzeniach bez segmentów; żarówki i Curtain Lights po cichu odrzucały te pakiety, więc złożone sceny nigdy się nie odtwarzały. Wyłączenie urządzenia resetuje wszystkie listy modów do '---' zdarzenia z ioBrokera i z aplikacji Govee.",
94
+ "uk": "Multi-packet A3 BLE сцени (scenceParam) тепер активуються через Cloud на пристроях без сегментів; bulbs і Curtain Lights раніше мовчки відкидали ці пакети, тож складні сцени не запускалися. Вимкнення пристрою скидає всі моди-випадайки на '---' — як для ioBroker, так і для Govee-app off-події.",
95
+ "zh-cn": "多包 A3 BLE 场景(scenceParam)现在在没有 segments 的设备上通过 Cloud 激活;灯泡和 Curtain Lights 之前会静默丢弃这些包,导致复杂场景从未播放。关闭设备时所有模式下拉菜单重置为 '---' —— ioBroker 和 Govee-app 触发的关机事件都生效。"
96
96
  }
97
97
  },
98
98
  "titleLang": {
@@ -157,12 +157,12 @@
157
157
  },
158
158
  "dependencies": [
159
159
  {
160
- "js-controller": ">=7.0.23"
160
+ "js-controller": ">=6.0.11"
161
161
  }
162
162
  ],
163
163
  "globalDependencies": [
164
164
  {
165
- "admin": ">=7.6.17"
165
+ "admin": ">=7.6.20"
166
166
  }
167
167
  ]
168
168
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "iobroker.govee-smart",
3
- "version": "2.0.2",
3
+ "version": "2.0.3",
4
4
  "description": "Control Govee WiFi devices via LAN, MQTT and Cloud.",
5
5
  "author": {
6
6
  "name": "krobi",