I'm new to this system and need to start a new project soon and test that on my house network first.
I had before X10 modules that are 220 volt coil and each module for one circuit single phase with momentary switch, mobile apps and RF remote i had 1 home automation panel that contain all house interior floors lighting load that are coming from 2 sources main and emergency through 3 DB's 
Then finally the automation panel contain the following
1- 2 sources main, emergency 3 phases
2- 3 DBs each are 3 phases
3. All relays are 220 volt coil and distributed each phase and source

If you are trying to replace the system to DC coil 12 volt then you need for each source and single phase a separate AC 220v/ 12 vdc converter
This mean that you need for the automation panel 
3 converters for emergency to present each phase.
6 converters for main 3 for each DB.
Then i need to convert to DC 9 separate converters.
Other wise you will use single phase for emergency as an example phase R convert to DC 12 v and feed all controllers if this phase failed all system will be off.

I really need to know the big reason behind the all system 12 v DC coils !?
And is any way to release version with 220 v AC coil?

You applied free sample KC868-A8 have sent by YANWEN, tracking number is VR445934410YP .

Hope your project goes well and share everyone your achievements.

Is this a possibility to use the open source OpenSprinkler ported firmware ?

https://opensprinkler.com/forums/topic/e...-firmware/

https://github.com/arijav/AriloSprinkler..._dev_esp32

If there is no technical barrier, then I guess the I/O of this board needs to be matched on the OpenSprinkler build I/O ?
Thanks.

esphome:
  name: kc868-a4
  platform: ESP32
  board: esp32dev
 
output:
  - platform: esp32_dac
    pin: GPIO25
    id: dac_output2
  - platform: esp32_dac
    pin: GPIO26
    id: dac_output1

light:
  - platform: monochromatic
    output: dac_output1
    name: "KC868-A4-DAC1"
    gamma_correct: 2
    id: dac_light1
  - platform: monochromatic
    output: dac_output2
    name: "KC868-A4-DAC2"
    id: dac_light2

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: "3b853165e19b67ba8193c59fe59f21a7"

wifi:
  ssid: "KinCony"
  password: "a12345678"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Kc868-A4 Fallback Hotspot"
    password: "RgIGz8qo4bVC"

captive_portal:

1: Ethernet work mode = "TCP Server"

controller is a "server", your software is "client".

2: WiFi work mode = "TCP Server"

controller is a "server", your software is "client".

3: Ethernet work mode = "TCP Client"

your software is a "server", controller is "client". when power on, controller will auto connect to your software by ethernet. just "client" will auto connect to "server".

4: WiFi work mode = "TCP Client" instead by MQTT in new firmware

your software is a "server", controller is "client". when power on, controller will auto connect to your software by wifi. just "client" will auto connect to "server".

5: Ethernet work mode = "TCP Client"; WiFi work mode = "TCP Server"

A. your software is a "server", controller is "client". when power on, controller will auto connect to your software by ethernet.

B. controller is a "server", you software is "client".

use one KC868-COL/COLB/COLBS send command to KC868-H32BS, KC868-D8 dimmer controller by RS485 modbus. MAX support 254 devices.

   

Hi,
I just opened and connected by COLB. I am able to visualize the change of status of the DI input ports from the smart board controller app.
I would like to know
1. what is the procedure to update the firmware step by step - I could not find the right thread in the forum, sorry if I missed something
2. I cannot connect to the web interface where to configure the MQTT server - I can only see the interface as attached to this message.

Any help is welcome!

Thanks
Lee

Attached Files

Thumbnail(s)
   

improvement:

support set domain for your own server. old version only set server IP address by number. This verison can set by a server domain name for TCP and MQTT server, added DNS function.

download the ZIP file , unzip update the bin file for KC868-H32BS relay controller by USB-RS232 cable.

  H32BS_V141_211101.zip (Size: 52.11 KB / Downloads: 893)

