I have this same problem! I have cloud data set to 'On Change' but it sends out information every 10 secs. Also the timestamp is wrong. I am in Australia and its always 10hrs ahead of time. I have the correct time zone set within the logo so it doesn't make sense to me.

I was expecting to only receive data when the state of the bits I'm watching change. It is annoying as I will have to write something at the other end to filter it out of the log, as well as add in the correct timestamp.

If anyone has solved this I would very much appreciate the solution!

Cheers, Simon.

Did anyone find out any information on this (or maybe a solution)?  I have the exact same problem.  Setting the Period to 5 minutes in the cloud data transfer settings jut results in 29 empty JSON packets (just timestamp) being sent every 10s, followed by 1 packet with data in it.  The empty JSON packets are a nuisance.

Some time ago I asked the support the same question. The answer was more or less the timestamp message send all 10s, is a LOGO! feature which can’t be changed.

In LOGO! manual the feature is documented:

„BM publishes LOGO! time data value every 10 seconds.“

Just asking if any solution has been found?

This is a pity. All the great work done for Logo/AWS integration is strongly disturbed by this hardcoded 10s interval.

Cost increase is huge compared to running only the necessary communication, which in many cases is way longer interval or even only on change.