binsentsu / home-assistant-solaredge-modbus

Home assistant Component for reading data locally from Solaredge inverter through modbus TCP
280 stars 70 forks source link

SolarEdge Modbus entities unavailable #253

Closed Scigik closed 1 week ago

Scigik commented 3 weeks ago

Hi, since 8 Aug 2024, apparently around at 0.00 am it seems my SolarEdge modbus entities became unavailable. The Energy Dashboard and all automations depending on the SolarEdge Modbus entities are now non-functional.

home-assistant_solaredge_modbus_2024-08-23T19-57-41.341Z.log I'm new to HA, so not entirely sure how to troubleshoot this. I see in the backup log that HA was updated from core 2024.6.4 to version 2024.7.3 on 9 Aug, so after the start of the bug. The SolarEdge Modbus integration is on version 1.11.1.

I tried to run a debug log on the SolarEdge Modbus entity today (see attached) and saw a few potential issues without knowing how these could have been caused:

"[homeassistant.helpers.frame] Detected that custom integration 'solaredgemodbus' calls asyncforward_entry_setup for integration, solaredge_modbus with title: solaredge and entry_id: 452a94259733555d8ec1f30087c43d3a, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/solaredge_modbus/__init.py, line 130: hass.async_create_task(, please report it to the author of the 'solaredge_modbus' custom integration"

"2024-08-23 15:53:00.723 WARNING (SyncWorker_0) [custom_components.solaredge_modbus] not able to connect to 192.168.50.149:1502 2024-08-23 15:53:15.683 ERROR (SyncWorker_23) [pymodbus.logging] Connection to (192.168.50.149, 1502) failed: [Errno 113] Host is unreachable"

Could you please advise?

Thanks a lot!

robi59italy commented 2 weeks ago

update HA to 2024.08.02

Scigik commented 2 weeks ago

That's already the case. I also just applied the new update to the SolarEdge Modbus integration (now on 1.12.0) but the problem remains. See screenshot attached below.

Any other ideas?

Thank you


From: robi59italy @.> Sent: Saturday, August 24, 2024 1:32:59 PM To: binsentsu/home-assistant-solaredge-modbus @.> Cc: Scigik @.>; Author @.> Subject: Re: [binsentsu/home-assistant-solaredge-modbus] SolarEdge Modbus entities unavailable (Issue #253)

update HA to 2024.08.02

— Reply to this email directly, view it on GitHubhttps://github.com/binsentsu/home-assistant-solaredge-modbus/issues/253#issuecomment-2308362195, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BEXK6LQ62PIOHBG7BE5TK3DZTBVOXAVCNFSM6AAAAABNA3S33OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGM3DEMJZGU. You are receiving this because you authored the thread.Message ID: @.***>

Scigik commented 2 weeks ago

image Screenshot 2024-08-26 215053

Scigik commented 2 weeks ago

I also captured an updated logfile, hoping it can help you assess what's not working. home-assistant_solaredge_modbus_2024-08-26T19-56-04.804Z.log

Thanks a lot for the support.

Kindly

robi59italy commented 2 weeks ago

are you sure your inverter is connected? Try to ping it.

Scigik commented 2 weeks ago

The ping seems successful:

Pinging 192.168.50.149 with 32 bytes of data: Reply from 192.168.50.104: Destination host unreachable. Reply from 192.168.50.104: Destination host unreachable. Reply from 192.168.50.104: Destination host unreachable. Reply from 192.168.50.104: Destination host unreachable.

Ping statistics for 192.168.50.149: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

robi59italy commented 2 weeks ago

no it is not connected you should get time in millisecond... Screenshot 2024-08-26 231815

Scigik commented 1 week ago

@robi59italy Update: seems that something changed in the inverter configuration (not my doing, presumably SolarEdge?) which changed the IP address of the inverter, which is why the connection wasn't working. Thanks for your support!