starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-26 09:46:06 +03:00
Code Issues 12 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #5607] ESPHome update from 2025.4.0 to 2025.6.2 breaks Update button in Dashboard #1198

New issue
Closed
opened 2026-02-26 12:48:04 +03:00 by kerem · 22 comments
kerem commented 2026-02-26 12:48:04 +03:00
Owner
Copy link

Originally created by @jsbrich on GitHub (Jul 1, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5607

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Esphome

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/esphome.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

I was using the ESPHome LXC and was at 2025.4.0. When I ran the bash script command in the console to update it, the dashboard says it was at 2025.6.2. When I click on the Update button for a device, it is still compiling the code as 2025.4.0.

🔄 Steps to reproduce the issue.

Step 1: Start with LXC running ESPHome 2025.4.0
Step 2: Run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/esphome.sh)"
Step 3: Update device in dashboard

❌ Paste the full error output (if available).

INFO ESPHome 2025.4.0 INFO Reading configuration /root/config/air-quality-upstairs.yaml... INFO Generating C++ source... INFO Compiling app... Processing air-quality-upstairs (board: d1; framework: arduino; platform: platformio/espressif8266@4.2.1) --------------------------------------------------------------------------------

🖼️ Additional context (optional).

I noticed that during the update it looks like a lot was moved to a venv. My config files are still stored in their original location /root/config/. Does that need to change?

Originally created by @jsbrich on GitHub (Jul 1, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5607 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Esphome ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/esphome.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. I was using the ESPHome LXC and was at 2025.4.0. When I ran the bash script command in the console to update it, the dashboard says it was at 2025.6.2. When I click on the Update button for a device, it is still compiling the code as 2025.4.0. ### 🔄 Steps to reproduce the issue. Step 1: Start with LXC running ESPHome 2025.4.0 Step 2: Run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/esphome.sh)"` Step 3: Update device in dashboard ### ❌ Paste the full error output (if available). `INFO ESPHome 2025.4.0 INFO Reading configuration /root/config/air-quality-upstairs.yaml... INFO Generating C++ source... INFO Compiling app... Processing air-quality-upstairs (board: d1; framework: arduino; platform: platformio/espressif8266@4.2.1) --------------------------------------------------------------------------------` ### 🖼️ Additional context (optional). I noticed that during the update it looks like a lot was moved to a venv. My config files are still stored in their original location /root/config/. Does that need to change?
kerem 2026-02-26 12:48:04 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jul 1, 2025):

What for an Update Button? How can we reproduce this?

<!-- gh-comment-id:3022041817 --> @MickLesk commented on GitHub (Jul 1, 2025): What for an Update Button? How can we reproduce this?
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@jsbrich commented on GitHub (Jul 1, 2025):

When you update to a new version of ESPHome, on the dashboard, each device gets an Update button

Image

<!-- gh-comment-id:3022196786 --> @jsbrich commented on GitHub (Jul 1, 2025): When you update to a new version of ESPHome, on the dashboard, each device gets an Update button ![Image](https://github.com/user-attachments/assets/0355a207-6e9a-4e63-b243-02648d6dd4cb)
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jul 1, 2025):

And where you see the old Version?

The config is unchanged in the service File

<!-- gh-comment-id:3022213580 --> @MickLesk commented on GitHub (Jul 1, 2025): And where you see the old Version? The config is unchanged in the service File
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@jsbrich commented on GitHub (Jul 1, 2025):

When you click update, the dialog comes up asking how you want to install. I usually choose Wireless as the devices aren't plugged in to the computer. Then it starts to compile the binary image. In the output, you get the message I put in the Full Error Output section showing that it is compiling using 2025.4.0 instead of 2025.6.2

It seems that the dashboard is trying to use the old location the ESPHome bin was in /use/bin instead of using the one in the .venv. As a test, I did an ln -sf linking the esphome bin in the virtual environment to the old /use/bin location and I was able to update using the button. But that defeats the purpose of running in a virtual environment

<!-- gh-comment-id:3022240128 --> @jsbrich commented on GitHub (Jul 1, 2025): When you click update, the dialog comes up asking how you want to install. I usually choose Wireless as the devices aren't plugged in to the computer. Then it starts to compile the binary image. In the output, you get the message I put in the Full Error Output section showing that it is compiling using 2025.4.0 instead of 2025.6.2 It seems that the dashboard is trying to use the old location the ESPHome bin was in /use/bin instead of using the one in the .venv. As a test, I did an ln -sf linking the esphome bin in the virtual environment to the old /use/bin location and I was able to update using the button. But that defeats the purpose of running in a virtual environment
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jul 1, 2025):

can you share the output of service file?

cat /etc/systemd/system/esphomeDashboard.service

<!-- gh-comment-id:3022273626 --> @MickLesk commented on GitHub (Jul 1, 2025): can you share the output of service file? cat /etc/systemd/system/esphomeDashboard.service
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@jsbrich commented on GitHub (Jul 1, 2025):

`[Unit]
Description=ESPHome Dashboard
After=network.target

[Service]
ExecStart=/opt/esphome/.venv/bin/esphome dashboard /root/config/
Restart=always
User=root

[Install]
WantedBy=multi-user.target`

<!-- gh-comment-id:3022306445 --> @jsbrich commented on GitHub (Jul 1, 2025): `[Unit] Description=ESPHome Dashboard After=network.target [Service] ExecStart=/opt/esphome/.venv/bin/esphome dashboard /root/config/ Restart=always User=root [Install] WantedBy=multi-user.target`
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@jsbrich commented on GitHub (Jul 1, 2025):

Running which esphome gives me /usr/local/bin/esphome so my guess is the dashboard when it runs the esphome commands it is just using what is in $PATH, so maybe need to add the /opt/esphome... path to $PATH as part of the update?

