Smart Home Automation Forum
Portal

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

Username
  

Password
  

Search Forums

(Advanced Search)

Forum Statistics
» Members: 10,242
» Latest member: paulrothenbergmd
» Forum threads: 4,267
» Forum posts: 21,181

Full Statistics

Online Users
There are currently 409 online users.
» 0 Member(s) | 392 Guest(s)
AhrefsBot, Amazonbot, Applebot, Baidu, Bytespider, Google, PetalBot, bot

Latest Threads
KC868-A32 - TCP comunicat...
Forum: KC868-A series and Uair Smart Controller
Last Post: admin
Yesterday, 11:11 PM
» Replies: 3
» Views: 61
Suggestion for Kincony bo...
Forum: DIY Project
Last Post: cautionking
Yesterday, 07:42 AM
» Replies: 2
» Views: 641
4-20mA temperature sensor...
Forum: AIO Hybrid
Last Post: admin
Yesterday, 12:24 AM
» Replies: 0
» Views: 19
MQTT Discovery: missing s...
Forum: N30
Last Post: admin
Yesterday, 12:05 AM
» Replies: 2
» Views: 317
IFTTT
Forum: KC868-A16
Last Post: admin
10-14-2026, 10:22 PM
» Replies: 11
» Views: 200
SSD not visible for insta...
Forum: Pi5R16
Last Post: admin
10-13-2026, 01:16 PM
» Replies: 16
» Views: 240
KC868-AI mDNS problem
Forum: KC868-AI
Last Post: admin
10-13-2026, 01:30 AM
» Replies: 4
» Views: 130
KC868-A16 and Tuya
Forum: KC868-A series and Uair Smart Controller
Last Post: admin
10-13-2026, 01:27 AM
» Replies: 11
» Views: 344
N30 (KCS): energy counter...
Forum: N30
Last Post: admin
10-12-2026, 05:52 AM
» Replies: 2
» Views: 96
N60 Loss of kWh on reset
Forum: N60
Last Post: admin
10-12-2026, 05:51 AM
» Replies: 13
» Views: 1,421

  KC868A6
Posted by: Chris89 - 02-04-2025, 07:37 PM - Forum: "KCS" v2 firmware system - Replies (1)

I have bought a kincony 868A6. The first time, red led power in on and 6 other red leds are blinking and clicking. I have a 12V power. But now only the red led power is on. No blinking and no clicking for the 6 red leds.
Unpossible to use flashtools. The board is recognized whan i put the usb. But nothing other. Is the board out of order? I try to reset it with the button. Nothing.
What can i do? Send to the seller? thanks for your answer
Christian (France)

Print this item

  M16 Warning: Component <unknown> took a long time for an operation
Posted by: linuxeux - 02-04-2025, 02:42 PM - Forum: KC868-M16 / M1 / MB / M30 - Replies (3)

Hi,
I just received my M16 and I flash it with ESPHome. Everything seems to work properly but the logs are flooded by a Warning that I don't know how to solve. I saw a post similar and putting the frequency at 400kHz solved the problem but not for me. Here is a snapshot of thoses warnings:

