6/13/2022 6:51 PM | |
Joined: 5/7/2022 Last visit: 6/19/2022 Posts: 3 Rating: (0) |
Hi, awesome! I'm new to Azure and would like to confirm if I understood how you solved it. I've also followed the Siemens application example and there the generation of password for the SAS token on iothubowner was using Device Explorer Twin Tool - this was causing the 80C5 issue? Would appreciate if you can confirm if you used this resource for generating the password using Powershell - Control access to IoT Hub using Shared Access Signatures (Microsoft Azure)? Which default command and Azure help pages did you mean? Thank you. ------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 06/22/2022 13:56:19New subject after splitting |
|
6/22/2022 1:57 PM | |
Joined: 6/19/2017 Last visit: 9/6/2024 Posts: 8175 Rating: (171) |
Closed cause question posted twice. The second thread with the subject S7-1200 MQTT to Azure IOT-Hub 80C5 status code is published within the conference Communication / Networks. Jen_Moderator |
Follow us on