iobroker.tibberlink 7.0.0 → 7.1.1

package/README.md

@@ -26,10 +26,10 @@
 
 [![NPM](https://nodei.co/npm/iobroker.tibberlink.png?downloads=true)](https://nodei.co/npm/iobroker.tibberlink/)
 
-## Adapter for Utilizing TIBBER energy data in ioBroker
+## Adapter for Utilizing Tibber Energy Data in ioBroker
 
-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.
-New Feature: The adapter now supports direct local reading of the Tibber Pulse Sensor through your home network, allowing for real-time monitoring and data collection without relying solely on the cloud API.
+This adapter connects your Tibber account's API data to ioBroker, whether for a single home or multiple residences.
+It also supports direct local reading of the Tibber Pulse sensor via your home network, enabling real-time monitoring and data collection without relying solely on the cloud API.
 
 If you're not currently a Tibber user, I would greatly appreciate it if you could use my referral link: [Tibber Referral Link](https://invite.tibber.com/mu8c82n5).
 
@@ -38,24 +38,32 @@ If you're not currently a Tibber user, I would greatly appreciate it if you coul
 - 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](https://developer.tibber.com).
 - 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.
+- Save the settings and exit the configuration to restart the adapter; this step allows your home(s) to be queried for 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).
-- Note: If you have more than one home actively in your Tibber account you have to add all of them to get rid of error message caused by potentially not needed homes. Add them all and disable the options.
-- 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
+- Note: If you have more than one home in your Tibber account, you must add all of them to avoid error messages caused by homes that may not be needed. Add them all and disable the unwanted ones.
+- You have the option to deactivate the retrieval of price data for today and tomorrow, for instance, if you only intend to use the Pulse live feed.
 - 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.
+- Note: It's essential to be mindful of the dataset size, as excessively large requests may result in no 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. For example, 48 is a recommended value for hours.
 - Save the settings.
 
+## Consumption Data Documentation
+
+When daily historical consumption is enabled, the adapter provides an aggregated state for the current month:
+
+- `Homes.<HOME-ID>.Consumption.currentMonthConsumption`
+
+This state is the total consumption for the current calendar month in `kWh`, calculated from the daily consumption data returned by Tibber. If too few days are configured, the value will only reflect that number of days — not a complete month.
+
 ## Calculator Configuration
 
 - 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 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 enable the calculator channel ("Active").
 - These channels have to be activated or deactivated based on corresponding states.
-- 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 states of a calculator channel are positioned adjacent to the home states and named according to the channel number. The channel name entered in the admin screen is displayed here to help identify your configurations.  
+  <img src="docu/calculatorStates.png" width="938" alt="Calculator States">
 - 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.
+- Each channel populates one or two external states as output, which have to be selected in the settings tab. For instance, this state might be "0_userdata.0.example_state" or any other writeable external state.
 - If no external output state is selected, an internal state within the channel's range will be created.
 - 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:
@@ -76,18 +84,17 @@ If you're not currently a Tibber user, I would greatly appreciate it if you coul
             - Expensive timeslots: Battery charging is disabled (value NO) and feed into the home energy system is enabled (value 2 YES). These slots have the highest prices, above the dynamically calculated threshold based on the cheapest timeslot prices and efficiency loss.
             - Normal timeslots: Where charging is not economically viable, both outputs are disabled.
         - This approach ensures that the battery is only used when it is economically beneficial, rather than strictly adhering to a fixed number of hours.
-- 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.
+- 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.
 
 ## Graph Output Configuration
 
-The adapter helps visualize price trends and calculator results. It provides three levels of complexity, each offering different options.
-These three methods provide various options for visualizing price trends and calculator results. Depending on your requirements, you can choose from a simple JSON-based approach to a fully customized JavaScript solution.
+The adapter helps visualize price trends and calculator results. It provides three levels of complexity — from a simple JSON-based approach to a fully customized JavaScript solution.
 
 ### 1. **(Under Development) Visualization using the "E-Charts" Adapter**
 
 This method requires the "E-Charts" adapter to be installed separately.
 
-- JSON data can be used, generated in the Calculator States section as `Output-E-Charts`.
+- JSON data generated in the Calculator States section (`Output-E-Charts`) can be used.
 - The capabilities are limited by the constraints of the E-Charts adapter.
 
 ### 2. **Using the "FlexCharts" (or "Fully Featured eCharts") Adapter with JSON**
@@ -96,13 +103,13 @@ This method requires the "FlexCharts" adapter to be installed separately.
 
 - The TibberLink adapter creates a state called `jsonFlexCharts`.
 
-    ![jsonFlexChartsState.png](docu/jsonFlexChartsState.png)
+        <img src="docu/jsonFlexChartsState.png" width="938" alt="jsonFlexCharts State">
 
 - The FlexCharts adapter renders this state via the following URL:
     ```
     http://[YOUR IP of FLEXCHARTS]:8082/flexcharts/echarts.html?source=state&id=tibberlink.0.Homes.[TIBBER-HOME-ID].PricesTotal.jsonFlexCharts
     ```
-- Starting with V0.7.0 FlexCharts supports automatic chart updates via SSE (Server Sent Events). To use this add `&sse` to the URL:
+- Starting with V0.7.0, FlexCharts supports automatic chart updates via SSE (Server-Sent Events). To use this add `&sse` to the URL:
     ```
     http://[YOUR IP of FLEXCHARTS]:8082/flexcharts/echarts.html?source=state&id=tibberlink.0.Homes.[TIBBER-HOME-ID].PricesTotal.jsonFlexCharts&sse=30
     ```
@@ -111,16 +118,16 @@ This method requires the "FlexCharts" adapter to be installed separately.
 #### **JSON Template Usage**
 
 - The `jsonFlexCharts` state is generated based on a template configured via the JSON editor in the adapter settings.
-- **Important:** The built-in JSON editor in ioBroker.Admin does not support JSON5, which may cause false error messages.
+- The built-in JSON editor uses JSON5 mode, so comments and trailing commas are permitted.
 - A sample template can be downloaded from: [TemplateFlexChart01.md](docu/TemplateFlexChart01.md).
 - Copy and paste the template into the JSON editor.
 - The template contains the placeholders:
-    - `%%xAxisData%%` and `%%yAxisData%%` (populated with price information at runtime).
+    - `%%seriesData%%` (populated with the time-series price data at runtime).
     - `%%CalcChannelsData%%` (populated with selected calculator channel data).
 - The rest of the template follows the Apache ECharts configuration. For reference, see [Apache ECharts Examples](https://echarts.apache.org/examples/en/index.html).
 - **Recommendation:** Test the TibberLink adapter without a real template using the default string:
     ```
-    %%xAxisData%%\n\n%%yAxisData%%\n\n%%CalcChannelsData%%
+    %%seriesData%%\n\n%%CalcChannelsData%%
     ```
     This helps understand its functionality.
 - Template adjustments can be tested on Apache ECharts examples pages using the "Output-E-Charts" state data.
@@ -139,25 +146,86 @@ For maximum flexibility and customization, the FlexCharts adapter can be used wi
 ### 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.
+<img src="docu/calculatorStatesInverse.png" width="938" alt="Calculator States Inverse">
+
+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 just examples and can be freely chosen).
+
+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' output 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.
+The calculation is performed for "multiday" data. As we only have information for "today" and "tomorrow" (available after approximately 13:00), the time scope covers up to 48 hours, though typically around 35 hours immediately after the 13:00 price update. 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.
 
 ## Direct local poll of Pulse data
 
 To make it work, you need to modify the web interface of the Bridge to remain permanently enabled.
-marq24 has described how to do this excellently for his HomeAssistant integration here:
+marq24 provides an excellent description of how to do this for his Home Assistant integration here:
 
 https://github.com/marq24/ha-tibber-pulse-local
 
-If everything works correctly, the meter data will be written to IoBroker states every 2 seconds.
+If everything works correctly, the meter data will be written to ioBroker states every 2 seconds.
+
+## Vehicles & Chargers Configuration
+
+Tibber operates two separate APIs with different purposes:
+
+- **Developer GraphQL API** (`api.tibber.com`) — energy prices, consumption history, and the Pulse live feed. This is what the standard Tibber API token (from [developer.tibber.com](https://developer.tibber.com)) gives access to.
+- **Tibber Data API** (`data-api.tibber.com`) — IoT device data for paired vehicles, chargers, heat pumps, and inverters. This is a newer, separate REST API that requires its own OAuth2 client registration.
+
+Neither API replaces the other — they complement each other. The vehicle and charger feature described here uses the Data API and therefore needs its own credentials in addition to the main API token.
+
+### Prerequisites
+
+1. Open [https://data-api.tibber.com/clients/manage](https://data-api.tibber.com/clients/manage) and click **+ New client**.
+
+ <img src="docu/dataApi1.png" width="938" alt="Tibber Data API Client Management">
+
+2. Give the client a name (e.g. `ioBrokerTibber`), set the **Redirect URI** to exactly `http://localhost/` (with trailing slash), and enable at least these scopes:
+    - `data-api-homes-read`
+    - `data-api-vehicles-read`
+    - `data-api-chargers-read`
+
+    <img src="docu/dataApi2.png" width="938" alt="Create client form with scopes">
+
+3. Click **Create**. Copy the **Client ID** and **Client Secret** immediately — the secret is only shown once.
+
+ <img src="docu/dataApi3.png" width="938" alt="Client created with ID and Secret">
+
+4. Open the **Vehicles & Chargers** tab in the adapter configuration, enter both values, and save.
+5. Restart the adapter. It will log a **warning** containing the ready-to-use authorization URL with your Client ID already filled in:
+    ```
+    [tibberDataAPI]: no auth code configured — please authorize. URL: https://thewall.tibber.com/connect/authorize?client_id=<your-id>&...
+    ```
+6. Open that URL in a browser and log in with your Tibber account to grant access.
+7. The browser will redirect to `http://localhost/` and show a connection error — this is **expected and correct**. Copy the full URL from the address bar (it contains `?code=...`).
+
+ <img src="docu/dataApi4.png" width="938" alt="Browser showing localhost connection refused with code in URL">
+
+8. Paste the complete URL into the **Auth Code** field in the adapter configuration and save.
+9. The adapter exchanges the code for tokens and begins polling. The Auth Code field is cleared automatically.
+
+The adapter stores the refresh token internally and renews the access token automatically, so this one-time authorization step does not need to be repeated.
+
+### Available States
+
+Vehicle data is written to `Vehicles.<VIN>.*`:
+
+| State                 | Description                       |
+| --------------------- | --------------------------------- |
+| `ChargingStatus`      | Current charging status           |
+| `HomeId`              | Associated Tibber home ID         |
+| `LastUpdated`         | Timestamp of the last data update |
+| `PlugStatus`          | Plug connection status            |
+| `Range`               | Remaining range in km             |
+| `StateOfCharge`       | Battery state of charge in %      |
+| `TargetStateOfCharge` | Target state of charge in %       |
+
+### Poll Interval
+
+The poll interval can be configured in the **Vehicles & Chargers** tab (1–60 minutes, default: 5 minutes).
 
 ## Sentry
 
@@ -174,6 +242,21 @@ If you enjoyed this project — or just feeling generous, consider buying me a b
   Placeholder for the next version (at the beginning of the line):
   ### **WORK IN PROGRESS**
 -->
+### 7.1.1 (2026-06-07)
+
+- (HombachC) optimized vehicle states
+- (HombachC) fixed adapter checker warnings
+
+### 7.1.0 (2026-06-07)
+
+- (claude) added integration for vehicles(#67)
+- (HombachC) optimized documentation
+- (claude) added code documentation
+- (claude) performance optimization of event listeners
+- (HombachC) added current month consumption docu
+- (HombachC) updated release-script
+- (HombachC) fixed adapter checker warnings
+
 ### 7.0.0 (2026-06-04)
 
 - (copilot) BREAKING: Adapter requires node.js >= 22 now
@@ -197,19 +280,6 @@ If you enjoyed this project — or just feeling generous, consider buying me a b
 - (HombachC) switch to ES2023 code
 - (HombachC) update dependencies
 
-### 6.2.0 (2026-03-07)
-
-- (HombachC) enable umlauts to calculation channel names (#844)
-- (HombachC) enhance resolution of pulse meter data (#840)
-- (HombachC) fix wrong end block state calculation (#841)
-- (HombachC) setup auto-merge for dependabot (#834)
-- (HombachC) update dependencies
-
-### 6.1.1 (2026-02-05)
-
-- (HombachC) fix LTF shifting for frames greater 24h
-- (HombachC) update dependencies
-
 ### Old Changes see [CHANGELOG OLD](CHANGELOG_OLD.md)
 
 ## License

package/admin/i18n/de.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "Das Passwort für Ihre lokale Tibber Bridge, wie auf der Hardware angegeben.",
 	"TTIP_item_tibberBridgeRawDataInterval": "Das Intervall (in Millisekunden) für die Abfrage Ihrer Bridge nach Pulse-Daten.",
 	"TTIP_item_tibberBridgeUrl": "Name Ihrer Bridge oder ihre IP-Adresse (standardmäßig „tibber-host“).",
-	"TTIP_item_tibberPulseLocalNodeId": "Die Knoten-ID, unter der Ihr Pulse auf der Bridge registriert ist."
-}
+	"TTIP_item_tibberPulseLocalNodeId": "Die Knoten-ID, unter der Ihr Pulse auf der Bridge registriert ist.",
+	"LBL_VehiclesTab": "Fahrzeuge & Ladestationen",
+	"LBL_vehiclesHelp1": "Schritt 1: OAuth2-Client unter data-api.tibber.com/clients/manage registrieren. Redirect-URI exakt auf http://localhost/ setzen (mit abschließendem Schrägstrich) und folgende Scopes aktivieren: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Dann Client ID und Client Secret unten eintragen.",
+	"LBL_vehiclesRegisterLink": "Tibber Data API Client-Verwaltung oeffnen",
+	"LBL_TibberClientId": "Tibber Data API Client ID",
+	"TTIP_TibberClientId": "OAuth2 Client ID aus dem Tibber Data API Client-Verwaltungsportal",
+	"LBL_TibberClientSecret": "Tibber Data API Client Secret",
+	"TTIP_TibberClientSecret": "OAuth2 Client Secret aus dem Tibber Data API Client-Verwaltungsportal",
+	"LBL_vehiclesHelp2": "Schritt 2: Einstellungen speichern und Adapter neu starten. Im ioBroker-Log erscheint dann eine Warnung mit der vollständigen Autorisierungs-URL (Client ID bereits eingesetzt). Diese URL im Browser öffnen und mit dem Tibber-Konto anmelden.",
+	"LBL_vehiclesHelp2b": "Der Browser zeigt 'Verbindung abgelehnt' – das ist erwartet. Vollständige URL aus der Adressleiste kopieren und unten in das Feld 'Autorisierungs-Callback-URL' einfügen.",
+	"LBL_TibberAuthCode": "Autorisierungs-Callback-URL (einmalig einfuegen, dann leer lassen)",
+	"TTIP_TibberAuthCode": "Die vollstaendige Callback-URL (http://localhost/?code=...) hier einfuegen. Sie wird beim naechsten Adapterstart verarbeitet und automatisch geloescht.",
+	"LBL_TibberDataApiInterval": "Abfrageintervall (Minuten)",
+	"TTIP_TibberDataApiInterval": "Wie oft Fahrzeug- und Ladedaten von der Tibber Data API abgefragt werden (1-60 Minuten)"
+}

package/admin/i18n/en.json

@@ -104,5 +104,18 @@
 	"LBL_FlexGraphPastCutOff": "FlexGraph past hours cut off",
 	"TTIP_FlexGraphPastCutOff": "number of hours to be shown in the past",
 	"LBL_FlexGraphFutureCutOff": "FlexGraph future hours cut off",
-	"TTIP_FlexGraphFutureCutOff": "number of hours to be shown in the future"
-}
+	"TTIP_FlexGraphFutureCutOff": "number of hours to be shown in the future",
+	"LBL_VehiclesTab": "Vehicles & Chargers",
+	"LBL_vehiclesHelp1": "Step 1: Register an OAuth2 client at data-api.tibber.com/clients/manage. Set the redirect URI to exactly http://localhost/ (with trailing slash) and enable these scopes: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Then enter your Client ID and Client Secret below.",
+	"LBL_vehiclesRegisterLink": "Open Tibber Data API client management",
+	"LBL_TibberClientId": "Tibber Data API Client ID",
+	"TTIP_TibberClientId": "OAuth2 Client ID from the Tibber Data API client management portal",
+	"LBL_TibberClientSecret": "Tibber Data API Client Secret",
+	"TTIP_TibberClientSecret": "OAuth2 Client Secret from the Tibber Data API client management portal",
+	"LBL_vehiclesHelp2": "Step 2: Save the settings and restart the adapter. It will log a warning containing the authorization URL with your Client ID already filled in. Open that URL in your browser and log in with your Tibber account.",
+	"LBL_vehiclesHelp2b": "The browser will show ‘connection refused’ — that is expected. Copy the full URL from the address bar and paste it into the Authorization callback URL field below.",
+	"LBL_TibberAuthCode": "Authorization callback URL (paste once, then leave empty)",
+	"TTIP_TibberAuthCode": "Paste the full callback URL (http://localhost/?code=...) here. It will be consumed on the next adapter start and cleared automatically.",
+	"LBL_TibberDataApiInterval": "Poll interval (minutes)",
+	"TTIP_TibberDataApiInterval": "How often vehicle and charger data is fetched from the Tibber Data API (1-60 minutes)"
+}

package/admin/i18n/es.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "La contraseña de su Tibber Bridge local, tal como se proporciona en el hardware.",
 	"TTIP_item_tibberBridgeRawDataInterval": "El intervalo, en milisegundos, para sondear los datos de Bridge for Pulse.",
 	"TTIP_item_tibberBridgeUrl": "Nombre de su Bridge o su dirección IP (el valor predeterminado es 'tibber-host').",
-	"TTIP_item_tibberPulseLocalNodeId": "El ID del nodo donde está registrado su Pulse en el Bridge."
+	"TTIP_item_tibberPulseLocalNodeId": "El ID del nodo donde está registrado su Pulse en el Bridge.",
+	"LBL_VehiclesTab": "Vehículos y cargadores",
+	"LBL_vehiclesHelp1": "Paso 1: Registre un cliente OAuth2 en data-api.tibber.com/clients/manage. Configure el URI de redirección exactamente como http://localhost/ (con barra final) y active estos permisos: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Luego introduzca su Client ID y Client Secret a continuación.",
+	"LBL_vehiclesRegisterLink": "Abrir administración de clientes de Tibber Data API",
+	"LBL_TibberClientId": "ID de cliente de Tibber Data API",
+	"TTIP_TibberClientId": "ID de cliente OAuth2 del portal de administración de clientes de Tibber Data API",
+	"LBL_TibberClientSecret": "Secreto de cliente de Tibber Data API",
+	"TTIP_TibberClientSecret": "Secreto de cliente OAuth2 del portal de administración de clientes de Tibber Data API",
+	"LBL_vehiclesHelp2": "Paso 2: Guarda la configuración y reinicia el adaptador. El log de ioBroker mostrará una advertencia con la URL de autorización completa (con tu Client ID ya incluido). Abre esa URL en tu navegador e inicia sesión con tu cuenta Tibber.",
+	"LBL_vehiclesHelp2b": "El navegador mostrará 'conexión rechazada' — eso es esperado. Copia la URL completa de la barra de direcciones y pégala en el campo URL de callback de autorización abajo.",
+	"LBL_TibberAuthCode": "URL de devolución de llamada (pegar una vez, luego dejar vacío)",
+	"TTIP_TibberAuthCode": "Pegue aquí la URL completa de devolución de llamada (http://localhost/?code=...). Se usará en el próximo inicio del adaptador y se borrará automáticamente.",
+	"LBL_TibberDataApiInterval": "Intervalo de sondeo (minutos)",
+	"TTIP_TibberDataApiInterval": "Con qué frecuencia se obtienen datos de vehículos y cargadores de Tibber Data API (1-60 minutos)"
 }

package/admin/i18n/fr.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "Le mot de passe de votre Tibber Bridge local, tel qu'indiqué sur le matériel.",
 	"TTIP_item_tibberBridgeRawDataInterval": "L'intervalle, en millisecondes, pour interroger votre Bridge for Pulse.",
 	"TTIP_item_tibberBridgeUrl": "Nom de votre Bridge ou son adresse IP (par défaut 'tibber-host').",
-	"TTIP_item_tibberPulseLocalNodeId": "L'ID du nœud où votre Pulse est enregistré sur le Bridge."
+	"TTIP_item_tibberPulseLocalNodeId": "L'ID du nœud où votre Pulse est enregistré sur le Bridge.",
+	"LBL_VehiclesTab": "Véhicules et chargeurs",
+	"LBL_vehiclesHelp1": "Étape 1 : Enregistrez un client OAuth2 sur data-api.tibber.com/clients/manage. Définissez l'URI de redirection exactement sur http://localhost/ (avec barre oblique finale) et activez ces autorisations : data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Saisissez ensuite votre Client ID et Client Secret ci-dessous.",
+	"LBL_vehiclesRegisterLink": "Ouvrir la gestion des clients Tibber Data API",
+	"LBL_TibberClientId": "ID client Tibber Data API",
+	"TTIP_TibberClientId": "ID client OAuth2 du portail de gestion des clients Tibber Data API",
+	"LBL_TibberClientSecret": "Secret client Tibber Data API",
+	"TTIP_TibberClientSecret": "Secret client OAuth2 du portail de gestion des clients Tibber Data API",
+	"LBL_vehiclesHelp2": "Étape 2 : Enregistrez les paramètres et redémarrez l'adaptateur. Le log ioBroker affichera un avertissement contenant l'URL d'autorisation complète (avec votre Client ID déjà inclus). Ouvrez cette URL dans votre navigateur et connectez-vous avec votre compte Tibber.",
+	"LBL_vehiclesHelp2b": "Le navigateur affichera « connexion refusée » — c'est normal. Copiez l'URL complète depuis la barre d'adresse et collez-la dans le champ URL de rappel d'autorisation ci-dessous.",
+	"LBL_TibberAuthCode": "URL de rappel d'autorisation (coller une fois, puis laisser vide)",
+	"TTIP_TibberAuthCode": "Collez ici l'URL de rappel complète (http://localhost/?code=...). Elle sera utilisée au prochain démarrage de l'adaptateur et effacée automatiquement.",
+	"LBL_TibberDataApiInterval": "Intervalle d'interrogation (minutes)",
+	"TTIP_TibberDataApiInterval": "Fréquence de récupération des données des véhicules et chargeurs depuis Tibber Data API (1-60 minutes)"
 }

package/admin/i18n/it.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "La password per il tuo Tibber Bridge locale, come fornita sull'hardware.",
 	"TTIP_item_tibberBridgeRawDataInterval": "L'intervallo, in millisecondi, per il polling dei dati Bridge for Pulse.",
 	"TTIP_item_tibberBridgeUrl": "Nome del tuo Bridge o relativo indirizzo IP (il valore predefinito è \"tibber-host\").",
-	"TTIP_item_tibberPulseLocalNodeId": "L'ID del nodo in cui è registrato il tuo Pulse sul Bridge."
+	"TTIP_item_tibberPulseLocalNodeId": "L'ID del nodo in cui è registrato il tuo Pulse sul Bridge.",
+	"LBL_VehiclesTab": "Veicoli e caricatori",
+	"LBL_vehiclesHelp1": "Passaggio 1: Registra un client OAuth2 su data-api.tibber.com/clients/manage. Imposta l'URI di reindirizzamento esattamente su http://localhost/ (con barra finale) e abilita questi permessi: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Inserisci quindi il tuo Client ID e Client Secret qui sotto.",
+	"LBL_vehiclesRegisterLink": "Apri la gestione client Tibber Data API",
+	"LBL_TibberClientId": "ID client Tibber Data API",
+	"TTIP_TibberClientId": "ID client OAuth2 dal portale di gestione client Tibber Data API",
+	"LBL_TibberClientSecret": "Segreto client Tibber Data API",
+	"TTIP_TibberClientSecret": "Segreto client OAuth2 dal portale di gestione client Tibber Data API",
+	"LBL_vehiclesHelp2": "Passaggio 2: Salva le impostazioni e riavvia l'adattatore. Il log di ioBroker mostrerà un avviso con l'URL di autorizzazione completo (con il tuo Client ID già incluso). Apri quell'URL nel browser e accedi con il tuo account Tibber.",
+	"LBL_vehiclesHelp2b": "Il browser mostrerà «connessione rifiutata» — è normale. Copia l'URL completo dalla barra degli indirizzi e incollalo nel campo URL di callback di autorizzazione sottostante.",
+	"LBL_TibberAuthCode": "URL di callback di autorizzazione (incolla una volta, poi lascia vuoto)",
+	"TTIP_TibberAuthCode": "Incolla qui l'URL di callback completo (http://localhost/?code=...). Verrà utilizzato al prossimo avvio dell'adattatore e cancellato automaticamente.",
+	"LBL_TibberDataApiInterval": "Intervallo di polling (minuti)",
+	"TTIP_TibberDataApiInterval": "Con quale frequenza vengono recuperati i dati di veicoli e caricatori dall'API Tibber Data (1-60 minuti)"
 }

package/admin/i18n/nl.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "Het wachtwoord voor uw lokale Tibber Bridge, zoals aangegeven op de hardware.",
 	"TTIP_item_tibberBridgeRawDataInterval": "Het interval, in milliseconden, voor het opvragen van uw Bridge for Pulse-gegevens.",
 	"TTIP_item_tibberBridgeUrl": "Naam van uw Bridge of zijn IP-adres (standaard 'tibber-host').",
-	"TTIP_item_tibberPulseLocalNodeId": "Het knooppunt-ID waar uw Pulse op de Bridge is geregistreerd."
+	"TTIP_item_tibberPulseLocalNodeId": "Het knooppunt-ID waar uw Pulse op de Bridge is geregistreerd.",
+	"LBL_VehiclesTab": "Voertuigen en laders",
+	"LBL_vehiclesHelp1": "Stap 1: Registreer een OAuth2-client op data-api.tibber.com/clients/manage. Stel de omleidings-URI in op precies http://localhost/ (met afsluitende schuine streep) en schakel deze rechten in: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Voer daarna uw Client ID en Client Secret hieronder in.",
+	"LBL_vehiclesRegisterLink": "Tibber Data API-clientbeheer openen",
+	"LBL_TibberClientId": "Tibber Data API Client ID",
+	"TTIP_TibberClientId": "OAuth2 Client ID van het Tibber Data API-clientbeheerportaal",
+	"LBL_TibberClientSecret": "Tibber Data API Client Secret",
+	"TTIP_TibberClientSecret": "OAuth2 Client Secret van het Tibber Data API-clientbeheerportaal",
+	"LBL_vehiclesHelp2": "Stap 2: Sla de instellingen op en herstart de adapter. Het ioBroker-log toont een waarschuwing met de volledige autorisatie-URL (met je Client ID al ingevuld). Open die URL in je browser en log in met je Tibber-account.",
+	"LBL_vehiclesHelp2b": "De browser toont 'verbinding geweigerd' — dat is verwacht. Kopieer de volledige URL uit de adresbalk en plak deze in het veld Autorisatie-callback-URL hieronder.",
+	"LBL_TibberAuthCode": "Autorisatie callback-URL (eenmalig plakken, daarna leeg laten)",
+	"TTIP_TibberAuthCode": "Plak hier de volledige callback-URL (http://localhost/?code=...). Deze wordt gebruikt bij de volgende start van de adapter en automatisch verwijderd.",
+	"LBL_TibberDataApiInterval": "Poll-interval (minuten)",
+	"TTIP_TibberDataApiInterval": "Hoe vaak worden voertuig- en ladergegevens opgehaald uit de Tibber Data API (1-60 minuten)"
 }

package/admin/i18n/pl.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "Hasło do lokalnego mostu Tibber Bridge, podane na sprzęcie.",
 	"TTIP_item_tibberBridgeRawDataInterval": "Interwał w milisekundach odpytywania danych Bridge for Pulse.",
 	"TTIP_item_tibberBridgeUrl": "Nazwa Twojego mostu lub jego adres IP (domyślnie „tibber-host”).",
-	"TTIP_item_tibberPulseLocalNodeId": "Identyfikator węzła, w którym Twój Pulse jest zarejestrowany na moście."
+	"TTIP_item_tibberPulseLocalNodeId": "Identyfikator węzła, w którym Twój Pulse jest zarejestrowany na moście.",
+	"LBL_VehiclesTab": "Pojazdy i ładowarki",
+	"LBL_vehiclesHelp1": "Krok 1: Zarejestruj klienta OAuth2 na data-api.tibber.com/clients/manage. Ustaw URI przekierowania dokładnie jako http://localhost/ (z końcowym ukośnikiem) i włącz te uprawnienia: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Następnie wprowadź swój Client ID i Client Secret poniżej.",
+	"LBL_vehiclesRegisterLink": "Otwórz zarządzanie klientami Tibber Data API",
+	"LBL_TibberClientId": "Tibber Data API Client ID",
+	"TTIP_TibberClientId": "OAuth2 Client ID z portalu zarządzania klientami Tibber Data API",
+	"LBL_TibberClientSecret": "Tibber Data API Client Secret",
+	"TTIP_TibberClientSecret": "OAuth2 Client Secret z portalu zarządzania klientami Tibber Data API",
+	"LBL_vehiclesHelp2": "Krok 2: Zapisz ustawienia i uruchom ponownie adapter. W logu ioBroker pojawi się ostrzeżenie z pełnym adresem URL autoryzacji (z Twoim Client ID już wstawionym). Otwórz ten URL w przeglądarce i zaloguj się na swoje konto Tibber.",
+	"LBL_vehiclesHelp2b": "Przeglądarka pokaże 'odmowa połączenia' — to oczekiwane. Skopiuj pełny adres URL z paska adresu i wklej go w pole URL wywołania zwrotnego autoryzacji poniżej.",
+	"LBL_TibberAuthCode": "URL wywołania zwrotnego autoryzacji (wkleić raz, potem pozostawić puste)",
+	"TTIP_TibberAuthCode": "Wklej tutaj pełny URL wywołania zwrotnego (http://localhost/?code=...). Zostanie użyty przy następnym uruchomieniu adaptera i automatycznie usunięty.",
+	"LBL_TibberDataApiInterval": "Interwał odpytywania (minuty)",
+	"TTIP_TibberDataApiInterval": "Jak często dane pojazdów i ładowarek są pobierane z Tibber Data API (1-60 minut)"
 }

