Receiving_Credential_and_Schedule_Information_from_the_Hosted_Server

Receiving Credential and Schedule Information from the Hosted Server

When a device is first commissioned using the Mobile Application (MAPP), the device WiFi update cycle is set to the default of once every 24 hours (typically between midnight and 4 am). The update (download) cycle frequency is always on a 24 hour cycle and cannot be changed.

It is possible to change the time at which the update cycle occurs. For example; if you want the update to run at midnight, you can set it to midnight. But, if you want to run a special update, say at 2 pm in the afternoon to get some new information, you can run it at 2 pm. But, remember, the cycle frequency is every 24 hours, so the next cycle update will not be at midnight, but at 2 pm the next day.

If you want to change it back to midnight, you can do that by resetting the cycle time to midnight and rerunning it again at midnight. The cycle default is still every 24 hours.

Once a device is commissioned, it is ready to receive credential and schedule information from the hosted server. If there are new credentials set for devices, or schedules are added or changed, that information is transmitted to devices from the hosted server during the periodic scheduled WiFi update cycle once every 24 hours.

Example:

Next Database Download Time - dbDwnLdTm. This JSON device parameter can command a specific time for the device to request a download. This is a “one Time” command and will not change the download frequency from a 24 hour frequency.

In this snippet of Download JSON, the download time is set for "20190612152000" = 2019/06/12 15:20.

"config": {
  "wifiDwnldRtyTmIntv": 5
},
"dbDwnLdTm": "20190612152000",
"nxtDbVerTS": "0x0000000000100000"
}

Once this scheduled download has taken place, the interval still remains at 24 hours, but the time of day has been modified to be 24 hours from the commanded download.

From the returned device config file the next scheduled db download time is set to 24 hours after the last DB download, which in this example is: "20190613152000" = 2019/06/13/ 15:20.

Response:

JSON Config file returned from the device to the server, confirming that the download time has been changed:

"rtcTime": "20190612152009",

"dbDwnldTm": "20190613152000",