home-assistant-solaredge-modbus icon indicating copy to clipboard operation
home-assistant-solaredge-modbus copied to clipboard

Modbus entity unkonw

Open meden199 opened this issue 3 years ago • 15 comments

I have installed the HACS component. Add the solarEdge to the intergrations. The devices are showing up, but all data is unknow.

Where dit I make a mistake? was it at the Modbus RS458-2 configuration? Maybe a screenshot from a working device will help me?

meden199 avatar Nov 06 '21 14:11 meden199

Hi, I've set up the RS458-2 to "SolarEdge Device" But I will try to provide a Screenshot from my inverter Settings later today

ChristophCaina avatar Nov 08 '21 14:11 ChristophCaina

I also have issue with unknow device. I can ping my inverter. But from logs I see that component can not logon to SE inverter. Ten błąd pochodzi z niestandardowej integracji.

Logger: custom_components.solaredge_modbus Source: custom_components/solaredge_modbus/init.py:215 Integration: SolarEdge Modbus (documentation) First occurred: 17:59:12 (610 occurrences) Last logged: 19:44:58

Error reading modbus data Traceback (most recent call last): File "/config/custom_components/solaredge_modbus/init.py", line 187, in async_refresh_modbus_data update_result = self.read_modbus_data() File "/config/custom_components/solaredge_modbus/init.py", line 228, in read_modbus_data self.read_modbus_data_inverter() File "/config/custom_components/solaredge_modbus/init.py", line 552, in read_modbus_data_inverter inverter_data = self.read_holding_registers(unit=1, address=40071, count=38) File "/config/custom_components/solaredge_modbus/init.py", line 215, in read_holding_registers return self._client.read_holding_registers(address, count, **kwargs) File "/usr/local/lib/python3.9/site-packages/pymodbus/client/common.py", line 114, in read_holding_registers return self.execute(request) File "/usr/local/lib/python3.9/site-packages/pymodbus/client/sync.py", line 106, in execute raise ConnectionException("Failed to connect[%s]" % (self.str())) pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.30.8:1502)]

kazek127 avatar Nov 10 '21 18:11 kazek127

Hi, sorry - due to late shift I was not able to get the data from the inverter to show my settings :-(

If you login to your inverter with SetApp, you should be able to change the settings for RS458-2. Please post some screenshots about your settings in RS458-1 and RS458-2 this could help trying to solve your connection issues.

ChristophCaina avatar Nov 10 '21 18:11 ChristophCaina

I check the inverter again and nothing changes on it, only perform update OS of the inverter. Earlier work fine.

kazek127 avatar Nov 10 '21 19:11 kazek127

I am pretty sure, that this issue is not related with the integration itself. Most probably it is something with your modbus settings on the inverter.

It might be, that you need to change the settings for RS458-2 temporariyl and then change them back to your original configuration. Honestly speaking, I am not quite sure about this issue - Since you haven't provided screenshots of your settings, I cannot really compare them with my setup...

ChristophCaina avatar Nov 10 '21 19:11 ChristophCaina

If it's any value, last time I upgraded I had to do what ChristophCaina suggested to get it to open the port = change the ra485 settings then change them back again. I went and actully changed all the settings when it didn't work the first time just changing -2.

HyperActiveJ avatar Nov 10 '21 19:11 HyperActiveJ

But from SE application I can see that the inverter is connecting to the power meter via RS485. I attaching screens from my inverter SJ1021-07E0D4A3F-14-20211110-0821-10 SJ1021-07E0D4A3F-14-20211110-0821-41 SJ1021-07E0D4A3F-14-20211110-0821-47 SJ1021-07E0D4A3F-14-20211110-0821-54 SJ1021-07E0D4A3F-14-20211110-0822-06

kazek127 avatar Nov 10 '21 19:11 kazek127

The First Connection rs458-1 seems to be OK, thus is the Connection to the Meter.

The important Connection for the Integration should be the rs458-2. As far as I got from the Translation, the settings in rs458-2 should also be OK.

I would try to Change it to Solarlog and then Change it Back to the current setting.

ChristophCaina avatar Nov 10 '21 20:11 ChristophCaina

I'm experiencing the same error. Has this been resolved? I'm on the latest firmware

Version core-2022.2.9
Installation Type Home Assistant OS

Giolovin avatar Feb 25 '22 16:02 Giolovin

These are my settings (in Dutch)

I'm connected with a powerline adaptor with a lan + fixed ip address on the inverter Printscreen

Giolovin avatar Feb 25 '22 16:02 Giolovin

I still have this issue. After the last update, Homeassistant SE stops working with HA. SE is pinging but I got error that HA can not connect to SE

kazek127 avatar Feb 25 '22 17:02 kazek127

Are you connecting to the inverter over wifi? ModbusTCP over wifi seems to be an issue with the new firmware.

See details in #67

purcell-lab avatar Mar 15 '22 09:03 purcell-lab

In new FW was disabled ModbusTCP over WIFI. Only now works on LAN

pepsonEL avatar Mar 15 '22 10:03 pepsonEL

I've got this issue too; can anyone help please? I'm connecting over ethernet (never had WiFi). The inverter responds to ping ok. I'm not convinced that port 1502 is open but I can't seem to figure out what i've done wrong.

PS. Ignore the battery error, Solar Edge are working on my Power Banks and have them turned off currently.

2022-05-04 17:55:08 ERROR (MainThread) [pymodbus.client.sync] Connection to (192.168.68.187, 1502) failed: [Errno 111] Connection refused 2022-05-04 17:55:13 ERROR (MainThread) [pymodbus.client.sync] Connection to (192.168.68.187, 1502) failed: [Errno 111] Connection refused 2022-05-04 17:55:13 ERROR (MainThread) [custom_components.solaredge_modbus] Error reading modbus data

IMG_1383

theneiljohnson avatar May 04 '22 17:05 theneiljohnson

I managed to fix my issue by disabling Modbus TCP and then re-enabling again. Very weird!

theneiljohnson avatar May 04 '22 19:05 theneiljohnson