Florian

@TomRoush Do you want to rebase the PR now that we have bumped version ? Also I would suggest to add the envs as `;default_envs = ` in platformio.ini

Thanks

It could be interesting to increase your receiver task Stack and see if you eliminate the message corruption.

> //RFrtl_433_ESPdata["origin"] = (char*)topic.c_str(); //handleJsonEnqueue(RFrtl_433_ESPdata); pub(topic.c_str(), RFrtl_433_ESPdata); Interesting, I introduced this change and fixed data corruption for numerous people using RTL_433 https://github.com/1technophile/OpenMQTTGateway/issues/1836

Could be a concurrency issue in the queue, discovery topics are quite heavy in terms of number and length and having them mixed in the queue with the regular messages...

Try to increase the task stack associated with RTL_433 `rtl_433_Decoder_Stack`, if I recall well this helped during my testing. We also added a mutex but went to the same conclusion...

It's worth a try considering your message-heavy setup. If it helps, at least it gives a direction towards memory allocation versus concurrency.

Thanks for the detailled analysis > serialize -> push -> pop -> deserialize Could be tested for sure.

Great, thanks for this! What do you think about using a char array instead of a String ?

> would you mind taking it from here to polish? Yes sure, I would need your help to retest after by the way