KC868-M16v2 configure yaml for ESPhome

[admin]

Hello,

I tested the lastest code (with external components from Git) with ESPHome version 2025.7.4 (the latest release), and I'm getting the error shown in the attached screenshot.
It appears that the ADC components are no longer working with the current version of the library.
Could you please take a look?
Is anyone else experiencing the same issue?

when have free time, we will test it with newest esphome.

[sanketgroup]

I am having same issue after upgrading 2025.7

It has completely stopped working after ESPHome HA upgrade 2025.7
Please do the needful urgently.

Code:

[12:22:38]E (496) ADC: CONFLICT! driver_ng is not allowed to be used with the legacy driver
[12:22:38]
[12:22:38]abort() was called at PC 0x40105fdb on core 0
[12:22:38]
[12:22:38]
[12:22:38]Backtrace: 0x40083679:0x3ffe3b30 0x4008dec9:0x3ffe3b50 0x400940c5:0x3ffe3b70 0x40105fdb:0x3ffe3bf0 0x400fc206:0x3ffe3c10 0x40082b8a:0x3ffe3c40 0x400796aa:0x3ffe3c90 |<-CORRUPTED
[12:22:38]
[12:22:38]
[12:22:38]
[12:22:38]
[12:22:38]ELF file SHA256: 110e21ef1
[12:22:38]
[12:22:38]E (516) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
[12:22:38]E (524) esp_core_dump_elf: Elf write init failed!
[12:22:38]E (529) esp_core_dump_common: Core dump write failed with error=-1
[12:22:38]Rebooting...
[12:22:38]ets Jul 29 2019 12:21:46
[12:22:38]
[12:22:38]rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
[12:22:38]configsip: 0, SPIWP:0xee
[12:22:38]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[12:22:38]mode:DIO, clock div:2
[12:22:38]load:0x3fff0030,len:4688
[12:22:38]load:0x40078000,len:15504
[12:22:38]load:0x40080400,len:4
[12:22:38]load:0x40080404,len:3196
[12:22:38]entry 0x400805a4
[12:22:38]E (496) ADC: CONFLICT! driver_ng is not allowed to be used with the legacy driver
[12:22:38]
[12:22:38]abort() was called at PC 0x40105fdb on core 0
[12:22:38]
[12:22:38]
[12:22:38]Backtrace: 0x40083679:0x3ffe3b30 0x4008dec9:0x3ffe3b50 0x400940c5:0x3ffe3b70 0x40105fdb:0x3ffe3bf0 0x400fc206:0x3ffe3c10 0x40082b8a:0x3ffe3c40 0x400796aa:0x3ffe3c90 |<-CORRUPTED
[12:22:38]
[12:22:38]
[12:22:38]
[12:22:38]
[12:22:38]ELF file SHA256: 110e21ef1
[12:22:38]
[12:22:38]E (516) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
[12:22:38]E (524) esp_core_dump_elf: Elf write init failed!
[12:22:38]E (529) esp_core_dump_common: Core dump write failed with error=-1
[12:22:38]Rebooting...
[12:22:38]ets Jul 29 2019 12:21:46
[12:22:38]
[12:22:38]rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
[12:22:38]configsip: 0, SPIWP:0xee
[12:22:38]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[12:22:38]mode:DIO, clock div:2
[12:22:38]load:0x3fff0030,len:4688
[12:22:38]load:0x40078000,len:15504
[12:22:38]load:0x40080400,len:4
[12:22:38]load:0x40080404,len:3196
[12:22:38]entry 0x400805a4
[12:22:38]E (496) ADC: CONFLICT! driver_ng is not allowed to be used with the legacy driver

[admin]

M16v2 or M30 board?

[sanketgroup]

M16v2

---

M16v2

Seems issue with old legacy ADC driver which is not supported by 2025.7 anymore.

[admin]

have tested with ESPHome: 2025.7.5

  M16v2-HA.txt (Size: 9.26 KB / Downloads: 119)

[sanketgroup]

M16v2 or M30 board?

have tested with ESPHome: 2025.7.5

I downloaded this txt file and installed on the board.

But still getting same error.

Code:

[19:36:03]E (492) ADC: CONFLICT! driver_ng is not allowed to be used with the legacy driver
[19:36:03]
[19:36:03]abort() was called at PC 0x40103bef on core 0
[19:36:03]
[19:36:03]
[19:36:03]Backtrace: 0x40083679:0x3ffe3b30 0x4008dec9:0x3ffe3b50 0x400940c5:0x3ffe3b70 0x40103bef:0x3ffe3bf0 0x400f9eaa:0x3ffe3c10 0x40082b8a:0x3ffe3c40 0x400796aa:0x3ffe3c90 |<-CORRUPTED
[19:36:03]
[19:36:03]
[19:36:03]
[19:36:03]
[19:36:03]ELF file SHA256: 96dd0c6d8
[19:36:03]
[19:36:03]E (512) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
[19:36:03]E (520) esp_core_dump_elf: Elf write init failed!
[19:36:03]E (525) esp_core_dump_common: Core dump write failed with error=-1
[19:36:03]Rebooting...
[19:36:03]ets Jul 29 2019 12:21:46
[19:36:03]
[19:36:03]rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
[19:36:03]configsip: 0, SPIWP:0xee
[19:36:03]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[19:36:03]mode:DIO, clock div:2
[19:36:03]load:0x3fff0030,len:4688
[19:36:03]load:0x40078000,len:15504
[19:36:03]load:0x40080400,len:4
[19:36:03]load:0x40080404,len:3196
[19:36:03]entry 0x400805a4

[sanketgroup]

Just to let you know,
I downgraded esphome to 2025.6 on same Home Assistant instance
and it is working very well.

Your and mine both configuration files are working well under 2025.6

But if i upgrade it to above 2025.7, none of the file works and gives previosly shared erorrs.
Another important thing i would like to draw, if you are trying with multiple ESPHOME versions on same instance then you would not have this error.

So try with only one ESPHOME version above 2025.7 on same instance.

So it confirms that 2025.7 this config files have issues.

[admin]

my computer only have one ESPHome version: INFO ESPHome 2025.7.5
see photo.
   
   

[sanketgroup]

I tried this on 3 different machines running latest Home Assistant.

1st Machine: ESPHome 2025.6 running on Home Assistant_1
Result: No issue with M16v2

2nd Machine: ESPHome 2025.7.2 running on Home Assistant_2
Result: Problem, throws an error as shown before

3rd Machine: ESPHome 2025.6 and 2025.7.2 running on Home Assistant_3
Result: No issue with M16v2

Also, the same configuration was working well for many weeks, but suddenly, after upgrading Home Assistant and ESPHome to 2025.7, it stopped working.
(I did not make any changes or upload a new yaml to your device)

Are you running ESPHome on a separate standalone rather than within the Home Assistant add-on?
Because after trying on 3 different machines with different versions, I am sure there is some issue withthe Home Assistant Add-on ESPHome 2025.7

[cignu]

I'm setting up my M16V2
I get this error in ESPHome Device Builder and can't upload the yaml file

Do you have any suggestion?

tnks