get_last

To retrieve the current state of an active event or the last known state of a completed event, use the events/get_last method.

Unlike events/get, this method doesn’t require events to be loaded into the session and doesn’t return event history.

svc=events/get_last&params={
  "itemId": <long>,
  "type": <text>,
  "filter1": <long>,
  "filter2": <text>,
  "detalization": <uint>,
  "measure": <uint>,
  "lang": <text>
}

The request can contain the following parameters:

If the request is completed successfully, the response contains an object keyed by detector type. Otherwise, an error code is returned.

The data structure inside each key depends on the detector and the requested flags.

With the 0x1 flag, the trips and counters detectors return their data directly, in the following structure. Other detectors group event objects by a detector-specific ID, as shown in the examples.

{
  "<detector_type>": {
    "from": {
      "t": <uint>,
      "y": <double>,
      "x": <double>
    },
    "to": {
      "t": <uint>,
      "y": <double>,
      "x": <double>
    },
    "m": <uint>,
    "f": <uint>
  }
}

For a private position, the x and y values are returned as 0.

The other flags return the same data as the corresponding flags of events/check_updates: detector-specific data (0x2), parameters of the message associated with the event (0x4), additional detail data (0x8), detailed message data (0x10), and formatted values (0x20). For the resource_drivers detector, the returned fields are described in the example below.

The following examples show how to retrieve event states for different use cases.

To retrieve the state of all available detectors for a unit, specify only the unit ID:

svc=events/get_last&params={
  "itemId": <unit_id>
}

The response is an object keyed by each available detector type:

{
  "<detector_type>": {
    "...": "..."
  }
}

To retrieve the fuel level state for all fuel level sensors of a unit, specify the unit ID and the fuel_level detector. Use detalization 39 (0x27) to include basic event data, detector-specific data, message parameters, and formatted values:

svc=events/get_last&params={
  "itemId": <unit_id>,
  "type": "fuel_level",
  "filter1": 0,
  "filter2": "",
  "detalization": 39
}

The response is grouped by sensor ID. With detalization 39 (0x27), it can contain the following fields:

{
  "fuel_level": {
    "<sensor_id>": {
      "from": {
        "t": <uint>,
        "y": <double>,
        "x": <double>
      },
      "to": {
        "t": <uint>,
        "y": <double>,
        "x": <double>
      },
      "m": <uint>,
      "f": <uint>,
      "value": <double>,
      "raw_value": <double>,
      "filled": <double>,
      "timeDiff": <uint>,
      "latDiff": <double>,
      "lonDiff": <double>,
      "format": {
        "value": <text>,
        "raw_value": <text>,
        "filled": <text>,
        "theft": <text>,
        "custom_value": <text>
      }
    }
  }
}

To retrieve the current state of driver assignments, specify the resource ID and the resource_drivers detector. Set filter1 to a driver ID to get the state of one driver, or 0 for all drivers. The detalization value 7 (0x7) returns basic event data, detector-specific data, and parameters from the message associated with the event.

svc=events/get_last&params={
  "itemId": <resource_id>,
  "type": "resource_drivers",
  "filter1": 0,
  "filter2": "",
  "detalization": 7
}

The response is grouped by driver ID. Each driver ID has one object that describes the current state of that driver.

{
  "resource_drivers": {
    "<driver_id>": {
      "from": {
        "t": <uint>,
        "y": <double>,
        "x": <double>
      },
      "to": {
        "t": <uint>,
        "y": <double>,
        "x": <double>
      },
      "m": <uint>,
      "f": <uint>,
      "state": <uint>,
      "aflags": <uint>,
      "unit_id": <long>,
      "real_time_from": <uint>,
      "validate_sensor_id": <uint>,
      "switched_to": <long>
    }
  }
}

The from, to, m, and f fields are described in the common structure. The detector also returns the following fields:

The aflags field can contain the following flags. The same flags are used in the completed events returned by events/get, so a current state usually contains only the flags that describe how the assignment started.

For state 0, the to object doesn’t show the time and place of the unassignment. It shows the last processed message. The unassignment time is the end time of the completed event in the event history, which you can retrieve with events/get.