1. fixed bug: update energy data to home assistant by MQTT.

Attached Files

  KCS_N10_V3.18.2_beta_20251230-144041.zip (Size: 972.53 KB / Downloads: 88)
  KCS_N20_V3.18.2_beta_20251230-144035.zip (Size: 972.65 KB / Downloads: 82)
  KCS_N30_V3.18.2_beta_20251230-144045.zip (Size: 972.64 KB / Downloads: 81)
  KCS_N60_V3.18.2_beta_20251230-144036.zip (Size: 987.97 KB / Downloads: 106)

1. fixed bug for energy data and power factor.
you can download by bootloader.exe tool by RS485.
ARM BIN file download:

  N10203060_KU_V20_251231.zip (Size: 13.11 KB / Downloads: 121)

bootloader.exe tool: 
  KC868 Controller Bootloader.zip (Size: 8.56 KB / Downloads: 92)
   
1. set baud rate=38400bps.
2. open com port.
3. power on Nx board, during LED fast blink when the "bootloader Detect" button right now. Then board will go to bootloader mode.
4. open BIN file
5. press "Download" button, begin download firmware, after finished, press "Run" button, ARM CPU begin work.
   

Hi, 

in the modbus specifiaction from N30 it is mentioned that Energy Sensor from BL0910 has a resolution of 1kWh only.

Is there any way to get a more accurat reading? For power circuits with low consumption it is misleading to see 0kWh consumption on end of day.

Does the BL0910 has a possibility to report for example 0,1kWh as resolution for Energy Consumption?

Thank you.

br

Hello
I need help with setup wallpad using modbus:
google drive with manual:
https://drive.google.com/drive/folders/1...drive_link

i have some errors, code from ai

[17:49:15.467][D][modbus_controller:039]: Modbus command to device=2 register=0x100B no response received - removed from send queue [17:49:15.705][W][modbus_controller:284]: Duplicate modbus command found: type=0x4 address=4107 count=1 

any user tryed this wall pad?



esphome:
  name: kincony_a16_wall_switch
  platform: ESP32
  board: esp32dev

wifi:
  ssid: "YOUR_WIFI"
  password: "YOUR_PASSWORD"

logger:
  baud_rate: 0

api:
ota:

uart:
  id: rs485_uart
  tx_pin: GPIO17
  rx_pin: GPIO16
  baud_rate: 9600
  stop_bits: 1

modbus:
  id: modbus1
  uart_id: rs485_uart

modbus_controller:
  - id: wallpad
    address: 0x02
    modbus_id: modbus1
    setup_priority: -10
    update_interval: 200ms

# ======================
# RELAYS (Kincony A16)
# ======================
switch:
  - platform: gpio
    id: relay_1
    name: "Relay 1"
    pin: GPIO32
    on_turn_on:
      - script.execute: led_1_on
    on_turn_off:
      - script.execute: led_1_off

  - platform: gpio
    id: relay_2
    name: "Relay 2"
    pin: GPIO33
    on_turn_on:
      - script.execute: led_2_on
    on_turn_off:
      - script.execute: led_2_off

  - platform: gpio
    id: relay_3
    name: "Relay 3"
    pin: GPIO25
    on_turn_on:
      - script.execute: led_3_on
    on_turn_off:
      - script.execute: led_3_off

  - platform: gpio
    id: relay_4
    name: "Relay 4"
    pin: GPIO26
    on_turn_on:
      - script.execute: led_4_on
    on_turn_off:
      - script.execute: led_4_off

# ======================
# BUTTON INPUTS (RS485)
# ======================
binary_sensor:
  - platform: modbus_controller
    modbus_controller_id: wallpad
    name: "Button 1"
    register_type: holding
    address: 0x100B
    bitmask: 0x0001
    on_press:
      - switch.toggle: relay_1

  - platform: modbus_controller
    name: "Button 2"
    register_type: holding
    address: 0x100B
    bitmask: 0x0002
    on_press:
      - switch.toggle: relay_2

  - platform: modbus_controller
    name: "Button 3"
    register_type: holding
    address: 0x100B
    bitmask: 0x0004
    on_press:
      - switch.toggle: relay_3

  - platform: modbus_controller
    name: "Button 4"
    register_type: holding
    address: 0x100B
    bitmask: 0x0008
    on_press:
      - switch.toggle: relay_4