[09:09:52][W][component:238]: Components should block for at most 30 ms.
[09:09:52][W][component:237]: Component <unknown> took a long time for an operation (53 ms).
[09:09:52][W][component:238]: Components should block for at most 30 ms.
[09:09:59][W][component:237]: Component <unknown> took a long time for an operation (52 ms).
[09:09:59][W][component:238]: Components should block for at most 30 ms.
[09:10:07][W][component:237]: Component <unknown> took a long time for an operation (52 ms).
[09:10:07][W][component:238]: Components should block for at most 30 ms.
[09:10:09][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:10:09][W][component:238]: Components should block for at most 30 ms.
[09:10:12][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:10:12][W][component:238]: Components should block for at most 30 ms.
[09:10:17][W][component:237]: Component <unknown> took a long time for an operation (52 ms).
[09:10:17][W][component:238]: Components should block for at most 30 ms.
[09:10:22][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:10:22][W][component:238]: Components should block for at most 30 ms.
[09:10:22][W][component:237]: Component <unknown> took a long time for an operation (54 ms).
[09:10:22][W][component:238]: Components should block for at most 30 ms.
[09:10:24][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:10:24][W][component:238]: Components should block for at most 30 ms.
[09:10:29][W][component:237]: Component <unknown> took a long time for an operation (53 ms).
[09:10:29][W][component:238]: Components should block for at most 30 ms.
[09:10:32][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:10:32][W][component:238]: Components should block for at most 30 ms.
[09:10:42][W][component:237]: Component <unknown> took a long time for an operation (54 ms).
[09:10:42][W][component:238]: Components should block for at most 30 ms.
[09:10:44][W][component:237]: Component <unknown> took a long time for an operation (52 ms).
[09:10:44][W][component:238]: Components should block for at most 30 ms.
[09:10:47][W][component:237]: Component <unknown> took a long time for an operation (54 ms).
[09:10:47][W][component:238]: Components should block for at most 30 ms.
[09:10:52][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:10:52][W][component:238]: Components should block for at most 30 ms.
[09:10:54][W][component:237]: Component <unknown> took a long time for an operation (53 ms).
[09:10:54][W][component:238]: Components should block for at most 30 ms.
[09:10:57][W][component:237]: Component <unknown> took a long time for an operation (53 ms).
[09:10:57][W][component:238]: Components should block for at most 30 ms.
[09:11:07][W][component:237]: Component <unknown> took a long time for an operation (53 ms).
[09:11:07][W][component:238]: Components should block for at most 30 ms.
[09:11:12][W][component:237]: Component <unknown> took a long time for an operation (55 ms).
[09:11:12][W][component:238]: Components should block for at most 30 ms.
[09:11:17][W][component:237]: Component <unknown> took a long time for an operation (58 ms).
[09:11:17][W][component:238]: Components should block for at most 30 ms.
[09:11:22][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:11:22][W][component:238]: Components should block for at most 30 ms.
[09:11:24][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:11:24][W][component:238]: Components should block for at most 30 ms.
[09:11:34][W][component:237]: Component <unknown> took a long time for an operation (51 ms).
[09:11:34][W][component:238]: Components should block for at most 30 ms.

Print this item

  Help with Bioreactor Automation
Posted by: propag8tor - 02-04-2025, 05:42 AM - Forum: DIY Project - Replies (6)

Seeking Advice: Automating a CO₂-Controlled Bioreactor System with Raspberry Pi & KinCony

Hi everyone,
I’m building a temporary immersion bioreactor system for tissue culturing trees for restoration projects. I want to design a scalable, automated system that integrates CO₂ monitoring, solenoid-controlled gas flow, and light automation—with the ability to log data for future AI optimization.

System Overview:

  • Bioreactors: 10 shelves, each with 10 bioreactors (total of 100).
  • Aeration:
    • Each bioreactor receives CO₂-enriched air from a pump inside a CO₂ incubator (for sterilization and elevated CO₂ levels).
    • I plan to monitor CO₂ levels in 1 vessel per shelf (10 total monitored vessels).
    • The CO₂ sensor data will control a solenoid valve (normally closed) to regulate CO₂ for the entire shelf.
  • Lighting:
    • I want automated lighting with control based on PPFD (Photosynthetic Photon Flux Density) or intensity.
  • Data Logging & AI Integration:
    • The system should log all data (CO₂ levels, light intensity, etc.) for future AI-driven optimization.

My Approach & Questions:
  • I plan to use a Raspberry Pi as the main controller.
  • I’ve come across KinCony products and believe they could provide a solution. Has anyone used KinCony for similar automation projects?
  • I’d love suggestions for CO₂ sensors, solenoid controllers, and light intensity sensors that integrate well with a Raspberry Pi & KinCony setup.
  • I want to allow for future expansion, so modularity and scalability are key.


If anyone can offer suggestions or advice it would be extremely appreciated.  I attached an image to help understand what it is I am building.
Thanks 

[Image: view?usp=drive_link]

Print this item

  Product packaging
Posted by: mitzuuu89 - 02-03-2025, 08:55 AM - Forum: Suggestions and feedback on KinCony's products - Replies (1)

Hi,

I've just received my K868-A32 and K868-A16s boards in Romania.

I just want to suggest to improve the package wrapping, the K868-A32 plastic case came broken. 

Thanks! Looking forward to installing the boards.



Attached Files Thumbnail(s)
   
Print this item

  [arduino code examples for A16v3]-13 read DS18B20 temperature sensors
Posted by: admin - 02-03-2025, 06:17 AM - Forum: KC868-A16v3 - No Replies

Code:
// https://github.com/junkfix/esp32-ds18b20

#include "OneWireESP32.h"
const uint8_t MaxDevs = 1;
float currTemp[MaxDevs];

void tempTask(void *pvParameters){
    OneWire32 ds1(47); //gpio pin
    OneWire32 ds2(48); //gpio pin
  OneWire32 ds3(38); //gpio pin

    uint64_t addr1[MaxDevs];
  uint64_t addr2[MaxDevs];
  uint64_t addr3[MaxDevs];
    
    //uint64_t addr[] = {
    //    0x183c01f09506f428,
    //    0xf33c01e07683de28,
    //};
    
    //to find addresses
    uint8_t devices1 = ds1.search(addr1, MaxDevs);
    for (uint8_t i = 0; i < devices1; i += 1) {
        Serial.printf("T1: 0x%llx,\n", i, addr1[i]);
        //char buf[20]; snprintf( buf, 20, "0x%llx,", addr[i] ); Serial.println(buf);
    }

    uint8_t devices2 = ds2.search(addr2, MaxDevs);
    for (uint8_t i = 0; i < devices2; i += 1) {
        Serial.printf("T2: 0x%llx,\n", i, addr2[i]);
        //char buf[20]; snprintf( buf, 20, "0x%llx,", addr[i] ); Serial.println(buf);
    }

    uint8_t devices3 = ds3.search(addr3, MaxDevs);
    for (uint8_t i = 0; i < devices3; i += 1) {
        Serial.printf("T3: 0x%llx,\n", i, addr3[i]);
        //char buf[20]; snprintf( buf, 20, "0x%llx,", addr[i] ); Serial.println(buf);
    }
    //end

    for(;;){
        ds1.request();
    ds2.request();
    ds3.request();
        vTaskDelay(750 / portTICK_PERIOD_MS);
        for(byte i = 0; i < MaxDevs; i++){
            uint8_t err = ds1.getTemp(addr1[i], currTemp[i]);
            if(err){
                const char *errt[] = {"", "CRC", "BAD","DC","DRV"};
                Serial.print(i); Serial.print(": "); Serial.println(errt[err]);
            }else{
                Serial.print("T1"); Serial.print(": "); Serial.println(currTemp[i]);
            }
        }

        for(byte i = 0; i < MaxDevs; i++){
            uint8_t err = ds2.getTemp(addr2[i], currTemp[i]);
            if(err){
                const char *errt[] = {"", "CRC", "BAD","DC","DRV"};
                Serial.print(i); Serial.print(": "); Serial.println(errt[err]);
            }else{
                Serial.print("T2"); Serial.print(": "); Serial.println(currTemp[i]);
            }
        }

        for(byte i = 0; i < MaxDevs; i++){
            uint8_t err = ds3.getTemp(addr3[i], currTemp[i]);
            if(err){
                const char *errt[] = {"", "CRC", "BAD","DC","DRV"};
                Serial.print(i); Serial.print(": "); Serial.println(errt[err]);
            }else{
                Serial.print("T3"); Serial.print(": "); Serial.println(currTemp[i]);
            }
        }

        vTaskDelay(3000 / portTICK_PERIOD_MS);
    }
} // tempTask

void setup() {
    delay(1000);
    Serial.begin(115200);
    xTaskCreatePinnedToCore(tempTask, "tempTask", 4096,  NULL,  1,  NULL, 0);
}


void loop() {}
arduino ino file download:
.zip   13-ds18b20.zip (Size: 888 bytes / Downloads: 835)
BIN file (you can use esp32 download tool download to ESP32-S3 with address 0x0 then directly to use) download:
.zip   13-ds18b20.ino.merged.zip (Size: 183.21 KB / Downloads: 833)

Print this item

  Multiple fan wall project advice
Posted by: coroee - 02-02-2025, 04:39 PM - Forum: DIY Project - Replies (2)

Hello all!

We are working on an art project which consists of 8 walls of server brushless fans that are separated from each other.  in each wall there are 30 12v 0.2a fans, and 18 24v 0.5 fans. 

We would like to create different cycling programs in each wall that are triggered by a message from a main controller (esp32 / RPi) 
The walls are separated from each other so we thought that going wireless should be the cleanest way to build it.

We thought to use a Kincony A6 for each wall, that reads the message through esp-now or controlled by esphome or KCS firmware (can it control several boards?). 

I'm a pretty technical guy but making first steps into home automation.. so.. 

