iobroker.tibberlink 1.4.3 → 1.6.0

package/README.md

@@ -47,24 +47,69 @@ If you're not currently a Tibber user, I would greatly appreciate it if you coul
 -   The Calculator operates using channels, with each channel linked to a selected home.
 -   These channels can be activated or deactivated based on corresponding states.
 -   These states are designed to serve as external, dynamic inputs for TibberLink, allowing you to, for example, adjust the marginal cost ("TriggerPrice") from an external source or disable the calculator channel ("Active").
--   The states of a calculator channel are positioned adjacent to the home states and named according to the channel number.
-    ![Calculator States](admin/calculatorStates.png)
+-   The states of a calculator channel are positioned adjacent to the home states and named according to the channel number. Hereby the channelname choosen in admin screen is shown here to better identify your configurations.  
+    ![Calculator States](docu/calculatorStates.png)
 -   The behavior of each channel is determined by its type: "best cost," "best single hours," or "best hours block".
 -   Each channel populates an external state as output, which has to be selected in the settings tab. For instance, this state might be "0_userdata.0.example_state" or any other writable external state.
 -   The values to be written to the output state can be defined in "value YES" and "value NO," e.g., "true" for boolean states or a number or text to be written.
 -   Outputs:
-    -   "Best cost": Utilizes the "TriggerPrice" state as input, and the output is "YES" every hour when the current Tibber energy cost is below the trigger price.
-    -   "Best single hours": The output is "YES" during the cheapest number of hours, with the number defined in the "AmountHours" state.
-    -   "Best hours block": The output is "YES" during the best block of hours, with the number of hours defined in the "AmountHours" state.
+    -   "Best cost": Utilizes the "TriggerPrice" state as input, producing a "YES" output every hour when the current Tibber energy cost is below the trigger price.
+    -   "Best single hours": Generates a "YES" output during the least expensive hours, with the number defined in the "AmountHours" state.
+    -   "Best hours block": Outputs "YES" during the most cost-effective block of hours, with the number of hours specified in the "AmountHours" state.
+    -   "Best cost LTF": "Best cost" within a Limited Time Frame (LTF).
+    -   "Best single hours LTF": "Best single hours" within a Limited Time Frame (LTF).
+    -   "Best hours block LTF": "Best hours block" within a Limited Time Frame (LTF).
+-   LTF channels: Function similarly to standard channels but only operate within a time frame defined by the "StartTime" and "StopTime" state objects. After "StopTime," the channel deactivates itself. "StartTime" and "StopTime" may span over several days. The states must be filled with a date-time string in ISO-8601 format with a timezone offset, such as: "2023-11-17T21:00:00.000+01:00".
+
+### Hint
+
+#### Inverse Usage:
+
+To obtain, for example, peak hours instead of optimal hours, simply invert the usage and parameters:
+![Calculator States Inverse](docu/calculatorStatesInverse.png)
+By swapping true <-> false, you will receive a true at a low cost in the first line and a true at a high cost in the second line (Channel names are not triggers and are still free to choose).
+
+Attention: For peak single hours, such as in the example, you also need to adjust the number of hours. Original: 5 -> Inverse (24-5) = 19 -> You will obtain a true result during the 5 peak hours.
+
+#### LTF channels:
+
+The calculation is performed for "multiday" data. As we only have information for "today" and "tomorrow" (available after approximately 13:00), the time scope is effectively limited to a maximum of 35 hours. However, it's crucial to be mindful of this behavior because the calculated result may/will change around 13:00 when new data for tomorrow's prices becomes available.
+
+To observe this dynamic change in the time scope for a standard channel, you may opt for a Limited Time Frame (LTF) spanning several years. This is particularly useful for the "Best Single Hours LTF" scenario.
 
 ## Notes
 
 This adapter employs Sentry libraries to automatically report exceptions and code errors to the developers. For more details and information on how to disable error reporting, please consult the [Sentry-Plugin Documentation](https://github.com/ioBroker/plugin-sentry#plugin-sentry)! Sentry reporting is initiated starting with js-controller 3.0.
 
+## Donate
+
+<a href="https://www.paypal.com/donate/?hosted_button_id=F7NM9R2E2DUYS"><img src="https://raw.githubusercontent.com/Hombach/ioBroker.tibberlink/main/docu/bluePayPal.svg" height="40"></a>  
+If you enjoyed this project — or just feeling generous, consider buying me a beer. Cheers! :beers:
+
 ## Changelog
 
 ! Note that missing version entries are typically dependency updates for improved security.
 
+### 1.6.0 (2023-11-26)
+
+-   (HombachC) fixed major bug in 1.5.0, not working calculator channels (#212)
+-   (HombachC) implement limit calculations to a time frame (#153)
+-   (HombachC) fix error of missing price data upon not working tibber server connect at adapter start (#204)
+-   (HombachC) fixed possible error with wrong price date in multi home systems
+-   (HombachC) fixed possible type error, notified by Sentry
+-   (HombachC) added some documentation for inverse use of channels (#202)
+-   (HombachC) added Sentry statistics
+-   (HombachC) optimize translation handling
+-   (HombachC) bump dependencies
+
+### 1.5.0 (2023-11-13)
+
+-   (HombachC) implement calculator channel names (#186)
+-   (HombachC) fix error in cron jobs (#190)
+-   (HombachC) remove not used calculator channel state objects (#188)
+-   (HombachC) code optimizations
+-   (HombachC) optimize translation handling
+
 ### 1.4.3 (2023-11-08)
 
 -   (HombachC) fix possible type error in first calculator calls notified by Sentry
@@ -206,7 +251,6 @@ This adapter employs Sentry libraries to automatically report exceptions and cod
 
 ### 0.1.10 (2023-08-15)
 
--   (HombachC) bump dependencies, code cleanups
 -   (HombachC) preparations for tibber calculator
 -   (HombachC) mitigate multi homes & pulse problems (#41)
 -   (HombachC) add documentation to config screen (#47)
@@ -250,10 +294,6 @@ This adapter employs Sentry libraries to automatically report exceptions and cod
 -   (HombachC) hide unused checkboxes in config
 -   (HombachC) fix snyc and appveyor
 
-### 0.1.1 (2023-07-16)
-
--   (HombachC) remove release script and dev-server
-
 ### 0.1.0 (2023-07-14)
 
 -   (HombachC) initial version

package/admin/i18n/de/OLDtranslations.json

@@ -0,0 +1,3 @@
+{
+	"s_Active": "Aktiv"
+}

package/admin/i18n/en/OLDtranslations.json

@@ -0,0 +1,3 @@
+{
+	"s_Active": "Active"
+}

package/admin/i18n/es/OLDtranslations.json

@@ -0,0 +1,3 @@
+{
+	"s_Active": "Activo"
+}

package/admin/i18n/fr/translations.json

@@ -1,9 +1,3 @@
 {
-	"s_Home": "Maison Tibber",
-	"s_CalculatorChannels": "Canaux d'automatisation",
-	"s_UseCalculator": "Utiliser l'automatisation",
-	"s_ChannelHome": "Canal Maison",
-	"s_ChannelType": "Type de canal",
-	"s_Active": "Actif",
-	"s_TargetState": "État cible"
+	"s_Active": "Actif"
 }

package/admin/i18n/it/translations.json

@@ -1,9 +1,3 @@
 {
-	"s_Home": "Casa Tibber",
-	"s_CalculatorChannels": "Canali di automazione",
-	"s_UseCalculator": "Utilizza l'automazione",
-	"s_ChannelHome": "Canale Casa",
-	"s_ChannelType": "Tipo di canale",
-	"s_Active": "Attivo",
-	"s_TargetState": "Stato obiettivo"
+	"s_Active": "Attivo"
 }

package/admin/i18n/nl/translations.json

@@ -1,9 +1,3 @@
 {
-	"s_Home": "Tibber Thuis",
-	"s_CalculatorChannels": "Automatiseringskanalen",
-	"s_UseCalculator": "Automatisering gebruiken",
-	"s_ChannelHome": "Kanaal Thuis",
-	"s_ChannelType": "Kanaaltype",
-	"s_Active": "Actief",
-	"s_TargetState": "Doelstaat"
+	"s_Active": "Actief"
 }

package/admin/i18n/pl/translations.json

@@ -1,9 +1,3 @@
 {
-	"s_Home": "Dom Tibber",
-	"s_CalculatorChannels": "Kanały automatyzacji",
-	"s_UseCalculator": "Użyj automatyzacji",
-	"s_ChannelHome": "Kanał domowy",
-	"s_ChannelType": "Typ kanału",
-	"s_Active": "Aktywny",
-	"s_TargetState": "Stan docelowy"
+	"s_Active": "Aktywny"
 }

package/admin/i18n/pt/translations.json

@@ -1,9 +1,3 @@
 {
-	"s_Home": "Casa Tibber",
-	"s_CalculatorChannels": "Canais de automação",
-	"s_UseCalculator": "Usar automação",
-	"s_ChannelHome": "Canal Casa",
-	"s_ChannelType": "Tipo de canal",
-	"s_Active": "Ativo",
-	"s_TargetState": "Estado alvo"
+	"s_Active": "Ativo"
 }

package/admin/i18n/ru/translations.json

@@ -1,9 +1,3 @@
 {
-	"s_Home": "Дом Tibber",
-	"s_CalculatorChannels": "Каналы автоматизации",
-	"s_UseCalculator": "Использовать автоматизацию",
-	"s_ChannelHome": "Канал Дом",
-	"s_ChannelType": "Тип канала",
-	"s_Active": "Активен",
-	"s_TargetState": "Целевое состояние"
+	"s_Active": "Активен"
 }

package/admin/i18n/uk/translations.json

@@ -1,9 +1,3 @@
 {
-	"s_Home": "Tibber Дім",
-	"s_CalculatorChannels": "Канали автоматизації",
-	"s_UseCalculator": "Використовувати автоматизацію",
-	"s_ChannelHome": "Канал Дім",
-	"s_ChannelType": "Тип каналу",
-	"s_Active": "Активний",
-	"s_TargetState": "Цільовий стан"
+	"s_Active": "Активний"
 }

package/admin/i18n/zh-cn/translations.json

@@ -1,9 +1,3 @@
 {
-	"s_Home": "Tibber家",
-	"s_CalculatorChannels": "自动化通道",
-	"s_UseCalculator": "使用自动化",
-	"s_ChannelHome": "家庭通道",
-	"s_ChannelType": "通道类型",
-	"s_Active": "活跃",
-	"s_TargetState": "目标状态"
+	"s_Active": "活跃"
 }