Connection timeout & Unexpected server response: 504

[libertyx82]

Hi,

after i have Updatet the Module to Version 6.1.0 i got a high amount of Connection Timeouts (Connection timed out after 70000 ms.) and Unexpected server response: 504 or 502. on the Tibber-Feet (Puls)

I have only one Instance for the Puls Feed.

[tollaner]

Same Problem here

[libertyx82]

I am a little bit further, i get that Timeouts also with the Version 6.0.4 so i guess it is a problem on the API side.

[pittbull]

Got the same errors and talking to support they are having no issues and are pointing back to this nodered app. The API explorer at their site repsonds with the correct data so most likely there's been changes to the API.

[libertyx82]

They always say it's not their fault

Regarding to the bad Performance of the APP and the thing that only the Puls feed is affected, i would say the problem is on their side.

And the API changes should only take effect to the query

[pittbull]

I just refer to the customer service representative. I have no way of knowing whichever solution is at fault. What I do know is that this has worked perfectly for many years, and now all of a sudden is failing with these errors (I've also seen some 502 errors):

25 Oct 09:34:04 - [info] [tibber-feed:Get live data] Connecting...
25 Oct 09:34:04 - [info] [tibber-feed:Get live data] Connecting: {"timeout":4743,"retryBackoff":3743}
25 Oct 09:34:04 - [error] [tibber-feed:Get live data] Unexpected server response: 504
25 Oct 09:34:04 - [info] [tibber-feed:Get live data] Disconnected: "Disconnected from Tibber feed."
25 Oct 09:34:05 - [info] [tibber-feed:Get live data] Can connect: false. Last retry: 1729841644796. With backoff for: 3743 ms.
25 Oct 09:34:06 - [info] [tibber-feed:Get live data] Can connect: true. Last retry: 1729841646796. With backoff for: 3992 ms.
25 Oct 09:34:06 - [info] [tibber-feed:Get live data] Connecting...
25 Oct 09:34:06 - [info] [tibber-feed:Get live data] Connecting: {"timeout":4992,"retryBackoff":3992}
25 Oct 09:34:07 - [error] [tibber-feed:Get live data] Unexpected server response: 504
25 Oct 09:34:07 - [info] [tibber-feed:Get live data] Disconnected: "Disconnected from Tibber feed."
25 Oct 09:34:07 - [info] [tibber-feed:Get live data] Can connect: false. Last retry: 1729841646796. With backoff for: 3992 ms.
25 Oct 09:34:08 - [info] [tibber-feed:Get live data] Can connect: true. Last retry: 1729841648798. With backoff for: 3310 ms.
25 Oct 09:34:08 - [info] [tibber-feed:Get live data] Connecting...
25 Oct 09:34:08 - [info] [tibber-feed:Get live data] Connecting: {"timeout":4310,"retryBackoff":3310}
25 Oct 09:34:08 - [error] [tibber-feed:Get live data] Unexpected server response: 504
25 Oct 09:34:08 - [info] [tibber-feed:Get live data] Disconnected: "Disconnected from Tibber feed."
25 Oct 09:34:09 - [info] [tibber-feed:Get live data] Can connect: false. Last retry: 1729841648798. With backoff for: 3310 ms.
25 Oct 09:34:10 - [info] [tibber-feed:Get live data] Can connect: false. Last retry: 1729841648798. With backoff for: 3310 ms.
25 Oct 09:34:11 - [info] [tibber-feed:Get live data] Can connect: false. Last retry: 1729841648798. With backoff for: 3310 ms.
25 Oct 09:34:11 - [error] [tibber-feed:Get live data] Unexpected server response: 504
25 Oct 09:34:11 - [info] [tibber-feed:Get live data] Disconnected: "Disconnected from Tibber feed."
25 Oct 09:34:12 - [info] [tibber-feed:Get live data] Can connect: true. Last retry: 1729841652798. With backoff for: 3439 ms.
25 Oct 09:34:12 - [info] [tibber-feed:Get live data] Connecting...
25 Oct 09:34:12 - [info] [tibber-feed:Get live data] Connecting: {"timeout":4439,"retryBackoff":3439}
25 Oct 09:34:13 - [info] [tibber-feed:Get live data] Can connect: false. Last retry: 1729841652798. With backoff for: 1315 ms.
25 Oct 09:34:14 - [info] [tibber-feed:Get live data] Can connect: true. Last retry: 1729841654799. With backoff for: 2077 ms.
25 Oct 09:34:14 - [info] [tibber-feed:Get live data] Connecting...
25 Oct 09:34:14 - [info] [tibber-feed:Get live data] Connecting: {"timeout":3077,"retryBackoff":2077}
25 Oct 09:34:15 - [error] [tibber-feed:Get live data] Unexpected server response: 504

[gulli1986]

Exact same errors here, as been working fine for years so suspect something is wrong or new on Tibber's side.

[gulli1986]

The "Get Live Data" now reports connecting. Not able to connect in other words.. Was working this morning (with errors above)

[pittbull]

It's been fluctuating on my side, between connected, connecting and disconnected without any apparent reason. I am also seeing 429 - rate limiting - likely due to excessive retries from my client.

Edit: Confirming that the client is not connecting at all. No error message from api just endlessly trying to connect. I have also restarted the dialog with Tibber support. Since there has been no change in the code, something must've changed somewhere else.

[libertyx82]

On my side it is working currently without errors and reconnects.

That the errors only are occurring sporadically, is also the reason why i am guessing that it is an Problem on API side.

[pittbull]

On my side it is working currently without errors and reconnects.

That the errors only are occurring sporadically, is also the reason why i am guessing that it is an Problem on API side.

What version are you on. I am currently on 6.1.0.

And how can I downgrade when running Nodered in docker.

[libertyx82]

Yesterday i have downgraded to 6.0.4 but got the same error´s and reconnects as with 6.1.0

[pittbull]

But now it suddenly works?

[libertyx82]

currently, but i also get the errors with the version 6.0.4

[pittbull]

Reconnected now and had a stable connection for the last 5 minutes.

[tollaner]

now it´s working fine here for the last 3 hours and still stable connected

[libertyx82]

Over the Weekend it works fine, since this morning the timeouts and reconnects are back

[tollaner]

Exactly the same here...

[belowm]

Last retry: 1729841646796. With backoff for: 3992 ms.

Without looking into the sources, Last retry and backoff indicate that there is some means of re-connecting implemented when the websocket connection is lost. But this doesn't seem to work.