Esphome compilation on windows desktop with samba share to HA server fails

ESPHome
1

After setting the compile_process_limit: 1 in the yaml file my raspi 4 (2 GB) compile stable, but it takes a long time.

So I tried to move the compilation to my windows desktop. I installed the addon samba share on my HA system to be able to access the directory config\esphome which worked fine.

I was able to run the syntax validation at command line : esphome config “samba file share”

But running the compilation I get an error : UNC path not supported
I do not know what that means or how I can prevent it

PS C:\Users\PC RUDI 2019> esphome run \\192.168.178.55\config\esphome\d1mini.yaml
INFO ESPHome 2025.5.2
INFO Reading configuration \\192.168.178.55\config\esphome\d1mini.yaml...
INFO Generating C++ source...
INFO Core config, version or integrations changed, cleaning build files...
INFO Compiling app...
Processing d1mini (board: esp01_1m; framework: arduino; platform: platformio/[email protected])
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Library Manager: Installing esphome/ESPAsyncTCP-esphome @ 2.0.0
INFO Installing esphome/ESPAsyncTCP-esphome @ 2.0.0
Unpacking  [####################################]  100%
Library Manager: [email protected] has been installed!
INFO [email protected] has been installed!
Library Manager: Installing esphome/ESPAsyncWebServer-esphome @ 3.3.0
INFO Installing esphome/ESPAsyncWebServer-esphome @ 3.3.0
Unpacking  [####################################]  100%
Library Manager: [email protected] has been installed!
INFO [email protected] has been installed!
Library Manager: Resolving dependencies...
INFO Resolving dependencies...
Library Manager: Installing esphome/noise-c @ 0.1.6
INFO Installing esphome/noise-c @ 0.1.6
Unpacking  [####################################]  100%
Library Manager: [email protected] has been installed!
INFO [email protected] has been installed!
Library Manager: Resolving dependencies...
INFO Resolving dependencies...
Library Manager: Installing esphome/libsodium @ 1.10018.4
INFO Installing esphome/libsodium @ 1.10018.4
Unpacking  [####################################]  100%
Library Manager: [email protected] has been installed!
INFO [email protected] has been installed!
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif8266/esp01_1m.html
PLATFORM: Espressif 8266 (4.2.1) > Espressif Generic ESP8266 ESP-01 1M
HARDWARE: ESP8266 80MHz, 80KB RAM, 1MB Flash
PACKAGES:
 - framework-arduinoespressif8266 @ 3.30102.0 (3.1.2)
 - tool-esptool @ 1.413.0 (4.13)
 - toolchain-xtensa @ 2.100300.220621 (10.3.0)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ off, Compatibility ~ soft
Found 41 compatible libraries
Scanning dependencies...
Dependency Graph
|-- ESPAsyncTCP-esphome @ 2.0.0
|-- ESPAsyncWebServer-esphome @ 3.3.0
|-- DNSServer @ 1.1.1
|-- ESP8266WiFi @ 1.0
|-- ESP8266mDNS @ 1.2
|-- noise-c @ 0.1.6
Building in release mode
Compiling .pioenvs\d1mini\src\esphome\components\adc\adc_sensor_common.cpp.o
"\\192.168.178.55\config\esphome\.esphome\build\d1mini"
CMD.EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis gestartet.
UNC-Pfade werden nicht unterst\x81tzt.
Stattdessen wird das Windows-Verzeichnis als aktuelles Verzeichnis gesetzt.
xtensa-lx106-elf-g++: error: src\esphome\components\adc\adc_sensor_common.cpp: No such file or directory
xtensa-lx106-elf-g++: fatal error: no input files
compilation terminated.
*** [.pioenvs\d1mini\src\esphome\components\adc\adc_sensor_common.cpp.o] Error 1
================================================================================== [FAILED] Took 31.70 seconds ==================================================================================
2

It complains about an UNC path (\\host\share\path format). So I would try to map a drive and use that. But why would you want your stuff on the driver where HA lives in the first place? HA doesn’t need them. As long as you back the yaml up (which you should do with any system worth while) you are fine.

1 Like
3

Thank you very much for your notice - mapping a drive solved the problem. I did not know, that HA doesn’t need the config files. My opinion was also to have all the config files within the HA Backup.

1 Like
4

Things make a lot more sense once you change your mindset to realize that the HA host is the production machine receiving the data from the ESPHome device. You can develop, compile and send OTA updates to the ESPHome device from whatever development platform you have handy (in your case, your Windows desktop.)

I still keep the ESPHome add-on in HA, and I even synch the .yaml “source” files. But I haven’t even started the add-on in months, never mind actually use it for anything.

Oh, and you should probably give credit where credit is due for the solution in this thread, not mark your own post.

5

Vielen Dank für den Hinweis. Es war nicht meine Absicht, den Lösungshinweis nicht zu würdigen. Dafür möchte ich mich ausdrücklich entschuldigen und habe das jetzt nachgeholt. In Zukunft werde ich verstärkt darauf achten.