From 381d3593d18064b198487ef84b41afb6481c29e4 Mon Sep 17 00:00:00 2001 From: Aaron Bach Date: Sun, 31 Jul 2022 05:18:08 -0600 Subject: [PATCH] Fix incorrect event data keys in SimpliSafe docs (#23586) --- source/_integrations/simplisafe.markdown | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/source/_integrations/simplisafe.markdown b/source/_integrations/simplisafe.markdown index c53b1655d10..7b2fddb84a3 100644 --- a/source/_integrations/simplisafe.markdown +++ b/source/_integrations/simplisafe.markdown @@ -95,14 +95,14 @@ Set one or more system properties. web and mobile apps. When received, they come with event data that contains the following keys: -* `changed_by`: the PIN that triggered the event (if appropriate) -* `event_type`: the type of event -* `info`: a human-friendly string describing the event in more detail -* `sensor_name`: the sensor that triggered the event (if appropriate) -* `sensor_serial`: the serial number of the sensor that triggered the event (if appropriate) -* `sensor_type`: the type of sensor that triggered the event (if appropriate) +* `last_event_changed_by`: the PIN that triggered the event (if appropriate) +* `last_event_type`: the type of event +* `last_event_info`: a human-friendly string describing the event in more detail +* `last_event_sensor_name`: the sensor that triggered the event (if appropriate) +* `last_event_sensor_serial`: the serial number of the sensor that triggered the event (if appropriate) +* `last_event_sensor_type`: the type of sensor that triggered the event (if appropriate) * `system_id`: the system ID to which the event belongs -* `timestamp`: the UTC datetime at which the event was received +* `last_event_timestamp`: the UTC datetime at which the event was received For example, when someone rings the doorbell, a `SIMPLISAFE_EVENT` event will fire with the following event data: