You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,8 @@ In this version, I have made some changes from the older version. Mainly the plu
52
52
"name": "Kitchen Temperature",
53
53
"type": "temperaturesensor",
54
54
"device_id": "<<device id>>",
55
-
"event_name": "tvalue"
55
+
"event_name": "tvalue",
56
+
"split_character": ":"
56
57
}
57
58
]
58
59
}
@@ -70,3 +71,10 @@ The `devices` array contains all the accessories. You can see the accessory obje
70
71
-**event_name** - The name of the event to listen for sensor value update. This is only valid if the accessory is a sensor (i.e. currently `temperaturesensor` or `humiditysensor`). The plugin listens for events published from a Particle Device (using `Particle.publish`). The device firmware should publish the sensor values as a raw number.
71
72
-**function_name** - The name of the particle function that will be called when an action is triggered via HomeKit. If there is no function provided, the default `power` will be used. This is only valid if the accessory is an actor (i.e. `lightbulb` or `switchaccessory`).
72
73
74
+
**Particle Event Data Format**
75
+
-------------------------------------
76
+
By default it expects the event data as "key=value".
77
+
```
78
+
Particle.publish("tvalue", "temperature=20.7")
79
+
```
80
+
In order to parse JSON format, a custom `split_character` can be configured.
0 commit comments