Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

After update no communication with inverter #67

Open
andrejs2 opened this issue Oct 27, 2021 · 39 comments
Open

After update no communication with inverter #67

andrejs2 opened this issue Oct 27, 2021 · 39 comments

Comments

@andrejs2
Copy link

After update of integration last week (to 1.5.1) I can't get any data to entities in HA anymore. It states "unknown".
Tried:

  • reseting inverter
  • reinstalling component
  • deleting integration and install it again
  • checked router and IP - works as before
  • SE app over API works.

Anyone has any suggestions, how to handle this?
Thanks!
@ChristophCaina
Copy link
Contributor

have you checked if your entities are enabled in the entity secion of the integration?

@chrisbucher
Copy link

I have the same issue and tried the same things. All entities are enabled but state "unknown".

@KM192
Copy link

KM192 commented Nov 26, 2021

I have the same issue after solaredge firmware upgrade to CPU: 4.14.107, DISP1: 1.20.939, DISP2: 2.20.609, WSA: 4.14.70.

@rudybroersma
Copy link

rudybroersma commented Dec 20, 2021 •
edited

Same here, it looks like SE's firmware is broken. With 4.14.107 the ModbusTCP port isn't open:

telnet 192.168.178.121 502
Trying 192.168.178.121...
telnet: Unable to connect to remote host: Connection refused

AC powercycling the inverter doesn't help. Nothing seems to work so far. I guess we need to wait for a new firmware, but as of today (december 20) 4.14.107 is the latest one.

I have created a support ticket with SolarEdge. I'll let you know once they give any information.

Note: I think the issue KM192 and I are seeing isn't related to the issue opener. That looks like a integration upgrade, while I'm seeing issues after a inverter firmware upgrade.

@KM192
Copy link

KM192 commented Dec 20, 2021

It's worst. The solaredge support claims that this is a feature, not a bug. Unless they change their minds, nothing will change.

@chrisbucher
Copy link

I also reported this problem to solaredge support. After 2 weeks their their solution was to downgrade my inverter's firmware to the previous version. I got modbus TCP working again that way.

@KM192 what did they tell you? What should this "feature" do?

@KM192
Copy link

KM192 commented Dec 20, 2021 •
edited

Support answered that Modbus interface shouldn't work via Wifi from the beginning and in the newest version they "repaired" that.
We should rise as many support ticket as possible to have this option back.

@rudybroersma
Copy link

I got a reply from support that this issue is fixed in a newer firmware, but that firmware isn't released yet. They tried to update my inverter remotely, but that failed. As of yesterday SetApp doesnt have a newer version:

@KM192 If Modbus shouldn't work from WiFi, how else is ModbusTCP supposed to work? Only using Ethernet? That doesn't make sense.

@KM192
Copy link

KM192 commented Jan 10, 2022 via email •
edited

@pepsonEL
Copy link

pepsonEL commented Jan 10, 2022 via email

@Sven-v-Beuningen
Copy link

In my case it‘s also not working with wired LAN connection with the mentioned version. All sensors show „unknown“. I can‘t tell if it would work with old firmware, because it‘s a newly installed inverter.

@MarcHagen
Copy link

i can somewhat understand why you don't want modbus tcp over wifi, reliability could be a issue, but i think allot of installations have the extra wifi module (THAT COSTS MONEY) because there is NO ethernet connection....

Also opened a support case.

@rudybroersma
Copy link

rudybroersma commented Jan 28, 2022 •
edited

The service dept. from SolarEdge wanted to upgrade my firmware to a beta version last month, as that might resolve the issue. There is a new firmware out today (version .222), installed it, but doesn't fix it. I'll inform SolarEdge.

@MarcHagen There is an ethernet connection, inside the unit. But that doesn't matter. ModbusTCP doesn't work over ethernet either

@MarcHagen
Copy link

MarcHagen commented Jan 28, 2022 •
edited

I think it's time for a ESP32 with WiFi antenna to connect with the RS485 interface ... (I have a SE3000)
Almost regret getting a solaredge system

Update:
I've bought a cheap wifi client with an ethernet cable (TL-WR802N) and modbus TCP works just fine now.

@pepsonEL
Copy link

Can you explain more....

@rudybroersma
Copy link

I just received a reply from SolarEdge that they fixed something, and indeed! My ModbusTCP is back!!
I've asked for an update regarding the how and what and if this is a permanent solution.