Hi
I have H32L I connect it to home assistant : https://www.kincony.com/how-to-create-sw...stant.html
When I power on or off channel from switch terminal board  or wall push bottom it power on but the real status not update on home assistant  app is not changing the status in home assistant to on or off
i work whit node-red ,          , need help whit this

ESPHome configure for KC868-A8:

function list:
1. 8 relay output
2. 8 switch input trigger relay output by on_press action
3. monitor 2 channel analog input for DC
4. TEMP-1 port: 2 channel DS18B20 temperature sensor use by 1 ports, actually, you can connect multi DS18B20 by one wire.
5. TEMP-4 port: WS2812B LED strip for 1 meter (30 LEDs)
6. network by Ethernet cable

   
-----------------------------------------------------------------------------------------------------

esphome:
  name: kc868-a8
  platform: ESP32
  board: esp32dev

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: "bfb55afbf347b27a4bda0a1d36ee994f"

web_server:
  port: 80


# Example configuration entry for ESP32
i2c:
  sda: 4
  scl: 5
  scan: true
  id: bus_a
 
# Example configuration entry
ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT
  phy_addr: 0

  # Optional manual IP
  manual_ip:
    static_ip: 192.168.1.199
    gateway: 192.168.1.1
    subnet: 255.255.255.0


# Example configuration entry
pcf8574:
  - id: 'pcf8574_hub_output'
    address: 0x24
   
  - id: 'pcf8574_hub_input'
    address: 0x22


# Individual outputs
switch:
  - platform: gpio
    name: "switch1"
    id: switch1
    pin:
      pcf8574: pcf8574_hub_output
      # Use pin number 0
      number: 0
      # One of INPUT or OUTPUT
      mode: OUTPUT
      inverted: true
 
  - platform: gpio
    name: "switch2"
    id: switch2
    pin:
      pcf8574: pcf8574_hub_output
      # Use pin number 0
      number: 1
      # One of INPUT or OUTPUT
      mode: OUTPUT
      inverted: true
     
  - platform: gpio
    name: "switch3"
    id: switch3
    pin:
      pcf8574: pcf8574_hub_output
      # Use pin number 0
      number: 2
      # One of INPUT or OUTPUT
      mode: OUTPUT
      inverted: true
     
  - platform: gpio
    name: "switch4"
    id: switch4
    pin:
      pcf8574: pcf8574_hub_output
      # Use pin number 0
      number: 3
      # One of INPUT or OUTPUT
      mode: OUTPUT
      inverted: true
     
  - platform: gpio
    name: "switch5"
    id: switch5
    pin:
      pcf8574: pcf8574_hub_output
      # Use pin number 0
      number: 4
      # One of INPUT or OUTPUT
      mode: OUTPUT
      inverted: true
     
  - platform: gpio
    name: "switch6"
    id: switch6
    pin:
      pcf8574: pcf8574_hub_output
      # Use pin number 0
      number: 5
      # One of INPUT or OUTPUT
      mode: OUTPUT
      inverted: true
     
  - platform: gpio
    name: "switch7"
    id: switch7
    pin:
      pcf8574: pcf8574_hub_output
      # Use pin number 0
      number: 6
      # One of INPUT or OUTPUT
      mode: OUTPUT
      inverted: true
     
  - platform: gpio
    name: "switch8"
    id: switch8
    pin:
      pcf8574: pcf8574_hub_output
      # Use pin number 0
      number: 7
      # One of INPUT or OUTPUT
      mode: OUTPUT
      inverted: true
     
