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: docs/messages/pointset.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ while the `pointset` typing is applied as part of the [message envelope](envelop
44
44
45
45
*`points`: Collection of point names.
46
46
*_{`point_name`}_: Point name.
47
-
*`present_value`: The specific point data reading.
47
+
*`present_value`: The specific point data reading. If the value represents a number, then this must be serialized as a JSON number, not a quoted string.
48
48
*`partial_update`: Optional indicator if this is an incremental update (not all points included).
49
49
50
50
Event telemetry messages should be sent "as needed" or according to specific requirements as
@@ -97,7 +97,7 @@ block with the following structure:e
97
97
*`points`: Collection of point names, defining the representative point set for this device.
98
98
*_{`point_name`}_: Point name.
99
99
*`units`: Set as-operating units for this point.
100
-
* (`set_value`): Optional setting to control the specified device point. See [writeback documentation](../specs/sequences/writeback.md).
100
+
* (`set_value`): Optional setting to control the specified device point. If the set_value represents a number, then this must be serialized as a JSON number, not a quoted string. See [writeback documentation](../specs/sequences/writeback.md).
101
101
* (`cov_threshold`): Optional threshold for triggering a COV event update.
102
102
103
103
The points defined in the `config.pointset.points` dictionary is the authoritative source
0 commit comments