Changed router, lost inverter connection.

[HughInDevon]

Hi,
Just changed router. Kept the same SSID and password but now, thanks to my daft fiddling I have lost the connection to my router.
I am using HA with the Nathan Marlon modbus integration. To try and restore it I deleted the foxes integration from HA and now I can’t reconnect.
I am using a Waveshare RS485 to Ethernet adaptor and using the Vircom tool to restore the previously saved settings.
When I try and add the foxes integration I get the following.

Unable to connect to your adapter. Ensure the adapter is properly configured and the connection details are correct, then try again. Details: Connection to (192.168.1.200, 502) failed: Errno 101 Network unreachable.

I am very stuck and would really appreciate some help. I am using the Adapter IP address of 198.168.1.200, adapter port 502 and inverter slave ID of 247. Last value checked on inverter display.

Thanks, Hugh

[Dave Foster]

You need to start by double checking that the new router has the same IP range as the old, the default address of 192.168.1.200 is not a range used by many routers, it could be 192.168.0.x for example so restoring the waveshare to what it was may be making it unreachable.

Once you know for sure what the routers IP range is you can set the waveshares device IP address and also gateway address (which is usually the IP address of your router) and then use the device IP address in the integration to connect to.

[HughInDevon]

Hi Dave,
Thanks for the reply. I have made a bit of progress and have now managed to get the Nathan Marlor integration reloaded. Home Assistant is now running and has the Foxess integration loaded. I can see the outputs from the sensors I have added to the system but unfortunately, I am not getting any input from the inverter. On my dashboard I just see "Entity is currently unavailable: - followed by the entity name." for all the parameters I am tracking.

I have tried turning the inverter off and on again - not sure if I did it correctly - but it hasn't made any difference.

I am at a loss as to what to try next so any advice is very welcome.

Regards, Hugh

[HughInDevon]

Hi Dave,

I may have spoken too soon.

This is the message I get when I look at the log entry.

Connection Status changed to Modbus Error: [Connection] Failed to connect[CustomModbusTcpClient 192.168.178.1:502]

[Dave Foster]

I’m wondering if when you added the integration this time the inverter name has changed which will rename all your sensors, that means that any of your old sensor names in the dashboard will show as unavailable.

Check to see what the integration has setup, you can see that in HA under Settings, Devices & Services, find Foxess - modbus in the list and click on ‘1 device’ , does that list all your sensors and whether they are working, or are they showing as unavailable?.

Not sure why they would be unavailable but you’ll need to check system, logs to see what is being reported.

[HughInDevon]

Weirder still!

When I look at the list of entities for the inverter in settings, all the ones that used to be available, in the Status column they all show a white exclamation mark in a red circle. When I hover the mouse cursor over this it says 'unavailable'. However, when I click on the red circle it immediately shows a graph of the output for today. So, the connection is OK and it must be something to do with names as you suggest.
Next question, how do I check what the names are?

Regards, Hugh

[Dave Foster]

If you are looking at the list of entities in Devices & Settings, they are the correct entity names so if it's showing historical data but 'unavailable' now that suggests it has lost its connection.

Obviously the inverter / wiring hasn't changed so this isn't a problem there - if you've changed the waveshare settings I would start by double checking those settings are as per the guide (apart from the IP/gateway address which is specific to you) and then power cycle that device.

The waveshare is connected over ethernet so that should be stable, is the home assistant connected over ethernet or wifi ?.

Also what version of the integration are you running, Fox have changed the firmware so often that it's best to load the latest beta release of the integration v1.16.0b2 and also check what firmware your inverter is running if it hasn't been updated within the last 6 months.

[HughInDevon]

Hi Dave

Not sure what the inverter software version is. Fox app shows

Device Information
State：
Offline
SN：
60KE1030456C052
Plant：
West Dodscott Cottage
Model：
KH10
Datalogger：
609L3EJF2C6A854
Version_Master：
1.60
Version_Slave：
1.02
Version_ARM：
1.58

Are these the latest versions?

Thanks, Hugh

[Dave Foster]

Very latest on the firmware page is Master 1.71, Manager 1.67, Slave 1.03 so you are a bit off the latest but not that far and it should be fine to work on the latest foxess modbus integration.

Your datalogger is off-line so looks like you’ll need to re-connect that (have a look at Will’s video ‘shorts’ he has done a recent one that shows the best way to connect that https://youtube.com/shorts/_fWcbtRehbI ... h11VScIeLi) but again that shouldn’t be the issue with your modbus but better to fix it now, then once you are back on-line restart your HA and check the logs to see what it reports on startup.

[Dave Foster]

Hi Hugh, any joy with it ?