kWh resolution

[admin]

please download newest PC software v1.0.26.0306. this version support show with 0.001kwh.

[Vega]

Data was cleared, but I did it again with this version.


But still this, this is with a 100W bulb



This is part of the yaml code.

Code:

uart:
# id: modbus_uart
  rx_pin: 9
  tx_pin: 10
  baud_rate: 115200
  stop_bits: 1
  data_bits: 8
  parity: none
 
modbus:

modbus_controller:
  - address: 1
    update_interval: 5s

sensor:
  - platform: modbus_controller
    address: 100
    register_type: holding
    name: current_1
    id: n30_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: 118
    register_type: holding
    name: current_10
    id: n30_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: power_1
    id: n30_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: 138
    register_type: holding
    name: power_10
    id: n30_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: energy_01
    id: n30_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: 158
    register_type: holding
    name: energy_10
    id: n30_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: energy_sum
    id: n30_1_energy_sum
    unit_of_measurement: kWh
    accuracy_decimals: 1
    value_type: U_DWORD_R

  - platform: modbus_controller
    address: 162
    register_type: holding
    name: voltage
    id: n30_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: frequency
    id: n30_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: tps1
    id: n30_1_tps_1
    unit_of_measurement: °C
    device_class: temperature
    accuracy_decimals: 1
    value_type: FP32_R

[admin]

we will update esphome yaml later, will post at here.

[Vega]

Any ETA on the corrected YAML file?

[spacerunner]

Same here, please post the updated YAML file. Just ordered 4 (!) units of N30, N20 and N10 and need the correct ESPHOME definitions for precise measurements.

thank you

[admin]

under developing, when finish, will make video tour upload to our YouTube channel to explain.

[Painy]

When you make the video, could you make it into a real life scenario tutorial?
I've made two mistakes when installing the n30 that could have been avoided with better instructions.

1. How to measure voltage. I used a CT clamp first, which does not work of course. You suggested using the two terminals of a power plug cable in an outlet and hook that up to the n30. That was not possible for me because the N30 is in my distribution box. Instead, I put two extra wires (neutral and live) behind three of the fuses in the distribution box and connected them to V1-V3. That also worked.
   
   
2. I have a 3x230V system without a neutral. The three voltages are split over all my two fase fuses. So 1/3 of my fuses use the first voltage (V1), 1/3 uses V2 and 1/3 uses V3. At first i had just randomly connected the CT clamps to the 1-30 terminals. After seeing that some power readings were al wrong, I concluded that I had to connect all fuses connected to the first voltage of my distribution box to N30 V1: 1-10 connections. Same with V2 and V3. Like I said, lost a lot of time with that
   

Maybe write down how different distribution box types can be used? Like a one phase system is easy, but can you wire a 3x230V + 1N to the N30?
The documentation on the website is lacking about hardware configuration. It's mainly about software.

Thank you
 [/list]

[admin]

ok, thanks for suggestion.

[spacerunner]

We are currently in the process of implementing several Nxx units into a larger building project. Unfortunately, as Painy has stated before, there are some important informations missing in the documentation. I would greatly appreciate if the missing information would be Mae available here in the forum or on the documentation first. Videos can be helpful, but more detailed written information is even more valuable.

Therefor, I want to ask for:

1. ARM source code

Would you be willing to always share the current ARM source code (corresponding for example to -> N102030_KU_V20_260305SP.zip binary) here in the forum? BL0910 documentation is widely available in detail, but the Arm chip sitting between the ESP32 and the BL0910 is the blind spot. Understanding / being able to debug / customize the current ARM firmware would greatly help to improve the unit.

2. CT ratios

Please document on how to adjust the CT ratios per channel, also via ESPHome. 2000:1 is by far not suitable for all needs. Especially for lower current / low power measurements.

3. CT input limits documentation

Please document the maximum input limit (mA) of the Nxx units. In combination with setting / adjusting the CT ratios per channel, this will enable to pick the right CTs for the individual use case.

4. BL0910 Active Power registers

Like Painys problem before, maybe there is a way to manually register the active power for a channel in the BL0910 internal registers? This would allow to, for example, connect CT channel 17 to the voltage input of voltage channel 1 (phase 1). The reason is simple, and directly connected to Painys issue. Real world scenario here: We have a N30 interface but need to measure

  - 15 datapoints on Phase 1
  - 7 datapoints on Phase 2
  - 6 datapoints on phase 4

Not possible at the moment.

Thank four for helping !

[admin]

here is new KCS v3 firmware for N10,N20,N30,N60 support 0.001kwh precision.

  KCS_N60_V3.24.2_beta_20260322-122241.zip (Size: 1.02 MB / Downloads: 14)

  KCS_N30_V3.24.2_beta_20260322-122240.zip (Size: 1.01 MB / Downloads: 15)

  KCS_N20_V3.24.2_beta_20260322-122349.zip (Size: 1.01 MB / Downloads: 16)

  KCS_N10_V3.24.2_beta_20260322-122243.zip (Size: 1.01 MB / Downloads: 16)

new ESPHome yaml download for  N10,N20,N30,N60 support 0.001kwh precision.
N60: https://www.kincony.com/forum/showthread.php?tid=9157
N30: https://www.kincony.com/forum/showthread.php?tid=9156
N20: https://www.kincony.com/forum/showthread.php?tid=9155
N10: https://www.kincony.com/forum/showthread.php?tid=9154