New project proposal: Integrating inverters and various energy meters into IAMMETER
We are committed to advancing the 'Integrate the data of the Solar inverter to IAMMETER cloud' project.
If you currently utilize a solar inverter and are considering transitioning its monitoring system from the official portal to IAMMETER. We kindly request the following information:
The brand and specific model of your solar inverter.
The local protocol it operates on (Modbus/RTU or Modbus/TCP) or the availability of a local API for the device.
The API interface details of the official portal (if they provide it)
Your cooperation in providing the above information will greatly assist us in implementing the most suitable integration method for your solar inverter's transition to IAMMETER
There are three potential approaches we can undertake:
Extracting data from the official portal's API (if provided) and establishing a bridge to transmit this data to IAMMETER.
Utilizing open-source hardware, such as ESP32, to locally retrieve data (if the inverter supports a local protocol like Modbus/RTU or Modbus/TCP) and subsequently uploading this data to IAMMETER. This approach will be developed in an open-source capacity.
Utilize either Home Assistant (HA) or Node-RED as an intermediary to facilitate integration. Create an integration within Home Assistant(or a corresponding node in Node-RED). This setup will allow us to access and extract data from the inverter, supported by either Home Assistant or Node-RED, and subsequently upload this data to IAMMETER-cloud.
Please let me know your preferred mode among the three options.
It's crucial to highlight that while the initial focus is on the inverter, we aim to encompass all devices related to energy measurement, including energy meters from different brands.We aim to develop a method that enables all energy measurement devices to seamlessly upload their data to IAMMETER-cloud. Your valuable insights and suggestions regarding this expanded scope are highly anticipated and deeply valued.
Estou bastante interessad nessa possibilidade, uma vez que atualmente tenho que consultar 3 portais diferentes para ver o balanço de energia do meu site.
Tenho o IAMMETER, o Solarman para o inversor SUN2000G3 e em modo local inversor MPI3000WPLUS via Esp32.
Lembro que sou um engenheiro eletronico aposentado e no caso do inversor MPI3000WPLUS, que tem protocolo fechado, desenvolvi meu proprio drive de comunicação serial usando um Esp32.
Estou fortemente inclinado para o protocolo Modbus/RTU ou Modbus/TCP.
Deixe-me saber, se precisar de mais informações.
1. Goodwe SDT G2 15kw Ongrid (3 phase) and Deye 8kw Low voltage hybrid (single phase).
2. Will confirm and get back.
3. Both have their own portals which are very basic, Ive never heard of them providing their portals api. I logon using "Sems Portal" app for Goodwe and "SolarMan Smart" for deye. Both do have web logins as well.
I know Rasberri Pi can be used with Deye to grab realtime data, not sure about goodwe.
1. Huawei SUN2000-8KTL-M1
2. Modbus TCP via SDongleA-05 (Modbus Interface Definitions includes registers for inverter, battery and smart meter)
Hi, I am using the Growatt 5000 TL3-S inverter. It uses a wifi dongle to upload data directly to their cloud (https://server.growatt.com/)
I found a link to their API integration but I am not sure how up to date that is. https://growatt.pl/wp-content/uploads/2020/01/Growatt-Server-API-Guide.pdf
So the preferred option would be to extract the data directly from their database through their API.
How would you store the data and how do you plan to display and integrate the data from the inverter on your platform? I am actually already tracking the PV production with a three phase meter from you. So would it not be duplicated data? Or is the idea, that once you can import the data from the inverter, I wouldn't need the three phase meter anymore to read the same data? And the energy data from the inverter itself is probably also a but mofe accurate?
Please let me know how you plan to implement that feature exactly.
Thank you and kind regards,
Martin
I also think that cloud-to-cloud communication would be the most user-friendly solution as many people do not want to run and administer a raspberry pi. Cycle-times could be lower locally though. I for example like how clever-pv does it. Everything is via cloud, also the triggering of a Shelly relay.
For me personally, I do have a raspberry pi, running my own excess energy task. I use Modbus TCP to access all data from the Huawei PV, also including battery charging/discharging power and smart meter import/export. I also do calculations based on the readings of the Huawei and IAMMETER smart meters.
Hi Martin:
"How would you store the data and how do you plan to display and integrate the data from the inverter on your platform? I am actually already tracking the PV production with a three phase meter from you."
If you have already installed two energy meters, one on the grid and one on the inverter side, you may not need to consider this option. However, this idea is specifically aimed at customers who have only purchased and installed a single energy meter on the grid side. These customers wish to monitor both the grid and solar aspects through IAMMETER, while also utilizing an existing official solar monitoring service.
In scenarios where purchasing an additional energy meter for the inverter side might seem redundant due to the existing official solar monitoring system, we propose a solution. Our plan involves enabling customers to directly retrieve data from their official solar monitoring system and transmit it to IAMMETER-cloud. This feature eliminates the need to buy another energy meter, offering a more cost-effective solution. Instead, customers would only need to subscribe to this feature, ensuring a more efficient and economical approach.
BR
Laoliu
Hi Daniel:
Thanks for sharing! Cloud sounds great to us too—it's so user-friendly. We're thinking of backing both cloud and HA bridge modes at the same time.
I'll dive into checking out 'clever-pv,' the thing you mentioned. And about triggering a Shelly relay through the cloud, that's interesting! I'll definitely take a look into that.
Any other cool gadgets like the Shelly relay that you think we should explore for IAMMETER? We're open to gathering ideas for our actuator proposal!
BR
Laoliu
Please refer to https://imeter.club/topic/558
Hi,
Regarding of uploading the inverter data to IAMMETER-Cloud, I have a concern: For monitoring all the plants, EV & Batteries we have (close to 120), it will be imposible with the trafic restrictions you have (Real time, alarms and history).
Right now we have 2 IAMMETERs testing, one WEM3080 with an EV Charger and a WEB3080T in a PV system. and we have been blocked several times for a high number of hits on the endpoints.
I hope you can allow more hits to the database.
Best regards
Could you please let us know how you determined this (i.e., that you were blocked due to a high number of requests to the endpoints)?
If possible, providing a snapshot would help us diagnose the issue more effectively.
Additionally, please let us know how you operate when the block occurs.
Normally, data uploads from the energy meter should not be blocked. Since the firmware sets the upload interval to IAMMETER-Cloud at a fixed 1-minute interval, we do not impose any restrictions on this operation.
However, we do have rate limitations on other API endpoints listed here:
https://www.iammeter.com/docs/system-api
When you experienced the block, were you also making frequent requests to the cloud API at the same time?
"For monitoring all the plants, EV & Batteries we have (close to 120), it will be imposible with the trafic restrictions you have (Real time, alarms and history)."
We have customers with more than 500+ plants under a single account and have never encountered any issues. Some of our cloud APIs are specifically designed to help them manage their devices more efficiently.
So please don't worry—120 plants is not considered a large number. Let's first confirm the issue you're facing so we can assist you effectively.
Thank you for your replay,
The blocking is with the API calls no with the meter, the meter works perfectly and updates the info every 5 minutes.
Our Operations Center, which is in charge of monitoring the devices, scans all the devices every 15 minutes (some every 5 minutes) and highlights any service malfunction, they start a remote diagnostic checking different variables on the devices (Internet, Volts, Amperage, DC and AC, etc.) if they can not solve the issue, sends an engineer to visit the site and try to solve the issue ASAP. (Our core business is selling energy)
The problem comes when we scan the system and start hitting different endpoints, the worst one is the alarms (- offlineAnalysis - energy interruption) which according with https://www.iammeter.com/docs/system-api we can only request 5 times in a day, and if we scan every 15 minutes, after 1 hour and a half, we star getting messages then we have to wait 24 hours. It also happen with meterdata.
Thanks in advance for your time and help.
Best regards,
Hi,
The Offline Analysis API is designed to analyze offline occurrences within a specific time period, rather than to check whether a device is currently online or offline.
For example, it helps you determine how many times the energy meter went offline in the past week. Since this is more of a summary report, we have limited its usage to five calls per day, as frequent reporting is unnecessary.
If you need to check whether the energy meter is currently offline, please use this API:
🔗 Get the Latest Uploading Data and UTC Time
You can compare the latest timestamp with the current time. If the difference exceeds 1 minute, the meter may be offline.
Alternatively, you can enable the offline alarm feature:
🔗 Energy Meter Offline Alarm
Let us know if you need further assistance!
In addition, if you have any suggestions for IAMMETER, please feel free to let us know (welcome to start a new thread on our forum).
We are always open to discussion. If your suggestion is valuable and beneficial to most customers, we are willing to include it in our roadmap and prioritize it for future upgrades.
Best Regards