Domoticz

Benneton wrote:HI Krizzz,

I still have no idea on how to get this done.
I know the ECU 3 has web interface and maybe there is a possibility to read data via this interface into Domotticz.
Seen some uses of JSON to read from web interface into Domoticz, but I ah a noob on programming.

Out of curiosity what firmware version is your ECU 3 running?
Mine is version 4.1

any input to make this happen is welcomed.

Benneton wrote:You can see this when you logon to the webinterface.
It is on home sections, it lists there all system info i.e.
ECU ID
Lifetime generation 2925.64 kWh
Last System Power 166 W
Generation of Current Day 0.29 kWh
Last Connection to website 2018-12-26 12:17:16
Number of Inverters 6
Last Number of Inverters Online 6
Current Software Version V4.1
Current Time Zone Europe/Amsterdam
ECU Eth0 Mac Address
ECU Wlan0 Mac Address
Inverter Comm. Signal Level

Bernard

PRB617 wrote:Connect the panels of a solar bank together, if there are more than one. They are usually wired in parallel to preserve the voltage of each panel, but you can also wire sets of them together in series to increase the voltage to conform to the voltage of the battery bank, if need be.
For more info click here

krizzz wrote: ↑Wednesday 28 August 2019 11:55 I found a solution which works quite well for me. Since the standard EMA app is really not sufficient. i decided to look for an options to download the data from my ECU to pvoutput. Appaerntly somebody uploaded a script for specific the APSystems ECU to upload to pvoutput. The link is below and I try to make a short installation guide.
https://github.com/willemstoker/aps-to-pvoutput

How to install?

First make an account @ PV output (https://pvoutput.org)

Than just created a new script within Domoticz/scripts/python:

Code: Select all

cd domoticz/scripts/python

Create script

Code: Select all

sudo nano apstopvoutput.py

- Copy code from https://github.com/willemstoker/aps-to- ... voutput.py and paste it into the apstopvoutput.py file

- change the things below in in the script. Leave the ' ' and replace the (for example) <ecuid> with the corresponding data

Code: Select all

ECU_ID = '<ecuid>'
PV_OUTPUT_SYSTEMID = '<systemid>'
PV_OUTPUT_APIKEY = '<apikey>'

you can find the ECU id in your app for example. The PV_OUTPUT_SYSTEMID and APIKEY you can find @ pvoutput.org

exit the file with Crtl-X and than save with Y(es) and confirm with enter

Than just follow the pvoutput guide (https://www.domoticz.com/wiki/Domoticz_and_PvOutput.org) to get the pvoutput data in your domoticz.

FireWizard wrote: ↑Wednesday 28 August 2019 14:36 Hi,

I understand the owners/users of the solar panels, that they want to have control over their own data. They paid for their system! Unfortunately the manufacturers/suppliers of the (micro) inverters do not understand this. Otherwise they should have documented an API, so that programmers can made their own interface to Home Automation systems, such as Domoticz, Home Assistant or OpenHab.
It is pity, but it is the way it is.

However, what I read so far it looks not too difficult.

The options to use PVOutput as an intermediate station is possible. But again you make use of a party, that is not under your control.
It should be possible without any external party.

I own solar panels, equipped with Enphase IQ7+ micro-inverters. They do not provide an fully equipped API either. They even claim that it is not possible to read the individual power production of each panel. However some posts were available and combining each other made it possible to get the information per panel in Domoticz. See example below.


Screenshot_solar-panels_roofplan_small.png

If this is your intention, you can follow these steps in order to install a MQTT broker and Node Red, if you have not done so.

1. Install Mosquitto MQTT broker. This can be done on the same device as Domoticz is running.
There are many guidelines on the Internet available.
E.g. See: https://appcodelabs.com/introduction-to ... spberry-pi
Test your MQTT broker, so that you know that it is working properly. Install also mosquitto-clients.

Test that you can connect with your tool to the Mosquitto broker. Default port is 1883.

Do not forget to secure your broker with at least username/password.

2. Install in Domoticz the MQTT Client Gateway with LAN interface and fill in the required fields
See:


MQTT Domoticz.png


Check that you can communicate between Domoticz and the MQTT Broker.
Subscribe with any client to domoticz/out and you will see various messages passing.

Install Node Red. This can be done on the same device as Domoticz is running.

I have installed NodeJS and Node-RED according to this guide:
NodeJS: https://www.instructables.com/id/Instal ... spberry-Pi
Node-RED: https://nodered.org/docs/getting-started/installation

A tool, I use, on the desktop is MQTTfx. (See https://mqttfx.jensd.de/) But there are many others.

Test everything in order to be sure that you can communicate between Domoticz, Mosquitto and Node Red.
Connect the (default) Node Red MQTT in node to domoticz/out and connect a debug node and chech that you can see the topics published by Domoticz.

Both the script used for the PV Output solution and the curl points to: http://api.apsystemsema.com:8073/apsema ... tPowerInfo

If you use this URL in your favorite browser what do you see?
In addition I found the following link: https://community.openenergymonitor.org ... rters/3491

It might be possible to use that solution "out of the box", but maybe you can use the output of the URL.
Can you publish the output of http://api.apsystemsema.com:8073/apsema ... tPowerInfo?

Regards