This adapter facilitates the connection of data from your Tibber account's API to be used within ioBroker, whether for a single home or multiple residences.
If you're not currently a Tibber user, I would greatly appreciate it if you could use my referral link: Tibber Referral Link.
- Begin by creating a new instance of the adapter.
- You'll also require an API token from Tibber, which you can obtain here: Tibber Developer API.
- Enter your Tibber API token in the standard settings and configure at least one line for live feed settings (select "None available").
- Save the settings and exit the configuration to restart the adapter; this step allows your home(s) to be queried the first time from the Tibber server.
- Return to the configuration screen and select the homes from which you wish to fetch real-time data using your Tibber Pulse. You can also select homes and disable the feed (Note: This works only if the hardware is installed and the Tibber server has verified the connection to Pulse).
- You have the option to deactivate the retrieval of price data for today and tomorrow, for instance, if you only intend to utilize Pulse live feeds
- Optionally, you can enable the retrieval of historical consumption data. Please specify the number of datasets for hours, days, weeks, months, and years. You can use "0" to disable one or more of these intervals based on your preferences.
- Note: It's essential to be mindful of the dataset size, as excessively large requests may result in a lack of response from the Tibber Server. We recommend experimenting with the dataset size to ensure optimal functionality. Adjusting the intervals and dataset numbers can help strike the right balance between obtaining insightful data and maintaining server responsiveness. E.g. 48 is a quite good amount for hours.
- Save the settings.
- Now that the Tibber connection is up and running, you can also leverage the Calculator to incorporate additional automation features into the TibberLink adapter.
- 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. Hereby the channelname choosen in admin screen is shown here to better identify your configurations.
- The behavior of each channel is determined by its type: "best cost (LTF)", "best single hours (LTF)", "best hours block (LTF)" or "smart battery buffer".
- Each channel populates one or two external states 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 writeable 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, 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.
Additionally, the average total cost in the determined block is written to a state "AverageTotalCost" nearby the input states of this channel. Also start and end hour of the block is written to "BlockStartFullHour" and "BlockEndFullHour" as a result of the calculation. - "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).
- "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."
To obtain, for example, peak hours instead of optimal hours, simply invert the usage and parameters:
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.
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.
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! Sentry reporting is initiated starting with js-controller 3.0.
If you enjoyed this project — or just feeling generous, consider buying me a beer. Cheers! 🍻
! Note that missing version entries are typically dependency updates for improved security.
- (HombachC) enable manual control of configured outputs when automation is deactivated (#334)
- (HombachC) fix not working LTF Channel when using too short LTF (#383)
- (HombachC) code optimisations
- (HombachC) update adapter-core to 3.1.4
- (HombachC) bump dependencies
- (HombachC) updated adapter testing
- (HombachC) bump dependencies
- (HombachC) BREAKING: dropped support for node.js 16 (#368)
- (HombachC) BREAKING: js-controller >= 5 is required
- (HombachC) changed to tier 2 as data provider
- (HombachC) corrected io-package.json according to new schema (#368)
- (HombachC) update typescript to 5.4.5
- (HombachC) update adapter-core to 3.0.6
- (HombachC) code optimizations
- (HombachC) fix undefined force mode (#349)
- (HombachC) fix poll of not existing current price state (#348)
- (HombachC) fix current price poll when configured as not to poll (#350)
- (HombachC) bump dependencies
- (HombachC) BREAKING: Calculator channels of type 'smart battery buffer' will now switch outputs to 'OFF' only once, directly after setting the channel to Active=false (#332)
- (HombachC) Fixed error in jsonConfig.json (#329)
- (HombachC) deleted feed disconnect debug-message, cause warn message already exists
- (HombachC) bump typescript-eslint to gen 7
- (HombachC) bump dependencies
- (HombachC) simplify internal state handling
- (HombachC) shorten home string in Calculator screen (#317)
- (HombachC) fix feedback loop trap (#321)
- (HombachC) add some tooltips to config screen (#317)
- (HombachC) fix edge case problems with defect feed data from Tibber server (#312)
- (HombachC) bump dependencies
- (HombachC) add data points for BestHoursBlock results - period and average cost (#240)
- (HombachC) fixed wrong error message texts
- (HombachC) fix some possible edge cases in internal support functions
- (HombachC) internal code docu optimization
- (HombachC) bump dependencies
- (HombachC) fix reconnect error for Pulse feed (#300)
- (HombachC) new error message handler
- (HombachC) internal code docu optimization
- (HombachC) add repeatablity for LTF channels (#289)
- (HombachC) tweak Smart Battery Buffer documentation
- (HombachC) modify timing in Tibber Pulse feed connect (#271)
- (HombachC) bump dependencies
- (HombachC) BREAKING: dropped support for js-controller 3.x (#247)
- (HombachC) diversificate Tibber server polls to prevent potential DDoS reactions (#252)
- (HombachC) add data point for averageRemaining of todays prices (#254)
- (HombachC) add 2 data points for last successfull update of today and tomorrow prices (#261)
- (HombachC) year 2024 changes
- (HombachC) fix small error in dynamic feed timing
- (HombachC) bump dependencies
- (HombachC) add notice about changes in configuration
- (HombachC) implement optional disable of price pull (#232)
- (HombachC) implement price categorization algorithm for battery buffer applications (#193)
- (HombachC) Fix 2 errors in pull of prices tomorrow (#235, #232)
- (HombachC) changed Tibber link in config
- (HombachC) implemented dynamic raise of feed reconnect (#225)
- (HombachC) small bugfix in pricecalls
- (HombachC) first changes for "smart battery buffer" (#193)
- (HombachC) update typescript to 5.3.3
- (HombachC) added hint for consumption data in documentation (#223)
- (HombachC) mitigate error handling (#217)
- (HombachC) added description to object Features/RealTimeConsumptionEnabled (#224)
- (HombachC) bump dependencies
- (HombachC) implement getting historical consumption data from Tibber Server (#163)
- (HombachC) fix error in adapter unload
- (HombachC) some code optimisations
- (HombachC) cleanup in documentation and translation handling
- (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
- (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
Old Changes see CHANGELOG OLD
GNU General Public License v3.0 only
Copyright (c) 2023-2024 C.Hombach TibberLink@homba.ch