<!-- gh-comment-id:3022324160 --> @jsbrich commented on GitHub (Jul 1, 2025): Running `which esphome` gives me `/usr/local/bin/esphome` so my guess is the dashboard when it runs the esphome commands it is just using what is in $PATH, so maybe need to add the /opt/esphome... path to $PATH as part of the update?
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jul 1, 2025):

maybe, its an very old install ?

You can try an backup and remove the /usr/local/bin/esphome and add an new link from .venv/bin? If this work?

<!-- gh-comment-id:3022330995 --> @MickLesk commented on GitHub (Jul 1, 2025): maybe, its an very old install ? You can try an backup and remove the /usr/local/bin/esphome and add an new link from .venv/bin? If this work?
kerem commented 2026-02-26 12:48:04 +03:00
Author
Owner
Copy link

@jsbrich commented on GitHub (Jul 1, 2025):

I redid it using the community scripts maybe 3-4 months ago? I will a new install and see if I can find the difference. I saw in the changelog that this LXC was recently switch to using venv, so maybe just some things the updater couldn't clean up or know about.

<!-- gh-comment-id:3022351073 --> @jsbrich commented on GitHub (Jul 1, 2025): I redid it using the community scripts maybe 3-4 months ago? I will a new install and see if I can find the difference. I saw in the changelog that this LXC was recently switch to using venv, so maybe just some things the updater couldn't clean up or know about.
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@jsbrich commented on GitHub (Jul 1, 2025):

Ok, I created a new CT using the bash script. I think the install script is missing something. When I try to use the dashboard to compile, it doesn't start at all. On a fresh install which esphome doesn't return anything. I think the issue is that the service being started for the dashboard is outside of the venv, so it is trying to find esphome outside the venv and not finding it? Looking at journalctl, I see this:

Jul 01 12:09:56 esphome esphome[12431]: 2025-07-01 12:09:56,538 INFO Running command 'esphome --dashboard compile --only-generate /root/config/air-quality-downstairs.yaml' Jul 01 12:09:56 esphome esphome[12431]: 2025-07-01 12:09:56,538 ERROR Exception in callback functools.partial(<function WebSocketProtocol._run_callback.<locals>.<lambda> at 0x7fbe639498a0>, <Task finished name='Task-137' coro=<EsphomeCommandWebSocket.on_message() done, defined at /opt/esphome/.venv/lib/python3.12/site-packages/esphome/dashboard/web_server.py:200> exception=FileNotFoundError(2, 'No such file or directory')>) Jul 01 12:09:56 esphome esphome[12431]: Traceback (most recent call last): Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/ioloop.py", line 758, in _run_callback Jul 01 12:09:56 esphome esphome[12431]: ret = callback() Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 668, in <lambda> Jul 01 12:09:56 esphome esphome[12431]: self.stream.io_loop.add_future(result, lambda f: f.result()) Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/esphome/dashboard/web_server.py", line 214, in on_message Jul 01 12:09:56 esphome esphome[12431]: await handlers[type_](self, json_message) Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/esphome/dashboard/web_server.py", line 237, in handle_spawn Jul 01 12:09:56 esphome esphome[12431]: self._proc = tornado.process.Subprocess( Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/process.py", line 240, in __init__ Jul 01 12:09:56 esphome esphome[12431]: self.proc = subprocess.Popen(*args, **kwargs) Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/root/.local/share/uv/python/cpython-3.12.11-linux-x86_64-gnu/lib/python3.12/subprocess.py", line 1026, in __init__ Jul 01 12:09:56 esphome esphome[12431]: self._execute_child(args, executable, preexec_fn, close_fds, Jul 01 12:09:56 esphome esphome[12431]: File "/root/.local/share/uv/python/cpython-3.12.11-linux-x86_64-gnu/lib/python3.12/subprocess.py", line 1955, in _execute_child Jul 01 12:09:56 esphome esphome[12431]: raise child_exception_type(errno_num, err_msg, err_filename) Jul 01 12:09:56 esphome esphome[12431]: FileNotFoundError: [Errno 2] No such file or directory: 'esphome' Jul 01 12:09:56 esphome esphome[12431]: 2025-07-01 12:09:56,539 ERROR Uncaught exception GET /compile (192.168.68.49) Jul 01 12:09:56 esphome esphome[12431]: HTTPServerRequest(protocol='http', host='esphome-dash.jnetinc.com', method='GET', uri='/compile', version='HTTP/1.1', remote_ip='192.168.68.49') Jul 01 12:09:56 esphome esphome[12431]: Traceback (most recent call last): Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/web.py", line 1848, in _execute Jul 01 12:09:56 esphome esphome[12431]: result = await result Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 277, in get Jul 01 12:09:56 esphome esphome[12431]: await self.ws_connection.accept_connection(self) Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 890, in accept_connection Jul 01 12:09:56 esphome esphome[12431]: await self._accept_connection(handler) Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 973, in _accept_connection Jul 01 12:09:56 esphome esphome[12431]: await self._receive_frame_loop() Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 1127, in _receive_frame_loop Jul 01 12:09:56 esphome esphome[12431]: await self._receive_frame() Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 1218, in _receive_frame Jul 01 12:09:56 esphome esphome[12431]: await handled_future Jul 01 12:09:56 esphome esphome[12431]: FileNotFoundError: [Errno 2] No such file or directory: 'esphome' Jul 01 12:10:00 esphome esphome[12431]: 2025-07-01 12:10:00,106 INFO 304 GET /devices (192.168.68.49) 1.44ms

So it looks like a $PATH issue still, maybe? Not knowing where to find the esphome python script?

EDIT: Adding /opt/esphome/.venv/bin to $PATH, does NOT stop the error.