1. Does this setup make sense or is there a more elegant solution? 
2. I have some arduino coding knowledge but tempted by the GUI offered through the other solutions - which one of them provides just what I need, including manual on/off triggering of all connected boards + program scheduling?
3. Will the relays bear 6 amps 24v each for several seconds, going on and off for half an hour year (5 days a week, 10 hours per day), or should I opt for SSRs?

Many thanks and a lovely week to come! 

Roee.

Print this item

Thumbs Down THT22 and 5v
Posted by: jltluc57 - 02-02-2025, 09:58 AM - Forum: Development - Replies (17)

Improvement to be made:

I find it a shame that it is not specified in the documentation that to use the THT22 it must be in 5 volts.
You have to look on the forum.

In addition, it is not clean to go and get the 5v on the RF port, it is a DIY job.
An external terminal block would be more judicious.

Maybe in the future...




Board : KC868-A16

Print this item

  aduino and kc86822a to D1
Posted by: sistemasyusa - 02-01-2025, 04:35 PM - Forum: KC868-A2 - No Replies

BUEN DÍA

PUEDES CONECTAR UN ARDUINO A D1 Y HACER COMUNICACIÓN SERIAL Y TENDRÁS UN EJEMPLO, TANQUES

Print this item

  Explanation of how the inputs and outputs work
Posted by: twostar - 02-01-2025, 06:53 AM - Forum: Development - No Replies

While investigating the possibility of a hack to deal with this issue I had a look at the circuit diagram to see if there was a way to wire an output back to an input to get the necessary chaining of IFTTT rules (thanks to Kincony for publishing this, it would have been much harder trying to trace it on a multilayer board with SMDs).

In case this is useful to others, here's how things work.  In particular if you're confused about dry vs. wet contacts and so on, read on.  The circuit diagram is a bit tricky to read since there are elements scattered across it in different locations, there are groups of pullups, snubber diodes, and other things off by themselves that you have to link to the main circuit element, if I've made any mistakes please let me know.

For the inputs, one side of the optocoupler LEDs is tied to 12V and the other, which corresponds to the dry-contact inputs, has a pullup to 12V when the contact is open and gets connected to GND when the contact is closed.  So contact open = no opto LEDs lit, contact closed = opto LEDs lit.  This is how an input dry contact is turned into a wet contact.

For the outputs, there's a p-channel MOSFET that switches a voltage onto the output.  This one is a bit confusing because if you look at the board images there's a 12/24V DC input next to the output connectors rather than the expected GND.  What happens is that when the output is off there's an open circuit between the 12/24VDC input and the output connector.  When it's on the voltage from the input connector is switched onto the output connector, with the GND provided separately.  In other words you externally wire the GND to the board and whatever it is you're driving from the output, and only a single wire, the output, goes to the other device with the GND shared between them.

This possibly also means you can switch something other than 12V or 24V onto the output, the inputs on the, ah, outputs are labelled LO0 and LO1 and only appear on the output side of the output optocouplers, so you may be able to run 5V relays off them by feeding in 5V on the "12/24V DC" input.

Print this item

  Chaining IFTTT rules
Posted by: twostar - 02-01-2025, 01:30 AM - Forum: Development - Replies (7)

The KC868 (almost) makes a great PLC for home automation, but one thing I can't find is any ability to chain IFTTT rules.  The rule table has "IF NUM" and "THEN NUM" entries which look like they would allow this but they're all set to zero and can't be edited.

To explain what I mean here, it's the ability to say IF <rule 1 condition met> THEN <goto rule 2>, where <rule 2> allows testing further conditions.  Let's say you want to use the device as an alarm controller, so you want to test:

Code:
IF ( motion_sensor1 OR motion_sensor2 OR motions_sensor3 ) AND is_armed THEN siren
The IFTTT rules only allow OR or AND but not complex expressions like the above, so it'd have to be done as:
Code:
rule1: IF ( motion_sensor1 OR motion_sensor2 OR motions_sensor3 ) THEN rule2
rule2: IF ( rule1 AND is_armed ) THEN siren_on + rule3
rule3: IF ( rule2 ) THEN delay 10 minutes + siren_off
Another example is for an aquarium pump controller where the IFTTT is almost perfect except for the ability to chain rules, I can sense inputs, add timing delays, run the pump as an output, but I need the ability to connect multiple rules to do that similar to the alarm.

Is there any way to chain rules in this manner, and if not could it be added?

Print this item