Tibber sensor for future price (tomorrow)

droidgren · March 21, 2023, 3:13pm

I can’t find it in tibber_data , what is that sensor called?

Zinken · March 21, 2023, 5:20pm

sensor.energy_price_***
ending with my home address. In the attributes of that sensor is both today and tomorrow prices.

droidgren · March 21, 2023, 6:45pm

But that’s not from Tibber data, that’s from the regular integration. Does it contain future data?

Zinken · March 21, 2023, 7:08pm

No I mean the one from tibber data, names are similar but not the same. The first one in this print screen is from core integration but the bottom one is from tibber data, that one has future prices as attribute.

droidgren · March 21, 2023, 7:17pm

Weird, I dont have those. Is it this integration you are using? Mine are called tibber_data and not tibber data.

Zinken · March 21, 2023, 7:31pm

Yes, that’s the one. I believe they will show up only when adding this part (for optional extra sensors):

tibber_data:
  email: Your email registered at Tibber
  password: Your Tibber password

droidgren · March 22, 2023, 10:03am

Now I got the sensors but with no values in them

Are you supposed to use quotes arround email and password like this?

tibber_data:
  email: "Your email registered at Tibber"
  password: "Your Tibber password"

Zinken · March 22, 2023, 10:26am

I don’t know really but I don’t have quotes in my configuration.yaml for either email or password.
Maybe it just takes some time for it to fetch the data. I don’t know how often it updates.

droidgren · March 22, 2023, 10:40am

Good point. I will give it a day.

droidgren · March 23, 2023, 9:05am

Still no data, I give up

EdwardTFN · March 23, 2023, 1:09pm

A while ago I also got some issues to get future data, so I’ve created my own RESTful sensor to fetch this info directly from Tibber and they work quite fine.
Feel free to copy it:

github.com

edwardtfn/HomeAssistant-Config/blob/f198a7c250faf0f80e0d981bbe549f9286523ef8/packages/electricity/tibber.yaml

#PriceLevel
#Price level based on trailing price average (3 days for hourly values and 30 days for daily values)
# NORMAL: The price is greater than 90 % and smaller than 115 % compared to average price.
# CHEAP: The price is greater than 60 % and smaller or equal to 90 % compared to average price.
# VERY_CHEAP: The price is smaller or equal to 60 % compared to average price.
# EXPENSIVE: The price is greater or equal to 115 % and smaller than 140 % compared to average price.
# VERY_EXPENSIVE: The price is greater or equal to 140 % compared to average price.

sensor:
  # https://community.home-assistant.io/t/tibber-sensor-for-future-price-tomorrow/253818/23
  - name: Tibber Electricity Price
    platform: rest
    resource: https://api.tibber.com/v1-beta/gql
    method: POST
    scan_interval: 900
    payload: '{ "query": "{ viewer { homes { currentSubscription { priceInfo { current { total currency level energy tax } today { total startsAt level } tomorrow { total startsAt level }}}}}}" }'
    json_attributes_path: "$.data.viewer.homes[0].currentSubscription.priceInfo"
    json_attributes:
      - current
      - today

This file has been truncated. show original

EdwardTFN · March 23, 2023, 1:11pm

And this the card I’m using on my dashboards:

Jovana · June 7, 2023, 9:18pm

Nice dashboard. But for some reason, the numbers are not correct. I take your code and take it whitout any adjustments. View below the results numbers on the right side. (Both examples are from this page).

And this is the data sensor data:

I think it is the setting of the decimal, but changing it does not give the solution.

Any ideas about what will go wrong?

Thanks!

BerriJ · July 18, 2023, 6:05pm

I just posted my solution for creating a tibber price graph (including future) over here: Tibber - Schedul prices upcoming 24 hours prices! - #58 by BerriJ.

FSHelgeland · August 21, 2023, 8:58pm

I totally lost track here.
Do I have to make an extra template sensor?

And from Tibber I got a sensor that shows me:

state_class: measurement
today: 0.2169, 0.2025, 0.1998, 0.1976, 0.2004, 0.2246, 0.2448, 0.2559, 0.3155, 0.2583, 0.259, 0.2576, 0.2574, 0.2561, 0.2546, 0.2541, 0.254, 0.2541, 0.2536, 0.2529, 0.2516, 0.2517, 0.2462, 0.2306
raw_today:

time: ‘2023-08-21T00:00:00.000+02:00’
total: 0.2169
etc etc

tomorrow_valid: true
tomorrow: 0.2324, 0.2261, 0.2172, 0.217, 0.2241, 0.2286, 0.2416, 0.2477, 0.2564, 0.2558, 0.2638, 0.2568, 0.2562, 0.2566, 0.2555, 0.2532, 0.2552, 0.2534, 0.2494, 0.2491, 0.2489, 0.2493, 0.2506, 0.2448
raw_tomorrow:

time: ‘2023-08-22T00:00:00.000+02:00’
total: 0.2324

etc etc
unit_of_measurement: NOK/kWh

And I got another sensor that shows me

state_class: measurement

app_nickname: Hjemme
grid_company: ********
estimated_annual_consumption: ******
price_level: NORMAL
max_price: 0.316
avg_price: 0.244
min_price: 0.198
off_peak_1: 0.218
peak: 0.261
off_peak_2: 0.245
unit_of_measurement: NOK/kWh
icon: mdi:currency-usd
friendly_name: Electricity price Hjemme

And which sensor to use for consumption? Accumulated current hour or accumulated consumption (day)

mahoromax · December 19, 2023, 8:02pm

About that Apex Chart:
Any way to make it show 2 decimals in the price?
The axes descriptions have them but when I hover on a graph I only get a single decimal and the price basically moves within by 0.1-0.3 at max…

Edit: Found it (after trying with tooltip options and original JS doc):
add float_precision: 2 to every series that shall be presented with 2 decimals

Berry00 · January 18, 2024, 1:04pm

Hi all,
i followed the Steps, but the “Sensor” won’t show up. What have i done wrong?

Solved!!
Edit: Noob Error: It has to be put under sensor:

Berry00 · January 26, 2024, 8:41am

How do i fix the tooltip to be also 2 oder 3 deciamals instead of 1?

Edit:
Solved it again by myself by adding flating precision, see here:

Isengo1989 · October 15, 2024, 11:02am

Thx @Berry00 - any idea how to fix the float in X axis ?

anmarcel · October 21, 2024, 4:03pm

Hey everbody,

I need your help. Can someone write me the sensor template which pulls only the max and min prices of today (and tomorrow if available) an store each of the for values in an separate sensor entitiy.

Tibber allows to pull these values via rest, but unfortunately, I cannot get it running.

Alternatively, how can I extract these values from the attributes of a sensor entitiy?

Thanks Marcel