Smart Home Automation Forum - Portal

KC868-A4 slide gate retrofit (ESPHome): watchdogs, travel telemetry, full config

Fri, 17 Jul 2026 07:27:42 +0800

Sharing a complete, field-proven ESPHome config for the KC868-A4 running a residential chain-driven slide gate (Eagle 1000 operator chassis with a CO-Z T329 V3.0 replacement control board). It has been in 24/7 outdoor service through Texas summer heat. The full v6 YAML is attached to this post (kc868-a4-slide-gate-v6.txt).

WHAT IT DOES
- Template cover (open/close/stop), each command mapped 1:1 to its own relay pulsing the T329's discrete OP / CL / STP trigger terminals to COM
- 4th relay bypasses the IR safety beam (FSW) for rainy days, with a 10-minute auto-off so you can't forget it
- Reads both travel-limit microswitches + a reed sensor on the gate panel, so the controller knows real position independent of the gate board
- Software auto-close timer (0-600s, adjustable live from HA, 0 = off)
- Control lock switch that blocks network-originated open/close but never STOP
- Monitors the gate board's supply voltage through a resistor divider on an analog input, with a live-tunable calibration multiplier (no reflash to recalibrate)
- Watches the IR transmitter's battery contact through the second analog input

SELF-MONITORING (v6 - the interesting part)
1. Travel-time telemetry: publishes "Last Open Time" / "Last Close Time" sensors on every completed limit-to-limit run. Trend these for chain wear / motor drift. (My gate: open 20-24s, close rock-steady at 21.1-21.3s.)
2. Command Fault sensor: fires if a relay pulse was sent but the gate board never acted on it (origin limit never released). Catches a dead trigger wire / loose COM bond within 10 seconds instead of "why is the gate still open?"
3. Travel Fault sensor: motion started (a limit released - from ANY source, RF remote or wall switch included) but no limit reached within 35s.
4. Limit Switch Fault: both limits active at once = impossible = wiring fault.
5. Chain Fault: close limit reached but the reed says the panel is not at the post = chain slipped/broke (5s debounce).

HARD-WON WIRING / BEHAVIOR NOTES
- Relay COM bond is mandatory: daisy-chain all four relay COMs and bond to the gate board's COM. With only R1 bonded, OPEN works but CLOSE/STOP are silently ignored - a maddening symptom.
- Read the limit switches on the microswitch's SPARE throw, not the gate board's limit sense terminals - many boards back-feed ~5V onto their own sense lines, which the opto reads as a false constant ON.
- The EL357 opto inputs are self-excited: wire passive dry contacts straight to INx + GND. No external voltage, no resistors. They keep reading even with the gate board powered off (as long as COM is bonded).
- Stop-before-reverse: the T329 (and likely similar STC-based boards) silently DISCARDS an OP/CL pulse while the motor is driving the other direction. Proven live: a close command mid-open does nothing - no reversal, no stop. The v6 cover actions pulse STP, wait 700ms, then pulse the direction whenever neither limit is active. If your gate "ignores" commands mid-travel, this is why.
- Don't tap the FSW line directly to an opto input to monitor the beam - on the T329 it idles at 7.3V, too high. Use a divider into an analog input instead (or a small relay).

SETUP
secrets.yaml needs: wifi_ssid, wifi_password, ap_password, api_key, ota_password, web_password. The two http_request buttons point at a Shelly Pro 4PM (Gen2 RPC) that master-switches the gate operator's mains - replace 192.168.1.50 with your Shelly's IP or delete those buttons if you don't have one. GPIO 2/15/5 are ESP32 strapping pins; ESPHome logs a boot warning - expected and harmless here.

Happy to answer questions about the wiring or the watchdog logic.

kc868-a4-slide-gate-v6.txt (Size: 24.86 KB / Downloads: 5)

KC868 A8 + Home Assistant + DS18B20+

Thu, 16 Jul 2026 20:48:56 +0800

Good afternoon! I bought two KC868 A8 and KC868 A16 boards to use with Home Assistant. I found configuration files for these boards on a forum, and all the inputs/outputs work, but I can't connect the sensors. Help please.

Questions on the B4M

Thu, 16 Jul 2026 19:07:11 +0800

I have a bunch of questions about the B4M that I don't see in any of the docs:

What is rated DC V and A range for the MOSFET relays? I'd like to use it for 5-24V, no more than 2A.

Can the B8M relays can handle mixed voltages/references? Like 12V on one relay and 24V on a different one?

What wire gauge size range do the relay terminals accept?

What is the power supply rating (V, A) in the B4M bundle B power supply?

With the KDS v3 firmware: does the B4M will present its relays over the network to Home Assistant (via auto discovery)?

If I connect several DS18B20 temperature sensors to the B4M one wire interfaces will these be automatically presented to Home Assistant as temp sensors across the network or will have to code the Home Assistant presentation and auto-discovery on the B4M?

Thanks for any help.

Ethernet static address

Thu, 16 Jul 2026 09:42:01 +0800

I use a Board KC868-A16 Rev1.6.3 with tasmota firmware-en-a16.bin from here. After installation I have two ip-addresses (via dhcp) one for wifi and one for ethernet.
In the console I can change the wifi adress to a static address with the command ipaddress1 xxx.xxx.xxx.xxx , that works fine.
But how can I change the ethernet-address to a static one?

KCS firmware wishlist

Wed, 15 Jul 2026 20:31:22 +0800

Good afternoon,
I'm using the KC868-A6v2, KC868-A16v2, and KC868-A16v3 boards on KCS, which completely meets my needs.
I like the functionality and practicality of these boards,
but the firmware is inconvenient:
1. The lack of a backup mechanism and external editing of IFTTT rules when updating the version or moving to another board.
2. The lack of double-tap and hold inputs in the MQTT protocol.
I understand that these implementations can be implemented on esphome, but I would like to see them developed for KCS as well.
Thank you for your product.

turn on one relay by mqtt sample on A8v3

Wed, 15 Jul 2026 08:26:13 +0800

  a8v3-mqtt-1.png (Size: 60.2 KB / Downloads: 22)

  a8v3-mqtt-2.png (Size: 137.72 KB / Downloads: 24)

  a8v3-mqtt-3.jpg (Size: 406.16 KB / Downloads: 24)

Request for Type A Project

Tue, 14 Jul 2026 12:19:49 +0800

Hello, I'm Mifta from UPN Jakarta in Indonesia. I would love to develop KC868-A4 for my final project in my campus. The project is about control two shuttle from joystick at the same time It would be very helpful if you could share the sample project for me (In this case, I request sample project for Type A). The previous project i only use 3 ESP32 for controlling 2 shuttle and 1 trolly to move synchronously. If you could share the sample project i will give you updates about my project that maybe can be a new application for KC868-A4

You can reach me through my email: miftahul.jannah@upnvj.ac.id

WhatsApp Image 2026-07-10 at 10.53.20.jpeg (Size: 222.77 KB / Downloads: 22)

KinCony MT4 – 4CH ESP32 DC Motor Driver released

Sat, 11 Jul 2026 11:01:07 +0800

KinCony MT4 ESP32-S3 4 Channel DC Motor Controller
Overview
KinCony MT4 is a professional 4 Channel DC Motor Controller based on the ESP32-S3-WROOM-1 (N16R8) module. It is designed for smart home automation, industrial automation, DIY IoT projects, motorized curtains, electric valves, linear actuators, robotic systems and other DC motor control applications.
MT4 integrates 4 independent DC motor drivers, RS485, 433MHz RF receiver, IR receiver, I²C expansion interface, 1-Wire GPIO, WiFi, Bluetooth, USB-C, and a Tuya WiFi module into one compact DIN Rail controller.
Whether you are a developer, system integrator, or smart home enthusiast, MT4 provides multiple firmware options, including KinCony KCS v3, ESPHome, Tasmota, Arduino, ESP-IDF, and MicroPython.

Features

ESP32-S3-WROOM-1 (N16R8) Dual-Core Processor
4 Channel DC Motor Driver (L298N)
Supports Forward / Reverse / Stop control
Maximum 2A load per motor channel
Built-in WiFi & Bluetooth
Built-in Tuya WiFi module
RS485 interface (Modbus supported by KCS firmware)
USB Type-C programming interface
433MHz RF Receiver
IR Receiver
I²C Expansion Port
2 Channel 1-Wire GPIO
DIN Rail installation with plastic enclosure
Open-source hardware platform
Supports Arduino IDE
Supports ESP-IDF
Supports MicroPython
Supports ESPHome
Supports Tasmota
Home Assistant MQTT Auto Discovery
Apple HomeKit support (KCS v3 firmware)

Applications
KinCony MT4 is suitable for various automation projects, including:

Motorized Curtains
Roller Blinds
Window Openers
Electric Valves
Linear Actuators
Smart Furniture
Automatic Doors
Smart Agriculture
Industrial Automation
DIY IoT Projects
Home Automation Systems

Technical Specifications
Item
SpecificationModel
KinCony MT4
Processor
ESP32-S3-WROOM-1 (N16R8)
Power Supply
DC 12V
Motor Driver
L298N
Motor Outputs
4 Channels
Maximum Motor Current
2A per Channel
Communication
WiFi / Bluetooth
Interfaces
RS485, USB-C, IR Receiver, 433MHz RF Receiver, I²C Expansion
GPIO
2 Channel 1-Wire GPIO
Installation
DIN Rail
PCB Size
87 × 93 mm

Hardware Interfaces
Outputs

4 × DC Motor Outputs
Maximum Load: 2A per channel

Inputs

2 × 1-Wire GPIO
Built-in pull-up resistors

Buttons

S1 – ESP32 Reset
S2 – Download Mode (GPIO0)
S3 – Tuya Configuration Button

Communication Interfaces

- WiFi
- Bluetooth
- RS485
- USB Type-C
- 433MHz RF Receiver
- IR Receiver
- I²C Expansion Interface

[arduino code examples for MT4]-06 IR receiver decode

Sat, 11 Jul 2026 10:21:10 +0800

Code:
/*

 * SimpleReceiver.cpp

 *

 * Demonstrates receiving ONLY NEC protocol IR codes with IRremote

 * If no protocol is defined, all protocols (except Bang&Olufsen) are active.

 *

 *  This file is part of Arduino-IRremote https://github.com/Arduino-IRremote/Arduino-IRremote.

 *

 ************************************************************************************

 * MIT License

 *

 * Copyright (c) 2020-2025 Armin Joachimsmeyer

 *

 * Permission is hereby granted, free of charge, to any person obtaining a copy

 * of this software and associated documentation files (the "Software"), to deal

 * in the Software without restriction, including without limitation the rights

 * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell

 * copies of the Software, and to permit persons to whom the Software is furnished

 * to do so, subject to the following conditions:

 *

 * The above copyright notice and this permission notice shall be included in all

 * copies or substantial portions of the Software.

 *

 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,

 * INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A

 * PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

 * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF

 * CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE

 * OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

 *

 ************************************************************************************

 */

#include 

#include  // include the library

uint8_t sender_pins[] = {47, 48};

uint8_t receiver_pin = 15;

int sender_pin_num = sizeof(sender_pins) / sizeof(sender_pins[0]);

uint8_t sender_pin_idx = 0;

uint8_t receive_cnt = 0;

uint8_t sCommand = 0x34;

uint8_t sRepeats = 0;

void setup() {

    Serial.begin(115200);

    IrReceiver.begin(receiver_pin, false);

    IrSender.begin(sender_pins[0]);

    xTaskCreate(

      sendIr,    // Function that should be called

      "Send IR",   // Name of the task (for debugging)

      4096,            // Stack size (bytes)

      NULL,            // Parameter to pass

      1,               // Task priority

      NULL             // Task handle

  );

}

void sendIr(void * parameter) {

  delay(2000);

  IrSender.setSendPin(47);

  IrSender.sendNEC(0x00, sCommand, sRepeats);

  Serial.printf("send by pin: %d\n", 47);

  delay(2000);

  IrSender.setSendPin(48);

  IrSender.sendNEC(0x00, sCommand, sRepeats);

  Serial.printf("send by pin: %d\n", 48);

  delay(2000);

  vTaskDelete(NULL);

}

void loop() {

  if (IrReceiver.decode()) {

      Serial.println("recv data");

      if (IrReceiver.decodedIRData.protocol == UNKNOWN) {

          Serial.println(F("Received noise or an unknown (or not yet enabled) protocol"));

          // We have an unknown protocol here, print extended info

          IrReceiver.printIRResultRawFormatted(&Serial, true);

          IrReceiver.resume(); // Do it here, to preserve raw data for printing with printIRResultRawFormatted()

      } else {

          IrReceiver.resume(); // Early enable receiving of the next IR frame

          IrReceiver.printIRResultShort(&Serial);

          IrReceiver.printIRSendUsage(&Serial);

      }

  } else {

    // Serial.println("no data");

  }

}

arduino ino file download:

SimpleSendReceiver.zip (Size: 1.62 KB / Downloads: 27)
BIN file (you can use esp32 download tool download to ESP32-S3 with address 0x0 then directly to use) download:

SimpleSendReceiver.ino.merged.zip (Size: 194.06 KB / Downloads: 23)

[arduino code examples for MT4]-05 RS485 communication test

Sat, 11 Jul 2026 10:19:54 +0800

Code:
/*

 * Made by KinCony IoT: https://www.kincony.com

 *

 * RS485 Communication Test

 *

 * This program is a simple test for RS485 communication using ESP32-S3.

 * It will send a message over RS485 and then read incoming messages.

 * The TXD pin is defined as GPIO 16 and RXD pin is defined as GPIO 17.

 */

#include 

// Define RS485 pins

#define RS485_RXD 7

#define RS485_TXD 6

// Create a hardware serial object

HardwareSerial rs485Serial(1);

void setup() {

  // Start serial communication for debugging

  Serial.begin(115200);

  while (!Serial);

  // Initialize RS485 Serial communication

  rs485Serial.begin(9600, SERIAL_8N1, RS485_RXD, RS485_TXD);

  Serial.println("RS485 Test Start");

}

void loop() {

  // Send a test message

  rs485Serial.println("Hello from KinCony");

  // Wait for a short period

  delay(1000);

  // Check if data is available to read

  if (rs485Serial.available()) {

    String receivedMessage = "";

    while (rs485Serial.available()) {

      char c = rs485Serial.read();

      receivedMessage += c;

    }

    // Print the received message

    Serial.print("Received: ");

    Serial.println(receivedMessage);

  }

  // Wait before sending the next message

  delay(2000);

}

arduino ino file download:

RS485-Test.zip (Size: 754 bytes / Downloads: 31)
BIN file (you can use esp32 download tool download to ESP32-S3 with address 0x0 then directly to use) download:

RS485-Test.ino.merged.zip (Size: 185.84 KB / Downloads: 36)