<![CDATA[Smart Home Automation Forum - N10]]> https://www.kincony.com/forum/ Sat, 26 Sep 2026 16:00:15 +0000 MyBB <![CDATA[N10 with L1 and L2 support ?]]> https://www.kincony.com/forum/showthread.php?tid=9835 Thu, 17 Sep 2026 06:12:32 +0800 aredan]]> https://www.kincony.com/forum/showthread.php?tid=9835
 Looking to monitor Grid-tied Inverter generation and grid consumption. I already have a Victron Meter VM-3P75CT and am in need of a second meter with the same capabilities (L1,L2 and L3) and cheaper. This will be integrated to Home-Assistant and Node-Red running on my CerboGX.

 Maybe you can build an N5 with L1,L2 and L3 ? Smile]]>
 Looking to monitor Grid-tied Inverter generation and grid consumption. I already have a Victron Meter VM-3P75CT and am in need of a second meter with the same capabilities (L1,L2 and L3) and cheaper. This will be integrated to Home-Assistant and Node-Red running on my CerboGX.

 Maybe you can build an N5 with L1,L2 and L3 ? Smile]]> <![CDATA[N10 - ESPHome - ARM CPU streams continuously, Modbus requests never transmitted]]> https://www.kincony.com/forum/showthread.php?tid=9811 Wed, 09 Sep 2026 16:39:27 +0800 luzozo13]]> https://www.kincony.com/forum/showthread.php?tid=9811
I am trying to integrate a new N10 board with ESPHome (v2026.8.0) and Home Assistant. After extensive testing I have isolated the problem precisely and hope someone who has successfully set up an N10 with ESPHome can help, or that KinCony staff can clarify some undocumented behaviour.

Board: KinCony N10 (ESP32-S3-WROOM-1U N16R8, 16MB flash)
ESPHome version: 2026.8.0
Chip: Freshly erased with esptool before first flash

SYMPTOM

ESPHome's modbus_controller never transmits a single request to the BL0910 ARM CPU. The UART RX line (GPIO10) is flooded with data from the moment power is applied, before ESPHome sends anything. Because ESPHome's Modbus component sees a perpetually busy bus, its frame-guard logic refuses to ever transmit. Every log shows thousands of "Clearing buffer of 2 bytes — timeout after partial response" messages and zero TX lines.

DIAGNOSTIC STEPS COMPLETED

1. Bare UART only (no modbus: component)
RX line completely silent for 60+ seconds. Confirmed the ARM CPU does NOT stream data unprovoked.

2. modbus: component, slave address 1, 115200 baud (ESPHome Devices reference config)
Continuous noise on RX, zero TX ever logged.

3. modbus: component, slave address 100, 38400 baud (per KinCony's own protocol document)
Same continuous noise, BUT real data bursts appeared embedded in the RX stream. This is the only configuration where the ARM CPU visibly responds — confirmed it is responding to address 100, not address 1.

4. All baud rates tested: 9600, 19200, 38400, 115200 with slave address 100.
Best results at 38400 (real data bursts visible). Other baud rates produce background patterns consistent with framing mismatch.

5. Boot drain lambda (on_boot reads and discards all RX bytes before modbus_controller initialises)
No effect, TX still never appears.

WHAT I BELIEVE IS HAPPENING

When ESPHome's modbus: component initialises, something causes the ARM CPU to enter a continuous streaming state. Once streaming starts, ESPHome can never transmit. Without the modbus: component, the ARM CPU stays completely quiet.

QUESTIONS

1. Does the N10 ARM CPU require the KCS factory firmware to run first and perform an initialisation before it will behave as a standard Modbus RTU slave? Has anyone successfully used ESPHome on a freshly-erased N10?

2. Can anyone confirm the correct slave address? Our testing points to 100, not 1 as shown in the ESPHome Devices reference config.

3. Can anyone confirm the correct baud rate? KinCony's protocol document says 38400; the ESPHome Devices reference says 115200. Our best results were at 38400.

4. Is there a known way to suppress the ARM CPU's startup streaming from ESPHome, so the Modbus component can get its first request out?

MINIMAL REPRODUCING CONFIG

Code:
esphome:
  name: n10-test
esp32:
  board: esp32-s3-devkitc-1
  variant: esp32s3
  framework:
    type: arduino
logger:
  hardware_uart: USB_SERIAL_JTAG
api:
ethernet:
  type: W5500
  clk_pin: GPIO42
  mosi_pin: GPIO43
  miso_pin: GPIO44
  cs_pin: GPIO41
  interrupt_pin: GPIO2
  reset_pin: GPIO1
uart:
  id: uart_bl0910
  tx_pin: GPIO9
  rx_pin: GPIO10
  baud_rate: 38400
  stop_bits: 1
  data_bits: 8
  parity: NONE
  debug:
    direction: BOTH
modbus:
  uart_id: uart_bl0910
modbus_controller:
  - id: energy_meter
    address: 100
    update_interval: 30s
sensor:
  - platform: modbus_controller
    modbus_controller_id: energy_meter
    address: 162
    register_type: holding
    name: "Line Voltage"
    unit_of_measurement: V
    value_type: U_WORD
    filters:
      - multiply: 0.01

Any help appreciated. Thank you.]]>
I am trying to integrate a new N10 board with ESPHome (v2026.8.0) and Home Assistant. After extensive testing I have isolated the problem precisely and hope someone who has successfully set up an N10 with ESPHome can help, or that KinCony staff can clarify some undocumented behaviour.

Board: KinCony N10 (ESP32-S3-WROOM-1U N16R8, 16MB flash)
ESPHome version: 2026.8.0
Chip: Freshly erased with esptool before first flash

SYMPTOM

ESPHome's modbus_controller never transmits a single request to the BL0910 ARM CPU. The UART RX line (GPIO10) is flooded with data from the moment power is applied, before ESPHome sends anything. Because ESPHome's Modbus component sees a perpetually busy bus, its frame-guard logic refuses to ever transmit. Every log shows thousands of "Clearing buffer of 2 bytes — timeout after partial response" messages and zero TX lines.

DIAGNOSTIC STEPS COMPLETED

1. Bare UART only (no modbus: component)
RX line completely silent for 60+ seconds. Confirmed the ARM CPU does NOT stream data unprovoked.

2. modbus: component, slave address 1, 115200 baud (ESPHome Devices reference config)
Continuous noise on RX, zero TX ever logged.

3. modbus: component, slave address 100, 38400 baud (per KinCony's own protocol document)
Same continuous noise, BUT real data bursts appeared embedded in the RX stream. This is the only configuration where the ARM CPU visibly responds — confirmed it is responding to address 100, not address 1.

4. All baud rates tested: 9600, 19200, 38400, 115200 with slave address 100.
Best results at 38400 (real data bursts visible). Other baud rates produce background patterns consistent with framing mismatch.

5. Boot drain lambda (on_boot reads and discards all RX bytes before modbus_controller initialises)
No effect, TX still never appears.

WHAT I BELIEVE IS HAPPENING

When ESPHome's modbus: component initialises, something causes the ARM CPU to enter a continuous streaming state. Once streaming starts, ESPHome can never transmit. Without the modbus: component, the ARM CPU stays completely quiet.

QUESTIONS

1. Does the N10 ARM CPU require the KCS factory firmware to run first and perform an initialisation before it will behave as a standard Modbus RTU slave? Has anyone successfully used ESPHome on a freshly-erased N10?

2. Can anyone confirm the correct slave address? Our testing points to 100, not 1 as shown in the ESPHome Devices reference config.

3. Can anyone confirm the correct baud rate? KinCony's protocol document says 38400; the ESPHome Devices reference says 115200. Our best results were at 38400.

4. Is there a known way to suppress the ARM CPU's startup streaming from ESPHome, so the Modbus component can get its first request out?

MINIMAL REPRODUCING CONFIG

Code:
esphome:
  name: n10-test
esp32:
  board: esp32-s3-devkitc-1
  variant: esp32s3
  framework:
    type: arduino
logger:
  hardware_uart: USB_SERIAL_JTAG
api:
ethernet:
  type: W5500
  clk_pin: GPIO42
  mosi_pin: GPIO43
  miso_pin: GPIO44
  cs_pin: GPIO41
  interrupt_pin: GPIO2
  reset_pin: GPIO1
uart:
  id: uart_bl0910
  tx_pin: GPIO9
  rx_pin: GPIO10
  baud_rate: 38400
  stop_bits: 1
  data_bits: 8
  parity: NONE
  debug:
    direction: BOTH
modbus:
  uart_id: uart_bl0910
modbus_controller:
  - id: energy_meter
    address: 100
    update_interval: 30s
sensor:
  - platform: modbus_controller
    modbus_controller_id: energy_meter
    address: 162
    register_type: holding
    name: "Line Voltage"
    unit_of_measurement: V
    value_type: U_WORD
    filters:
      - multiply: 0.01

Any help appreciated. Thank you.]]> <![CDATA[N series Energy Meter for Loxone UDP Protocol]]> https://www.kincony.com/forum/showthread.php?tid=9313 Mon, 04 May 2026 16:19:04 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9313 =======================

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


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

