Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
user:notify:trigger [22/12/2018 12:40]
tagr WH-725
user:notify:trigger [17/06/2019 09:54] (current)
mary [Connection loss] WH-1352
Line 72: Line 72:
   - __No coordinates__. There are also cases when all sensors are active and their values are known, but it is impossible to locate the unit (for example, someone has covered the GPS aerial).   - __No coordinates__. There are also cases when all sensors are active and their values are known, but it is impossible to locate the unit (for example, someone has covered the GPS aerial).
  
-Set the loss time of data/​coordinates (in minutes), after which the notification should trigger. ​+Set the loss time of data/​coordinates (in minutes), after which the notification should trigger. This time interval must not exceed 2880 minutes (2 days).
  
 Using the //​Geofences//​ option, you can monitor connection loss in regards to specific [[user/​geo/​geo|geofences]] or [[user/​geo/​groups|groups of geofences]]. Specify the control type: trigger inside or outside a geofence. Select the resource whose geofences should be shown in the list (select //All available// to view the geofences of all available resources). Select the geofences or groups of geofences (shown in the square brackets), for which this notification should work.  Using the //​Geofences//​ option, you can monitor connection loss in regards to specific [[user/​geo/​geo|geofences]] or [[user/​geo/​groups|groups of geofences]]. Specify the control type: trigger inside or outside a geofence. Select the resource whose geofences should be shown in the list (select //All available// to view the geofences of all available resources). Select the geofences or groups of geofences (shown in the square brackets), for which this notification should work. 
Line 152: Line 152:
 =====Driver===== =====Driver=====
  
-Choose control ​type: [[user/​drivers/​drivers|driver]] ​assignment ​or driver reset. To control both activities, two notifications ​of different types will be requiredUsing this notification you can control all drivers (*) or just some of them — input driver's name (or codemask. +Choose ​whether you want to control ​the assignment of the [[user/​drivers/​drivers|driver]] or its removal. To control both, create ​two notifications. ​To specify a particular ​driver, enter the code (or code [[user/​gui/​masks#​name_mask|mask]]) in the //Driver code// field. You can add multiple masks separated by commas without spaces. If you leave an asterisk (*) in this field, all drivers will be monitored without exception.
  
 {{ :​notify:​trigger_driver.png?​nolink }} {{ :​notify:​trigger_driver.png?​nolink }}
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2019 Gurtam