+- Smart Home Automation Forum (https://www.kincony.com/forum)
+-- Forum: Technical Support (https://www.kincony.com/forum/forumdisplay.php?fid=20)
+--- Forum: KC868-A16v3 (https://www.kincony.com/forum/forumdisplay.php?fid=68)
+--- Thread: KC868-A16v3 ESPHome yaml for home assistant (/showthread.php?tid=7615)
Pages:
1
2
KC868-A16v3 ESPHome yaml for home assistant - admin - 02-15-2025
Code:
esphome:
name: a16v3
friendly_name: a16v3
platformio_options:
board_build.flash_mode: dio
esp32:
board: esp32-s3-devkitc-1
framework:
type: esp-idf
# Enable logging
logger:
hardware_uart: USB_SERIAL_JTAG
api:
ethernet:
type: W5500
clk_pin: GPIO42
mosi_pin: GPIO43
miso_pin: GPIO44
cs_pin: GPIO15
interrupt_pin: GPIO2
reset_pin: GPIO1
i2c:
- id: bus_a
sda: 9
scl: 10
scan: true
frequency: 400kHz
# Example configuration entry
pcf8574:
- id: 'pcf8574_hub_out_1' # for output channel 1-8
address: 0x24
- id: 'pcf8574_hub_out_2' # for output channel 9-16
address: 0x25
- id: 'pcf8574_hub_in_1' # for input channel 1-8
address: 0x21
- id: 'pcf8574_hub_in_2' # for input channel 9-16
address: 0x22
uart:
- id: uart_1
baud_rate: 9600
debug:
direction: BOTH
dummy_receiver: true
after:
timeout: 10ms
tx_pin: 16
rx_pin: 17
switch:
- platform: uart
uart_id: uart_1
name: "RS485 Button"
data: [0x11, 0x22, 0x33, 0x44, 0x55]
- platform: gpio
name: "a16v3_output1"
pin:
pcf8574: pcf8574_hub_out_1
number: 0
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output2"
pin:
pcf8574: pcf8574_hub_out_1
number: 1
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output3"
pin:
pcf8574: pcf8574_hub_out_1
number: 2
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output4"
pin:
pcf8574: pcf8574_hub_out_1
number: 3
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output5"
pin:
pcf8574: pcf8574_hub_out_1
number: 4
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output6"
pin:
pcf8574: pcf8574_hub_out_1
number: 5
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output7"
pin:
pcf8574: pcf8574_hub_out_1
number: 6
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output8"
pin:
pcf8574: pcf8574_hub_out_1
number: 7
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output9"
pin:
pcf8574: pcf8574_hub_out_2
number: 0
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output10"
pin:
pcf8574: pcf8574_hub_out_2
number: 1
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output11"
pin:
pcf8574: pcf8574_hub_out_2
number: 2
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output12"
pin:
pcf8574: pcf8574_hub_out_2
number: 3
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output13"
pin:
pcf8574: pcf8574_hub_out_2
number: 4
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output14"
pin:
pcf8574: pcf8574_hub_out_2
number: 5
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output15"
pin:
pcf8574: pcf8574_hub_out_2
number: 6
mode: OUTPUT
inverted: true
- platform: gpio
name: "a16v3_output16"
pin:
pcf8574: pcf8574_hub_out_2
number: 7
mode: OUTPUT
inverted: true
binary_sensor:
- platform: gpio
name: "a16v3_input1"
pin:
pcf8574: pcf8574_hub_in_1
number: 0
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input2"
pin:
pcf8574: pcf8574_hub_in_1
number: 1
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input3"
pin:
pcf8574: pcf8574_hub_in_1
number: 2
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input4"
pin:
pcf8574: pcf8574_hub_in_1
number: 3
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input5"
pin:
pcf8574: pcf8574_hub_in_1
number: 4
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input6"
pin:
pcf8574: pcf8574_hub_in_1
number: 5
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input7"
pin:
pcf8574: pcf8574_hub_in_1
number: 6
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input8"
pin:
pcf8574: pcf8574_hub_in_1
number: 7
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input9"
pin:
pcf8574: pcf8574_hub_in_2
number: 0
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input10"
pin:
pcf8574: pcf8574_hub_in_2
number: 1
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input11"
pin:
pcf8574: pcf8574_hub_in_2
number: 2
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input12"
pin:
pcf8574: pcf8574_hub_in_2
number: 3
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input13"
pin:
pcf8574: pcf8574_hub_in_2
number: 4
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input14"
pin:
pcf8574: pcf8574_hub_in_2
number: 5
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input15"
pin:
pcf8574: pcf8574_hub_in_2
number: 6
mode: INPUT
inverted: true
- platform: gpio
name: "a16v3_input16"
pin:
pcf8574: pcf8574_hub_in_2
number: 7
mode: INPUT
inverted: true
- platform: gpio
name: "A16v3 IO47"
pin:
number: 47
inverted: true
- platform: gpio
name: "A16v3 IO48"
pin:
number: 48
inverted: true
- platform: gpio
name: "A16v3 IO38"
pin:
number: 38
inverted: true
- platform: gpio
name: "A16v3 IO39"
pin:
number: 39
inverted: true
- platform: gpio
name: "A16v3 IO40"
pin:
number: 40
inverted: true
- platform: gpio
name: "A16v3 IO41"
pin:
number: 41
inverted: true
- platform: gpio
name: "A16v3 DW"
pin:
number: 0
inverted: true
sensor:
- platform: adc
pin: 4
name: "A16v3 A1 Voltage"
update_interval: 5s
attenuation: 11db
filters:
- lambda:
if (x >= 3.11) {
return x * 1.60256;
} else if (x <= 0.15) {
return 0;
} else {
return x * 1.51;
}
- platform: adc
pin: 6
name: "A16v3 A2 Voltage"
update_interval: 5s
attenuation: 11db
filters:
# - multiply: 1.51515
- lambda:
if (x >= 3.11) {
return x * 1.60256;
} else if (x <= 0.15) {
return 0;
} else {
return x * 1.51;
}
- platform: adc
pin: 7
name: "A16v3 A3 Current"
update_interval: 5s
unit_of_measurement: mA
attenuation: 11db
filters:
- multiply: 6.66666666
- platform: adc
pin: 5
name: "A16v3 A4 Current"
update_interval: 5s
unit_of_measurement: mA
attenuation: 11db
filters:
- multiply: 6.66666666
web_server:
port: 80
# font:
# - file: "gfonts://Roboto"
# id: roboto
# size: 20
# display:
# - platform: ssd1306_i2c
# i2c_id: bus_a
# model: "SSD1306 128x64"
# address: 0x3C
# lambda: |-
# it.printf(0, 0, id(roboto), "A16v3");
A16v3-ESPHome.txt (Size: 7.81 KB / Downloads: 827)
RE: KC868-A16v3 ESPHome yaml for home assistant - twostar - 02-15-2025
Where can I get more information about the v3? There's a web page for it but it's not in the store, no indication of pricing or availability, and no comments in the forum from anyone using it.
RE: KC868-A16v3 ESPHome yaml for home assistant - admin - 02-15-2025
just released on today, tomorrow will upload to our online store.
RE: KC868-A16v3 ESPHome yaml for home assistant - Minty - 03-04-2025
Please can you provide iguidence/nformation on configuring the RF 433mhz receiver/transmitter.
I have tried:
remote_transmitter:
pin:
number: GPIO18
carrier_duty_percent: 100%
remote_receiver:
pin:
number: GPIO8
But that results in :
Remote Receiver:
[10:52:38][C][remote_receiver.esp32:065]: Pin: GPIO8
[10:52:38][C][remote_receiver.esp32:070]: Channel: 1
[10:52:38][C][remote_receiver.esp32:071]: RMT memory blocks: 3
[10:52:38][C][remote_receiver.esp32:072]: Clock divider: 80
[10:52:38][C][remote_receiver.esp32:074]: Tolerance: 25%
[10:52:38][C][remote_receiver.esp32:075]: Filter out pulses shorter than: 50 us
[10:52:38][C][remote_receiver.esp32:076]: Signal is done after 10000 us of no changes
[10:52:38][E][remote_receiver.esp32:079]: Configuring RMT driver failed: ESP_ERR_INVALID_ARG (in rmt_config)
[10:52:38][E][component:082]: Component remote_receiver is marked FAILED
If I change remote_receiver to :remote_receiver:
pin:
number: GPIO8
inverted: true
rmt_channel: 4
The error is gone. However the data received by the RF shown in the logs is different from the data received via a KC868-A16 logs for the same transmitting device (door sensor):
KC868-A16v3 RF Logs:
[11:01:52][I][remote.pronto:231]: Received Pronto: data=
[11:01:52][I][remote.pronto:233]: 0000 006D 0019 0000 000D 0027 000C 0027 000C 0027 0028 000B 0028 000B 000C 0027 000C 0027 000C 0027 000C 0027 0028 000B 0028 000B 000C 0027 0028 000B 0028 000B 0028 000B 000C 0027 000C 0027 000C 0027 000C 0027 000D 0027 0028 000B
[11:01:52][I][remote.pronto:233]: 0028 000B 0028 000B 000C 0027 000C 0181
KC868-A16RF Logs:
[11:04:50][I][remote.pronto:231]: Received Pronto: data=
[11:04:50][I][remote.pronto:233]: 0000 006D 0019 0000 000B 0029 000B 0029 000B 0028 0026 000D 0026 000D 000A 0029 000B 0029 000A 0029 000B 0028 0026 000D 0026 000D 000B 0028 0026 000D 0026 000D 0026 000D 000B 0029 000B 0028 000B 0028 000B 0028 000B 0028 0027 000D
[11:04:50][I][remote.pronto:233]: 0026 000D 0026 000D 000B 0029 000B 0181
[11:04:50][I][remote.rc_switch:261]: Received RCSwitch Raw: protocol=1 data='000110000110111000001110'
As you can see the remote.rc_switch data is missing in the V3 data??? Is this expected behaviour?
Is the config correct?
Many thanks
RE: KC868-A16v3 ESPHome yaml for home assistant - admin - 03-05-2025
you can try to use my code to test:
Code:
remote_receiver:
pin: 8
rmt_channel: 4
dump:
- rc_switch
tolerance: 50%
filter: 250us
idle: 2ms
buffer_size: 32kBtested with A16v3 PCB:
RE: KC868-A16v3 ESPHome yaml for home assistant - Minty - 03-05-2025
I have resolved the issue - I needed to clear build cache files, then re-flash. Then everything started to work as expected.
I suspect that because I have two boards (original version & V3) the existing cache files were conflicting...
Also the config yaml in the first post includes :
framework:
type: esp-idf
According to info here https://esphome.io/components/remote_receiver.html - the setting 'rmt_channel' is only supported in ESP32 Arduino configuration not ESP32-IDF config...
RE: KC868-A16v3 ESPHome yaml for home assistant - admin - 03-05-2025
yes, it's ok.
RE: KC868-A16v3 ESPHome yaml for home assistant - phiten - 03-14-2025
The PCF8574 addresses for the input are swapped so XO1 is input9. The correct config is the following:
Code:
pcf8574:
- id: 'pcf8574_hub_out_1' # for output channel 1-8
address: 0x24
- id: 'pcf8574_hub_out_2' # for output channel 9-16
address: 0x25
- id: 'pcf8574_hub_in_1' # for input channel 1-8
address: 0x22
- id: 'pcf8574_hub_in_2' # for input channel 9-16
address: 0x21RE: KC868-A16v3 ESPHome yaml for home assistant - sserry - 07-27-2025
Hello,
I'm getting in the logs continuously the message: "E rmt: user buffer too small, received symbols truncated" when I use following yaml code
remote_receiver:
pin: 8
dump:
- rc_switch
tolerance: 50%
filter: 250us
idle: 2ms
buffer_size: 32kB
Does someone know the solution please?
Thanks
RE: KC868-A16v3 ESPHome yaml for home assistant - admin - 07-27-2025
if you use RF function, we suggest to use KCS v3 firmware. ESPHome not very well for RF.