Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


  • 1

SmartHomeEddy
 Share

Question

This QuickApp gets your energy consumption and production data from Tibber Live. 
This QuickApp can be used in combination with the Tibber Monitor to get the Tibber Prices. 
Based on the Fibaro WebSockets/GraphQL demo by Peter Gebruers 

 

If you use Tibber for your Energy Panel, you can use this Tibber Live QuickApp for your energy consumption and production combined with the Tibber Monitor QuickApp to provide the Energy Panel with the hourly prices. 

 

Please login or register to see this image.

/monthly_2022_08/image.png.e02b5123ae5e74aa18c67a4d49af38b8.png" />

 

 

Main device with positive or negative actual power consumption

 

Child devices are available for:

  • power (Actual consumption with maxPower in log text)
  • powerProduction (Actual production with maxPowerProduction in log text)
  • accumulatedConsumption (Todays consumption, also the child device for the Energy Panel)
  • accumulatedProduction (Todays production)
  • accumulatedCost (Todays cost)
  • accumulatedConsumptionLastHour (Consumed since since last hour shift)
  • accumulatedProductionLastHour (Produced since last hour shift)
  • lastMeterConsumption (Total consumption)
  • lastMeterProduction (Total production)
  • voltagePhase1
  • voltagePhase2
  • voltagePhase3
  • currentL1
  • currentL2
  • currentL3

 

Please login or register to see this attachment.

 

Available information: 

  • power (Consumption at the moment (Watt))
  • maxPower (Peak consumption since midnight (Watt))
  • powerProduction (Net production (A-) at the moment (Watt))
  • maxPowerProduction (Max net production since midnight (Watt))
  • accumulatedConsumption (kWh consumed since midnight)
  • accumulatedProduction (net kWh produced since midnight)
  • accumulatedCost (Accumulated cost since midnight; requires active Tibber power deal)
  • currency (Currency of displayed cost; requires active Tibber power deal)
  • lastMeterConsumption (Last meter active import register state (kWh))
  • lastMeterProduction (Last meter active export register state (kWh))
  • voltagePhase1 (Voltage on phase 1) *
  • voltagePhase2 (Voltage on phase 2) *
  • voltagePhase3 (Voltage on phase 3) *
  • currentL1 (Current on L1) *
  • currentL2 (Current on L2) *
  • currentL3 (Current on L3) *
  • accumulatedConsumptionLastHour (kWh consumed since since last hour shift)
  • accumulatedProductionLastHour (net kWh produced since last hour shift)
  • accumulatedReward (Accumulated reward since midnight; requires active Tibber power deal)
  • minPower (Min consumption since midnight (Watt))
  • averagePower (Average consumption since midnight (Watt))
  • powerReactive (Reactive consumption (Q+) at the moment (kVAr)) *
  • powerProductionReactive (Net reactive production (Q-) at the moment (kVAr)) *
  • minPowerProduction (Min net production since midnight (Watt))
  • maxPowerProduction (Max net production since midnight (Watt))
  • powerFactor (Power factor (active power / apparent power)) *
  • signalStrength (Device signal strength (Pulse - dB; Watty - percent)) *
  • timestamp (Timestamp when usage occurred)

* on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. In this QuickApp "null" values are replaced by their previous values. 

 

To communicate with the API you need to acquire a OAuth access token and pass this along with every request passed to the server.
A Personal Access Token give you access to your data and your data only. 
This is ideal for DIY people that want to leverage the Tibber platform to extend the smartness of their home. 
Such a token can be acquired here:

Please login or register to see this link.

 

When creating your access token or OAuth client you’ll be asked which scopes you want the access token to be associated with. 
These scopes tells the API which data and operations the client is allowed to perform on the user’s behalf. 
The scopes your app requires depend on the type of data it is trying to request. 
If you for example need access to user information you add the USER scope. 
If information about the user's homes is needed you add the appropriate HOME scopes.
If you have more than one home in your subscription, you need to fill in your home number the change between your homes. 


If the Tibber server disconnects the webSocket, the QuickApp wil do a re-connect for the amount in the QuickApp variable reconnect. 
If the re-connect fails for that amount, there will be a timeout for the seconds in the QuickApp variable timeout. 

 

