search

bisand / node-red-contrib-tibber-api

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

How to handle multiple Pulse P1 devices on a single API key? #49

Closed mountaindude closed 2 years ago

mountaindude commented 2 years ago

I have a case here with two homes, each with a Pulse P1 meter. Both configured from a single Tibber account.

The warning for the tibber-feed is pretty clear:

Note! There should be only one instance running of tibber-feed per API key. Doing otherwise may return unpredictable result, or even error responses from the API.

But given my situation - any ideas on how to get streaming data for both P1 devices?

Would running two Node-RED instances solve it? Or is the limitation that there should only be one receiver of streaming data per API key - across all clients? Or is the only solution to have two separate accounts?

Sungtroll commented 2 years ago

I stream multiple accounts for the moment 4 different tibber accounts with no problems, different homeid and token. Has run it like that since last year. I never tried same token with user account that have more than one homes / timber pulse.

From: Göran Sander @.> Sent: Monday, November 22, 2021 7:50:51 PM To: bisand/node-red-contrib-tibber-api @.> Cc: Subscribed @.***> Subject: [bisand/node-red-contrib-tibber-api] How to handle multiple Pulse P1 devices on a single API key? (Issue #49)

I have a case here with two homes, each with a Pulse P1 meter. Both configured from a single Tibber account.

The warning for the tibber-feed is pretty clear:

Note! There should be only one instance running of tibber-feed per API key. Doing otherwise may return unpredictable result, or even error responses from the API.

But given my situation - any ideas on how to get streaming data for both P1 devices?

Would running two Node-RED instances solve it? Or is the limitation that there should only be one receiver of streaming data per API key - across all clients? Or is the only solution to have two separate accounts?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/bisand/node-red-contrib-tibber-api/issues/49, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJBWBPSCWPLOJPNCMGKH5RTUNKGIXANCNFSM5IRW2LWQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

mountaindude commented 2 years ago

Right, so it's different accounts then. Probably the safest solution.

Sungtroll commented 2 years ago

I use them in different flow. You can try with one account same token but different homeid. If something goes wrong you can see it in node-red command window as to many connections or something like that.

mountaindude commented 2 years ago

Mmm looks like it actually works having a couple of feed instances in NR using the same API key but different house IDs. Have gotten a single timeout, I can live with that. Will test this for some days before going to separate accounts.