I noticed a drop in PV output, so I think they did a remote firmware upgrade on my unit.

@kochen
Copy link

kochen commented Feb 16, 2022

I just received a reply from SolarEdge that they fixed something, and indeed! My ModbusTCP is back!! I've asked for an update regarding the how and what and if this is a permanent solution.

I noticed a drop in PV output, so I think they did a remote firmware upgrade on my unit.

After 2 weeks of 0 reaction (!), I got the same response from SolarEdge.s support.
Though they can't remotely update their FW, because the device keeps disconnecting from the WIFI 🤔

@chrisbucher
Copy link

I just received a reply from SolarEdge that they fixed something, and indeed! My ModbusTCP is back!! I've asked for an update regarding the how and what and if this is a permanent solution.

I noticed a drop in PV output, so I think they did a remote firmware upgrade on my unit.

Could you please tell us what FW version you now have? (And what inverter type)
Thanks!

@rudybroersma
Copy link

Cant right now, I'm not at home. Ill have to check later.
I have an SE17K (European) without display.

@rudybroersma
Copy link

I checked with SetApp. It seems my firmware is downgraded. I think my firmware was downgraded to 4.14.13 or 4.14.14. I immediately killed the App once it started upgrading to 4.14.222 again so I didn't have time to take a good look at it.

@rudybroersma
Copy link

I see that a new firmware was released a few days ago. 4.14.228. Could someone please try installing that and see if that resolves the issue?

@rudybroersma
Copy link

rudybroersma commented Feb 25, 2022 •
edited

Alright. My firmware was downgraded to 4.12.14 by SolarEdge. I've contacted them again, indicating that this is no solution.
They informed me that they have disabled ModbusTCP over WiFi and the latest firmware (released february 2022) has ModbusTCP working over Ethernet.

I've connected my inverter to Ethernet and I can confirm that with the latest firmware (as of Feb '22) I can able to connect to ModbusTCP on the SE inverter. I've asked them WHY they dropped WiFi Modbus support, but I get the feeling the person I'm talking to has no clue either.

Anyway.. ModbusTCP over Ethernet works!

PS: I have a SetApp (without display) inverter.

@SgtBatten
Copy link

Damn, just installed my system two days ago and was hoping to use this integration. Guess I'll have to get a sparky out to install an ethernet cable.

Out of curiosity can you guys access the web interface on your LAN? I can only access it using the inverters direct wifi connection

@rudybroersma
Copy link

rudybroersma commented Mar 11, 2022 •
edited

No, web interface is not available over ethernet or regular WiFi.

Instead of running an ethernet cable there are other options. You can buy a "WiFi to Ethernet" adapter for a few bucks, which might be cheaper than running a cable. Additionally, if you have the knowhow to do so you can actually use the "SetApp" WiFi (what you call 'direct wifi connection') network. As long as there is a client connected to that WiFi SSID, it stays online.

So you can use eg. a Raspberry Pi or something to tunnel from the SetApp WiFi to your regular network.

eg something like this:
https://www.amazon.com/IOGEAR-Ethernet-2-WiFi-Universal-Wireless-GWU637/dp/B018YPWORE

@SgtBatten
Copy link

SgtBatten commented Mar 11, 2022 •
edited

Additionally, if you have the knowhow to do so you can actually use the "SetApp" WiFi (what you call 'direct wifi connection') network. As long as there is a client connected to that WiFi SSID, it stays online.

Interesting. I am connected to it on my laptop right now but still can't telnet to 1502 which people are saying is a good test. Thank you though, I'll keep working at it.

I have an Energy Hub running 4.14.230 which is the latest according to the website.

@purcell-lab
Copy link

This is annoying, I have a new install with two inverters, one running firmware 4.15.110 (beta?) and the other running 4.14.228.

My old install has two inverters both running firmware 4.12.35 allows MODBUS over Wifi and has been rock solid into HA for over 12 months.

No mention of dropping ModbusTCP over wifi support in the Feb 22 changelog:
https://www.solaredge.com/setapp-inverters-firmware

I have also raised a ticket with SolarEdge, who have referred me back to my installer, I have gone back to SolarEdge and asked them to enable remotely.

Maybe I need to ask them to downgrade to 4.12.14, which seems to be the last working version?

