RE: KC868-A32 configure for ESPhome - nwells - 03-04-2023
(03-03-2023, 10:34 AM)admin Wrote: about I2C bus setting in ESPHome, there ia a "frequency" setting.
details see here: https://esphome.io/components/i2c.html
I tried increaing (and lowering) to a wide range of frequencies and none of them worked.
Using a multimeter I can touch the various GPIO and they trigger as expected.
When originally testing on a small ESP32 we had to add a resistor from the 3V connector to the GPIO the PIR was connected to in order for it is register. Does that help clarify what we might need to do with the A32 board?
RE: KC868-A32 configure for ESPhome - admin - 03-04-2023
do you want to send RF or IR signal?
RE: KC868-A32 configure for ESPhome - nwells - 03-04-2023
(03-04-2023, 12:48 AM)admin Wrote: do you want to send RF or IR signal?
Send IR signal.
To clarify, there are two issues I'm trying to resolve:
1. Using a radio_transmitter - I can't select the pcf8574 for the pin
2. None of the 7 PIR sensors I have connected are reporting a signal
The main one I'd like to get resolve is the PIR sensors. I've tried adjusting the frequency setting on the i2c settings but nothing worked. I was only trying randomly though - is there a specific frequency it would need to be set to and, if so, how would I find that out?
RE: KC868-A32 configure for ESPhome - admin - 03-04-2023
1. PCF8574 GPIO can't use for send IR signal. i have told you set the IIC bus frequency is for testing IR, now it confirmed, can't use by PCF8574 GPIO, if you want to use A32 send IR signal, chose a free GPIO for ESP32, then you can have a testing. i don't know your IR sender module circuit, maybe it only need a ESP32 GPIO connect to it directly.
2. you can test short digital input with GND for trigger, if it's ok in ESPHome. i think you can set the PIR, usually open it, have a "NC" or "NO" jumper. maybe you need to change it, just let it dry contact output, chose "NO".
KC868-A32 configure for ESPhome - Uart - REVELAS - 12-24-2023
Hello,
please, which pins are for ModBus comunications on this board?
uart:
id: mod_bus
tx_pin: ?
rx_pin: ?
Thank you very much for the answer.
Ladislav
RE: KC868-A32 configure for ESPhome - admin - 12-24-2023
RS485:
RXD:GPIO16
TXD:GPIO14
modbus by RS485
RE: KC868-A32 configure for ESPhome - REVELAS - 12-27-2023
(12-24-2023, 11:32 AM)admin Wrote: RS485:
RXD:GPIO16
TXD:GPIO14
modbus by RS485
Thank you very much!
RE: KC868-A32 configure for ESPhome - gigios - 09-04-2025
Yesterday I received my first Kincony KC868-A32 board and tried to install ESPHome.
I initially used the configuration described in the first post, but I had to make some changes as it was no longer compatible with the new version of ESPHome.
The first operation I performed after saving the configuration was validation, where the following warning was displayed:
Code: INFO ESPHome 2025.8.2
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 it possible to change the PIN to avoid the warning?
Is this a warning that can be ignored?
The changes made in the original example are:
1. The platform and Framework
From:
Code: esphome:
name: a32
platform: ESP32
board: esp32dev
To:
Code: esphome:
name: kc868-a32
friendly_name: KC868-A32
esp32:
board: esp32dev
framework:
type: esp-idf
version: recommended
2. Added the Wifi (commented in my case because I use Ethernet) and Ethernet configuration and enabled the Web Server to test the configuration:
Code: # Wifi section disabled to use Enthernet
#wifi:
# ssid: !secret wifi_ssid
# password: !secret wifi_password
## Enable fallback hotspot (captive portal) in case wifi connection fails
# ap:
# ssid: "Kc868-A32 Fallback Hotspot"
# password: "GmVxfzYtDqBl"
#captive_portal:
# Ethernet section used instead of Wi-Fi
# Ethernet Example configuration entry (It's possible to use only WIFI or only Ethernet, not both)
ethernet:
type: LAN8720
mdc_pin: GPIO23
mdio_pin: GPIO18
clk:
pin: GPIO17
mode: CLK_OUT
phy_addr: 0
manual_ip: # Recommended for router compatibility
static_ip: 192.168.1.183
gateway: 192.168.1.1
subnet: 255.255.255.0
dns1: 8.8.8.8 # DNS primary
dns2: 8.8.4.4 # DNS secondary
# Alternative debug and OTA web server
web_server:
port: 80
version: 2
include_internal: true
3. Changed the attenuation value for the adc from 11db to 12db
From:
Code: - platform: adc
pin: 39
name: "analog-1"
update_interval: 10s
attenuation: 11db
- platform: adc
pin: 34
name: "analog-2"
update_interval: 10s
attenuation: 11db
- platform: adc
pin: 36
name: "analog-3"
update_interval: 10s
attenuation: 11db
- platform: adc
pin: 35
name: "analog-4"
update_interval: 10s
attenuation: 11db
To:
Code: - 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
It might make sense to update the first post with the latest changes to the latest version of ESPHome!
RE: KC868-A32 configure for ESPhome - admin - 09-04-2025
thanks share your code.
RE: KC868-A32 configure for ESPhome - gigios - 09-04-2025
Ok, this is my current code with very small changes and update to use ESPHome 2025.8.3!
I have split the code in two post because I receive the error for the message too long:
Code: esphome:
name: kc868-a32
friendly_name: KC868-A32
esp32:
board: esp32dev
framework:
type: esp-idf
version: recommended
# Enable logging
logger:
# level: VERBOSE
# Enable Home Assistant API
api:
ota:
- platform: esphome
password: "ota_password"
safe_mode:
reboot_timeout: 10min # Longer Timeout
num_attempts: 3 # Multiple attempts
# ________________________________________________________________________________
# Network Configuration
# --- WiFi
#wifi:
# ssid: !secret wifi_ssid
# password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
# ap:
# ssid: "Kc868-A32 Fallback Hotspot"
# password: "ap_password"
#captive_portal:
# --- Ethernet
# Ethernet configuration entry (It's possible to use only WIFI or only Ethernet, not both)
ethernet:
type: LAN8720
mdc_pin: GPIO23
mdio_pin: GPIO18
clk:
pin: GPIO17
mode: CLK_OUT
phy_addr: 0
manual_ip: # Recommended for router compatibility
static_ip: 192.168.1.183
gateway: 192.168.1.254
subnet: 255.255.255.0
dns1: 8.8.8.8 # Primary DNS
dns2: 8.8.4.4 # Secondary DNS
# ________________________________________________________________________________
# Alternative debug and OTA web server
web_server:
port: 80
version: 2
include_internal: true
# ________________________________________________________________________________
# Syncronize the time with the Home Assistant
time:
- platform: homeassistant
id: homeassistant_time
timezone: Europe/Rome
# ________________________________________________________________________________
# Example configuration entry
i2c:
- id: bus_a
sda: 15
scl: 13
scan: true
frequency: 100kHz # Lower frequency for stability
- id: bus_b
sda: 4
scl: 5
scan: true
frequency: 100kHz # Lower frequency for stability
# ________________________________________________________________________________
# Example configuration entry
pcf8574:
- id: 'pcf8574_hub_out_1' # for output channel 1-8
i2c_id: bus_a
address: 0x24
- id: 'pcf8574_hub_out_2' # for output channel 9-16
i2c_id: bus_a
address: 0x25
- id: 'pcf8574_hub_out_3' # for output channel 17-24
i2c_id: bus_a
address: 0x21
- id: 'pcf8574_hub_out_4' # for output channel 25-32
i2c_id: bus_a
address: 0x22
- id: 'pcf8574_hub_in_1' # for input channel 1-8
i2c_id: bus_b
address: 0x24
- id: 'pcf8574_hub_in_2' # for input channel 9-16
i2c_id: bus_b
address: 0x25
- id: 'pcf8574_hub_in_3' # for input channel 17-24
i2c_id: bus_b
address: 0x21
- id: 'pcf8574_hub_in_4' # for input channel 25-32
i2c_id: bus_b
address: 0x22
# ________________________________________________________________________________
# Individual outputs
switch:
- platform: gpio
name: "relay1"
pin:
pcf8574: pcf8574_hub_out_1
number: 0
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay2"
pin:
pcf8574: pcf8574_hub_out_1
number: 1
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay3"
pin:
pcf8574: pcf8574_hub_out_1
number: 2
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay4"
pin:
pcf8574: pcf8574_hub_out_1
number: 3
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay5"
pin:
pcf8574: pcf8574_hub_out_1
number: 4
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay6"
pin:
pcf8574: pcf8574_hub_out_1
number: 5
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay7"
pin:
pcf8574: pcf8574_hub_out_1
number: 6
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay8"
pin:
pcf8574: pcf8574_hub_out_1
number: 7
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay9"
pin:
pcf8574: pcf8574_hub_out_2
number: 0
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay10"
pin:
pcf8574: pcf8574_hub_out_2
number: 1
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay11"
pin:
pcf8574: pcf8574_hub_out_2
number: 2
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay12"
pin:
pcf8574: pcf8574_hub_out_2
number: 3
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay13"
pin:
pcf8574: pcf8574_hub_out_2
number: 4
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay14"
pin:
pcf8574: pcf8574_hub_out_2
number: 5
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay15"
pin:
pcf8574: pcf8574_hub_out_2
number: 6
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay16"
pin:
pcf8574: pcf8574_hub_out_2
number: 7
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay17"
pin:
pcf8574: pcf8574_hub_out_3
number: 0
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay18"
pin:
pcf8574: pcf8574_hub_out_3
number: 1
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay19"
pin:
pcf8574: pcf8574_hub_out_3
number: 2
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay20"
pin:
pcf8574: pcf8574_hub_out_3
number: 3
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay21"
pin:
pcf8574: pcf8574_hub_out_3
number: 4
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay22"
pin:
pcf8574: pcf8574_hub_out_3
number: 5
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay23"
pin:
pcf8574: pcf8574_hub_out_3
number: 6
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay24"
pin:
pcf8574: pcf8574_hub_out_3
number: 7
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay25"
pin:
pcf8574: pcf8574_hub_out_4
number: 0
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay26"
pin:
pcf8574: pcf8574_hub_out_4
number: 1
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay27"
pin:
pcf8574: pcf8574_hub_out_4
number: 2
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay28"
pin:
pcf8574: pcf8574_hub_out_4
number: 3
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay29"
pin:
pcf8574: pcf8574_hub_out_4
number: 4
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay30"
pin:
pcf8574: pcf8574_hub_out_4
number: 5
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay31"
pin:
pcf8574: pcf8574_hub_out_4
number: 6
mode: OUTPUT
inverted: true
- platform: gpio
name: "relay32"
pin:
pcf8574: pcf8574_hub_out_4
number: 7
mode: OUTPUT
inverted: true
# Continued in the next post
|