Azure / Azure/iotedge

LeafDeviceId is not present in the messages which are routed to custom module.

Open
#4,689 8 comments 0 reactions 1 assignee Claimed by @vipeller View on GitHub
1.0.9 customer-reported iotedge no-issue-activity
Dominant language
C#
Stars
1.5k
Forks
473
Avg merge
2d 17h
Merged PRs (30d)
7

Description

Hi,

I am running iotedge as transparent gateway and successfully connected my leaf-device with iotedge.
I have deployed a custom module(management-suite) at iotedge and have added following route to receive reported property of leafDevice and i am able to receive it.
FROM /twinChangeNotifications INTO BrokeredEndpoint("/modules/management-suite/inputs/input1")

**Issue :**
twinChangeNotifications received at custom module (management-suite) does not have leafDeviceId present in the message.
**How will my iotedge module know which device sent twinChangeNotifications ?**
We are blocked due to this, could you please check this on priority ?

Note : I tried to fetch ConnectionDeviceId from message, but it gives edge-device-id. I did not find any way to get leaf deviceId.
Adding leaf-deviceId in each reported property does not make sense.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.