search

bisand / node-red-contrib-tibber-api

Node Red module for integrating with Tibber api
MIT License
20 stars 2 forks source link

Problem using tibber node #70

Closed fsamuelsson closed 1 year ago

fsamuelsson commented 1 year ago

I have a problem using the tibber feed node since today i get the following error

An error ocurred while trying to check if real time consumption is enabled. {"code":"ERR_INVALID_PROTOCOL"}

I know tibber made som echanges in their API recently ? is the plugin updated to support the new API functions. I have upgraded the node to the latest version.

bisand commented 1 year ago

Hi,

It sounds like you could be using an outdated version.

Which version are you using? Can you doubble check the query url you have configured?

The latest version (v5.1.4) uses the query url to retrieve the websocket url for the feed, so that should not fail. It would be nice if you could report back with your findings.

Thanks!

fsamuelsson commented 1 year ago

Hi !

I am using the latest version

@. @.

Nodes trying to connect but then I get An error ocurred while trying to check if real time consumption is enabled. {"code":"ERR_INVALID_PROTOCOL"}

Från: André Syvertsen Biseth @.> Skickat: Thursday, 12 January 2023 18:34 Till: bisand/node-red-contrib-tibber-api @.> Kopia: Fredrik Samuelsson @.>; Author @.> Ämne: Re: [bisand/node-red-contrib-tibber-api] Problem using tibber node (Issue #70)

Hi,

It sounds like you could be using an outdated version.

Which version are you using? Can you doubble check the query url you have configured?

The latest version (v5.1.4) uses the query url to retrieve the websocket url for the feed, so that should not fail. It would be nice if you could report back with your findings.

Thanks!

— Reply to this email directly, view it on GitHubhttps://github.com/bisand/node-red-contrib-tibber-api/issues/70#issuecomment-1380765897, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOSSGVBBOZHTKDFROSTOKX3WSA6BHANCNFSM6AAAAAATZKHF6M. You are receiving this because you authored the thread.Message ID: @.**@.>>

bisand commented 1 year ago

I was able to reproduce the issue. It seems like you have wrong URI registered in your configuration node. Could it be the old, deprecated web socket URI (wss://api.tibber.com/v1-beta/gql/subscriptions). The new change from Tibber only require the GraphQL Endpoint URI which currently is: https://api.tibber.com/v1-beta/gql like the screenshot below:

image

The error response in the screenshot was returned when I specified wss:// instead of https://

A small bug in the node requires you to restart Node-Red URI change. I will as soon as possible release a fix for that. Meanwhile, provide correct URI and restart Node-Red.

Hope this solves your problem.

bisand commented 1 year ago

Leaving this open until the fix is confirmed..

fsamuelsson commented 1 year ago

Confirmed after restart of node-red , node connects to Tibber api .

Thanx

Från: André Syvertsen Biseth @.> Skickat: Thursday, 12 January 2023 21:59 Till: bisand/node-red-contrib-tibber-api @.> Kopia: Fredrik Samuelsson @.>; Author @.> Ämne: Re: [bisand/node-red-contrib-tibber-api] Problem using tibber node (Issue #70)

Leaving this open until the fix is confirmed..

— Reply to this email directly, view it on GitHubhttps://github.com/bisand/node-red-contrib-tibber-api/issues/70#issuecomment-1380987539, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOSSGVCYX25JGF7JZVQMYQ3WSBWDBANCNFSM6AAAAAATZKHF6M. You are receiving this because you authored the thread.Message ID: @.***>