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: doc/1/guides/assets/index.md
+25-1Lines changed: 25 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ An asset is uniquely identified by the `type` + `model` + `reference` triplet.
31
31
"qos": {
32
32
"battery":2.3
33
33
},
34
-
34
+
35
35
"latitude":41.074688,
36
36
"longitude":28.9800192,
37
37
"accuracy":42,
@@ -85,3 +85,27 @@ By default, for each measurement type the following information are copied in ad
85
85
```
86
86
87
87
It is possible to override the [Decoder.copyToAsset](/official-plugins/device-manager/1/classes/decoder/copy-to-asset) method to choose what to copy into the asset.
88
+
89
+
## Historization
90
+
91
+
Assets are historized in the `assets-history` collection when a new measure is received.
92
+
93
+
Before historization, the `tenant:<tenant-id>:asset:measure:new` event is emitted. This event allows to enrich the asset before it is historized.
94
+
95
+
The payload contains the new `measures` and the `assetId`.
96
+
97
+
The content of `request.result.asset` will be used to update the asset measures and then create the history document.
0 commit comments