<!-- gh-comment-id:3024885382 --> @jsbrich commented on GitHub (Jul 1, 2025): Ok, I created a new CT using the bash script. I think the install script is missing something. When I try to use the dashboard to compile, it doesn't start at all. On a fresh install `which esphome` doesn't return anything. I think the issue is that the service being started for the dashboard is outside of the venv, so it is trying to find esphome outside the venv and not finding it? Looking at journalctl, I see this: `Jul 01 12:09:56 esphome esphome[12431]: 2025-07-01 12:09:56,538 INFO Running command 'esphome --dashboard compile --only-generate /root/config/air-quality-downstairs.yaml' Jul 01 12:09:56 esphome esphome[12431]: 2025-07-01 12:09:56,538 ERROR Exception in callback functools.partial(<function WebSocketProtocol._run_callback.<locals>.<lambda> at 0x7fbe639498a0>, <Task finished name='Task-137' coro=<EsphomeCommandWebSocket.on_message() done, defined at /opt/esphome/.venv/lib/python3.12/site-packages/esphome/dashboard/web_server.py:200> exception=FileNotFoundError(2, 'No such file or directory')>) Jul 01 12:09:56 esphome esphome[12431]: Traceback (most recent call last): Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/ioloop.py", line 758, in _run_callback Jul 01 12:09:56 esphome esphome[12431]: ret = callback() Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 668, in <lambda> Jul 01 12:09:56 esphome esphome[12431]: self.stream.io_loop.add_future(result, lambda f: f.result()) Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/esphome/dashboard/web_server.py", line 214, in on_message Jul 01 12:09:56 esphome esphome[12431]: await handlers[type_](self, json_message) Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/esphome/dashboard/web_server.py", line 237, in handle_spawn Jul 01 12:09:56 esphome esphome[12431]: self._proc = tornado.process.Subprocess( Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/process.py", line 240, in __init__ Jul 01 12:09:56 esphome esphome[12431]: self.proc = subprocess.Popen(*args, **kwargs) Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/root/.local/share/uv/python/cpython-3.12.11-linux-x86_64-gnu/lib/python3.12/subprocess.py", line 1026, in __init__ Jul 01 12:09:56 esphome esphome[12431]: self._execute_child(args, executable, preexec_fn, close_fds, Jul 01 12:09:56 esphome esphome[12431]: File "/root/.local/share/uv/python/cpython-3.12.11-linux-x86_64-gnu/lib/python3.12/subprocess.py", line 1955, in _execute_child Jul 01 12:09:56 esphome esphome[12431]: raise child_exception_type(errno_num, err_msg, err_filename) Jul 01 12:09:56 esphome esphome[12431]: FileNotFoundError: [Errno 2] No such file or directory: 'esphome' Jul 01 12:09:56 esphome esphome[12431]: 2025-07-01 12:09:56,539 ERROR Uncaught exception GET /compile (192.168.68.49) Jul 01 12:09:56 esphome esphome[12431]: HTTPServerRequest(protocol='http', host='esphome-dash.jnetinc.com', method='GET', uri='/compile', version='HTTP/1.1', remote_ip='192.168.68.49') Jul 01 12:09:56 esphome esphome[12431]: Traceback (most recent call last): Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/web.py", line 1848, in _execute Jul 01 12:09:56 esphome esphome[12431]: result = await result Jul 01 12:09:56 esphome esphome[12431]: ^^^^^^^^^^^^ Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 277, in get Jul 01 12:09:56 esphome esphome[12431]: await self.ws_connection.accept_connection(self) Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 890, in accept_connection Jul 01 12:09:56 esphome esphome[12431]: await self._accept_connection(handler) Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 973, in _accept_connection Jul 01 12:09:56 esphome esphome[12431]: await self._receive_frame_loop() Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 1127, in _receive_frame_loop Jul 01 12:09:56 esphome esphome[12431]: await self._receive_frame() Jul 01 12:09:56 esphome esphome[12431]: File "/opt/esphome/.venv/lib/python3.12/site-packages/tornado/websocket.py", line 1218, in _receive_frame Jul 01 12:09:56 esphome esphome[12431]: await handled_future Jul 01 12:09:56 esphome esphome[12431]: FileNotFoundError: [Errno 2] No such file or directory: 'esphome' Jul 01 12:10:00 esphome esphome[12431]: 2025-07-01 12:10:00,106 INFO 304 GET /devices (192.168.68.49) 1.44ms` So it looks like a $PATH issue still, maybe? Not knowing where to find the esphome python script? EDIT: Adding /opt/esphome/.venv/bin to $PATH, does NOT stop the error.
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jul 1, 2025):

i check it tomorrow

<!-- gh-comment-id:3025060982 --> @MickLesk commented on GitHub (Jul 1, 2025): i check it tomorrow
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@lockenkop commented on GitHub (Jul 2, 2025):

i fixed the errors with adding the path in the systemd service

root@esphome:~# cat /etc/systemd/system/esphomeDashboard.service 
[Unit]
Description=ESPHome Dashboard
After=network.target

[Service]
Environment="PATH=$PATH:/opt/esphome/.venv/bin/"
ExecStart=/opt/esphome/.venv/bin/esphome dashboard /root/config/
Restart=always
User=root

[Install]
WantedBy=multi-user.target
<!-- gh-comment-id:3028142002 --> @lockenkop commented on GitHub (Jul 2, 2025): i fixed the errors with adding the path in the systemd service ``` root@esphome:~# cat /etc/systemd/system/esphomeDashboard.service [Unit] Description=ESPHome Dashboard After=network.target [Service] Environment="PATH=$PATH:/opt/esphome/.venv/bin/" ExecStart=/opt/esphome/.venv/bin/esphome dashboard /root/config/ Restart=always User=root [Install] WantedBy=multi-user.target ```
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@SebSeifert commented on GitHub (Jul 3, 2025):

i fixed the errors with adding the path in the systemd service

root@esphome:~# cat /etc/systemd/system/esphomeDashboard.service 
[Unit]
Description=ESPHome Dashboard
After=network.target

