I am a student at BUT Brno, Faculty of Electrical Engineering, in the Czech Republic, and I am interested in IoT. At work, we often handle electrical installations and consulting projects, and I would like to suggest that we start implementing Smart Home systems. We have experience with Home Assistant, having built a few homes with it.
I believe that by learning with your system and implementing it in Home Assistant, we could integrate your products more frequently. To demonstrate this potential, I would like to design a smaller smart switchboard at home to showcase to the company. I think this fits with Situation B – starting a project.
If possible, I would be interested in the KC868-A4.
Thank you for considering my request.
Trump

После прошивки  KCS_KC868_A6_V2.2.6.zip плата перестала загружаться на кнопки S1 и S2 не реагирует. flash_download_tool_3.9.2 находиться постоянно в синхронизации.  Порт COM определяется. Как оживить плату ).

Attached Files

Thumbnail(s)
   

I am experiencing intermittent connectivity issues with my KinCony controller when it's operating in Cloud mode (using the KinCony Smart Home app). It connects initially, but after a few minutes, the connection drops, and I am unable to control the devices remotely. My home network is stable, and I have tested other cloud-connected devices without issues. Could this be related to specific firewall settings or is there any recommended troubleshooting procedure for improving the cloud connection reliability on both the controller and the app side? Also, are there any known server-side issues with KinCony's cloud infrastructure?

Hi, my A64 mosfet with esphome has a problem. Every active output turn off exactly after 15min.
Installation was configured under home assistant but for test HA server was not installed

Hi, I’m working on a project using the KC868-A16 to drive a relay board, and I really appreciate the KCS firmware available for this device. However, I have a concern: it seems that every output change is saved to NVS storage, which could be an issue. I’ll be frequently changing the output state of the MOSFETs, and I’m worried about potentially wearing out the storage. There might be some balancing implemented but none the less having the option to not persist to NVS would be great.

To clarify, I don’t need the output or input states to persist in NVS; storing them in SRAM would be preferable. Since the KCS firmware source code isn’t publicly available, I can’t modify this behavior myself unless I write my own firmware (something I’m considering).


Does anyone have any thoughts on this?

Please help us with the 3D files of the following parts
1.kc868-e16v2-din-rail-relay-module
2. 5-hole-row-ground-copper-bar-for-distribution-box
3. logic-level-converter-for-dc0v-to-12v
4. rc-absorption-snubber-circuit-module

How do i connect to the 868-E16P with TUYA license installed. I try to use my Iphone with the Smart Life app with the QR code on 868-E16P local website, this redirects me to https://smartapp.smart321.com, and there i get the message "package not found".

Attached Files

Image(s)
       

Is it possible to have direct RX / TX pins of the esp32 to be used in ESPHome?

I'm not using RS485 for example, could that be replaced? Any alternatives?

Hello. I'm configuring the KC868-A8 board with Esphome and the Tuya license. However, I found some errors and would like to share them for a possible solution. KC868-A8 board esphome + Tuya
It's giving an error that I don't know exactly. error image attached.





# Basic Config
esphome:
  name: kc868-a8-contato-web-dht-tuya2
  platform: ESP32
  board: esp32dev

external_components:
  - source:
      type: git
      url: https://github.com/hzkincony/esphome-tuya-iot
      ref: v1.2.0

# Enable logging
logger:
  baud_rate: 0

api:
  encryption:
    key: "It2KB/xCg0EuwXMc1KyiTXRTSjr0hdQXmxQXnwIVmOE="

ota:
  - platform: esphome
    password: "70604538ddb4bdb4362c2d63114dfb1d"


i2c:
  sda: 4
  scl: 5
  scan: true
  id: bus_a


ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT
  phy_addr: 0

  # Add web server
web_server:
  port: 80
  auth:
    username: admin
    password: "admin"

text_sensor:
  - platform: homeassistant
    name: "Casa Inteligente"
    id: home_assistant_text
    entity_id: input_text.test


pcf8574:
  - id: 'pcf8574_hub_out_1'  # for output channel 1-8
    address: 0x24

  - id: 'pcf8574_hub_in_1'  # for input channel 1-8
    address: 0x22


time:
  - platform: homeassistant
    id: homeassistant_time


