IIC Bus:

SDA:GPIO8
SCL:GPIO18

24C02 EPROM i2c address: 0x50
ADS1115 (4CH ADC): i2c address:0x48
-----------------------

PCF8574: i2c address:0x22

PCF8574->P0 (digital input-1)
PCF8574->P1 (digital input-2)
PCF8574->P2 (digital input-3)
PCF8574->P3 (digital input-4)
PCF8574->P4 (digital input-5)
PCF8574->P5 (digital input-6)
PCF8574->P6 (digital input-7)
PCF8574->P7 (digital input-8)


-----------------

Ethernet (W5500) I/O define:

clk_pin: GPIO1
mosi_pin: GPIO2
miso_pin: GPIO41
cs_pin: GPIO42

interrupt_pin: GPIO43
reset_pin: GPIO44

--------------------
RS485:
RXD:GPIO38
TXD:GPIO39

Tuya module:
RXD:GPIO7
TXD:GPIO6

Tuya network button: Tuya module's P28
Tuya network LED: Tuya module's P16
--------------------
1-Wire-TEP1:GPIO40
1-Wire-TEP2:GPIO17
1-Wire-TEP3:GPIO48
1-Wire-TEP4:GPIO47

--------------------

433MHz RF receiver: GPIO14
IR receiver: GPIO13

DL(download) button: GPIO0
---------------------
ARM CPU RXD: GPIO15
ARM CPU TXD: GPIO16
115200bps
--------------------
SD Card:
SPI-MOSI:GPIO10
SPI-SCK:GPIO11
SPI-MISO:GPIO12
SPI-CS:GPIO9
SPI-CD:GPIO5

   

KinCony KC868-A8 V1.7.1 — Verified DS18B20 Temperature Sensor Pinout and ESPHome Configuration
Hardware: KinCony KC868-A8, PCB revision V1.7.1
Firmware: ESPHome with ESP-IDF framework
Connection: Wired Ethernet (LAN8720)
Sensors tested: Konnected waterproof DS18B20 temperature probes
Verification date: October 19, 2026
1. Overview
The KC868-A8 V1.7.1 has a six-position connector providing four independent DS18B20 temperature sensor data connections, 3.3 V power, and ground.
The connector terminals are not individually labeled on this board revision. The following pinout was established through electrical measurements and successful operation of DS18B20 sensors using ESPHome.
All four temperature inputs have been tested successfully.
2. Verified connector pinout
Terminal numbering begins with the terminal nearest the USB-C connector.
Terminal
Connection
ESP32 GPIO
Verification
1
+3.3 V
—
Continuity to 3V3 test point
2
S4
GPIO33
DS18B20 operational
3
S3
GPIO32
DS18B20 operational
4
S2
GPIO13
DS18B20 operational
5
S1
GPIO14
DS18B20 operational
6
GND
—
Continuity to power supply negative
Physical terminal diagram
The following diagram shows the connector with the USB-C socket at the bottom.

• Terminal 1 showed continuity to the PCB's 3V3 test point.
  
• Terminal 6 showed continuity to power supply ground.
  
• Terminals 2, 3, 4, and 5 each measured approximately 4.7 kΩ to terminal 1.
  

• Terminals 1–5 each measured approximately 3.29 V relative to ground.
  

1. The eight DI1–DI8 optically isolated inputs are separate from the four dedicated temperature inputs.
   
2. GPIO32 and GPIO33 must not be configured simultaneously as binary inputs and OneWire temperature inputs.
   
3. The connector's 3.3 V supply and ground are shared among the temperature sensors.
   
4. Other KC868-A8 board revisions may use different physical terminal arrangements.
   
5. This pinout was verified on PCB revision V1.7.1 and should not be assumed correct for other revisions without checking.
   

Attached Files

  Kincony KC868-a8 pin id.pdf (Size: 445.27 KB / Downloads: 72)

Hello KinCony team,

We have received order #QEDPUML5Q (4x KC868-F24 DC 12 V, 27x KC868-HAv2, 6-gang and 2-gang momentary panels). Each F24 runs ESPHome with the kc868_ha component and has its own HAv2 RS485 bus (9600 baud, up to 8 panels). The panels sit in European 60 mm flush-mounted boxes.

We need temperature and humidity at each wall panel for heating control, and we cannot run new cables (the panel cable has no spare cores).

