Possible to obtain data like Inverter Model etc ?

[Roving-Ronin]

@wlcrs Hi Thijs,

Could you please assist, not being a programmer I can see that in the Huawei_Lib the bridge is providing the ability to 'pull' information such as:

• Inverter No. 1 its Model (i.e. SUN2000-6KTL-M1)
• Inverter No. 2 its Model (i.e. SUN2000-5KTL-L1)
• Battery, if there None/1/2 etc connected.
• Battery, what capacity they are (i.e. 15kWh)
• How many panels are attached to Inverter 1 / 2 etc.

I notice that in the WLCRS integration if you can to the 'Device Info' some of this information is populated there, such as the model_name (coming from Register 30,000). A quick look at the diagnostics shows, for example:

"slave_0": {
  "model_name": "SUN2000-5KTL-L1",
  "pv_string_count": 2,
  "has_optimizers": 0,
  "battery_type": 2,
  "battery_1_type": 2,
  "battery_2_type": 0,
  "power_meter_type": 0,
  "supports_capacity_control": true
},

"slave_2": {
  "model_name": "SUN2000-5KTL-L1",
  "pv_string_count": 2,
  "has_optimizers": 0,
  "battery_type": 0,
  "battery_1_type": 0,
  "battery_2_type": 0,
  "power_meter_type": null,
  "supports_capacity_control": false
},

So it looks like your already pulling this information via modbus, just wondering if there's somewhere your storing this that can be accessed? i.e. Buried away as an attribute, that I can use template sensor to pull the atribute out and publish a a sensor(s).

Or is this something where a new 'user-defined-custom-sensors' would be needed to created in the sensor.py file, to have this information (then somehow only triggering it upon start/reboot, so its not queried every 30sec like the normal sensors).

Many thanks for any assistance / direction you can provide.

[wlcrs]

Following the templating docs, you can do the following:

{{ device_attr("sensor.input_power", "model") }}
{{ device_attr("sensor.inverter_input_power", "serial_number") }}

I don't think that there is a way to expose extra device info, as I am limited to what HA's DeviceInfo supports. Feel free to tinker around with that and submit a PR if you found a clean way to expose that metadata in the DeviceInfo.

[Roving-Ronin]

Thanks Thijs,

MANY Thanks .. I thought they'd be hiding somewhere. Apologies to ask again, but could you point me in the direction of where to determine what other sensors contain the other info (i.e. pv strings, number of pv, batteries etc.) ?

Looking in the sensors.py I can see for instance that input_power doesn't even reference having the model attribute. Trying to filter/find them in Developer --> State shows none... not even the model and serial that are under input_power.

[wlcrs]

I don't think that this information can be accessed via HA methods. As already stated: I also don't think that HA supports that, due to the limitation of what I can put into DeviceInfo.

The diagnostics feature allows me to write whatever I want into the resulting file, as it is meant to be read by a human: HA does not understand or interpret it. So it is not particularly relevant to what you are asking, as HA must be able to understand that information and store it in a place that is accessible by the end user.

I am not aware of another channel to expose such static information. Feel free to point me in the right direction if you discover that it is possible.

[Roving-Ronin]

OK thanks. This was just trying to see if it was possible to 'pull out' things like the inverter model, for use with the Huawei PEES package. Noticed that it currently requires people to manually select they have 1 or 2 inverter and if they are 1 or 3 phase. Then based upon that then get a pull down of L1 / M1 (and trying to add MB0) inverters, thinking that if this info could be queried from HA+WLCRS it would make it possible to use some conditional logic to automate this process (and remove user errors).

[Roving-Ronin]

Hi Thijs,

I mean to ask, looking at the underlying code I notice that the Grid Codes that are listed for Australia are only the 'old' ones that Huawei had in the firmware:

AS4777
AS4777-ACT
AS4777-NSW-AG
AS4777-NSW-ESS
AS4777-QLD
AS4777-SA
AS4777-VIC
AS4777-WP

Just wondering if the Grid Code makes any difference within WLCRS, as in H2 2023 the inverter firmware from iirc around SPC155 added the following new Grid Codes for Australia:

