I set the inactivity time to 60000 ms and the inactivity period to 300000 ms. The first event occurred 7 minutes and 48 seconds after the device sent the last message (it should have occurred after 1 minute) However, repeated events appear exactly every 15 minutes, and according to the configuration they should occur every 5 minutes...
From what I noticed, it doesn't matter whether we set the repeat period to 60000 or 300000, the event is every 15 minutes.
Is there something I don't understand, or is it a bug, or maybe some minimum time is enforced and lower values are ignored?
This would make some sense to prevent pointless settings such as 1 ms
And if so, is there a configuration parameter for these values?
For repeating events, there is basically no point in setting it less than 15 minutes anyway. However, for the first event it would be useful in some cases.
Thanks, everything is clear.
By the way with a stable device and frequent sending of messages, setting a shorter time for events would be a way to immediately jamming notification - combined with the calendar and geofence, it would be perfect.
I set the inactivity time to 60000 ms and the inactivity period to 300000 ms. The first event occurred 7 minutes and 48 seconds after the device sent the last message (it should have occurred after 1 minute) However, repeated events appear exactly every 15 minutes, and according to the configuration they should occur every 5 minutes...
From what I noticed, it doesn't matter whether we set the repeat period to 60000 or 300000, the event is every 15 minutes.
Is there something I don't understand, or is it a bug, or maybe some minimum time is enforced and lower values are ignored?
This would make some sense to prevent pointless settings such as 1 ms
And if so, is there a configuration parameter for these values?
For repeating events, there is basically no point in setting it less than 15 minutes anyway. However, for the first event it would be useful in some cases.