Connection to (192.168.x.x, 502) failed: [Errno 111] Connection refused #247
-
|
Looking for a like help (newbie here) and guidance. I'm getting the following error message when trying to configure FoxESS - Modbus: "Unable to connect to your inverter. Make sure the connection details are correct and try again. Details: Connection to (192.168.xx.xx, 502) failed: [Errno 111] Connection refused." Inverter: H1-5.0E error logs: 2023-05-16 15:43:22.917 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 7 replies
-
|
"Connection refused" means that we sent a packet to your inverter, and your inverter sent back a packet rejecting us. So something's listening for connections at that IP address, but it refused our attempt to connect. Make sure the IP address is correct, first of all. I think there's an option in the inverter menu to see what IP it has? If you've assigned the inverter a static IP using the front panel, make sure that your router isn't configured to give that IP out to other devices on your network. In that case you can have two devices with the same IP, and it's pot luck which you end up connecting to (and connections won't be stable). |
Beta Was this translation helpful? Give feedback.
-
|
I've set the inverter with a Static IP address and registered the MAC address via the router/DHCP server. On scanning my network, I don't see it. The invertor is hardwired to my network and it seems to be using a FoxESS Smart LAN module which I can track back to the switch but offers me a completely different IP/MAC Address :( |
Beta Was this translation helpful? Give feedback.
-
|
Wait, you have plugged an ethernet cable into T he socket directly on the inverter (not the data logger thing with the qr code on), correct? |
Beta Was this translation helpful? Give feedback.
-
|
The ethernet cable is plugged into the Smart LAN ethernet adaptor, the Smart LAN adapter is plugged into the inverter - as setup by my installer |
Beta Was this translation helpful? Give feedback.
-
|
That's used by the data logger to send data to the foxess cloud, but you can't use that to access the modbus registers. For that, you need to have a separate cable connected directly to the inverter. See the images on the wiki. |
Beta Was this translation helpful? Give feedback.
-
|
Massive thanks - this newbie has just been educated! |
Beta Was this translation helpful? Give feedback.
-
|
I'll update the wiki to be clearer |
Beta Was this translation helpful? Give feedback.
-
|
If you've set the IP address as static on the inverter, you don't need to do anything with the DHCP server other than make sure that the static address you've set is not in the pool of addresses it's giving out. Otherwise you risk problems. For instance, I have my DHCP server using a pool of 192.168.0.50-192.168.0.255, everything below 192.168.0.50 is available to be statically assigned by me, although in practice I'm only actually using about 15 IP addresses in this range. I'd look for the setting on your router / DHCP server where you can set the pool, give yourself some room to manouevre at either the beginning or end of the range, and then make sure the inverter is assigned an address in that range. |
Beta Was this translation helpful? Give feedback.
-
|
You've explained what I've setup up perfectly - I've mapped the MAC address to the allocated static IP. |
Beta Was this translation helpful? Give feedback.
-
|
I know the main issue is resolved now but it's worth stressing this point - if you set a static IP on a device, you don't need to map anything (and doing so doesn't achieve anything). You just need to make sure that no other devices get assigned the same IP. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe worth pointing them to something like this
https://www.cisco.com/c/en/us/support/docs/smb/General/Best-practices-for-setting-a-static-IP-addresses-in-Cisco-Small-Business.html
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: calum-mcfarlane ***@***.***>
Sent: Wednesday, May 17, 2023 10:11:52 AM
To: nathanmarlor/foxess_modbus ***@***.***>
Cc: John W. Lucas ***@***.***>; State change ***@***.***>
Subject: Re: [nathanmarlor/foxess_modbus] Connection to (192.168.x.x, 502) failed: [Errno 111] Connection refused (Discussion #247)
I know the main issue is resolved now but it's worth stressing this point - if you set a static IP on a device, you don't need to map anything (and doing so doesn't achieve anything). You just need to make sure that no other devices get assigned the same IP.
—
Reply to this email directly, view it on GitHub<#247 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKTTIRXCUPGAMR2VHNVF6NDXGSI5RANCNFSM6AAAAAAYDY4ZHI>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
That's used by the data logger to send data to the foxess cloud, but you can't use that to access the modbus registers. For that, you need to have a separate cable connected directly to the inverter. See the images on the wiki.