Tibber

logiccloud Control can connect to the Tibber GraphQL API to retrieve data for a home (for example current and future electricity prices and consumption) and store the result in a program variable. To do this, a new connection of type Tibber must be created and parameterized in the connection settings of the respective runtime.

Create a new Tibber connection

Select Add Tibber connection and enter the Tibber GraphQL endpoint together with your personal access token. After the connection has been created, select it in the outline tree to edit its configuration.

Connection settings:

• Name: Name of the connection
• Description: Description, optional
• Url: endpoint of the Tibber GraphQL server (Tibber’s public API endpoint)
• Token: access token used to authenticate against the Tibber GraphQL server. Generate a personal access token in your Tibber developer account.
• Connect timeout: timeout (in seconds) for connecting and re-connecting to Tibber; default 30, minimum 3
• Poll period: interval (in seconds) at which data is fetched from Tibber; default 60, minimum 3
• Home id: identifier of the home in your Tibber account to read data for (optional; empty by default — see below)
• Variable name: the program variable that stores the data retrieved from Tibber

Finding the Home ID

A Tibber account can contain more than one home. The Home id selects which home the connection reads from. You can look up a home’s ID by querying the Tibber GraphQL API (for example the viewer.homes query, which returns each home’s id) with the same access token. If the account has only one home the field can be left empty, in which case that home is used.

Mapping data into the runtime

Unlike register- or topic-based connectors, a Tibber connection does not use a mapping table. The data returned by Tibber for the configured home is written directly into the single program variable named in Variable name. Create an access variable of a matching type to receive the retrieved data.