.txt   Nx-energy_loxone_protocol.txt (Size: 2.34 KB / Downloads: 138) ]]> =======================

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


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

.txt   Nx-energy_loxone_protocol.txt (Size: 2.34 KB / Downloads: 138) ]]> <![CDATA[N10 smart energy meter ESP32 system block diagram]]> https://www.kincony.com/forum/showthread.php?tid=9306 Sat, 02 May 2026 19:50:27 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9306
.png   KinCony-N10-smart-energy-meter-diagram.png (Size: 1.53 MB / Downloads: 307) ]]>
.png   KinCony-N10-smart-energy-meter-diagram.png (Size: 1.53 MB / Downloads: 307) ]]> <![CDATA[[SOLVED] N10 - no KWH shown]]> https://www.kincony.com/forum/showthread.php?tid=9299 Fri, 01 May 2026 08:47:28 +0800 Lattkincon]]> https://www.kincony.com/forum/showthread.php?tid=9299
I have tried the ESPhome firmware and the KC3 firmware > MQTT > Homeassistant with the same results - screenshots below for reference

When i used the ESPhome firmware i used this config file which mentions fixing the kwh  https://www.kincony.com/forum/attachment.php?aid=9373

I found this post - https://www.kincony.com/forum/showthread.php?tid=9107, and tried flashing via USBC port but it will not work - must this use the RS485? 

Thank you
 

.png   Screenshot 2026-05-01 085712.png (Size: 30.68 KB / Downloads: 331)
.png   Screenshot 2026-05-01 085842.png (Size: 10.55 KB / Downloads: 266)
.png   Screenshot 2026-05-01 090209.png (Size: 53.89 KB / Downloads: 286) ]]>
I have tried the ESPhome firmware and the KC3 firmware > MQTT > Homeassistant with the same results - screenshots below for reference

When i used the ESPhome firmware i used this config file which mentions fixing the kwh  https://www.kincony.com/forum/attachment.php?aid=9373

I found this post - https://www.kincony.com/forum/showthread.php?tid=9107, and tried flashing via USBC port but it will not work - must this use the RS485? 

Thank you
 

.png   Screenshot 2026-05-01 085712.png (Size: 30.68 KB / Downloads: 331)
.png   Screenshot 2026-05-01 085842.png (Size: 10.55 KB / Downloads: 266)
.png   Screenshot 2026-05-01 090209.png (Size: 53.89 KB / Downloads: 286) ]]> <![CDATA[N10 wire case diagram for 1 phase load]]> https://www.kincony.com/forum/showthread.php?tid=9206 Fri, 03 Apr 2026 08:22:52 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9206
.jpg   N10-1-phase.JPG (Size: 102.43 KB / Downloads: 221) ]]>
.jpg   N10-1-phase.JPG (Size: 102.43 KB / Downloads: 221) ]]> <![CDATA[N60 N30 N20 N10 ARM CPU firmware V20_260324SP]]> https://www.kincony.com/forum/showthread.php?tid=9169 Tue, 24 Mar 2026 12:59:27 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9169 you can download by bootloader.exe tool by RS485.
ARM BIN file download:

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

bootloader.exe tool: 
[Image: zip.png]   KC868 Controller Bootloader.zip 
[Image: attachment.php?aid=8891]   
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.
[Image: attachment.php?aid=8892]]]> you can download by bootloader.exe tool by RS485.
ARM BIN file download:

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

bootloader.exe tool: 
[Image: zip.png]   KC868 Controller Bootloader.zip 
[Image: attachment.php?aid=8891]   
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.
[Image: attachment.php?aid=8892]]]> <![CDATA[how to read BL0910 energy chip RAW data by modbus pull via RS485]]> https://www.kincony.com/forum/showthread.php?tid=9163 Tue, 24 Mar 2026 10:13:44 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9163
.png   modbus-open-config.png (Size: 92.01 KB / Downloads: 306)

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

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

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


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

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

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

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

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

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

[Image: attachment.php?aid=9381]
[Image: attachment.php?aid=9387]

.zip   NX_chip.zip (Size: 654 bytes / Downloads: 310) ]]>
.png   modbus-open-config.png (Size: 92.01 KB / Downloads: 306)

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

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

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


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

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

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

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

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

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

[Image: attachment.php?aid=9381]
[Image: attachment.php?aid=9387]

