Some more sensors

[vide0drome]

Thanx bugjam for very precious integration.
It would be great to have 2 more sensors:

• purchased power (W) the electricity obtained from the electrical grid. It could be useful to insert an alert in HA when the withdrawals from the grid are very high (battery flat), to avoid power cuts from the grid.
• total active power (ID 24 W ) to have the power of FV in (almost) real time also in HA.

[bugjam]

Great suggestions.
I initially chose the sensors based on the measure points which I can see for my own plant, but maybe other models give other possibilities.
I added a service in v0.7.0 which lists all the available measure points. Maybe you can use it to see if your plant supports the wanted data, and then share the code for them. (See picture below)

If the data is not available directly, you could use a Derivative sensor to estimate the current power (in W) based on the energy (Wh) sensors. (I use this to track current PV output derived from the daily yield sensor.)

[vide0drome]

thanx
from the data points i found :

• code: power
  value: 1789
  unit: W

but, how to add this code to have a new sensor?

[bugjam]

The sensors are defined here: https://github.com/bugjam/hass-isolarcloud/blob/main/custom_components/isolarcloud/sensor.py#L35

There is already a sensor for "power", it's called Power Flow in the user interface. (Translated names for the sensors are here).

[michaelrfelder]

Can you please provide some more detail on how to add the additional sensors?
I can see their availability in Developer --> Actions --> Sungrow iSolarCloud: List data points
But I am not sure what to do with them?
Just need some more details please.

[plslt]

michaelrfelder.

In File editor - /custom_components/isolarcloud/sensors.py Find the code ENERGY_SENSORS, POWER_SENSORS, BATTERY_SENSORS. Add the name of the found xtra sensors from Developer --> Actions --> Sungrow iSolarCloud: List data points.

Then File editor - /custom_components/isolarcloud/translations/en.json - find Entity/sensors and declare them there.

Reload yaml and they will show up in the intergration.

[riccidan]

michaelrfelder.

In File editor - /custom_components/isolarcloud/sensors.py Find the code ENERGY_SENSORS, POWER_SENSORS, BATTERY_SENSORS. Add the name of the found xtra sensors from Developer --> Actions --> Sungrow iSolarCloud: List data points.

Then File editor - /custom_components/isolarcloud/translations/en.json - find Entity/sensors and declare them there.

Reload yaml and they will show up in the intergration.

So I've found a stack of extra data points in my power plant.

I've attempted to add to the 2 x .py files staying within the same syntax, and then reloading the configuration.

When I do the integration fails to load.

Which results with me having to re-download the add-on.

Is there another step I am missing by chance?

(Have included the data points which I have attempted to add to the ENERGY_SENSORS section IN BOLD below)

`data_points:

• code: daily_feed_in_energy_pv
  value: 0
  unit: Wh
• code: daily_load_consumption
  value: 3100
  unit: Wh
• code: feed_in_energy_total
  value: 165900
  unit: Wh
• code: feed_in_energy_today
  value: 0
  unit: Wh
• code: power
  value: 0
  unit: W
• code: cumulative_discharge
  value: 154500
  unit: Wh
• code: energy_storage_cumulative_charge
  value: 168300
  unit: Wh
• code: ess_daily_discharge_ems
  value: 3100
  unit: Wh
• code: total_load_consumption
  value: 418800
  unit: Wh
• code: ess_daily_charge_ems
  value: 0
  unit: Wh
• code: energy_storage_soc_ems
  value: 29.5
  unit: ""
• code: daily_direct_energy_consumption
  value: 0
  unit: Wh
• code: battery_level_soc
  value: 0.295
  unit: ""
• code: total_purchased_energy
  value: 38000
  unit: Wh
• code: plant_equivalent_hours
  value: 0
  unit: h
• code: energy_purchased_today
  value: 0
  unit: Wh
• code: load_power
  value: 601
  unit: W
• code: total_yield
  value: 560500
  unit: Wh
• code: total_direct_energy_consumption
  value: 227600
  unit: Wh
• code: daily_yield
  value: 0
  unit: Wh
  `

[millesm]

fantastic work on this bugjam.

I ran the action to list all data points and found/ that there are nowhere near as many as I see in iSolar cloud for my inverter SH10RS.

Are you limiting the Measuring Point IDs that can be returned as I have tried many from the online docs and they mostly return empty arrays?

eg. 58603, Battery Temperature returns data_points: []

[bugjam]

fantastic work on this bugjam.

I ran the action to list all data points and found/ that there are nowhere near as many as I see in iSolar cloud for my inverter SH10RS.

Are you limiting the Measuring Point IDs that can be returned as I have tried many from the online docs and they mostly return empty arrays?

eg. 58603, Battery Temperature returns data_points: []

I'm not limiting the measuring points - but I have an idea about the possible cause. The integration uses the Query plant real-time measuring point data API. A plant is a logical unit which consists of multiple physical devices.
In the documentation there is also an API to Query device real-time measuring point data. I haven't tried this but it seems likely that additional measuring points will be available on the device level.

[millesm]

I'm not limiting the measuring points - but I have an idea about the possible cause. The integration uses the Query plant real-time measuring point data API. A plant is a logical unit which consists of multiple physical devices. In the documentation there is also an API to Query device real-time measuring point data. I haven't tried this but it seems likely that additional measuring points will be available on the device level.

That makes sense as it was the other devices that I was trying to query but getting no result.

My plant has 3 devices - Hybrid Inverter, Battery, Communications Module, with each associated screen in iSolar Cloud showing different data attributes.

There is an endpoint to query all devices within a plant /openapi/platform/getDeviceListByPsId

Perhaps this to create the device list and allow us to get the device metrics required from there?

[Solarbytes]

Those are the data elements I have on my SG8K-D

data_points:

• code: daily_feed_in_energy_pv
  value: 9300
  unit: Wh
• code: daily_load_consumption
  value: 21000
  unit: Wh
• code: feed_in_energy_total
  value: 47674500
  unit: Wh
• code: feed_in_energy_today
  value: 9300
  unit: Wh
• code: power
  value: 801
  unit: W
• code: inverter_total_yield
  value: 67851100
  unit: Wh
• code: total_load_consumption
  value: 75141600
  unit: Wh
• code: inverter_daily_yield
  value: 20200
  unit: Wh
• code: daily_equivalent_hours_of_inverter
  value: 2.3488
  unit: h
• code: inverter_ac_power
  value: 801
  unit: W
• code: inverter_ac_power_normalization
  value: 0.0931
  unit: W/Wp
• code: power_fraction
  value: 0.0931
  unit: ""
• code: daily_direct_energy_consumption
  value: 10900
  unit: Wh
• code: total_purchased_energy
  value: 54965000
  unit: Wh
• code: plant_equivalent_hours
  value: 2.3488
  unit: h
• code: energy_purchased_today
  value: 10100
  unit: Wh
• code: load_power
  value: 1567
  unit: W
• code: total_yield
  value: 67851100
  unit: Wh
• code: total_direct_energy_consumption
  value: 20176600
  unit: Wh
• code: daily_yield
  value: 20200
  unit: Wh

[Solarbytes]

Great work bugjam.

I'm not limiting the measuring points - but I have an idea about the possible cause. The integration uses the Query plant real-time measuring point data API. A plant is a logical unit which consists of multiple physical devices. In the documentation there is also an API to Query device real-time measuring point data. I haven't tried this but it seems likely that additional measuring points will be available on the device level.

There is another integration by the same name in HACS (it got me confused at first): https://github.com/KRoperUK/sungrow-hass. I was unable to make it work reliably (after a while the sensors become unavailable, and there is no interval configuration option.

The only thing that was better in that integration was that I got the whole set of sensors available from Sungrow. Perhaps you can look at that part of the code to get more sensors in your integration?

[Solarbytes]

@plslt many thanks for the crystal clear explananation, I was able to add the sensors I needed. Somehow, I now have entites labelled as Energy that are neither in sensor.py nor in en.json. Not a problem, I just disable the ones I don't need.

e.g. home_energy, home_energy_2/4

I do wonder how they can land in the display of an integration where they are not defined - not that I can see anyway...

[Solarbytes]

oh my, my panels stopped producing nearly 45 mins ago and iSolarcloud (the Sungrow app) still shows a production of 55W), there is clearly no need for a shorter interval than 5 mins to refresh data, I would say that 15mins is probably more adequate.

This integration cannot be used for any live management of loads under those circumstances. This is not because of the integration itself, but because of the huge lag on the Sungrow side.

[saschpe]

Unfortunately, there is also no suitable way to interact with iHomeManager via ModBus. I have a plant with SH15T inverter, SBH20 battery, AC22E-01 callbox and iHomeManager. Only the inverter can be queried to a certain degree but none of the others. The available registers also seem to work better or worse depending on the inverter model and if connected via LAN or Wifi. In essence, the cloud API integration is the most stable and only supported way to grab any data. I'll try to provide the list of data elements I have on my plant later...