tesseraFeatures Wishlist
Automatic compile on remote server using ESPHome Device Builder
Your project is great, but compiling the code for the display on a RPi running more than just Home Assistant takes a very long time and consumes nearly 100% of the RAM. This can be easily bypassed by automatically attempting to compile the code on a remote server connected to the ESPHome Device Builder - in this case, my PC, which has a much more powerful processor and more memory. Compilation then takes 3–4 minutes and succeeds every time.
Currently, if I want to add a new screen, I have to start the compilation on the RPi, wait for it to fail (10–15 minutes), and only then do I run the compilation on the external server.
Discussion 2
Add a commentThanks for writing this up so clearly.
Some background on why pairing a build server does not help here yet: ESP Screens compiles inside its own add-on, with its own pinned ESPHome, so ESPHome Device Builder's Build server never sees that job.
What works today: the screen's YAML is written into
/config/esphome, the same folder Device Builder reads. Create the screen once in ESP Screens, then open that file in ESPHome Device Builder and press Install there. Your build server picks it up, the screen is exactly the same screen, and updates work the same way.That is also the route we mean to keep. We are not going to build compiling on another machine into ESP Screens: ESPHome already has it, it works, and a second version of it would only be a worse copy that we would have to maintain alongside theirs. What we can do is hand our build over to your ESPHome add-on so you skip the detour, and that is on the list.
Original on GitHub
Thanks for the reply, this solution is more than enough for my needs :) Screen updates are running smoothly. I’m not sure if I was just blind and missed the "Create profile only" option when adding a new device. I consider the issue resolved :)
Original on GitHub