Version of the custom_component

0.0.13

Configuration

Describe the bug

Most of the days I got one exception for the Sunspec integration.
I have installed the SunSpec integrartion two times, one for the Fronius inverter and one for the solarEdge inverter.
I can't see in the logfile which one is producing this error.

Debug log

2021-09-25 21:20:25 WARNING (MainThread) [custom_components.sunspec] Response timeout 2021-09-25 21:20:25 ERROR (MainThread) [custom_components.sunspec] Unexpected error fetching sunspec data: Connection error: [Errno 111] Connection refused Traceback (most recent call last): File "/config/custom_components/sunspec/__init__.py", line 128, in _async_update_data data[model_id] = await self.api.async_get_data(model_id) File "/config/custom_components/sunspec/api.py", line 86, in async_get_data return await self.read(model_id) File "/config/custom_components/sunspec/api.py", line 89, in read return await self._hass.async_add_executor_job(self.read_model, model_id) File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/config/custom_components/sunspec/api.py", line 132, in read_model model.read() File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 85, in read data = self.model.device.read(self.model.model_addr + self.offset, self.len) File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 317, in read return self.client.read(addr, count, op) File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 584, in read data = self._read(addr + read_offset, read_count, op=op) File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 529, in _read raise ModbusClientError('Response timeout') sunspec2.modbus.modbus.ModbusClientError: Response timeout During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 481, in connect self.socket.connect((self.ipaddr, self.ipport)) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh self.data = await self._async_update_data() File "/config/custom_components/sunspec/__init__.py", line 133, in _async_update_data self.api.reconnect() File "/config/custom_components/sunspec/api.py", line 106, in reconnect client.connect() File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 308, in connect self.client.connect() File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 483, in connect raise ModbusClientError('Connection error: %s' % str(e)) sunspec2.modbus.modbus.ModbusClientError: Connection error: [Errno 111] Connection refused

Labels in config flow

Originally posted by @CJNE in CJNE/pythermiagenesis#1 (comment)

I only could use a few of the Sensors for the Energy Tab.
Non from my Inverter only from the AC meter.

this is the Issue HA pointed me to https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics

Next week I should have some time to look into this issue.

Great work on the SunSpec Home Assistant component! I'd like to suggest a feature for controlling inverter output (both real and reactive power). I'm under a dynamic contract where sometimes the energy price goes negative, so I'd like a way to throttle or completely disable my solar production when necessary.

I'd appreciate something similar to the Power Control Options in this component, where I can adjust the inverter output in percentages.

I've considered installing the above-mentioned component, but my inverter (SolarEdge) only supports a single connection. So, I'd have to choose between the two or install a proxy. I believe adding this feature to the SunSpec component could simplify this process significantly.

Version of the custom_component

0.0.7

Describe the bug

Small issue, do not think it really has any impact except for a warning. Seems like voltampere isn't really supported, maybe this is a HA issue not Sunspec.

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:196
Integration: Sensor (documentation, issues)
First occurred: 15:12:00 (1 occurrences)
Last logged: 15:12:00

sensor.inverter_ac_apparent_power has unknown unit VA

This issue is regarded directly to Issue #66 which I was unable to reopen.

Is your feature request related to a problem? Please describe.
Recently I attempted to change the IP of my inverter, i was migrating the device off a vlan that had external connectivity to one that didnt. After the address changed, i had to re-establish the integration, set the name and enter all the details. This resulted in me having to reconfigure the energy dashboard, various other automation and displays, as well as losing the historical data.

Describe the solution you'd like
When you click configure on a known integration, it gives you the ability to set the IP address as well as the other current variables.
Describe alternatives you've considered
Updating all the places that the data is used; but nothing can replace the lost data :(

Version of the custom_component

0.0.8

Configuration

Reading pages 103, 122

Describe the bug

Looks like a R/W error, possibly timeout from inverter or unavailable network and since this is a quite common situation maybe a warning should do?

EDIT: It seems like the sensors is set to 0 when this happens and this really breaks history and all calculations using the sensor. I do not think the sensor should be updated at all in this case.

These errors seems to appear now and then during nighttime so I have a feeling that maybe the inverter is in some sleeping/start up mode that makes it slower to respond. I have also seen that the error occurs just before midnight every day.

Debug log

2021-08-23 03:02:06 ERROR (MainThread) [custom_components.sunspec] timed out
2021-08-23 03:02:09 ERROR (MainThread) [custom_components.sunspec] Unexpected error fetching sunspec data: Connection error: [Errno 113] Host is unreachable
Traceback (most recent call last):
File "/config/custom_components/sunspec/init.py", line 128, in _async_update_data
data[model_id] = await self.api.async_get_data(model_id)
File "/config/custom_components/sunspec/api.py", line 86, in async_get_data
return await self.read(model_id)
File "/config/custom_components/sunspec/api.py", line 89, in read
return await self._hass.async_add_executor_job(self.read_model, model_id)
File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/sunspec/api.py", line 124, in read_model
model.read()
File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 85, in read
data = self.model.device.read(self.model.model_addr + self.offset, self.len)
File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 317, in read
return self.client.read(addr, count, op)
File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 584, in read
data = self._read(addr + read_offset, read_count, op=op)
File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 520, in _read
c = self.socket.recv(len_remaining)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 481, in connect
self.socket.connect((self.ipaddr, self.ipport))
OSError: [Errno 113] Host is unreachable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/sunspec/init.py", line 133, in _async_update_data
self.api.reconnect()
File "/config/custom_components/sunspec/api.py", line 106, in reconnect
client.connect()
File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 308, in connect
self.client.connect()
File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 483, in connect
raise ModbusClientError('Connection error: %s' % str(e))
sunspec2.modbus.modbus.ModbusClientError: Connection error: [Errno 113] Host is unreachable
2021-08-23 03:02:39 ERROR (MainThread) [custom_components.sunspec] Socket write error: [Errno 32] Broken pipe

I have a Fronius Gen 24 inverter (10 kW) with 2 MPPTs (strings). The scaling factor of the DC power of these strings seems not to be correct:


above 600 W it's hopping to 60-100 W

Thank you for the great work and this component!

Version of the custom_component:

0.0.7

Describe the bug

After upgrading from 0.0.5 to 0.0.7 an error is thrown.

Config

HA core-2021.7.4
HA OS 6.1
Fronius Galvo 1.5-1 inverter

Debug log

Logger: homeassistant.setup
Source: setup.py:311
First occurred: 4:46:09 PM (1 occurrences)
Last logged: 4:46:09 PM

Unable to prepare setup for platform sunspec.sensor: Platform not found (cannot import name 'ELECTRIC_CURRENT_AMPERE' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)).

Version of the custom_component

0.0.18

Configuration

Not available since installation of intregration does not work.

Describe the bug

System:

• E3DC S10 ( https://www.e3dc.com )
• Modbus Mode: Sunspec ( http://sunspec.org/wp-content/uploads/2016/02/SunSpec-Information-Model-Reference.xlsx )
• Configuration: https://www.loxwiki.eu/download/attachments/9339566/ModuBus-Dokumentation_2016-08-05.pdf?version=1&modificationDate=1471507657000&api=v2 -> see chapter 3.2 for sunspec config

Error occurs when trying to add the integration on "/config/integrations". It cannot install due to Failed to connect to host 192.168.0.245:502 slave 1 - Repeating group count not consistent with model length for model 803,model repeating len = 6, model repeating group len = 32(see logs below)

Did anyone successfully use this integration for an E3DC device?

It works fine when I use the modbus integration for direct register access. Here a part of my configuration (for details compare with excel above):

modbus:
  - name: E3DC
    type: tcp
    host: 192.168.0.245
    port: 502
    sensors:
      - name: e3dc_meter_home_incoming
        unit_of_measurement: kWh
        address: 40248 #40203+46-1
        slave: 1
        device_class: energy
        count: 2
        scan_interval: 15
        data_type: uint32
        scale: 0.001
        precision: 2
      - name: e3dc_meter_home_exporting
        unit_of_measurement: kWh
        address: 40240 #40203+38-1
        slave: 1
        device_class: energy
        count: 2
        scan_interval: 15
        data_type: uint32
        scale: 0.001
        precision: 2
...

Debug log

2021-11-13 21:03:09 DEBUG (MainThread) [custom_components.sunspec] New SunspecApi Client
2021-11-13 21:03:09 DEBUG (SyncWorker_1) [custom_components.sunspec] Client connect to IP 192.168.0.245 port 502 slave id 0 using timeout 60
2021-11-13 21:03:09 DEBUG (SyncWorker_1) [custom_components.sunspec] Client connected, perform initial scan
2021-11-13 21:03:09 ERROR (MainThread) [custom_components.sunspec] Failed to connect to host 192.168.0.245:502 slave 1 - Repeating group count not consistent with model length for model 803,model repeating len = 6, model repeating group len = 32

The number of decimals should be identical (and never higher than 3) for both measurements of the same kind.

Version of the custom_component

0.0.7

Describe the bug

If "last_reset" is set to an int, the event processing for the StatisticsTasks throws an error.

Debug log

2021-08-11 18:17:36 ERROR (Recorder) [homeassistant.components.recorder] Error while processing event StatisticsTask(start=datetime.datetime(2021, 8, 11, 15, 0, tzinfo=datetime.timezone.ut\
c)): argument 1 must be str, not int
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/recorder/__init__.py", line 623, in _run_event_loop
    self._process_one_event_or_recover(event)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/recorder/__init__.py", line 632, in _process_one_event_or_recover
    self._process_one_event(event)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/recorder/__init__.py", line 738, in _process_one_event
    self._run_statistics(event.start)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/recorder/__init__.py", line 721, in _run_statistics
    if statistics.compile_statistics(self, start):
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/recorder/util.py", line 303, in wrapper
    return job(instance, *args, **kwargs)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/recorder/statistics.py", line 154, in compile_statistics
    platform_stats.append(platform.compile_statistics(instance.hass, start, end))
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/sensor/recorder.py", line 284, in compile_statistics
    stat["last_reset"] = dt_util.parse_datetime(last_reset)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/util/dt.py", line 133, in parse_datetime
    return ciso8601.parse_datetime(dt_str)
TypeError: argument 1 must be str, not int

The problem seems to be here:

this should be changed to

dt.utc_from_timestamp(0)

where dt is

from homeassistant.util import dt

When trying to add the SunSpec integration I can't select the 801 specification for batteries. I can see that it exists in the python file but it's not shown in the dropdown list.

Version of the custom_component

Home Assistant 2021.8.0b7

Configuration

Using pages (models) 103, 122

Describe the bug

The integration does not start. It used to work but at some time quite resently it stopped unfortunately I do not now exactly when and what has changed. New Energy tab and handling in beta, could that be the issue?

Logger: homeassistant.setup
Source: setup.py:311
First occurred: 11:50:14 (4 occurrences)
Last logged: 11:56:45

Unable to prepare setup for platform sunspec.sensor: Platform not found (cannot import name 'ELECTRICAL_CURRENT_AMPERE' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)).

Version 0.20

How can I change the IP address?

After Updating the entity "Solaredge inverter Watts" does not refresh properly. After reloading the integration it works for some minutes.

The values reported

1. don't match the values from the native web interface
2. the values for both solar panels of each inverter are always the same, even if the native interface offers independent readings.

See screenshots

(the ones from 3 to 6 are not posted for conciseness)

Original interface

Hi,

I use this ha integration ver. 0.20 with my Fronius Symo Gen24 plus.
All (but changing configuration, already an open issue) works fine.
But, due to the behaviour of the battery handling in register map160 by fronius, I get intermittent "unavailable" as state of battery "mppt module 2 Lifetime Energy" and "mppt module 3 Lifetime Energy". (MPPT 2 and 3 are being used for the battery charge and discharge)
This seems to be due to the fact, that fronius sets these (as well as the power for the MPPTs) to 0. Fronius hotline claims that this behaviour would be correct, according sunspec definitions...
The ha-sunspec integration seems to handle that case not properly. In my opinion that needs to be changed, so that the data does not get "unavailable". Maybe the last correct value (non 0) could be given to the entity, whenever fronius sends "0" to indicate that the battery is being either "being charged" or "being discharged" or "idle".
Maybe the "input ID string" could be used to identify that a battery is connected, to adapt the output for MPPT 2 and 3 values in case of reading 0's?

Thank you all for your great work with this integration!!!

teamvc

Version of the custom_component

0.0.9

Configuration

Describe the bug

The value for AC power for the Fronius inverter are sometimes too high. More than the capacity of the unit.
My panels have a capacity of 1530 Wp. The values goes as high as 3000 Watt!
It looks the values looks 10 times too high. Also the DC Power values have those spikes.
The DC Voltage and DC Current values seems ok.
What can be wrong?

AC Power

AC Current

DC Power

DC Voltage

DC Current

Debug log

Hi, i try to connect Sunspec for Schneider Conext Combox.
The slave id same on Combox, but always error. Can u help me ?

Thanks.

Version: 0.0.8
I installed this integration with Homeassistant HACS.

But when i try to search for it in the integrations tab i dont find anything.

Output of log:
2021-08-16 09:20:06 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration sunspec which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

HA 2021.10 now does some quality checks for long term statistics, available via developer tools:
https://www.home-assistant.io/blog/2021/10/06/release-202110/#other-noteworthy-changes

The apparent power entities of ha-sunspec fail this check, as can be seen in the attached screenshot.

Resolution, either

1. remove device class 'power' from these entities for ha-sunspec, or
2. confirm with HA upstream that VA should be included as a valid device class 'power'

I run HA on Docker on Synology. I manually added the custom component using the instructions but SunSpec can not be found in the Integrations after restart. I see that with other manually added custom components you need to add it to the configuration.yaml file.

Does this need to be done here too? If so how?

HA - SunSpec integration with APsystem ECU_R_PRO (TCP/IP) is not working well. When you start the integration, the ECU_R_PRO is discover (host-ip) and also the read-modules (1, 101, 111,123). After the inverter is imported and device overview will show the (value) details. But after several seconds the device and entities becomes unavailable.
The ECU_R_PRO is configured with multiple inverters which assigned an unique address in the modbus configuration.
When additional inverters are added the same behavior takes places (see the values ones).
Deletion of the inverter, will block reactivation again for the same address until HA is restarted.

Please advise me how to generate the (debug) logs to investigate the problem and to help to develop the SunSpec integration for APsystems.

Hi,

Very nice integration!

But I receive the following log message:
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: custom_components.sunspec
Source: custom_components/sunspec/config_flow.py:40
Integration: sunspec (documentation, issues)
First occurred: 21. August 2022 um 12:40:34 (34 occurrences)
Last logged: 18:10:23

Failed to connect to host 192.168.40.3:502 slave 3 - Device responded - not SunSpec register map
Failed to connect to host 192.168.040.003:502 slave 3 - Connection error: timed out

Any suggestions? I have a SMA TriPower inverter running.

Hello, could you force the energy in watts per hour to be forced to display in kilowatts per hour?
Only kWh is correctly calculated by the energy module in the Home Assistant

I have a Fronius inverter & meter installed.
I can manually query both model 1 (Inverter) and 240 (meter) without issue.

The Integration is working well for the Inverter, but model 240 (meter) does not show up in the selection.

I'm not proficient at coding so I haven't figured out how to trace what may be missing.

Version of the custom_component

0.0.14

Configuration

Describe the bug

An exception error "Connection refused" shows up. I think it is triggered as soon as the inverter starts in the morning.
I've also seen those errors on the end of the day when the inverters stops.

Debug log

2021-09-28 07:25:36 WARNING (MainThread) [custom_components.sunspec] Response timeout 2021-09-28 07:25:36 ERROR (MainThread) [custom_components.sunspec] Unexpected error fetching sunspec data: Connection error: [Errno 111] Connection refused Traceback (most recent call last): File "/config/custom_components/sunspec/__init__.py", line 129, in _async_update_data data[model_id] = await self.api.async_get_data(model_id) File "/config/custom_components/sunspec/api.py", line 97, in async_get_data return await self.read(model_id) File "/config/custom_components/sunspec/api.py", line 104, in read return await self._hass.async_add_executor_job(self.read_model, model_id) File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/config/custom_components/sunspec/api.py", line 147, in read_model model.read() File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 85, in read data = self.model.device.read(self.model.model_addr + self.offset, self.len) File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 317, in read return self.client.read(addr, count, op) File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 584, in read data = self._read(addr + read_offset, read_count, op=op) File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 529, in _read raise ModbusClientError('Response timeout') sunspec2.modbus.modbus.ModbusClientError: Response timeout During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 481, in connect self.socket.connect((self.ipaddr, self.ipport)) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh self.data = await self._async_update_data() File "/config/custom_components/sunspec/__init__.py", line 138, in _async_update_data self.api.reconnect() File "/config/custom_components/sunspec/api.py", line 121, in reconnect client.connect() File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/client.py", line 308, in connect self.client.connect() File "/usr/local/lib/python3.9/site-packages/sunspec2/modbus/modbus.py", line 483, in connect raise ModbusClientError('Connection error: %s' % str(e)) sunspec2.modbus.modbus.ModbusClientError: Connection error: [Errno 111] Connection refused 2021-09-28 07:26:06 WARNING (MainThread) [custom_components.sunspec] Socket write error: [Errno 32] Broken pipe

As described in conersation on community forum.
(Issue to increase the repair chance as author correctly noticed.)

Version of the custom_component

0.0.5

Configuration

SMA inverter Tripower 8.0
ip 192.168.178.85
port 502
Sunspec ID 126 (from manual)

Describe the bug

ha-sunspec cannot connect to my SMA inverter. The sunspec support starts with registers above 40001, so the ID address is 40086, no 40085 exists. I think this is the main cause.

On the manual they said:

Das SunSpec Modbus-Profil für SMA
Produkte beginnt ab der Registernummer 40001.

Debug log

Logger: custom_components.sunspec
Source: custom_components/sunspec/config_flow.py:121
Integration: SunSpec (documentation, issues)
First occurred: 15:47:57 (3 occurrences)
Last logged: 15:52:35

Failed to connect to host 192.168.178.85:502 - Modbus exception 2: addr: 40085 count: 98

Version of the custom_component

v0.0.20

Configuration

Add your logs here.

state_class: total_increasing
integration: sunspec
sunspec_key: TotWhExp
label: Total Watt-hours Exported
unit_of_measurement: Wh
device_class: energy
icon: mdi:solar-panel
friendly_name: Ac_meter Total Watt-hours Exported

## Describe the bug

A clear and concise description of what the bug is.

Hi i use this sunspec intregration, i have problem with one sensor total watt hours exported, the value in HA is count down, In my kostal smart meter the value is count up.
When i add the sensor to energy dashboard in HA it can't rister the feed in power correct because the sensor is count down the value. 
Is it possible to chenge so the value is count UP.



Add your logs here.

Hello and thank you for this integration !!!

I have 2 Fronius Symo connected in daisy chain and a Fronius smartmeter. I set up this integration 3 times, for slave 1 and 2 as the inverters and 240 for the meter.
Data is coming through and all seems good.

However i am struggling to find out how to get the Site data. Fronius modbus docs specify that
"The following registers can be used to query power and energy data from all inverters
connected to this Fronius Datamanager via Fronius Solar Net.
These values are displayed in Watt (W) or Watt hours (Wh) and do not require scale factors.

• F_Site_Power(500–501): Power
• F_Site_Energy_Day(502–505): Daily Energy
• F_Site_Energy_Year(506–509): Yearly Energy
• F_Site_Energy_Total(510–513): Total energy of the entire system."

This data is available when doing a http call to the meter: "http://ipaddress/solar_api/v1/GetPowerFlowRealtimeData.fcgi". The response contains:

Basically what i am trying to get is the Site Power (P_Load) - aka the total power in Watts for the house and the P_Grid - power from Grid

Is this possible please ?

Thank you

On version 0.20 a change of a modbus value from 0 to a different value was automatically recognized and (re-)activated.
With version 0.22 this is no longer working. Entities are no longer dynamically recognised.
Only restarting the integration (ver. 0,22) does the trick.
teampyt

Is your feature request related to a problem? Please describe.
Update Interval should be configure able

Describe the solution you'd like
A clear and concise description of what you want to happen.
Maybe a setting per device or a central setting for:
update-interval: 10 sec

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Is there an option? What is the interval?

thanks a lot!

Version of the custom_component

0.0.13

Configuration

Describe the bug

The recorder reports an unknown unit VA which is being used by the sunspec integration for the sensors:
sensor.solaredge_inverter_ac_apparent_power
sensor.fronius_inverter_ac_apparent_power

Debug log

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:229
Integration: Sensor (documentation, issues)
First occurred: 2:12:00 PM (2 occurrences)
Last logged: 2:12:01 PM

sensor.solaredge_inverter_ac_apparent_power has unknown unit VA
sensor.fronius_inverter_ac_apparent_power has unknown unit VA

Hello together,

I have deleted a devices what works so that I can reduce the query time. Unfortunately I can't create the device anymore. I only get the error message "aborted". No entry is made in the logs

What can/must I do?

User request for support for serial connection in addition to TCP

Add a configuration option for connection type, TCP or serial with an additional step for connection details.

I´m not able to connect to my SE10K inverter from Solaredge although it implements the sunspec implementation.
I disabled and reenabled the Modbus TCP connection and tried to connect through the integration within a timespan of 2minutes but can´t connect to the inverter.

Version of the custom_component

0.0.5 (latest)

Configuration

IP Address from inverter (192.168.2.53)
Port (1502 was set in Solaredge SetApp)

According to https://developers.home-assistant.io/blog/2021/08/16/state_class_total/
the sensor_class for energy and last_reset handling should be changed. Temperature sensors seems also to be handled in a new way.

I guess that much is going on at the moment regarding the new energy handling in HA and I’m not 100% sure that mentioed change affects this component, it could be that it only applies to hourly updated sensors.

Version of the custom_component

0.0.20

Configuration

HA 2022.3.2

Add your logs here.

No new log line is produced

Describe the bug

After initial configuration I wanted to add meter specific values so I tried to add the 65233 model (Configuration>integrations>sunspec>configure) but the config gui gives an error of malformed input on already configured model

d

It would be nice if each device having a common block (inverter, meter, battery, etc.) was visible as a separate device in the Home Assistant for better organization of sensors.

Version of the custom_component

Latest. 0.0.22

Configuration

Just install the integration via HACS and setup in config through the wizard.

Describe the bug

It connects to the ECU and extract the data from the inverter set in the address only once. In the next data refresh the sensors are lost (marked all as unavailable).

Also, once a modbus address fails, it returns an error if you retry to setup it again (removed previously).

Debug log

I only have info level logs, now is not possible to reach the ECU after a lot of retries

2023-03-03 19:28:46.743 DEBUG (MainThread) [custom_components.sunspec] Test connection to 10.0.0.12:502 slave id 1
2023-03-03 19:28:46.743 DEBUG (MainThread) [custom_components.sunspec] New SunspecApi Client
2023-03-03 19:28:46.744 DEBUG (SyncWorker_0) [custom_components.sunspec] Not using cached connection
2023-03-03 19:28:46.744 DEBUG (SyncWorker_0) [custom_components.sunspec] Client connect to IP 10.0.0.12 port 502 slave id 1 using timeout 60
2023-03-03 19:28:46.746 DEBUG (SyncWorker_0) [custom_components.sunspec] Client connected, perform initial scan
2023-03-03 19:28:47.387 INFO (MainThread) [custom_components.sunspec] <custom_components.sunspec.api.SunSpecModelWrapper object at 0x7f7c50621e70>
2023-03-03 19:28:47.387 DEBUG (MainThread) [custom_components.sunspec] Sunspec device unique id: 704000132194
2023-03-03 19:28:47.387 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:28:54.325 DEBUG (MainThread) [custom_components.sunspec] Creating entry with data {'host': '10.0.0.12', 'port': 502, 'slave_id': 1, 'prefix': '', 'models_enabled': [101, 123], 'scan_interval': 30}
2023-03-03 19:28:54.326 INFO (MainThread) [homeassistant.setup] Setting up sunspec
2023-03-03 19:28:54.326 INFO (MainThread) [homeassistant.setup] Setup of domain sunspec took 0.0 seconds
2023-03-03 19:28:54.326 INFO (MainThread) [custom_components.sunspec] 
-------------------------------------------------------------------
SunSpec
Version: 0.0.22
This is a custom integration!
If you have any issues with this you need to open an issue here:
https://github.com/cjne/ha-sunspec/issues
-------------------------------------------------------------------

2023-03-03 19:28:54.326 DEBUG (MainThread) [custom_components.sunspec] New SunspecApi Client
2023-03-03 19:28:54.326 DEBUG (MainThread) [custom_components.sunspec] Setup conifg entry for SunSpec
2023-03-03 19:28:54.326 DEBUG (MainThread) [custom_components.sunspec] Data: {'host': '10.0.0.12', 'port': 502, 'slave_id': 1, 'prefix': '', 'models_enabled': [101, 123], 'scan_interval': 30}
2023-03-03 19:28:54.326 DEBUG (MainThread) [custom_components.sunspec] Options: {}
2023-03-03 19:28:54.326 DEBUG (MainThread) [custom_components.sunspec] Setup entry with models {123, 101}, scan interval 0:00:30. IP: 10.0.0.12 Port: 502 ID: 1
2023-03-03 19:28:54.327 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:28:54.327 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:28:54.328 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:28:54.328 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:28:54.932 DEBUG (MainThread) [custom_components.sunspec] Get data for model 101
2023-03-03 19:28:55.536 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 1.210 seconds (success: True)
2023-03-03 19:28:55.539 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.sunspec
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for Conn in model 123 using prefix : Controls Conn uid c9453defe2077f4f6dbdafd7c2371139_Conn-123-0, device class None unit 
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for WMaxLimPct in model 123 using prefix : Controls WMaxLimPct uid c9453defe2077f4f6dbdafd7c2371139_WMaxLimPct-123-0, device class None unit % WMax
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for WMaxLim_Ena in model 123 using prefix : Controls WMaxLim_Ena uid c9453defe2077f4f6dbdafd7c2371139_WMaxLim_Ena-123-0, device class None unit 
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for A in model 101 using prefix : Inverter Amps uid c9453defe2077f4f6dbdafd7c2371139_A-101-0, device class current unit A
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for AphA in model 101 using prefix : Inverter Amps PhaseA uid c9453defe2077f4f6dbdafd7c2371139_AphA-101-0, device class current unit A
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for PhVphA in model 101 using prefix : Inverter Phase Voltage AN uid c9453defe2077f4f6dbdafd7c2371139_PhVphA-101-0, device class voltage unit V
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for W in model 101 using prefix : Inverter Watts uid c9453defe2077f4f6dbdafd7c2371139_W-101-0, device class power unit W
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for Hz in model 101 using prefix : Inverter Hz uid c9453defe2077f4f6dbdafd7c2371139_Hz-101-0, device class None unit Hz
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for VA in model 101 using prefix : Inverter VA uid c9453defe2077f4f6dbdafd7c2371139_VA-101-0, device class None unit VA
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for VAr in model 101 using prefix : Inverter VAr uid c9453defe2077f4f6dbdafd7c2371139_VAr-101-0, device class None unit var
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for PF in model 101 using prefix : Inverter PF uid c9453defe2077f4f6dbdafd7c2371139_PF-101-0, device class None unit Pct
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for WH in model 101 using prefix : Inverter WattHours uid c9453defe2077f4f6dbdafd7c2371139_WH-101-0, device class energy unit Wh
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for TmpCab in model 101 using prefix : Inverter Cabinet Temperature uid c9453defe2077f4f6dbdafd7c2371139_TmpCab-101-0, device class temperature unit °C
2023-03-03 19:28:56.145 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for St in model 101 using prefix : Inverter Operating State uid c9453defe2077f4f6dbdafd7c2371139_St-101-0, device class None unit 
2023-03-03 19:28:56.146 DEBUG (MainThread) [custom_components.sunspec] Createed sensor for Evt1 in model 101 using prefix : Inverter Event1 uid c9453defe2077f4f6dbdafd7c2371139_Evt1-101-0, device class None unit 
2023-03-03 19:28:56.146 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.controls_conn
2023-03-03 19:28:56.147 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.controls_wmaxlimpct
2023-03-03 19:28:56.147 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.controls_wmaxlim_ena
2023-03-03 19:28:56.147 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_amps
2023-03-03 19:28:56.148 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_amps_phasea
2023-03-03 19:28:56.148 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_phase_voltage_an
2023-03-03 19:28:56.149 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_watts
2023-03-03 19:28:56.149 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_hz
2023-03-03 19:28:56.150 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_va
2023-03-03 19:28:56.150 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_var
2023-03-03 19:28:56.150 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_pf
2023-03-03 19:28:56.151 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_watthours
2023-03-03 19:28:56.152 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_cabinet_temperature
2023-03-03 19:28:56.152 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_operating_state
2023-03-03 19:28:56.153 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.sunspec entity: sensor.inverter_event1
2023-03-03 19:29:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:29:26.202 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:29:26.203 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:29:26.203 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:29:26.804 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:29:26.820 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:29:26.821 ERROR (MainThread) [custom_components.sunspec] Error fetching sunspec data: 
2023-03-03 19:29:26.822 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.620 seconds (success: False)
2023-03-03 19:29:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:29:56.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:29:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:29:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:29:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:29:56.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:29:56.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:30:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:30:26.202 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:30:26.203 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:30:26.203 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:30:26.804 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:30:26.805 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:30:26.806 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:30:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:30:56.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:30:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:30:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:30:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:30:56.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:30:56.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:31:26.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:31:26.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:31:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:31:26.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:31:26.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:31:26.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:31:26.804 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.603 seconds (success: False)
2023-03-03 19:31:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:31:56.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:31:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:31:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:31:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:31:56.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:31:56.804 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:32:26.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:32:26.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:32:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:32:26.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:32:26.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:32:26.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:32:26.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:32:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:32:56.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:32:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:32:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:32:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:32:56.804 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:32:56.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:33:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:33:26.202 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:33:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:33:26.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:33:26.804 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:33:26.804 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:33:26.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:33:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:33:56.202 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:33:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:33:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:33:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:33:56.804 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:33:56.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:34:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:34:26.202 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:34:26.203 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:34:26.203 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:34:26.804 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:34:26.805 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:34:26.806 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.603 seconds (success: False)
2023-03-03 19:34:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:34:56.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:34:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:34:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:34:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:34:56.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:34:56.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.603 seconds (success: False)
2023-03-03 19:35:26.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:35:26.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:35:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:35:26.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:35:26.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:35:26.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:35:26.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.603 seconds (success: False)
2023-03-03 19:35:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:35:56.202 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:35:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:35:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:35:56.804 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:35:56.804 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:35:56.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:36:26.200 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:36:26.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:36:26.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:36:26.201 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:36:26.802 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:36:26.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:36:26.804 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:36:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:36:56.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:36:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:36:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:36:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:36:56.804 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:36:56.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:37:26.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:37:26.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:37:26.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:37:26.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:37:26.802 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:37:26.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:37:26.804 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.603 seconds (success: False)
2023-03-03 19:37:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:37:56.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:37:56.203 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:37:56.203 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:37:56.804 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:37:56.805 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:37:56.807 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.605 seconds (success: False)
2023-03-03 19:38:26.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:38:26.202 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:38:26.203 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:38:26.203 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:38:26.804 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:38:26.805 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:38:26.806 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:38:56.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:38:56.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:38:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:38:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:38:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:38:56.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:38:56.804 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.603 seconds (success: False)
2023-03-03 19:39:26.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:39:26.201 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:39:26.201 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:39:26.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:39:26.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:39:26.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:39:26.805 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.604 seconds (success: False)
2023-03-03 19:39:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2023-03-03 19:39:56.202 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2023-03-03 19:39:56.202 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {123, 101}
2023-03-03 19:39:56.202 DEBUG (MainThread) [custom_components.sunspec] Get data for model 123
2023-03-03 19:39:56.803 WARNING (MainThread) [custom_components.sunspec] Response timeout
2023-03-03 19:39:56.803 DEBUG (MainThread) [custom_components.sunspec] Client reconnecting
2023-03-03 19:39:56.804 DEBUG (MainThread) [custom_components.sunspec] Finished fetching sunspec data in 0.603 seconds (success: False)
.....

Is your feature request related to a problem? Please describe.
Any of sensors provided with this integrations support long term statistics for use with the new Energy panel in HA.

Describe the solution you'd like
HA suggest a solution in: https://www.home-assistant.io/more-info/statistics/

Hello Expert,
update 0.0.6 is not available as update but i had to manually upgrade using reinstall feature.
Now HACS suggests to upgrade from 0.0.6 to 0.0.5.

Thanks
Marcello

Version of the custom_component

0.0.22 on HA 2023.2.3

Describe the bug

I use the sunspec integration to get the values of 4 fronius inverter.
3 of them are connected via lan cable, 1 via wifi.
the wifi connection is terrible so it is lost sometimes.

since I installed the integration HA sometimes was laggy or even sometimes for a short period of time unavailable.
But I was not able to figure out the reason.

Yesterday i disabled the wifi connection, so the 1 inverter is unavailable since then.
HA user experience is worse.

now I disabled the 1 unavailable inverter in the integration settings, and response of HA is normal again.

For me it seems that the tries to reach the unavailable inverter, slows down HA, leads to unavailibilty of the UI and even to restarts of HA.

Maybe it floods the max number of tcp connection or something?

Does this integration still work on HA core-2022.6.6 /Home Assistant OS (supervised), Python-versie | 3.9.12, OS 5.15.32-v8
Components are installed everything is in its place/folder only the integration isn't visible under HA UI -> "Configuration" -> "Integrations" click "+" and search for "SunSpec". I once had it running on my RPI4 HA-server a couple of months ago without any problems (and visible).

In logfile I see:
2022-06-17 11:27:28 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration auto_backup which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-17 11:27:28 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xiaomi_cloud_map_extractor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-17 11:27:28 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-17 11:27:28 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration anniversaries which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-17 11:27:28 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration nest_protect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-17 11:27:28 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration genius_lyrics which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-17 11:27:28 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration sunspec which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-17 11:27:28 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration powercalc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-17 11:27:28 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration apsystems_ecur which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

In configuration.yaml I didn't make any adjustment only installed sunspec using HACS and restarted my HA-server (now serveral times)
version of integration is V0.0.20

Hi,
I want install the sunspec part via HACS, but the process hangs. I have wait for about 60min but the process will not finished completly.

Files in /sunspec folder are not complete. A manualy download/copy of the files are possible.
The sunspec integration installation are also not possible, process is also hanging!

I run into the following issue: When trying to setup the sunspec integration when entering the information as required:

Failed to connect to host 192.168.2.222:502 slave 3 - Device responded - not SunSpec register map

I have eabled the TCP port, het is for sure slave 3 and the IP is also correct. The inverter is a SB3000-TL21 and using the latest version of HA and Sunspec integration.

Is my Inverter to old to be integrated and uses different registers, or might something else be wrong. Who can help?

Great app, works fine with my Fronius Gen24 with battery and smart meter.
I'm really new to home assistant so it might just be me missing something, but I would really like to have the ability to change settings through this integration, i.e write to modbus registers in order to control charging/discharging of my batteries from/to grid. Inspiration can be found here: https://github.com/wlcrs/huawei_solar

BR Oscar