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: articles/industry/agriculture/ingest-historical-telemetry-data-in-azure-farmbeats.md
+36-1Lines changed: 36 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ Follow these steps.
67
67
68
68
Now that you have the required credentials, you can define the device and sensors. To do this, create the metadata by calling FarmBeats APIs. Please note you will need to call the APIs as the client app that you created in the above section
69
69
70
-
FarmBeats Datahub has the following APIs that enable creation and management of device or sensor metadata.
70
+
FarmBeats Datahub has the following APIs that enable creation and management of device or sensor metadata. Please note that as a partner you have access to only read, create and update the metadata; **Delete is not allowed by a partner.**
71
71
72
72
- /**DeviceModel**: DeviceModel corresponds to the metadata of the device, such as the manufacturer and the type of device, which is either a gateway or a node.
73
73
- /**Device**: Device corresponds to a physical device present on the farm.
@@ -379,6 +379,41 @@ Here's an example of a telemetry message:
379
379
}
380
380
```
381
381
382
+
## Troubleshooting
383
+
384
+
### Can't view telemetry data after ingesting historical/streaming data from your sensors
385
+
386
+
**Symptom**: Devices or sensors are deployed, and you've created the devices/sensors on FarmBeats and ingested telemetry to the EventHub, but you can't get or view telemetry data on FarmBeats.
387
+
388
+
**Corrective action**:
389
+
390
+
1. Ensure you have done the partner registration correctly - you can check this by going to your datahub swagger, navigate to /Partner API, Do a Get and check if the partner is registered. If not, please follow the [steps here](get-sensor-data-from-sensor-partner.md#enable-device-integration-with-farmbeats) to add partner.
391
+
2. Ensure that you have created the metadata (DeviceModel, Device, SensorModel, Sensor) using the partner client credentials.
392
+
3. Ensure that you have used the correct Telemetry message format (as specified below):
393
+
394
+
```json
395
+
{
396
+
"deviceid": "<id of the Device created>",
397
+
"timestamp": "<timestamp in ISO 8601 format>",
398
+
"version" : "1",
399
+
"sensors": [
400
+
{
401
+
"id": "<id of the sensor created>",
402
+
"sensordata": [
403
+
{
404
+
"timestamp": "< timestamp in ISO 8601 format >",
405
+
"<sensor measure name (as defined in the Sensor Model)>": <value>
406
+
},
407
+
{
408
+
"timestamp": "<timestamp in ISO 8601 format>",
409
+
"<sensor measure name (as defined in the Sensor Model)>": <value>
0 commit comments