Tibber.com API call - help with authorization.

Avatar
  • updated

Hi.

I'm trying to reach my electricity company through their public API.

I'm able to use the POST field in the command to get a response but a layer of authorization is required.


Is anyone able to point me in the right direction on how to incorporate the authorization token in my call?

This call gives me a response (from their examples)

call:

{
"query": "{ viewer { name }}"
}

response:

{"data":null,"errors":[{"message":"No valid access token in request","locations":[{"line":1,"column":3}],"path":["viewer"],"extensions":{"code":"INTERNAL_SERVER_ERROR"}}]}


Documentation:

https://developer.tibber.com/docs/guides/calling-api


Any help is appreciated

Avatar
Joachim O

Hi. Sorry for my late answer. I'm not any closer to resolve this issue. I was hoping that the dev team would pick up on this post and get WSS to work.

The data not received from the HAN port i was able to get from their API. Hourly price etc was OK. Stopped working after a while for some reason and I haven't done anything more with it.

Avatar
Joachim O
Quote from Geir Hardt

Hi Joachim

I am struggling with the same issue. 

Have you found a way to set up bOS to receive the power datastream from Tibber?


Until now I have worked around this by using a Raspberry PI to read and convert HAN Data, before writing a subset of the data to bOS with RPC. However, more information is available from Tibber (accumulated cost, hourly price etc) than through the HAN ports, which makes me prefer the Tibber subscription stream data,  (could of course set up the PI to read the datastream, and forward to bOS using RPC, but I would like to get rid of the extra components).

Anyone have had some success with the Tibber live measurement through WSS (Web Socket Subscription)?


@Geir? @Comfortclick?


With the current electricity prices this is more relevant than ever.🤯