package/admin/i18n/pt.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "A senha do seu Tibber Bridge local, conforme fornecida no hardware.",
 	"TTIP_item_tibberBridgeRawDataInterval": "O intervalo, em milissegundos, para pesquisar dados do Bridge for Pulse.",
 	"TTIP_item_tibberBridgeUrl": "Nome da sua Bridge ou seu endereço IP (o padrão é 'tibber-host').",
-	"TTIP_item_tibberPulseLocalNodeId": "O ID do nó onde seu Pulse está registrado na Bridge."
+	"TTIP_item_tibberPulseLocalNodeId": "O ID do nó onde seu Pulse está registrado na Bridge.",
+	"LBL_VehiclesTab": "Veículos e carregadores",
+	"LBL_vehiclesHelp1": "Passo 1: Registe um cliente OAuth2 em data-api.tibber.com/clients/manage. Defina o URI de redirecionamento exatamente como http://localhost/ (com barra final) e ative estas permissões: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Em seguida, introduza o seu Client ID e Client Secret abaixo.",
+	"LBL_vehiclesRegisterLink": "Abrir gestão de clientes Tibber Data API",
+	"LBL_TibberClientId": "ID de cliente Tibber Data API",
+	"TTIP_TibberClientId": "ID de cliente OAuth2 do portal de gestão de clientes Tibber Data API",
+	"LBL_TibberClientSecret": "Segredo de cliente Tibber Data API",
+	"TTIP_TibberClientSecret": "Segredo de cliente OAuth2 do portal de gestão de clientes Tibber Data API",
+	"LBL_vehiclesHelp2": "Passo 2: Guarde as definições e reinicie o adaptador. O log do ioBroker mostrará um aviso com o URL de autorização completo (com o seu Client ID já incluído). Abra esse URL no browser e inicie sessão com a sua conta Tibber.",
+	"LBL_vehiclesHelp2b": "O browser mostrará 'ligação recusada' — isso é esperado. Copie o URL completo da barra de endereços e cole-o no campo URL de callback de autorização abaixo.",
+	"LBL_TibberAuthCode": "URL de callback de autorização (colar uma vez, depois deixar vazio)",
+	"TTIP_TibberAuthCode": "Cole aqui o URL de callback completo (http://localhost/?code=...). Será utilizado no próximo arranque do adaptador e apagado automaticamente.",
+	"LBL_TibberDataApiInterval": "Intervalo de sondagem (minutos)",
+	"TTIP_TibberDataApiInterval": "Com que frequência os dados de veículos e carregadores são obtidos da Tibber Data API (1-60 minutos)"
 }

