iobroker.lovelace 4.1.2 → 4.1.5

package/README.md

@@ -11,16 +11,16 @@
 
 ## lovelace adapter for ioBroker
 
-With this adapter you can build visualization for ioBroker with Home Assistant Lovelace UI.
+With this adapter, you can build visualization for ioBroker with Home Assistant Lovelace UI.
 
 [Deutsche Dokumentation](docs/de/README.md)
 
 ## Instance objects
-In the folder instances there are some objects that can be used to control the UI. For every browser a new subfolder will
-be created with a random ID. This ID is stored in the client browser's web storage. If you delete the web storage a new
+In the folder instances, there are some objects that can be used to control the UI. For every browser, a new subfolder will
+be created with a random ID. This ID is stored in the client browser's web storage. If you delete the web storage, a new
 instance will be created. If you use Fully Kiosk Browser make sure the function `Delete webstorage on reload` is **disabled**.
 
-This functionality uses browser_mod, which is installed and updated by the adapter. Do not add your own version of browser_mod as custom card.
+This functionality uses browser_mod, which is installed and updated by the adapter. Do not add your own version of browser_mod as a custom card.
 
 ## Configuration
 There are two ways how the entities could be configured:
@@ -35,7 +35,7 @@ In auto mode the similar process will be applied like for `google home` or `mate
 You can define friendly names and this will be used in entities.
 
 ### Manual
-The objects can be defined manually in object tree like sql or histroy. The type of entity must be provided and optionally the name of object.
+The objects can be defined manually in an object tree like sql or histroy. The type of entity must be provided and optionally the name of object.
 With this method only simple entities, like input_number, input_text or input_boolean could be created. It may not have more than one state or attribute.
 
 ## Panels
@@ -96,8 +96,8 @@ common: {
 ```
 
 ### Select input
-This can be done manually if input_select entity type in custom dialog is selected.
-The list of options to select from should be provide in standard commom.states object:
+This can be done manually if `input_select` entity type in custom dialog is selected.
+The list of options to select from should be provided in a standard `common.states` object:
 
 ```
 "common": {
@@ -115,10 +115,10 @@ The list of options to select from should be provide in standard commom.states o
       }
     }
 ```
-in other words in should also be input select in IoB.
+in other words, there should also be select input in IoB.
 
 ### Timer
-Timer could be simulated by following script:
+Timer could be simulated by the following script:
 
 ```
 createState(
@@ -202,11 +202,11 @@ createState(
 ```
 
 ### Weather
-Tested with yr and daswetter. One or more of following objects must have `Function=Weather` and `Room=Any` set to be available in configuration:
-- daswetter.0.NextDays.Location_1
-- yr.0.forecast
+Tested with `yr` and `daswetter`. One or more of the following objects must have `Function=Weather` and `Room=Any` set to be available in configuration:
+- `daswetter.0.NextDays.Location_1`
+- `yr.0.forecast`
 
-Tested with AccuWeather driver v1.1.0 https://github.com/iobroker-community-adapters/ioBroker.accuweather.
+Tested with `AccuWeather` driver v1.1.0 https://github.com/iobroker-community-adapters/ioBroker.accuweather.
 Custom Lovelace card created in support of accuweather forecast - https://github.com/algar42/IoB.lovelace.accuweather-card
 
 ### Shopping list
