Hi,
I’ve been working with esphome in several projects but I’ve tried to compile and upload a new nodemcu but with only compiling It gets stuck compiling… and HA restarts.
had Anyone this problem before? and how to fix it?
Then it should not be a problem as I also run the setup in a similar platform. Please check if the system is having the correct power supply and there is no power supply problems?
Also check how much processor usage is there. if this is high, then the system could stall.
This is what i have in logs, I think it is something related with DNS… I don’t know
21-04-12 12:47:39 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-9088' coro=<_websocket_forward() done, defined at /usr/src/supervisor/supervisor/api/ingress.py:269> exception=ConnectionResetError('Cannot write to closing transport')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/api/ingress.py", line 278, in _websocket_forward
await ws_to.ping()
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_ws.py", line 287, in ping
await self._writer.ping(message)
File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 673, in ping
await self._send_frame(message, WSMsgType.PING)
File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 650, in _send_frame
self._write(header + message)
File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 660, in _write
raise ConnectionResetError("Cannot write to closing transport")
ConnectionResetError: Cannot write to closing transport
21-04-12 12:47:40 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-9062' coro=<_websocket_forward() done, defined at /usr/src/supervisor/supervisor/api/ingress.py:269> exception=ConnectionResetError('Cannot write to closing transport')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/api/ingress.py", line 278, in _websocket_forward
await ws_to.ping()
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_ws.py", line 287, in ping
await self._writer.ping(message)
File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 673, in ping
await self._send_frame(message, WSMsgType.PING)
File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 650, in _send_frame
self._write(header + message)
File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 660, in _write
raise ConnectionResetError("Cannot write to closing transport")
ConnectionResetError: Cannot write to closing transport
21-04-12 12:51:20 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-04-12 12:51:20 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
In that case it could be somethin related with the new setup. i have seen such cases in the community before also. please search for esphome error in community and i think you can find more threads on the issue.
In the meantime i will also do my research and get back.
It gives me the same error with dev, i think it is something related with DNS server because it is what is getting problems when it it compiling… @sheminasalam I looked for before creating this topic but the error was different.
After this error the system breaks down and HA is not reachable. I have to unplug to restart.
I don’t actually know from which moment on this error appears. I compiled with ESP Home several entities without problems.
Make sure that you have at least 500Mb of memory free. I had the same issue and after hours of testing and trying and doing research, the problem was that I didn’t have enough memory free when compiling.
This is an issue with the amount of RAM memory not disk space. You need at least 500MB of free RAM memory at the time that you are compiling your EspHome node.
