blockchain: Problem with ❝Delivering Data from IoT Hub to Azure Blockchain Workbench❞

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Just followed the steps described in https://github.com/Azure-Samples/blockchain/blob/master/blockchain-workbench/iot-integration-samples/ConfigureIoTDemo.md and everything looks fine image

but when I check it on ABW UI there is no activity from device. I can log in as device in ABW UI and enter telemetry data.

image I also checked the database and couldn’t find any data coming from device. (only data ingested from UI was registered) image

How can I debug this? Is there any log/information available after I send a message to “ingressQueue”?

Versions

ABW 1.7.3

Mention any other details that might be useful

Here is my data coming from device: {“deviceid”:“0fea776f-96b2-4ecf-9dd5-b48a78317c33”,“temperature”: 28,“humidity”: 76} ※as you see I use my on user external-id as deviceid.

Data send to queue: { “requestId”: “680de98d-09e9-4eb4-88a0-30523421b97e”, “userChainIdentifier”: “0xca2d7158d0780e2fe88e1f6d9b5518f131601c56”, “contractLedgerIdentifier”: “0xb4f3734cc97a11bb48ada02167025924cc8638d9”, “workflowFunctionName”: “IngestTelemetry”, “Parameters”: [ { “name”: “humidity”, “value”: “76” }, { “name”: “temperature”, “value”: “28” }, { “name”: “timestamp”, “value”: “1571969366” } ], “connectionId”: “1”, “messageSchemaVersion”: “1.0.0”, “messageName”: “CreateContractActionRequest” }


Thanks! We’ll be in touch soon.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 20 (1 by maintainers)

Most upvoted comments

@mesgar You are right! this was my issue as well. Finally I have fixed it and able to ingest telemetry. Thank you very much for your big help on this. Let’s leave the bug open since anyway it looks like the ingestion through message queue doesn’t work.