.zip   NX_chip.zip (Size: 654 bytes / Downloads: 310) ]]> <![CDATA[N10 configure yaml for ESPhome 0.001kwh precision]]> https://www.kincony.com/forum/showthread.php?tid=9154 Mon, 23 Mar 2026 09:54:55 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9154 ARM CPU firmware download: https://www.kincony.com/forum/showthread.php?tid=9107
Code:
esphome:
  name: n10
  friendly_name: n10

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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_1_power_factor
    accuracy_decimals: 3
    state_class: measurement
    value_type: FP32_R
yaml download: 

.txt   n10_esphome.txt (Size: 12.27 KB / Downloads: 275) ]]> ARM CPU firmware download: https://www.kincony.com/forum/showthread.php?tid=9107
Code:
esphome:
  name: n10
  friendly_name: n10

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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_1_power_factor
    accuracy_decimals: 3
    state_class: measurement
    value_type: FP32_R
yaml download: 

.txt   n10_esphome.txt (Size: 12.27 KB / Downloads: 275) ]]> <![CDATA[N10 port modbus]]> https://www.kincony.com/forum/showthread.php?tid=9085 Tue, 03 Mar 2026 18:41:09 +0800 R43]]> https://www.kincony.com/forum/showthread.php?tid=9085 <![CDATA[Problem when connecting USB-C]]> https://www.kincony.com/forum/showthread.php?tid=8673 Fri, 24 Oct 2025 02:27:46 +0800 aym55]]> https://www.kincony.com/forum/showthread.php?tid=8673 I just bought N10 module, i connected it to 24V power and it works. However when i try to put USB-C cable from computer to Kincony for download firmware it suddenly have short cut and my 24V power supply turn off , i must take off usb-c for it to work again, this situation is from early begining.I get deffective Unit ?

Thanks.]]> I just bought N10 module, i connected it to 24V power and it works. However when i try to put USB-C cable from computer to Kincony for download firmware it suddenly have short cut and my 24V power supply turn off , i must take off usb-c for it to work again, this situation is from early begining.I get deffective Unit ?

Thanks.]]> <![CDATA[N10 configure yaml for ESPhome]]> https://www.kincony.com/forum/showthread.php?tid=8645 Mon, 13 Oct 2025 18:22:57 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8645
Code:
esphome:
  name: n10
  friendly_name: n10

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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_1_tps_1
    unit_of_measurement: °C
    device_class: temperature
    accuracy_decimals: 1
    value_type: FP32_R
yaml download: 

.txt   N10-HA.txt (Size: 10.03 KB / Downloads: 458) ]]>
Code:
esphome:
  name: n10
  friendly_name: n10

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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_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: n10_1_tps_1
    unit_of_measurement: °C
    device_class: temperature
    accuracy_decimals: 1
    value_type: FP32_R
yaml download: 

.txt   N10-HA.txt (Size: 10.03 KB / Downloads: 458) ]]> <![CDATA[N10 Energy RS485 Modbus Protocol]]> https://www.kincony.com/forum/showthread.php?tid=8642 Mon, 13 Oct 2025 10:04:32 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8642
Code:
N10 Energy Module Modbus Protocol Specification
==============================================

1. Overview
-----------

This document specifies the Modbus communication protocol for the N10 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.

2. Module Characteristics
-------------------------

- Energy Monitoring Chips: 1
- 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 N10 Energy Module contains 1 measurement chip with base address:

+-------------+--------------+--------------------+
| Chip Number | Base Address | Physical Location  |
+-------------+--------------+--------------------+
| Chip 1      | 100          | Main board         |
+-------------+--------------+--------------------+

5. Data Structure
-----------------

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

5.1 Current Measurements (RMS)
------------------------------

+----------------+------------+-------+--------+---------------+
| 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).
Display: Reading of 5432 represents 5.432A (5432 × 0.001A)

5.2 Power Measurements (WATT)
-----------------------------

+----------------+------------+-------+--------+---------------+
| 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).
Display: Reading of 12345 represents 1234.5W (12345 × 0.1W)

5.3 Energy Consumption Measurements
-----------------------------------

+----------------+-------------+-------+--------+---------------------+
| 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
----------------------

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

7. Energy Clearing Functions (Function Code 0x05)
--------------------------------------------------

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

7.1 Clear All Channels on the Chip
-----------------------------------

+----------+--------------------------------+
| Register | Function                       |
+----------+--------------------------------+
| 520      | Clear all energy on Chip 1     |
+----------+--------------------------------+

7.2 Clear Individual Channels
------------------------------

+----------------+------------------------------------------------+
| Register Range | Function                                       |
+----------------+------------------------------------------------+
| 526-535        | Clear energy on Chip 1, channels 1-10          |
| 586            | Clear sum energy on Chip 1                     |
+----------------+------------------------------------------------+

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

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

