N30 Energy entry not working and power entry is wrong

[Vega]

Did you test this at all? Before you put this on the market?

I'm very disappointed about this system, wanted to used with ESPHome and Home Assistant but now I’m not so sure anymore, it is very unreliable, even with your own software is completly useless.

9.62A is 2.212,6W and not 1214,4W
Power factor option is useless, again a random number.
No Energy

[admin]

no other people have this issue feedback. so we will test it. the value only manager by BL0910 chip.

[admin]

we will update KCS firmware for N30.

[Vega]

In what time frame?
What about ESPHome?
I want to use ESPHome instead of KCS firmware.

[admin]

1: update ARM CPU by USB-RS485 adapter, how to download firmware , see here: https://www.kincony.com/forum/showthread.php?tid=8863
2: update KCS v3.18.2,  how to download firmware , see here: https://www.kincony.com/forum/showthread.php?tid=8864
esphome is no problem, just you need update your ARM CPU firmware.
3: if your energy data is a very large number, first time, please use the new PC software to clear to 0. here is PC monitor software: https://www.kincony.com/forum/showthread.php?tid=8406   just download newest version:  APPV1.0.25.1231  https://www.kincony.com/forum/attachment.php?aid=8886

   

[molelightn]

Hi,

@admin - thank you for the updates, unluckily i have no USB-RS485 available yet to test the latest firmwares. See below suggestion to User Vega which is working OK for two devices at the moment.

@Vega - we ran into same problem as you with N30 devices. Our solution in ESPHome now was:

-removed all Energy and Current Sensors from Modbus
-create new Energy Sensors calculated by ESPHome  Link with source data coming from N30 Power readings
-tweaked modbus interval for power Sensors down to 3s

To mention it, the energy Sensors in ESPhome reset at Midnight (daily_energy), but no problem for Homeassistant statistics.
An ESPHome Device Update may also Reset a daily Energy Sensor.
For correct energy calculation time component is important. Setup high priority during boot to avoid miscalculated energy sensors (did happen on mine previously)

Code:

esphome:
  name: kinconyn30
  friendly_name: kinconyn30
  on_boot:
    priority: -100
    then:
      - delay: 1s
      - wait_until:
          condition:
            lambda: |-
              return id(ha_time).now().is_valid();

br

[admin]

just update the ARM cpu firmware, the issue will be solved, even if use by esphome.

[molelightn]

OK, thank you. Can you explain in detail what is changed with latest Firmware for KCS and ARM?

[admin]

ARM cpu have energy data register id bug, have fixed.
new KCS have enabled mqtt auto discovery for home assistant that feedback energy data.