Sungrow Inverter not integrated via Modbus anymore - after network update

Third party integrations
,
1

hi,

I am using Home Assistant (docker version) with the Sungrow Integration of mkaiser via ModBus: https://github.com/mkaiser/Sun…ter-Modbus-Home-Assistant

This has been working for quite a while (energy dashboard, entities… all fine). Since “some” change I did (I am not sure what might have been the trigger), I have the following status:

  1. The Modbus entities are shown as “unavailable” .

  2. I can reach the inverter under the previously configured fixed IP via “ping”. An “nmap” portscan shows the open Modbus port 502.

  3. The IP that I use for “ping” is the same that is configured in “secrets.yaml” under sungrow_modbus_host_ip

The problem seems to be on modbus level or in the modbus integration in Home Assistant, not on IP level.

configuration.yaml contains:

homeassistant:
  packages: !include_dir_named integrations

The “integrations” folder contains the file modbus_sungrow.yaml.

How can I check that Home Assistant is trying a communication via Modbus?

Thanks.