[Service]
Environment="PATH=$PATH:/opt/esphome/.venv/bin/"
ExecStart=/opt/esphome/.venv/bin/esphome dashboard /root/config/
Restart=always
User=root

[Install]
WantedBy=multi-user.target

Hi,
i pasted this Service in my LXC. Now it says esphome 2025.6.3 but now i got the error:

INFO ESPHome 2025.6.3
INFO Reading configuration /root/config/airgradient-wz.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing airgradient-wz (board: d1_mini; framework: arduino; platform: platformio/espressif8266@4.2.1)
--------------------------------------------------------------------------------
HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
Dependency Graph
|-- ESP8266WiFi @ 1.0
|-- ESP8266mDNS @ 1.2
|-- noise-c @ 0.1.6
|-- Wire @ 1.0
Compiling .pioenvs/airgradient-wz/src/esphome/components/api/api_connection.cpp.o
Compiling .pioenvs/airgradient-wz/src/esphome/components/api/api_frame_helper.cpp.o
*** [.pioenvs/airgradient-wz/src/esphome/components/api/api_connection.cpp.o] sh: No such file or directory
*** [.pioenvs/airgradient-wz/src/esphome/components/api/api_frame_helper.cpp.o] sh: No such file or directory
========================== [FAILED] Took 0.71 seconds ==========================

I had an working 2025.6.0 Version.
And if I install the recent 2025.6.3 Container and add a yaml the console output shows nothing. Also when I add an new device with no config.

<!-- gh-comment-id:3030878433 --> @SebSeifert commented on GitHub (Jul 3, 2025): > i fixed the errors with adding the path in the systemd service > > ``` > root@esphome:~# cat /etc/systemd/system/esphomeDashboard.service > [Unit] > Description=ESPHome Dashboard > After=network.target > > [Service] > Environment="PATH=$PATH:/opt/esphome/.venv/bin/" > ExecStart=/opt/esphome/.venv/bin/esphome dashboard /root/config/ > Restart=always > User=root > > [Install] > WantedBy=multi-user.target > ``` Hi, i pasted this Service in my LXC. Now it says esphome 2025.6.3 but now i got the error: ``` INFO ESPHome 2025.6.3 INFO Reading configuration /root/config/airgradient-wz.yaml... INFO Generating C++ source... INFO Compiling app... Processing airgradient-wz (board: d1_mini; framework: arduino; platform: platformio/espressif8266@4.2.1) -------------------------------------------------------------------------------- HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash Dependency Graph |-- ESP8266WiFi @ 1.0 |-- ESP8266mDNS @ 1.2 |-- noise-c @ 0.1.6 |-- Wire @ 1.0 Compiling .pioenvs/airgradient-wz/src/esphome/components/api/api_connection.cpp.o Compiling .pioenvs/airgradient-wz/src/esphome/components/api/api_frame_helper.cpp.o *** [.pioenvs/airgradient-wz/src/esphome/components/api/api_connection.cpp.o] sh: No such file or directory *** [.pioenvs/airgradient-wz/src/esphome/components/api/api_frame_helper.cpp.o] sh: No such file or directory ========================== [FAILED] Took 0.71 seconds ========================== ``` I had an working 2025.6.0 Version. And if I install the recent 2025.6.3 Container and add a yaml the console output shows nothing. Also when I add an new device with no config.
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@lockenkop commented on GitHub (Jul 3, 2025):

I get the same errors, it seems that the dashboard still has some path issues but now with dependencies.
my workaround is building from commandline on the host which does not have the pathing issues.
So i copy the build command from the journal to the cli and let it build there. Once it was build the dashboard will use the build and does not try to build it again.

from journal after failed build from dashboard

Jul 03 11:38:05 esphome esphome[148]: 2025-07-03 11:38:05,904 INFO Running command 'esphome --dashboard compile /root/config/esphome-web-06.yaml

paste the build command into a cli on the host

esphome --dashboard compile /root/config/esphome-web-06.yaml

and run the update/install again after build from cli.

<!-- gh-comment-id:3031595509 --> @lockenkop commented on GitHub (Jul 3, 2025): I get the same errors, it seems that the dashboard still has some path issues but now with dependencies. my workaround is building from commandline on the host which does not have the pathing issues. So i copy the build command from the journal to the cli and let it build there. Once it was build the dashboard will use the build and does not try to build it again. from journal after failed build from dashboard ``` Jul 03 11:38:05 esphome esphome[148]: 2025-07-03 11:38:05,904 INFO Running command 'esphome --dashboard compile /root/config/esphome-web-06.yaml ``` paste the build command into a cli on the host ``` esphome --dashboard compile /root/config/esphome-web-06.yaml ``` and run the update/install again after build from cli.
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@SebSeifert commented on GitHub (Jul 3, 2025):

I get the same errors, it seems that the dashboard still has some path issues but now with dependencies. my workaround is building from commandline on the host which does not have the pathing issues. So i copy the build command from the journal to the cli and let it build there. Once it was build the dashboard will use the build and does not try to build it again.

from journal after failed build from dashboard

Jul 03 11:38:05 esphome esphome[148]: 2025-07-03 11:38:05,904 INFO Running command 'esphome --dashboard compile /root/config/esphome-web-06.yaml

paste the build command into a cli on the host

esphome --dashboard compile /root/config/esphome-web-06.yaml

and run the update/install again after build from cli.

Okay that works not for me because then it still uses 2025.6.0 for compiling. Also after compiling with cli in the webinterface is the same error when try to install.

<!-- gh-comment-id:3031644115 --> @SebSeifert commented on GitHub (Jul 3, 2025): > I get the same errors, it seems that the dashboard still has some path issues but now with dependencies. my workaround is building from commandline on the host which does not have the pathing issues. So i copy the build command from the journal to the cli and let it build there. Once it was build the dashboard will use the build and does not try to build it again. > > from journal after failed build from dashboard > > ``` > Jul 03 11:38:05 esphome esphome[148]: 2025-07-03 11:38:05,904 INFO Running command 'esphome --dashboard compile /root/config/esphome-web-06.yaml > ``` > > paste the build command into a cli on the host > > ``` > esphome --dashboard compile /root/config/esphome-web-06.yaml > ``` > > and run the update/install again after build from cli. Okay that works not for me because then it still uses 2025.6.0 for compiling. Also after compiling with cli in the webinterface is the same error when try to install.
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@OBerghmans commented on GitHub (Jul 4, 2025):

I have the same issue , but coming from 2025.5.2. Looks like the PATH isn't updated correctly everywhere. The dashboard/website shows ESPHome by Open Home Foundation | Fund development | 2025.6.3 Documentation at the bottom, but the compile process shows 2025.5.2.

root@esphome:~/config# esphome --dashboard compile ep-one-basement.yaml
INFO ESPHome 2025.5.2 <<<<<<<<<<<<<<<<
INFO Reading configuration ep-one-basement.yaml...

The service file:

root@esphome:~/config# cat /etc/systemd/system/esphomeDashboard.service
[Unit]
Description=ESPHome Dashboard
After=network.target

[Service]
ExecStart=/opt/esphome/.venv/bin/esphome dashboard /root/config/
Restart=always
User=root

[Install]
WantedBy=multi-user.target

Some path investigation commands:

root@esphome:~/config# which esphome
/usr/local/bin/esphome
root@esphome:~/config# esphome --version
Version: 2025.5.2
root@esphome:~/config# /usr/local/bin/esphome --version
Version: 2025.5.2
root@esphome:~/config# /opt/esphome/.venv/bin/esphome --version
Version: 2025.6.3
<!-- gh-comment-id:3034772559 --> @OBerghmans commented on GitHub (Jul 4, 2025): I have the same issue , but coming from 2025.5.2. Looks like the PATH isn't updated correctly everywhere. The dashboard/website shows `ESPHome by Open Home Foundation | Fund development | 2025.6.3 Documentation` at the bottom, but the compile process shows 2025.5.2. ``` root@esphome:~/config# esphome --dashboard compile ep-one-basement.yaml INFO ESPHome 2025.5.2 <<<<<<<<<<<<<<<< INFO Reading configuration ep-one-basement.yaml... ``` The service file: ``` root@esphome:~/config# cat /etc/systemd/system/esphomeDashboard.service [Unit] Description=ESPHome Dashboard After=network.target [Service] ExecStart=/opt/esphome/.venv/bin/esphome dashboard /root/config/ Restart=always User=root [Install] WantedBy=multi-user.target ``` Some path investigation commands: ``` root@esphome:~/config# which esphome /usr/local/bin/esphome root@esphome:~/config# esphome --version Version: 2025.5.2 root@esphome:~/config# /usr/local/bin/esphome --version Version: 2025.5.2 root@esphome:~/config# /opt/esphome/.venv/bin/esphome --version Version: 2025.6.3 ```
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jul 4, 2025):

try again after merge: #5685

<!-- gh-comment-id:3034814979 --> @MickLesk commented on GitHub (Jul 4, 2025): try again after merge: #5685
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@OBerghmans commented on GitHub (Jul 4, 2025):

Seems to work for me, thanks!

<!-- gh-comment-id:3035251669 --> @OBerghmans commented on GitHub (Jul 4, 2025): Seems to work for me, thanks!
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jul 4, 2025):

Can anyone of you try it again?

<!-- gh-comment-id:3035258699 --> @MickLesk commented on GitHub (Jul 4, 2025): Can anyone of you try it again?
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@SebSeifert commented on GitHub (Jul 4, 2025):

Can anyone of you try it again?

So i updated with "update" in console. Now the flashing via Console Works. In the webinterface i have still:

INFO ESPHome 2025.6.3
INFO Reading configuration /root/config/airgradient-wz.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing airgradient-wz (board: d1_mini; framework: arduino; platform: platformio/espressif8266@4.2.1)
--------------------------------------------------------------------------------
HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
Dependency Graph
|-- ESP8266WiFi @ 1.0
|-- ESP8266mDNS @ 1.2
|-- noise-c @ 0.1.6
|-- Wire @ 1.0
Compiling .pioenvs/airgradient-wz/src/esphome/components/api/api_connection.cpp.o
Compiling .pioenvs/airgradient-wz/src/esphome/components/api/api_frame_helper.cpp.o
*** [.pioenvs/airgradient-wz/src/esphome/components/api/api_connection.cpp.o] sh: No such file or directory
*** [.pioenvs/airgradient-wz/src/esphome/components/api/api_frame_helper.cpp.o] sh: No such file or directory
========================== [FAILED] Took 0.71 seconds ==========================
<!-- gh-comment-id:3036220388 --> @SebSeifert commented on GitHub (Jul 4, 2025): > Can anyone of you try it again? So i updated with "update" in console. Now the flashing via Console Works. In the webinterface i have still: ``` INFO ESPHome 2025.6.3 INFO Reading configuration /root/config/airgradient-wz.yaml... INFO Generating C++ source... INFO Compiling app... Processing airgradient-wz (board: d1_mini; framework: arduino; platform: platformio/espressif8266@4.2.1) -------------------------------------------------------------------------------- HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash Dependency Graph |-- ESP8266WiFi @ 1.0 |-- ESP8266mDNS @ 1.2 |-- noise-c @ 0.1.6 |-- Wire @ 1.0 Compiling .pioenvs/airgradient-wz/src/esphome/components/api/api_connection.cpp.o Compiling .pioenvs/airgradient-wz/src/esphome/components/api/api_frame_helper.cpp.o *** [.pioenvs/airgradient-wz/src/esphome/components/api/api_connection.cpp.o] sh: No such file or directory *** [.pioenvs/airgradient-wz/src/esphome/components/api/api_frame_helper.cpp.o] sh: No such file or directory ========================== [FAILED] Took 0.71 seconds ========================== ```
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jul 4, 2025):

Looks Like an issue from esphome himself?

<!-- gh-comment-id:3036240649 --> @MickLesk commented on GitHub (Jul 4, 2025): Looks Like an issue from esphome himself?
kerem commented 2026-02-26 12:48:05 +03:00
Author
Owner
Copy link

@jsbrich commented on GitHub (Jul 4, 2025):

Updating to uv 0.7.19 seems to have resolved the issue for me as well.

<!-- gh-comment-id:3036884370 --> @jsbrich commented on GitHub (Jul 4, 2025): Updating to uv 0.7.19 seems to have resolved the issue for me as well.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
github-action-update-changelog
github-action-archive-changelog
add-script-trek-1777146237
pr-update-app-files
add-script-fireshare-1777034879
refactor_ghostfolio
add-script-jitsi-meet-1776754982
add-script-apprise-api-1776844606
add-script-transmute-1776844620
fix/update-motd-profile-terminal-500
revert-13797-phs-verbose
revert-13951-hotfix_core_motd
fix/node-options-auto-heap-termix
fix/twingate-connector-real-update
fix/mealie-startsh-missing-after-failed-update
fix/setup-nodejs-upgrade-minor-patch
hotfix_core_motd
fix/uv-venv-clear-update-scripts
add-script-ownfoil-1776758482
add-script-mini-qr-1776757900
add-script-dashy-1776446840
add-script-erpnext-1776807942
add-script-minthcm-1776758021
add-script-anchor-1776753635
add-script-foldergram-1776755549
add-script-gogs-1776754912
copilot/fix-homelable-installation-error
add-script-whodb-1776695185
fix/lxc-stack-upgrade-and-storage-validation
fix/node-version-drift
fix/pangolin-migration-user-roles
fix/pmg-post-install-detection
fix/pangolin-safe-migration
fix/wanderer-pocketbase-wrapper
fix/slskd-config-migration
fix-actualbudget-warnings
add-script-nametag-1776613576
fix/litellm-prisma-generate
fix/clean-orphaned-lvm-cluster-aware
fix/babybuddy-django-settings-module
fix/yamtrack-nginx-update-config
add-script-dagu-1776530655
fix/intel-igc-version-pinning
fix/build-func-pct-create-audit
add-script-igotify-1776263238
add-script-step-ca-1776263572
cleanup_docs_and_co
add-script-github-runner-1776088530
revert-13570-remove_unused_scripts
fix/lyrion-service-name
fix/mealie-v3.15-nuxt4
fix/reitti-v4-refactor
copilot/fix-mealie-version-update
copilot/fix-git-command-not-found
fix/slskd-soularr-lockfile
fix/build-func-tmpdir-leak
refactor/bytestash-data-backup
copilot/fix-bambuddy-update-issue
MickLesk-patch-2
fix/ironclaw-keychain
fix/alpine-wakapi-busybox-df
fix/bentopdf-wasm-coep-headers
fix/crafty-controller-creds-wait
feat/elementsynapse-element-call
fix/metube-pnpm-builds
fix/romm-dynamic-base-path
fix/immich-env-newline
copilot/fix-homarr-update-script
fix/github-token-attempt-zero-crash
fix/filebrowser-quantum-host-warning
fix/homarr-redis-bind-localhost
CrazyWolf13-patch-3
fix/dynamic-os-detection
fix/checkmk-release-security-suffix
fix/bambuddy-ffmpeg-updateable
fix/immich-helmet-csp
core_add_scriptsite_donation_url
add-script-ironclaw-1775649518
fix/proxmox-error-resilience
remove_unused_scripts
CrazyWolf13-patch-1
fix/papra-env-backup-fallback
CrazyWolf13-patch-2
add-script-homelable-1775421958
add-script-openthread-br-1775416012
fix/silent-return-instead-of-exit
fix/nvidia-glx-fallback
fix/npm-ensure-nginx-dirs
fix/motioneye-run-as-root
fix/grist-remove-ee
fix/openwrt-vm-shutdown
fix/core-func-profiled-sourcing
fix/crafty-controller-java25
fix/lxc-updater-apt-pager
fix/npm-openresty-user-config
add-script-netboot-xyz-1775157692
copilot/fix-zigbee2mqtt-update-error
feat/apt-proxy-url-support
fix/cron-updater-path
fix/grist-backup-empty-docs
fix/filebrowser-noauth
feat/core-hardening-proxmoxve
add-script-drawdb-1775060927
fix/build-func-empty-gateway
fix/graylog-max-map-count
fix/koillection-envlocal-newline
add-script-bambuddy-1774853250
MickLesk-patch-1
fix/immich-maintenance-mode-redis-error
fix/npm-unmask-openresty-on-migration
fix/ollama-intel-gpg-error-handling
add-script-yourls-1774732133
add-script-matter-server-1774638379
fix/dispatcharr-pg-port
cron_update_lxc
chore/immich-v2.6.3
add-script-geopulse-1774548387
cdn_improvements
add-script-birdnet-1774535320
fix/tools-func-exit-codes
fix/immich-update-db-hostname
update/frigate-0.17.1
fix/use-absolute-path-for-install
fix/pin-npm-version
shell_safe_fixes
remove_booklore
chore/update-url-community-scripts
komodov2
refactor/turnkey-modernize
add-script-nextexplorer-1774344421
add-script-homebrew-1774342032
fix/shell-security-hardening-v2
improve/build-func-performance-cleanup
fix/build-dns-prefix
fix/anytype-mongodb-wait
fix/frigate-cpu-model-path
copilot/fix-installation-failure-isponsorblocktv
fix/reactive-resume-add-git
copilot/scanopy-fix-apt-configuration-error
add-script-isponsorblocktv-1774009652
add-script-alpine-wakapi-1774008954
fix/coder-code-server-existing-config-and-reachability
add-script-teleport-1773928044
CrazyWolf13-patch-wealthfolio-1
refactor/tools-func-qol
fix/stirling-pdf-jdk-reinstall
fix/pinned-version-wording
MickLesk-patch-10
fix/reactive-resume-v5013
fix/tracearr-update-version-oom
copilot/fix-hdd-space-for-owncast
tremor021-patch-6
pocketbase_bot
disp_fix
fix/tdarr-binary-check-curl-retry
MickLesk-patch-9
refactor/podman-quadlets
alpine-ntfy
refactor/jellyfin
CrazyWolf13-patch-11
feature/autousermod_hwaccell
add-script-split-pro-1773677692
fix/frigate-openvino-fallback
fix/paperless-ngx-default-ram
fix/plex-restart-after-update
fix/gluetun-openvpn-env
MickLesk-patch-8
termix_add_guacd
MickLesk-patch-7
fix/tududi-nodejs-in-update
fix/sparkyfitness-npm-peer-deps
docs/website-metadata-workflow
fix-pbs_microcode
remove_jsons
michelroegl-brunner-patch-4
add-script-test-1773325265
cleanup_workflows
feat/remove-frontend
automated/update-github-versions
feat/mode-generated
fix/n8n-build-essential
fix/sparkyfitness-shared-deps
fix/rocm-path-escaping
fix/storage-validation-cross-node
fix/frigate-nvidia-version-regex
arm64-build-support
readme
michelroegl-brunner-patch-3
fix/coder-code-server-backup
copilot/fix-immich-update-dependency-issue
rust
fix/linkwarden-update-playwright
fix/powerdns-sqlite-permissions
fix/duplicate-nameserver-searchdomain
CrazyWolf13-patch-7
feat/ollama-rocm-support
fix/seerr-migration-update-script
preflight_tests
adgu_fix
2026-04-25
2026-04-24
2026-04-23
2026-04-22
2026-04-21
2026-04-20
2026-04-19
2026-04-18
2026-04-17
2026-04-16
2026-04-15
2026-04-14
2026-04-13
2026-04-12
2026-04-11
2026-04-10
2026-04-09
2026-04-08
2026-04-07
2026-04-06
2026-04-05
2026-04-04
2026-04-03
2026-04-02
2026-04-01
2026-03-31
2026-03-30
2026-03-29
2026-03-28
2026-03-27
2026-03-26
2026-03-25
2026-03-24
2026-03-23
2026-03-22
2026-03-21
2026-03-20
2026-03-19
2026-03-18
2026-03-17
2026-03-16
2026-03-15
2026-03-14
2026-03-13
2026-03-12
2026-03-11
2026-03-10
2026-03-09
2026-03-08
2026-03-07
2026-03-06
2026-03-05
2026-03-04
2026-03-03
2026-03-02
2026-03-01
2026-02-28
2026-02-27
2026-02-26
2026-02-25
2026-02-24
2026-02-23
2026-02-22
2026-02-21
2026-02-20
2026-02-19
2026-02-18
2026-02-17
2026-02-16
2026-02-15
2026-02-14
2026-02-13
2026-02-12
2026-02-11
2026-02-10
2026-02-09
2026-02-08
2026-02-07
2026-02-06
2026-02-05
2026-02-04
2026-02-03
2026-02-02
2026-02-01
2026-01-31
2026-01-30
2026-01-29
2026-01-28
2026-01-27
2026-01-26
2026-01-25
2026-01-24
2026-01-23
2026-01-22
2026-01-21
2026-01-20
2026-01-19
2026-01-18
2026-01-17
2026-01-16
2026-01-15
2026-01-14
2026-01-13
2026-01-12
2026-01-11
2026-01-10
2026-01-09
2026-01-08
2026-01-07
2026-01-06
2026-01-05
2026-01-04
2026-01-03
2026-01-02
2026-01-01
2025-12-31
2025-12-30
2025-12-29
2025-12-28
2025-12-27
2025-12-26
2025-12-25
2025-12-24
2025-12-23
2025-12-22
2025-12-21
2025-12-20
2025-12-19
2025-12-18
2025-12-17
2025-12-16
2025-12-15
2025-12-14
2025-12-13
2025-12-12
2025-12-11
2025-12-10
2025-12-09
2025-12-08
2025-12-07
2025-12-06
2025-12-05
2025-12-04
2025-12-03
2025-12-02
2025-12-01
2025-11-30
2025-11-29
2025-11-28
2025-11-27
2025-11-26
2025-11-25
2025-11-24
2025-11-23
2025-11-22
2025-11-21
2025-11-20
2025-11-19
2025-11-18
2025-11-17
2025-11-16
2025-11-15
2025-11-14
2025-11-13
2025-11-12
2025-11-11
2025-11-10
2025-11-09
2025-11-08
2025-11-07
2025-11-06
2025-11-05
2025-11-04
2025-11-03
2025-11-02
2025-11-01
2025-10-31
2025-10-30
2025-10-29
2025-10-28
2025-10-27
2025-10-26
2025-10-25
2025-10-24
2025-10-23
2025-10-22
2025-10-21
2025-10-20
2025-10-19
2025-10-18
2025-10-17
2025-10-16
2025-10-15
2025-10-14
2025-10-13
2025-10-12
2025-10-11
2025-10-10
2025-10-09
2025-10-08
2025-10-07
2025-10-06
2025-10-05
2025-10-04
2025-10-03
2025-10-02
2025-10-01
2025-09-30
2025-09-29
2025-09-28
2025-09-27
2025-09-26
2025-09-25
2025-09-24
2025-09-23
2025-09-22
2025-09-21
2025-09-20
2025-09-19
2025-09-18
2025-09-17
2025-09-16
2025-09-15
2025-09-14
2025-09-13
2025-09-12
2025-09-11
2025-09-10
2025-09-09
2025-09-08
2025-09-07
2025-09-06
2025-09-05
2025-09-04
2025-09-03
2025-09-02
2025-09-01
2025-08-31
2025-08-30
2025-08-29
2025-08-28
2025-08-27
2025-08-26
2025-08-25
2025-08-24
2025-08-23
2025-08-22
2025-08-21
2025-08-20
2025-08-19
2025-08-18
2025-08-17
2025-08-16
2025-08-15
2025-08-14
2025-08-13
2025-08-12
2025-08-11
2025-08-10
2025-08-09
2025-08-08
2025-08-07
2025-08-06
2025-08-05
2025-08-04
2025-08-03
2025-08-02
2025-08-01
2025-07-31
2025-07-30
2025-07-29
2025-07-28
2025-07-27
2025-07-26
2025-07-25
2025-07-24
2025-07-23
2025-07-22
2025-07-21
2025-07-20
2025-07-19
2025-07-18
2025-07-17
2025-07-16
2025-07-15
2025-07-14
2025-07-11
2025-07-10
2025-07-09
2025-07-08
2025-07-07
2025-07-06
2025-07-05
2025-07-04
2025-07-03
2025-07-02
2025-07-01
2025-06-30
2025-06-29
2025-06-28
2025-06-27
2025-06-26
2025-06-25
2025-06-24
2025-06-23
2025-06-22
2025-06-21
2025-06-20
2025-06-19
2025-06-18
2025-06-17
2025-06-16
2025-06-15
2025-06-14
2025-06-13
2025-06-12
2025-06-11
2025-06-10
2025-06-09
2025-06-08
2025-06-07
2025-06-06
2025-06-05
2025-06-04
2025-06-03
2025-06-02
2025-06-01
2025-05-31
2025-05-30
2025-05-29
2025-05-28
2025-05-27
2025-05-26
2025-05-25
2025-05-24
2025-05-23
2025-05-22
2025-05-21
2025-05-20
2025-05-19
2025-05-18
2025-05-17
2025-05-16
2025-05-15
2025-05-14
2025-05-13
2025-05-12
2025-05-11
2025-05-10
2025-05-09
2025-05-08
2025-05-07
2025-05-06
2025-05-05
2025-05-04
2025-05-03
2025-05-02
2025-05-01
2025-04-30
2025-04-29
2025-04-28
2025-04-27
2025-04-26
2025-04-25
2025-04-24
2025-04-23
2025-04-22
2025-04-20
2025-04-21
2025-04-19
2025-04-18
2025-04-17
2025-04-15
2025-04-16
2025-04-14
2025-04-13
2025-04-12
2025-04-11
2025-04-10
2025-04-09
2025-04-08
2025-04-07
2025-04-06
2025-04-05
2025-04-04
2025-04-03
2025-04-02
2025-04-01
2025-03-31
2025-03-30
2025-03-29
2025-03-28
2025-03-27
2025-03-26
2025-03-25
2025-03-24
2025-03-23
2025-03-22
2025-03-21
2025-03-20
2025-03-19
2025-03-18
2025-03-17
2025-03-16
2025-03-15
2025-03-14
2025-03-13
2025-03-12
2025-03-11
2025-03-10
2025-03-09
2025-03-08
2025-03-07
2025-03-06
2025-03-05
2025-03-04
2025-03-03
2025-03-02
2025-03-01
2025-02-28
2025-02-27
2025-02-26
2025-02-25
2025-02-24
2025-02-23
2025-02-21
2025-02-20
2025-02-19
2025-02-18
2025-02-17
2025-02-16
2025-02-15
2025-02-14
2025-02-13
2025-02-12
2025-02-11
2025-02-10
2025-02-09
2025-02-08
2025-02-07
2025-02-06
2025-02-05
2025-02-04
2025-02-03
2025-02-02
2025-02-01
2025-01-31
2025-01-30
2025-01-29
2025-01-28
2025-01-27
2025-01-26
2025-01-24
2025-01-23
2025-01-22
2025-01-21
2025-01-20
2025-01-19
2025-01-18
2025-01-17
2025-01-16
2025-01-15
2025-01-14
2025-01-13
2025-01-11
2025-01-10
2025-01-09
2025-01-08
2025-01-07
2025-01-06
2025-01-05
2025-01-04
2025-01-03
2025-01-02
2025-01-01
2024-12-31
2024-12-30
2024-12-29
2024-12-28
2024-12-27
2024-12-26
2024-12-25
2024-12-23
2024-12-21
2024-12-20
2024-12-19
2024-12-18
2024-12-17
2024-12-16
2024-12-13
2024-12-12
2024-12-09
2024-12-08
2024-12-07
2024-12-06
2024-12-05
2024-12-04
2024-12-03
2024-12-02
2024-11-30
2024-11-29
2024-11-28
2024-11-27
2024-11-26
2024-11-25
2024-11-24
2024-11-23
Labels
Clear labels   
Implemented in VED waiting push to Main

   
automated

   
breaking change

   
bug

   
bug

   
bugfix

   
deferred

   
delete script

   
dependencies

   
enhancement

   
external

   
feature

   
github

   
help wanted

   
in project pipeline

   
invalid

   
investigation

   
json

   
maintenance

   
needs triage

   
new script

   
new script

   
nice to have

   
not a script issue

   
not planned

   
organization

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
refactor

   
rename script

   
security

   
telemetry

   
update script

   
website

   
wontdo

   
🛑 Failure to comply with the guidelines
No labels
Implemented in VED waiting push to Main
automated
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
question
refactor
rename script
security
telemetry
update script
website
wontdo
🛑 Failure to comply with the guidelines
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#1198
No description provided.