Smart Home Automation Forum - N30

N30 most recent ESPhome

Fri, 23 Oct 2026 18:31:05 +0800

Hello!

I'm interested in buying the N30, but I see multiple issues on this forum about the current direction detection.

I came accross this one on the forum:
https://www.kincony.com/forum/attachment.php?aid=9375

This one is on the webshop: (i guess this is the wrong one?)
https://www.kincony.com/forum/attachment.php?aid=8460

This one on ESPHOME: (also older one?)
https://devices.esphome.io/devices/kincony-n30/

Which N30 ESPHome configuration correctly expose signed, bidirectional active power for each BL0910 CT channel?
Which is the most recent ESPHOME config?

N30 (KCS): energy counters of BL0910 #2 and #3 published as 0 kWh at boot

Fri, 09 Oct 2026 16:34:06 +0800

Hello,

I found an issue with the energy counters on the N30 running KCS firmware (version: v3.27.2), integrated in Home Assistant through MQTT discovery.

What happens:
Each time the N30 restarts (firmware flash, power cut, reboot), the channels of BL0910 #2 and #3 (Energy 2 and Energy 3, all 10 channels each, plus energy_total) publish energy = 0 kWh for a moment, then the real value again a few seconds later.
BL0910 #1 (Energy 1) does not do this. Its channels only go unavailable during the restart and come back with the correct value, never 0.

The counters are not lost inside the N30: after the restart the values continue from where they were (e.g. 258.062 kWh -> 0 -> 258.062 kWh).

Why it is a problem:
Home Assistant treats energy sensors as increasing counters (state_class: total_increasing). A drop to 0 is seen as a meter reset, and the return to the real value is counted as new consumption.
This morning the N30 restarted 3 times after a firmware flash. Each channel of Energy 2 and Energy 3 was counted as consuming its whole counter value 4 times. For example, one channel with 258 kWh got 1032 kWh of phantom consumption added in one morning. I had to correct the statistics by hand.

Request:
Please do not publish energy values until the real counters have been read from the BL0910 chips at boot. Publishing nothing (or keeping the previous retained value) is fine. Publishing 0 is not.
It would also help to know why only chips #2 and #3 behave like this and not chip #1.

Thank you.

Best way to read from N30

Fri, 25 Sep 2026 17:13:36 +0800

Hi all,

I am building a new home setup, with a Proxmox server hosting Home Assistant, Mosquitto, VictoriaMetrics and Grafana. I am about to install an N30 into my switchboard, and would like to collect data from it into VictoriaMetrics, as well as use the energy data for Home Assistant dashboards and automations. Ideally the energy data would be recorded into VictoriaMetrics at one second intervals, while Home Assistant should deal with a lower frequency of data, e.g. every 30 seconds.

What is the best (not necessarily simplest) way to do this? I can't find much documentation on the relative merits and functionality of the ESPHome vs KCS v3 firmware, how quickly the energy data updates, or which protocol would be best suited. Note the N30 will be connected by Ethernet, and I also have an Elfin EE11 RS485-Ethernet adapter if that's helpful. I'm also happy to install extra software (e.g. Telegraf) into Proxmox if that provides a better solution.

Modbus 485 extender kcs V3 and lora and PCB eletechsup 10ioA12

Fri, 11 Sep 2026 13:18:15 +0800

Buongiorno vorrei capire se posso integrare in kcs V3 queste schede modbus 485 rele e input eletechsup 10ioA12, la scheda ha 12 relè e 12 input tramite modbus. Inoltre vorrei sapere se posso comandare una scheda a6 sempre con lora slave? Inoltre volevo sapere a quale distanza massima posso installare i CT dalla scheda?

Current direction detection incorrect on channels 2 and 3

Thu, 13 Aug 2026 18:49:03 +0800

Hello,
I have also noticed another issue with the KinCony N30 when using the current direction detection.
My N30 has three rows/modules, and all of my current clamps are installed and wired in exactly the same physical direction.
However, when I enable the current direction detection, I get inconsistent results:

Module 1: current direction is detected correctly and the power values are positive.
Module 2: the power values are negative.
Module 3: the power values are also negative.

This happens even though the clamps on modules 1, 2 and 3 are installed in exactly the same direction.
Without current direction detection, the measured power values are otherwise consistent.
This makes me suspect that there may be an issue with the polarity/sign handling or current direction detection in the firmware for modules 2 and 3.
Could you please check whether the current direction detection is implemented identically for all three modules?
In particular, I would like to know whether there is a firmware configuration or calibration parameter that could cause modules 2 and 3 to have their current direction inverted compared with module 1.
The expected behavior is that, with all clamps physically oriented in the same direction, the three modules should report the same sign for the same direction of current.
Thank you.
Capture d’écran 2026-08-13 à 12.48.33.png (Size: 5.73 MB / Downloads: 213)
Capture d’écran 2026-08-13 à 12.48.10.png (Size: 5.36 MB / Downloads: 234)

MQTT Discovery: missing state_class for power sensors in Home Assistant

Thu, 13 Aug 2026 18:41:45 +0800

Hello,
I noticed an issue with the MQTT Discovery configuration generated by the N30 when the device is integrated into Home Assistant.
For example, Home Assistant creates the following entity:

Code:
sensor.n30_d0cf13020244_energy2_ch2_power

The N30 publishes this MQTT Discovery payload:

Code:
{

  "uniq_id": "D0CF13020244_sensor_energy2_power_ch2",

  "~": "homeassistant/sensor/D0CF13020244energy2_power_ch2",

  "name": "energy2_ch2.power",

  "device": {

    "name": "N30-D0CF13020244",

    "identifiers": "D0CF13020244",

    "manufacturer": "KinCony",

    "model": "N30"

  },

  "config_topic": "~/config",

  "avty_t": "D0CF13020244/avail",

  "unit_of_meas": "W",

  "dev_cla": "power",

  "val_tpl": "{{ value | float | round(1) }}",

  "stat_t": "~/state"

}

In Home Assistant, the entity is therefore detected with:

Code:
device_class: power

unit_of_measurement: W

but without:

Code:
state_class: measurement

The missing field in the MQTT Discovery payload is:

Code:
"stat_cla": "measurement"

Interestingly, some other N30 power sensors are correctly detected by Home Assistant with:

Code:
state_class: measurement

unit_of_measurement: W

device_class: power

For example,

Code:
sensor.n30_bl0910_1_power_6

already has the correct

Code:
state_class

.
This suggests that the issue is specific to some of the MQTT Discovery configurations generated by the N30 firmware, particularly the

Code:
energy*_ch*_power

sensors.
Could you please check the N30 firmware and add:

Code:
"stat_cla": "measurement"

to the MQTT Discovery configuration of all instantaneous power sensors?
The expected configuration would be:

Code:
"unit_of_meas": "W",

"dev_cla": "power",

"stat_cla": "measurement"

This would allow Home Assistant to correctly identify these entities as power measurements and use them properly for statistics and energy-related features.
Thank you.

solar production and consomation

Thu, 13 Aug 2026 16:36:39 +0800

Current sensor does not detect current direction
Hello,
I have a question regarding the current/power sensor on my KinCony device.
The circuit is connected to a 1100 W pump, with approximately 1000 W peak solar PV production.
I expected the sensor to detect the direction of the current and therefore show negative power when the solar panels are producing energy and sending it back through the circuit.
In the attached screenshot:

Green area: nighttime. The pump is running and consuming approximately 1100 W. This is normal.
Red area: daytime. The solar panels are producing around 400 W, with no consumption from the pump. However, the sensor still reports the power as positive instead of negative.

So it appears that the sensor measures the current magnitude but does not detect its direction.
Is this sensor supposed to be bidirectional?
If so, is there a specific orientation for the current transformer/sensor, or does it require a particular configuration to detect the direction of the current?
Could someone explain how the current direction is detected and how I should configure or install the sensor to obtain positive values for consumption and negative values for solar production?
Thank you.

Greenshot 2026-08-13 10.31.05.png (Size: 54.95 KB / Downloads: 188)

Can't make AC868-A6 V1.4Sp work with Arduino IDE

