Release.zip (Size: 26.56 MB / Downloads: 53)

   

  DEMO_PROG_RMC3_compiled.zip (Size: 2.46 MB / Downloads: 49)

   
   

GUI file and source code:

  Gui.zip (Size: 21.58 MB / Downloads: 58)

  Kincony_Module_Documentation_260720.pdf (Size: 49.85 KB / Downloads: 55)

Hi everyone,
I'm using the KCS v2 firmware and would like each relay to restore its last state automatically after a power outage. Right now, all relays switch to OFF every time the controller reboots.
Is there a built-in setting in KCS v2 to save the relay state in flash memory and restore it after startup, or does this need to be handled through MQTT or Home Assistant? If anyone has configured this successfully, could you share the required settings or steps?
Thanks!

Hey KinCony, 

Having issues whenever the controller restarts or looses power for a minute the IFTTT Settings do not save. I do not see any options that would fix this. Any help is appreciated! 

I'm currently on firmware version 3.25.4
   

new version improvement:

1: add support new model: MT4
2: add auto feedback DAC and ADC value by TCP string command.
3: fixed bug temperature sensor trigger SMS or phone call.
4: support use negative temperature value.
5: add "Duration" for IF condition using IFTTT.
6: if repalce new DS18B20 sensor, add auto detect function. Not need to re config sensor manually.
7: full unicode support for 4G module and Longer SMS Message content. You can use local language for SMS.Even emojis in SMS.

Attached Files

  KCS_A2V3_V3.26.1.zip (Size: 1.19 MB / Downloads: 79)
  KCS_A6V3_V3.26.1.zip (Size: 1.17 MB / Downloads: 69)
  KCS_A8V3_V3.26.1.zip (Size: 1.22 MB / Downloads: 72)
  KCS_A16V3_V3.26.1.zip (Size: 1.24 MB / Downloads: 103)
  KCS_A32PRO_V3.26.1.zip (Size: 1.2 MB / Downloads: 64)
  KCS_AG8_V3.26.1.zip (Size: 1.18 MB / Downloads: 62)
  KCS_AGV3_V3.26.1.zip (Size: 1.13 MB / Downloads: 70)
  KCS_AIO_HYBRID_V3.26.1.zip (Size: 1.41 MB / Downloads: 64)
  KCS_ALR_V3.26.1.zip (Size: 1.17 MB / Downloads: 62)
  KCS_B4_V3.26.1.zip (Size: 1.23 MB / Downloads: 73)
  KCS_B4M_V3.26.1.zip (Size: 1.23 MB / Downloads: 64)
  KCS_B8_V3.26.1.zip (Size: 1.23 MB / Downloads: 72)
  KCS_B8M_V3.26.1.zip (Size: 1.23 MB / Downloads: 63)
  KCS_B16_V3.26.1.zip (Size: 1.23 MB / Downloads: 62)
  KCS_B16M_V3.26.1.zip (Size: 1.23 MB / Downloads: 76)
  KCS_B24_V3.26.1.zip (Size: 1.23 MB / Downloads: 62)
  KCS_B24M_V3.26.1.zip (Size: 1.23 MB / Downloads: 64)
  KCS_B32M_V3.26.1.zip (Size: 1.23 MB / Downloads: 68)
  KCS_DM4_V3.26.1.zip (Size: 1.23 MB / Downloads: 64)
  KCS_DM8_V3.26.1.zip (Size: 1.23 MB / Downloads: 77)
  KCS_DM16_V3.26.1.zip (Size: 1.2 MB / Downloads: 65)
  KCS_DM32_V3.26.1.zip (Size: 1.23 MB / Downloads: 70)
  KCS_F4_V3.26.1.zip (Size: 1.22 MB / Downloads: 69)
  KCS_F8_V3.26.1.zip (Size: 1.22 MB / Downloads: 67)
  KCS_F16_V3.26.1.zip (Size: 1.23 MB / Downloads: 68)
  KCS_F24_V3.26.1.zip (Size: 1.23 MB / Downloads: 64)
  KCS_F32_V3.26.1.zip (Size: 1.23 MB / Downloads: 74)
  KCS_G1_V3.26.1.zip (Size: 1.19 MB / Downloads: 75)
  KCS_KC_TA_V3.26.1.zip (Size: 1.18 MB / Downloads: 62)
  KCS_MT4_V3.26.1.zip (Size: 1.18 MB / Downloads: 62)
  KCS_N10_V3.26.1.zip (Size: 1.09 MB / Downloads: 72)
  KCS_N20_V3.26.1.zip (Size: 1.09 MB / Downloads: 66)
  KCS_N30_V3.26.1.zip (Size: 1.09 MB / Downloads: 70)
  KCS_N60_V3.26.1.zip (Size: 1.11 MB / Downloads: 67)
  KCS_T16M_V3.26.1.zip (Size: 1.17 MB / Downloads: 61)
  KCS_T32M_V3.26.1.zip (Size: 1.2 MB / Downloads: 64)
  KCS_T64M_V3.26.1.zip (Size: 1.2 MB / Downloads: 56)
  KCS_T128M_V3.26.1.zip (Size: 1.2 MB / Downloads: 59)
  KCS_TR_V3.26.1.zip (Size: 1.15 MB / Downloads: 61)
  KCS_Z1_V3.26.1.zip (Size: 1.32 MB / Downloads: 47)

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.

Attached Files

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

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.

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.