The flexibility of the DeepHub® allows for granular control and management of timeout settings for fences:

  • timeout: the timeout in milliseconds after which a location should expire and trigger a fence exit event (if no more location updates are sent). Must be a positive number or -1 in case of an infinite timeout.
  • tolerance_timeout: the timeout in milliseconds after which a location outside of a fence, but still within exit_tolerance distance to that fence, should trigger a fence exit event. If not set, or null, the timeout will be equal to the fence timeout. If tolerance_timeout is greater than the fence timeout, the tolerance_timeout will be reduced to the fence timeout. The provided number must be positive or -1 in case of an infinite tolerance_timeout.
  • exit_delay: The delay in milliseconds in which an imminent exit event should wait for another location update. The provided number must be positive or -1 in case of an infinite exit_delay.


The timeout settings defined for a fence can be overridden by defining corresponding properties for a trackable as well. These properties for trackables are the following: 

  • fence_timeout 
  • tolerance_timeout
  • exit_delay


Furthermore, the timeout settings of a trackable can be overridden by defining corresponding properties for a location provider of that trackable. The properties have the same name and meaning as for a trackable. 


Note: tolerance_timeout is also relevant for collision events, as it defines the timeout in milliseconds after which a collision outside of an obstacle but still within exit_tolerance distance should release from a collision event.


For more information, refer to the DeepHub® API.