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
That's great, very useful. Can you give a bit more detail on step 7. Say I've constructed the URL as TTN spec, how does that get used by the Cloud2Device service, or however you supply the downlink?
The text was updated successfully, but these errors were encountered:
Hi @BenHFT - thanks for your comment, glad you find it useful 😄
I will try to update the guide to include information on this but fundamentally it's not something you would solve with Cloud2Device in IoTHub with this form of integration.
The pattern would be that a subscribing application such as Logic Apps or something custom would pick up on the downlink_url and call that directly. This would bypass the IoT Hub but in this case, since you don't have an established connection to the device, there is no option to do this via IoT Hub.
Hello Philip,
Thanks for the useful content and your further comments.
I see what you mean, this is a “single” device connection as far as IOT Hub is concerned.
And your other link seems to throw cold water on connecting downlinks in the bridge case:
https://github.com/Azure/iotc-device-bridge#limitations
I’ve tested downlinks successfully as a manually created CURL exercise, I was hoping to find a torchbearer on integrating it into Azure. Might have to think a bit more about this. TTN server should have Azure integration, but not until next year I believe.
Thanks for the update.
Best regards,
Ben
Based on comment from @BenHFT
The text was updated successfully, but these errors were encountered: