Smart Home Automation Forum - N20

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: 88)
protocol download:

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

N20 smart energy meter ESP32 system block diagram

Sat, 02 May 2026 19:49:11 +0800

N20 smart energy meter ESP32 system block diagram

KinCony-N20-smart-energy-meter-diagram.png (Size: 1.55 MB / Downloads: 92)

N20 wire case diagram for 1 phase load

Fri, 03 Apr 2026 07:34:33 +0800

N20 wire case diagram for 1 phase load

N20-1-phase-1.jpg (Size: 85.54 KB / Downloads: 109)

N20-1-phase-2.jpg (Size: 86.41 KB / Downloads: 104)

N60 N30 N20 N10 ARM CPU firmware V20_260324SP

Tue, 24 Mar 2026 12:59:27 +0800

fixed bug can't remember energy data when power off.
you can download by bootloader.exe tool by RS485.
ARM BIN file download:

  N10203060_KU_V20_260324SP.zip (Size: 14.42 KB / Downloads: 105)

bootloader.exe tool:
   KC868 Controller Bootloader.zip

1. set baud rate=38400bps.
2. open com port.
3. power on Nx board, during LED fast blink when the "bootloader Detect" button right now. Then board will go to bootloader mode.
4. open BIN file
5. press "Download" button, begin download firmware, after finished, press "Run" button, ARM CPU begin work.

how to read BL0910 energy chip RAW data by modbus pull via RS485

Tue, 24 Mar 2026 10:13:44 +0800

1: open NX_chip.mbp in modbus pull software.

  modbus-open-config.png (Size: 92.01 KB / Downloads: 124)

2: set COM port. you can use USB-RS485 adapter connect to your computer:

  modbus-pull-COM-setting.png (Size: 87.06 KB / Downloads: 123)

3:
you can read BL0910-1 chip from address 100 , register count: 68
you can read BL0910-2 chip from address 200 , register count: 68
you can read BL0910-3 chip from address 300 , register count: 68
you can read BL0910-4 chip from address 400 , register count: 68
you can read BL0910-5 chip from address 500 , register count: 68
you can read BL0910-6 chip from address 600 , register count: 68

  modbus-pull-read-BL0910-1.png (Size: 96.25 KB / Downloads: 121)

  modbus-pull-read-BL0910-2.png (Size: 98.36 KB / Downloads: 129)

  modbus-pull-read-BL0910-3.png (Size: 94.91 KB / Downloads: 111)

  modbus-pull-read-BL0910-4.png (Size: 96.68 KB / Downloads: 123)

  modbus-pull-read-BL0910-5.png (Size: 95.49 KB / Downloads: 131)

  modbus-pull-read-BL0910-6.png (Size: 95.27 KB / Downloads: 113)

  NX_chip.zip (Size: 654 bytes / Downloads: 92)

N20 configure yaml for ESPhome 0.001kwh precision

Mon, 23 Mar 2026 09:56:10 +0800

note: ARM CPU firmware version should >= V20_260305SP
ARM CPU firmware download: https://www.kincony.com/forum/showthread.php?tid=9107

Code:
esphome:

  name: n20

  friendly_name: n20

esp32:

  board: esp32-s3-devkitc-1

  framework:

    type: arduino

logger:

  # baud_rate: 0

api:

ota:

  platform: esphome

ethernet:

  type: W5500

  clk_pin: GPIO42

  mosi_pin: GPIO43

  miso_pin: GPIO44

  cs_pin: GPIO41

  interrupt_pin: GPIO2

  reset_pin: GPIO1

uart:

  id: uart_modbus

  rx_pin: 9

  tx_pin: 10

  baud_rate: 115200

  stop_bits: 1

  data_bits: 8

  parity: NONE

web_server:

  port: 80

text_sensor:

  - platform: ethernet_info

    ip_address:

      name: ESP IP Address

      id: eth_ip

    dns_address:

      name: ESP DNS Address

    mac_address:

      name: ESP MAC Address

font:

  - file: "gfonts://Roboto"

    id: roboto

    size: 15

i2c:

  sda: 18

  scl: 17

display:

  - platform: ssd1306_i2c

    model: "SSD1306 128x64"

    address: 0x3C

    lambda: |-

      it.printf(0, 15, id(roboto), "IP: %s", id(eth_ip).state.c_str());

modbus:

  id: mb1

  uart_id: uart_modbus

modbus_controller:

  - id: energy_meter

    modbus_id: mb1

    address: 1

    update_interval: 5s

    command_throttle: 200ms

sensor:

  # Protocol notes for this PR:

  # - current: U_DWORD_R, scaled by 0.001 A

  # - power:   S_DWORD_R, scaled by 0.1 W

  # - energy:  FP32_R, unit kWh

  # - voltage/frequency remain U_WORD * 0.01

  # - temperature remains FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 100

    register_type: holding

    name: bl0910_1_current_1

    id: n20_1_current_1

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 102

    register_type: holding

    name: bl0910_1_current_2

    id: n20_1_current_2

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 104

    register_type: holding

    name: bl0910_1_current_3

    id: n20_1_current_3

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 106

    register_type: holding

    name: bl0910_1_current_4

    id: n20_1_current_4

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 108

    register_type: holding

    name: bl0910_1_current_5

    id: n20_1_current_5

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 110

    register_type: holding

    name: bl0910_1_current_6

    id: n20_1_current_6

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 112

    register_type: holding

    name: bl0910_1_current_7

    id: n20_1_current_7

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 114

    register_type: holding

    name: bl0910_1_current_8

    id: n20_1_current_8

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 116

    register_type: holding

    name: bl0910_1_current_9

    id: n20_1_current_9

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 118

    register_type: holding

    name: bl0910_1_current_10

    id: n20_1_current_10

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 120

    register_type: holding

    name: bl0910_1_power_1

    id: n20_1_watt_1

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 122

    register_type: holding

    name: bl0910_1_power_2

    id: n20_1_watt_2

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 124

    register_type: holding

    name: bl0910_1_power_3

    id: n20_1_watt_3

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 126

    register_type: holding

    name: bl0910_1_power_4

    id: n20_1_watt_4

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 128

    register_type: holding

    name: bl0910_1_power_5

    id: n20_1_watt_5

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 130

    register_type: holding

    name: bl0910_1_power_6

    id: n20_1_watt_6

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 132

    register_type: holding

    name: bl0910_1_power_7

    id: n20_1_watt_7

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 134

    register_type: holding

    name: bl0910_1_power_8

    id: n20_1_watt_8

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 136

    register_type: holding

    name: bl0910_1_power_9

    id: n20_1_watt_9

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 138

    register_type: holding

    name: bl0910_1_power_10

    id: n20_1_watt_10

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 140

    register_type: holding

    name: bl0910_1_energy_1

    id: n20_1_energy_1

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 142

    register_type: holding

    name: bl0910_1_energy_2

    id: n20_1_energy_2

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 144

    register_type: holding

    name: bl0910_1_energy_3

    id: n20_1_energy_3

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 146

    register_type: holding

    name: bl0910_1_energy_4

    id: n20_1_energy_4

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 148

    register_type: holding

    name: bl0910_1_energy_5

    id: n20_1_energy_5

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 150

    register_type: holding

    name: bl0910_1_energy_6

    id: n20_1_energy_6

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 152

    register_type: holding

    name: bl0910_1_energy_7

    id: n20_1_energy_7

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 154

    register_type: holding

    name: bl0910_1_energy_8

    id: n20_1_energy_8

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 156

    register_type: holding

    name: bl0910_1_energy_9

    id: n20_1_energy_9

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 158

    register_type: holding

    name: bl0910_1_energy_10

    id: n20_1_energy_10

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 160

    register_type: holding

    name: bl0910_1_energy_sum

    id: n20_1_energy_sum

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 162

    register_type: holding

    name: bl0910_1_voltage

    id: n20_1_voltage

    unit_of_measurement: V

    device_class: voltage

    state_class: measurement

    accuracy_decimals: 2

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 163

    register_type: holding

    name: bl0910_1_frequency

    id: n20_1_frequency

    unit_of_measurement: Hz

    device_class: frequency

    state_class: measurement

    accuracy_decimals: 2

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 164

    register_type: holding

    name: bl0910_1_temperature

    id: n20_1_temperature

    unit_of_measurement: °C

    device_class: temperature

    state_class: measurement

    accuracy_decimals: 1

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 166

    register_type: holding

    name: bl0910_1_power_factor

    id: n20_1_power_factor

    accuracy_decimals: 3

    state_class: measurement

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 200

    register_type: holding

    name: bl0910_2_current_1

    id: n20_2_current_1

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 202

    register_type: holding

    name: bl0910_2_current_2

    id: n20_2_current_2

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 204

    register_type: holding

    name: bl0910_2_current_3

    id: n20_2_current_3

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 206

    register_type: holding

    name: bl0910_2_current_4

    id: n20_2_current_4

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 208

    register_type: holding

    name: bl0910_2_current_5

    id: n20_2_current_5

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 210

    register_type: holding

    name: bl0910_2_current_6

    id: n20_2_current_6

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 212

    register_type: holding

    name: bl0910_2_current_7

    id: n20_2_current_7

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 214

    register_type: holding

    name: bl0910_2_current_8

    id: n20_2_current_8

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 216

    register_type: holding

    name: bl0910_2_current_9

    id: n20_2_current_9

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 218

    register_type: holding

    name: bl0910_2_current_10

    id: n20_2_current_10

    unit_of_measurement: A

    device_class: current

    state_class: measurement

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 220

    register_type: holding

    name: bl0910_2_power_1

    id: n20_2_watt_1

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 222

    register_type: holding

    name: bl0910_2_power_2

    id: n20_2_watt_2

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 224

    register_type: holding

    name: bl0910_2_power_3

    id: n20_2_watt_3

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 226

    register_type: holding

    name: bl0910_2_power_4

    id: n20_2_watt_4

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 228

    register_type: holding

    name: bl0910_2_power_5

    id: n20_2_watt_5

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 230

    register_type: holding

    name: bl0910_2_power_6

    id: n20_2_watt_6

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 232

    register_type: holding

    name: bl0910_2_power_7

    id: n20_2_watt_7

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 234

    register_type: holding

    name: bl0910_2_power_8

    id: n20_2_watt_8

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 236

    register_type: holding

    name: bl0910_2_power_9

    id: n20_2_watt_9

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 238

    register_type: holding

    name: bl0910_2_power_10

    id: n20_2_watt_10

    unit_of_measurement: W

    device_class: power

    state_class: measurement

    accuracy_decimals: 1

    value_type: S_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 240

    register_type: holding

    name: bl0910_2_energy_1

    id: n20_2_energy_1

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 242

    register_type: holding

    name: bl0910_2_energy_2

    id: n20_2_energy_2

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 244

    register_type: holding

    name: bl0910_2_energy_3

    id: n20_2_energy_3

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 246

    register_type: holding

    name: bl0910_2_energy_4

    id: n20_2_energy_4

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 248

    register_type: holding

    name: bl0910_2_energy_5

    id: n20_2_energy_5

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 250

    register_type: holding

    name: bl0910_2_energy_6

    id: n20_2_energy_6

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 252

    register_type: holding

    name: bl0910_2_energy_7

    id: n20_2_energy_7

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 254

    register_type: holding

    name: bl0910_2_energy_8

    id: n20_2_energy_8

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 256

    register_type: holding

    name: bl0910_2_energy_9

    id: n20_2_energy_9

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 258

    register_type: holding

    name: bl0910_2_energy_10

    id: n20_2_energy_10

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 260

    register_type: holding

    name: bl0910_2_energy_sum

    id: n20_2_energy_sum

    unit_of_measurement: kWh

    device_class: energy

    state_class: total_increasing

    accuracy_decimals: 3

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 262

    register_type: holding

    name: bl0910_2_voltage

    id: n20_2_voltage

    unit_of_measurement: V

    device_class: voltage

    state_class: measurement

    accuracy_decimals: 2

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 263

    register_type: holding

    name: bl0910_2_frequency

    id: n20_2_frequency

    unit_of_measurement: Hz

    device_class: frequency

    state_class: measurement

    accuracy_decimals: 2

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 264

    register_type: holding

    name: bl0910_2_temperature

    id: n20_2_temperature

    unit_of_measurement: °C

    device_class: temperature

    state_class: measurement

    accuracy_decimals: 1

    value_type: FP32_R

  - platform: modbus_controller

    modbus_controller_id: energy_meter

    address: 266

    register_type: holding

    name: bl0910_2_power_factor

    id: n20_2_power_factor

    accuracy_decimals: 3

    state_class: measurement

    value_type: FP32_R

yaml download:

n20_esphome.txt (Size: 23.27 KB / Downloads: 114)

Monitor 1 shows power=0 while Monitor 2 shows correct values

Sun, 15 Mar 2026 23:48:35 +0800

My Monitor 1 shows Power=0 for all channels even if there is current which is wrong.
Monitor 2 shows values correctly.

Voltage / Freq 226V, 50Hz is shown on both inputs (both connect to the same phase)

Protocol -> Energy has the same values for Energy 1 and 2 for all of the values of Current Factor=0.5, Power Factor=1, Energy Factor=1

Firmware v3.22.0

What might be the Problem?

Is there no OTA-Update available? Do I need to connect a via USB PC to Update the Firmware?

Multiple phase L1,L2,L3

Wed, 04 Mar 2026 22:43:37 +0800

Hi,

do the L1,L2 Input need to correlate to the current measured?

I.e., when attaching L1 to Block 1 and L2 to Block 2,
must i only measure L1 currents on CT #1-10 and L2 on CT #2-20?
Or is the L1,L2 only used for voltage measurement to be able to calculate P=U*I from that?

Or can I mix this? e.g. measaure L1,L2,L3 (e.g. for the oven) with Inputs #1,#2 and #3?

BR
Thomas

N20 CT Shorting terminal board

Mon, 05 Jan 2026 12:41:52 +0800

Generally current transformers should have the ability to be shorted in order to perform maintenance. Disconnecting a current transformer while it is installed on a current carrying conductor can result in damage, although at residential current levels this is not as likely.

Often shorting terminal strips are used but on a whim I've decided to make my own shorting terminal block tailored for my N20.
Components are almost all on hand.
Waiting for a DIN rail mounted pcb holder to arrive.
Once that shows up I'll confirm measurements and send the circuit board design for fabrication.

CT Shorting Board.jpg (Size: 103.62 KB / Downloads: 232)

N20 Problem with Home Assistant Conection

Sat, 27 Dec 2025 16:26:47 +0800

Hello, I recently received an N20. I have access to it via Ethernet, but I can't connect it to "kinconyn20.local" nor can I connect it to Home Assistant. The strange thing is that it connects via MQTT from Home Assistant.

As soon as the device arrived, I flashed it to version v3 3.18.0. Its IP address is 192.168.3.78 (within my network range, OK), and its Wi-Fi access point is 192.168.4.1.

Is the problem that it can't access "kinconyn20.local"? Why doesn't Home Assistant recognize it?

I need to check the configuration of the CT clamps, as well as the L1 and L2 power inputs, which are not appearing.

I'm Spanish, sorry for the autotranslated English.

  Resumen – Home Assistant.jpeg 1.png (Size: 410.18 KB / Downloads: 226)

  ESPHome Builder – Home Assistant.jpeg.png (Size: 449.11 KB / Downloads: 227)

  Resumen – Home Assistant.jpeg.png (Size: 240.21 KB / Downloads: 207)

N20 ESPHome YAML Updated and Tailored for 120/240V Split Phase

Wed, 17 Dec 2025 13:04:37 +0800

Hi,

I am an electrician in Canada that dabbles in smart home equipment and programming.

I wanted to get better power consumption data into my Home Assistant and eventually settled on the N20.
The N20 has two voltage inputs so should be well suited to typical residential services in North America which are usually 120/240V split phase.
That is two hot lines, each 120 volts to neutral/ground but 240V between each other.

After getting the yaml provided on this forum installed I discovered a shortcoming when used in this fashion.

The N20 uses two BL0910 chips which each have 10 current transformer inputs and 1 voltage sensing input (1 BL0910 on the N10 and 3 on the N30 which would be good for 3-phase monitoring).
Each BL0910 chip does calculations internally to provide watts and kWh but those calculations are done based on the single voltage input on each chip.

This is not a problem when one uses two current transformers, one for each hot line, but for a purely 240V load only a single current transformer is required.
Except the BL0910 chip calculates the watts based only on that single voltage input, 120V rather than 240V.

This yaml makes a few changes to tailor the firmware for typical USA/Canadian 120/240V residential services.

#1. Sensors have been renamed to aid readability.
bl0910_1_current_1 becomes CT1_1_Current
bl0910_1_power_1 becomes CT1_1_Power (or CT1_1_Power_HV when the power is based on a higher 240V circuit)
bl0910_2_power_1 becomes CT2_1_Power

The labelling on the outside of the unit lists CT1 to 11 and CT11-20 but I believe retaining the separation between BL0910 chip #1 and chip #2 is still important conceptually so went with CT1 1-10 and CT2 1-10.

#2 The renaming results in reordering of the entities in Home Assistant. Originally it would list currents 1-10, then watts 1-10, etc. Now all 3 sensors for each input is grouped and easily visible at a glance rather than scrolling 10 entries down.

#3 Reconfigured to use wifi rather than ethernet. Deleted unnecessary(?) text sensors for unused IP addresses.

#4 The OLED screen. Originally it only displayed the unit's IP address.
Now it shows the IP address, Line 1 & 2 voltages, Line-to-line voltage, L1 watts and L2 watts.
For Line 1 & 2 watts I have CTs on my main panel feeder to get the whole house consumption. If you do not have CTs this could be changed to a specific load or commented out.

#5 This is one of the important ones. A sensor has been added that adds together voltage 1 and voltage 2 to get the Line-to-Line voltage. This is trivial to do with a helper in Home Assistant but having a dedicated sensor is nice and is also vital for the next change.

#6 I've added commented-out sections for each current sensor input that multiply the current by the Line-to-Line voltage for 240V loads using single current transformers.
Simply delete or comment out the original sensor entry for 120V loads and uncomment the 240V entry.
The new entities add "HV" to their name to indicate the watts are derived from 240V rather than 120V.

#7 At this time I have not looked into a way to fix the kWh sensors to accommodate 240V loads but I suspect it should be possible.
In the meantime I've added comments indicating the kWh sensors should be commented out if a single CT is used for a 240V load.
kWh tracking is also trivial in Home Assistant so I'm not in a hurry to figure this one out.

If anyone has feedback or modifications please share here.
Please give credit if my modified yaml is shared elsewhere. Thank you

KinCony North America 120-240V split phase.txt (Size: 35.66 KB / Downloads: 167)

20251216_212002.jpg (Size: 132.3 KB / Downloads: 171)

N20 ESPHome & HA - Line to Line voltage?

Wed, 10 Dec 2025 10:52:12 +0800

Hello,

I have just received my N20.
Not very experienced with ESPHome but I did get firmware compiled and the unit is working over Wifi rather than ethernet.

I am in Canada. My electrical service is 120V/240V split phase.
Line 1 to ground is ~120V, line 2 to ground is ~120V, and L1 to L2 is ~240V.

I bought the N20 with its two voltage inputs in the hope that I could measure both 120V circuits and 240V circuits.

Is there a way to change to configuration for individual watt and kWh sensors to use the Line 1 plus Line 2 voltages?

So for example right now I have a 240V 4000W heater running.
There is no 120V load and no neutral so it only needs a single CT, but the voltage is the sum of L1 & L2.

For example my sensors currently read:
bl0910_1_current_1: 16.086A
bl0910_1_power_1: 1874.9W (incorrect)
bl0910_1_voltage: 117.3V

And also:
bl0910_2_voltage: 118.2V

The kWh would also be incorrect.

Can I adjust the yaml so that it calculates bl0910_1_power_1 based on bl0910_1_voltage PLUS bl0910_2_voltage?
But ONLY for that specific CT input?
So that other CTs on 120V circuits still calculate correctly?

It seems like it may be able to calculate this within Home Assistant.
I've already made a helper that adds the two voltage sensors together.
But they don't seem to have implemented the multiplication/product helper.

It would be immensely simpler if it could be implemented in the yaml.

Thank you

N20 configure yaml for ESPhome

Mon, 13 Oct 2025 18:23:57 +0800

Code:
esphome:

  name: n20

  friendly_name: n20

esp32:

  board: esp32-s3-devkitc-1

  framework:

    type: arduino

# Enable logging

logger:

  # baud_rate: 0

# Enable Home Assistant API

api:

ota:

  platform: esphome

ethernet:

  type: W5500

  clk_pin: GPIO42

  mosi_pin: GPIO43

  miso_pin: GPIO44

  cs_pin: GPIO41

  interrupt_pin: GPIO2

  reset_pin: GPIO1

uart:

  rx_pin: 9

  tx_pin: 10

  baud_rate: 115200

  stop_bits: 1

  data_bits: 8

  parity: NONE

web_server:

  port: 80

text_sensor:

  - platform: ethernet_info

    ip_address:

      name: ESP IP Address

      id: eth_ip

      address_0:

        name: ESP IP Address 0

      address_1:

        name: ESP IP Address 1

      address_2:

        name: ESP IP Address 2

      address_3:

        name: ESP IP Address 3

      address_4:

        name: ESP IP Address 4

    dns_address:

      name: ESP DNS Address

    mac_address:

      name: ESP MAC Address

font:

  - file: "gfonts://Roboto"

    id: roboto

    size: 15

i2c:

  sda: 18

  scl: 17

display:

  - platform: ssd1306_i2c

    model: "SSD1306 128x64"

    address: 0x3C

    lambda: |-

      it.printf(0, 15, id(roboto), "IP: %s", id(eth_ip).state.c_str());

modbus:

modbus_controller:

  - address: 1

    update_interval: 5s

sensor:

  - platform: modbus_controller

    address: 100

    register_type: holding

    name: bl0910_1_current_1

    id: n20_1_current_1

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 102

    register_type: holding

    name: bl0910_1_current_2

    id: n20_1_current_2

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 104

    register_type: holding

    name: bl0910_1_current_3

    id: n20_1_current_3

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 106

    register_type: holding

    name: bl0910_1_current_4

    id: n20_1_current_4

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 108

    register_type: holding

    name: bl0910_1_current_5

    id: n20_1_current_5

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 110

    register_type: holding

    name: bl0910_1_current_6

    id: n20_1_current_6

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 112

    register_type: holding

    name: bl0910_1_current_7

    id: n20_1_current_7

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 114

    register_type: holding

    name: bl0910_1_current_8

    id: n20_1_current_8

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 116

    register_type: holding

    name: bl0910_1_current_9

    id: n20_1_current_9

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 118

    register_type: holding

    name: bl0910_1_current_10

    id: n20_1_current_10

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

      - multiply: 0.001

  - platform: modbus_controller

    address: 120

    register_type: holding

    name: bl0910_1_power_1

    id: n20_1_watt_1

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 122

    register_type: holding

    name: bl0910_1_power_2

    id: n20_1_watt_2

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 124

    register_type: holding

    name: bl0910_1_power_3

    id: n20_1_watt_3

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 126

    register_type: holding

    name: bl0910_1_power_4

    id: n20_1_watt_4

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 128

    register_type: holding

    name: bl0910_1_power_5

    id: n20_1_watt_5

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 130

    register_type: holding

    name: bl0910_1_power_6

    id: n20_1_watt_6

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 132

    register_type: holding

    name: bl0910_1_power_7

    id: n20_1_watt_7

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 134

    register_type: holding

    name: bl0910_1_power_8

    id: n20_1_watt_8

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 136

    register_type: holding

    name: bl0910_1_power_9

    id: n20_1_watt_9

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    address: 138

    register_type: holding

    name: bl0910_1_power_10

    id: n20_1_watt_10

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

      - multiply: 0.1

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 140

    register_type: holding

    name: bl0910_1_energy_1

    id: n20_1_energy_1

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 142

    register_type: holding

    name: bl0910_1_energy_2

    id: n20_1_energy_2

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 144

    register_type: holding

    name: bl0910_1_energy_3

    id: n20_1_energy_3

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 146

    register_type: holding

    name: bl0910_1_energy_4

    id: n20_1_energy_4

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 148

    register_type: holding

    name: bl0910_1_energy_5

    id: n20_1_energy_5

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 150

    register_type: holding

    name: bl0910_1_energy_6

    id: n20_1_energy_6

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 152

    register_type: holding

    name: bl0910_1_energy_7

    id: n20_1_energy_7

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 154

    register_type: holding

    name: bl0910_1_energy_8

    id: n20_1_energy_8

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 156

    register_type: holding

    name: bl0910_1_energy_9

    id: n20_1_energy_9

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 158

    register_type: holding

    name: bl0910_1_energy_10

    id: n20_1_energy_10

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    state_class: total_increasing

    device_class: energy

    address: 160

    register_type: holding

    name: bl0910_1_energy_sum

    id: n20_1_energy_sum

    unit_of_measurement: kWh

    accuracy_decimals: 1

    value_type: U_DWORD_R

  - platform: modbus_controller

    address: 162

    register_type: holding

    name: bl0910_1_voltage

    id: n20_1_voltage

    unit_of_measurement: V

    device_class: voltage

    accuracy_decimals: 1

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    address: 163

    register_type: holding

    name: bl0910_1_frequency

    id: n20_1_period

    unit_of_measurement: Hz

    device_class: frequency

    accuracy_decimals: 1

    value_type: U_WORD

    filters:

      - multiply: 0.01

  - platform: modbus_controller

    address: 164

    register_type: holding

    name: bl0910_1_tps1

    id: n20_1_tps_1

    unit_of_measurement: °C

    device_class: temperature

    accuracy_decimals: 1

    value_type: FP32_R

  - platform: modbus_controller

    address: 200

    register_type: holding

    name: bl0910_2_current_1

    id: n20_2_current_1

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 202

    register_type: holding

    name: bl0910_2_current_2

    id: n20_2_current_2

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 204

    register_type: holding

    name: bl0910_2_current_3

    id: n20_2_current_3

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 206

    register_type: holding

    name: bl0910_2_current_4

    id: n20_2_current_4

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 208

    register_type: holding

    name: bl0910_2_current_5

    id: n20_2_current_5

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 210

    register_type: holding

    name: bl0910_2_current_6

    id: n20_2_current_6

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 212

    register_type: holding

    name: bl0910_2_current_7

    id: n20_2_current_7

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 214

    register_type: holding

    name: bl0910_2_current_8

    id: n20_2_current_8

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 216

    register_type: holding

    name: bl0910_2_current_9

    id: n20_2_current_9

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 218

    register_type: holding

    name: bl0910_2_current_10

    id: n20_2_current_10

    unit_of_measurement: A

    device_class: current

    accuracy_decimals: 3

    value_type: U_DWORD_R

    filters:

    - multiply: 0.001

  - platform: modbus_controller

    address: 220

    register_type: holding

    name: bl0910_2_power_1

    id: n20_2_watt_1

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 222

    register_type: holding

    name: bl0910_2_power_2

    id: n20_2_watt_2

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 224

    register_type: holding

    name: bl0910_2_power_3

    id: n20_2_watt_3

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 226

    register_type: holding

    name: bl0910_2_power_4

    id: n20_2_watt_4

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 228

    register_type: holding

    name: bl0910_2_power_5

    id: n20_2_watt_5

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 230

    register_type: holding

    name: bl0910_2_power_6

    id: n20_2_watt_6

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 232

    register_type: holding

    name: bl0910_2_power_7

    id: n20_2_watt_7

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 234

    register_type: holding

    name: bl0910_2_power_8

    id: n20_2_watt_8

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 236

    register_type: holding

    name: bl0910_2_power_9

    id: n20_2_watt_9

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 238

    register_type: holding

    name: bl0910_2_power_10

    id: n20_2_watt_10

    unit_of_measurement: W

    device_class: power

    accuracy_decimals: 1

    value_type: U_DWORD_R

    filters:

    - multiply: 0.1

  - platform: modbus_controller

    address: 240

    register_type: holding

    name: bl0910_2_energy_1

    id: n20_2_energy_1

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 242

    register_type: holding

    name: bl0910_2_energy_2

    id: n20_2_energy_2

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 244

    register_type: holding

    name: bl0910_2_energy_3

    id: n20_2_energy_3

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 246

    register_type: holding

    name: bl0910_2_energy_4

    id: n20_2_energy_4

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 248

    register_type: holding

    name: bl0910_2_energy_5

    id: n20_2_energy_5

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 250

    register_type: holding

    name: bl0910_2_energy_6

    id: n20_2_energy_6

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 252

    register_type: holding

    name: bl0910_2_energy_7

    id: n20_2_energy_7

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 254

    register_type: holding

    name: bl0910_2_energy_8

    id: n20_2_energy_8

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 256

    register_type: holding

    name: bl0910_2_energy_9

    id: n20_2_energy_9

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 258

    register_type: holding

    name: bl0910_2_energy_10

    id: n20_2_energy_10

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 260

    register_type: holding

    name: bl0910_2_energy_sum

    id: n20_2_energy_sum

    unit_of_measurement: kWh

    device_class: energy

    accuracy_decimals: 1

    value_type: U_DWORD_R

    state_class: total_increasing

  - platform: modbus_controller

    address: 262

    register_type: holding

    name: bl0910_2_voltage

    id: n20_2_voltage

    unit_of_measurement: V

    device_class: voltage

    accuracy_decimals: 1

    value_type: U_WORD

    filters:

    - multiply: 0.01

  - platform: modbus_controller

    address: 263

    register_type: holding

    name: bl0910_2_frequency

    id: n20_2_period

    unit_of_measurement: Hz

    device_class: frequency

    accuracy_decimals: 1

    value_type: U_WORD

    filters:

    - multiply: 0.01

  - platform: modbus_controller

    address: 264

    register_type: holding

    name: bl0910_2_tps1

    id: n20_2_tps_1

    unit_of_measurement: "°C"

    device_class: temperature

    accuracy_decimals: 1

    value_type: FP32_R

