MQTT_TX_BUFFER_TOO_SHORT_ERROR on AWS IoT embedded C
Posted: Mon May 01, 2017 1:17 pm
Hi there,
We've been busy using the AWS IoT from the embedded C within the IDF. We also use shadow and everything works nicely, be it that initializing/retrieving the shadow state can sometimes cause random crashes which we have still under investigation.
We run a publishing loop just like the examples and for all messages < 512 bytes publishing an MQTT message on AWS IoT works like a charm. But as messages will be around 1000 and 2000 bytes in real life application, we run into the MQTT_TX_BUFFER_TOO_SHORT_ERROR (-33) message.
These settings are defined within the aws_iot_config.h file, but overriding these settings to 1024 or 2048 when sending just over 512 bytes will still return the MQTT_TX_BUFFER_TOO_SHORT_ERROR error.
Could this be a bug?
Kind regards,
Martijn
We've been busy using the AWS IoT from the embedded C within the IDF. We also use shadow and everything works nicely, be it that initializing/retrieving the shadow state can sometimes cause random crashes which we have still under investigation.
We run a publishing loop just like the examples and for all messages < 512 bytes publishing an MQTT message on AWS IoT works like a charm. But as messages will be around 1000 and 2000 bytes in real life application, we run into the MQTT_TX_BUFFER_TOO_SHORT_ERROR (-33) message.
These settings are defined within the aws_iot_config.h file, but overriding these settings to 1024 or 2048 when sending just over 512 bytes will still return the MQTT_TX_BUFFER_TOO_SHORT_ERROR error.
Could this be a bug?
Kind regards,
Martijn