Do not access cloud services at fixed timestamps

[mcm1957]

Describe the bug

Tibber cloud service seems to be accessed at fixed timestampes defined by crontab. This will lead to high load peaks at the cloud service as all ioBorker installations will use the service at almost the same time. Cloud provide might block access from ioBroker to avoid this - thus breaking the adapter for all users.

Please use random timestamps, i.e. randomizing cron entry, by delaying the access several minutes, ...

Expected behavior
Access should net be performed at almost the same time by hardcoded crontab or timestamp values.

Versions:

• Adapter version: 1.8.1 (and older)
• JS-Controller version: n/a
• Node version: n/a
• Operating system: n/a

Additional context
Please add this fix for the next release you plan to release as stable.

[hombach]

I hope Tibber has much more traffic - so that the 1000 accessing machine don't really count, - BUT this is a very good idea!!

[hombach]

implemented for 2.0

[mcm1957]

Thanks. In regards to your comment abot 1000 Users. We ('ioBroker') had already more than once feedback from cloud providers and even blocking measurements caused by to high load peaks. So @Apollon77 and I try to catch all possible adapters and try to convince devs to randomize the access even if the adapter is curently only used by few people. We want to avoid any situation where services are overloaded or cloud providers explicitly prohibit usage of their service for non own applications.

Thanks for implementing a randomization.

mcm1957

[hombach]

Hi Martin, good to know that already blocking issues have happened. Hopefully I'm not too "pseudo random" by using math.random. I don't know what seed is used in node.js to start the algorythm....

[hombach]

2.0.0 released for latest (beta) repository