Anyone using the deye/sunsynk inverter with batteries?
I searched the web for information on the solarman API capabilities but can’t find anything so far. Biggest question I have is if it possible to instruct the battery to charge and discharge through an api call.
Hello Skully!
Thanks for the method proposed but I have a problem I cannot get out.
At step 4, I get the following message:
{
“code”: “2101006”,
“msg”: “invalid param”,
“success”: false,
“requestId”: “ee42a0ebadbe7a10”
}
And I do not understand how to proceed. I have checked all the input proposed without success.
A question: DeviceSn is the serial number of the inverter or the logger?
I have tried both with the same result.
Any suggestion? Thanks in advance
Sincere apologies for my very late reply… been distracted with a building job that needed finishing before autumn turns to winter. I’m a bit ashamed to be honest that you asked for help and I didn’t quicker.
Oh no no its completely okay. Thanks to the delay I got to learn you can request update time decrease to 1 minute from 5-10 minutes (default) by emailing Solarman team. Its not real time but pretty close to it directly on Solarman app without any effort.
Let me try your provided configuration and get back with more questions!
Hmmm I am again getting this same error. This time no confusion regarding my id & key … Anyone else have the same? I’ve emailed support to confirm my API access is still OK.
@goancea, I’m very happy with this solution which obtains data locally from the solar datalogger, without having to use a cloud api and without having to readout the inverter with its specific modbus registers. Your solution works really well and I imagine it will be useful for many similar (rebranded) data loggers / wifi sticks: Solarman, Solis, Sofar, Omnik, AEG, Deye, etc!
I slightly tweaked some of the code, and also added in a “template sensor”, so that the solar power production can be added to the Home Assistant “Energy Dashboard”.
As a note to other users, of which you are probably already aware: “webdata_today_e” gives unreliable values which sometimes decrease throughout the day, which should not technically be possibly and does not match up with the other two variables, best to avoid using this variable.
I’ve also validated the above code and mechanism (curling data via webinterface of the solar datalogger) and it matches up very well with the power readings of my meter (my solar panels are alone on their own phase in my meter).
Is there a way to include the locally pulled data into the Home Assistant Energy dashboard, e.g. to display the hourly Solar production?
For pulling data via WLAN from the inverter, I’ve been using this HA integration:
However, in the Energy dashboard the bar chart for hourly Sorlar production starts off with a negative value in the morning.
The value of previous day total seems to be stored overnight. When the inverter starts up the next day, the value seems to be reset to zero by subtracting the previous day’s solar production.
Have not found a solution for this issue yet.
With a helper entitity (Utility meter) I could also not get it to work.
Maybe somebody has found a solution for this or has an idea?
Would like to avoid going over the Solarman cloud and prefer to do it based on locally pulled data (via LAN).
I have the exact problem like you. With an no name inverter and solarman logger with was older, everything worked perfect. No negative values in the morning or any other problems. But, I’ve changed my inverter with an INVT IMARS, witch has a newer solarman logger, and had the exact problems like you. So I was forced to don’t use the read data directly from logger method and to use the API method. Data are a little late that direct data collecting … but … at least is working correctly. I’ve tried also utility meter reset, calibrate … etc but no go. It seams that the software of the loggers are different and some of them are connecting to older solarman platform (the ones that are working ok with direct data reading solution ), and other to newer solarman platform (the ones that are giving bad values at start and at stop of the inverter). I could not find any solution to modify logger firmware also, I would like to try with an older firmware, but … no go also. So until someone find a good solution to get rid of those bad data at start and stop of the inverter … I will use API method.