yaml download:

N20-HA.txt (Size: 18.78 KB / Downloads: 275)

N20 Energy RS485 Modbus Protocol

Mon, 13 Oct 2025 10:05:18 +0800

Code:
N20 Energy Module Modbus Protocol Specification

==============================================

1. Overview

-----------

This document specifies the Modbus communication protocol for the N20 Energy Module.

The device communicates using the Modbus RTU protocol and provides access to electrical

measurement parameters including current, power, energy consumption, voltage, frequency,

temperature, and power factor from 2 independent energy monitoring chips.

2. Module Characteristics

-------------------------

- Energy Monitoring Chips: 2

- Communication Protocol: Modbus RTU

- Wireless Technology: Not applicable (wired connection)

- Maximum Sensors Supported: 32

- Board Features: Display, Ethernet (W5500), 4G, SD Card support

- GPIO Availability: 2 free GPIOs (pins 15, 16)

3. Communication Parameters

---------------------------

- Protocol: Modbus RTU

- Baud Rate: 38400

- Function Codes:

  * 0x03: Read Holding Registers (for reading data)

  * 0x05: Write Single Coil (for control operations)

  * 0x10: Write Multiple Registers (for configuration)

4. Chip Addressing

------------------

The N20 Energy Module contains 2 measurement chips, each with a base address:

+-------------+--------------+--------------------+

| Chip Number | Base Address | Physical Location  |

+-------------+--------------+--------------------+

| Chip 1      | 100          | Main board P1      |

| Chip 2      | 200          | Main board P2      |

+-------------+--------------+--------------------+

Aggregate data from both chips is available starting at address 1000.

5. Data Structure

-----------------

Each chip provides the following data (accessible via Function Code 0x03):

5.1 Current Measurements (RMS) per Chip

---------------------------------------

+----------------+------------+-------+--------+---------------+

| Register Offset| Parameter  | Units | Format | Resolution    |

+----------------+------------+-------+--------+---------------+

| 0              | RMS_1      | A     | uint32 | 0.001A/LSB    |

| 2              | RMS_2      | A     | uint32 | 0.001A/LSB    |

| 4              | RMS_3      | A     | uint32 | 0.001A/LSB    |

| 6              | RMS_4      | A     | uint32 | 0.001A/LSB    |

| 8              | RMS_5      | A     | uint32 | 0.001A/LSB    |

| 10             | RMS_6      | A     | uint32 | 0.001A/LSB    |

| 12             | RMS_7      | A     | uint32 | 0.001A/LSB    |

| 14             | RMS_8      | A     | uint32 | 0.001A/LSB    |

| 16             | RMS_9      | A     | uint32 | 0.001A/LSB    |

| 18             | RMS_10     | A     | uint32 | 0.001A/LSB    |

+----------------+------------+-------+--------+---------------+