Hope this is of assistance.

[wlcrs]

The Grid code does not influence any of the sensors exposed in HA

[Roving-Ronin]

FYI Thijs,

Looks good, managed to get this working so we can detect if there's one or two inverters and drop out the model details of:

Huawei = SUN2000-##KTL-L# | SUN2000-##KTL-M# | SUN2000-##KTL-MB# (so 1 and 3 phase)
iStore (OEM) = IS-HYB-####-1PH | IS-HYB-####-3PH (also all the 1 and 3 phase models)

template:
  - sensor:
    - name: "Inverter 1 - Model"
      unique_id: inverter_1_model
      icon: mdi:solar-power
      state: >-
        {{ device_attr("sensor.inverter_input_power", "model") | regex_findall_index('(SUN\d+-\d+KTL-[L|M|MB]\d+)|(IS-HYB-\d-\[1|3]PH)', 0) | first }}
      availability: >-
        {{  (states('sensor.inverter_input_power') not in [ 'unknown', 'unavailable', 'none' ] ) }}


  - sensor:
    - name: "Inverter 2 - Model"
      unique_id: inverter_2_model
      icon: mdi:solar-power
      state: >-
        {{ device_attr("sensor.inverter_input_power_2", "model") | regex_findall_index('(SUN\d+-\d+KTL-[L|M|MB]\d+)|(IS-HYB-\d-\[1|3]PH)', 0) | first }}
      availability: >-
        {{  (states('sensor.inverter_input_power_2') not in [ 'unknown', 'unavailable', 'none' ] ) }}

Unfortunately doesn't look like there's anywhere to pull the battery model from, with {{ device_attr("sensor.inverter_input_power", "battery_type") }} and {{ device_attr("sensor.inverter_input_power", "battery_1_type") }} responding with 'None' even though the diagnostic reports:

"slave_0": {
  "model_name": "SUN2000-5KTL-L1",
  "pv_string_count": 2,
  "has_optimizers": 0,
  "battery_type": 2,
  "battery_1_type": 2,
  "battery_2_type": 0,
  "power_meter_type": 0,
  "supports_capacity_control": true

Was hopeful it could be pulled, that would allow (iirc the values) 1 = LG battery and 2 = LUNA2000 battery. That (or/with a check of one of the standard LUNA sensors status) could then be used to determine how many batteries... then would just need to work out if its a 5/10/15 or a 7/14/21 battery.

[wlcrs]

Starting from 1.4 (now in Alpha), you can pull that info from the (sensors of the) "battery 1" device

[Roving-Ronin]

Hi Thijs,

Would you happen to know if there's any way to pull out the overall size of each attached LUNA battery (i.e. its a 10kWh or 15kWh stack or 7/14/21kWh in the new LUNA S1) ? Or alternatively, report the total 'Batteries' rated capacity (i.e. 30kWh )?

Looking at the Huawei modbus definitions documentation and in your Huawei Solar Library there is the following that, that appears to be the closest to this and that reports the Wh (not kWh). I would assume this is the overall 'Batteries' Wh and not the individual battery 1, 2 etc capacity:

Huawei Documentation:

• Register Name = [Energy storage]Ratedcapacity
  Solar Library:
• registers.py at line 1037 = rn.STORAGE_RATED_CAPACITY: U32Register("Wh", 1, 37758),
• register_names.py at line 229 = STORAGE_RATED_CAPACITY = "storage_rated_capacity"

Is this register available via attributes in v1.4.1 or some other way? I've been trying to call it, assuming its an attribute, without success.

Have managed to get the other data extracted though, for Huawei and iStore (Australia OEM) devices:

Comment:
Also, looking through for a SoH (Health) and funny to see that whilst Huawei have 'SoH Calibration Status' for the individual battery packs, and an overall 'SoH Calibration State', they have failed to provide a register that publishes the SoH of the battery, or even the packs for that matter. So there's no way to see the health as a % and/or how much kWh the battery can hold after x years in operation.