Use this QuickApp at your own risk. You are responsible for ensuring that the information provided via this QuickApp do not contain errors. 
Tibber is a registered trademark being the property of TIBBER. TIBBER reserves all rights to the registered trademarks.
Information which is published on TIBBER’s websites belongs to TIBBER or is used with the permission of the rights holder. 
Making of copies, presentations, distribution, display or any other transfer of the information on the website to the public is, except for strictly private use, prohibited unless done with the consent of TIBBER. 
Published material on dedicated TIBBER press websites, intended for public use, is exempt from the consent requirement.
Also see:

Please login or register to see this link.

 

Guide Communicating with the Tibber API:

Please login or register to see this link.


Tibber API Explorer:

Please login or register to see this link.


Fibaro webSocket manual:

Please login or register to see this link.


Fibaro Forum Headers in webSocket:

Please login or register to see this link.


WebSocket++ Documentation:

Please login or register to see this link.


GraphQL query language:

Please login or register to see this link.

 

Version 2.0 (5th August 2022)

  • Added two child devices, Hourly Consumption and Hourly Production
  • Added re-connect routine to handleError. If an Tibber error occurs, the QuickApp will try to re-connect. Thanks @JcBorgs for testing. 
  • Improved routine to handle Tibber null values. Thanks @Darquan for testing. 
  • Changed labels a bit to save some space
  • Changed "volt" and "amp" text in the labels. Thanks @Morten22 for mentioning. 
  • Changed kWh device types from com.fibaro.electricMeter to com.fibaro.energyMeter

Version 1.0 (19th June 2022)

  • Initial webSocket version Tibber Live
  • Thanks @JcBorgs for testing all beta versions and great suggestion to improve the quickapp
  • Based on the Fibaro WebSockets/GraphQL demo by @petergebruers


