how to add APSystems ECU-3 solar inverter monitor

[lsp242]

From device set in Domoticz ?

Can I change the devices in Domoticz the same idx to another kind?

[FireWizard]

@lsp24,

Just change the same device to "From Device" and test.

Regards

[lsp242]

Still domoticz crashes direct when I connect and manually trigger the output

Thank for thinking with me..

Now i've solar and the new update... it won't crash..
but 3 panels stay on 0kW

IDX 237 IDX238 IDX239

Code: Select all

26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 232, nvalue: 0, svalue: "94;0" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 246, nvalue: 0, svalue: "236" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 233, nvalue: 0, svalue: "74;0" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 247, nvalue: 0, svalue: "236" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 258, nvalue: 0, svalue: "50.1" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 273, nvalue: 0, svalue: "19" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 234, nvalue: 0, svalue: "133;0" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 248, nvalue: 0, svalue: "236" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 235, nvalue: 0, svalue: "65;0" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 249, nvalue: 0, svalue: "236" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 259, nvalue: 0, svalue: "50.1" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 272, nvalue: 0, svalue: "19" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
[b]{ command: "udevice", idx: 238, nvalue: 0, svalue: "64;0" }[/b]
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 252, nvalue: 0, svalue: "237" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
[b]{ command: "udevice", idx: 239, nvalue: 0, svalue: "113;0" }[/b]
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 253, nvalue: 0, svalue: "237" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 261, nvalue: 0, svalue: "50.1" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 270, nvalue: 0, svalue: "20" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 240, nvalue: 0, svalue: "63;0" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 254, nvalue: 0, svalue: "236" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 241, nvalue: 0, svalue: "71;0" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 255, nvalue: 0, svalue: "236" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 262, nvalue: 0, svalue: "50.0" }
26-3-2021 09:35:26node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 269, nvalue: 0, svalue: "20" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 228, nvalue: 0, svalue: "134;0" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 242, nvalue: 0, svalue: "236" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 229, nvalue: 0, svalue: "75;0" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 243, nvalue: 0, svalue: "236" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 256, nvalue: 0, svalue: "50.1" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 275, nvalue: 0, svalue: "19" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 230, nvalue: 0, svalue: "136;0" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 244, nvalue: 0, svalue: "237" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 231, nvalue: 0, svalue: "75;0" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 245, nvalue: 0, svalue: "237" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 257, nvalue: 0, svalue: "50.0" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 274, nvalue: 0, svalue: "19" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 236, nvalue: 0, svalue: "135;0" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 250, nvalue: 0, svalue: "237" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
[b]{ command: "udevice", idx: 237, nvalue: 0, svalue: "75;0" }[/b]
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 251, nvalue: 0, svalue: "237" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 260, nvalue: 0, svalue: "50.1" }
26-3-2021 09:35:27node: Domoticz In
msg.payload : Object
{ command: "udevice", idx: 271, nvalue: 0, svalue: "18" }

[lsp242]

Update @firewizard

Get a fault in domoticz:

Code: Select all

2021-03-26 09:45:06.320 Error: MainWorker::UpdateDevice exception occurred : 'stof'
2021-03-26 09:45:06.320 Error: MQTT: Problem updating sensor (check idx, hardware enabled)
2021-03-26 09:45:06.527 Error: MainWorker::UpdateDevice exception occurred : 'stof'
2021-03-26 09:45:06.527 Error: MQTT: Problem updating sensor (check idx, hardware enabled)
2021-03-26 09:45:07.065 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":254,"nvalue":0,"svalue":"238"}
2021-03-26 09:45:07.175 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":241,"nvalue":0,"svalue":"71;0"}
2021-03-26 09:45:07.285 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":255,"nvalue":0,"svalue":"238"}
2021-03-26 09:45:07.394 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":262,"nvalue":0,"svalue":"50.0"}
2021-03-26 09:45:07.503 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":269,"nvalue":0,"svalue":"21"}
2021-03-26 09:45:07.613 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":228,"nvalue":0,"svalue":"141;0"}
2021-03-26 09:45:07.725 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":242,"nvalue":0,"svalue":"236"}
2021-03-26 09:45:07.834 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":229,"nvalue":0,"svalue":"85;0"}
2021-03-26 09:45:07.944 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":243,"nvalue":0,"svalue":"236"}
2021-03-26 09:45:08.053 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":256,"nvalue":0,"svalue":"50.1"}
2021-03-26 09:45:08.164 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":275,"nvalue":0,"svalue":"20"}
2021-03-26 09:45:08.274 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":230,"nvalue":0,"svalue":"142;0"}
2021-03-26 09:45:08.386 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":244,"nvalue":0,"svalue":"237"}
2021-03-26 09:45:08.495 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":231,"nvalue":0,"svalue":"85;0"}
2021-03-26 09:45:08.607 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":245,"nvalue":0,"svalue":"237"}
2021-03-26 09:45:08.716 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":257,"nvalue":0,"svalue":"50.0"}
2021-03-26 09:45:08.826 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":274,"nvalue":0,"svalue":"20"}
2021-03-26 09:45:08.936 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":236,"nvalue":0,"svalue":"141;0"}
2021-03-26 09:45:09.047 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":250,"nvalue":0,"svalue":"238"}
2021-03-26 09:45:09.157 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":237,"nvalue":0,"svalue":"84;0"}
2021-03-26 09:45:09.258 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":251,"nvalue":0,"svalue":"238"}
2021-03-26 09:45:09.369 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":260,"nvalue":0,"svalue":"50.0"}
2021-03-26 09:45:09.478 MQTT: Topic: domoticz/in, Message: {"command":"udevice","idx":271,"nvalue":0,"svalue":"19"}

I put those 3 to "from device" and they work ---> the rest is on "computed"
Very strange

[FireWizard]

Hi, @lsp242

Do the following:

1. Update to v13119
2. Set all your Electricity (Instant + Counter) to "Computed" instead of "From device".
3, Test

If it is correct, your problems should be fixed.

Regards

[lsp242]

Everything is now running…

All on “computed”
Had some negative readings —-> solved with empty cache.

Thank for your help..

[FireWizard]

@lsp242,

I'm glad it is working again and I consider this issue as solved.

You were really unlucky that you installed after the crash a latest version (between 13088 and 13118) that had issues with the Electricity sensor.

Regards

[daanvdl]

I wrote this python script for use with my APS ECU-R.
https://github.com/daanvdl/-ecu2pvoutput

(I dont own a ECU-C, so i can't confirm this will work well with the APS ECU-C)

It scrapes the HTML form on the local webinterface, sum the panel values,collects voltages and inverter temperture and push the data to a pvoutput account.

[Benneton]

Hi,

Since a week or so I have issues with the ECU-3. The device is not reporting anymore.
After powercycle same issue, interface can be reached, solar installation working but no reporting from the ECU-3.
When I looked in my pi-hole login I noticed that the ECU-3 is trying to connect to a AP systems website:
https://ecu.apsystemsema.com/ (not blocked in Pi-hole)
When I navigate to this site in my browser I get a message:

"APsystems EMA 目前正在维护。系统将于2021年3月27日下午6:00点恢复,请稍后登录。
The APsystems EMA portal is currently down for scheduled maintenance. The portal will be available at 6:00 PM on March 27, 2021 (Beijing Time). Thank you for your patience. Please note that your systems will continue to operate normally during this downtime."

It appears that (for now) that this ECU-3 to work locally needs a connection to AP systems. I hope this is not true as when I bought this I asked for a system which does not need remote connection to work and share data with their platform

Any ECU-3 user here that has issues too, or am I just unlucky and has part of my device gone dead .

Thank you,
Bernard

[lsp242]

@bernard

No issue here with ECU-3 - i scrape on the local ip and that works fine!

I know for sure that is is connected to the servers from AP-systems.. because when you go to: https://apsystemsema.com/ema/logoutEMA.action and log into your account you will have all the information about your system there..

[Benneton]

Hi,

Thank you for this!
I do not have an account and preferably would have no home calling from the ECU-3, that is why the integration in Domoticz started.
Then I need to check why it is not working as it should.

Just one other question, which firmware version is your ECU-3 running on?
Mine is: Current Software Version V4.1

Kind regards,
Bernard

[lsp242]

@Bernard
I can't check my software version right now, it isn't given in the app..
have to check when i am home.

but i'm pretty sure to be on 4.1

[FireWizard]

Hello @Benneton and @lsp242,

Reading your posts, I conclude that it is not related to the web scraping of the local website.
I assume you can go to the webpage, but as I understand, Bernards website is not updated any more.
Strange, as you both run software version 4.1.

Perhaps, because you don't have an account created.

This has no relation with the solution we created in Node Red to Domoticz.
So, there is not much I can do for you.

Regards

[lsp242]

@fireWizard

scraping the website on the ECU-3 local IP works fine.. so you are right this is no problem.

i don't know if the connection to APsystems is needed, because before it works @bernard
first thing i should check if the ip in node red is the right one
second maybe APsystems changed the routines and do you need a account... (account for me is made by the installer of the solar panels)

[Benneton]

Hi Firewizard, lsp242,

No scraping is working fine, no issues at all.
Problem is my ECU-3. Not sure what has happened worked until 02/05/2021, then no data on ECU-3 page. did a power-cycle of the ECU-3 need to start somewhere
This did not resolve issue, checked network that is fine, moved it from switch to modem port to rule out local network, no change. Then yesterday evening I had some data again ?!?
looking at the web interface of the ECU-3 I noticed:
Last Connection to website 2021-05-07 20:58:41
Previous it was a time stamp on May second.
I am not sure what it means, but is not last time locally accessed via web interface the ECU-3.
I also noticed that the ECU-3 is trying to connect to https://ecu.apsystemsema.com/ a site which is down when checked web browser.
So my guess is that the ECU-3 needs to connect to AP systems to provide me data locally in the web interface, which we scrape.
I checked if I still generate power, which is the case, counter for 'teruglevering' is still increasing.

As last resort I tried this morning to reset the complete installation, just to be sure and force ECU-3 and converters to connect up again.
Still same result, no data in the ECU-3

I am a bit out of ideas on how to fix. As confirmed by lsp242 the system is working as his ECO-3 is working as should.
To me it appears that the ECU-3 is working, but connectivity for what ever reason is not good. I will try to setup different DNS. Already removed hub via PI-Hole and resolving is now done via XS4ALL DNS, will try Google ones just to rule out that bit as well.

I am open for ideas
Thanks for the support!
Bernard

[lsp242]

How did you check the site the ecu-3 wants to connect to.

I didn’t do the installation, they are installed by a company who made the connections and my login. This also works for the app from apsystems.

Are the inverters set when you look into the ip from ecu-3?
I added them manually again when I got at first many problems.

The strange thing it worked at your side..
I’ve another url to check online the data with my account..

[Benneton]

I found this out when I looked through the PI-hole loging.
The inverters are set in the ECU-3, basically I did not change anything and it stopped working on may second and Yesterday it did get some connection.

Maybe it is as you say and to make it work you need an account at AP Systems? Hope not as I hate stuff that requires this kind of remote accounts at firms, it should work standalone, without an internet connection.

[Benneton]

Strange, see this afternoon some data again.
Last System Power 417 W
Generation of Current Day 3.18 kWh
Last Connection to website 2021-05-08 14:42:44
Number of Inverters 6
Last Number of Inverters Online 6

When I look at realtime data I see:
Reporting Time: 2021-05-08 13:59:54
refresh at 18:20 from my browser...

The more I think on the less I understand it.

[lsp242]

This is very strange

[Benneton]

It is getting more weird, I now have observed that every evening around 23:00 the device has a successful connection:
Last Connection to website 2021-05-20 22:55:49
But no data in the ECU, a few days 1 or 2 connections see picture:


Also noticed when saving chart data is not local again, but comes from:
http://export.highcharts.com

I was sold the ECU as a local device to monitor and track my APS Solar power system. I now believe the ECU box is no more than an interface to a remote third party database and services. Not happy with as it makes solving this issue hard, no reply from APS.

As last resort I will create an account on the APS monitoring portal to check if this is account related....