1. We already have KinCony TS sensors (SHT30, RS485 Modbus), but we were told the TS cannot share the HAv2 bus. We would like to understand why.
From your protocol document (KC868-HA protocol v1.06, tid=8624) and our own bus captures: an HAv2 button frame is a Modbus FC16 write addressed to the controller (byte 0 = controller address, default 1), and the register field carries the panel's own HAv2 address (10-99). On the TS, register 0x000A is its own RS485 address and 0x000B its baud rate, and the TS default address is 1, the same as the controller. So a TS on its default address would take every button frame as a write to itself, and the panels with HAv2 address 10 and 11 would overwrite its address and baud rate.
- Is that the reason?
- If every TS is set to its own address of 100+ (never the controller address the HAv2 modules target) and its terminating jumper is off, does the restriction still apply? If yes, what is the reason?
- Do the HAv2 modules (V2 firmware) ignore Modbus frames that are not "03 12 55 BB" frames from the controller?
- If an HAv2 button frame collides with a Modbus poll from the F24, does the HAv2 retry the button event?

2. In thread tid=6966 you mentioned an "HAv2 with SHT30 sensor" as a possible product. Is that available or planned?

3. Could you share the HAv2 V2 firmware source code (AT32F413), or at least the full specification of the V2 private protocol? We would like to add a temperature/humidity reading to the HAv2 frames ourselves. (We have the schematic R485HA_V200.pdf from tid=5840.)

4. The HAv2 has the P3 terminating resistor jumper. Does the F24 also have built-in 120 ohm termination on its RS485 port, or should we fit an external resistor there?

Thank you,
swisstmack25

I found a reproducible problem with an SHT30/SHT31 sensor on KC868-A16v3 running KCS v3.27.2.
Hardware:

• KC868-A16v3
  
• KCS v3.27.2
  
• KinCony SHT30 temperature/humidity sensor
  
• I2C address 68 decimal (0x44)
  

1. Power off the whole A16v3 (12 V supply).
   
2. Power it on again.
   
3. SHT30 data appears immediately and works normally.
   
4. In the KCS web interface select Reboot.
   
5. After the reboot the SHT30 is no longer available and the log reports I2C NACK / sht31 error.
   
6. Remove 12 V power completely and power the A16v3 again.
   
7. SHT30 works immediately again.
   

Good morning
I had to replace my kc868-H32B board (which worked for more than 4 years without problems) with the new kc868-32 board. The problem is that when I press the inputs a few times or turn the outputs on and off, the board loses connection (I observe this from the board's web server). The installed firmware is v2.2.14, and only the TCP server is active.
I had already reported this problem in the past with the kc868-a8 board and it seemed to be resolved, but that one also used to freeze often.
I can't understand where the problem is.
Do you have any suggestions or software to test this problem?
Thank you

Hi,

I wanted to use KCS firmware and IFTTT to control a relay on and off, by using an adc input from a potentiometer which would act as the temp setpoint, then if actual temp measured by temp sensor was below the adc setpoint, it switches the relay on.   Problem seems to be you cannot use the actual adc value in ifttt to comapre to the temp sensor value(unless you tell me otherwise).  So it looks like I will have to use arduino code.  So my question would be how do i then monitor all the inputs, outputs, sdcvalues  and temp sensors etc.  Do I have to use home assistant or arduino web server Tasmota etc ??  no isea what is the best way to do this ?

TIA

install home assistant on PI5R16 , following the steps , in pi imager i can't see my SSD ( it's new and it is 256GB ) , any idea ? smal sd card is possible this is fine

Hello,
Let me start from the biegining.
I bought last year one KC868-AI and configured with HA on RPi5 and it works till now on firmware 2.2.18.
Last week I got two new boards for my new project I set one up on 2.2.21 firmware, also I got new RPI5 with HA flashed on it.
My problem is that I can't connect it to Home Assistant becase it can't see KC board by mDNS.
HA can see the board becase on ESP add on it has "Available" status.
KC works with static IP 192.168.1.230
I can't add manually Integration because I get this:

"Unable to connect to the ESPHome device. Make sure the device’s YAML configuration includes an `api` section."
Of course there's a line for API in the code. 
I can ping KC board from Terminal in HA, I can log on to the board, but HA can't find it.
New RPi and KC boards are in same network. New set up of HA can find old board by mDNS, it is finding also all of my hardware by mDNS just not this board so it seems it's not the network.

Solutions I tried:
Downgrading to 2.2.18,
Changing name of the board in code,
Setting up new network on different TP-link router,
Setting up API without password in code,
Reseting compilation environment,
Uploading simple configuration with just few lines,
Changing port in yaml and tried to connect on different port,

Nothing worked. Need help, any solution?
I uploaded yaml in ZIP. Don't worry about encrypion keys, I'll change them later.

Attached Files

Image(s)
   

  868aidev1.zip (Size: 4.18 KB / Downloads: 54)

Hi ,

just got my board working now but I cannot use the tuya app.  Whenever i scan the QR code from within KCS I just get the message 'Device_already_bind' (see pic)  and therefore the board does appear in the app so rendering app of no use.  The licence is all enabled in KCS (see pic).  Thanks for your help.

Attached Files

Thumbnail(s)