N60 Loss of kWh on reset

[chuyskywalker]

I've had the N60 up and running for about a week now and something on it went sideways (stopped reporting to home assistant; not really sure what went wrong) so I turned it off and back on again. It rebooted and came back online, but all the kWh values had been reset to zero.

I thought the system saved these values to flash and would reload them at boot so that kWh remains continuous across reboots. Is that understanding wrong?

The reason I ask is because when an ESPHome device reports values of the type "total_increasing" to home assistant, values that go backwards are handled oddly. Worse, values that go to zero are considered reseting the sensor. It's all a bit quirky, but ideally the device would retain those values and restore them. If that's not the case, I'll figure out something.

Thanks!

[admin]

do you have updated newest ARM CPU firmware?
here is ARM CPU firmware: https://www.kincony.com/forum/showthread.php?tid=9172

[chuyskywalker]

do you have updated newest ARM CPU firmware?
here is ARM CPU firmware: https://www.kincony.com/forum/showthread.php?tid=9172

Is there a way to tell what version I have installed?

The unit was purchased <1 month ago direct from y'all and I had to use the ESPHome yaml for 0.001kwh resolution, so it's pretty recent.

For clarity: if I need to update the firmware, I hook up a usb-rs485 converter to my PC and connect the A and B channel wires to the A&B on the top of the board, yes?

[admin]

suggest you overwrite the newest ARM CPU firmware.
I hook up a usb-rs485 converter to my PC and connect the A and B channel wires to the A&B on the top of the board, yes? --YES

[chuyskywalker]

Thank you; I downloaded the latest firmware and patching utility. I was able to follow the tutorial pictures and steps on the linked forum post. The steps resulted in the same output as in the post (ending on "Download finished begin running") at which point I closed the program, disconnected, and restarted the device.

Unfortunately, kWh data is still being reset on power cycle:

   

Here I let me server cabinet run for a while, accumulate some stats, and then I power cycled the device. You can see that the next reported stat is 0.01kwh. 

(The only reason it did not report "0.0kwh" is because I added a bit of YAML to prevent that.)

The YAML for the data above is reported through this YAML:

Code:

  # energy (kWh)
  - platform: modbus_controller
    id: ct_54_energy
    internal: true
    address: 646
    register_type: holding
    value_type: FP32_R
    unit_of_measurement: kWh
    state_class: total_increasing
    device_class: energy
    accuracy_decimals: 3
    # Never report a negative or zero value
    filters:
      - lambda: |-
          if (x <= 0.0) {
            return {};
          } else {
            return x;
          }

  - platform: combination
    type: sum
    name: "Data (P2B8) Energy"
    id: data_p2b8_energy
    # this specific stateclasss must be defined
    state_class: total_increasing
    sources:
      - source: ct_54_energy

(I do this because some sources combine multiple CT's, like 240 split phase loads like my EV charger and it all runs through the same "hide the ct, combine the outputs" script regardless of how many input ct's there are)

However, the CT on modbus at "address: 348" did come back with saved values. Many other's did as well; I don't have a comprehensive list, though. I could figure that out if needed.

What I suspect: Is it possible the firmware update isn't storing all the values for the expanded scope of the N60?

Thanks!

[admin]

so i suggest you download newest KCS firmware for testing. if KCS firmware work well, that means issue from ESPHome yaml.

[chuyskywalker]

so i suggest you download newest KCS firmware for testing. if KCS firmware work well, that means issue from ESPHome yaml.

That...doesn't really make sense. My understanding (based on how the esphome software is configured) is that neither ESPHome nor the KCS esp32 software would have anything to do with keeping/storing/restoring the saved kwh data. That's all done on the ARM chip side of things. All the ESPhome software does is read from a modbus address for a value. I can't see any reason why reading a modbus address using the KCS firmware would produce any different results.

Given that on the previous ARM firmware, I every kWh register was resetting, and now only some of them are, it seems more likely that the arm firmware isn't behaving correctly.

[chuyskywalker]

I'm continuing to investigate my situation. I was reading the modbus docs linked in the forum and noticed a nice feature that would be helpful while testing: the ability to reset the energy saved values.

But it doesn't seem to work.

I setup a yaml like this:


  esphome.yaml.txt (Size: 31.6 KB / Downloads: 16)

But the results I get when running are:


  log.txt (Size: 47.71 KB / Downloads: 15)

Writing to the coils doesn't seem to be clearing the kWh values as I'm expecting.

Am I doing something incorrect here to trigger a reset of the kWh values? Am I misunderstanding the purpose of the 5xx coils? Is it the correct value being written to them? Is this...not a supported feature, actually?

[chuyskywalker]

These buttons (modbus coil writes) also do not reset...anything, as far as I can tell.

Code:

- platform: template
  name: "Warm Reset"
  icon: "mdi:refresh"
  id: clear_btn_chip_500
  on_press:
    - modbus_client.write_single_coil:
        address: 0x01
        start_address: 500
        value: true
- platform: template
  name: "Factory Reset"
  icon: "mdi:refresh"
  id: clear_btn_chip_510
  on_press:
    - modbus_client.write_single_coil:
        address: 0x01
        start_address: 510
        value: true

---

Installed ARM firmware from here (https://www.kincony.com/forum/showthread.php?tid=9172)

Installed KCS from here (https://www.kincony.com/forum/showthread.php?tid=8864)

Version page:

   

Monitor page (bank 5 and 6):

   

I attempted to use the "clear" buttons from within the KCS software to reset the stored kWh values, they did not reset anything. Additionally, I attempted a "Factory Reset" button click, also did not reset any saved kWh values. (In both cases, the button press was then followed by waiting for the unit to reboot itself.)

----

I've gone down this rabbit hole because I wanted to have a fresh starting point for testing the CT's. In addition to one of the CT's not restoring previous kWh values that started this thread, I've also noticed that CT 59 and 60 (bank 6, ch 9&10) have registered kWh's...despite the fact that I don't have anything plugged into those ct pins!

[admin]

test by this newest KCS firmware v3.26.1 : https://www.kincony.com/forum/showthread.php?tid=9643
if also have issue, we will check it , then feedback to you.