Example: To read RMS_1 from Chip 1, read registers 100 and 101 (2 registers for uint32).

Example: To read RMS_1 from Chip 2, read registers 200 and 201 (2 registers for uint32).

Display: Reading of 5432 represents 5.432A (5432 × 0.001A)

5.2 Power Measurements (WATT) per Chip

--------------------------------------

+----------------+------------+-------+--------+---------------+

| Register Offset| Parameter  | Units | Format | Resolution    |

+----------------+------------+-------+--------+---------------+

| 20             | WATT_1     | W     | uint32 | 0.1W/LSB      |

| 22             | WATT_2     | W     | uint32 | 0.1W/LSB      |

| 24             | WATT_3     | W     | uint32 | 0.1W/LSB      |

| 26             | WATT_4     | W     | uint32 | 0.1W/LSB      |

| 28             | WATT_5     | W     | uint32 | 0.1W/LSB      |

| 30             | WATT_6     | W     | uint32 | 0.1W/LSB      |

| 32             | WATT_7     | W     | uint32 | 0.1W/LSB      |

| 34             | WATT_8     | W     | uint32 | 0.1W/LSB      |

| 36             | WATT_9     | W     | uint32 | 0.1W/LSB      |

| 38             | WATT_10    | W     | uint32 | 0.1W/LSB      |

+----------------+------------+-------+--------+---------------+

Example: To read WATT_1 from Chip 1, read registers 120 and 121 (2 registers for uint32).

Example: To read WATT_1 from Chip 2, read registers 220 and 221 (2 registers for uint32).

Display: Reading of 12345 represents 1234.5W (12345 × 0.1W)

5.3 Energy Consumption Measurements per Chip

--------------------------------------------

+----------------+-------------+-------+--------+---------------------+

| Register Offset| Parameter   | Units | Format | Resolution          |

+----------------+-------------+-------+--------+---------------------+

| 40             | Energy_1    | kWh   | uint32 | 1kWh/LSB            |

| 42             | Energy_2    | kWh   | uint32 | 1kWh/LSB            |

| 44             | Energy_3    | kWh   | uint32 | 1kWh/LSB            |

| 46             | Energy_4    | kWh   | uint32 | 1kWh/LSB            |

| 48             | Energy_5    | kWh   | uint32 | 1kWh/LSB            |

| 50             | Energy_6    | kWh   | uint32 | 1kWh/LSB            |

| 52             | Energy_7    | kWh   | uint32 | 1kWh/LSB            |

| 54             | Energy_8    | kWh   | uint32 | 1kWh/LSB            |

| 56             | Energy_9    | kWh   | uint32 | 1kWh/LSB            |

| 58             | Energy_10   | kWh   | uint32 | 1kWh/LSB            |

| 60             | Energy_Sum  | kWh   | uint32 | 1kWh/LSB            |

+----------------+-------------+-------+--------+---------------------+

Note: The maximum measurable energy per channel is 65535 kWh.

5.4 Other Measurements per Chip

-------------------------------

+----------------+-------------+-------+--------+---------------------+

| Register Offset| Parameter   | Units | Format | Resolution          |

+----------------+-------------+-------+--------+---------------------+

| 62             | RMS_V       | V     | uint16 | 0.01V/LSB           |

| 63             | Period      | Hz    | uint16 | 0.01Hz/LSB          |

| 64             | TPS1        | °C    | float  | 0.1°C/LSB           |

| 66             | PF          | -     | float  | Power Factor (0-1)  |

+----------------+-------------+-------+--------+---------------------+

6. Channel Mapping

------------------

Total of 20 energy monitoring channels:

- Channels 1-10: Managed by Chip 1 (base address 100)

- Channels 11-20: Managed by Chip 2 (base address 200)

Each chip reports its 10 channels as local channels 1-10 in the register mapping.

7. Control Functions (Function Code 0x05)

------------------------------------------

The following control registers can be written to using the Modbus function code 0x05:

+----------+------------------------------+--------------------------------------------+

| Register | Function                     | Description                                |

+----------+------------------------------+--------------------------------------------+

| 500      | Warm Reset                   | Resets the device                          |

| 501      | Save Parameters to Flash     | Save communication parameters to flash     |

| 503      | Save Coefficients to Flash   | Save calibration coefficients to flash     |

| 504      | Clear Coefficients           | Reset all coefficients to 1.0 (use caution)|

| 510      | Restore Factory Settings     | Restore factory communication parameters   |

+----------+------------------------------+--------------------------------------------+

8. Energy Clearing Functions (Function Code 0x05)

--------------------------------------------------

The following registers clear energy consumption data when written with function code 0x05:

8.1 Clear All Channels on a Chip

---------------------------------

+----------+--------------------------------+

| Register | Function                       |

+----------+--------------------------------+

| 520      | Clear all energy on Chip 1     |

| 521      | Clear all energy on Chip 2     |

+----------+--------------------------------+

8.2 Clear Individual Channels

------------------------------

+----------------+------------------------------------------------+

| Register Range | Function                                       |

+----------------+------------------------------------------------+

| 526-535        | Clear energy on Chip 1, channels 1-10          |

| 536-545        | Clear energy on Chip 2, channels 1-10          |

| 586            | Clear sum energy on Chip 1                     |

| 587            | Clear sum energy on Chip 2                     |

+----------------+------------------------------------------------+

9. Calibration Coefficients (Function Code 0x03 to read, 0x10 to write)

------------------------------------------------------------------------

All coefficients are stored as floating-point values in CDBA format.

9.1 Current (RMS) Coefficients for Chip 1

------------------------------------------

+----------+---------------------+---------+

| Register | Parameter           | Default |

+----------+---------------------+---------+

| 3000     | FACTOR OF RMS1      | 1.0     |

| 3002     | FACTOR OF RMS2      | 1.0     |

| 3004     | FACTOR OF RMS3      | 1.0     |

| 3006     | FACTOR OF RMS4      | 1.0     |

| 3008     | FACTOR OF RMS5      | 1.0     |

| 3010     | FACTOR OF RMS6      | 1.0     |

| 3012     | FACTOR OF RMS7      | 1.0     |

| 3014     | FACTOR OF RMS8      | 1.0     |

| 3016     | FACTOR OF RMS9      | 1.0     |

| 3018     | FACTOR OF RMS10     | 1.0     |

+----------+---------------------+---------+

9.2 Power (WATT) Coefficients for Chip 1

-----------------------------------------

+----------+---------------------+---------+

| Register | Parameter           | Default |

+----------+---------------------+---------+

| 3020     | FACTOR OF WATT1     | 1.0     |

| 3022     | FACTOR OF WATT2     | 1.0     |

| 3024     | FACTOR OF WATT3     | 1.0     |

| 3026     | FACTOR OF WATT4     | 1.0     |

| 3028     | FACTOR OF WATT5     | 1.0     |

| 3030     | FACTOR OF WATT6     | 1.0     |

| 3032     | FACTOR OF WATT7     | 1.0     |

| 3034     | FACTOR OF WATT8     | 1.0     |

| 3036     | FACTOR OF WATT9     | 1.0     |

| 3038     | FACTOR OF WATT10    | 1.0     |

+----------+---------------------+---------+

9.3 Energy Coefficients for Chip 1

-----------------------------------

+----------+-----------------------+---------+

| Register | Parameter             | Default |

+----------+-----------------------+---------+

| 3040     | FACTOR OF ENERGY1     | 1.0     |

| 3042     | FACTOR OF ENERGY2     | 1.0     |

| 3044     | FACTOR OF ENERGY3     | 1.0     |

| 3046     | FACTOR OF ENERGY4     | 1.0     |

| 3048     | FACTOR OF ENERGY5     | 1.0     |

| 3050     | FACTOR OF ENERGY6     | 1.0     |

| 3052     | FACTOR OF ENERGY7     | 1.0     |

| 3054     | FACTOR OF ENERGY8     | 1.0     |

| 3056     | FACTOR OF ENERGY9     | 1.0     |

| 3058     | FACTOR OF ENERGY10    | 1.0     |

| 3060     | FACTOR OF ENERGY SUM  | 1.0     |

+----------+-----------------------+---------+

9.4 Chip 2 Calibration Coefficient Base Address

-----------------------------------------------

The calibration coefficients for Chip 2 follow the same structure but start at

base address 3064:

+-------------+---------------+

| Chip Number | Base Register |

+-------------+---------------+

| Chip 2      | 3064          |

+-------------+---------------+

10. Data Aggregation

--------------------

Gateway systems can aggregate data from both chips:

- Total System Current = Sum of all RMS values from both chips

- Total System Power = Sum of all WATT values from both chips

- Total System Energy = Sum of all Energy values from both chips

- Average System Voltage = Average of RMS_V from both chips

- Average System Frequency = Average of Period from both chips

11. Programming Notes

---------------------

1. After modifying communication parameters, write to register 501 to save them to flash.

2. After modifying calibration coefficients, write to register 503 to save them to flash.

3. Read the entire data structure for a chip by reading 68 registers starting at the

   chip's base address.

4. For 32-bit values (uint32, float), read/write two consecutive registers.

5. When writing float values, use the CDBA format.

6. All energy measurements have a maximum value of 65535 kWh per channel.

7. Monitor both chips to detect individual chip failures.

12. Comparison Table

--------------------

+------------------+------------------+------------------+------------------+

| Feature          | N10             | N20              | N30              |

+------------------+------------------+------------------+------------------+

| Communication    | Modbus RTU      | Modbus RTU       | Modbus RTU       |

| Energy Chips     | 1               | 2                | 3                |

| Channels         | 10              | 20               | 30               |

| Base Addresses   | 100             | 100, 200         | 100, 200, 300    |

| Data Structure   | Standard        | Dual-chip        | Triple-chip      |

| Installation     | Wired           | Wired            | Wired            |

+------------------+------------------+------------------+------------------+

13. Conclusion

--------------

The N20 Energy Module provides dual-chip energy monitoring with Modbus RTU

communication, offering twice the monitoring capacity of the N10 while maintaining

the same communication protocol structure. The device is ideal for medium-scale

installations requiring electrical measurement and monitoring across multiple circuits.

==============================================================================

Document generated for N20 Energy Module Modbus Protocol

For technical support, please contact Kincony support team.

protocol document download:

N20_Energy_Modbus_Protocol.txt (Size: 13.25 KB / Downloads: 219)

N60/N30/N20/N10/M30 CT selection and Load MAX current formula

Thu, 04 Sep 2025 07:47:15 +0800

CT-1.png (Size: 47.07 KB / Downloads: 380)
every CT clamp input channel will have two resistance. for example, CT2 channel are R23, R24

CT-2.png (Size: 119.56 KB / Downloads: 367)
use the formula let input voltage <700mV

if your CT clamp sensor is 2000:1
Load current=30A,
input voltage = 5.1R*2*30A/2000=153mA (VIPN)

so if input voltage <700mA , use 5.1R resistance on PCB, 2000:1 MAX can detect 137A AC220V load.

if you want support more large current, you can change the resistance or change CT 2000:1 with other models. Just use by the formula.