Smart Home Automation Forum

Welcome, Guest

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

Search Forums

Forum Statistics

» Members: 10,074
» Latest member: ReelsOn
» Forum threads: 4,254
» Forum posts: 21,076

Full Statistics

Online Users

There are currently 396 online users.
» 0 Member(s) | 382 Guest(s)
Applebot, Baidu, Bing, Bytespider, Crawl, Google, PetalBot, bot

Latest Threads

KC868-A6 Analog inputs
Forum: KC868-A6
Last Post: Tomas4289
5 hours ago
» Replies: 2
» Views: 5

N60/N30/N20/N10 PC softwa...
Forum: N10
Last Post: admin
5 hours ago
» Replies: 13
» Views: 1,584

getting the A8A inputs to...
Forum: Development
Last Post: admin
9 hours ago
» Replies: 5
» Views: 159

Best way to read from N30
Forum: N30
Last Post: admin
Yesterday, 12:20 AM
» Replies: 3
» Views: 38

extend KC868-A16v3
Forum: KC868-A series and Uair Smart Controller
Last Post: bitet96717
09-24-2026, 06:41 AM
» Replies: 2
» Views: 213

Las Firmware ?
Forum: KC868-A16
Last Post: admin
09-22-2026, 11:15 PM
» Replies: 8
» Views: 921

kc868-a6 analog input
Forum: KC868-A6
Last Post: admin
09-21-2026, 11:38 PM
» Replies: 1
» Views: 127

A32 pro tuya
Forum: "KCS" v3 firmware
Last Post: admin
09-21-2026, 11:38 PM
» Replies: 1
» Views: 53

Disconnect loop with Home...
Forum: F16
Last Post: admin
09-21-2026, 01:16 AM
» Replies: 3
» Views: 109

KC-868-A1 linked Home Ass...
Forum: News
Last Post: admin
09-21-2026, 01:16 AM
» Replies: 5
» Views: 1,434

DM8 ESPHome yaml for home assistant without tuya

Posted by: admin - 03-17-2026, 12:49 AM - Forum: DM8 - No Replies

Code:
esphome:

  name: dm8

  friendly_name: dm8

esp32:

  board: esp32-s3-devkitc-1

  framework:

    type: arduino

# Enable logging

logger:

# Enable Home Assistant API

api:

ethernet:

  type: W5500

  clk_pin: GPIO1

  mosi_pin: GPIO2

  miso_pin: GPIO41

  cs_pin: GPIO42

  interrupt_pin: GPIO43

  reset_pin: GPIO44

uart:

  - id: uart_1 # RS485

    baud_rate: 9600

    debug:

      direction: BOTH

      dummy_receiver: true

      after:

        timeout: 10ms

    tx_pin: 39

    rx_pin: 38

  - id: dac_uart

    rx_pin: 4

    tx_pin: 6

    baud_rate: 115200

    stop_bits: 1

    data_bits: 8

    parity: NONE

    debug:

modbus:

  uart_id: dac_uart

modbus_controller:

  - address: 1

    update_interval: 5s

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());

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 (0x0FA7 / 4007)

  - 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;

# -------------------

# 8 路 Light (调光灯)

# -------------------

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

pcf8574:

  - id: pcf8574_hub_1 # for input channel 1-8

    i2c_id: bus_a

    address: 0x24

switch:

  - platform: uart

    uart_id: uart_1

    name: "RS485 Button"

    data: [0x11, 0x22, 0x33, 0x44, 0x55]

binary_sensor:

  - platform: gpio

    name: "dm8-input01"

    id: dm8_input01

    pin:

      pcf8574: pcf8574_hub_1

      number: 0

      mode: INPUT

      inverted: true

  - platform: gpio

    name: "dm8-input02"

    id: dm8_input02

    pin:

      pcf8574: pcf8574_hub_1

      number: 1

      mode: INPUT

      inverted: true

  - platform: gpio

    name: "dm8-input03"

    id: dm8_input03

    pin:

      pcf8574: pcf8574_hub_1

      number: 2

      mode: INPUT

      inverted: true

  - platform: gpio

    name: "dm8-input04"

    id: dm8_input04

    pin:

      pcf8574: pcf8574_hub_1

      number: 3

      mode: INPUT

      inverted: true

  - platform: gpio

    name: "dm8-input05"

    id: dm8_input05

    pin:

      pcf8574: pcf8574_hub_1

      number: 4

      mode: INPUT

      inverted: true

  - platform: gpio

    name: "dm8-input06"

    id: dm8_input06

    pin:

      pcf8574: pcf8574_hub_1

      number: 5

      mode: INPUT

      inverted: true

  - platform: gpio

    name: "dm8-input07"

    id: dm8_input07

    pin:

      pcf8574: pcf8574_hub_1

      number: 6

      mode: INPUT

      inverted: true

  - platform: gpio

    name: "dm8-input08"

    id: dm8_input08

    pin:

      pcf8574: pcf8574_hub_1

      number: 7

      mode: INPUT

      inverted: true

  ## pull-up resistance on PCB

  - platform: gpio

    name: "dm8-W1-io47"

    pin:

      number: 47

      inverted: true

  - platform: gpio

    name: "dm8-W1-io48"

    pin:

      number: 48

      inverted: true

  - platform: gpio

    name: "dm8-W1-io17"

    pin:

      number: 17

      inverted: true

  - platform: gpio

    name: "dm8-W1-io40"

    pin:

      number: 40

      inverted: true

  ## without resistance on PCB

  - platform: gpio

    name: "dm8-W1-io13"

    pin:

      number: 13

      inverted: false

  - platform: gpio

    name: "dm8-W1-io14"

    pin:

      number: 14

      inverted: false

  - platform: gpio

    name: "dm8-W1-io21"

    pin:

      number: 21

      inverted: false

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

web_server:

  port: 80

esphome yaml file download:

.txt

esphome_dm8.txt (Size: 6.63 KB / Downloads: 275)

How restart а board using IFTTT and Custom Protocol?

Posted by: apps4check - 03-16-2026, 07:59 PM - Forum: "KCS" v2 firmware system - Replies (1)

	Hello, is it possible to restart the board (KC868-A2 or KC868-A4S, KCS v2 firmware) using IFTTT and Custom Protocol? Any advice would be greatly appreciated.

Battery backup model on AOI

Posted by: H_spadacini - 03-16-2026, 09:42 AM - Forum: AIO Hybrid - Replies (1)

	Francais : Serait-il possible de connaitre la référence de la pile bouton qui doit va dans le rtc battery socket qui peut-être mis sur le AIO pour maintenir sa sauvegarde. Cordialement. English : Could you please provide the part number for the button cell battery that fits into the RTC battery socket, which can be installed on the AIO to maintain its backup? Regards.

KinCony DM8 8CH ESP32 Dimmer Board released

Posted by: admin - 03-16-2026, 08:16 AM - Forum: News - No Replies

KinCony DM8 ESP32 smart dimmer controller based on ESP32-S3-WROOM-1U (N16R8) wifi chip. Support 8 channel DC 0-10v output, 7 channel 1-wire GPIOs, 4 channel ADS1115 16bit analog input ports. One SD card using SPI bus. DM8 include DS3231 high precision RTC clock chip. OLED display will show wifi and ethernet IP address and Tuya connection state. DM8 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. DM8 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: DM8-1.jpg]
Model No. KinCony DM8
Description: KinCony 8 Channel ESP32-S3 Smart Dimmer Controller – DM8
Power supply: 12-24V DC
Processor: ESP32-S3-WROOM-1U (N16R8)
Size: 140mm*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:
8CH 0-10v Outputs.
Inputs:
ADS1115 16bit ADC: 2CH analog input DC0-5V (A1,A2) 2CH analog input 4-20mA (A3,A4)
8CH 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: DM8-1.jpg]

Monitor 1 shows power=0 while Monitor 2 shows correct values

Posted by: tombueng - 03-15-2026, 03:48 PM - Forum: N20 - Replies (1)

My Monitor 1 shows Power=0 for all channels even if there is current which is wrong.
Monitor 2 shows values correctly.

Voltage / Freq 226V, 50Hz is shown on both inputs (both connect to the same phase)

Protocol -> Energy has the same values for Energy 1 and 2 for all of the values of Current Factor=0.5, Power Factor=1, Energy Factor=1

Firmware v3.22.0

What might be the Problem?

Is there no OTA-Update available? Do I need to connect a via USB PC to Update the Firmware?

KinCony DM32 32CH ESP32 Dimmer Board released

Posted by: admin - 03-15-2026, 10:31 AM - Forum: News - No Replies

KinCony DM32 ESP32 smart dimmer controller based on ESP32-S3-WROOM-1U (N16R8) wifi chip. Support 32 channel DC 0-10v output, 7 channel 1-wire GPIOs, 4 channel ADS1115 16bit analog input ports. One SD card using SPI bus. DM32 include DS3231 high precision RTC clock chip. OLED display will show wifi and ethernet IP address and Tuya connection state. DM32 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. DM32 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: DM32-1.jpg]
Model No. KinCony DM32
Description: KinCony 32 Channel ESP32-S3 Smart Dimmer Controller – DM32
Power supply: 12-24V DC
Processor: ESP32-S3-WROOM-1U (N16R8)
Size:
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:
32CH 0-10v Outputs.
Inputs:
ADS1115 16bit ADC: 2CH analog input DC0-5V (A1,A2) 2CH analog input 4-20mA (A3,A4)
32CH 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: DM32-2.jpg]

KinCony DM4 4CH ESP32 Dimmer Board released

Posted by: admin - 03-15-2026, 04:21 AM - Forum: News - No Replies

KinCony DM4 ESP32 smart dimmer controller based on ESP32-S3-WROOM-1U (N16R8) wifi chip. Support 4 channel DC 0-10v output, 7 channel 1-wire GPIOs, 4 channel ADS1115 16bit analog input ports. One SD card using SPI bus. DM4 include DS3231 high precision RTC clock chip. OLED display will show wifi and ethernet IP address and Tuya connection state. 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. DM4 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: DM4-1.jpg]
Model No. KinCony DM4
Description: KinCony 4 Channel ESP32-S3 Smart Dimmer Controller – DM4
Power supply: 12-24V DC
Processor: ESP32-S3-WROOM-1U (N16R8)
Size: 114mm*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:
4CH 0-10v Outputs.
Inputs:
ADS1115 16bit ADC: 2CH analog input DC0-5V (A1,A2) 2CH analog input 4-20mA (A3,A4)
4CH dry contact inputs (optocoupler isolation, long distance circuit for MAX 500 meters cable)
3 buttons: 1:ESP32 Reset 2:ESP32 Download 3:Tuya config
1-Wire GPIO: 4CH (with pull-up resistance on PCB)
Free GPIO: 4CH (ESP32 pin directly, without pull-up resistance on PCB)
[Image: DM4-2.jpg]

F8 on device physical switches in ESPHome

Posted by: Vinceken - 03-14-2026, 08:07 PM - Forum: F8 - Replies (1)

	Hi - with esp-idf in ESPHome, how can I access the state of the physical on device switches? I can't seem to observe those on any GPIO pins. I would like to configure (in esphome) some of them to control their output relay directly, but for others for them to act as momentary switches. I can manage all the coding myself if I can work out where to observe their state... Thanks.

Adding a debounce capability to inputs

Posted by: twostar - 03-14-2026, 02:09 PM - Forum: KC868-A16v3 - Replies (6)

At the moment the KC868 inputs are instantaneous which is a problem for signals that glitch occasionally from things like noise coupled onto the input lines. Would it be possible to add a debounce capability where you can specify that an input has to be asserted for x seconds, x user-settable, before it gets reported as an asserted input? What I'm thinking of is adding a per-input capability where you can specify that it needs to be asserted for (say) 5 seconds before it's treated as valid. The overall range would be maybe 0-60s, 0s = instant response, > 0s = input must be asserted for that long before it's reported as asserted.

KC868-a8v3 IFTTT for Aircon use

Posted by: beegeenz - 03-12-2026, 10:59 AM - Forum: KC868-A2v3 - Replies (1)

I have KC868-a8v3.1 board loaded with the current firmware V3.23.2

It is used for switching 24VAC to control AC ducts in conjunction with Home Assistant.

My challenge is that the Rumpus room duct (controlled by DO8 on KC868) is fed from a master upstairs duct (controller by DO2 on KC868) so both ducts need to be open for AC to reach the Rumpus room.
For ease of user operation I would like to setup the a IFTTT rule so that;
1. when a user turns on the Rumpus duct (D08) the upstairs duct will also activate (D02) (turn on could by by HA or RF on the KC868)
2. if the user subsequently turns off the Rumpus duct, the Upstairs duct will remain open.

Also, if the Upstairs duct is turned off, there should be a rule to turn on the Rumpus room duct, this is necessary to reflect through to the HA dashboard.

Using IFTTT I setup an IF condition on the DO8 which performs an action on D02.

I found that this doesn't work properly and the KC web page status indicator for D02 and D08 are not linked corectly by the rule. At one stage the KC868 crashed and I had to relead the formward with the formward loader tool.

Can you please advise if IFTTT can be used for this sort of rules or is there another way on the KC868 to achieve this.

Regards

Pages (422): « Previous 1 … 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 … 422 Next »

Login
Username:
Password:	Lost Password?
	Remember me