hello,
after adding battery 2 everything works perfectly,
only there is an error in the data “discharge battery 2”,
this happens when this battery comes into standby i think.
yeah , I got some unlimited value , I think it depends on the BMS, also see the same on solaredge and don’t see this on my LG batt. Will try to suppress it.
Got Huawei emma working and it is fast , not like s-dongle . Also will try to do some write tests and then will make a new device for emma.
only requirement fow now is to disable TLS on modbus.
Hello everyone
I am new to the world of photovoltaics and also rather new (since 1.5 years) owner of a Homey Pro 2023. I have abolished a photovoltaic system and wonder how I can integrate it into Homey. The following items are installed:
-
Solar Panels: Jinko Tiger Neo JKM440N-54HL4R-V - (BF, R30, EVO2)
-
Inverter: Huawei SUN2000-10KTL-M1
-
Performance optimizer: Huawei SUN2000-450W-P2
-
Huawei Smart Power Sensor DTSU666-H 100A/40mA
-
Smart Dongle WLAN- FE
Option, not yet installed:
- Solar Manager Gateway
=> Do I absolutely need this Solar Manager Gateway for the integration in Homey?
=> or what is the advantage if I buy and install the Solar Manager Gateway?
Now my questions:
-
Which of the devices listed above must then communicate with Homey, the inverter, right?
-
which Homey apps do I need or is the SolarEdge + Growatt TCP modbus app sufficient?
What else do IOS app or account do I need? (I have the FusionSolar app and a corresponding account)
I am also happy to provide more information if necessary and thank you in advance for the feedback.
hey ,
s-dongle should be enough to get started with this app. enable modbus and connect to this port.
Good morning Edwin
Thank you very much for your feedback, so far everything has worked out and I can see the data in Homey.
If I now also want to control the photovoltaics, do I need more components than the ones I listed?
hey,
so it seems that huawei allows control but you should not be on wifi (will do some auth) see Huawei Inverter + Battery. Flow cards "Then" not available? · Issue #89 · biemond/solaredge.modbus · GitHub
the plan is to add it back.
Hi, I have tried to see if there are any post related to my issue.
I’m new to Homey Pro and have developed an advanced flow that read data from my inverter (Sungrow SH10RT).
I have found out that the app stops updateing data and I cannot understand why.
The longest time span I have had reading data continuesly is 3,5 hours.
But it is very often that the app stops updating just after 3-5 min.
My flow is dependent on getting data related to solar power and load yield.
Without this data my flow do not work.
When I restart the app or restart Homey Pro, then the data is updated again.
I do not have to restart the inverter.
What could be the reson behind this issue?
I have created a case in the development page, but would like to see if someone here could help me to pinpoint the issue and find a solution to the problem.
UPDATE:
I made som changes in the advanced flow and now the app seems to be working.
It might be that the flow created a conflict that stopped the app from receive more data from the inverter. I will continue monitoring this and see if the issue might come back.
Hi,
I’m not sure if i post the correctly, but hope if its ok.
Often when I change a flow card, like ‘Battery 1st’ the app itself is not been updated with the value changes, but the inverter have received the information.
I have waited for 10 min to see if anything happened, but not. Sometimes it helps to write twice.
Is there a reason for that, or a way where I can ensure that the information in the app is updated?
All other read values in the the app is updating.
My Inverter is a Growatt SPH
Hi Peav,
I have similar experiences with the app (the tiles not always updating), with SPH and also with XL Growatt. To be honest, it happens frequently that also other tiles are not updating, they have nothing to do with the Solar App. Homey insights does update always.
Regarding the priority changes on a SPH I can share you that my SPH does not like this at all, it works, but I experienced strange inverter behaviours, so that I stopped doing (changing prio modes within flows.
With the XH I set 2 different prios over 24h, allowing some settings to export with remaining battery power on dynamically most expensive hours, but I do not change the prio modes.
Phil
EDIT @Edwin_Biemond, as I remembered, the prio settings I tested we did for the XL. Is the SPH different in register references as a root cause for the problems as written by @peav ?
hey,
what is the flow action or trigger you used ? triggers are mostly auto generated by homey. actions can be, it is rejected or so . can you send me a report just after you do this action. maybe it is rejected or so.
thanks Edwin
@Peav need to answer that one. We tested the settings for the app with this:
And it is a similar flow card I use, where I see the issues…from time to time.
Thanks for the answer.
I’m using the ‘Battery 1.st Timeslot 1’ flow card, where I enable/disable it. I’m not using the ‘Priority Mode’ flow card. I tried once, With no success.
/Poul-Erik
I do not think it’s rejected, because I triggered by ‘Test from here’ and do not see any errors. I’ll keep an eye on it, and send you a report if its happen again.
The ‘normal’ action to change the flow card have just appear, and here everything is updated. Maybe it’s only if I do the ‘Test from here’ triggering??
/Poul-Erik
Hi @Edwin_Biemond ,
I’ve successfully connected the Modbus to my Growatt MOD 5000TL3-XH (BP) with an APX Battery system, and most things are working well. However, I’m facing an issue I need help with.
The battery capacity isn’t large enough to meet my complete energy needs, so I want to prevent the system from discharging the battery except during the most expensive hours of my dynamic energy contract. I tried setting the “Battery Minimum Capacity” to 100%, assuming it would prevent the battery from discharging below that level, but it doesn’t seem to work as expected. Could you advise on how to achieve this?
Additionally, I’m using the “Power by the Hour” app to optimize charging and discharging based on dynamic energy rates. The developer (@Gruijter) can integrate this feature, but he needs the following battery capabilities: SoC (State of Charge - battery percentage) and power in/out data. More information is available here: Power by the Hour app integration.
Can you provide these capabilities?
Hi Satoer,
I have Growatt_MIN-3600-TL-XH. as from a data perspective they should be the same.
As long as I stay in Priority LOAD, I switch the min batt capacity also in the boiler module,
as soon as the 4 less expensive hours arrive AND the price is below 0,0 I switch the battery min capacity to the level of capacity, blocking the battery pack to provide power to the boiler and using the free of charge grid power. If there is enough battery capacity (another module) and the prices are low, the boiler is permitted to heat-up.
It functions flawlessly.
[EDIT] Note that if the minimum batt capacity is reached (or set and reached) and eventhough the priority is LOAD, growatt allows to use GRID power to restore the minimum batt capacity !!
With this in mind, you should have another look at the value of 100%.
are these measure_battery or battery not ok solaredge.modbus/drivers/growattwithbatt_tl/driver.compose.json at main · biemond/solaredge.modbus · GitHub?
plus these
“measure_power”,
“measure_power.input”,
“measure_power.gridoutput”,
“measure_power.pv1input”,
“measure_power.pv2input”,
“measure_power.houseload”,
@Phil_Bro and @Edwin_Biemond , thanks for the reply.
Phil, I’m trying to understand what I have been doing wrong to prevent the battery discharging. I have the priority set to “Load First,” and the “Batt AC Charge switch” (grid charging) is off. My understanding is that if I set the “Battery Minimum Capacity” to 100%, the battery should neither discharge nor charge from the grid right? Even though “Battery Minimum Capacity” is not #Battery like your example. Thanks for the screenshot, I shall experiment further according to your example (Set “Battery Minimum Capacity” to the current capacity)
Edwin, I don’t know. I have passed your answer to the PBTH developer.
Hi,
We had been testing this over and over and to my suprise, if prio is set to load and the batt min capacity is reached or some % below that value, the inverter starts to pump it up using AC power. This is proven many times. So if you set the min batt capacity to 100% and the real batt capacity is f.i. 15%, it will start charging upto 100% since that is the minimum the inverter has been told to keep. It is chinese logic, but for sure I have seen this many times. This is why I use the setting as per screenshot and not above the actual batt capacity.
So test this in the evening, or no solar power. Set the the min batt cap 2% above the actual and prio LOAD on. I have grid charging always OFF. I did some testing to charge battery when pricing is below 0, but since this occurs some times per year, I see no advantages. Additionally, if set to ON and for any reason the domotics are dead … it keeps on charging with GRID power. Not-done.