Hi,

no i wrote a VB.NET app to query the API in the end

thanks for the follow up

Gareth

Hello Gareth,

Thank you for your post, please provide following details -

MobiControl version -

Manufacturer -

Device Enrollment type - Android Plus/Android Enterprise/iOS/DEP iOS

Regards,

Hi,

MobiControl version - 15.1.0.3416

Manufacturer - Honeywell

Device Enrollment Type - Android Enterprise

Thanks

Gareth

Hi Gareth,

How many devices are there?  Are they all in the same device group?

How many depot(s) are there?

Do the devices have GPS turned on when they are powered on?   Do the GPS hardware reliably get the GPS location (e.g. due to weak GPS signal level if the depot  is  indoor/underground, etc.)  when the devicess are back at their depot?  Will the device get cionnected to  known Wifi access point (i.e. with known SSID/BSSID/mac address) when it is back at thte depot?

Hi,

90 devices.

5 depots each with its own group with relevant devices attached to the group.

They all have GPS turned on when powered on, and they have a good GPS signal at base

when they are back at the depot the connect to a known Wifi SSID

thanks

Gareth

Hi Gareth,

After reading the above comments, it seems like the internet connection of the devices changes from cellular to WiFi when they reach the depots. Is that right?

If this is the case, then we can work on getting it done using scripts. Please confirm.

Regards,

Hi,

yes thats correct.

thanks

Gareth

Hi Gareth,

If you have sufficient prigramming skills, I believe what you need can be implemented using various MobiControl REST api calls in your preferred development language/environment.

Otherwise,  I believe you should be able to achieve similar results by configuring a combination of  fiile-sync, data-collection and alert rules on your MobiControl web-console.  These have to be repeated for each of the five groups of devices, assuming each group of devices has a different known SSID/BSSID of the Wifi Access Point in the corresponding depot.  BTW, will the device be turned off before 9 p.m. if it's already back to the depot well before 9 p.m.?  Also, will there be any time allowance for any device time-mismatch and or server schuduling/processing delay (e.g. the device still count as already back to depot by 9:03pm or 9:05 pm)? 

Hi,

im not sure using the rest API is an option at present

The SSID is the same for each site.

The devices are never turned off, only put on charge.

The 9pm cut off already includes a tolerance in it so should cover any processing delays etc.

thanks

Gareth

Please elaborate what you meant when you said the 9pm cut-off already includes a tolerance.  What is the amount of tolerance (in terms of time window) are you talking about or expecting?  Is that only a target in your requirement or something implemented by something other than the MobiCnontrol server?

Hi,

Its more that we would expect all the vehicles back by 7pm, but in case some are late etc. we have set to 9pm

thanks

Gareth

Hi,

i have looked at the API details an beleive i can get this working. which call would you recomment for this?

we can set up Geo Locations, and when the device enters the location it will create a log entry?

which API should i call to retrieve this?

thanks

Gareth

Hi Gareth,

I will outline what I would do using MobiControl rules rather than API's, but I have to admit I haven't actually tried them out myself recently on any MobiControl server to confirm that the whole thing works.  You have to repeat the following for each of your five groups  The target is to make the alert  rule in (4) only applicable to the device of interest near 9 pm every day.

(1) For device group DG#,  create a child group ,say DG#/DG#_9pm, which will inherit all the MDM profiles/rules/advanced-configurations of the parent group DG by default.

(2) Add a file-sync rule FS#_1 to ALWAYS (i.e. overwrite even if the file exist in the destination) download a small dummy file from your MobiControl server to a selected directory (say %sdcard%/Download of the device.  Add seven weekly file-sync schedules (at 9:00 pm), one for each day of a week. Target this FS rule to DG#. 

(3) Add an alert rule AR#_1 targeted to DG# with action to relocate the device from DG# to DG#/DG#_9pm when file has been synced to the device.

(4) Add an alert rule AR#_2 targeted to DG#/DG#_9pm to generate an email-alert when the Wifi SSID is not equal to the expected value for the group #.  Make sure you add the action to  relocate the device from DG#/DG#_9pm back to DG#.

If the above results in more than one alert emails generated on the same day, you might need to leave out the relocation action in (4). and add the following two rules instead. 

(4b) Add a file-sync rule FS#_2  to ALWAYS (i.e. overwrite even if the file exist in the destination) download a small dummy file from your MobiControl server to a selected directory (say %sdcard%/Download of the device.  Add seven weekly file-sync schedules (at 9:15 pm), one for each day of a week. Target this FS rule to DG#/DG#_9pm.

(4c) Add an alert rule AR#_3 targeted to DG#/DG#_9pm with action to relocate the device from DG#/DG#_9pm back to DG# when file has been synced to the device. 

Hi Gareth,

Did you get a chance to try the steps provided by Raymond Chan on the above comment? If it helped you, please mark it as "is solution", so others may benefit from this information.
If not, please raise a support case(click here) or call SOTI Support team(click here) to assist you better? We shall either get it done either by generating reports based on Location services or by creating Device Relocation rule.

Regards,