You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First found in my own program, I have identified a bug which can be reproduced using the mqtt_tcp example. This event doesn't fire:
58 case MQTT_EVENT_PUBLISHED:
59 ESP_LOGI(TAG, "MQTT_EVENT_PUBLISHED, msg_id=%d", event->msg_id);
60 break;
Subscribing to relevant mqtt topic shows that data packets do flow to their correct locations; it's just the event that isn't firing.
I (4170) MQTT_SAMPLE: MQTT_EVENT_SUBSCRIBED, msg_id=63326
I (4180) MQTT_SAMPLE: sent publish successful, msg_id=0
D (4190) MQTT_CLIENT: msg_type=11, msg_id=23782
D (4190) MQTT_CLIENT: pending_id=23782, pending_msg_count = 1
D (4200) MQTT_CLIENT: UnSubscribe successful
I (4200) MQTT_SAMPLE: MQTT_EVENT_UNSUBSCRIBED, msg_id=23782
The text was updated successfully, but these errors were encountered:
First found in my own program, I have identified a bug which can be reproduced using the mqtt_tcp example. This event doesn't fire:
Subscribing to relevant mqtt topic shows that data packets do flow to their correct locations; it's just the event that isn't firing.
The text was updated successfully, but these errors were encountered: