GET /system/date-time
This resource is used to view or edit the device's date, time, and timezone.
Used when you are operating a browser without access to the header parameter. This allows you to choose which encoding you want to use for the response:
All these resources can be used according what the resource allows.
If this parameter is not in the request, the Application/Json will be chosen by default.
There are multiple possible values (according the resource):
The first two are the most often used.
This query parameter is used to choose the date format :
Object Name: DateTime
| Property Name | Type | Description | Method |
|---|---|---|---|
| Time | empty | This is the controller clock’s time. The value is represented by the hours, minutes, and seconds all separated by ':'. These three values are essential for the time property. Format : HH : mm : ss | GET POST |
| Date | empty | This indicates the current date of the controller. The value is represented by the month, the day and the year all separated with '-'. These three values need to be present for the date property. Format : MM-dd-yyyy | GET POST |
| TimeZone | empty | This indicates the time zone the controller is located in. The value need to be one in the list below : - Etc/GMT+12 - Etc/GMT+11 - Pacific/Honolulu - America/Anchorage - America/Santa_Isabel - America/Los_Angeles - America/Phoenix - America/Chihuahua - America/Denver - America/Guatemala - America/Chicago - America/Mexico_City - America/Regina - America/Bogota - America/New_York - America/Indianapolis - America/Caracas - America/Asuncion - America/Halifax - America/Cuiaba - America/La_Paz - America/Santiago - America/St_Johns - America/Sao_Paulo - America/Buenos_Aires - America/Cayenne - America/Godthab - America/Montevideo - America/Bahia - Etc/GMT+2 - Atlantic/Azores - Atlantic/Cape_Verde - Africa/Casablanca - Etc/GMT - Europe/London - Atlantic/Reykjavik - Europe/Berlin - Europe/Budapest - Europe/Paris - Europe/Warsaw - Africa/Lagos - Africa/Windhoek - Asia/Amman - Europe/Bucharest - Asia/Beirut - Africa/Cairo - Asia/Damascus - Africa/Johannesburg - Europe/Kiev - Europe/Istanbul - Asia/Jerusalem - Europe/Kaliningrad - Africa/Tripoli - Asia/Baghdad - Asia/Riyadh - Europe/Minsk - Europe/Moscow - Africa/Nairobi - Asia/Tehran - Asia/Dubai - Asia/Baku - Europe/Samara - Indian/Mauritius - Asia/Tbilisi - Asia/Yerevan - Asia/Kabul - Asia/Tashkent - Asia/Yekaterinburg - Asia/Karachi - Asia/Calcutta - Asia/Colombo - Asia/Katmandu - Asia/Almaty - Asia/Dhaka - Asia/Novosibirsk - Asia/Rangoon - Asia/Bangkok - Asia/Krasnoyarsk - Asia/Shanghai - Asia/Irkutsk - Asia/Singapore - Australia/Perth - Asia/Taipei - Asia/Ulaanbaatar - Asia/Tokyo - Asia/Seoul - Asia/Yakutsk - Australia/Adelaide - Australia/Darwin - Australia/Brisbane - Australia/Sydney - Pacific/Port_Moresby - Australia/Hobart - Asia/Magadan - Asia/Vladivostok - Asia/Srednekolymsk - Pacific/Guadalcanal - Asia/Kamchatka - Pacific/Auckland - Etc/GMT-12 - Pacific/Fiji - Pacific/Tongatapu - Pacific/Apia - Pacific/Kiritimati |
GET POST |
| ISODateTime | empty | This is the time, date and timezone according to the ISO8601 standard. This property can't be combine with other property except with the timezone. The dateTime send will be apply to match the device's timeZone. If a 'Z' is send instead of the timeZone value, it will be like +00:00. Format : yyyy-MM-dd'T'HH : mm : ssZ (Java annotation) Example: Initial State : Device's TimeZone : Europe/Paris Device's Time : 12:00:00 Device's Date : 01-01-2016 Request : {"ISODateTime":"2016-01-15T12:00:00-05:00"} Result : Device's TimeZone : Europe/Paris Device's Time : 18:00:00 Device's Date : 01-15-2016 |
POST |
URL Example: https://0.0.0.0/api/rest/v1/system/date-time
{
"date": "03-10-2016",
"timeZone": "America/New_York",
"time": "17:20:33"
}
URL Example: https://0.0.0.0/api/rest/v1/system/date-time
<?xml version="1.0" encoding="utf-8"?>
<DateTime>
<Date>03-10-2016</Date>
<Time>17:20:40</Time>
<TimeZone>America/New_York</TimeZone>
</DateTime>