IFTTT
1) If -> DI1 Rising Edge, and, DO1 OFF -> Then -> Toggle DO2 , DO1 ON
2) If _> DI1 Rising Edge, and, DO1 ON -> Then -> Toggle DO3, DO1 OFF
When I test the code via IFTTT by clicking "run," it works.
However, when I use my pushbutton DI1, output DO1 turns on and I get a pulse from DO2.
This happens repeatedly, no matter how many times I press the button.
The output doesn't turn off when I press the button a second time.
It seems like the "If DO1 on" nor the "If DO1 off" is working.
Will there be an option to back up settings?
With the option to restore the backup after an update.
Greeting from Finland!
I just finished installation of my N60 yesterday and I got it sending data to my mqtt broker. Installation, upgrading the firmware and auto discovery worked flawlessly.
Overall great device and I have been looking for couple of years for a solution to monitor my entire electricity usage on fuse level. This is first reasonable product to do this.
Some basic information. I am using KCS V3 Firmware version v3.18.0. Connected with ethernet in my IOT VLAN. Monitoring three phase system with 3x16 fuses.
Power measurement appears to be reasonably accurate. I am using DL-CT03CL1.0 2000:1 current transformers. No Coefficients factors used for current power or energy.
I discovered some bugs in the MQTT integration.
N60 not sending energy (kwh) information in MQTT message:
Example Monitor1 Channel 8:
Home Assistant data
Data from Kincony webUI
MQTT data from MQTT Explorer
N60 is periodically sending kwh energy data but is not correct.
Incorrect state_class
Some of the measurement types have incorrect state class statement. Measurement is basically working but these entities cannot be used as Devices in
Home Assistant Energy dashboard. For power meter Energy dashboard assume device type: power and state class: measurement.
Currently N60 sends incorrectly:
unit_of_measurement: W
device_class: power
friendly_name: 3.1 Valo Keittiö Power
(state_class missing)
This is working example:
state_class: measurement
unit_of_measurement: W
device_class: power
friendly_name: EVSE 2 Total Power
There is a workaround to create helper entities from raw data from power sensor but this quite tedious to do 96 times for 48 channels (power and energy measurement).
Power Factor
Third observation is about power factor calculation. For some reason only one of six monitors are giving reasonable value. This is not usually super important in normal domestic
house as we are not charged for reactive power. For me this is interesting measurement as I run my house mostly battery powered and heat pumps generate quite a lot reactive power
and this strains inverters. It would be nice to know exact reactive power values. reference voltages match measured phases.
I am measuring L1 with monitor 1 and 2, L2 with monitor 3 and 4 and L3 with monitor 5 and 6.
Hopefully we can get these small bugs sorted out soon enough. Another possibility would be to use ESPHome but I really like the idea of this easy MQTT auto-discovery. So easy when
it works.
BR, Veikko Suihkonen
PS. My screen installation is kind of wonky. I see very little use for the screen anyway but I wonder what went wrong? Also, wifi is disabled on my N60. Software could be changed to show
"[Wifi] disabled" or something else on screen if it really is disabled. This could prevent some confusion in future.
Posted by: aksurd - 12-12-2025, 04:05 AM - Forum: DIY Project
- No Replies
1. Introduction
Hello everyone,
I purchased the KC868-A16V3 controller and was genuinely impressed by its hardware capabilities. To explore its potential beyond smart home applications, I developed a fully functional OPC UA server as a proof-of-concept. This project transforms the A16V3 into a practical industrial OPC UA data gateway. 2. Project Overview & Features
This is a stable, working implementation that demonstrates the controller's ability to serve as an industrial communication node:
OPC UA Server: Full server implementation based on open62541 and ESP-IDF.
Hardware Support: Utilizes all core I/O of the A16V3:
16 digital input/output channels (via integrated PCF8574).
4 analog input (ADC) channels.
Performance: Achieves consistent read times of less than 5ms per tag in testing.
Real-World Validation: Successfully integrated and tested with an industrial SCADA system (Simple SCADA). Screenshots are attached below.
Complete & Open: All source code is available, documented, and ready to be built upon.
3. Proof of Concept & Evidence
The project is not a commercial product but a verified and stable proof-of-concept. The screenshots below show the server's data points (tags) being actively read and monitored in a real SCADA client interface, confirming successful integration.
*(Прикрепи здесь 1-2 ключевых скриншота из Simple SCADA)* 4. Project Goals & Status
Primary Goal: To demonstrate that affordable, accessible hardware like the KC868-A16V3 can be effectively adapted for standard industrial protocols.
Current Status:Stable proof-of-concept. All core functionalities are implemented, tested, and operational. The code provides a solid foundation for further development, pilot projects, or customization.
Disclaimer: This is an open-source community project, not an official or commercial product from KinCony.
Good evening,
I am writing to report an issue with a KC868-A16 board: the firmware fails to upload.
I have strictly followed the procedure detailed in the following guide:https://www.kincony.com/esp32-kcsv2-firmware.html
An explanatory video detailing all the actions I perform is attached to this request.
Details of Troubleshooting Performed
- I have tested the procedure on three different PCs.
- I have tried using both USB 2.0 and USB 3.0 ports.
- The flashing program does not return any error, but the firmware is not uploaded.
Error Message Displayed
The only message that appears in the flashing tool is:
