Hinen inverter profile

[nathan026]

Is there any documentation on getting started with creating a new inverter profile? I have a Hinen H5000 inverter and have tried all of the current profiles without any luck.

[davidrapan]

Hi @nathan026, if you don't have modbus rtu protocol from the manufacturer the simplest proly would be to create your custom profile (empty for the start) in inverter_definitions/custom/your_name.yaml (but not sure if there are proper cheks to be able to load it completely empty, though, but you will see)

And then use bult-in services trough Developer Tools > ACTIONS > Solarman Read 0x3 and 0x4 and start probing registers.

But I would try to ask your manufacturer if they are not maybe willing to provide you with documentation on the modbus protocol.

😉

[nathan026]

Thanks, I started probing the registers but wow, that would have been a nightmare! I managed to get in contact with them and have the protocol now. I'll see what I can do with it.

Hinen Inverter Modbus RTU Protocol V1.62 20240927.xlsx

[nathan026]

Is it better to clone and modify an existing profile or to create a new one from scratch?

[davidrapan]

I would say it's better to take some of the deye profiles as an example. 😉 And just replace register numbers.

[thiagofigueiro]

@nathan026, did you get anywhere with your profile? I also have a H5000 and am looking to monitor/control it locally via modbus.

[thiagofigueiro]

@davidrapan, I'm building the configuration for the Hinen H5000 based on the documentation attached to this issue.

The uint16 registers are being decoded successfully, but I am having some trouble with the uint32 registers.

For example, EChargeTotal H and EChargeTotal L are registers [278, 279] and defined as a uint32 with a scale of 0.1kWh.

Reading them, I get 0 for H and 3460 for L.

The value, according to the Solarman site is 346kWh, which matches the values above.

However, when decoding with rule 1 or 3, I get a very high number:

If I pick only the L register, I get 120kWh:

This is the configuration:

      - name: "Total Battery Charge"
        class: "energy"
        state_class: "total_increasing"
        uom: "kWh"
        scale: 0.1
        rule: 1
        registers: [278,279]
          #        registers: [279]
        icon: "mdi:battery-plus"
        validation:
          min: 0.1

Do you have any advice for me to get the same value as the actions query is reporting?

Thanks in advance!

[davidrapan]

However, when decoding with rule 1 or 3, I get a very high number:

You need to change the order in registers list. It's low then high bytes.

[thiagofigueiro]

OOOOooooh! that makes sense. Thank you so much.

Interestingly enough, it still shows the same value

      - name: "Total Battery Charge 2"
        class: "energy"
        state_class: "total_increasing"
        uom: "kWh"
        scale: 0.1
        rule: 3
        registers: [279,278]
        icon: "mdi:battery-plus"
        validation:
          min: 0.1

      - name: "Total Battery Charge"
        class: "energy"
        state_class: "total_increasing"
        uom: "kWh"
        scale: 0.1
        rule: 3
        registers: [278,279]
        icon: "mdi:battery-plus"
        validation:
          min: 0.1

Am I missing something really silly?

[thiagofigueiro]

Looks like it's working. I'll send a PR with the configuration file once I finish checking values and adding some more sensors.

[davidrapan]

It proly just needed a reload or restart. 😉

[thiagofigueiro]

Meanwhile, here's what I've got so far

parameters:
 - group: solar
   items:
    - name: "Total Production"
      class: "energy"
      state_class: "total_increasing"
      uom: "kWh"
      scale: 0.1
      rule: 1
      registers: [253,252]
      icon: 'mdi:solar-power'

    - name: "Total Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 1
      registers: [2,1]
      icon: 'mdi:home-lightning-bolt'

    - name: "Total Production PV1"
      class: "energy"
      state_class: "total_increasing"
      uom: "kWh"
      scale: 0.1
      rule: 1
      registers: [259,258]
      icon: 'mdi:solar-panel'
 - group: Battery
   items:
    - name: "Total Battery Charge"
      class: "energy"
      state_class: "total_increasing"
      uom: "kWh"
      scale: 0.1
      rule: 1
      registers: [279,278]
      icon: 'mdi:battery-plus'

    - name: "Total Battery Discharge"
      class: "energy"
      state_class: "total_increasing"
      uom: "kWh"
      scale: 0.1
      rule: 1
      registers: [283,282]
      icon: 'mdi:battery-minus'

    - name: "Battery Discharge Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [103,102]
      icon: 'mdi:battery'

    - name: "Battery Charge Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [105,104]
      icon: 'mdi:battery'

    - name: "Battery SOC"
      class: "battery"
      state_class: "measurement"
      uom: "%"
      scale: 1
      rule: 1
      registers: [128]
      icon: 'mdi:battery'

    - name: "Battery Priority"
      scale: 1
      rule: 1
      registers: [125]
      isstr: true
      icon: 'mdi:fuel-cell'
      lookup:
      -  key: 0
         value: "Load priority"
      -  key: 1
         value: "Battery priority"
      -  key: 2
         value: "Grid priority"

 - group: Inverter
   items:
    - name: "Running Status"
      class: ""
      state_class: ""
      uom: ""
      scale: 1
      rule: 1
      registers: [0]
      isstr: true
      lookup:
      -  key: 0
         value: "Stand-by"
      -  key: 1
         value: "Grid-connected"
      -  key: 2
         value: "Off-grid"
      -  key: 3
         value: "FAULT"
      -  key: 4
         value: "Update mode"
      -  key: 5
         value: "Charging"
      -  key: 6
         value: "Discharging"
      -  key: 7
         value: "Bypass"
      icon: 'mdi:home-lightning-bolt'

    - name: "Backflow power limit"
      class: "power"
      state_class: "measurement"
      uom: "%"
      rule: 1
      registers: [75]
      icon: 'mdi:home-lightning-bolt'

    - name: "Load-first charge rate"
      class: "power"
      state_class: "measurement"
      uom: "%"
      rule: 1
      registers: [136]
      icon: 'mdi:battery'

[davidrapan]

Great!

Just make sure you are using common entity naming as I can see few deviations. 😉

Examples:

• Battery instead of Battery SOC (Note: class: battery can be used only once)
• Device State instead of Running Status
• Just Power instead of Total Power (but only if it refers to the device output power, if it's for grid, load or else it has to be stated but as a rule don't use Total with context of a sum power, etc.)
• Total Production 1 instead of Total Production PV1

Edit2: You can look into deye_p3.yaml how are entity names structured.

Edit: isstr: true is not needed and do not include empty properties such as class: "" or default scale: 1 (rule: 1 is needed though). Descriptions which contains lookup should have class: "Enum" if they are not defined as platform: select.

[thiagofigueiro]

Yes, thanks for the feedback.

I'll start with deye_hybrid.yaml, find the matching registers, but keep the names and the icons.

We can work-out any kinks in the MR review.

Thanks again for your help with this. I'm quite happy using modbus instead of the cloud solarman api, which only updates every 5 minutes and depends on the Internet.