Niels,
I already want to thank you a lot for this. Things are finally working. My solarpanels are visible again and things are showing up in the Energy panel
I now also see the sensor.inverter things. I’m not sure if I ever did see them.
Thanks again! I was already thinking to do a restore or a reinstall. You saved me from doing that!
Regards,
Ron
I wouldn’t mind getting some tips from you on getting this done in Grafana. It does look impressive!
Take a look at this: Verbrauchsdaten mit Grafana visualisieren | haus-automatisierung.com [4K] - YouTube It learns you some of the basics for grafana. It’s not for HA but still gets you a lot of information how to set it up. To set up in HA you first install it by using the supervisor addons InfluxDB. After configured this database you can install grafana the same way.
grafana+influxdb|690x384. When it’s running its not that difficult and great for visualising sensordata 
The current firmware of my ECU-C is version C1.2.0
. For who is interrested in this config. Now not working because of sleepingmode ECU (I think)
I now have installed the beta version v1.12:
Now it comes up under integrations as a new discoverd device:
It’s the wifi IP I’am sure about. It’s checked in the webportal of my ECU:
Do I have to remove the configuration in the configuration.yaml which is now:
apsystems_ecur:
host: 192.168.XXX.XXX
scan_interval: 300
I can’t get it to work in this new beta version.
Can you check the home-assistant.log? and search for apsystems please provide any output you see from that.
It should auto-import the settings from your configuration.yaml. But you can certainly delete from the file.
Log:
Logger: custom_components.apsystems_ecur.config_flow
Source: custom_components/apsystems_ecur/APSystemsECUR.py:231
Integration: APSystems PV solar ECU-R (documentation)
First occurred: 16:26:15 (5 occurrences)
Last logged: 16:28:27
APSystemsInvalidData exception: Error getting checksum int from ‘ECU Query’ data=b’’
Traceback (most recent call last):
File “/config/custom_components/apsystems_ecur/APSystemsECUR.py”, line 228, in check_ecu_checksum
checksum = int(data[5:9])
ValueError: invalid literal for int() with base 10: b’’
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/config/custom_components/apsystems_ecur/config_flow.py”, line 40, in async_step_user
test_query = await ap_ecu.async_query_ecu()
File “/config/custom_components/apsystems_ecur/APSystemsECUR.py”, line 112, in async_query_ecu
self.process_ecu_data()
File “/config/custom_components/apsystems_ecur/APSystemsECUR.py”, line 254, in process_ecu_data
self.check_ecu_checksum(data, “ECU Query”)
File “/config/custom_components/apsystems_ecur/APSystemsECUR.py”, line 231, in check_ecu_checksum
raise APSystemsInvalidData(f"Error getting checksum int from ‘{cmd}’ data={debugdata}")
custom_components.apsystems_ecur.APSystemsECUR.APSystemsInvalidData: Error getting checksum int from ‘ECU Query’ data=b’’
In configuration.yaml I now have:
apsystems_ecur:
host: 192.168.XXX.XX
When I don’t put in the IP adres and only the line
apsystems_ecur:
Nothing happens, which I think is understandable
Can you try power cycling your ECU? This is unfortunately an error condition we’ve seen from these devices. What’s happening at this stage, is the integration opened the connection and issued the first command APS1100160001END which when the ECU works correctly will cause it to return data about itself.
For some reason ECUs can get into a state where they just return no data at all, which is what your device is doing (indicated by data=b’’) - basically an empty byte array. We haven’t been able to figure out why this happens, other than the device and/or firmware isn’t very good.
When we’ve seen this the only solution has been a power-cycle of the device.
When its open:
When its closed:
Using the ethernetport of the device instead of wifi ip also doesn’t fix the problem.
Tomorrow a new day 
Oh wow, that’s quite a complicated setup. My ECU just plugs into a regular wall outlet, and I’ve put a smart switch on it, so I can just power cycle it that way. Sorry I don’t have a better answer. It would be really nice if APSystems would just make and publish an API that they would support for local query.
This one is using CT clamps to see the actual energy consumption on the main wires (3 phase a 25 A). Sometimes I regret buying this complicated ECU-C instead of a ECU-R…NOT
Yes, I looked at the “C” models and seemed pretty nice, but my installer didn’t really offer it. I installed a z-wave power monitor that has CT clamps on my incoming electrical feed, which has worked surprisingly well.
Sorry for not posting if solution above works in my case (power down+new version 1.2.5). My EPU-C broke down…the button I meant.
Now my installer going to install a new ECU-C. My trust in APS has dropped quite a bit. I’'ll be back when everything is fixed over here.
The ecu has been replaced. Thumps up for the installer ;-). But I can’t get the integration from https://github.com/ksheumaker/homeassistant-apsystems_ecur working (v.1.2.5) yet. It keeps reporting that the ip address is not correct and have just checked it on ECU-C web interface and am sure I entered the correct address. In configuration.yaml I have the following text:
apsystems_ecur:
** host: 192.168.XXX.XXX (WIFI IP ADDRESS).**
logfile:
This error was caused by a custom integration.
Logger: custom_components.apsystems_ecur.APSystemsECUR
Source: custom_components/apsystems_ecur/APSystemsECUR.py:147
Integration: APSystems PV solar ECU-R (documentation)
First occurred: 14:29:47 (1 occurrences)
Last logged: 14:29:47
Unkonwn error from ECU after issuing cmd=APS1100280002XXXXXXXXXXXXXEND error=[Errno 104] Connection reset by peer. Closing socket and trying again try 1 of 3
Maybe I’m doing something wrong: Did make an issue on github https://github.com/ksheumaker/homeassistant-apsystems_ecur/issues/40. Anybody knows what I am doing wrong?
The ip-address needs to be from the wireless connection. You probably have a wired connection. On my ECU-R I needed to logon to it, activate the wireless connection and use that ip-address.
It could be the same for your setup
The v1.2.5 beta integrations doesn’t work with the ECU-C (I think). I am trying v.1.1.2 and it’s working for now.
With 1 ECU-C, 6 micro-inverters (3xQS1 and 3xYC-600) and 18 solarpanels I now got 7 devices and 47 entities:
.
In grafana it now looks like this:
Hope it still works tomorrow.
No it was the ip-adres of wifi I’m sure. In the ECU-C you can check that in the local portal of the ECU itself. Is more advanced than the ECU-R 
Your setup is very impressive indeed.
Today everything was gone from this APS ECU-integration. Strange to see 8 devices instead of 7 with a warning in HA.
More info on: https://github.com/ksheumaker/homeassistant-apsystems_ecur/issues/40
This morning I had the same issue.
Suddenly there was 1 extra device added: ECU None
Then I re-installed the Integration, but get an error when I entered the WiFi address
After re-assigning the ECU-R to the WiFi network, I was able to install the integration and all is working now without issues.
I will see what tomorrow brings.
