ok, so I went up to the roof. Turned the lever briefly to P, then connected my phone to SolarEdge AP. On my phone I visited the WiFi gateway IP, which is the actual solaredge device: 172.16.0.1
Under Site communication ModBus was already enabled (not surprisingly, since I was successfully reading inverter data for over a year), port is in default 1502.
But again, home assistant still cant communicate with the inverter, connection refused
My StorEdge inverter converts - fixed IP-address in IoT network - from time to time to a 169.xxx.xxx.xxx (?) network IP-adress. During those times I get the connection refused errno 111.
well, I assigned a static IP in mikrotik for the inverter, not in the device itsels. Iāve never noticed it loosing its IP address, so Iād say yes, itās quite steady. I can ping it ANYTIME, but it wonāt accept now connection to port 1502.
Iāll climb up to the roof again - at least itās sunny and not raining now -, and see if the 120 sec initial connection receiving after enabling modbus is my problem or not.
well, I tried again, but to no avail. Tried disabling then enabling modbus TCP, changing port, but hassio only says connection refused.
Also, I did not find any ethernet port on the device :(:(:(: itās model number is: SE 12.5K - RW0T0BNN4
on the side sticker where the wifi password is written it is also only mentions wifi mac address, no ethernet macā¦ would it be possible that is doesnāt have ethernet port?? then how will I get modbus reporting again?
UPDATE: I tried turning off the inverter and back to see if it helps. Well, when turning off and on modbus in the inverter, I DID receive the message from the inverter about network listening started for 300 sec, what other were mentioning. But even during this period, any connection was refused by the inverterā¦ sux.
There has been some changes in the firmware for the SetApp versions of the SolarEdge inverters, mentioning the modbus over (secured) WiFi. Please check if you have the latest firmware running that allows you to run the modbus over secured WiFi.
Please check this SolarEdge webpage for the information about the latest firmware updates.
hm, wonder what does secure and unsecure wifi to solaredge, tried to find some definition on it, without succesā¦
the installer will hopefully come back in a couple of weeks to install some additional panels, Iāll ask them to update the firmware, and also to plug in an UTP cable to avoid this problem in the future (to plug in UTP I realised you have to open the cover and plug it into the motherboard, and feed the cable through a rubber enclosing, so itās not a job for the average Joe like me).
Until then Iām stuck with the monitoring API integration I guess.
This is the best way to get a 100% solid connection to your inverter and indeed never tinker the inside of an inverter if youāre not certified to do so (like me).
yep, good luck indeed, since the energy price crisis, people in my country (Hungary) went nuts to install solar power (like it wasnāt an existing alternative before, nvmā¦). I placed my purchase order 6 months ago with a not so small downpayment, and I still canāt get a date for plugging in 6 panels into an existing installation.
BTW, I wonder what the company is doing currently, since our government was ākindā enough to effectively kill consumer solar power business by denying power export into the grid for future installations (only battery usage is possible currently, crazy, eh?)
At least, that could help you to identify if this is an possible issue with the firmware.
THen, I would get in contact with the SolarEdge support.
They can also update the firmware if it is related to the Wifi in combination with the Firmware.
Question now: can I anyhow force a firmware update? Unfortunately I canāt use the SetApp, with my regular monitoring credentials it wonāt let me log in to the app. I can only use the inverterās admin page after I connect to its AP.
SolarEdge can do it remotely if I ask them? Should I contact my solarpanel dealer how installed SolarEdge, or SolarEdge directly?
as said,
their support can do another firmware update where these issues should be resolved, as far as I can say.
But since I donāt have wifi connected devices, I canāt say for sure.
Hi all, has anyone implemented an automatism that sends a notification if the inverter is not available? It happened to me after a blackout that the inverter didnāt restart, I noticed it after several hours.
Thanks
I tried to get my modbus tcp working tonight, and I was able to get it enabled on my master inverter. But, my slave inverter (I have 2 inverters and 1 meter) must not be ID 2 on the RS485-1 bus as Iām getting an error during setup of the integration that it gets no response from inverter ID 2.
So, I then tried to get to my slave inverterās commissioning page by following the same steps to enable wifi that I did on the master and then accessing 172.16.0.1 on the slave inverterā¦ however, when I connect to the slave inverterās wifi SSID I cannot access that IPā¦ the browser just times out.
Is there a special way to access the commissioning page on a slave inverter to configure it versus the master? I think the only thing I need to do is change the ID of the slave to ID 2 on the RS485-1 bus.
I got the issue figured out. In case anyone else has the same issueā¦ for some reason that slave inverter would not bring up the commissioning page via the IPā¦ so, I just signed up for a SE Installer account and downloaded SetApp. That worked like a charm. Loving this integration!
try modbus port 1502
the inverter can run either on 502 or 1502 ā¦ for me, it started working as soon as I used the second port.
also, check the logs from the integration. it should highlight if it could not establish a connection to the inverterā¦
Also, are you using wireless or wired connection?
-, and see if the 120 sec initial connection receiving after enabling modbus is my problem or not.