This was referenced Mar 15, 2022
Open
Open
@kiwibayer
Copy link

kiwibayer commented Jun 1, 2022 •
edited

just got a replacement new inverter and ran into the same issue.
Modbus over Wifi seems to be not enabled anymore.
Modbus over the ethernet port works fine.

Is there a public thread that we can refer Solaredge to and add our voice?

@rudybroersma
Copy link

I wouldn't bother. They said to me they disabled ModbusTCP over WiFi due to 'security concerns'.
They did this on purpose.. So I don't think they will revert the change.

@MarcHagen
Copy link

I've bought a cheap wifi client with an ethernet cable (TL-WR802N) in wifi client mode.
Now i can still access the inverter over wifi and modbus on the ethernet port.

@stuarts0011
Copy link

stuarts0011 commented Jun 1, 2022 via email

@SgtBatten
Copy link

I just ran a cable. I asked my installer to do that originally anyway and they would only give me the wifi module. pretty annoying but working fine hard wired now.

@bjeanes
Copy link

bjeanes commented Jun 2, 2022

I have one getting installed in next 2-3 weeks and made sure the installer would wire it in for me. I already have the cat6 in the roof where the inverter will be going!

@MarcHagen that's clever. I actually have a device similar to the TL-WR802N kicking around that I am not using, so that's a great back-up plan

@Santanachia Santanachia mentioned this issue Jun 22, 2022
Closed
@rkambach
Copy link

rkambach commented Jun 24, 2022 •
edited

Same here opened the Inverter mounted a Ethernet cable and connected it to the comms board, if your not trained specialist in electricity switch of the inverter off before you open it it has 400AC and 750DC more then enough to kill ya, wait a minute before you open it, Capacitors... use a TL-WR802N @bjeanes mentioned and configure it for client mode, boot system back up, connects over the same IP as before but then trough the TPLINK device, problem solved, oh go to your ethernet prohibit comms for the inverter give it a fixed IP address as well, at least you stopped solar edge from the next update that's gonna break something. The TPLIN device turns a wireless signal into a wired one very handy and low cost...$25

@bjeanes
Copy link

bjeanes commented Jun 24, 2022

i just got my inverter installed and had them wire it via ethernet anyway. I'm still waiting for the grid to certify installation so not quite up and running yet but I hopefully shouldn't need to use my TL-WR802N (not sure if that's actually the model I have but I have one of the similar products in their line up if not)

@infoedkok
Copy link

infoedkok commented Oct 18, 2022 •
edited

Same issue here. But as of september 2022 SE released a new inverter firmware and this is what they say about modbus com in tje release notes:
Modbus TCP over secured Wi-Fi is now officially supported for residential inverters
Modbus TCP over unsecured Wi-Fi is blocked
Modbus TCP over Wi-Fi for commercial inverters is blocked
Note: Modbus TCP over Ethernet and Modbus TCP over RS485 for all inverters are supported.

Could secured wifi for our inverters solve this issue?

@ChristophCaina
Copy link
Contributor

@infoedkok : I don't know, what SolarEdge defines as "secured / unsecured WiFi".
my guess is, that unsecured wifi is an open wifi without encryption - which I would NEVER use in my network.

So, yes - a firmware update and a secured wifi could solve the issues.
Also a wired connection over ethernet would be an option (which I would also prefer over the wifi - if possible)...

What you could also do:
Install a Wifi extender near your Inverter - and connect the inverter to the extender through ethernet.
Then, you could use the extender to connect to your existing wifi network again.

This COULD workaround the limitations given from SolarEdge...

@infoedkok
Copy link

Got the latest firmware and now it's working (Domoticz) ! Apparently, my home Wifi is secure ;-)
And that connection reports a whole bunch of data elements.

@gimmi
Copy link

gimmi commented Aug 14, 2023

I have a new SolarEdge installation (CPU Version report 4.18.200) that is connected to my home WiFi, and I am not able to connect to Modbus TCP on port 1502.

Using SetApp, I can confirm that Modbus TCP is enabled and that the port is 1502

@leroyraw
Copy link

Same for me, also latest firmware and not able to connect via wifi. Wifi is setup as WPA so is secure, not sure why I can't connect. If anyone finds a solution to this, please post here :-)

I'm also open to use a workaround like the wifi router option, but not sure how this would work. Anyone care to explain a bit more?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests