Smart Home Automation Forum
Portal

Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  

Search Forums

(Advanced Search)

Forum Statistics
» Members: 10,093
» Latest member: amonggame.org
» Forum threads: 4,254
» Forum posts: 21,077

Full Statistics

Online Users
There are currently 332 online users.
» 0 Member(s) | 312 Guest(s)
AhrefsBot, Amazonbot, Applebot, Baidu, Bing, Bytespider, Crawl, Google, HeadlessChrome, PetalBot, bot

Latest Threads
KC868-HAv2 phantom press ...
Forum: KC868-HA /HA v2
Last Post: phrfpeixoto
09-29-2026, 01:57 AM
» Replies: 2
» Views: 1,487
KC868-A6 Analog inputs
Forum: KC868-A6
Last Post: Tomas4289
09-28-2026, 12:57 PM
» Replies: 2
» Views: 37
N60/N30/N20/N10 PC softwa...
Forum: N10
Last Post: admin
09-28-2026, 12:49 PM
» Replies: 13
» Views: 1,640
getting the A8A inputs to...
Forum: Development
Last Post: admin
09-28-2026, 08:38 AM
» Replies: 5
» Views: 220
Best way to read from N30
Forum: N30
Last Post: admin
09-27-2026, 12:20 AM
» Replies: 3
» Views: 51
extend KC868-A16v3
Forum: KC868-A series and Uair Smart Controller
Last Post: bitet96717
09-24-2026, 06:41 AM
» Replies: 2
» Views: 243
Las Firmware ?
Forum: KC868-A16
Last Post: admin
09-22-2026, 11:15 PM
» Replies: 8
» Views: 954
kc868-a6 analog input
Forum: KC868-A6
Last Post: admin
09-21-2026, 11:38 PM
» Replies: 1
» Views: 150
A32 pro tuya
Forum: "KCS" v3 firmware
Last Post: admin
09-21-2026, 11:38 PM
» Replies: 1
» Views: 77
Disconnect loop with Home...
Forum: F16
Last Post: admin
09-21-2026, 01:16 AM
» Replies: 3
» Views: 139

  KinCony DM16 Smart Dimmer Controller released
Posted by: admin - 09-09-2025, 02:25 AM - Forum: News - No Replies

KinCony DM16 ESP32 smart dimmer controller based on ESP32-S3-WROOM-1U (N16R8) wifi chip. Support 16 channel DC 0-10v output, 7 channel 1-wire GPIOs, 4 channel ADS1115 16bit analog input ports. One SD card using SPI bus. DM16 include DS3231 high precision RTC clock chip. OLED display will show wifi and ethernet IP address and Tuya connection state. DM16 have 2pcs of RS485 port. one RS485 connect with ARM CPU, support use by modbus directly. Another RS485 work with ESP32. You can write any code by Arduino IDE / MicroPython / ESP-IDF development tool to ESP32 module. We will supply Arduino / ESP-IDF demo code for different samples. Everyone can modify and change the code for your own smart home automation system project. it support use by ESPHome for home assistant or tasmota firmware for smart home automation DIY. DM16 use KCS v3 firmware, it support home assistant auto discovery function by MQTT, so without write any config code (zero code) for home assistant. KCS v3 support KinCony cloud service (official shop customer free 2 years), remote monitor and control device by webpage in anywhere. KCS v3 support KinCony board integrate to Loxone Miniserver. Support Apple HomeKit for Siri.
[Image: DM16-1.jpg]
Model No. KinCony DM16
Description: KinCony 16 Channel ESP32-S3 Smart Dimmer Controller – DM16
Power supply: 12-24V DC
Processor: ESP32-S3-WROOM-1U (N16R8)
Size: 174mm*83mm*59mm
interfaces: Ethernet(RJ45)-LAN 100Mbps IPv4/IPv6,WiFi,RS485,Bluetooth,USB-C,OLED,Tuya Module
RTC: DS3231 high precision chip (battery socket on PCB)
SD Card: SPI bus
Installation method: DIN RAIL
OLED: SSD1306 I2C display
Outputs:
16CH 0-10v Outputs.
Inputs:
ADS1115 16bit ADC: 2CH analog input DC0-5V (A1,A2) 2CH analog input 4-20mA (A3,A4)
16CH dry contact inputs (optocoupler isolation, long distance circuit for MAX 500 meters cable)
4 buttons: 1:ESP32 Reset 2:ESP32 Download 3:Tuya config 4: ARM CPU Reset
1-Wire GPIO: 4CH (with pull-up resistance on PCB)
Free GPIO: 4CH (ESP32 pin directly, without pull-up resistance on PCB)
[Image: DM16-2.jpg]

