TeslaMateAgile.PriceHelper Tibber fail about teslamateagile HOT 5 CLOSED

Hello! Looking at your first example there I plugged those exact same dates into my query and ran it and it seemed to return 4 as expected on my end:

I am however using their demo token. It's possible maybe you have an incorrect / expired Tibber API token or that they were having issues at this time.

If you go to the Tibber API explorer and put in the following query you can try it yourself with your own token: https://developer.tibber.com/explorer

{
  viewer {
    homes {
      id
      currentSubscription {
        priceInfo {
          range(
            resolution: HOURLY
            after: "MjAyNC0wNS0yMFQxMDowNzowMC4wMDAwMDAwKzAwOjAw"
            first: 4
          ) {
            nodes {
              total
              startsAt
            }
          }
          current {
            total
            startsAt
            level
          }
        }
      }
    }
  }
}

You can see here at least with the demo token it is working as expected:

Hope this helps 🙂

from teslamateagile.

Hi Matt,

I used your query and got only one entry with my token but 4 with the demo token.

I will now inquire about the error with Tibber support, as instead of the 4 values, only one value is being output with the personal token.

from teslamateagile.

Weird! I'm very curious to see what Tibber's support say about this, keep me posted!

from teslamateagile.

I've got an answer from Tibber support. The API returns only one key because the contract is not started yet. They said as soon as the contract starts it should return the whole data. I will have a look then again.

Maybe they can return charging cost soon because they changed to smart charging 2.0 feature.

from teslamateagile.

Interesting, good to know thanks for the update!

from teslamateagile.