Russell Summers

The sample IOT applications are weak about how they demonstrate the concepts. They are poor patterns to follow. You will see them calling MQTT_ProcessLoop(&_mqttContext, timeoutVar) only during specific actions. That...

I assume you are handling incoming messages in an event_callback() handler? Incidentally, my stack size is set to 28k. That is enough to handle all IOT services. I'm not sure...

One more comment that might be significant here.... Looking at your while loop.... I'm seeing that you are indiscriminately moving through the MQTT_ProcessLoop() but not specifically reacting to incoming message...

The way I understand it -- the Agent mechanism was added to the demo projects as a way of over-coming the weakness in doing all the MQTT calls in different...

I rolled all the sample projects into one. I have one task that runs it all. So, I have no idea why someone would want to make the project more...

By default, the components directory will be automatically registered as a place to find components. Place the esp-aws-iot library right into your components directory. In your main directory (another component...

You may have several errors.... one that I see immediately is: I don't think this is necessary: set(AWS_IOT_PATH "components/esp-aws-iot") set(EXTRA_COMPONENT_DIRS "${AWS_IOT_PATH}/libraries" ) You just drop the esp-aws-iot into the components...

I have my project set up a bit differently -- my iot component includes this CMakeLists. Notice the items from the esp-awt-iot component that I include: The only unusual thing...

You got it. Good going. These things are hard. K. ________________________________ From: Toby Loki ***@***.***> Sent: Wednesday, March 8, 2023 10:22 AM To: espressif/esp-aws-iot ***@***.***> Cc: keith ssledlighting.com ***@***.***>; Comment...

It is nice of you to send me some happy feedback. We are up to v4.4.5 now, but no further.