# Individual outputs
switch:
  - platform: gpio
    name: "light1"
    id: light1
    pin:
      pcf8574: pcf8574_hub_out_1
      number: 0
      mode: OUTPUT
      inverted: true
    restore_mode: RESTORE_DEFAULT_ON
    on_turn_on:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output1", true);
    on_turn_off:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output1", false);

  - platform: gpio
    name: "light2"
    id: light2
    pin:
      pcf8574: pcf8574_hub_out_1
      number: 1
      mode: OUTPUT
      inverted: true
    restore_mode: RESTORE_DEFAULT_ON
    on_turn_on:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output2", true);
    on_turn_off:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output2", false);

  - platform: gpio
    name: "light3"
    id: light3
    pin:
      pcf8574: pcf8574_hub_out_1
      number: 2
      mode: OUTPUT
      inverted: true
    restore_mode: RESTORE_DEFAULT_ON
    on_turn_on:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output3", true);
    on_turn_off:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output3", false);

  - platform: gpio
    name: "light4"
    id: light4
    pin:
      pcf8574: pcf8574_hub_out_1
      number: 3
      mode: OUTPUT
      inverted: true
    restore_mode: RESTORE_DEFAULT_ON
    on_turn_on:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output4", true);
    on_turn_off:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output4", false);

  - platform: gpio
    name: "light5"
    id: light5
    pin:
      pcf8574: pcf8574_hub_out_1
      number: 4
      mode: OUTPUT
      inverted: true
    restore_mode: RESTORE_DEFAULT_ON
    on_turn_on:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output5", true);
    on_turn_off:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output5", false);

  - platform: gpio
    name: "light6"
    id: light6
    pin:
      pcf8574: pcf8574_hub_out_1
      number: 5
      mode: OUTPUT
      inverted: true
    restore_mode: RESTORE_DEFAULT_ON
    on_turn_on:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output6", true);
    on_turn_off:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output6", false);

  - platform: gpio
    name: "light7"
    id: light7
    pin:
      pcf8574: pcf8574_hub_out_1
      number: 6
      mode: OUTPUT
      inverted: true
    restore_mode: RESTORE_DEFAULT_ON
    on_turn_on:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output7", true);
    on_turn_off:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output7", false);

  - platform: gpio
    name: "light8"
    id: light8
    pin:
      pcf8574: pcf8574_hub_out_1
      number: 7
      mode: OUTPUT
      inverted: true
    restore_mode: RESTORE_DEFAULT_ON
    on_turn_on:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output8", true);
    on_turn_off:
      - lambda: !lambda |-
          id(tuya_iot_component).property_report("output8", false);

binary_sensor:
  - platform: gpio
    name: "input1"
    on_press:
      then:
        - switch.toggle: light1
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 0
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "input2"
    on_press:
      then:
        - switch.toggle: light2
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 1
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "input3"
    on_press:
      then:
        - switch.toggle: light3
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 2
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "input4"
    on_press:
      then:
        - switch.toggle: light4
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 3
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "input5"
    on_press:
      then:
        - switch.toggle: light5
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 4
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "input6"
    on_press:
      then:
        - switch.toggle: light6
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 5
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "input7"
    on_press:
      then:
        - switch.toggle: light7
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 6
      mode: INPUT
      inverted: true

  - platform: gpio
    name: "input8"
    on_press:
      then:
        - switch.toggle: light8
    pin:
      pcf8574: pcf8574_hub_in_1
      number: 7
      mode: INPUT
      inverted: true


  - platform: gpio
    name: "a8-s3"
    pin:
      number: 32
      inverted: true

  - platform: gpio
    name: "a8-s4"
    pin:
      number: 33
      inverted: true

one_wire:
  - platform: gpio
    pin: GPIO14

sensor:
  - platform: dallas_temp
    name: "Temperatura QCC"
    id: temperatura_1
    address: 0x06136e7e1f64ff28  # Endereço específico do sensor
    accuracy_decimals: 1  # Precisão do sensor em casas decimais
    update_interval: 30s  # Intervalo de atualização dos dados

 
  - platform: dht
    pin: GPIO13  # Ajuste para o pino que você está usando
    model: DHT22  # Substitua pelo modelo do seu sensor (DHT11, DHT22, AM2301, etc.)
    temperature:
      name: "Temperatura externa"
    humidity:
      name: "Umidade externa"
    update_interval: 30s  # Ajuste o intervalo de atualização conforme necessário

tuya_iot:
  id: tuya_iot_component
  product_id: xxx
  device_id: xxx
  device_secret: xxx
  region: us # eu, us, eus, weu, in, cn
  # eu: Central Europe Data Center
  # us: US West Data Center
  # eus: US East Data Center
  # weu: Western Europe Data Center
  # in: India Data Center
  # cn: Chinese Data Center

  on_event:
    - event_name: property/set
      then:
        - lambda: !lambda |-
              // Append the required switch in switch_map to respond to commands issued by Tuya.
              static std::map<float, switch_::Switch*> switch_map {
                { 1, id(light1) },
                { 2, id(light2) },
                { 3, id(light3) },
                { 4, id(light4) },
                { 5, id(light5) },
                { 6, id(light6) },
                { 7, id(light7) },
                { 8, id(light8) },
              };
 ......>

Attached Files

Thumbnail(s)
   

Hello,

I have purchased the KC868-ATC V1.4 and want to use the rs232 functionality to control a Heat recovery system.
I use the tuya app to control my house, however i am not sure how to convert this app and KC868-ATC to the full protocol functionallity in the pdf...

Anyone any ideas?

I have a tuya developer account and Arduino IDE, i have created a IDE code, but doesn't work, the connection to tuya is missing i think...

Attached Files

  Protocol_Eng.pdf (Size: 1.34 MB / Downloads: 1949)