Hi everyone, I just got an update to my iOS app for AP Systems and noticed that they are implementing an official API program, anyone else got this? I believe this is great if it allow us to have a proper path to the data.
1 Like
Interesting, still i would not want to be dependent on their website. (and i expect them to make it a subscription when they have enougth users on the api)
Today proven once again when evohome from honeywell had interruptions. Could not control my own thermostate because of it, (had to walk to the radiator and use the turn knob 
)
If they would implement the same api on the ECU, i would be very pleased.
1 Like
Just saw that as well. I am quite disappointed as it seems to be cloud-dependent, and what is this 1,000 times a month limit? If I can’t get more than 1,000 data poll a month, it’s quite useless. Finally, this “Subscribe to a service” button is a bit scary.
Why couldn’t they have a local JSON table available to poll like many other boxes…
1 Like
Hi All, just a small beginners question that I didn’t see come up yet in this threat, I got the solar panels and app up and running but how can I find the local IP adress and port of the APsystems which is required for connecting it to Home assistant… I tried every button within the EMA app but nothing there, I dont have the small display on the device (which the manual refers to) and tried to go through my Net analyzer app to check all local ip adresses but nothing clearly stands out as the APsystem ip adress. help is very much appreciated.
Some important details are missing but I assume you have an ECU-R connected wirelessly via WiFi. The bottom LED on the ECU is on, so you have an internet connection on the ECU. You can find the IP address of the ECU in your router. The ECU probably received an IP address via DHCP, then look for a hostname like Beijing LT Honway Technology Co.,Ltd, ESP_FFE or Espressif Inc. You could do a: ping -t from the command line (Windows). If you then switch off the ECU, there will be no response if you have found the correct IP address. It is best to specify in the Router that you want to provide the MAC address of the ECU with a fixed IP address.
I get these kind of errors lately when the sun is down. And in the morning HA will not start to read the data. I have to restart the ECU every time. I did not have this issue before:
Using cached data from last successful communication from ECU. Invalid data error: Result on ‘Inverter data’ incorrect end signature ‘202’ != END data=b’xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa’
Seen more in the thread with this issue. What is a good fix for it? Haven’t found it yet. I run the ECU_R_1.3.16 firmware on the device.
Replace the number string with x’s as I am not sure it’s sensitive data. 
Which integration are you currently using? GitHub - ksheumaker/homeassistant-apsystems_ecur: Home Assistant custom component for local querying of APSystems ECU-R Solar System or GitHub - HAEdwin/homeassistant-apsystems_ecu_reader: Reader for APsystems ECU's or have you tried GitHub - HAEdwin/homeassistant-apsystems_ecu_proxy: A Home Assistant proxy integration for APsystems ECU-R and ECU-B micro-inverters
I use the GitHub - ksheumaker/homeassistant-apsystems_ecur: Home Assistant custom component for local querying of APSystems ECU-R Solar System integration.
Ran it for more than one year, without issues. It’s something from the last couple of week, that is suddenly is less stable. I run the latest HA.
Edit: I just see now that you have a new version. What version should I use for just reading amount of inverters online and get the current power produced?
So something has changed,… is it the ECU firmware? You might want to try my git as an alternative because this is the maintained version right now. See if it helps, but wait at least 10 minutes after an ECU reboot before trying to connect.
Haven’t done any updates on the ECU. Would not dare to. 
I just installed the APsystems ECU Reader package. I was able to connect to the ECU and see some info like the number of inverters and the lifetime energy. So that seems to work.
I will keep an eye out on it tomorrow. as the solar panels are not doing anything right now. It’s dark.
Great, notice that you’ll have to build an automation to trigger a smart-plug when the cache count reaches for example 5. There’s no query switch anymore.
Ah, thanks for letting me know. Will get on it.
One more question left. I notice that all inverters have an on/off switch. According to the older version of the software that I was using, it was not possible to turn off the inverters.
Is it actually possible now with this new version or is this still something that only works with the 2162x version of the ECU?
Unfortunately only for the 2162xxxx ECU-R models (ECU-R-Pro).
Ok, thanks.
Have something to think about then. Have seen the 2162x online. Would be great to be able to disable them in the future when prices go negative again.
Update: the new reader version of the software is working. I see the amount of inverters online and how much energy it’s producing.
The old software, that is still installed, isn’t doing anything. It’s still all on 0.
And the new version is down.
Logger: custom_components.apsystems_ecu_reader
Bron: helpers/update_coordinator.py:380
integratie: APsystems ECU Reader (documentatie, problemen)
Eerst voorgekomen: 07:56:07 (1 gebeurtenissen)
Laatst gelogd: 07:56:07
Unexpected error fetching apsystems_ecu_reader data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 281, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/apsystems_ecu_reader/__init__.py", line 147, in do_ecu_update
return await ecu.update(
^^^^^^^^^^^^^^^^^
...<3 lines>...
)
^
File "/config/custom_components/apsystems_ecu_reader/__init__.py", line 108, in update
data = await self.ecu.query_ecu(port_retries, show_graphs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/apsystems_ecu_reader/ecu_api.py", line 140, in query_ecu
_LOGGER.debug("Inverter raw data: %s", self.inverter_raw_data.hex())
^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'hex'
If you put the integration into debug mode, you’ll be able to see how the data looks like. Sounds like you’re receiving wrong data somehow.
I will put it in debug mode later today, when I am back home again. For now it seems stable. See the data coming in.
Oh, I thought it was not running because of you remark:
But if all runs well, there is no need to put it in debug mode.
1 Like
Getting the same error again as posted above. It ran fine for a while and just noticed that the sensors are offline. Same error in the log again.
To be more clear. I run the APSystems PV solar ECU 1.3.4 version to get the data. And I run the APsystems ECU Reader 2.2.3 version.
The older version is still up and running and pulling the data as expected. The “reader” has crashed three times so far today. It comes back up though. I do see a lot of notices in the logs:
“Update failure during occurred while querying inverter. Status is: incomplete inverter data received due to ECU recovery”.
It might even be that 2 integrations querying your ecu, makes the responses less reliable. The ecu isnt strong hardware and not up to the task of parallel querying. You could try to temporarly disbling old one and see if the reader gets stable that way.