SolarEdge Local does not (and will not) work

[Santanachia]

The problem

As you can see in this issue and this issue, this integration has not worked for a long time and is not likely to work again.

Here you can see how many people are using it:

Maybe it is time to remove this integration? You have already removed integrations that worked and were used by many users (e.g. rpi_gpio), but this one does not work and almost nobody uses it

What version of Home Assistant Core has the issue?

core-2022.6.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

SolarEdge Local

Link to integration documentation on our website

https://www.home-assistant.io/integrations/solaredge_local

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

requests.exceptions.ConnectionError: HTTPConnectionPool(host='***', port=80): Max retries exceeded with url: /web/v1/status (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8b12c790>: Failed to establish a new connection: [Errno 110] Operation timed out'))

[probot-home-assistant]

solaredge_local documentation
solaredge_local source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @drobtravels, @scheric, mind taking a look at this issue as it has been labeled with an integration (solaredge_local) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[scheric]

Well the three installations have the analytics on so there could be more.

The integration could still work. I can not verify this anymore because the manufacturer SolarEdge has pushed a software update. This update blocked usage of protobuf communication (used by this integration) when the inverter is in normal operation mode.

[phispi]

Today I got a SolarEdge SE5K-RWB inverter installed (that's one without display) where the solaredge_local integration works seemlessly:

• CPU Version: 4.15.119
• DSP1 Version: 1.20.1056
• DSP2 Version: 2.20.710
• Zähler Version: 0.1077.0
• DSP3 Version: 0.3.4
• WSA Version: 4.15.41

I hope that this gets not updated tonight to a version where this integration does not work anymore but given the CPU version, I already should be affected by the problem many people describe.
http://192.168.1.59/web/v1/status returns protobuf data.
I'll post if it stops working during the next days.

[phispi]

Next day: Still works. I really hope that solaredge_local continues to work (and is not removed) as I don't want my data to leave the home network. Let's see what's in a week.

[badblocks]

My SolarEdge setup with Home Assistant does work, so I don't know what the problem is.

My device recently did upgrade from CPU Version 4. 7.26 to 4.14.229 and it's still working with "solaredge_local". (I would expect it would not)

Only one thing needs attention by the developer of "solaredge_local":
I suspect the protobuf data has changed on the readout of each connected optimizer (if present in your setup). (maintenance.proto)
So I don't receive power, status & temperature data anymore from each optimizer. Other data is still coming in.

I think SolarEdge has changed some things in the software update....

[phispi]

Since 17th of June, 11:07 AM I can't reach the local webserver on the SolarEdge device anymore (http://192.168.1.59/web/v1/status times out and therefore solaredge_local stopped working). I did not do any configuration changes myself. https://monitoring.solaredge.com/ continues to work. This doesn't seem to be caused by a firmware update - my CPU version (according to https://monitoring.solaredge.com/) still is 4.15.119. I'll try to follow up on this...

[scheric]

@phispi If you do not want use the online integration you can also use the local modbus TCP integration. https://github.com/binsentsu/home-assistant-solaredge-modbus

[phispi]

@scheric Thanks, that's what I'll do.

Still, regarding this issue, I hope I could contribute to the discussion by providing the experience with a new installation. I asked the technician whether he has some kind of additional admin interface where he could enable the local web server but he said no and recommended to use the API.

By the way: The local web server that used to be available for a few days after switch-on was not protected by a password - so I guess it's intentional that anyone being in your local network cannot mess with SolarEdge settings.

In case I find a way to make http://192.168.1.59/web/v1/status available I'll post, but chances are low.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.