Closed MrVhek closed 2 years ago
@MrVhek have u raised this issue in the Edge repo?
To get more debug logs add:
import logging logging.basicConfig(level=logging.DEBUG)
At the beginning of your application.
@MrVhek have u raised this issue in the Edge repo?
Not yet, not sure if this can be related to your SDK or to Azure IoT Edge directly ?
To get more debug logs add:
import logging logging.basicConfig(level=logging.DEBUG)
At the beginning of your application.
Thanks, I've added it but don't see more python logs than those that I posted above. I need to see if I can have more logs on Azure side.
i am facing same problem
@MrVhek can you try reverting to IoT Edge 1.1? There are known issues with using Edge 1.2 with the SDK.
@raowaqas72 if you could try the same, that would also be appreciated
Sorry for the late reply, I finally found the issue, it was related to the routing of send_message.
Be sure to not have an output after your module name (here GWApp or ToolsApp). Thanks for your help anyway ! I just hope that some warning or error log could be emitted if messages are not being routed. But maybe it is already the case.
Hello, I've been facing a weird issue using: iotedge 1.2.10 edgeAgent/edgeHub 1.2.10.55800403 azure-iot-device 2.11.0
When I create the client module using create_from_edge_environment function within my IoT Edge Module, the module is able to correctly push and pull twin, but any message sent is never received on the hub. If I use the from_connection_string and use a connection string within the same Docker, it works... This is really strange, here some information I got from logs:
As you can see, no message is received on the IoT Hub... I normally have a function app that will use the fallback route to receive messages sent.![image](https://user-images.githubusercontent.com/16084117/172629178-dcd674cb-f2cb-4e11-97ba-a13f7bc1debd.png)
Any way to investiguate it further on IoT Hub side ? Or some additional logs to investigate on python side ?
Thanks