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

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 10,552
» Latest member: geekshared
» Forum threads: 4,337
» Forum posts: 21,344

Full Statistics

Online Users
There are currently 290 online users.
» 0 Member(s) | 276 Guest(s)
Applebot, Baidu, Bing, Bytespider, Crawl, Google, PetalBot, bot

Latest Threads
KCS debounce option for K...
Forum: KC868-A16
Last Post: tech1977
9 hours ago
» Replies: 0
» Views: 29
[arduino code examples fo...
Forum: F32
Last Post: admin
Today, 04:27 AM
» Replies: 0
» Views: 21
[arduino code examples fo...
Forum: F32
Last Post: admin
Today, 04:25 AM
» Replies: 0
» Views: 19
KC868-A16 wiring diagram
Forum: KC868-A16
Last Post: admin
Yesterday, 09:31 PM
» Replies: 24
» Views: 22,078
N20 energy
Forum: N20
Last Post: admin
Yesterday, 09:29 PM
» Replies: 1
» Views: 26
Automatic Modbus Sensor p...
Forum: "KCS" v3 firmware
Last Post: admin
Yesterday, 09:27 PM
» Replies: 4
» Views: 122
[arduino code examples fo...
Forum: CO16
Last Post: admin
Yesterday, 04:33 AM
» Replies: 0
» Views: 30
KC868-A8 PCB V1.7 - Maxim...
Forum: KC868-A8
Last Post: admin
11-16-2026, 09:29 AM
» Replies: 1
» Views: 63
Device change after damag...
Forum: Getting Started with ESPHome and Home Assistant
Last Post: grayweird
11-16-2026, 04:43 AM
» Replies: 2
» Views: 779
CT Clamp Compatibility
Forum: KC868-M16 / M1 / MB / M30
Last Post: admin
11-14-2026, 11:38 PM
» Replies: 16
» Views: 3,851

  N10 - ESPHome - ARM CPU streams continuously, Modbus requests never transmitted
Posted by: luzozo13 - 09-09-2026, 08:39 AM - Forum: N10 - Replies (3)

Hello,

I am trying to integrate a new N10 board with ESPHome (v2026.8.0) and Home Assistant. After extensive testing I have isolated the problem precisely and hope someone who has successfully set up an N10 with ESPHome can help, or that KinCony staff can clarify some undocumented behaviour.

Board: KinCony N10 (ESP32-S3-WROOM-1U N16R8, 16MB flash)
ESPHome version: 2026.8.0
Chip: Freshly erased with esptool before first flash

SYMPTOM

ESPHome's modbus_controller never transmits a single request to the BL0910 ARM CPU. The UART RX line (GPIO10) is flooded with data from the moment power is applied, before ESPHome sends anything. Because ESPHome's Modbus component sees a perpetually busy bus, its frame-guard logic refuses to ever transmit. Every log shows thousands of "Clearing buffer of 2 bytes — timeout after partial response" messages and zero TX lines.

DIAGNOSTIC STEPS COMPLETED

1. Bare UART only (no modbus: component)
RX line completely silent for 60+ seconds. Confirmed the ARM CPU does NOT stream data unprovoked.

2. modbus: component, slave address 1, 115200 baud (ESPHome Devices reference config)
Continuous noise on RX, zero TX ever logged.

3. modbus: component, slave address 100, 38400 baud (per KinCony's own protocol document)
Same continuous noise, BUT real data bursts appeared embedded in the RX stream. This is the only configuration where the ARM CPU visibly responds — confirmed it is responding to address 100, not address 1.

4. All baud rates tested: 9600, 19200, 38400, 115200 with slave address 100.
Best results at 38400 (real data bursts visible). Other baud rates produce background patterns consistent with framing mismatch.

5. Boot drain lambda (on_boot reads and discards all RX bytes before modbus_controller initialises)
No effect, TX still never appears.

WHAT I BELIEVE IS HAPPENING

When ESPHome's modbus: component initialises, something causes the ARM CPU to enter a continuous streaming state. Once streaming starts, ESPHome can never transmit. Without the modbus: component, the ARM CPU stays completely quiet.

QUESTIONS

1. Does the N10 ARM CPU require the KCS factory firmware to run first and perform an initialisation before it will behave as a standard Modbus RTU slave? Has anyone successfully used ESPHome on a freshly-erased N10?

2. Can anyone confirm the correct slave address? Our testing points to 100, not 1 as shown in the ESPHome Devices reference config.

3. Can anyone confirm the correct baud rate? KinCony's protocol document says 38400; the ESPHome Devices reference says 115200. Our best results were at 38400.

4. Is there a known way to suppress the ARM CPU's startup streaming from ESPHome, so the Modbus component can get its first request out?

MINIMAL REPRODUCING CONFIG

Code:
esphome:
  name: n10-test
esp32:
  board: esp32-s3-devkitc-1
  variant: esp32s3
  framework:
    type: arduino
logger:
  hardware_uart: USB_SERIAL_JTAG
api:
ethernet:
  type: W5500
  clk_pin: GPIO42
  mosi_pin: GPIO43
  miso_pin: GPIO44
  cs_pin: GPIO41
  interrupt_pin: GPIO2
  reset_pin: GPIO1
uart:
  id: uart_bl0910
  tx_pin: GPIO9
  rx_pin: GPIO10
  baud_rate: 38400
  stop_bits: 1
  data_bits: 8
  parity: NONE
  debug:
    direction: BOTH
modbus:
  uart_id: uart_bl0910
modbus_controller:
  - id: energy_meter
    address: 100
    update_interval: 30s
sensor:
  - platform: modbus_controller
    modbus_controller_id: energy_meter
    address: 162
    register_type: holding
    name: "Line Voltage"
    unit_of_measurement: V
    value_type: U_WORD
    filters:
      - multiply: 0.01

Any help appreciated. Thank you.

Print this item

  KNX ETS software project file for CO16
Posted by: admin - 09-08-2026, 03:44 AM - Forum: CO16 - No Replies

   
   
ETS project download:

.zip   CO16.zip (Size: 103.09 KB / Downloads: 145)

Print this item

  "KCS" v3.27.1 firmware BIN file download
Posted by: admin - 09-08-2026, 03:24 AM - Forum: "KCS" v3 firmware - No Replies

new version improvement:

Optimized memory issues to fix BACnet/IP protocol stack startup.



Attached Files
.zip   KCS_A2V3_V3.27.1.zip (Size: 1.26 MB / Downloads: 146)
.zip   KCS_A6V3_V3.27.1.zip (Size: 1.24 MB / Downloads: 156)
.zip   KCS_A8V3_V3.27.1.zip (Size: 1.29 MB / Downloads: 153)
.zip   KCS_A16V3_V3.27.1.zip (Size: 1.31 MB / Downloads: 157)
.zip   KCS_A32PRO_V3.27.1.zip (Size: 1.28 MB / Downloads: 146)
.zip   KCS_AG8_V3.27.1.zip (Size: 1.23 MB / Downloads: 140)
.zip   KCS_AGV3_V3.27.1.zip (Size: 1.17 MB / Downloads: 146)
.zip   KCS_AIO_HYBRID_V3.27.1.zip (Size: 1.48 MB / Downloads: 142)
.zip   KCS_ALR_V3.27.1.zip (Size: 1.21 MB / Downloads: 142)
.zip   KCS_B2_V3.27.1.zip (Size: 1.3 MB / Downloads: 143)
.zip   KCS_B4_V3.27.1.zip (Size: 1.3 MB / Downloads: 141)
.zip   KCS_B4M_V3.27.1.zip (Size: 1.3 MB / Downloads: 133)
.zip   KCS_B8_V3.27.1.zip (Size: 1.3 MB / Downloads: 136)
.zip   KCS_B8M_V3.27.1.zip (Size: 1.3 MB / Downloads: 134)
.zip   KCS_B16_V3.27.1.zip (Size: 1.3 MB / Downloads: 146)
.zip   KCS_B16M_V3.27.1.zip (Size: 1.3 MB / Downloads: 134)
.zip   KCS_B24_V3.27.1.zip (Size: 1.3 MB / Downloads: 133)
.zip   KCS_B24M_V3.27.1.zip (Size: 1.3 MB / Downloads: 138)
.zip   KCS_B32M_V3.27.1.zip (Size: 1.3 MB / Downloads: 144)
.zip   KCS_CO16_V3.27.1.zip (Size: 1.29 MB / Downloads: 148)
.zip   KCS_DM4_V3.27.1.zip (Size: 1.3 MB / Downloads: 140)
.zip   KCS_DM8_V3.27.1.zip (Size: 1.3 MB / Downloads: 131)
.zip   KCS_DM16_V3.27.1.zip (Size: 1.27 MB / Downloads: 139)
.zip   KCS_DM32_V3.27.1.zip (Size: 1.3 MB / Downloads: 140)
.zip   KCS_F4_V3.27.1.zip (Size: 1.29 MB / Downloads: 146)
.zip   KCS_F8_V3.27.1.zip (Size: 1.29 MB / Downloads: 142)
.zip   KCS_F16_V3.27.1.zip (Size: 1.3 MB / Downloads: 144)
.zip   KCS_F24_V3.27.1.zip (Size: 1.3 MB / Downloads: 138)
.zip   KCS_F32_V3.27.1.zip (Size: 1.3 MB / Downloads: 156)
.zip   KCS_G1_V3.27.1.zip (Size: 1.23 MB / Downloads: 135)
.zip   KCS_KC_TA_V3.27.1.zip (Size: 1.25 MB / Downloads: 140)
.zip   KCS_MT4_V3.27.1.zip (Size: 1.23 MB / Downloads: 144)
.zip   KCS_N10_V3.27.1.zip (Size: 1.14 MB / Downloads: 130)
.zip   KCS_N20_V3.27.1.zip (Size: 1.14 MB / Downloads: 135)
.zip   KCS_N30_V3.27.1.zip (Size: 1.14 MB / Downloads: 141)
.zip   KCS_N60_V3.27.1.zip (Size: 1.16 MB / Downloads: 131)
.zip   KCS_T16M_V3.27.1.zip (Size: 1.24 MB / Downloads: 129)
.zip   KCS_T32M_V3.27.1.zip (Size: 1.26 MB / Downloads: 133)
.zip   KCS_T64M_V3.27.1.zip (Size: 1.26 MB / Downloads: 138)
.zip   KCS_T128M_V3.27.1.zip (Size: 1.26 MB / Downloads: 135)
.zip   KCS_TR_V3.27.1.zip (Size: 1.2 MB / Downloads: 135)
.zip   KCS_Z1_V3.27.1.zip (Size: 1.37 MB / Downloads: 139)
Print this item

  wish
Posted by: R43 - 09-07-2026, 12:36 PM - Forum: KC868-A16v3 - Replies (5)

Пожалуйста, добавьте Weigand в вывод MQTT.

Print this item

  "KCS" v3.27 firmware BIN file download
Posted by: admin - 09-07-2026, 02:51 AM - Forum: "KCS" v3 firmware - No Replies

new version improvement:

1: support CO16 controller
2: added BACnet, DMX512, KNX protocols
3: added enable/disable Tuya module option
4: added "Modbus Slave Debugger" tool in webpage



Attached Files
.zip   KCS_B32M_V3.27.0.zip (Size: 1.3 MB / Downloads: 139)
.zip   KCS_A2V3_V3.27.0.zip (Size: 1.26 MB / Downloads: 131)
.zip   KCS_A6V3_V3.27.0.zip (Size: 1.24 MB / Downloads: 142)
.zip   KCS_A8V3_V3.27.0.zip (Size: 1.29 MB / Downloads: 134)
.zip   KCS_A16V3_V3.27.0.zip (Size: 1.31 MB / Downloads: 142)
.zip   KCS_A32PRO_V3.27.0.zip (Size: 1.28 MB / Downloads: 131)
.zip   KCS_AG8_V3.27.0.zip (Size: 1.23 MB / Downloads: 129)
.zip   KCS_AGV3_V3.27.0.zip (Size: 1.17 MB / Downloads: 135)
.zip   KCS_AIO_HYBRID_V3.27.0.zip (Size: 1.48 MB / Downloads: 139)
.zip   KCS_ALR_V3.27.0.zip (Size: 1.21 MB / Downloads: 133)
.zip   KCS_B2_V3.27.0.zip (Size: 1.3 MB / Downloads: 145)
.zip   KCS_B4_V3.27.0.zip (Size: 1.3 MB / Downloads: 141)
.zip   KCS_B4M_V3.27.0.zip (Size: 1.3 MB / Downloads: 144)
.zip   KCS_B8_V3.27.0.zip (Size: 1.3 MB / Downloads: 134)
.zip   KCS_B8M_V3.27.0.zip (Size: 1.3 MB / Downloads: 152)
.zip   KCS_B16_V3.27.0.zip (Size: 1.3 MB / Downloads: 129)
.zip   KCS_B16M_V3.27.0.zip (Size: 1.3 MB / Downloads: 130)
.zip   KCS_B24_V3.27.0.zip (Size: 1.3 MB / Downloads: 136)
.zip   KCS_B24M_V3.27.0.zip (Size: 1.3 MB / Downloads: 137)
.zip   KCS_CO16_V3.27.0.zip (Size: 1.29 MB / Downloads: 139)
.zip   KCS_DM4_V3.27.0.zip (Size: 1.3 MB / Downloads: 143)
.zip   KCS_DM8_V3.27.0.zip (Size: 1.3 MB / Downloads: 129)
.zip   KCS_DM16_V3.27.0.zip (Size: 1.27 MB / Downloads: 146)
.zip   KCS_DM32_V3.27.0.zip (Size: 1.3 MB / Downloads: 130)
.zip   KCS_F4_V3.27.0.zip (Size: 1.29 MB / Downloads: 133)
.zip   KCS_F8_V3.27.0.zip (Size: 1.29 MB / Downloads: 134)
.zip   KCS_F16_V3.27.0.zip (Size: 1.3 MB / Downloads: 140)
.zip   KCS_F24_V3.27.0.zip (Size: 1.3 MB / Downloads: 151)
.zip   KCS_F32_V3.27.0.zip (Size: 1.3 MB / Downloads: 130)
.zip   KCS_G1_V3.27.0.zip (Size: 1.23 MB / Downloads: 139)
.zip   KCS_KC_TA_V3.27.0.zip (Size: 1.25 MB / Downloads: 135)
.zip   KCS_MT4_V3.27.0.zip (Size: 1.23 MB / Downloads: 139)
.zip   KCS_N10_V3.27.0.zip (Size: 1.14 MB / Downloads: 141)
.zip   KCS_N20_V3.27.0.zip (Size: 1.14 MB / Downloads: 143)
.zip   KCS_N30_V3.27.0.zip (Size: 1.14 MB / Downloads: 140)
.zip   KCS_N60_V3.27.0.zip (Size: 1.16 MB / Downloads: 135)
.zip   KCS_T16M_V3.27.0.zip (Size: 1.24 MB / Downloads: 132)
.zip   KCS_T32M_V3.27.0.zip (Size: 1.26 MB / Downloads: 137)
.zip   KCS_T64M_V3.27.0.zip (Size: 1.26 MB / Downloads: 137)
.zip   KCS_T128M_V3.27.0.zip (Size: 1.26 MB / Downloads: 133)
.zip   KCS_TR_V3.27.0.zip (Size: 1.2 MB / Downloads: 136)
.zip   KCS_Z1_V3.27.0.zip (Size: 1.37 MB / Downloads: 127)
Print this item

  OLED not found in I2C scan
Posted by: Armsp0 - 09-07-2026, 01:28 AM - Forum: KC868-A6v3 - Replies (1)

I have an OLED screen 1.5" 128x128 IC: SH1107. I can use this screen on esp32 dev board or ESP8266 without issue. If i connect to my KC868 A6 I2C bus it does not get found with i2C scan. I find its address using I2C scan on another device as 0x3C. if i go ahead and use that address in a EspHome yaml configuration to try and force a connection it fails. could this be pull up resistor issue?

Print this item

  ESPHome modbus not functional
Posted by: Bergoglio - 09-06-2026, 05:56 PM - Forum: KC868-A8S - Replies (3)

Hello, we recently bought and set up the KC868-A8S with a Midea heat pump. ESPHome was used to set up the switches, binary sensors and modbus. The first two work as intended, while the modbus seemingly not being able to read or send requests properly.

Here is the chunk of the code that relates to and might influence the modbus and one of the sensors:

Code:
esphome:
  name: centralina-freddo
  friendly_name: Centralina freddo

esp32:
  variant: ESP32
  flash_size: 4MB
  board: esp32dev

logger:

api:
  encryption:
    key: [cencored for privacy]

ota:
  - platform: esphome
    password: [cencored for privacy]

i2c:
  - id: bus_a
    sda: GPIO4
    scl: GPIO5
    scan: true

ethernet:
  type: LAN8720
  clk:
    pin: GPIO17
    mode: CLK_OUT
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  phy_addr: 0

uart:
  - id: uart_1
    tx_pin: GPIO33
    rx_pin: GPIO32
    baud_rate: 9600
    stop_bits: 1
    parity: NONE
    data_bits: 8
    rx_full_threshold: 8B
    debug:
      direction: BOTH

modbus:
  - id: modbus_1
    uart_id: uart_1
    role: client

modbus_controller:
  - id: modbus_controller_1
    address: 0x01
    modbus_id: modbus_1
    setup_priority: -10
    update_interval: 15s
   

sensor:
  - platform: modbus_controller
    name: "Temp. Esterna (PdC)"
    id: pdc_esterna_TP
    modbus_controller_id: modbus_controller_1
    address: 107
    register_type: holding
    unit_of_measurement: °C
    device_class: temperature
    state_class: measurement
    value_type: S_WORD
    accuracy_decimals: 1

Attempted fixes (that did not work):
  • phisically inverting the A and B connections
  • changing the modbus controller adress
  • changing the sensor adress to hexadecimal
  • changing the register type
  • changing the value type
  • adding accuracy decimals
  • changing th esp variant from inf to dev
  • changing the api to be more generic
  • inverting the tx and rx pins
  • changing the parity to even and odd
  • changing the amount of data bits
  • changing the amount of rx_full_threshold
  • removing the client role
  • removing the uart id
  • changing the update interval
  • decreasing the turnaround time to 50ms

At the moment, with this code, the log output repeats these lines:
Quote:[19:49:26.943][W][modbus:1214]: Clearing buffer of 21 bytes - timeout after partial response 1188899ms after last send
[19:49:26.954][D][uart_debug:113]: <<< 7E:66:66:00:66:F8:FE:18:E6:FE:E6:F8:FE:FE:E6:06:FE:E6:F8:FE:FE
Quote:[19:50:11.845][D][modbus:1118]: Frame already active for 1 with 2 requests pending, refused
[19:50:11.847][D][modbus_controller:204]: Poll refused by hub for range 0x68


We are unsure of what to do, and I am out of ideas on how to fix this.
All the GPIOs are correct. They have been checked.

Any help would be appreciated,
Thank you

Print this item

  Kc868ia
Posted by: Pingonet - 09-05-2026, 01:45 PM - Forum: KC868-AI - Replies (1)

Hello Can someone help me to get my New Board working in Esp-Home 

I keep getting errors on the board .


component:164]: Setup i2c took 762ms
[15:31:32][D][esp-idf:000]: E (889) i2c.master: I2C hardware timeout detected
[15:31:32][W][component:290]: pcf8574 set Warning flag: unspecified
[15:31:32][E][pcf8574:010]: PCF8574 not available under 0x24
[15:31:32][E][component:204]: pcf8574 was marked as failed
[15:31:32][E][component:297]: pcf8574 set Error flag: unspecified
[15:31:32][D][esp-idf:000]: E (912) i2c.master: I2C hardware timeout detected
[15:31:32][W][component:290]: pcf8574 set Warning flag: unspecified
[15:31:32][E][pcf8574:010]: PCF8574 not available under 0x25
[15:31:32][E][component:204]: pcf8574 was marked as failed
[15:31:32][E][component:297]: pcf8574 set Error flag: unspecified
[15:31:32][D][esp-idf:000]: E (945) i2c.master: I2C hardware timeout detected
[15:31:32][W][component:290]: pcf8574 set Warning flag: unspecified
[15:31:32][E][pcf8574:010]: PCF8574 not available under 0x21
[15:31:32][E][component:204]: pcf8574 was marked as failed
[15:31:32][E][component:297]: pcf8574 set Error flag: unspecified
[15:31:32][D][esp-idf:000]: E (978) i2c.master: I2C hardware timeout detected
[15:31:32][W][component:290]: pcf8574 set Warning flag: unspecified
[15:31:32][E][pcf8574:010]: PCF8574 not available under 0x22
[15:31:32][E][component:204]: pcf8574 was marked as failed
[15:31:32][E][component:297]: pcf8574 set Error flag: unspecified
[15:31:32][D][esp-idf:000]: E (1000) i2c.master: I2C hardware timeout detected
[15:31:32][W][component:290]: pcf8574 set Warning flag: unspecified
[15:31:32][E][pcf8574:010]: PCF8574 not available under 0x26
[15:31:32][E][component:204]: pcf8574 was marked as failed
[15:31:32][E][component:297]: pcf8574 set Error flag: unspecified
[15:31:32][D][esp-idf:000]: E (1034) i2c.master: I2C hardware timeout detected
[15:31:32][W][component:290]: pcf8574 set Warning flag: unspecified
[15:31:32][E][pcf8574:010]: PCF8574 not available under 0x23
[15:31:32][E][component:204]: pcf8574 was marked as failed
[15:31:32][E][component:297]: pcf8574 set Error flag: unspecified
[15:31:37][C][component:164]: Setup ethernet took 4328ms
[15:31:37][W][component:290]: api set Warning flag: waiting for client connection
[15:31:37][I][app:117]: setup() finished successfully!
compo

Print this item

  KC868-H32B
Posted by: kulibin - 09-05-2026, 10:18 AM - Forum: KC868-HxB series Smart Controller - Replies (5)

Hi . What is the maximum wire diameter I can connect for out terminal ?  32 relay х 10 A  [Image: vc6KWqVK]
   

Print this item

  Request for Type B Project
Posted by: lemanat - 09-03-2026, 08:47 AM - Forum: Apply for free sample product - No Replies

Application for Free Sample – KC868-A4 ESP32 Board
Project: KinCony-Powered DIY Smart Home & Smart Distribution System – Kenya
Dear KinCony Team,
My name is Nathan, and I am based in Kenya. I am currently working on my own residential house project, and one of my main objectives is to design and implement a comprehensive DIY smart home automation system for the house.
Over the past few months, I have researched different home automation solutions, including proprietary commercial systems as well as DIY platforms. During this research, I came across KinCony and became particularly interested in your products and approach to DIY home automation.
I have come to really like KinCony because it provides the flexibility and control that I am looking for. Rather than being completely dependent on a closed or proprietary ecosystem, I would like to build a system that I can understand, modify, expand and integrate with other technologies.
My Proposed Smart Home Project
My intention is to build the automation system progressively, starting with testing and learning the KinCony platform and eventually developing a comprehensive smart distribution and automation system for the house.
In particular, I am very interested in using KinCony's: 32CH Smart Distribution Box Solution with Home Assistant & Energy Monitoring as the main distribution and automation system for the house.
I believe this solution could provide an excellent foundation for centralizing the control of lighting, appliances, electrical circuits and energy monitoring while allowing Home Assistant to provide the overall smart-home interface and automation platform.
My vision is to have the electrical distribution system designed around smart control from the beginning rather than adding smart devices as an afterthought.
Areas I Intend to Automate
Depending on the results of my testing and the final design, I would like to automate and monitor areas such as:
  • Indoor and outdoor lighting
  • Security lighting
  • Garden and exterior lighting
  • Water pump control
  • Selected appliance circuits
  • Electric water heating
  • Gate and access-control systems
  • Motion and door sensors
  • Security-related automation
  • Energy monitoring
  • Automated schedules
  • Timers and scenes
  • Remote monitoring and control
  • Energy usage optimization
  • Integration with other smart-home sensors and devices
I would also like to explore how different parts of the house can work together through Home Assistant to create useful automation scenarios rather than simply providing remote ON/OFF switching.
For example, I would like to explore scenarios where lighting, motion sensors, security systems, energy monitoring and scheduled events interact automatically.
Why I Would Like to Start With the KC868-A4
I would like to request the KC868-A4 ESP32 board as a starting point for the project.
Before committing to a larger installation, I want to properly understand and test the KinCony ecosystem in a real-world environment.
I would use the KC868-A4 to experiment with relay control, sensors, automation logic, Home Assistant integration and other aspects of the KinCony platform.
The experience gained from this initial testing would then help me make informed decisions when designing the larger smart distribution system for my house.
I am particularly interested in understanding:
  • How reliably the KC868-A4 operates in a residential environment.
  • Its integration with Home Assistant.
  • How it can interact with sensors and other smart devices.
  • How the system behaves during network interruptions.
  • Local versus remote control capabilities.
  • Automation and scheduling possibilities.
  • Energy monitoring and management possibilities.
  • Expansion possibilities as the house automation grows.
  • The practical installation requirements for a Kenyan residential environment.
I believe there is significant potential for smart-home automation in Kenya.
Many people constructing new homes are increasingly interested in modern electrical systems, security, energy efficiency, automated gates, smart lighting and remote control.
However, many homeowners are still unfamiliar with DIY smart-home systems, while some commercial solutions can be expensive or lock the homeowner into a particular ecosystem.
This is one of the reasons I am particularly interested in KinCony.
The combination of ESP32-based hardware, flexible DIY control, Home Assistant and smart electrical distribution is very interesting to me because it potentially allows homeowners to have a much greater understanding and control of their own automation system.
My house will therefore serve as a practical test and learning environment.
In addition to automating my own house, I am also interested in exploring the possibility of introducing and marketing home automation solutions in Kenya.
As I learn more about KinCony products and gain practical experience with the installation, configuration and integration process, I would like to evaluate whether KinCony's solutions could be offered to other homeowners who are looking for affordable and flexible smart-home systems.
I believe the best way for me to do this responsibly is to first install and test the technology in my own house.
This would allow me to understand the system from an installer, developer and homeowner perspective before recommending it to other people.
What I Would Provide to the KinCony Community
If KinCony is able to provide me with a KC868-A4 sample, I would be happy to document the project and share my experience with the KinCony community.
I intend to document:
  1. My initial setup and configuration of the KC868-A4.
  2. Testing of the relay outputs and inputs.
  3. Integration with Home Assistant.
  4. Wiring and automation concepts.
  5. Practical applications within my house.
  6. Testing results and lessons learned.
  7. Integration ideas for the larger smart distribution system.
  8. Photos and videos of the project where appropriate.
  9. Tutorials or practical guides based on my experience.
  10. Feedback regarding the product's strengths, limitations and suitability for residential applications in Kenya.
My intention is to create useful information that can help other people understand what is possible with KinCony products.
My long-term goal is to develop a fully integrated DIY smart home where the electrical distribution, automation, security and energy monitoring systems work together.
The KinCony 32CH Smart Distribution Box Solution with Home Assistant & Energy Monitoring is currently one of the solutions I am most interested in evaluating as the main distribution and control platform for this project.
The KC868-A4 would give me an opportunity to start learning and testing the KinCony ecosystem before implementing the larger system.
If the testing is successful, I would be interested in expanding the project with additional KinCony hardware and eventually using the experience gained to help introduce smart-home automation solutions to other homeowners in Kenya.
I would therefore be very grateful if the KinCony team would consider my project for a free KC868-A4 ESP32 sample.
I am not looking at the sample simply as a free product. I see it as an opportunity to learn, test, build, document and demonstrate what can be achieved with KinCony technology in a real Kenyan home.
I believe this project could become a useful real-world demonstration of KinCony's DIY smart-home ecosystem and potentially provide valuable exposure to a growing market for home automation in Kenya.
Thank you for considering my application. I look forward to the opportunity to work with KinCony and share my experience with the community.
Nathan Noah

Print this item