package/admin/i18n/ru.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "Пароль для вашего локального Tibber Bridge, предусмотренный на оборудовании.",
 	"TTIP_item_tibberBridgeRawDataInterval": "Интервал в миллисекундах для опроса вашего моста на предмет импульсных данных.",
 	"TTIP_item_tibberBridgeUrl": "Имя вашего моста или его IP-адрес (по умолчанию «tibber-host»).",
-	"TTIP_item_tibberPulseLocalNodeId": "Идентификатор узла, на котором ваш Pulse зарегистрирован на мосту."
+	"TTIP_item_tibberPulseLocalNodeId": "Идентификатор узла, на котором ваш Pulse зарегистрирован на мосту.",
+	"LBL_VehiclesTab": "Транспортные средства и зарядные устройства",
+	"LBL_vehiclesHelp1": "Шаг 1: Зарегистрируйте клиент OAuth2 на data-api.tibber.com/clients/manage. Установите URI перенаправления точно как http://localhost/ (с завершающим слешем) и включите следующие разрешения: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Затем введите ваш Client ID и Client Secret ниже.",
+	"LBL_vehiclesRegisterLink": "Открыть управление клиентами Tibber Data API",
+	"LBL_TibberClientId": "Tibber Data API Client ID",
+	"TTIP_TibberClientId": "OAuth2 Client ID из портала управления клиентами Tibber Data API",
+	"LBL_TibberClientSecret": "Tibber Data API Client Secret",
+	"TTIP_TibberClientSecret": "OAuth2 Client Secret из портала управления клиентами Tibber Data API",
+	"LBL_vehiclesHelp2": "Шаг 2: Сохраните настройки и перезапустите адаптер. В логе ioBroker появится предупреждение с полным URL авторизации (с уже подставленным Client ID). Откройте этот URL в браузере и войдите в аккаунт Tibber.",
+	"LBL_vehiclesHelp2b": "Браузер покажет «отказано в подключении» — это ожидаемо. Скопируйте полный URL из адресной строки и вставьте его в поле URL обратного вызова авторизации ниже.",
+	"LBL_TibberAuthCode": "URL обратного вызова авторизации (вставить один раз, затем оставить пустым)",
+	"TTIP_TibberAuthCode": "Вставьте сюда полный URL обратного вызова (http://localhost/?code=...). Он будет использован при следующем запуске адаптера и автоматически очищен.",
+	"LBL_TibberDataApiInterval": "Интервал опроса (минуты)",
+	"TTIP_TibberDataApiInterval": "Как часто данные транспортных средств и зарядных устройств запрашиваются из Tibber Data API (1-60 минут)"
 }

