@brossingo I have encountered this. (mainly when using incorrect firmware). You should also include the stacktrace, so we can see where in umqtt it is occuring. T