Replies: 2 comments 1 reply
-
I have the exact same issue. Already changed the Token multiple times. My graphql query through a function is working like a charme, but the tibber node is always in state connecting. But used to work a couple of weeks ago. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Check if NodeRed's log on the server. If it works in the Tibber's API explorer, it should also work with NodeRed. And just in case, double check that you have enabled the live meassurement in your subscription. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using the tibber-feed but I cant get a proper connection. It does always just show "connecting":
![image](https://user-images.githubusercontent.com/743342/235782257-3bda8d30-c9b4-4b52-8a7d-35ef81b1bc7c.png)
In the log I can see:
If I use the Demo-Token & Demo-Home it works though. And I can execute other requests with "tibber-data" successfully with my personal token, so it seems only the websocket subscription seems to fail. On the other hand I can see the liveMeasurements in the Api Explorer...
Any idea why that is and how to fix it?
Regards
Michael
Beta Was this translation helpful? Give feedback.
All reactions