Print this item

  DM16 ESPHome yaml for home assistant without tuya
Posted by: admin - 09-09-2025, 02:17 AM - Forum: DM16 - No Replies

Code:
esphome:
  name: dm16
  friendly_name: dm16

esp32:
  board: esp32-s3-devkitc-1
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  platform: esphome

web_server:
  port: 80

ethernet:
  type: W5500
  clk_pin: GPIO1
  mosi_pin: GPIO2
  miso_pin: GPIO41
  cs_pin: GPIO42
  interrupt_pin: GPIO43
  reset_pin: GPIO44

i2c:
   - id: bus_a
     sda: 8
     scl: 18
     scan: true
     frequency: 400kHz
     
text_sensor:
  - platform: ethernet_info
    ip_address:
      name: ESP IP Address
      id: eth_ip
      address_0:
        name: ESP IP Address 0
      address_1:
        name: ESP IP Address 1
      address_2:
        name: ESP IP Address 2
      address_3:
        name: ESP IP Address 3
      address_4:
        name: ESP IP Address 4
    dns_address:
      name: ESP DNS Address
    mac_address:
      name: ESP MAC Address

font:
  - file: "gfonts://Roboto"
    id: roboto
    size: 15

display:
  - platform: ssd1306_i2c
    model: "SSD1306 128x64"
    address: 0x3C
    lambda: |-
      it.printf(0, 15, id(roboto), "IP: %s", id(eth_ip).state.c_str());
uart:
  id: dac_uart
  rx_pin: 4
  tx_pin: 6
  baud_rate: 115200
  stop_bits: 1
  data_bits: 8
  parity: NONE
  debug:

modbus:

modbus_controller:
  - address: 1
    update_interval: 5s

output:
  # CH1 (0x0FA0 / 4000)
  - platform: modbus_controller
    id: dac_ch1_out
    address: 0x0FA0
    value_type: U_WORD
    write_lambda: |-
      // state = 0.0 ~ 1.0 → 0 ~ 4095
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH2 (0x0FA1 / 4001)
  - platform: modbus_controller
    id: dac_ch2_out
    address: 0x0FA1
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH3
  - platform: modbus_controller
    id: dac_ch3_out
    address: 0x0FA2
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH4
  - platform: modbus_controller
    id: dac_ch4_out
    address: 0x0FA3
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH5
  - platform: modbus_controller
    id: dac_ch5_out
    address: 0x0FA4
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH6
  - platform: modbus_controller
    id: dac_ch6_out
    address: 0x0FA5
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH7
  - platform: modbus_controller
    id: dac_ch7_out
    address: 0x0FA6
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH8
  - platform: modbus_controller
    id: dac_ch8_out
    address: 0x0FA7
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH9
  - platform: modbus_controller
    id: dac_ch9_out
    address: 0x0FA8
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH10
  - platform: modbus_controller
    id: dac_ch10_out
    address: 0x0FA9
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH11
  - platform: modbus_controller
    id: dac_ch11_out
    address: 0x0FAA
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH12
  - platform: modbus_controller
    id: dac_ch12_out
    address: 0x0FAB
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH13
  - platform: modbus_controller
    id: dac_ch13_out
    address: 0x0FAC
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH14
  - platform: modbus_controller
    id: dac_ch14_out
    address: 0x0FAD
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH15
  - platform: modbus_controller
    id: dac_ch15_out
    address: 0x0FAE
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

  # CH16
  - platform: modbus_controller
    id: dac_ch16_out
    address: 0x0FAF
    value_type: U_WORD
    write_lambda: |-
      uint16_t reg = (uint16_t) round(x * 4095.0);
      return reg;

# -------------------
# 16 Channel Dimmer
# -------------------
light:
  - platform: monochromatic
    name: "DAC CH1"
    output: dac_ch1_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH2"
    output: dac_ch2_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH3"
    output: dac_ch3_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH4"
    output: dac_ch4_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH5"
    output: dac_ch5_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH6"
    output: dac_ch6_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH7"
    output: dac_ch7_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH8"
    output: dac_ch8_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH9"
    output: dac_ch9_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH10"
    output: dac_ch10_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH11"
    output: dac_ch11_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH12"
    output: dac_ch12_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH13"
    output: dac_ch13_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH14"
    output: dac_ch14_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH15"
    output: dac_ch15_out
    default_transition_length: 0s

  - platform: monochromatic
    name: "DAC CH16"
    output: dac_ch16_out
    default_transition_length: 0s



pcf8574:
  - id: 'pcf8574_hub_in_1'  # for input channel 1-16
    i2c_id: bus_a
    address: 0x22
    pcf8575: true

binary_sensor:
  - platform: gpio
    name: "dm16-input01"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 8
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input02"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 9
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input03"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 10
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input04"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 11
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input05"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 12
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input06"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 13
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input07"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 14
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input08"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 15
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input09"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 0
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input10"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 1
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input11"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 2
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input12"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 3
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input13"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 4
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input14"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 5
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input15"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 6
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "dm16-input16"
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 7
      mode: INPUT
      inverted: true

ads1115:
  - address: 0x48
sensor:
  - platform: ads1115
    multiplexer: 'A0_GND'
    gain: 6.144
    resolution: 16_BITS
    name: "ADS1115 Channel A0-GND"
    update_interval: 5s
  - platform: ads1115
    multiplexer: 'A1_GND'
    gain: 6.144
    name: "ADS1115 Channel A1-GND"
    update_interval: 5s
  - platform: ads1115
    multiplexer: 'A2_GND'
    gain: 6.144
    name: "ADS1115 Channel A2-GND"
    update_interval: 5s
  - platform: ads1115
    multiplexer: 'A3_GND'
    gain: 6.144
    name: "ADS1115 Channel A3-GND"
    update_interval: 5s
   
esphome yaml file download:

.txt   DM16-HA-without Tuya.txt (Size: 9.49 KB / Downloads: 417)

Print this item

Sad AG Pro - Disappointed
Posted by: vishal.alex@gmail.com - 09-08-2025, 11:54 AM - Forum: KC868-AG / AG Pro / AG8 / Z1 - Replies (5)

I brought the AG Pro in June of 2024 when i saw that it had all in one as a Gateway. It was advertised in such a way that it was all in one solution. But as soon as i received it, i found that many of the things advertised is not functioning out of the box. the Zigbee had to be used with tasmota and remaining functions like IR, RF, Tuya and to be with Kincony firmware. and on top of this both firmware cannot work together. I some how managed to flash the Tasmota firmware because i needed the ZHA integration.. and this worked until last month. Now the tasmota firmware has failed to recognize the Zigbee device inside. i tried rolling back to several tasmota version but it all remains the same. 

I sent a message to their support and all the response i get is to change the firmware. I feel dumped.. Kincony should have either fixed the firmware issues or informed the customer that these problems exits. 92$(inc Shipping) wasted.

Print this item

  1-WIRE multiple sensors
