Querying sensorEDGE data via netFIELD Cloud WebSocket API services
75/166
No.
Element
Description
(1)
"topic"
MQTT topic (UTF-8 coded)
(2)
"PublisherId"
ID of the instance in the sensorEDGE device (i.e. the netFIELD
App OPC-UA IO-Link Adapter) that published the data to the
MQTT message bus.
(3)
"Messages"
Array of messages containing the retrieved health information of
the connected sensor(s) and of the netFIELD App OPC-UA IO-
Link Adapter. Depends on how many sensors are connected (and
support health diagnostics).
(4)
“Timestamp”
Timestamp taken in the sensorEDGE device at the time the value
was read.
(5)
"POI"
Point of interest: Unique string that specifies the sensor (or other
item or “asset”) for which the health status is reported.
Besides the name, it can also include the serial number of the
device at the end of the string (if available).
(6)
"Payload"
Payload section containing the actual health information
parameters and values of the sensor (or other item or “asset”).
Table 20: Important elements in Health message
The path for accessing health information of a certain sensor/asset value –
in this example
healthscore
of the
ifm
sensor connected at port X1 of the
sensorEDGE – thus would be:
payload.data.Messages[1].Payload.healthScore
netFIELD sensorEDGE | User manual
DOC200601UM01EN | Revision 1 | English | 2021-09 | Released | Public
© Hilscher 2021
