Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
KC868-A32 configure for ESPhome
#21
This is the second part of my code:

Code:
# Continued from previous post

# ________________________________________________________________________________
# Individual inputs
binary_sensor:
  - platform: gpio
    name: "input1"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 0
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input2"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 1
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input3"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 2
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input4"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 3
      mode: INPUT
      inverted: true
     
  - platform: gpio
    name: "input5"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 4
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input6"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 5
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input7"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 6
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input8"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 7
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input9"
    pin:
      pcf8574: pcf8574_hub_in_2
      number: 0
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input10"
    pin:
      pcf8574: pcf8574_hub_in_2
      number: 1
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input11"
    pin:
      pcf8574: pcf8574_hub_in_2
      number: 2
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input12"
    pin:
      pcf8574: pcf8574_hub_in_2
      number: 3
      mode: INPUT
      inverted: true
     
  - platform: gpio
    name: "input13"
    pin:
      pcf8574: pcf8574_hub_in_2
      number: 4
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input14"
    pin:
      pcf8574: pcf8574_hub_in_2
      number: 5
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input15"
    pin:
      pcf8574: pcf8574_hub_in_2
      number: 6
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input16"
    pin:
      pcf8574: pcf8574_hub_in_2
      number: 7
      mode: INPUT
      inverted: true
     
     
  - platform: gpio
    name: "input17"
    pin:
      pcf8574: pcf8574_hub_in_3
      number: 0
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input18"
    pin:
      pcf8574: pcf8574_hub_in_3
      number: 1
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input19"
    pin:
      pcf8574: pcf8574_hub_in_3
      number: 2
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input20"
    pin:
      pcf8574: pcf8574_hub_in_3
      number: 3
      mode: INPUT
      inverted: true
     
  - platform: gpio
    name: "input21"
    pin:
      pcf8574: pcf8574_hub_in_3
      number: 4
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input22"
    pin:
      pcf8574: pcf8574_hub_in_3
      number: 5
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input23"
    pin:
      pcf8574: pcf8574_hub_in_3
      number: 6
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input24"
    pin:
      pcf8574: pcf8574_hub_in_3
      number: 7
      mode: INPUT
      inverted: true
     
  - platform: gpio
    name: "input25"
    pin:
      pcf8574: pcf8574_hub_in_4
      number: 0
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input26"
    pin:
      pcf8574: pcf8574_hub_in_4
      number: 1
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input27"
    pin:
      pcf8574: pcf8574_hub_in_4
      number: 2
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input28"
    pin:
      pcf8574: pcf8574_hub_in_4
      number: 3
      mode: INPUT
      inverted: true
     
  - platform: gpio
    name: "input29"
    pin:
      pcf8574: pcf8574_hub_in_4
      number: 4
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input30"
    pin:
      pcf8574: pcf8574_hub_in_4
      number: 5
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input31"
    pin:
      pcf8574: pcf8574_hub_in_4
      number: 6
      mode: INPUT
      inverted: true
  - platform: gpio
    name: "input32"
    pin:
      pcf8574: pcf8574_hub_in_4
      number: 7
      mode: INPUT
      inverted: true
# ________________________________________________________________________________
# Example configuration entry
sensor:
  # WiFi Signal (anche se usi Ethernet, per debug)
  #- platform: wifi_signal
  #  name: "WiFi Signal"
  #  update_interval: 60s
  - platform: adc
    pin: 39
    name: "analog-1"
    update_interval: 10s
    attenuation: 12db
  - platform: adc
    pin: 34
    name: "analog-2"
    update_interval: 10s
    attenuation: 12db
   
  - platform: adc
    pin: 36
    name: "analog-3"
    update_interval: 10s
    attenuation: 12db
   
  - platform: adc
    pin: 35
    name: "analog-4"
    update_interval: 10s
    attenuation: 12db
Reply
#22
And this is the full file in a zip archive.

[img]data:application/x-zip-compressed;base64,UEsDBBQAAAAIAK52JFu+V8GWrAYAAHgzAAAOAAAAS0M4NjgtQTMyLnlhbWzFm11v0zAUhu8r9T+YcQFIdCx2upXeDRhQAQPxeRk5idtapHZInI3y6zm207X7gNg0CZkmJcfOOa+P7SfRWcbKfClXbDocICQonKDvyeR4MqIEa9O84Eyk2TqybW+e67ZT3TYcwK0EmxtjSYt0iowhZRf2RrjhUhbfdQc41DpnpseIp3NrumBFyaWYooIlcrWCOCzVfu+jM0HjjKFMLhZcLIYDfcKKqW5CGbtg2RR9Pfv47P2ns2v9X8NA0GlZ8lJRodDph9lwQHM+1Z2kokbJCOUZVXNZrKaoHrtVk9OyvJR6GAfQN9pcHgwHJZ2zaCVTkyQQG0upIsVXTFZqioKjFRcI3UdvpQCR6LNtMPmsVhFViq1yVU4RQebQXd9VmeI5KN602mFELR/a5zlTehbQcynmfFEVVEHKbbjRaIS+8Zcczi/5nNv0QvYgBfdKlhRMIW2PtAnarlJ0s702Qx896KvZmNMsi2nyHS2lKnOp0MOE5opfMJTLQtHsEYK8JbRkxgtKpBAs0ergTp6VJiLNraqNroM3Sb0A0cuN+9fW/QF0vDGPNN+dRmivBURWwHSbhjO1ZIVgCq6vzrWibcoQE6pYo4cz9aCEAYAcPUYlUQUDkCJbo2+zlzMkC3Nx5eQxEjDyWKrlI9gwtRECbzbE29PzyQk+0oZVmkQ5h+3w6sPsPSbWxOXWFky0Lck2W2rbcGINZo2i52/fRO+/fNamfLmOaJoWU2QjUFHRLOL5FN087qOP202I5jCMAhYxLGcw5pCAmGdcrW2YUoEhMW6Cp/gwOJ4cBofBhNjWBVXskq532/A4rO+sYj18hMfjw83vkW1KRRlM0eTQ/FxX9qHgKwq5f3H+6aovtn3Dw/B6308wCpHWvbvbVaeZgpmkZjWnLK4WiIoUvf98ii5ZjEpWANuGAziP7LmeMbPsQbYe8JZ9hrJcJFmVsogL4xbwpoqKdSf/01okhRT8F6zgJfzyld6EaglXNyk6HOjWW+jU3KSbPnZWeHrdbBlp2/TZLylgdZ5VhczZk49y1eH4zn7SFeD1rh08HHCc2OEYxXFVRrRenSmFVTuuL5IMLsjmggo7J/Z6XrAfFROJXuVHR99f/7L8v2TFtslsIsjDdudsA8Y7AcOdeOM2w6H/kt08mU/GJ+FOhh/UpmhZxRFAJQoegH6jF67yCkC7pMD+DAWjiR0wTFF0Y3I0xlhZAsl+YkjZX9zjP7l/OgqOnfyP/+qf/FH+yQiHTgGCvwYI/xQAj0cEOwWwvf4Qg4udKeCicQZinxkA53jHeXP+Y5/8g3ey490h+7FP9sF9uOPeIfd3uMdw3en+m4mUX/AUHuX1AinhHRXwnSxvYXqRc6ltm3f7g4JldB0cbF8g4Mwcm32Lbu1W28O8zcZs8yqxfd2AV40P9m3D5EbAk02xdIMvN0F4L0FB+4LIXoJw+4LCvQQRH0HG6KZqvJeq0EeVm6DjvQSN2xd0speg4/YFTfYSdOInyE3SUx9JuAccBUd7KeqAR4EXsnEPQAq8mI37IlLgRW7cA5ICL3TjHpgUeGEb9wClwIvbeC8q+SwmL3qTPsjkhW/SB5m86E16IBP2ojfpi0zYC+GkBzJhL4STHsiEvehNeiAT9qI36YtM2AvhYQ9kwl4ID3sgE/aid9gHmbzoHfZGJi+Ehz2QiXghPOyBTMSL3mEPZCJe9A7bIRMc3VXtt3UtEGDLWjEX8Lcc+COKKGXRXN0ytznPFBeNxa3Z+T7zZOQ4TxMXjaWtFuQ4P2G5aCxstSDH+fHKRWNZa3busoSbNTk/W7loLGq1kCLnBysXjSWtFuQ4P1W5aCxotSDH+ZHKRWM5a3a+XzXLCHJ+mHLRWMxqIT/utSwuGktZbejxwTPuHkDudSwuGstYbRHIvYrFRWMRq40k+WAad88g9woWF40FrDb0+DAa70MhY/RbSz7AJj0AyYfYpAcg+QCbdA8k9/IVF43VK7e15CDKh9qkeyC5l664aKxctaHHB9ikeyC5l624aKxatbaIfKgddk8i95IVF40Vqzb0+JA67IFEPqQO+yKRD67D7knkXqriorFS1YYeH1KH3ZPIvUzFRWOV6k49XX8s+9fPHXcqU/fNx/ToE18IqGA9pCJZMvgUGD4Q5zufg+essF8MPzL37CSw/tje3G7arhK54/egbqnylKr6g+EL/cHw8VF5e0pomux8Kk6eXpseCu7kYlSvl9seA/CoW8w/KYjKDBusOI0bA4V3BcL/EgisDbGO74pFuok1vitW6B8L4vwGUEsBAj8AFAAAAAgArnYkW75XwZasBgAAeDMAAA4AJAAAAAAAAAAgAAAAAAAAAEtDODY4LUEzMi55YW1sCgAgAAAAAAABABgA0UFe6Jod3AEAAAAAAAAAAAAAAAAAAAAAUEsFBgAAAAABAAEAYAAAANgGAAAAAA==[/img]
.zip   KC868-A32 - ESPHome 2025.8.3.zip (Size: 1.83 KB / Downloads: 150)

About my original question, related the warning:

Code:
INFO ESPHome 2025.8.3
INFO Reading configuration /config/esphome/kc868-a32.yaml...
WARNING GPIO15 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins

Is there a solution?
Thanks
Reply
#23
Just ignore these warnings.
Reply
#24
Hello. I received my new KC868-A16 (corrected from A32) today and I am having an issue installing via ESPHome 2025.8.3. This was just installed today with the latest Home Assistant build.

I am using the config posted by the user above: 

esphome:
  name: kc868-a32
  friendly_name: KC868-A32

esp32:
  board: esp32dev
  framework:
    type: esp-idf
    version: recommended


But I am getting installation errors. Can anyone help?

INFO ESPHome 2025.8.3
INFO Reading configuration /config/esphome/a16.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing kc868-a16 (board: esp32dev; framework: espidf; platform: https://github.com/pioarduino/platform-e...ssif32.zip)
--------------------------------------------------------------------------------
INFO Package configuration completed successfully
Library Manager: Installing esphome/noise-c @ 0.1.10
INFO Installing esphome/noise-c @ 0.1.10
Unpacking  [####################################]  100%
Library Manager: noise-c@0.1.10 has been installed!
INFO noise-c@0.1.10 has been installed!
Library Manager: Resolving dependencies...
INFO Resolving dependencies...
Library Manager: Installing esphome/libsodium @ 1.10020.7
INFO Installing esphome/libsodium @ 1.10020.7
Unpacking  [####################################]  100%
Library Manager: libsodium@1.10020.7 has been installed!
INFO libsodium@1.10020.7 has been installed!
INFO Package configuration completed successfully
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
- framework-espidf @ 3.50402.0 (5.4.2)
- tool-cmake @ 3.30.2
- tool-esp-rom-elfs @ 2024.10.11
- tool-esptoolpy @ 5.0.2
- tool-mklittlefs @ 3.2.0
- tool-ninja @ 1.13.1
- tool-scons @ 4.40801.0 (4.8.1)
- toolchain-esp32ulp @ 2.35.0-20220830
- toolchain-xtensa-esp-elf @ 14.2.0+20241119
Reading CMake configuration...
-- Found Git: /usr/bin/git (found version "2.39.5")
-- git rev-parse returned 'fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).'
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- The ASM compiler identification is unknown
-- Found assembler: xtensa-esp32-elf-gcc
-- Warning: Did not find file Compiler/-ASM
-- Configuring incomplete, errors occurred!

fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:571 (__project):
  The CMAKE_C_COMPILER:

    xtensa-esp32-elf-gcc

  is not a full path and was not found in the PATH.

  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)


CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:571 (__project):
  The CMAKE_CXX_COMPILER:

    xtensa-esp32-elf-g++

  is not a full path and was not found in the PATH.

  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)


CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:571 (__project):
  The CMAKE_ASM_COMPILER:

    xtensa-esp32-elf-gcc

  is not a full path and was not found in the PATH.

  Tell CMake where to find the compiler by setting either the environment
  variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)



========================== [FAILED] Took 1.63 seconds ==========================
Reply
#25
take a photo of your PCB. do you use A32 or A32 Pro ?
Reply
#26
Sure here is a photo. My apologies I should have said A16 not A32. Thank you.

   
Reply
#27
here is KC868-A16 ESPHome yaml file: https://www.kincony.com/forum/showthread.php?tid=1628
Reply
#28
Thank you. That code is now invalid and will not install.

INFO ESPHome 2025.8.3
INFO Reading configuration /config/esphome/k868-a16.yaml...
Failed config

esphome: [source /config/esphome/k868-a16.yaml:2]
  name: a16
 
  Please remove the `platform` key from the [esphome] block and use the correct platform component. This style of configuration has now been removed.
  platform: ESP32
  board: esp32dev

The entry at the top needs to be:

esphome:

  name: a16

esp32:
  board: esp32dev

However, I still have these errors on install. It has something to do with xtensa-esp32-elf-g++

INFO ESPHome 2025.8.3
INFO Reading configuration /config/esphome/k868-a16.yaml...
WARNING ? IMPORTANT: This device doesn't have a framework specified!

Currently, ESP32 defaults to the Arduino framework.
This will change to ESP-IDF in ESPHome 2026.1.0.

Note: Newer ESP32 variants (C6, H2, P4, etc.) already use ESP-IDF by default.

Why change? ESP-IDF offers:
  ✨ Up to 40% smaller binaries
  ? Better performance and optimization
  ? Custom-built firmware for your exact needs
  ? Active development and testing by ESPHome developers

Trade-offs:
  ⏱️  Compile times are ~25% longer
  ? Some components need migration

What should I do?
  Option 1: Migrate to ESP-IDF (recommended)
    Add this to your YAML under 'esp32:':
      framework:
        type: esp-idf

  Option 2: Keep using Arduino (still supported)
    Add this to your YAML under 'esp32:':
      framework:
        type: arduino

Need help? Check out the migration guide:
https://esphome.io/guides/esp32_arduino_to_idf.html
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-a...pping-pins
INFO Generating C++ source...
INFO Compiling app...
Processing a16 (board: esp32dev; framework: arduino; platform: https://github.com/pioarduino/platform-e...ssif32.zip)
--------------------------------------------------------------------------------
INFO Package configuration completed successfully
Library Manager: Installing esphome/noise-c @ 0.1.10
INFO Installing esphome/noise-c @ 0.1.10
Unpacking  [####################################]  100%
Library Manager: noise-c@0.1.10 has been installed!
INFO noise-c@0.1.10 has been installed!
Library Manager: Resolving dependencies...
INFO Resolving dependencies...
Library Manager: Installing esphome/libsodium @ 1.10020.7
INFO Installing esphome/libsodium @ 1.10020.7
Unpacking  [####################################]  100%
Library Manager: libsodium@1.10020.7 has been installed!
INFO libsodium@1.10020.7 has been installed!
INFO Package configuration completed successfully
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
- framework-arduinoespressif32 @ 3.2.1
- framework-arduinoespressif32-libs @ 5.4.0+sha.858a988d6e
- tool-esptoolpy @ 5.0.2
- tool-mklittlefs @ 3.2.0
- toolchain-xtensa-esp-elf @ 14.2.0+20241119
Dependency Graph
|-- Networking @ 3.2.1
|-- WiFi @ 3.2.1
|-- ESPmDNS @ 3.2.1
|-- Update @ 3.2.1
|-- noise-c @ 0.1.10
|-- Wire @ 3.2.1
Compiling .pioenvs/a16/lib4c5/Network/NetworkClient.cpp.o
sh: 1: xtensa-esp32-elf-g++: not found
*** [.pioenvs/a16/lib4c5/Network/NetworkClient.cpp.o] Error 127
Compiling .pioenvs/a16/lib4c5/Network/NetworkEvents.cpp.o
sh: 1: xtensa-esp32-elf-g++: not found
*** [.pioenvs/a16/lib4c5/Network/NetworkEvents.cpp.o] Error 127
========================== [FAILED] Took 2.44 seconds ==========================


.zip   k868-a16.yaml.zip (Size: 1.03 KB / Downloads: 145)
Reply
#29
For readers of the forum, I uninstalled ESPHome and reinstalled, which resolved the problem.
Reply
#30
ok, good.
Reply


Forum Jump:


Users browsing this thread:
1 Guest(s)