Posted by: Ndogo - 09-08-2025, 09:29 AM - Forum: KC868-A16v3 - Replies (1)

Can I connect multiple DS18B20 sensors to one 47 GPIO in the native firmware?

Print this item

  KinCony Raspberry Pi CM5 Linux Server released
Posted by: admin - 09-07-2025, 08:59 AM - Forum: News - No Replies

KinCony Pi5 is a Raspberry Pi CM5 server for smart home automation and industrial automation control. It can use for home assistant local server. It's a Linux computer, you can install software by yourself, such as Node red. The product default CM5 version is CM5004000. It without Bluetooth and wifi, RAM:4G Lite version.
[Image: Pi5_1.jpg]
Model No. KinCony Pi5
Description: KinCony Automation Local Server – Pi5
Power supply: 12-24V DC
Processor: Raspberry Pi Compute Module 5
Size: 139mm*83mm*56mm
interfaces: Ethernet(RJ45)-LAN 1000Mbps IPv4/IPv6,USB-C
Installation method: DIN RAIL
2 × USB 3 sockets
microSD card socket for CM5 Lite modules
M.2 M key PCIe socket
1 × full-size HDMI 2.0 connectors
DIP SWITCH for jumpers
[Image: Pi5_2.jpg]

Print this item

  DM16 ESP32-S3 IO pins define
Posted by: admin - 09-07-2025, 02:31 AM - Forum: DM16 - No Replies

SDA:GPIO8
SCL:GPIO18

PCF8575: (input1-16): i2c address:0x22 by B16-core

P8:input1
P9:input2
P10:input3
P11:input4
P12:input5
P13:input6
P14:input7
P15:input8

P0:input9
P1:input10
P2:input11
P3:input12
P4:input13
P5:input14
P6:input15
P7:input16

ADS1115 (4CH ADC): i2c address:0x48
Analog input (A1: DC 0-5v)
Analog input (A2: DC 0-5v)
Analog input (A3: DC 4-20mA)
Analog input (A4: DC 4-20mA)

24C02 EPROM i2c address: 0x50
DS3231 RTC i2c address: 0x68

1-wire (pull-up resistance on PCB):
1-wire1:GPIO47
1-wire2:GPIO48
1-wire3:GPIO7
1-wire4:GPIO40

free GPIOs:
GPIO13
GPIO14
GPIO21

-----------------------
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:GPIO17
TXD:GPIO16

Tuya network button: Tuya module's P28
Tuya network LED: Tuya module's P16

ARM CPU TXD:GPIO4
ARM CPU RXD:GPIO6

SD Card:
SPI-MOSI:GPIO10
SPI-SCK:GPIO11
SPI-MISO:GPIO12
SPI-CS:GPIO9
SD-Detect: GPIO5

Print this item

  "KCS" v3.12.0 firmware BIN file download
Posted by: admin - 09-06-2025, 04:56 AM - Forum: "KCS" v3 firmware - No Replies

v3.12.0 improvement:
1. Adapt to new KinCony Controller: B8/B8M/B24/B24M/DM16
2. Sensor pull-up option: When PCB include pull-up resistor, "pull-up" will auto shown as enabled
3. Network webpage -- LAN mode will show the actual ethernet IP address
4. GSM phone list: Add ID numbers
5. Password-related inputs option added masking
6. Sensor configuration webpage: added sensor name
7. IFTTT "sensor channel" change to "sensor name" have preset
8. Removed default MQTT port number "1883"
9. IFTTT THEN actions: Add "step value" for AO (analog output)
10. improve previous version first time downloaded firmware boot up speed slowly issue.



Attached Files
.zip   KCS_A2V3_V3.12.0.zip (Size: 1.07 MB / Downloads: 642)
.zip   KCS_A6V3_V3.12.0.zip (Size: 1.04 MB / Downloads: 643)
.zip   KCS_A8V3_V3.12.0.zip (Size: 1.09 MB / Downloads: 639)
.zip   KCS_A16V3_V3.12.0.zip (Size: 1.11 MB / Downloads: 728)
.zip   KCS_A32PRO_V3.12.0.zip (Size: 1.08 MB / Downloads: 617)
.zip   KCS_AG8_V3.12.0.zip (Size: 1.06 MB / Downloads: 616)
.zip   KCS_ALR_V3.12.0.zip (Size: 1.02 MB / Downloads: 573)
.zip   KCS_B8_V3.12.0.zip (Size: 1.1 MB / Downloads: 606)
.zip   KCS_B8M_V3.12.0.zip (Size: 1.1 MB / Downloads: 639)
.zip   KCS_B16_V3.12.0.zip (Size: 1.1 MB / Downloads: 576)
.zip   KCS_B16M_V3.12.0.zip (Size: 1.1 MB / Downloads: 615)
.zip   KCS_B24_V3.12.0.zip (Size: 1.1 MB / Downloads: 590)
.zip   KCS_B24M_V3.12.0.zip (Size: 1.1 MB / Downloads: 590)
.zip   KCS_DM16_V3.12.0.zip (Size: 1.07 MB / Downloads: 586)
.zip   KCS_F8_V3.12.0.zip (Size: 1.09 MB / Downloads: 638)
.zip   KCS_F16_V3.12.0.zip (Size: 1.1 MB / Downloads: 568)
.zip   KCS_F24_V3.12.0.zip (Size: 1.1 MB / Downloads: 585)
.zip   KCS_G1_V3.12.0.zip (Size: 1.06 MB / Downloads: 604)
.zip   KCS_KC_TA_V3.12.0.zip (Size: 1.05 MB / Downloads: 553)
.zip   KCS_N60_V3.12.0.zip (Size: 986.2 KB / Downloads: 587)
.zip   KCS_T16M_V3.12.0.zip (Size: 1.05 MB / Downloads: 644)
.zip   KCS_T32M_V3.12.0.zip (Size: 1.07 MB / Downloads: 609)
.zip   KCS_T64M_V3.12.0.zip (Size: 1.07 MB / Downloads: 589)
.zip   KCS_T128M_V3.12.0.zip (Size: 1.07 MB / Downloads: 595)
.zip   KCS_Z1_V3.12.0.zip (Size: 1.21 MB / Downloads: 651)
Print this item

  Unable to connect with firmware tool
Posted by: zmatthiaz - 09-05-2025, 06:04 PM - Forum: KC868-HxB series Smart Controller - Replies (1)

I have a kc868-h32b I can log in to the webpanel just fine with ethernet and I can see it has firmware H32B_Pro_V1.19

I can connect the USB-C to my windows 10 machine. And it shows up as COM4. 
I can click "OPEN PORT" as soon as the device restarts
But when I click on the bootloader detect button nothing happens

I've tried restarting the device more than 50 times. With varying timings and Baudrates. But no change. I never get the results shown in the youtube video

How do I debug this, what am I doing wrong? 
Is the USB C version different than what is shown in the video?



Attached Files Thumbnail(s)
   
Print this item

  using HAv2 with KC868-D
Posted by: swisstmack25 - 09-05-2025, 01:05 PM - Forum: KC868-HA /HA v2 - Replies (1)

Can you provide a solution to utilise the KC868-D 8 and 16 channel dimmer over KC868-HAv2 RS485 interface 
I would like to use multiple KC868-HAv2 (8 of them) connecting over RS485 to the Dimming module and all to the F16 device

I want to use some of the switch paddles for the dimmer and others to switch the outputs on the F16.
thanks

Print this item

  rpiboot_setup.exe for CM5 USB driver
Posted by: admin - 09-05-2025, 05:22 AM - Forum: Pi5 - No Replies

rpiboot_setup.exe for CM5 lite USB driver.

.zip   rpiboot_setup.zip (Size: 32.75 MB / Downloads: 688)

Print this item