No TibberFeed connection (multiple homes but only one Pulse?)

[arichter83]

Describe the bug
I try to get the Pulse data into iobroker, but get No TibberFeed connected.

Screenshots & Logfiles ... tibberlink.0 | 2023-08-20 21:43:27.855 | debug | No TibberFeed connected try reconnecting now in 6sec interval! tibberlink.0 | 2023-08-20 21:43:27.840 | debug | No TibberFeed connected try reconnecting now in 6sec interval! tibberlink.0 | 2023-08-20 21:43:21.854 | debug | No TibberFeed connected try reconnecting now in 6sec interval! tibberlink.0 | 2023-08-20 21:43:21.840 | debug | No TibberFeed connected try reconnecting now in 6sec interval! tibberlink.0 | 2023-08-20 21:43:15.854 | warn | Feed was disconnected. I try to reconnect in 6s tibberlink.0 | 2023-08-20 21:43:15.852 | debug | Tibber Feed: Disconnected from Tibber feed. tibberlink.0 | 2023-08-20 21:43:15.837 | warn | Feed was disconnected. I try to reconnect in 6s tibberlink.0 | 2023-08-20 21:43:15.833 | debug | Tibber Feed: Disconnected from Tibber feed. tibberlink.0 | 2023-08-20 21:42:15.834 | debug | Tibber Feed: Connected to Tibber feed. tibberlink.0 | 2023-08-20 21:42:15.822 | debug | Tibber Feed: Connected to Tibber feed. tibberlink.0 | 2023-08-20 21:42:14.948 | debug | Got prices tomorrow from tibber api: [] tibberlink.0 | 2023-08-20 21:42:14.788 | debug | Got prices today from tibber api: [] tibberlink.0 | 2023-08-20 21:42:14.576 | debug | Got current price from tibber api: {}

Versions:

• Adapter version: 0.1.9
  • JS-Controller version: 4.0.24
  • Node version: v18.17.1
  • Operating system: raspberry pi

Additional context
I have two houses set up in tibber, only one has Pulse installed. I can not delete the other house in the tibber app, so I can not try if that is the reason.

[hombach]

There is still an issue about getting Pulse data from multiple homes, but you also don't get any price data - are you sure your Tibber API is correct? Is there a Homes folder - or 2 in your case been built up by the adapter? Is e.g. Address filled with correct data? - so there has been positive connect between Adapter and Tibber Server...

[Marty56]

I have a similar bug, showing more entries in the log file. After this bug, timber.connect does not reconnect again. Bug is occurring in Tibber Connect Version 0.2.

I would change the lable of this issue form question to bug.

2023-09-10 11:12:08.158 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
--
2023-09-10 11:12:09.721 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:12:09.725 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:12:12.139 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:12:12.141 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:12:17.225 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:12:17.227 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:12:27.709 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:12:27.711 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:12:48.657 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:12:48.660 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:13:46.237 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:13:46.240 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:14:56.154 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:14:56.157 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:18:42.683 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:18:42.697 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:25:35.720 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:25:35.722 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 11:42:26.288 - error: tibberlink.0 (2649364) ERROR on Tibber-Feed: [object Object]
2023-09-10 11:42:26.290 - warn: tibberlink.0 (2649364) A feed was disconnected. I try to reconnect in 6s
2023-09-10 12:00:14.853 - error: tibberlink.0 (2649364) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-09-10 12:00:14.854 - error: tibberlink.0 (2649364) unhandled promise rejection: undefined
2023-09-10 12:00:14.854 - error: tibberlink.0 (2649364) undefined
2023-09-10 12:00:14.953 - error: tibberlink.0 (2649364) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-09-10 12:00:14.954 - error: tibberlink.0 (2649364) unhandled promise rejection: undefined
2023-09-10 12:00:14.954 - error: tibberlink.0 (2649364) undefined
2023-09-10 12:00:14.964 - warn: tibberlink.0 (2649364) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-09-10 12:00:15.559 - error: host.iobrokerstable Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-09-10 12:00:15.566 - error: host.iobrokerstable Caught by controller[1]: {
2023-09-10 12:00:15.566 - error: host.iobrokerstable Caught by controller[1]: responseMessage: '\r\n' +
2023-09-10 12:00:15.566 - error: host.iobrokerstable Caught by controller[1]: '\r\n' +
2023-09-10 12:00:15.566 - error: host.iobrokerstable Caught by controller[1]: '\r\n' +
2023-09-10 12:00:15.566 - error: host.iobrokerstable Caught by controller[1]: '504 Gateway Time-out\r\n' +
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[1]: '\r\n' +
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[1]: '\r\n',
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[1]: httpCode: 504,
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[1]: statusCode: 504,
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[1]: statusMessage: 'Gateway Time-out'
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[1]: }
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[3]: {
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[3]: responseMessage: '\r\n' +
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[3]: '\r\n' +
2023-09-10 12:00:15.567 - error: host.iobrokerstable Caught by controller[3]: '\r\n' +
2023-09-10 12:00:15.568 - error: host.iobrokerstable Caught by controller[3]: '504 Gateway Time-out\r\n' +
2023-09-10 12:00:15.568 - error: host.iobrokerstable Caught by controller[3]: '\r\n' +
2023-09-10 12:00:15.568 - error: host.iobrokerstable Caught by controller[3]: '\r\n',
2023-09-10 12:00:15.568 - error: host.iobrokerstable Caught by controller[3]: httpCode: 504,
2023-09-10 12:00:15.568 - error: host.iobrokerstable Caught by controller[3]: statusCode: 504,
2023-09-10 12:00:15.568 - error: host.iobrokerstable Caught by controller[3]: statusMessage: 'Gateway Time-out'
2023-09-10 12:00:15.568 - error: host.iobrokerstable Caught by controller[3]: }
2023-09-10 12:00:15.568 - error: host.iobrokerstable instance system.adapter.tibberlink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-09-10 12:00:29.771 - error: tibberlink.0 (2703236) Error (Gateway Time-out) occured during: -fetching homes from Tibber API- :
2023-09-10 12:00:29.786 - warn: tibberlink.0 (2703236) Got no homes in your account - probably by a Tibber Server Error- adapter restarts in 2 minutes
2023-09-10 12:02:29.788 - warn: tibberlink.0 (2703236) Restart initiated
2023-09-10 12:02:38.513 - warn: tibberlink.0 (2703332) skipping feed of live data - no Pulse configured for this home according to Tibber server

[hombach]

This morning "Tibber Server was down" for some hours. They had problems with Pulse Updates. I also had confusing errors. Which version did you use this morning? -> But TibberLink tried to solve.... second last line "Restart initiated"

Version 0.3.0 is Work in Process for multiple homes

[hombach]

Describe the bug I try to get the Pulse data into iobroker, but get No TibberFeed connected.

• Adapter version: 0.1.9
• JS-Controller version: 4.0.24
• Node version: v18.17.1
• Operating system: raspberry pi

Additional context I have two houses set up in tibber, only one has Pulse installed. I can not delete the other house in the tibber app, so I can not try if that is the reason.

With TibberLink 0.3.0 - available in some hours in "latest" repository - you have the option to choose only the one home with Pulse installed to get the live data feed .... would be nice to have a test with this version... ;)

[hombach]

looks like solution starting with 0.3.0 is working - see #41

[hombach]

@arichter83 : is it working with >=0.3.2 in latest repo?

[hombach]

@arichter83 : 0.3.2 now in stable repository