package/admin/i18n/uk.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "Пароль для вашого локального Tibber Bridge, як зазначено на апаратному забезпеченні.",
 	"TTIP_item_tibberBridgeRawDataInterval": "Інтервал, у мілісекундах, для опитування вашого Bridge для даних Pulse.",
 	"TTIP_item_tibberBridgeUrl": "Ім'я вашого Bridge або його IP-адреса (за замовчуванням \"tibber-host\").",
-	"TTIP_item_tibberPulseLocalNodeId": "Ідентифікатор вузла, де ваш Pulse зареєстровано на Bridge."
+	"TTIP_item_tibberPulseLocalNodeId": "Ідентифікатор вузла, де ваш Pulse зареєстровано на Bridge.",
+	"LBL_VehiclesTab": "Транспортні засоби та зарядні пристрої",
+	"LBL_vehiclesHelp1": "Крок 1: Зареєструйте клієнт OAuth2 на data-api.tibber.com/clients/manage. Встановіть URI перенаправлення точно як http://localhost/ (з кінцевим слешем) і увімкніть такі дозволи: data-api-homes-read, data-api-vehicles-read, data-api-chargers-read. Потім введіть ваш Client ID і Client Secret нижче.",
+	"LBL_vehiclesRegisterLink": "Відкрити управління клієнтами Tibber Data API",
+	"LBL_TibberClientId": "Tibber Data API Client ID",
+	"TTIP_TibberClientId": "OAuth2 Client ID з порталу управління клієнтами Tibber Data API",
+	"LBL_TibberClientSecret": "Tibber Data API Client Secret",
+	"TTIP_TibberClientSecret": "OAuth2 Client Secret з порталу управління клієнтами Tibber Data API",
+	"LBL_vehiclesHelp2": "Крок 2: Збережіть налаштування та перезапустіть адаптер. У лозі ioBroker з'явиться попередження з повним URL авторизації (з вашим Client ID вже вставленим). Відкрийте цей URL у браузері та увійдіть в акаунт Tibber.",
+	"LBL_vehiclesHelp2b": "Браузер покаже «відмовлено у з'єднанні» — це очікувано. Скопіюйте повний URL з адресного рядка та вставте його в поле URL зворотного виклику авторизації нижче.",
+	"LBL_TibberAuthCode": "URL зворотного виклику авторизації (вставити один раз, потім залишити порожнім)",
+	"TTIP_TibberAuthCode": "Вставте сюди повний URL зворотного виклику (http://localhost/?code=...). Його буде використано при наступному запуску адаптера та автоматично очищено.",
+	"LBL_TibberDataApiInterval": "Інтервал опитування (хвилини)",
+	"TTIP_TibberDataApiInterval": "Як часто дані транспортних засобів та зарядних пристроїв запитуються з Tibber Data API (1-60 хвилин)"
 }

