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)

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.

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.
    

• 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.
  

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)
   

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.

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

BUEN DÍA

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

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.

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: