Closed thomasweichselbaumer closed 1 month ago
We also have concern about following remark under porting mqtt: THIS FEATURE IS IN PREVIEW AND THE API IS SUBJECT TO CHANGE
Yes it is. Is there anything particular you need?
THIS FEATURE IS IN PREVIEW AND THE API IS SUBJECT TO CHANGE
This is referring to the MQTT abstraction layer feature and not the SDK. Currently we don't fully support swapping out the MQTT layer from CoreMQTT.
Also, please note, this is a freeRTOS wapper for the actual embedded IoT SDK. This SDK handles the freeRTOS interaction. The IoT hub features are implemented and exposed on the IoT Hub SDK.
closing this issue
Is there an existing issue for this?
Version
master
Description of the issue
Our dev-team want to move from azure-iot-sdk-c to Azure Iot Middleware for FreeRTOS or azure-sdk-for-c to save resourcess on our embedded target. Now we are not sure if this is the right choice because there is no commit in the last year. The last release is mor than 2 years ago. Is this project still under maintenance?
@danewalton i saw you in the video. Can you tell use something about that? Which SDK would you recommend on an embedded target like the esp32?
Expected behavior
No response
Steps to reproduce the issue
No response
Relevant log output
No response
Code of Conduct