Coder Social home page Coder Social logo

alexdelprete / ha-abb-powerone-pvi-sunspec Goto Github PK

View Code? Open in Web Editor NEW
23.0 23.0 5.0 1.24 MB

HA Custom Component to integrate data from ABB/Power-One/FIMER PV Inverters that support SunSpec Modbus (Sunspec M1, M101, M103, M160), natively or through the VSN300 wifi logger card.

License: MIT License

Python 98.81% Shell 1.19%
abb fimer home-assistant home-assistant-component home-assistant-custom homeassistant inverter modbus modbus-tcp power-one sunspec

ha-abb-powerone-pvi-sunspec's People

Contributors

alexdelprete avatar binsentsu avatar dependabot[bot] avatar hwikene avatar vnijhuis-sqills avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

ha-abb-powerone-pvi-sunspec's Issues

randomic HA response delay with ABB Integration

Hi

after some weeks of troubleshooting, I'm pretty sure there is a problem with the integration. Let me describe:
When the sun goes down, the inverter switch off and home assistant is not able to reach the inverter, also via IP (ping).
In that phase starts a random delay in the HA responsivenessy. At least in my case it is easy to reproduce. It's enough to switch on/off a light, or a switch, repeatedly and after 4-5 cycles you can see that delay. That Light or switch does not respond for 2-3 secs and then start again switching fine, till the next 4-5 cycles.
I could imagine an issue when the abb integration try to reach the inverter (polling period) during the switch off phase.
Reloading HA or the Integration only, fix the issue because inverter is switched off and entities are removed.

I'm not sure when it appeared, I realized one or two months ago.

running the follow:
immagine

the configuration I use is the follow:

immagine

As a workaround I solved with an automation that is reloading the abb config entry, after few minutes from the switch off (that I detect with a ping sensor) to remove entities and few minutes after the switch on to restore entities.

alias: Abb Inverter reload
description: ""
trigger:

  • platform: state
    entity_id:
    • binary_sensor.ping_abb_inverter
      to: "off"
      for:
      hours: 0
      minutes: 3
      seconds: 0
  • platform: state
    entity_id:
    • binary_sensor.ping_abb_inverter
      to: "on"
      for:
      hours: 0
      minutes: 5
      seconds: 0
      condition: []
      action:
  • service: homeassistant.reload_config_entry
    data: {}
    target:
    device_id: b906894628baf2ad2040b276f38b68ca
    mode: single

No particular logs a part from the one when the integration is unable to reach the inverter. I reloaded HA so I lost the one from this night but I can gather tomorrow if you need.

Config flow - error 500 Internal Server Error

Running HASSOS on Raspberry Pi 4. Added through HACS, restarted HA, and proceeded to add integration in HA.
HA on latest version 2023.01.04

Getting error:
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

Any idea how to fix?

Log:

Logger: aiohttp.server
Source: config_entries.py:865
First occurred: 12:03:47 AM (8 occurrences)
Last logged: 12:27:53 AM

Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 81, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 148, in post
return await super().post(request)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
result = await method(view, request, data, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 71, in post
result = await self._flow_mgr.async_init(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 229, in async_init
flow, result = await task
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 247, in _async_init
flow = await self.async_create_flow(handler, context=context, data=data)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 865, in async_create_flow
flow = handler()
TypeError: ABBPowerOnePVISunSpecConfigFlow.__init__() missing 1 required positional argument: 'config_entry'

Integrazione di un inverete PVI6000 del 2010

Salve,
vorrei integrare il mio inverte PVI6000 del 2010 in HA.
Ho contattato PoverOne e mi hanno detto che VSN300 non è compatibile con i vecchi inverter ma ci vuole il VSN700 che costa 700€!
C'e' qualche modo per usare il VSN300 perche non si può spendere 700€ per un logger!
Grazie

Model unknown Manuf.: ABB - Model: -3P25-

Hello Alex,

Could you please add the model FIMER UNO-DM-5.0-TL-PLUS to the database, which is identified with the code -3P25-?
Also, I'm facing an issue due to an error following the installation of the latest version (2.2.1) due to pymodbus not working. Could you please help me in solving this, please?
Thanks in advance for your assistance
Domenico

New Inverter Model

@alexdelprete

Can you update the model list?

Logger: custom_components.abb_powerone_pvi_sunspec
Source: custom_components/abb_powerone_pvi_sunspec/api.py:134
Integration: ABB/Power-One/FIMER PVI SunSpec (documentation, issues)
First occurred: 18:52:01 (116 occurrences)
Last logged: 19:48:31

(opt_comm_model) Model unknown, report to @alexdelprete on the forum the following data: Manuf.: ABB - Model: -3P21- - Options: 0x00ED/0xFF69/ - OptModel: 0x00ED/0xFF69/ - OptModelInt: 0

My model is UNO-DM-3.3-TL-PLUS

Thank you

Traceback with HASSIO and UNO-DM-4.6-TL-PLUS

After months without issues (UNO-DM-4.6-TL-PLUS), today after HA reboot started the following traceback, with all entities unavaileable:

Logger: homeassistant.components.sensor
Source: custom_components/abb_powerone_pvi_sunspec/init.py:293
Integration: Sensor (documentation, issues)
First occurred: 08:21:20 (1 occurrences)
Last logged: 08:21:20
Error while setting up abb_powerone_pvi_sunspec platform for sensor

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/abb_powerone_pvi_sunspec/sensor.py", line 21, in async_setup_entry
hub.read_modbus_data_realtime()
File "/config/custom_components/abb_powerone_pvi_sunspec/init.py", line 293, in read_modbus_data_realtime
self.data["invtype"] = INVERTER_TYPE[invtype]
KeyError: 102

Also tested with a previous VM snapshot. Same traceback.

Home Assistant Core 2022.6.7
Home Assistant Supervisor 2022.05.3
Home Assistant OS 8.2

Anything to check?

Conflict with Modbus: official integration

Hello Alex,

I installed the new version after updating HA Core.
HA receives data from my 2 inverters, the model is now recognised but LOG is showing the folowing error regarding modbus:

2023-01-23 11:00:41.597 ERROR (MainThread) [homeassistant.setup] Setup failed for modbus: Unable to import component: No module named 'pymodbus.client.sync'`

Also, another device which uses modbus does not work, seemingly due to some sort of conflict.

Could you please help me in solving this?
Thanks again for your great support,
Domenico

Originally posted by @usrpend in #44 (comment)

Model unknown

Hi Alessandro,

I receive this message in the logs

Model unknown, report to @alexdelprete on the forum the following data: Manuf.: ABB - Model: -3P38- - Options: 0x0BED/0xFF69/ - OptModel: 0x0BED/0xFF69/

my Model: UNO-DM-2.0-TL-PLUS

Regards.
LN

The inverter disconnects and reconnects frequently.

Hi. For a few weeks now, my inverter has started disconnecting and reconnecting frequently and the sensors become, consequently, unavailable.

Device specifications:
UNO-DM-3.0-TL-PLUS
ABB
Firmware: 2201A

Inverter connection options:
TCP port: 502
Modbus Slave address of the inverter: 254
Modbus Register Map Base Address: 40000
Polling period: 30

Hardware: Raspberry Pi4 with Hassio

You can find attached the complete logs from the restart of Home Assistant and a screenshot of a graphic showing the frequent disconnections.

If it can be useful, I've noticed that, among the logs, you can find lines like this:

2023-10-17 10:28:35.628 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] ABB SunSpec Update data coordinator update
2023-10-17 10:28:35.628 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Hub connect to IP: 192.168.1.130 port: 502 slave id: 254 timeout: 29
2023-10-17 10:28:35.628 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Check_Port: opening socket on 192.168.1.130:502 with a 3.0s timeout.
2023-10-17 10:28:38.633 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Check_Port (ERROR): port not available on 192.168.1.130:502 - error: 11
2023-10-17 10:28:38.634 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Inverter not ready for Modbus TCP connection
2023-10-17 10:28:38.634 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Async Update Data error: Inverter not active on 192.168.1.130:502
2023-10-17 10:28:38.635 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Error fetching abb_powerone_pvi_sunspec data:
2023-10-17 10:28:38.635 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Finished fetching abb_powerone_pvi_sunspec data in 3.008 seconds (success: False)

Also, there wouldn't seem to be any problems using the inverter's official application (Energy Viewer), because it shows normal values.

Thanks in advance.

home-assistant_abb_powerone_pvi_sunspec_2023-10-17T08-39-35.512Z.log
Graphic

Update Problem (file missing)

@alexdelprete

there's something wrong with HACS update process.
Today i update your integration to 2.6.7 via HACS and it is not working again.

This is the folder before update

pre_update

and this is after update

post_update

Now i try to reload the file manually as yesterday

Thank you for your support

DC voltage shows -0.0 V regardless of output

I have only tried v3.3.0 of the integration, so have no info on previous versions. My inverter has the option to connect two strings, but I only have one connected.
So far the integration works well (kudos for it) except the missing DC power.

Thanks in advance!

Inverter
ABB UNO-DM-2.0-TL-PLUS-SB-Q (single phase)
2201A firmware

Integration options
Modbus address: 254
Register map base address: 40000
TCP port: 502

image
image
image

Error installing integration

Hi,

I've been trying installing this integration, but I always get the following error:

Errore
Impossibile caricare il flusso di configurazione: {"message":"Invalid handler specified"}

The log shows the following:

2022-10-24 18:12:06.919 INFO (SyncWorker_7) [homeassistant.util.package] Attempting install of pymodbus==3.0.0
2022-10-24 18:12:15.199 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.abb_powerone_pvi_sunspec.config_flow
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.10/site-packages/homeassistant/loader.py", line 722, in get_platform
    cache[full_name] = self._import_platform(platform_name)
  File "/srv/homeassistant/lib/python3.10/site-packages/homeassistant/loader.py", line 739, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
  File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 992, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/home/homeassistant/.homeassistant/custom_components/abb_powerone_pvi_sunspec/__init__.py", line 15, in <module>
    from pymodbus.client import ModbusTcpClient
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/__init__.py", line 5, in <module>
    from pymodbus.client.serial import AsyncModbusSerialClient, ModbusSerialClient
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/serial.py", line 10, in <module>
    from pymodbus.client.base import ModbusBaseClient, ModbusClientProtocol
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/base.py", line 9, in <module>
    from pymodbus.client.mixin import ModbusClientMixin
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/mixin.py", line 19, in <module>
    class ModbusClientMixin:  # pylint: disable=too-many-public-methods
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/mixin.py", line 56, in ModbusClientMixin
    count: int = Defaults.Count,
AttributeError: type object 'Defaults' has no attribute 'Count'
2022-10-24 18:12:15.211 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration abb_powerone_pvi_sunspec: Exception importing custom_components.abb_powerone_pvi_sunspec.config_flow

Could you please help me with this?

Thanks

Entities unavailable after upgrade to V.2.0.0

Hi,

Big improvements in this new version! was waiting for some of them! Thanks!
however I am having issues after upgrading to V.2.0.0

V1.2.1 - OK
V.2.0.0 - NOK
for tested, I tried a downgrade to 1.2.1 and it started working again!

home-assistant.log:

2021-09-10 12:32:48 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Reading data failed! Inverter is unreachable on ID=247
2021-09-10 12:32:48 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Reading data failed! Inverter is unreachable on ID=247
2021-09-10 12:32:48 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up abb_powerone_pvi_sunspec platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/abb_powerone_pvi_sunspec/sensor.py", line 25, in async_setup_entry
    "model": hub.data["comm_model"],
KeyError: 'comm_model'

Inverter : UNO-3.0-TL-OUTD + VSN300

System Health

version core-2021.9.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.9.6
os_name Linux
os_version 5.10.17-v8
arch aarch64
timezone America/Sao_Paulo
Home Assistant Community Store
GitHub API ok
Github API Calls Remaining 4461
Installed Version 1.15.2
Stage running
Available Repositories 881
Installed Repositories 11
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 6.3
update_channel stable
supervisor_version supervisor-2021.09.0
docker_version 20.10.7
disk_total 57.8 GB
disk_used 6.0 GB
healthy true
supported true
board rpi4-64
supervisor_api ok
version_api ok
installed_addons eWeLink Smart Home (1.2.0), File editor (5.3.3), Terminal & SSH (9.1.3), ESPHome (2021.8.2)
Lovelace
dashboards 3
resources 10
views 3
mode storage

Thanks,
Bruno

Dynamic Feed-In Control Sensor

Hi there.
I'am using an inverter UNO-DM-4.0-TL-PLUS with Dynamic Feed-In Control via REACT-MTR-1PH but it seems that the app is not loggin the Grid useage as in the Inverter APP/Web portal.
This will be pretty handy to check and keep my grid usage and total energy consumtion (including the solar).
Inverter_snapshot

I don't know if its feasible.
Thanks in advance for your time.

Edit: Spelling

Model unkmown

Hi, I have a Uno DM 6.0 and I get the following error for unknown model:

Manuf.: ABB - Model: -3P31- - Options: 0x05ED/0xFF45/ - OptModel: 0x05ED/0xFF45/ - OptModelInt: 5

Some of the values are correct but mostly not with base 40000 and slave ID 1

What could be done?

UNO-DM-4.0-TL-PLUS 140055-3P22-1721

Ciao Alex,
ho scaricato la tua integrazione per provare ad integrare l'inverter in oggetto, ma non ci riesco...ti chiedo cortesemente supporto.
Il modello è nell'oggetto: Questo il log che ho scaricato dal debug:
2024-01-04 15:24:10.602 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Setup config entry for ABB
2024-01-04 15:24:10.602 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Data: {'port': 502, 'slave_id': 1, 'base_addr': 40084, 'scan_interval': 31, 'name': 'ABB Inverter', 'host': '192.168.1.36'}
2024-01-04 15:24:10.603 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Options: {}
2024-01-04 15:24:10.603 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Setup entry with scan interval 0:00:31. Host: 192.168.1.36 Port: 502 ID: 1
2024-01-04 15:24:10.603 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] ABB SunSpec Update data coordinator update
2024-01-04 15:24:10.603 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Hub connect to IP: 192.168.1.36 port: 502 slave id: 1 timeout: 30
2024-01-04 15:24:10.603 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Check_Port: opening socket on 192.168.1.36:502 with a 3.0s timeout.
2024-01-04 15:24:10.610 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Check_Port (SUCCESS): port open on 192.168.1.36:502
2024-01-04 15:24:10.610 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Inverter ready for Modbus TCP connection
2024-01-04 15:24:10.621 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Modbus TCP Client connected
2024-01-04 15:24:10.621 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Start Get data (Slave ID: 1 - Base Address: 40084)
2024-01-04 15:24:10.682 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] (read_rt_1) Slave ID: 1
2024-01-04 15:24:10.682 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] (read_rt_1) Base Address: 40084
2024-01-04 15:24:10.682 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Async Update Data error: 'ascii' codec can't decode byte 0xff in position 10: ordinal not in range(128)
2024-01-04 15:24:10.682 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] Finished fetching abb_powerone_pvi_sunspec data in 0.079 seconds (success: False)

Se hai pazienza di darmi qualche dritta, te ne sarei grato.

PS: Ho già aperto un thread sull'argomento, ma è andato perso perchè ho avuto altre difficoltà che mi hanno distolto dal seguire la mia richiesta.
Grazie Comunque,
C.

v3.2.0 introduces static values values for DCx Current, DCx Voltage, and DCx Power

Since updating from v3.1.5 to v3.2.0, the entites for DCx Current, DCx Voltage, and DCx Power are set at 1, rather than the expected values for each DC array (two in my case, DC1 and DC2). The solar inverter is already updated to latest firmware version 2201A and RS485 protocol is set to Protocol Aurora Server, but this seems to make no difference to any of the values shown in this integration (I've tried all four options)

Expected Result:
DC1 Current, DC1 Voltage, DC1 Power, DC2 Current, DC2 Voltage, and DC2 Power entities show correct values for each DC array

Current Result:
DC1 Current, DC1 Voltage, DC1 Power, DC2 Current, DC2 Voltage, and DC2 Power entities show value of 1

Hardware:
Make: ABB
Model: UNO-DM-5.0-TL-PLUS
Firmware: 2201A
Inverter Type: Single Phase

Integration options:
TCP port: 502
Modbus Slave address of the inverter: 254
Modbus Register Map Base Address: 40000
Polling period: 30

Thanks in advance, cheers for the great integration

home-assistant_abb_powerone_pvi_sunspec_2023-11-26T02-39-48.861Z.log
2023-11-26 10_36_12-

Configuration Wizard only permit to select serial dongles

Hi there,

After adding the repository and restarting HA, the integration "Aurora ABB PowerOne Solar PV" appears available, but when I select it, que configuration wizard is different from the available in the documentation:
image

Instead of an IP, a TCP Port, etc, only permit to choose from the available serial dongles, as a RS485 or USB-RS485 Adaptor Port...

Am I doing something wrong?

Thanks.

Best regards.

Not getting DC value on multiple mppt with single phase inverter

I just installed this component v2.6.6 and found that I can see only a single DC Voltage (and Current) with value of -0.0 V. The AC and Energy values appear to be OK.

2023-08-10 16:52:05.155 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] (read_inv) Manufacturer: Power-One
2023-08-10 16:52:05.155 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] (read_inv) Model: -3G03-
2023-08-10 16:52:05.155 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] (read_inv) Options: 6
2023-08-10 16:52:05.155 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] (opt_printable) opt_model: 6 - opt_model_int: 54
2023-08-10 16:52:05.155 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] (opt_comm_model) comm_model: PVI-6000-OUTD
2023-08-10 16:52:05.155 DEBUG (MainThread) [custom_components.abb_powerone_pvi_sunspec] (read_inv) Version: C033

My inverter is single-phase version but running connected to two-phase AC (AC Voltage and Current are ok) with two DC MPPT strings .

@alexdelprete I have made a test a test branch (based on v2.6.6) to try to make it define single or multiple mppt sensors.

Can you check to see if you agree with this idea : v2.6.6...ivanfmartinez:ha-abb-powerone-pvi-sunspec:check_mppt

I know that there are a multi_mppt_nr on the code but I have tried to make just little changes now to make it works in my system with v2.6.6, as I have seen that the master branch have a lot of other commits.

Unable to import component: No module named 'pymodbus.client.sync' after upgrade to 2022.10.3 and/or OS 9.2

recently I started to see error msgs after the reboot. Usually after one or two try the error disapper and working fine. Today I'm not able to make it works.
Looks like a module is missing. Could be one of recent updates?

2022-10-14 08:22:57.839 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration abb_powerone_pvi_sunspec: Unable to import component: No module named 'pymodbus.client.sync'

Model unknown Manuf.: ABB - Model: -3P46-

After long time running fine, today started loggin this message of model unknown

2022-10-14 13:48:43.663 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] (opt_comm_model) Model unknown, report to @alexdelprete on the forum the following data: Manuf.: ABB - Model: -3P46- - Options: 0x03ED/0xFF69/ - OptModel: 0x03ED/0xFF69/ - OptModelInt: 3

Lost of data readings after one day

Buonasera,

I have installed your plugin via HACS on a venv installation of HA core on RPI 4. Everything is working fine with my PVI-3.0-OUTD and I can access all sensor data. The problem is that every day/couple of days the integration stops reading data and I have to re-configure it (I just click "INVIA") to have it work again. It is important to notice that I restart HA through an automation every night. Can it be related ? Can I automate this step to force reload configuration after HA restart ?

Grazie
Screenshot 2023-07-03 alle 21 40 43
Screenshot 2023-07-03 alle 21 34 30
Screenshot 2023-07-03 alle 21 33 02

ABB, UNO-DM-PLUS ETHERNET COM KIT

Hi, I have an Aurora 3.0 UNO with a Lantronics 485 to IP converter which communicates to the windows software called Aurora Communicator.Screenshot 2021-09-05 at 14 08 07
Will your integration work, If not will this card work?

"Invalid handler specified"

error in configuration spet by click on new integration -> ABB Power-One PVI SunSpec
Errore
Impossibile caricare il flusso di configurazione: {"message":"Invalid handler specified"}

Inverter non connesso

Salve, l'integrazione all'inverter funzionava correttamente fino alla versione 2023.11.2 (mi pare... cioè fino a due versione fa rispetto alla 2023.12.0)... ho provato a ricaricare l'integrazione più volte, riavviare Home Assisitant e alla fine anche cancellare l'integrazione e reinserirla, ma niente.
Sui registri ho il seguente errore

Logger: aiohttp.server
Source: /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py:421
First occurred: 11:09:14 (1 occurrences)
Last logged: 11:09:14

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 543, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 114, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 233, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 31, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 149, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 63, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 177, in post
    return await super().post(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper
    result = await method(view, request, data, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 293, in async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 389, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/abb_powerone_pvi_sunspec/config_flow.py", line 90, in async_step_user
    uid = await self.test_connection(name, host, port, slave_id, base_addr, scan_interval)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/abb_powerone_pvi_sunspec/config_flow.py", line 65, in test_connection
    self.hub_data = await self.hub.async_get_data()
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/abb_powerone_pvi_sunspec/api.py", line 185, in async_get_data
    self.read_sunspec_modbus_model_1()
  File "/config/custom_components/abb_powerone_pvi_sunspec/api.py", line 221, in read_sunspec_modbus_model_1
    read_model_1_data.registers, byteorder=Endian.BIG
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ModbusIOException' object has no attribute 'registers'

Le seguenti sono le informazioni sulla versione:
Core 2023.12.0
Supervisor 2023.11.6
Operating System 11.2
Frontend 20231206.0

Integration Error after HA Update

Hi @alexdelprete ,

after last HA update i have the following error on log window about the integration.

`Logger: custom_components.abb_powerone_pvi_sunspec
Source: custom_components/abb_powerone_pvi_sunspec/init.py:228
Integration: ABB Power-One PVI SunSpec (documentation, issues)
First occurred: 05:32:57 (1 occurrences)
Last logged: 05:32:57

(read_data) Error: check Slave ID: 1 & Base Address: 40000`

Until this update everything worked fine

Can you help me to resolve this issue?

Thank you for your support

HA Running Information:

Home Assistant 2023.9.0
Supervisor 2023.08.3
Operating System 10.5
Frontend 20230906.1 - latest

Model unknown

I would like to report an unsupported inverter model:

(opt_comm_model) Model unknown, report to @alexdelprete on the forum the following data: Manuf.: Power-One - Model: -3N41- - Options: 0xF2 - OptModel: 0xF2 - OptModelInt: 242
(read_inv) Reading data failed! Please check Slave ID: 247
(read_inv) Reading data failed! Please check Reg. Base Address: 0
(read_data) Error: check Slave ID: 247 & Base Address: 0

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.