loaddevice

Returns consumer's devices data.

Command's fields description:

  • txtUser1 field is the “username” of MyWakes account.

  • txtUser2 field is the “password” of MyWakes account.

  • txtCommand field contains the command: “loaddevice”.

  • txtFormat optional field specifies txtParameters and response formats. more info.

  • txtParameter field contains a structure like this:

<?xml version="1.0" encoding="utf-8" ?> 
<loaddevice>
	<consumer>44</consumer>
	<time>20101025183000</time> 
</loaddevice>
{
  "loaddevice": {
    "consumer": "44",
    "time": "20101025183000"
  }
}

 

Where

  • <consumer> mandatory. The Consumer's Id to read devices data linked to.

  • <time> mandatory, date and time in UTC. The accepted format is “yyyyMMddhhmmss”.

  • txtProvider field must contain the application calling ID and generated characters.

  • txtSignature field must contain the signature based on the string made of “Command Name” + “consumer” + “time” + “generated character to 32”.

Looking at the previous example, the string on which calculate the check will be:
“loaddevice4420101025183000xxxxxx”


Therefore the txtProvider field will be:
“76a865d4-fab8-51cd-ba78-2da325f6955axxxxxx”

Returns a structure like the following:

<?xml version="1.0" encoding="utf-8" ?> 
<furesult> 
	<message><![CDATA[ OK ]]></message>
	<sms>25</sms>
	<devices>
		<device>
			<id>44</id>
			<type>30</type>
			<expiration>20141231000000</expiration>
			<imei>123456789012345</imei>
			<tel>+393351234567</tel>
			<password>0000</password>
			<servermode>1</servermode>
			<apn>apn.carrier.com</apn>
			<apnuser />
			<apnpassword />
			<intervalmode>1</intervalmode>
			<interval>300</interval>
			<geolat1>44.15</geolat1>
			<geolon1>11.3275</geolon1>
			<georadius1>1000</georadius1>
			<gpsmode>1</gpsmode>
			<tracktype>0</tracktype>
			<radar>1</radar>
			<battery>60</battery>
		</device>
	</devices>
</furesult>
{
  "furesult": {
    "message": " OK ",
    "sms": "25",
    "devices": {
      "device": {
        "id": "44",
        "type": "30",
        "expiration": "20141231000000",
        "imei": "123456789012345",
        "tel": "+393351234567",
        "password": "0000",
        "servermode": "1",
        "apn": "apn.carrier.com",
        "intervalmode": "1",
        "interval": "300",
        "geolat1": "44.15",
        "geolon1": "11.3275",
        "georadius1": "1000",
        "gpsmode": "1",
        "tracktype": "0",
        "radar": "1",
        "battery": "60"
      }
    }
  }
}

 

Where

  • <message> contains OK or Error description
  • <sms> user's number of SMS left
  • <devices> the collection of consumer's devices. Each consumer should have linked only one device. If more than one device is linked to a consumer you should point out this anomaly.
    • <device> this tag encloses each device data
      • <id> device Id
      • <type> device type, can have one of the following value:
        • 1 = TK102-2
        • 2 = TK102
        • 4 = TK203
        • 5 = TK201-2
        • 6 = TK201
        • 7 = XT107
        • 20 = IFD6000
        • 21 = IFD-NET
        • 30 = Daggy
        • 40 = Angelo
      • <expiration> service expiration date
      • <imei> device's IMEI code
      • <tel> SIM's telephone number
      • <password> device password
      • <servermode> connection mode to My Wakes platform, can be:
        • 0 (zero) not connected
        • 1 (one) connected do My Wakes platform
      • <apn> APN address of the SIM into the device
      • <apnuser> APN user name
      • <apnpassword> APN password
      • <intervalmode> timing sampling mode, can be:
        • 0 (zero) disabled
        • 1 (one) enabled
      • <interval> sampling interval in seconds
      • <sendinterval> permit to group more sampling into one packet
      • <geolat1> virtual fence latitude in degree and decimal degrees. If the position is in the southern hemisphere the value will be negative so it will be preceded by a minus sign. If virtual fence is a circle this value is the latitude of the center of the circle, otherwise the top left of the area.
      • <geolon1> virtual fence longitude in degree and decimal degrees. If the position is in the western hemisphere the value will be negative so it will be preceded by a minus sign. If virtual fence is a circle this value is the latitude of the center of the circle, otherwise the top left of the area.
      • <georadius1> virtual fence radius in meters.
      • <geolat2> virtual fence latitude in degree and decimal degrees. If the position is in the southern hemisphere the value will be negative so it will be preceded by a minus sign. It is the latitude of the bottom right of the area.
      • <geolon2> virtual fence longitude in degree and decimal degrees. If the position is in the western hemisphere the value will be negative so it will be preceded by a minus sign. It is the latitude of the bottom right of the area.
      • <gpsmode> GPS mode, can be:
        • 0 (zero) disabled
        • 1 (one) enabled
      • <phone1> first telephone number
      • <phone2> second telephone number
      • <phone3> third telephone number
      • <centerphone> phone number to sent SMS and fences alarms to
      • <tracktype> tracking mode, can be:
        • -1 (minus one) no track is recorded
        • 0 (zero) – if track is private and still visible only to the track owner.
        • 1 (one) – if the track will be published to a page that has to be shown to friends
        • 2 (two) – if the track can be published in a common page where all public tracks are visible to everybody
      • <radar> consumer's position update mode:
        • 0 (zero) the device will not update the consumer's position
        • 1 (one) the device will update the consumer's position
      • <battery> battery's charge percentage

If MyWakes server returns an error, the format of this answer is described in the error section.

Terms Of Use | Privacy Statement | Company info
  • © Cedac Sistemi srl
  • Head office: Via Toscana, 3 40035 Castiglione dei Pepoli (Italy) Tel.: +39 0534-93811 Fax: +39 0534-93899
  • Branch office: Via del Lavoro, 47 40033 Casalecchio di Reno (Italy)
  • Branch office: Via Parini, 1 40033 Casalecchio di Reno (Italy)
  • Share capital Euro 26,000.00 - Company Register of Bologna / VAT no / fiscal code 01695261204