binary_sensor:     
  - platform: gpio
    name: "input1"
    pin:
      pcf8574: pcf8574_hub_input
      # Use pin number 0
      number: 0
      # One of INPUT or OUTPUT
      mode: INPUT
      inverted: false
    on_press:
      then:
        - switch.toggle: switch1
       
  - platform: gpio
    name: "input2"
    pin:
      pcf8574: pcf8574_hub_input
      # Use pin number 0
      number: 1
      # One of INPUT or OUTPUT
      mode: INPUT
      inverted: false
    on_press:
      then:
        - switch.toggle: switch2
       
  - platform: gpio
    name: "input3"
    pin:
      pcf8574: pcf8574_hub_input
      # Use pin number 0
      number: 2
      # One of INPUT or OUTPUT
      mode: INPUT
      inverted: false
    on_press:
      then:
        - switch.toggle: switch3
       
  - platform: gpio
    name: "input4"
    pin:
      pcf8574: pcf8574_hub_input
      # Use pin number 0
      number: 3
      # One of INPUT or OUTPUT
      mode: INPUT
      inverted: false
    on_press:
      then:
        - switch.toggle: switch4
       
  - platform: gpio
    name: "input5"
    pin:
      pcf8574: pcf8574_hub_input
      # Use pin number 0
      number: 4
      # One of INPUT or OUTPUT
      mode: INPUT
      inverted: false
    on_press:
      then:
        - switch.toggle: switch5
       
  - platform: gpio
    name: "input6"
    pin:
      pcf8574: pcf8574_hub_input
      # Use pin number 0
      number: 5
      # One of INPUT or OUTPUT
      mode: INPUT
      inverted: false
    on_press:
      then:
        - switch.toggle: switch6
       
  - platform: gpio
    name: "input7"
    pin:
      pcf8574: pcf8574_hub_input
      # Use pin number 0
      number: 6
      # One of INPUT or OUTPUT
      mode: INPUT
      inverted: false
    on_press:
      then:
        - switch.toggle: switch7
       
  - platform: gpio
    name: "input8"
    pin:
      pcf8574: pcf8574_hub_input
      # Use pin number 0
      number: 7
      # One of INPUT or OUTPUT
      mode: INPUT
      inverted: false
    on_press:
      then:
        - switch.toggle: switch8
       
       
# Example configuration entry
dallas:
  - pin: GPIO14
    update_interval: 5s
sensor:
  - platform: dallas
    address: 0xE701202C5ADED628
    name: "Temperature_1"
    id: Temperature_1
   
  - platform: dallas
    address: 0xBE012115DCBEBC28
    name: "Temperature_2"
    id: Temperature_2
   
  - platform: adc
    pin: GPIO34
    name: "Analog-IN1"
    update_interval: 5s
    attenuation: 11db

  - platform: adc
    pin: GPIO35
    name: "Analog-IN2"
    update_interval: 5s
    attenuation: 11db
   

light:
  - platform: fastled_clockless
    chipset: WS2812B
    pin: GPIO33    # Pin Define connected with LED strip
    num_leds: 150  #LEDs number
    rgb_order: GRB
    name: "light_strip"
    effects:
      - addressable_rainbow:        ##defined 7 effects styles
      - addressable_color_wipe:
      - addressable_scan:
      - addressable_twinkle:
      - addressable_random_twinkle:
      - addressable_fireworks:
      - addressable_flicker:

-------------------------------------------------------------------------------
KC868-A8/A4 http command list for third party software integration:

read relay state:
http://192.168.1.199/switch/switch1

control relay:
http://192.168.1.199/switch/switch1/turn_on
http://192.168.1.199/switch/switch1/turn_off
http://192.168.1.199/switch/switch1/toggle

read DI state:
http://192.168.1.199/binary_sensor/input1

read temperature:
http://192.168.1.199/sensor/temperature_1

read analog input:
http://192.168.1.199/sensor/analog-in1

read LED strip:
http://192.168.1.199/light/light_strip

control LED strip:
http://192.168.1.199/light/light_strip/turn_on
http://192.168.1.199/light/light_strip/turn_off
http://192.168.1.199/light/light_strip/turn_toggle

debug send command for TEST example: curl -X POST http://192.168.1.199/switch/switch1/toggle