package/admin/i18n/zh-cn.json

@@ -104,5 +104,18 @@
 	"TTIP_item_tibberBridgePassword": "硬件上提供的本地 Tibber Bridge 的密码。",
 	"TTIP_item_tibberBridgeRawDataInterval": "轮询 Bridge 获取脉冲数据的时间间隔（以毫秒为单位）。",
 	"TTIP_item_tibberBridgeUrl": "您的网桥名称或其 IP 地址（默认为“tibber-host”）。",
-	"TTIP_item_tibberPulseLocalNodeId": "您的 Pulse 在网桥上注册的节点 ID。"
+	"TTIP_item_tibberPulseLocalNodeId": "您的 Pulse 在网桥上注册的节点 ID。",
+	"LBL_VehiclesTab": "车辆与充电器",
+	"LBL_vehiclesHelp1": "步骤1：在 data-api.tibber.com/clients/manage 注册 OAuth2 客户端。将重定向 URI 设置为 http://localhost/（末尾带斜杠），并启用以下权限：data-api-homes-read、data-api-vehicles-read、data-api-chargers-read。然后在下方输入您的 Client ID 和 Client Secret。",
+	"LBL_vehiclesRegisterLink": "打开 Tibber Data API 客户端管理",
+	"LBL_TibberClientId": "Tibber Data API 客户端 ID",
+	"TTIP_TibberClientId": "来自 Tibber Data API 客户端管理门户的 OAuth2 客户端 ID",
+	"LBL_TibberClientSecret": "Tibber Data API 客户端密钥",
+	"TTIP_TibberClientSecret": "来自 Tibber Data API 客户端管理门户的 OAuth2 客户端密钥",
+	"LBL_vehiclesHelp2": "第二步：保存设置并重启适配器。ioBroker 日志将显示一条包含完整授权 URL（已填入您的 Client ID）的警告信息。在浏览器中打开该 URL 并使用 Tibber 账户登录。",
+	"LBL_vehiclesHelp2b": "浏览器将显示「连接被拒绝」——这是正常现象。从地址栏复制完整 URL 并粘贴到下方的授权回调 URL 字段中。",
+	"LBL_TibberAuthCode": "授权回调 URL（粘贴一次后留空）",
+	"TTIP_TibberAuthCode": "在此粘贴完整的回调 URL（http://localhost/?code=...）。它将在下次适配器启动时使用并自动清除。",
+	"LBL_TibberDataApiInterval": "轮询间隔（分钟）",
+	"TTIP_TibberDataApiInterval": "从 Tibber Data API 获取车辆和充电器数据的频率（1-60 分钟）"
 }

package/admin/jsonConfig.json

@@ -1158,6 +1158,112 @@
 					]
 				}
 			}
+		},
+
+		"_VehiclesTab": {
+			"type": "panel",
+			"label": "LBL_VehiclesTab",
+			"xs": 12,
+			"sm": 12,
+			"md": 12,
+			"lg": 12,
+			"xl": 12,
+			"items": {
+				"_vehiclesHelp1": {
+					"type": "staticText",
+					"text": "LBL_vehiclesHelp1",
+					"xs": 12,
+					"sm": 12,
+					"md": 12,
+					"lg": 12,
+					"xl": 12,
+					"newLine": true
+				},
+				"_vehiclesRegisterLink": {
+					"type": "staticLink",
+					"label": "LBL_vehiclesRegisterLink",
+					"href": "https://data-api.tibber.com/clients/manage",
+					"button": true,
+					"icon": "info",
+					"xs": 12,
+					"sm": 12,
+					"md": 12,
+					"lg": 12,
+					"xl": 12,
+					"newLine": true
+				},
+				"TibberClientId": {
+					"type": "text",
+					"label": "LBL_TibberClientId",
+					"tooltip": "TTIP_TibberClientId",
+					"maxLength": 120,
+					"xs": 12,
+					"sm": 12,
+					"md": 8,
+					"lg": 6,
+					"xl": 4,
+					"newLine": true
+				},
+				"TibberClientSecret": {
+					"type": "password",
+					"label": "LBL_TibberClientSecret",
+					"tooltip": "TTIP_TibberClientSecret",
+					"maxLength": 120,
+					"xs": 12,
+					"sm": 12,
+					"md": 8,
+					"lg": 6,
+					"xl": 4,
+					"newLine": true
+				},
+				"_vehiclesHelp2": {
+					"type": "staticText",
+					"text": "LBL_vehiclesHelp2",
+					"xs": 12,
+					"sm": 12,
+					"md": 12,
+					"lg": 12,
+					"xl": 12,
+					"newLine": true
+				},
+				"_vehiclesHelp2b": {
+					"type": "staticText",
+					"text": "LBL_vehiclesHelp2b",
+					"xs": 12,
+					"sm": 12,
+					"md": 12,
+					"lg": 12,
+					"xl": 12,
+					"newLine": true
+				},
+				"TibberAuthCode": {
+					"type": "text",
+					"label": "LBL_TibberAuthCode",
+					"tooltip": "TTIP_TibberAuthCode",
+					"maxLength": 500,
+					"xs": 12,
+					"sm": 12,
+					"md": 12,
+					"lg": 10,
+					"xl": 8,
+					"newLine": true
+				},
+				"TibberDataApiInterval": {
+					"type": "number",
+					"label": "LBL_TibberDataApiInterval",
+					"tooltip": "TTIP_TibberDataApiInterval",
+					"min": 1,
+					"max": 60,
+					"step": 1,
+					"default": 5,
+					"xs": 12,
+					"sm": 6,
+					"md": 4,
+					"lg": 3,
+					"xl": 2,
+					"newLine": true
+				}
+			}
 		}
 	}
 }