My post was to get rid of the compile problems and the Wi-Fi not having enough RAM to run - and to get you to a baseline without all the other cruft. The config above is designed to work with problematic devices without impacting performance too much. I don’t know why there was a mix-up with on_value vs on_state - it was a while ago.
Having said that - your commitment to time to resolve your issue is admirable; but sometimes it may just be the device itself, or you just have too much LVGL going on for an esp32s3 to cope with. Perhaps it’s time to move on and have fun with another device, as you alluded to in your post.
An interesting post by Clyde hints at the additional processing using a display and LVGL causes (this is for OTA flashing - but it shows the impact of display/LVGL can have):
I’d recommend getting the new Waveshare 7b covered in this thread or any of the other recent esp32p4’s with touchscreen running on an esp32p4 and esp32c6 (for advanced WiFi/Blue tooth). This may suit your use case better - faster WiFi for one offloaded to a separate esp32c6.
Shame we couldn’t resolve your issue and you ran out of steam.
Thanks,
Charlie