The fix for me was enabling wifi at the start of my code, I knew I needed wifi for the RTC functions but assumed it wouldn't affect positioning of objects, but it did. I added a check loop to make sure wifi is connected before proceeding.
I have a function that is executed in successive iterations and needs to have local variables. On Arduino it's very easy to create local variables that work within the function. In UiFlowin i see that it's not possible.
Now that things seem to work: is there a really pressing reason to migrate to UIFlow2.0?
My ultimate goal is to eventually start running openHASP on them and remotely control what they display through Home Assistant, so ideally I do no extra coding, but maybe there's a security concern or something that should change my mind?
ESP32 microcontroller supports both BLE and Wi-Fi simultaneously. The ESP32 chip has dedicated hardware for both BLE and Wi-Fi, allowing them to operate independently and concurrently. This means you can run BLE and Wi-Fi tasks concurrently without one interfering with the other.
Now M5Fire device with UIFlow only supports BLE Uart profile, not HID profile