A note the all in this thread; connecting wifi/bluetooth with the mtc4pu is indeed not flawless, we are trying/testing alternative code. Besides that it looks as there is a problem with the battery check code enabled in the main loop(). As the esp32 is a dual core there are mqtt and hub callbacks running concurrently, both doing mqtt things, which leads to corrupted mqtt messages sometimes. I investigated this with extra logging. I bit technical maybe. My simple advise for now is to comment the requestPoweredUpBatteryLevel(); line.