jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-09 18:36:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix incorrect event data keys in SimpliSafe docs (#23586)

Browse Source
This commit is contained in:
Aaron Bach 2022-07-31 05:18:08 -06:00 committed by GitHub
parent 0b438681f7
commit 381d3593d1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
source/_integrations/simplisafe.markdown
View File

@ -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: