Could this harm inverter communications in any way?

[MrPeteH]

I'm beginning to become concerned about possible serious costs of failure... at the bottom of this post I have a few questions

My setup:

• All hard-wired ethernet communication (using wifi only for initial inverter stuff)
• Reasonably sophisticated home lab network with rock solid gigabit switch, firewall, etc
• Solaredge with 25 panels, no battery, paid to extend all warranties to 25 years
• Great install/service company, although I pay for service calls under warranty (if it wasn't their install issue)
• Original install Fall 2020

All was well, reasonably stable.

• I've had HA since early 2023, with usual updates
• In April 2025, my SolarEdge communications went wonky:
  • Production fine (visible to power company ;) )
  • Pings fine
  • But zero communication with the monitoring site
  • I didn't notice (lots of life going on)

August we got it taken care of. Required replacing the entire inverter :(

• Apparently a known issue
• New inverter "should be" more robust in comm's

Once that was working, I installed solaredge-modbus-multi

• All well
• Now I discover, again no communication since late September!

Just a guess but "they" are likely to poke hard at anything unusual.

Just in case:

• I disabled the three SolarEdge devices detected by this addon
  • Inverter, ImpExp Meter, Production Meter
  • I still see a small amount of network traffic between HA and the Inverter; no idea what this is

QUESTIONS

• Aside from bad commands, which I don't use, Is there any evidence that LAN traffic to/from inverter could cause an issue (I've NEVER used "commands" to inverter over LAN)
• Aside from uninstalling this tool, which would lose a lot of configuration work and past data, is there anything else I can disable to make this addon completely silent from the inverter's perspective?

Thanks for ANY insights, ideas and more!
Pete
*

[WillCodeForCats]

I can't imagine any way that reading causes failures.

[WillCodeForCats]

If you want to stick with things that are officially documented and supported by SolarEdge, then you should only use the Auto-Detect Meters option. I see no reason any failure could be blamed for using a feature (modbus) that SolarEdge provides documented support for.

Batteries and control commands, on the other hand, are not in public support documentation and were implemented through info found on the internet or trial and error. The integration defaults reflect this (meters on, batteries off, all controls off).

Example:

Whether or not your installer has any experience with modbus is a totally separate issue, but SolarEdge supports modbus just fine.

[MrPeteH]

Makes sense. Since I've got no batteries attached, that's a perfectly safe set of assumptions anyway :)

We'll see how this goes...