Variables (mandatory and created automatically): 

  • token = Authorization token (see the Tibber website: https://developer.tibber.com)

  • homeId = Tibber Home ID (see the Tibber website: https://developer.tibber.com)

  • reconnect = Amount of re-connects after disconnect from Tibber server (default = 10)

  • timeout = Pause after maximum amount of re-connects (default = 300)

  • debugLevel = Number (1=some, 2=few, 3=all, 4=Offline Simulation Mode, 5=Live Test Mode) (default = 1)

 

Fibaro Firmware:

Minimal version 5.111.48 (beta)

 

Download the QuickApp here (download the file and un-zip):

Please login or register to see this link.

or from the Fibaro Marketplace:

Please login or register to see this link.


How to install: 

  1. Open the Configuration Interface
  2. Go to Settings > Devices
  3. Click  +
  4. Choose Other Device
  5. Choose Upload File
  6. Choose file from your computer with .fqa

 

 

 

 

 

Edited by SmartHomeEddy
  • Like 2
  • Thanks 2
Link to comment
Share on other sites

18 answers to this question

Recommended Posts

  • 0
  • Inquirer
  • Posted (edited)

    Thanks to @petergebruers for getting the (new) Fibaro webSocket to work with Tibber Live, soon to come the Tibber Live Quickapp ...

     

     

    Please login or register to see this attachment.


     

    Please login or register to see this attachment.


     


     

    Edited by SmartHomeEddy
    • Like 2
    • Thanks 1
    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • @JcBorgs and I have fought some null and nil values, disconnects, but it looks like we got a fine working quickapp now. Let’s see how it behaves for a while. 

    • Thanks 1
    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • Posted (edited)

    The Tibber Live QuickApp is available for download. Minimal Fibaro HC3 firmware version 5.111.48 (beta). 

     

    Thanks to the work of @petergebruers for finding out how the new Fibaro webSocket worked and what Tibber Live needed to get initialised, for authorisation and payload headers and what data is returned. Also thanks for @JcBorgs for testing all beta version and the great suggestions for improving the QuickApp. 

     

    This QuickApp gets your energy consumption and production data from Tibber Live and can be used in combination with the Tibber Monitor to get the Tibber Prices. 
     

    If the Tibber server disconnects the webSocket, the QuickApp wil do a re-connect for the amount in the QuickApp variable reconnect. If the re-connect fails for that amount, there will be a timeout for the seconds in the QuickApp variable timeout. 

     

    If you use Tibber for your Energy Panel, you can use this Tibber Live QuickApp for your energy consumption and production combined with the

    Please login or register to see this link.

    to provide the Energy Panel with the hourly prices. 

     

    You need a Tibber account to use this QuickApp, otherwise the Offline Simulation Mode or Online Test Mode is only available. 

     

    Edited by SmartHomeEddy
    • Like 3
    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • Posted (edited)

    Version 2 of the Tibber Live QuickApp is available for download. 

     

    Please login or register to see this attachment.

     

    • Added two child devices, Hourly Consumption and Hourly Production
    • Added re-connect routine to handleError. If an Tibber error occurs, the QuickApp will try to re-connect. Thanks @JcBorgs for testing. 
    • Improved routine to handle Tibber null values. Thanks @Darquan for testing. 
    • Changed labels a bit to save some space
    • Changed "volt" and "amp" text in the labels. Thanks @Morten22 for mentioning. 
    • Changed kWh device types from com.fibaro.electricMeter to com.fibaro.energyMeter

     

    Because there is a change in the child devices, best way is to install a new QuickApp. Check the settings of all the child devices for the Energy Panel direct after installing the new QuickApp!

     

     

     

    Edited by SmartHomeEddy
    • Thanks 1
    Link to comment
    Share on other sites

    • 0

    @SmartHomeEddy This last version is working stable and very well.

    Nice work!

     

    For your info I see that Tibber is making some improvements soon, so it may affect your setup. 

    Edited by dorten75
    • Thanks 1
    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • 31 minutes ago, dorten75 said:

    For your info I see that Tibber is making some improvements soon, so it may affect your setup. 


    Thanks @dorten75

     

    Did they give a forecast on the changes? 

    Link to comment
    Share on other sites

    • 0
    2 hours ago, SmartHomeEddy said:

    Did they give a forecast on the changes? 

    I`ll let you know.
    They are implementing prices from cabel owner into their prices, but not sure if that will effect your setup for pricing.

    I have now 0,52 nkr in the daytime pr kwh, and 0,42 nkr after 22.00 o`clock.
     

    Tibber have prices with and without tax today (it is a choice in the app to show the price with/without tax), but that is not included in your setup when pulling pricing from Tibber.

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • Posted (edited)

     

    8 hours ago, dorten75 said:

    They are implementing prices from cabel owner into their prices, ...

     

    Nice!

     

     

    8 hours ago, dorten75 said:

    Tibber have prices with and without tax today (it is a choice in the app to show the price with/without tax), but that is not included in your setup when pulling pricing from Tibber.

     

    What field would that be, with/without tax? The fields we get back from livemeasurement are:

     

    LiveMeasurement

    Field Argument Type Description
    timestamp

    Please login or register to see this link.

    !

    Timestamp when usage occurred

    power

    Please login or register to see this link.

    !

    Consumption at the moment (Watt)

    lastMeterConsumption

    Please login or register to see this link.

    Last meter active import register state (kWh)

    accumulatedConsumption

    Please login or register to see this link.

    !

    kWh consumed since midnight

    accumulatedProduction

    Please login or register to see this link.

    !

    net kWh produced since midnight

    accumulatedConsumptionLastHour

    Please login or register to see this link.

    !

    kWh consumed since since last hour shift

    accumulatedProductionLastHour

    Please login or register to see this link.

    !

    net kWh produced since last hour shift

    accumulatedCost

    Please login or register to see this link.

    Accumulated cost since midnight; requires active Tibber power deal

    accumulatedReward

    Please login or register to see this link.

    Accumulated reward since midnight; requires active Tibber power deal

    currency

    Please login or register to see this link.

    Currency of displayed cost; requires active Tibber power deal

    minPower

    Please login or register to see this link.

    !

    Min consumption since midnight (Watt)

    averagePower

    Please login or register to see this link.

    !

    Average consumption since midnight (Watt)

    maxPower

    Please login or register to see this link.

    !

    Peak consumption since midnight (Watt)

    powerProduction

    Please login or register to see this link.

    Net production (A-) at the moment (Watt)

    powerReactive

    Please login or register to see this link.

    Reactive consumption (Q+) at the moment (kVAr)

    powerProductionReactive

    Please login or register to see this link.

    Net reactive production (Q-) at the moment (kVAr)

    minPowerProduction

    Please login or register to see this link.

    Min net production since midnight (Watt)

    maxPowerProduction

    Please login or register to see this link.

    Max net production since midnight (Watt)

    lastMeterProduction

    Please login or register to see this link.

    Last meter active export register state (kWh)

    powerFactor

    Please login or register to see this link.

    Power factor (active power / apparent power)

    voltagePhase1

    Please login or register to see this link.

    Voltage on phase 1; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware.

    voltagePhase2

    Please login or register to see this link.

    Voltage on phase 2; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. Value is always null for single phase meters.

    voltagePhase3

    Please login or register to see this link.

    Voltage on phase 3; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. Value is always null for single phase meters.

    currentPhase1 ⚠️

    Please login or register to see this link.

    Current on phase 1; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware.

    ⚠️ DEPRECATED

    Replaced by currentL1.

    currentL1

    Please login or register to see this link.

    Current on L1; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware.

    currentPhase2 ⚠️

    Please login or register to see this link.

    Current on phase 2; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. Value is always null for single phase meters.

    ⚠️ DEPRECATED

    Replaced by currentL2.

    currentL2

    Please login or register to see this link.

    Current on L2; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. Value is always null for single phase meters.

    currentPhase3 ⚠️

    Please login or register to see this link.

    Current on phase 3; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. Value is always null for single phase meters.

    ⚠️ DEPRECATED

    Replaced by currentL3.

    currentL3

    Please login or register to see this link.

    Current on L3; on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. Value is always null for single phase meters.

    signalStrength

    Please login or register to see this link.

    Device signal strength (Pulse - dB; Watty - percent)

     

     

    Edited by SmartHomeEddy
    Link to comment
    Share on other sites

    • 0
    On 6/17/2022 at 12:06 AM, SmartHomeEddy said:

    This QuickApp gets your energy consumption and production data from Tibber Live. 
    This QuickApp can be used in combination with the Tibber Monitor to get the Tibber Prices. 
    Based on the Fibaro WebSockets/GraphQL demo by Peter Gebruers 

     

    If you use Tibber for your Energy Panel, you can use this Tibber Live QuickApp for your energy consumption and production combined with the Tibber Monitor QuickApp to provide the Energy Panel with the hourly prices. 

     

    Please login or register to see this link.

     

     

    Main device with positive or negative actual power consumption

     

    Child devices are available for:

    • power (Actual consumption with maxPower in log text)
    • powerProduction (Actual production with maxPowerProduction in log text)
    • accumulatedConsumption (Todays consumption, also the child device for the Energy Panel)
    • accumulatedProduction (Todays production)
    • accumulatedCost (Todays cost)
    • accumulatedConsumptionLastHour (Consumed since since last hour shift)
    • accumulatedProductionLastHour (Produced since last hour shift)
    • lastMeterConsumption (Total consumption)
    • lastMeterProduction (Total production)
    • voltagePhase1
    • voltagePhase2
    • voltagePhase3
    • currentL1
    • currentL2
    • currentL3

     

    Please login or register to see this attachment.

     

    Available information: 

    • power (Consumption at the moment (Watt))
    • maxPower (Peak consumption since midnight (Watt))
    • powerProduction (Net production (A-) at the moment (Watt))
    • maxPowerProduction (Max net production since midnight (Watt))
    • accumulatedConsumption (kWh consumed since midnight)
    • accumulatedProduction (net kWh produced since midnight)
    • accumulatedCost (Accumulated cost since midnight; requires active Tibber power deal)
    • currency (Currency of displayed cost; requires active Tibber power deal)
    • lastMeterConsumption (Last meter active import register state (kWh))
    • lastMeterProduction (Last meter active export register state (kWh))
    • voltagePhase1 (Voltage on phase 1) *
    • voltagePhase2 (Voltage on phase 2) *
    • voltagePhase3 (Voltage on phase 3) *
    • currentL1 (Current on L1) *
    • currentL2 (Current on L2) *
    • currentL3 (Current on L3) *
    • accumulatedConsumptionLastHour (kWh consumed since since last hour shift)
    • accumulatedProductionLastHour (net kWh produced since last hour shift)
    • accumulatedReward (Accumulated reward since midnight; requires active Tibber power deal)
    • minPower (Min consumption since midnight (Watt))
    • averagePower (Average consumption since midnight (Watt))
    • powerReactive (Reactive consumption (Q+) at the moment (kVAr)) *
    • powerProductionReactive (Net reactive production (Q-) at the moment (kVAr)) *
    • minPowerProduction (Min net production since midnight (Watt))
    • maxPowerProduction (Max net production since midnight (Watt))
    • powerFactor (Power factor (active power / apparent power)) *
    • signalStrength (Device signal strength (Pulse - dB; Watty - percent)) *
    • timestamp (Timestamp when usage occurred)

    * on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. In this QuickApp "null" values are replaced by their previous values. 

     

    To communicate with the API you need to acquire a OAuth access token and pass this along with every request passed to the server.
    A Personal Access Token give you access to your data and your data only. 
    This is ideal for DIY people that want to leverage the Tibber platform to extend the smartness of their home. 
    Such a token can be acquired here:

    Please login or register to see this link.

     

    When creating your access token or OAuth client you’ll be asked which scopes you want the access token to be associated with. 
    These scopes tells the API which data and operations the client is allowed to perform on the user’s behalf. 
    The scopes your app requires depend on the type of data it is trying to request. 
    If you for example need access to user information you add the USER scope. 
    If information about the user's homes is needed you add the appropriate HOME scopes.
    If you have more than one home in your subscription, you need to fill in your home number the change between your homes. 


    If the Tibber server disconnects the webSocket, the QuickApp wil do a re-connect for the amount in the QuickApp variable reconnect. 
    If the re-connect fails for that amount, there will be a timeout for the seconds in the QuickApp variable timeout. 

     

    Use this QuickApp at your own risk. You are responsible for ensuring that the information provided via this QuickApp do not contain errors. 
    Tibber is a registered trademark being the property of TIBBER. TIBBER reserves all rights to the registered trademarks.
    Information which is published on TIBBER’s websites belongs to TIBBER or is used with the permission of the rights holder. 
    Making of copies, presentations, distribution, display or any other transfer of the information on the website to the public is, except for strictly private use, prohibited unless done with the consent of TIBBER. 
    Published material on dedicated TIBBER press websites, intended for public use, is exempt from the consent requirement.
    Also see:

    Please login or register to see this link.

     

    Guide Communicating with the Tibber API:

    Please login or register to see this link.


    Tibber API Explorer:

    Please login or register to see this link.


    Fibaro webSocket manual:

    Please login or register to see this link.


    Fibaro Forum Headers in webSocket:

    Please login or register to see this link.


    WebSocket++ Documentation:

    Please login or register to see this link.


    GraphQL query language:

    Please login or register to see this link.

     

    Version 2.0 (5th August 2022)

    • Added two child devices, Hourly Consumption and Hourly Production
    • Added re-connect routine to handleError. If an Tibber error occurs, the QuickApp will try to re-connect. Thanks @JcBorgs for testing. 
    • Improved routine to handle Tibber null values. Thanks @Darquan for testing. 
    • Changed labels a bit to save some space
    • Changed "volt" and "amp" text in the labels. Thanks @Morten22 for mentioning. 
    • Changed kWh device types from com.fibaro.electricMeter to com.fibaro.energyMeter

    Version 1.0 (19th June 2022)

    • Initial webSocket version Tibber Live
    • Thanks @JcBorgs for testing all beta versions and great suggestion to improve the quickapp
    • Based on the Fibaro WebSockets/GraphQL demo by @petergebruers


    Variables (mandatory and created automatically): 

    • token = Authorization token (see the Tibber website: https://developer.tibber.com)

    • homeId = Tibber Home ID (see the Tibber website: https://developer.tibber.com)

    • reconnect = Amount of re-connects after disconnect from Tibber server (default = 10)

    • timeout = Pause after maximum amount of re-connects (default = 300)

    • debugLevel = Number (1=some, 2=few, 3=all, 4=Offline Simulation Mode, 5=Live Test Mode) (default = 1)

     

    Fibaro Firmware:

    Minimal version 5.111.48 (beta)

     

    Download the QuickApp here (download the file and un-zip):

    Please login or register to see this link.

    or from the Fibaro Marketplace:

    Please login or register to see this link.


    How to install: 

    1. Open the Configuration Interface
    2. Go to Settings > Devices
    3. Click  +
    4. Choose Other Device
    5. Choose Upload File
    6. Choose file from your computer with .fqa

     

     

     

     

     

     

    On 6/17/2022 at 12:06 AM, SmartHomeEddy said:

    This QuickApp gets your energy consumption and production data from Tibber Live. 
    This QuickApp can be used in combination with the Tibber Monitor to get the Tibber Prices. 
    Based on the Fibaro WebSockets/GraphQL demo by Peter Gebruers 

     

    If you use Tibber for your Energy Panel, you can use this Tibber Live QuickApp for your energy consumption and production combined with the Tibber Monitor QuickApp to provide the Energy Panel with the hourly prices. 

     

    Please login or register to see this link.

     

     

    Main device with positive or negative actual power consumption

     

    Child devices are available for:

    • power (Actual consumption with maxPower in log text)
    • powerProduction (Actual production with maxPowerProduction in log text)
    • accumulatedConsumption (Todays consumption, also the child device for the Energy Panel)
    • accumulatedProduction (Todays production)
    • accumulatedCost (Todays cost)
    • accumulatedConsumptionLastHour (Consumed since since last hour shift)
    • accumulatedProductionLastHour (Produced since last hour shift)
    • lastMeterConsumption (Total consumption)
    • lastMeterProduction (Total production)
    • voltagePhase1
    • voltagePhase2
    • voltagePhase3
    • currentL1
    • currentL2
    • currentL3

     

    Please login or register to see this attachment.

     

    Available information: 

    • power (Consumption at the moment (Watt))
    • maxPower (Peak consumption since midnight (Watt))
    • powerProduction (Net production (A-) at the moment (Watt))
    • maxPowerProduction (Max net production since midnight (Watt))
    • accumulatedConsumption (kWh consumed since midnight)
    • accumulatedProduction (net kWh produced since midnight)
    • accumulatedCost (Accumulated cost since midnight; requires active Tibber power deal)
    • currency (Currency of displayed cost; requires active Tibber power deal)
    • lastMeterConsumption (Last meter active import register state (kWh))
    • lastMeterProduction (Last meter active export register state (kWh))
    • voltagePhase1 (Voltage on phase 1) *
    • voltagePhase2 (Voltage on phase 2) *
    • voltagePhase3 (Voltage on phase 3) *
    • currentL1 (Current on L1) *
    • currentL2 (Current on L2) *
    • currentL3 (Current on L3) *
    • accumulatedConsumptionLastHour (kWh consumed since since last hour shift)
    • accumulatedProductionLastHour (net kWh produced since last hour shift)
    • accumulatedReward (Accumulated reward since midnight; requires active Tibber power deal)
    • minPower (Min consumption since midnight (Watt))
    • averagePower (Average consumption since midnight (Watt))
    • powerReactive (Reactive consumption (Q+) at the moment (kVAr)) *
    • powerProductionReactive (Net reactive production (Q-) at the moment (kVAr)) *
    • minPowerProduction (Min net production since midnight (Watt))
    • maxPowerProduction (Max net production since midnight (Watt))
    • powerFactor (Power factor (active power / apparent power)) *
    • signalStrength (Device signal strength (Pulse - dB; Watty - percent)) *
    • timestamp (Timestamp when usage occurred)

    * on Kaifa and Aidon meters the value is not part of every HAN data frame therefore the value is null at timestamps with second value other than 0, 10, 20, 30, 40, 50. There can be other deviations based on concrete meter firmware. In this QuickApp "null" values are replaced by their previous values. 

     

    To communicate with the API you need to acquire a OAuth access token and pass this along with every request passed to the server.
    A Personal Access Token give you access to your data and your data only. 
    This is ideal for DIY people that want to leverage the Tibber platform to extend the smartness of their home. 
    Such a token can be acquired here:

    Please login or register to see this link.

     

    When creating your access token or OAuth client you’ll be asked which scopes you want the access token to be associated with. 
    These scopes tells the API which data and operations the client is allowed to perform on the user’s behalf. 
    The scopes your app requires depend on the type of data it is trying to request. 
    If you for example need access to user information you add the USER scope. 
    If information about the user's homes is needed you add the appropriate HOME scopes.
    If you have more than one home in your subscription, you need to fill in your home number the change between your homes. 


    If the Tibber server disconnects the webSocket, the QuickApp wil do a re-connect for the amount in the QuickApp variable reconnect. 
    If the re-connect fails for that amount, there will be a timeout for the seconds in the QuickApp variable timeout. 

     

    Use this QuickApp at your own risk. You are responsible for ensuring that the information provided via this QuickApp do not contain errors. 
    Tibber is a registered trademark being the property of TIBBER. TIBBER reserves all rights to the registered trademarks.
    Information which is published on TIBBER’s websites belongs to TIBBER or is used with the permission of the rights holder. 
    Making of copies, presentations, distribution, display or any other transfer of the information on the website to the public is, except for strictly private use, prohibited unless done with the consent of TIBBER. 
    Published material on dedicated TIBBER press websites, intended for public use, is exempt from the consent requirement.
    Also see:

    Please login or register to see this link.

     

    Guide Communicating with the Tibber API:

    Please login or register to see this link.


    Tibber API Explorer:

    Please login or register to see this link.


    Fibaro webSocket manual:

    Please login or register to see this link.


    Fibaro Forum Headers in webSocket:

    Please login or register to see this link.


    WebSocket++ Documentation:

    Please login or register to see this link.


    GraphQL query language:

    Please login or register to see this link.

     

    Version 2.0 (5th August 2022)

    • Added two child devices, Hourly Consumption and Hourly Production
    • Added re-connect routine to handleError. If an Tibber error occurs, the QuickApp will try to re-connect. Thanks @JcBorgs for testing. 
    • Improved routine to handle Tibber null values. Thanks @Darquan for testing. 
    • Changed labels a bit to save some space
    • Changed "volt" and "amp" text in the labels. Thanks @Morten22 for mentioning. 
    • Changed kWh device types from com.fibaro.electricMeter to com.fibaro.energyMeter

    Version 1.0 (19th June 2022)

    • Initial webSocket version Tibber Live
    • Thanks @JcBorgs for testing all beta versions and great suggestion to improve the quickapp
    • Based on the Fibaro WebSockets/GraphQL demo by @petergebruers


    Variables (mandatory and created automatically): 

    • token = Authorization token (see the Tibber website: https://developer.tibber.com)

    • homeId = Tibber Home ID (see the Tibber website: https://developer.tibber.com)

    • reconnect = Amount of re-connects after disconnect from Tibber server (default = 10)

    • timeout = Pause after maximum amount of re-connects (default = 300)

    • debugLevel = Number (1=some, 2=few, 3=all, 4=Offline Simulation Mode, 5=Live Test Mode) (default = 1)

     

    Fibaro Firmware:

    Minimal version 5.111.48 (beta)

     

    Download the QuickApp here (download the file and un-zip):

    Please login or register to see this link.

    or from the Fibaro Marketplace:

    Please login or register to see this link.


    How to install: 

    1. Open the Configuration Interface
    2. Go to Settings > Devices
    3. Click  +
    4. Choose Other Device
    5. Choose Upload File
    6. Choose file from your computer with .fqa

     

     

     

     

     

    Values shown on Tibber live changes about every 2 seconds between '0' to the 'actual value' shown in the Tibber app for Voltage and Ampere on all 3 fases. 

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • 10 minutes ago, Patrick75 said:

    Values shown on Tibber live changes about every 2 seconds between '0' to the 'actual value' shown in the Tibber app for Voltage and Ampere on all 3 fases. 

     

    Hi @Patrick75

     

    Do you mean that is an issue, or is it for information only?

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • Ah, thanks

     

    Since the new firmware supporting WebSockets I can do some testing too. This is what I see, every 10 seconds an update of the values, from one value the the other value: 

     

    (I hope the video works) 

    Please login or register to see this spoiler.

     

    Link to comment
    Share on other sites

    • 0
    1 hour ago, SmartHomeEddy said:

    Ah, thanks

     

    Since the new firmware supporting WebSockets I can do some testing too. This is what I see, every 10 seconds an update of the values, from one value the the other value: 

     

    (I hope the video works) 

    Please login or register to see this spoiler.

     

    Link to comment
    Share on other sites

    • 0
    13 minutes ago, Patrick75 said:

     

    Correct

     

    12 minutes ago, SmartHomeEddy said:

    thanks Patrick. Does this only show on Voltage L1, L2 and L3 and Ampere L1, not Ampere L2 and L3 ?

    correct

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • Apparently Tibber returns a zero value for those devices.

     

    I could prevent the zero value to show in the QuickApp. That is already happening for null and nil values. For the Voltage devices, that preventing a zero value to show could be ok, because a change from 230 Volt to zero Volt is not to be expected. But the Ampere devices could return to zero if there is no consumption on that phase.  

    Link to comment
    Share on other sites

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Answer this question...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

     Share

    ×
    ×
    • Create New...