Hi there. Since some time now I was wondering what are my options to stay on my RPi3 and not switch to nothing bigger.
After some HA update I cannot update my ESP Home devices due to lack of RAM. I found similar problems and I searched for solutions but nothing was satisfying.
The idea is simple. Since on RPi there is not enough memory, compile esphome node on my main pc which is much stronger and move binaries to ha server. Then through the OTA update node.
Is there such a option? I thought it should be one of basic things in esphome project
If you put this into your ESP YAML code, you will get an OTA button when you click on “Visit” or log on to the device IP address…
web_server:
port: 80
I have run into similar situation with my rpi4/4G system. I have compiled larger configs on my Macbook and copied / uploaded to my device via USB. Check with Ai for step-by-step.
The ESPHome Builder addon is just for compiling and that part can be run elsewhere.
Wally has the answer. Why bog down your poor RPi production machine with development work like compiling ESP device firmware? Do that on your regular laptop or desktop or whatever.
The only question I have is that you mention being unable to update the ESP devices due to a lack of RAM. I think we’re all assuming that’s the RAM on your RPi. But of course you can also create an ESPHome project which takes more memory than your ESP device has available, especially since it needs to keep the old image running while it’s downloading and installing the new. If that’s the problem, that’s a completely different issue, although you’d still benefit from using ESPHome Command Line instead of compiling on your RPi.
The problem with this setup is that you loose the possibility to edit esphome devices from anywhere, you’re stuck with your pc/laptop. If you have esphome builder on your server you can login from anywhere and work.
Perhaps now it’s time to upgrade your ancient Pi? Pi3 is officially “not ok” anyway.
I keep my ESPHome Device Builder on HA in synch with my ESPHome Command-Line on my laptop. All I have to do is copy any .yaml file I’ve changed to the other device.
Eventually I found I never really use the Builder add-on. I try not to do any development on HA when I’m away. I ended up setting the Builder not to start automatically. I could still start it if I had to, and copy files as needed, but that seems risky if I’m not there to fix anything which goes wrong hardware-wise.
This is all especially true for an aging RPi. I’d be very reluctant to load that up by doing compiles. Also, not running the add-on frees up memory, which is a huge constraint on an RPi 3.