ESP12 seems to like to freeze now if we feed to much output data to mqtt PubSubClient. It goes away if timers are not synced, but the general solution is to use a state machine and update the mqtt broker incrementally piece by piece (Not blocking the main loop for too long).
This could also open the door to a more active mqtt publishing - after triplet of client-master-client packet exchange, there usually is a window to send the updated data to broker before the next second starts. This can easily be made configurable.
volca02
commented
6 years ago
ESP12 seems to like to freeze now if we feed to much output data to mqtt PubSubClient. It goes away if timers are not synced, but the general solution is to use a state machine and update the mqtt broker incrementally piece by piece (Not blocking the main loop for too long).
This could also open the door to a more active mqtt publishing - after triplet of client-master-client packet exchange, there usually is a window to send the updated data to broker before the next second starts. This can easily be made configurable.