iobroker.tibberlink 3.5.2 → 3.5.4

package/README.md

@@ -68,7 +68,7 @@ If you're not currently a Tibber user, I would greatly appreciate it if you coul
     -   "Best hours block LTF": "Best hours block" within a Limited Time Frame (LTF).
     -   "Smart Battery Buffer": Utilize the "EfficiencyLoss" parameter to specify the efficiency loss of the battery system. The "EfficiencyLoss" parameter can range from 0 to 1, where 0 represents no efficiency loss and 1 represents complete efficiency loss. For example, a value of 0.25 indicates a 25% efficiency loss for a charge/discharge cycle.  
         Use the "AmountHours" parameter to input the desired number of hours for battery charging. The calculator will activate battery charging ("value YES") and deactivate battery feed ("value 2 NO") during the specified "AmountHours" cheapest hours. Conversely, it will deactivate battery charging ("value NO") and activate battery feed ("value 2 YES") during hours with the highest cost, provided the cost is higher than the highest total price among the cheap hours. In the remaining normal hours where energy buffering by the battery is not economically viable, both outputs will be switched off.
--   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: "2024-01-17T21:00:00.000+01:00". Additionally, the channels have a new state parameter called "RepeatDays," which is set to 0 by default. If "RepeatDays" is set to a positive integer value, the channel will repeat its cycle by increasing both StartTime and StopTime by the number of days specified in "RepeatDays", once StopTime is reached. E.g. For daily repetition, set "RepeatDays" to 1."
+-   LTF channels: These operate similarly to standard channels but are active only within a time frame defined by the 'StartTime' and 'StopTime' state objects. After 'StopTime,' the channel automatically deactivates. 'StartTime' and 'StopTime' can span two calendar days, as Tibber does not provide data beyond a 48-hour window. Both states require a date-time string in ISO-8601 format with a timezone offset, e.g., '2024-12-24T18:00:00.000+01:00'." Additionally, the LTF channels feature a new state parameter called 'RepeatDays,' which defaults to 0. When 'RepeatDays' is set to a positive integer, the channel will repeat its cycle by incrementing both 'StartTime' and 'StopTime' by the specified number of days after 'StopTime' is reached. For example, set 'RepeatDays' to 1 for daily repetition.
 
 ### Hints
 
@@ -106,6 +106,23 @@ If you enjoyed this project — or just feeling generous, consider buying me a b
 
 ## Changelog
 
+### 3.5.4 (2024-12-01)
+
+-   (HombachC) add warning when LTF stop time isn't same or next day and provide docu
+-   (HombachC) fix error in calculator channel 'best single hours' (#594)
+-   (HombachC) intruduce 'iobroker/eslint-config' (#591)
+-   (HombachC) performance optimizations
+-   (HombachC) dependency updates
+
+### 3.5.3 (2024-11-23)
+
+-   (HombachC) fix edge case in output state setup and usage
+-   (HombachC) optimzed state subscription
+-   (HombachC) update deprecated state calls
+-   (HombachC) add await to delObjectAsync
+-   (HombachC) harmonize project tools
+-   (HombachC) dependency updates
+
 ### 3.5.2 (2024-10-30)
 
 -   (HombachC) add verification for YES/NO 2 values in calculator (#547)

package/admin/jsonConfig.json

@@ -59,6 +59,11 @@
 					"href": "https://invite.tibber.com/mu8c82n5",
 					"button": true,
 					"icon": "info",
+					"xs": 12,
+					"sm": 12,
+					"md": 12,
+					"lg": 12,
+					"xl": 12,
 					"newLine": true
 				},
 				"HomesList": {