SolarEdge, GIVTCP MQTT issues

Installation
1

I started to have issues my home assistant that the supervisor would not start or my GivTCP hangs, so I have been repeaty rebooting my system, and so far I have been lucky, but in doing so I have lost a lot of data. so I have chosen to rebuild the environment, but here I have run into a few issues

is that when I install the givTCP and put in my details for my inverter, with an ip address of “192.168.1.7” and my Invertor is located on a vlan with a IP address of “192.168.40.2” the givtcp addon can’t see if
so I have gone to the file, and I am confused, I have one invertor, and two battery’s – can some one please help me fill this in.
{
“Web_Dash”: false,
“Web_Dash_Port”: 3000,
“MQTT_Output”: true,
“MQTT_Address”: “core-mosquitto”,
“MQTT_Username”: “mqttuser”,
“MQTT_Password”: “mqttuser”,
“MQTT_Retain”: false,
“MQTT_Topic”: “givtcp”,
“MQTT_Port”: 1883,
“inverter_enable_1”: true,
“invertorIP_1”: “192.168.40.2”,
“serial_number_1”: “SJ2820-073039E45-59”,
“inverterName_1”: “GivTCP”,
“inverter_battery_only_1”: true,
“inverter_enable_2”: false,
“invertorIP_2”: “”,
“serial_number_2”: “”,
“inverterName_2”: “GivTCP2”,
“inverter_battery_only_2”: false,
“inverter_enable_3”: false,
“invertorIP_3”: “”,
“serial_number_3”: “”,
“inverterName_3”: “GivTCP3”,
“inverter_battery_only_3”: false,
“inverter_enable_4”: false,
“invertorIP_4”: “”,
“serial_number_4”: “”,
“inverterName_4”: “GivTCP4”,
“inverter_battery_only_4”: false,
“inverter_enable_5”: false,
“invertorIP_5”: “”,
“serial_number_5”: “”,
“inverterName_5”: “GivTCP5”,
“inverter_battery_only_5”: false,
“Influx_Output”: false,
“influxURL”: “”,
“influxToken”: “”,
“influxBucket”: “”,
“influxOrg”: “”,
“self_run”: true,
“self_run_timer”: 30,
“self_run_timer_full”: 120,
“HA_Auto_D”: true,
“dynamic_tariff”: false,
“export_rate”: 0.04,
“day_rate”: 0.395,
“day_rate_start”: “05:30”,
“night_rate”: 0.155,
“night_rate_start”: “23:30”,
“TZ”: “Europe/London”,
“Print_Raw_Registers”: true,
“Log_Level”: “Info”,
“queue_retries”: 2,
“data_smoother”: “none”,
“Smart_Target”: false,
“GE_API”: “”,
“SOLCASTAPI”: “”,
“SOLCASTSITEID”: “”,
“SOLCASTSITEID2”: “”,
“PALM_WINTER”: “01,02,03,10,11,12”,
“PALM_SHOULDER”: “04,05,09”,
“PALM_MIN_SOC_TARGET”: 25,
“PALM_MAX_SOC_TARGET”: 45,
“PALM_BATT_RESERVE”: 4,
“PALM_BATT_UTILISATION”: 0.85,
“PALM_WEIGHT”: 35,
“LOAD_HIST_WEIGHT”: “1”,
“evc_enable”: false,
“evc_ip_address”: “”,
“evc_self_run_timer”: 10,
“evc_import_max_current”: 60,
“v3upgrade”: true,
“auto_scan”: true,
“Model_1”: “Ac”,
“Model_2”: “”,
“Model_3”: “”,
“Model_4”: “”,
“Model_5”: “”,
“Host_IP”: “192.168.1.49”,
“cache_location”: “/config/GivTCP”,
“PYTHONPATH”: “/app”,
“serial_number_evc”: “”,
“timezone”: “Europe/London”
}

and I am getting the following results

image
image1162×684 26.7 KB

So when I try and set up my Solaredge, I don’t get the admin tab to allow me to get access to the API, is this a normal issue ?

2

Pretty sure GivTCP is for GivEnergy Inverters only ?

There is an HA Solaredge Integration:

or this modbus interface:

3

hi Holdestmade, the stuff above is point to my GivEnergy, which I am having issues with,

the question about the SolarEdge I understand that there is a addon, but it is asking for a API, which I can’t get access to - as it is asking me to click on a admin tab - which is not shown in my web portal

4

Not sure what you mean, have you got a GivEnergy inverter or a SolarEdge one ?

EDIT: I see it has discovered an AC3 and 2 batteries. Have you got a SolarEdge as well ?

Also, I think you need to set up the username and password for MQTT, that’s probably what the errors are at the end of the log

5

afternoon
ok I have the GivEnergy finding and reporting information, but no saving it, which is not a big issues at the moment as I want to get everything talking, plus I need to go and refresh my knowledge obn how to do this.

with the solaredge, I tryied with the local option, but adding in the sensor into my Config file the following lines,

    - sensor:
  -     platform: solaredge_local
        name: SolarEdge
        ip_address: 192.168.40.3

but after a reboot it is not reporting any data so I return back to the doc and it looks like my inventor don’t allow local API as my as last four digitals are BNN4

“Only specific models support the local API. The local API is available on inverters that do not have an LCD character screen. You can also check the datasheets if in the section “Additional Features”, sub-section “Inverter Commissioning” is present the following line “With the SetApp mobile application using built-in Wi-Fi access point for local connection”. These inverters also have a part number that ends with a 4. For example: SEXXK-XXXXXBXX4 or SEXXXXH-XXXXXBXX4”

so I am back to the issue that I can’t get the API from the web poral for SolarEdge

6

The solaredge_local integration is useless now because SE blocked LAN access to the inverter’s internal web server. I don’t remember which FW version did this but it was many years ago.

The only option for local access now is Modbus, which I recommend my integration: GitHub - WillCodeForCats/solaredge-modbus-multi: The Complete Local (Modbus/TCP) SolarEdge Integration for Home Assistant