@@ -235,7 +235,7 @@ createState('location', '39.5681295;2.6432632', false, {
 });
 ```
 
-or this two objects:
+or these two objects:
 
 ```
 createState('location.longitude', 2.6432632, false, {
@@ -257,7 +257,7 @@ createState('location.latitude', 39.5681295, false, {
 ```
 
 ### Picture entity
-You can use static picture for it or use any state that delivers URL as state.
+You can use static picture for it or use any state that delivers URL as a state.
 E.g.:
 
 ```
@@ -275,34 +275,34 @@ E.g.:
 }
 ```
 
-or just set manually the entity type to `camera` and write URL into it.
+or just manually set the entity type to `camera` and write URL into it.
 
 ### Markdown
 You can use bindings in markdown like in [iobroker.vis](https://github.com/ioBroker/ioBroker.vis#bindings-of-objects).
 
-E.g. Text `Admin adapter is {a:system.adapter.admin.0.alive;a === true || a === 'true' ? ' ' : 'not '} *alive*.` will produce text `Admin adapter is alive` in markdown panel.
+E.g., Text `Admin adapter is {a:system.adapter.admin.0.alive;a === true || a === 'true' ? ' ' : 'not '} *alive*.` will produce text `Admin adapter is alive` in a markdown panel.
 
 ## Custom cards
 ### Upload of custom cards
-To upload the custom card write following:
+To upload the custom card, write the following:
 
 ```iobroker file write PATH_TO_FILE\bignumber-card.js /lovelace.0/cards/```
 
 After restart of lovelace adapter it will include all files from the `cards` directory automatically.
 
-Following custom cards could be tested successfully:
-- bignumber-card: https://github.com/custom-cards/bignumber-card/blob/master/bignumber-card.js
-- simple-thermostat: https://github.com/nervetattoo/simple-thermostat/releases (take the latest release)
-- thermostat: https://github.com/ciotlosm/custom-lovelace/tree/master/thermostat-card (both files .js and .lib.js are required)
+The following custom cards could be tested successfully:
+- `bignumber-card`: https://github.com/custom-cards/bignumber-card/blob/master/bignumber-card.js
+- `simple-thermostat`: https://github.com/nervetattoo/simple-thermostat/releases (take the latest release)
+- `thermostat`: https://github.com/ciotlosm/custom-lovelace/tree/master/thermostat-card (both files .js and .lib.js are required)
 
 I found this link https://github.com/jimz011/homeassistant as an interesting resource for custom cards.
 
-Often the custom cards are stored on github as sources and must be compiled before use.
-You should check the `Releases` menu on github and try to find compiled files there.
+Often the custom cards are stored on GitHub as sources and must be compiled before use.
+You should check the `Releases` menu on GitHub and try to find compiled files there.
 Like this one: [https://github.com/kalkih/mini-graph-card/releases](https://github.com/kalkih/mini-graph-card/releases) (Look for the file `mini-graph-card-bundle.js`)
 
 ## Own images
-The custom images (e.g. for background) could be loaded via the same configuration dialog like the custom cards. And use it like this:
+The custom images (e.g., for a background) could be loaded via the same configuration dialog like the custom cards. And use it like this:
 
 `background: center / cover no-repeat url("/cards/background.jpg") fixed`
 
@@ -310,10 +310,10 @@ or
 
 `background: center / cover no-repeat url("/local/custom_ui/background.jpg") fixed`
 
-in lovelace configuration file. Read more about background in lovelace [here](https://www.home-assistant.io/lovelace/views/#background).
+in lovelace configuration file. Read more about the background in lovelace [here](https://www.home-assistant.io/lovelace/views/#background).
 
 ## Themes
-The themes can be defined in configuration dialog of ioBroker.
+The themes can be defined in the configuration dialog of ioBroker.
 Paste something like:
 ```
 midnight:
@@ -386,7 +386,7 @@ midnight:
 taken from [here](https://community.home-assistant.io/t/midnight-theme/28598/2).
 
 ## Icons
-Use icons in form `mdi:NAME`, like 'mdi:play-network'. Names can be taken from here: https://materialdesignicons.com/
+Use icons in form `mdi:NAME`, like `mdi:play-network`. Names can be taken from here: https://materialdesignicons.com/
 
 ## Notifications
 You can add notifications via `sendTo` functionality or by writing the state into `lovelace.X.notifications.add`:
@@ -419,14 +419,14 @@ on({id: 'lovelace.0.conversation', ack: false, change: 'any'}, obj => {
 
 ## Trouble Shooting
 If you messed up the YAML Code and see a blank page but still have the top menu, you can enable edit mode (if not already enabled) from the menu and then open the menu again to access the "RAW Yaml Editor" in which you see the complete YAML code and can clean it up.
-If that does not help, you can open the object lovelace.*.configuration in raw-editor in ioBroker and have a look there.
+If that does not help, you can open the object `lovelace.*.configuration` in raw-editor in ioBroker and have a look there.
 You can also restore that object from a backup. It contains the complete configuration of your visualization.
 
 ## Original sources for lovelace
 Used sources are here https://github.com/GermanBluefox/home-assistant-polymer .
 
 ## Todo
-Security must be taken from current user and not from default_user
+Security must be taken from the current user and not from default_user
 
 ## Development
 ### Version
@@ -434,7 +434,7 @@ Used version of home-assistant-frontend@20231208.2
 Version of Browser Mod: 2.3.0
 
 ### How to build the new Lovelace version
-First of all the actual https://github.com/home-assistant/frontend (dev branch) must be **manually** merged into https://github.com/GermanBluefox/home-assistant-polymer.git (***iob*** branch!).
+First of all, the actual https://github.com/home-assistant/frontend (dev branch) must be **manually** merged into https://github.com/GermanBluefox/home-assistant-polymer.git (***iob*** branch!).
 
 All changes for ioBroker are marked with comment `// IoB`.
 For now (20231208.2) following files were modified:
@@ -443,14 +443,14 @@ For now (20231208.2) following files were modified:
 - `src/data/weather.ts` - add support to display weather icon from url.
 - `src/dialogs/more-info/const.ts` - remove weather state & history
 - `src/dialogs/more-info/ha-more-info-dialog.ts` - remove entity settings button and tab
-- `src/dialogs/more-info/ha-more-info-history.ts` - remove 'show more' link in history
+- `src/dialogs/more-info/ha-more-info-history.ts` - remove `show more` link in history
 - `src/dialogs/more-info/controls/more-info-weather.ts` - add support to display weather icon from url.
 - `src/dialogs/voice-command-dialog/ha-voice-command-dialog.ts` - disable configuration of voice assistants
 - `src/entrypoints/core.ts` - modified authentication process
 - `src/panels/lovelace/cards/hui-weather-forecast-card.ts` - add support to display weather icon from url.
 - `src/panels/lovelace/entity-rows/hui-weather-entity-row.ts` - add support to display weather icon from url with auth.
 - `src/panels/lovelace/hui-root.ts` - added notifications and voice control
-- `src/util/documentation-url.ts` - for link to iobroker help instead of homeassistant.
+- `src/util/documentation-url.ts` - for link to iobroker help instead of home assistant.
 - `.gitignore` - add `.idea` ignore
 - `.husky/pre-commit` - remove git commit hooks.
 - `package.json` - remove husky commit hook
@@ -465,14 +465,25 @@ After that checkout modified version in `./build` folder. Then.
 6. `gulp build-app` for release or `gulp develop-iob` for the debugging version. To build web after changes you can call `webpack-dev-app` for faster build, but you need to call `build-app` anyway after the version is ready for use.
 7. copy all files from `./build/home-assistant-polymer/hass_frontend` into `./hass_frontend` in this repo
 8. Run `gulp rename` task multiple times (until no changes happen).
-9. Update Version in Readme and also in server.js VERSION constant.
+9. Update version in `README.md` and also in `server.js` the `VERSION` constant.
 
 ## Changelog
 
 <!--
-	PLACEHOLDER for next version:
+	PLACEHOLDER for the next version:
 	### **WORK IN PROGRESS**
 -->
+### 4.1.5 (2024-03-05)
+* (Garfonso) fixed: possible crashes during startup
+
+### 4.1.4 (2024-02-10)
+* (Garfonso) improved fix: lamp icons now turn gray on switch off.
+
+### 4.1.3 (2024-02-10)
+* (Garfonso) prevent warning for browser_mod/recall_id service call
+* (Garfonso) fix: lamp icons now turn gray on switch off.
+* (Garfonso) fix: notifications via sendTo work again.
+
 ### 4.1.2 (2024-01-09)
 * (Garfonso) fix: time in timestamp display
 
@@ -482,15 +493,6 @@ After that checkout modified version in `./build` folder. Then.
 * (Garfonso) added: handle browser_mod/recall_id service call.
 * (Garfonso) changed: all states are strings (fixes #483)
 
-### 4.1.0 (2023-12-18)
-* (Garfons) add an option to show users on login screen (off by default)
-
-### 4.0.12 (2023-12-15)
-* (Garfonso) fix lint errors
-
-### 4.0.11 (2023-12-15)
-* (Garfonso) updated dependencies
-
 ## License
 
 Copyright 2019-2024, bluefox <dogafox@gmail.com>

package/io-package.json

@@ -1,8 +1,29 @@
 {
   "common": {
     "name": "lovelace",
-    "version": "4.1.2",
+    "version": "4.1.5",
     "news": {
+      "4.1.5": {
+        "en": "fixed: possible crashes during startup",
+        "de": "behoben: mögliche abstürzen beim start",
+        "ru": "фиксированный: возможные аварии во время запуска",
+        "pt": "corrigido: possíveis falhas durante a inicialização",
+        "nl": "vast: mogelijke crashes tijdens opstarten",
+        "fr": "corrigé: crashs possibles pendant le démarrage",
+        "it": "fisso: possibili crash durante l'avvio",
+        "es": "fijo: posibles fallos durante la puesta en marcha",
+        "pl": "stałe: możliwe awarie podczas uruchamiania",
+        "uk": "виправлено: можливі аварії під час запуску",
+        "zh-cn": "固定: 启动时可能发生的崩溃"
+      },
+      "4.1.4": {
+        "en": "improved fix: lamp icons now turn gray on switch off.",
+        "de": "verbesserter fix: lampensymbole werden nun grau beim ausschalten."
+      },
+      "4.1.3": {
+        "en": "prevent warning for browser_mod/recall_id service call\nfix: lamp icons now turn gray on switch off.\nfix: notifications via sendTo work again.",
+        "de": "Verhindere warnung für browser_mod/recall_id service call\nfix: Lampensymbole werden nun grau beim ausschalten.\nfix: Benachrichtigung mittels sendTo funktionieren wieder."
+      },
       "4.1.2": {
         "en": "fix: time in timestamp display",
         "de": "fix: zeit im zeitstempel-display",
@@ -36,27 +57,6 @@
         "pl": "błędy lintowe",
         "uk": "виправлено помилки в розмітці",
         "zh-cn": "f 固定错误"
-      },
-      "4.0.11": {
-        "en": "updated dependencies",
-        "de": "aktualisierte abhängigkeiten",
-        "ru": "обновленные зависимости",
-        "pt": "dependências atualizadas",
-        "nl": "vertaling:",
-        "fr": "dépendances actualisées",
-        "it": "dipendenze aggiornate",
-        "es": "dependencias actualizadas",
-        "pl": "zależności aktualizacji",
-        "uk": "оновлені залежності",
-        "zh-cn": "二. 最新依赖"
-      },
-      "4.0.10": {
-        "en": "brought back shopping list. Now also supports shopping/todo lists from manual entities.\nfix: browser console errors\nfix: login & authorization\nadded: user images & names on login screen",
-        "de": "Einkaufsliste funktioniert wieder. Zusätzliche Shopping/Todo-Listen können als manuellen Entities angelegt werden.\nfix: browser fehler\nfix: anmeldung & autorisierung\nhinzugefügt: benutzerbilder & namen auf login-bildschirm"
-      },
-      "4.0.9": {
-        "en": "fixed: timestamp in legacy history data",
-        "de": "fixed: zeitstempel in alten History daten"
       }
     },
     "title": "Visualization with Lovelace-UI",
@@ -175,6 +175,60 @@
           "agree",
           "cancel"
         ]
+      },
+      {
+        "condition": {
+          "operand": "and",
+          "rules": [
+            "oldVersion<=3.0.0",
+            "newVersion>=4.0.0"
+          ]
+        },
+        "title": {
+          "en": "Visualisation Update",
+          "de": "Aktualisierung der Visualisierung",
+          "ru": "Обновление визуализации",
+          "pt": "Atualização da visualização",
+          "nl": "Visualisatie Update",
+          "fr": "Mise à jour de la visualisation",
+          "it": "Aggiornamento della visualizzazione",
+          "es": "Actualización de Visualización",
+          "pl": "Visualizacja",
+          "uk": "Оновлення візуалізації",
+          "zh-cn": "更新"
+        },
+        "text": {
+          "en": "The update to version 4.x will change the frontend version from 20221026.0 to 20231208.2. This implies many months of Lovelace development in a single update. You will likely need to update or fix your themes and custom cards. Make sure to review your visualization after this update. Seek help in the forum or Discord if needed.",
+          "de": "Das Update auf Version 4.x wird die Frontend Version von 20221026.0 auf 20231208.2 ändern. Dies bedeutet 10 Monate Entwicklung von Lovelace in einem Update. Sie müssen wahrscheinlich Ihre Themen und benutzerdefinierten Karten aktualisieren oder reparieren. Achten Sie darauf, Ihre Visualisierung nach diesem Update zu überprüfen. Fragen Sie im Forum oder Discord nach Hilfe.",
+          "ru": "Обновление до версии 4.x изменит версию интерфейса с 20221026.0 на 20231208.2. Это означает многомесячную разработку Lovelace в рамках одного обновления. Вам, вероятно, придется обновить или исправить свои темы и пользовательские карты. Обязательно проверьте свою визуализацию после этого обновления. Задавайте вопросы на форуме или в Discord, если вам нужна помощь.",
+          "pt": "A atualização para a versão 4.x irá alterar a versão do frontend de 20221026.0 para 20231208.2. Isso significa muitos meses de desenvolvimento do Lovelace em uma única atualização. Você provavelmente precisará atualizar ou corrigir seus temas e cartões personalizados. Certifique-se de verificar sua visualização após esta atualização. Procure ajuda no fórum ou no Discord, se necessário.",
+          "nl": "De update naar versie 4.x zal de frontend-versie veranderen van 20221026.0 naar 20231208.2. Dit betekent vele maanden ontwikkeling van Lovelace in één update. Waarschijnlijk moet u uw thema's en aangepaste kaarten bijwerken of herstellen. Controleer na deze update uw visualisatie. Vraag om hulp op het forum of Discord indien nodig.",
+          "fr": "La mise à jour vers la version 4.x changera la version du frontend de 20221026.0 à 20231208.2. Cela signifie plusieurs mois de développement de Lovelace en une seule mise à jour. Vous devrez probablement mettre à jour ou réparer vos thèmes et cartes personnalisées. Assurez-vous de vérifier votre visualisation après cette mise à jour. Demandez de l'aide sur le forum ou sur Discord si nécessaire.",
+          "it": "L'aggiornamento alla versione 4.x cambierà la versione del frontend da 20221026.0 a 20231208.2. Ciò significa molti mesi di sviluppo di Lovelace in un singolo aggiornamento. Probabilmente sarà necessario aggiornare o correggere i temi e le carte personalizzate. Assicurati di controllare la tua visualizzazione dopo questo aggiornamento. Chiedi aiuto sul forum o su Discord se necessario.",
+          "es": "La actualización a la versión 4.x cambiará la versión del frontend de 20221026.0 a 20231208.2. Esto significa muchos meses de desarrollo de Lovelace en una sola actualización. Probablemente necesitarás actualizar o corregir tus temas y tarjetas personalizadas. Asegúrate de revisar tu visualización después de esta actualización. Busca ayuda en el foro o en Discord si es necesario.",
+          "pl": "Aktualizacja do wersji 4.x zmieni wersję frontendu z 20221026.0 na 20231208.2. Oznacza to wiele miesięcy rozwoju Lovelace w jednej aktualizacji. Prawdopodobnie będziesz musiał zaktualizować lub naprawić swoje motywy i niestandardowe karty. Upewnij się, że sprawdzisz swoją wizualizację po tej aktualizacji. Szukaj pomocy na forum lub Discord, jeśli to konieczne.",
+          "uk": "Оновлення до версії 4.x змінить версію фронтенду з 20221026.0 на 20231208.2. Це означає багато місяців розробки Lovelace у одному оновленні. Ймовірно, вам доведеться оновити або виправити свої теми та власні картки. Переконайтеся, що після цього оновлення ви переглянете свою візуалізацію. Звертайтеся за допомогою на форумі або в Discord, якщо потрібно.",
+          "zh-cn": "升级到4.x版本将把前端版本从20221026.0更改为20231208.2。这意味着在一个更新中进行了数月的Lovelace开发。您可能需要更新或修复您的主题和自定义卡片。请确保在此更新后检查您的可视化。如有需要，请在论坛或Discord上寻求帮助。"
+        },
+        "link": "https://forum.iobroker.net/topic/59435/test-lovelace-4-x/408?_=1705695186248",
+        "level": "warn",
+        "linkText": {
+          "en": "A few issues with themes were already discussed here.",
+          "de": "Hier wurden bereits einige Themen diskutiert.",
+          "ru": "Здесь уже обсуждались несколько вопросов с темами.",
+          "pt": "Algumas questões com temas já foram discutidas aqui.",
+          "nl": "Een paar problemen met ze werden hier al besproken.",
+          "fr": "Quelques questions avec des thèmes ont déjà été discutées ici.",
+          "it": "Sono già state discusse alcune questioni con temi.",
+          "es": "Algunos temas con temas ya se discutieron aquí.",
+          "pl": "Omawiano tam kilka tematów.",
+          "uk": "Тут вже обговорювалися кілька питань з темами.",
+          "zh-cn": "这里已经讨论了几个专题的问题。."
+        },
+        "buttons": [
+          "agree",
+          "cancel"
+        ]
       }
     ],
     "dependencies": [

package/lib/converters/genericConverter.js

@@ -59,7 +59,7 @@ exports.iobState2EntityState = function (entity, val, attribute) {
         return val ? 'on' : 'off';
     } else if (type === 'binary_sensor') {
         return val ? 'on' : 'off';
-    }else if (typeof val === 'number' && entity.attributes && ['date', 'timestamp'].includes(entity.attributes.device_class)) {
+    } else if (typeof val === 'number' && entity.attributes && ['date', 'timestamp'].includes(entity.attributes.device_class)) {
         //convert to date string
         const date = new Date(val);
         let dateStr = date.toDateString();