Replies: 1 comment
-
Hi Ulf, the timing logic is simply random. between >0 and ~2 minutes after the full hour. The idea behind is that we had an issue that Tibber blocked the adapter users because >2000 users with same client calling the server at the same time had been qualified as DDoS attack. Please send a pm to the e-mail noted in adapter documentation. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hallo,
Thanks for developing this ioBroker integration. Very helpful and much appreciated!
What is the logic for the timing of the state actualization during a new hour. I see that this is obviously always some 1 or 2 minutes after the new hour, but always different...?! It would be better if this would happen more "predictable" directly after the new hour (maybe 30 seconds)...
Is there any chance to have a direct MS Teams call to discuss some more "observations" with the tibberlink. It would be helpful to share some insides on my use cases and "findings"... Difficult to describe here... Thanks!
Beta Was this translation helpful? Give feedback.
All reactions