8.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     |
+----------+---------------------+---------+

8.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     |
+----------+---------------------+---------+

8.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. 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 the chip by reading 68 registers starting at base
   address 100.
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.

10. Comparison with Other N-Series Modules
------------------------------------------

+------------------+------------------+------------------+------------------+
| 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            |
+------------------+------------------+------------------+------------------+

11. Conclusion
--------------

The N10 Energy Module provides single-chip energy monitoring with Modbus RTU
communication, making it ideal for small-scale installations requiring precise
electrical measurement and monitoring. The device offers 10 channels of current,
power, and energy monitoring with comprehensive calibration and control capabilities.

==============================================================================
Document generated for N10 Energy Module Modbus Protocol
For technical support, please contact Kincony support team.
protocol document download:

.txt   N10_Energy_Modbus_Protocol.txt (Size: 11.62 KB / Downloads: 375) ]]>
Code:
N10 Energy Module Modbus Protocol Specification
==============================================

1. Overview
-----------

This document specifies the Modbus communication protocol for the N10 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.

2. Module Characteristics
-------------------------

- Energy Monitoring Chips: 1
- 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 N10 Energy Module contains 1 measurement chip with base address:

+-------------+--------------+--------------------+
| Chip Number | Base Address | Physical Location  |
+-------------+--------------+--------------------+
| Chip 1      | 100          | Main board         |
+-------------+--------------+--------------------+

5. Data Structure
-----------------

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

5.1 Current Measurements (RMS)
------------------------------

+----------------+------------+-------+--------+---------------+
| 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).
Display: Reading of 5432 represents 5.432A (5432 × 0.001A)

5.2 Power Measurements (WATT)
-----------------------------

+----------------+------------+-------+--------+---------------+
| 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).
Display: Reading of 12345 represents 1234.5W (12345 × 0.1W)

5.3 Energy Consumption Measurements
-----------------------------------

+----------------+-------------+-------+--------+---------------------+
| 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
----------------------

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

7. Energy Clearing Functions (Function Code 0x05)
--------------------------------------------------

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

7.1 Clear All Channels on the Chip
-----------------------------------

+----------+--------------------------------+
| Register | Function                       |
+----------+--------------------------------+
| 520      | Clear all energy on Chip 1     |
+----------+--------------------------------+

7.2 Clear Individual Channels
------------------------------

+----------------+------------------------------------------------+
| Register Range | Function                                       |
+----------------+------------------------------------------------+
| 526-535        | Clear energy on Chip 1, channels 1-10          |
| 586            | Clear sum energy on Chip 1                     |
+----------------+------------------------------------------------+

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

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

8.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     |
+----------+---------------------+---------+

8.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     |
+----------+---------------------+---------+

8.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. 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 the chip by reading 68 registers starting at base
   address 100.
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.

10. Comparison with Other N-Series Modules
------------------------------------------

+------------------+------------------+------------------+------------------+
| 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            |
+------------------+------------------+------------------+------------------+

11. Conclusion
--------------

The N10 Energy Module provides single-chip energy monitoring with Modbus RTU
communication, making it ideal for small-scale installations requiring precise
electrical measurement and monitoring. The device offers 10 channels of current,
power, and energy monitoring with comprehensive calibration and control capabilities.

==============================================================================
Document generated for N10 Energy Module Modbus Protocol
For technical support, please contact Kincony support team.
protocol document download:

.txt   N10_Energy_Modbus_Protocol.txt (Size: 11.62 KB / Downloads: 375) ]]> <![CDATA[N60/N30/N20/N10/M30 CT selection and Load MAX current formula]]> https://www.kincony.com/forum/showthread.php?tid=8603 Thu, 04 Sep 2025 07:47:15 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8603
.png   CT-1.png (Size: 47.07 KB / Downloads: 485)
every CT clamp input channel will have two resistance. for example, CT2 channel are R23, R24

.png   CT-2.png (Size: 119.56 KB / Downloads: 511)
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.]]>
.png   CT-1.png (Size: 47.07 KB / Downloads: 485)
every CT clamp input channel will have two resistance. for example, CT2 channel are R23, R24

.png   CT-2.png (Size: 119.56 KB / Downloads: 511)
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.]]> <![CDATA[N60 N30 N20 N10 firmware BL0910 energy chip register RAW data structure]]> https://www.kincony.com/forum/showthread.php?tid=9164 Sun, 03 Aug 2025 11:31:20 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9164
.png   N60-meter-data-structure.png (Size: 31.39 KB / Downloads: 544) ]]>
.png   N60-meter-data-structure.png (Size: 31.39 KB / Downloads: 544) ]]>