# ======================
# LED CONTROL SCRIPTS
# ======================
script:
  - id: led_1_on
    then:
      - modbus_controller.write_register:
          id: wallpad
          address: 0x1008
          value: 0x0101  # White LED ON

  - id: led_1_off
    then:
      - modbus_controller.write_register:
          id: wallpad
          address: 0x1008
          value: 0x0001  # Yellow LED

  - id: led_2_on
    then:
      - modbus_controller.write_register:
          id: wallpad
          address: 0x1008
          value: 0x0102

  - id: led_2_off
    then:
      - modbus_controller.write_register:
          id: wallpad
          address: 0x1008
          value: 0x0002

  - id: led_3_on
    then:
      - modbus_controller.write_register:
          id: wallpad
          address: 0x1008
          value: 0x0104

  - id: led_3_off
    then:
      - modbus_controller.write_register:
          id: wallpad
          address: 0x1008
          value: 0x0004

  - id: led_4_on
    then:
      - modbus_controller.write_register:
          id: wallpad
          address: 0x1008
          value: 0x0108

  - id: led_4_off
    then:
      - modbus_controller.write_register:
          id: wallpad
          address: 0x1008
          value: 0x0008

I have 4 KC868-E16P-V2.3 with firmware version 2.2.14, after about one week, they go offline, no TUYA access(TUYA show Offline), and there is no Web-access. I have to power off/on to make them come online. It's random witch controller who goes offline, but all of them goes offline during one week or so.
They are powered by a MeanWell 12V 2.5A DIN-rail powersupply.

Hello

What is the suitable power supply voltage for KC868-16 - is the 13,5 V ok as well? Whats the minimum?

Hey there, 

some feedback and problems we detected on two N30 devices.

• Flash Guide with ESP Download Tool is incomplete, the guideline let you think to use the KCS bin file only. This is not correct, you will need more files (partion etc) to be able to flash.
  ESPHome Webflasher is the solution as it also accept the KCS Firmware File.
  

• EnergyConsumption in kWh seems to be not working in KCS Firmware (major bug!) Same problem as in Link
  

• Voltage Calibration is not possible in KCS Firmware
  
  
• Are negative power readings possible? 
  

• If yes, can there be an independent energy calculation per input for positive/negative consumption readings?
  

Hello,
I am looking for a KinCony solution for a professional home lighting automation setup.
Requirements:

• 16-channel relay controller (220V AC)
  
• Use of standard mechanical wall switches (2-way / 3-way)
  
• Real light state feedback (Home Assistant must always know ON/OFF state, even when switched manually)
  
• Mandatory Home Assistant integration (MQTT / ESPHome / native)
  
• Minimal GPIO usage (no one-GPIO-per-switch design)
  

1. Which KinCony model(s) do you recommend?
   
2. How is state feedback implemented (dry contact, relay feedback, current sensing, etc.)?
   
3. Do you have wiring diagrams or documentation for this scenario?
   

Attached Files

Thumbnail(s)
   

The DO1 output physically shows a high state. After uploading new software, when logging in directly to the controller, the inputs and outputs are disabled, but DO1 physically remains on all the time. I have no idea what is causing this. I haven’t connected any relays to the outputs yet.

Hello, I recently received an N20. I have access to it via Ethernet, but I can't connect it to "kinconyn20.local" nor can I connect it to Home Assistant. The strange thing is that it connects via MQTT from Home Assistant.

As soon as the device arrived, I flashed it to version v3 3.18.0. Its IP address is 192.168.3.78 (within my network range, OK), and its Wi-Fi access point is 192.168.4.1.

Is the problem that it can't access "kinconyn20.local"? Why doesn't Home Assistant recognize it?

I need to check the configuration of the CT clamps, as well as the L1 and L2 power inputs, which are not appearing.

I'm Spanish, sorry for the autotranslated English.

Attached Files

Thumbnail(s)