Thu, 02 Jul 2026 03:55:31 +0800

I just acquired an AC868-A6 V1.4 board from Aliexpress.

I downloaded the lastest KCS_KC868_A6_V2.2.20.bin firmware in it

I want to give a try to Arduino IDE.
I found some ''demo programs'' on the site, such as the one below: (by the way the comment ''Blink Led on PIN0 isn't appropriate !!!)
Selected ESP32Dev Module board type
I can compile and download the program.
After downloading the program, the ESP32 will keep reseting indefintely ...
getting this message in the serial monitor:

rst:0x8 (TG1WDT_SYS_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
modeIO, clock div:1
load:0x3fff0030,len:4876
ho 0 tail 12 room 4
load:0x40078000,len:16560
load:0x40080400,len:3500
entry 0x400805b4
ets Jul 29 2019 12:21:46

Any idea about what can be wrong there ?

Thanks

JL

/*
Blink led on PIN0
by Mischianti Renzo
https://www.mischianti.org/2019/01/02/pc...asy-usage/
*/
#include "Arduino.h"
#include "PCF8574.h"
// Set i2c address
PCF8574 pcf8574(0x24);
void setup()
{
Wire.begin(12, 11); // SDA: GPIO12, SCL: GPIO11
Serial.begin(115200);
// delay(1000);
// Set pinMode to OUTPUT
pcf8574.pinMode(P0, OUTPUT);
pcf8574.pinMode(P1, OUTPUT);
pcf8574.pinMode(P2, OUTPUT);
pcf8574.pinMode(P3, OUTPUT);
pcf8574.pinMode(P4, OUTPUT);
pcf8574.pinMode(P5, OUTPUT);
pcf8574.digitalWrite(P0, HIGH);
pcf8574.digitalWrite(P1, HIGH);
pcf8574.digitalWrite(P2, HIGH);
pcf8574.digitalWrite(P3, HIGH);
pcf8574.digitalWrite(P4, HIGH);
pcf8574.digitalWrite(P5, HIGH);
Serial.print("Init pcf8574...");
if (pcf8574.begin()){
Serial.println("OK");
}else{
Serial.println("KO");
}
}
void loop()
{
delay(300);
pcf8574.digitalWrite(P0, LOW);
delay(300);
pcf8574.digitalWrite(P1, LOW);
delay(300);
pcf8574.digitalWrite(P2, LOW);
delay(300);
pcf8574.digitalWrite(P3, LOW);
delay(300);
pcf8574.digitalWrite(P4, LOW);
delay(300);
pcf8574.digitalWrite(P5, HIGH);
delay(300);
pcf8574.digitalWrite(P4, HIGH);
delay(300);
pcf8574.digitalWrite(P5, LOW)
}

N30 power supply

Sun, 28 Jun 2026 00:33:39 +0800

Hi,
I just ordered N30, which I plan to power from a DIN rail power supply.
But i cannot find how much power does the board actually need - only 12-24V.

Anyone can help?

BR,
Stan

Energy calculation for negative currents

Sun, 17 May 2026 20:22:20 +0800

The energy calculation seems to be always positive and not take into account negatieve power.

2026-05-17 111107_N30_Energy.png (Size: 28.17 KB / Downloads: 257)

Although current was negatieve and power too the energy is positive.
Also noticed that in a phase where current was pos at first and neg later the energy keeps adding which makes the energy calculation incorrect.

Energy is defined as a 32-bit float so it should be able to handle pos and negatieve loads.

Reset Total Energy only works per chip

Fri, 15 May 2026 03:00:22 +0800

Hello,

I have made some changes to my setup and one of the reasons is that the calculations were not correct.

Tried to reset the BL0910 chips but Clear all does not seem to clear the Total Energy values . Just found out that "Clear Energy 1/2/3" so per chip did actually work.

N series Energy Meter for Loxone UDP Protocol

Mon, 04 May 2026 16:19:04 +0800

Energy Loxone Protocol
=======================

Overview
--------
This document describes the Loxone string protocol for Energy module.
Default delimiter is comma (,). Chip ID: 1-6, Channel: 1-10.

Commands
--------

1. GET_ENERGY_CURRENT - Get current (A) for specific channel
Request: RELAY-GET_ENERGY_CURRENT-255,{chip},{channel}
Response: RELAY-GET_ENERGY_CURRENT-255,{chip},{channel},{value},OK
Example:
Request: RELAY-GET_ENERGY_CURRENT-255,1,1
Response: RELAY-GET_ENERGY_CURRENT-255,1,1,2.350,OK

2. GET_ENERGY_POWER - Get power (W) for specific channel
Request: RELAY-GET_ENERGY_POWER-255,{chip},{channel}
Response: RELAY-GET_ENERGY_POWER-255,{chip},{channel},{value},OK
Example:
Request: RELAY-GET_ENERGY_POWER-255,1,1
Response: RELAY-GET_ENERGY_POWER-255,1,1,512.5,OK

3. GET_ENERGY_KWH - Get energy (kWh) for specific channel
Request: RELAY-GET_ENERGY_KWH-255,{chip},{channel}
Response: RELAY-GET_ENERGY_KWH-255,{chip},{channel},{value},OK
Example:
Request: RELAY-GET_ENERGY_KWH-255,1,1
Response: RELAY-GET_ENERGY_KWH-255,1,1,1250,OK

4. GET_ENERGY_VOLT - Get voltage (V) for chip
Request: RELAY-GET_ENERGY_VOLT-255,{chip}
Response: RELAY-GET_ENERGY_VOLT-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_VOLT-255,1
Response: RELAY-GET_ENERGY_VOLT-255,1,220.50,OK

5. GET_ENERGY_FREQ - Get frequency (Hz) for chip
Request: RELAY-GET_ENERGY_FREQ-255,{chip}
Response: RELAY-GET_ENERGY_FREQ-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_FREQ-255,1
Response: RELAY-GET_ENERGY_FREQ-255,1,50.00,OK

6. GET_ENERGY_TEMP - Get temperature © for chip
Request: RELAY-GET_ENERGY_TEMP-255,{chip}
Response: RELAY-GET_ENERGY_TEMP-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_TEMP-255,1
Response: RELAY-GET_ENERGY_TEMP-255,1,35.5,OK

7. GET_ENERGY_PF - Get power factor for chip
Request: RELAY-GET_ENERGY_PF-255,{chip}
Response: RELAY-GET_ENERGY_PF-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_PF-255,1
Response: RELAY-GET_ENERGY_PF-255,1,0.95,OK

8. GET_ENERGY_SUM - Get total energy (kWh) for chip
Request: RELAY-GET_ENERGY_SUM-255,{chip}
Response: RELAY-GET_ENERGY_SUM-255,{chip},{value},OK
Example:
Request: RELAY-GET_ENERGY_SUM-255,1
Response: RELAY-GET_ENERGY_SUM-255,1,12500,OK

Nx-Energy-meter-udp-loxone.png (Size: 141.99 KB / Downloads: 269)
protocol download:

Nx-energy_loxone_protocol.txt (Size: 2.34 KB / Downloads: 158)

N30 smart energy meter ESP32 system block diagram

Sat, 02 May 2026 19:47:55 +0800

N30 smart energy meter ESP32 system block diagram

KinCony-N30-smart-energy-meter-diagram.png (Size: 1.58 MB / Downloads: 396)

KCS update and ARM CPU update

Mon, 20 Apr 2026 16:01:16 +0800

Hello.

I want to upgrade my N30 (KCS v3.15.0) with KCS v3.24.3
Do I need to make new ARM CPU update firmware (support 0.001kwh now https://www.kincony.com/forum/showthread.php?tid=9107) before or not? Or KCS update is enougth?

Best Regards.

N30 wire case diagram for 1 phase load

Tue, 31 Mar 2026 09:23:55 +0800

  N30-1-phase-1.JPG (Size: 91.61 KB / Downloads: 323)

  N30-1-phase-2.JPG (Size: 91.76 KB / Downloads: 336)

  N30-1-phase-3.JPG (Size: 92.98 KB / Downloads: 326)