Skip to content

Commit 41528cf

Browse files
Merge pull request #291688 from kgremban/dec9-lincoln
No module lifecycle events
2 parents ecc0199 + 806b356 commit 41528cf

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/iot-hub/iot-hub-non-telemetry-event-schema.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,9 @@ Device lifecycle events are emitted whenever a device or module is created or de
133133
| Property | Value |
134134
| ---- | ----------- |
135135
| iothub-message-schema | deviceLifecycleNotification |
136-
| opType | One of the following values: createDeviceIdentity, deleteDeviceIdentity, createModuleIdentity, or deleteModuleIdentity. |
136+
| opType | One of the following values: createDeviceIdentity, deleteDeviceIdentity. |
137+
138+
Both modules and devices use the `createDeviceIdentity` and `deleteDeviceIdentity` application properties to report connection state events. If the event came from a module, then the event also includes a `moduleId` property. If there is no `moduleId` property, then the event came from a device.
137139

138140
**System properties**: The following table shows how system properties are set for device lifecycle events:
139141

@@ -166,8 +168,8 @@ The following JSON shows a device lifecycle event emitted when a module is creat
166168
"deviceId": "contoso-device-2",
167169
"operationTimestamp": "2022-05-27T18:49:38.4904785Z",
168170
"moduleId": "module-1",
169-
"opType": "createModuleIdentity",
170-
"iothub-message-schema": "moduleLifecycleNotification"
171+
"opType": "createDeviceIdentity",
172+
"iothub-message-schema": "deviceLifecycleNotification"
171173
}
172174
},
173175
"annotations": {

0 commit comments

Comments
 (0)