Esphome killing home assistant

ESPHome
, ,
5

Yeah I’m finding it difficult to get the logs out as they reset upon restarting the HA instance. After choosing the command to install manually, it does seem to be the compiling that’s killing the instance, which is odd as I’ve had it working on this device before I switched to an SSD. Below is the output of the compiling before it goes offline

INFO Reading configuration /config/esphome/living-room-plant.yaml...
INFO Generating C++ source...
INFO Compiling app...
INFO Running:  platformio run -d /config/esphome/living-room-plant
Processing living-room-plant (board: esp01_1m; framework: arduino; platform: platformio/[email protected])
--------------------------------------------------------------------------------
HARDWARE: ESP8266 80MHz, 80KB RAM, 1MB Flash
PACKAGES: 
 - framework-arduinoespressif8266 3.20704.0 (2.7.4) 
 - tool-esptool 1.413.0 (4.13) 
 - tool-esptoolpy 1.20800.0 (2.8.0) 
 - toolchain-xtensa 2.40802.200502 (4.8.2)
Library Manager: Installing Update
Library Manager: Already installed, built-in library
Dependency Graph
|-- <ESPAsyncTCP-esphome> 1.2.3
|   |-- <ESP8266WiFi> 1.0
|-- <ESPAsyncWebServer-esphome> 1.2.7
|   |-- <ESPAsyncTCP-esphome> 1.2.3
|   |   |-- <ESP8266WiFi> 1.0
|   |-- <Hash> 1.0
|   |-- <ESP8266WiFi> 1.0
|-- <ESP8266WiFi> 1.0
|-- <ESP8266mDNS> 1.2
|   |-- <ESP8266WiFi> 1.0
|-- <DNSServer> 1.1.1
|   |-- <ESP8266WiFi> 1.0
Compiling /data/living-room-plant/.pioenvs/living-room-plant/lib768/ESPAsyncWebServer-esphome/SPIFFSEditor.cpp.o
Compiling /data/living-room-plant/.pioenvs/living-room-plant/lib768/ESPAsyncWebServer-esphome/WebHandlers.cpp.o
Compiling /data/living-room-plant/.pioenvs/living-room-plant/lib768/ESPAsyncWebServer-esphome/WebRequest.cpp.o
Compiling /data/living-room-plant/.pioenvs/living-room-plant/lib768/ESPAsyncWebServer-esphome/WebResponses.cpp.o
6

As I said put esphome on another computer.

1 Like
7

I have the same issue…

8

Run esphome on another computer.

9

Is it possible to create a link between HA on the Raspberrypi and ESPHome on another computer so it works as seamless as for the add-on?

10

It works seamlessly on another computer, I’m not sure what you mean.

11

I mean how to create the link between HA and ESPHome when they run on two different computers.

12

A link? What for? Why?

13

When ESPHome is installed as an add-on it appears as an icon on the left side. Here you click and then you enter ESPHome. If ESPhome is installed on a different computer and not integrated as an add-on, I wonder how the integration works?

14

You could even use the public online compiler
https://web.esphome.io/
(you don’t need the addon integrated on HA, you only need esphome to compile, after that the esp module works with ha directly)

15
16

Installed ESPhome on an iMac with plenty of RAM using the package manager HomeBrew. This works very well. Thanks for the input!

17

@JL-EU Please mark as solution :wink:

18

I am sorry but I am new to this forum I don’t see a check box? :slight_smile:

19

My bad, only the author of the original question can mark it as answer :face_with_raised_eyebrow:
image

20

If you are still having compile problems, see the related thread at Compilation fails : xtensa-lx106-elf-g++: fatal error: Killed signal terminated program cc1plus

21

I have same problem

error
error887×457 52.1 KB

then I installed Python on my windows computer, and I run esphome file.yaml but I got this new error
ota
ota1082×606 85.6 KB

I need help to upgrade PlatformIO Core 6 … thanks in advance

22

Why are you cross posting this? It isn’t helpful, if you ask the same question in three different topics. And it will def. not get you more help…

23

So as mentioned in the other post referenced for me the solution was to limit compile processes in the config

esphome:
  ...
  compile_process_limit: 1

common problem to run out of ram if you build with many cores in parallel

1 Like
24

Yes it is a memory problem, I was running a VM on VMWare Pro with 1Gb RAM and increasing the RAM in the VM to 4Gb fixed the problem. If I’d had the sense to look at the VM console the answer would have been obvious as there was a low memory error message plainly displayed!