Tsa

WOW! Wonder if you get R2000 off your next Pylontech battery with that!

Howdy guys Newb on the subject, so excuse me if I am getting the terms\use wrong. Has anyone played with getting MQTT messages from Growatt inverter to a MQTT broker to work yet? What did you use? Please share you setup and software used. TIA

Glad everyone is taking this up with them. @charlvnk@charlvnk who is the local importer? Guys also keep in mind that as soon as you set 05 to Li the BMS takes over and your bulk/float charge and also setting 02 and 11(I think) . 02 and 11 control the current for charging and this also gets managed by the BMS and will fluctuate as the BMS sees fit.

Unfortunately there is no SUB setting on Growatt, but I know the Mecer\Axpert? ones have it from what I have seen on the forum.

@willietes Oh no, that's not good news. I am however happy that I'm not the only one, so points to an issue somewhere and still wondering if this is not a FW issue. The whole thing of us losing connection to the server, some settings not taking effect (beep program 15) and this battery tripping issue. I have changed my host\master to a different battery in my stack and monitoring. So far so good. So you basically need SUB setting for 01 like the Mecer's have it seems. Only when SOL and UTI isn't available, only then run BAT. Might be worth raising this with Mahone as a feature request. Wondering if setting your Back to battery (13) very high would assist with minimising batter usage? Not sure.

Well it was fun while it lasted... nearly 48hours later and my data is gone again at 15:35. Graph for 09/04 is totally screwed, but good thing I built that extra out building to house all my batteries......LOL 🤣 SOC graph is correct though.

I keep mine on Li, inverter and BMS comms is still 100% so it does what it needs to do. Mine still going string since 17:35 yesterday. So yes I agree with you that it would be a per inverter (ie firmware) issue as if it was a server issue we would all be having the same data drop at the same time. What will be interesting to see if mine again, as before, works fine until the batteries reach 99/100% and then start to auto discharge. Usually during this discharge cycle to 95% my data drop happens.

Lekka! Now THIS is what I am talking about! Very nice! I have very similar requirements as to your automation points noted. Please keep us posted on the progress.

So it seems around 17:35 yesterday my data started returning, after a long absence, and has been running fine since. Just wondering, if this was a Growatt server issue, should we all not be seeing the same issue at the same time? That's IF we all connect to the same server on their end.

My worry as well. Thing is the batteries were patched and new boards put in, so I was hoping that resolved it. I just now need to confirm if it is the same error codes popping up. Then try and find out who will be taking ownership of resolving it. The importers, distributor\ installer. The latter being the ones who have said to put it in USE mode.

@Mark R What does your PV setup look like? What is your capacity? Hehe, yip and today doesn't look any better either

Just for everyone's reference who finds this at some point, we are discussing this specific issue here.. https://powerforum.co.za/topic/5535-growatt-data-missing/

My dreaded power tripping on setting Li(05) has re-appeared. So now I am wondering if anyone else still has the tripping issue post these fixes. Mine was running perfectly after the battery FW and board fix, probably close to 2 weeks, and then all of a sudden it reappeared. Twice in 24hours. I just need to catch it during the day so that I can confirm the warning codes and if it is again warning 04 and 20. The other morning it tripped at 00:35! Power to house off for a few seconds, inverter beeping, and then everything came back on.

Thats good to know. I actually also saw 500 error on my web login earlier, but had it open so not sure when it happened. I hope you are also sending these updates to Mahone. The quicker they get all the feedback from as many sources as possible, the better chance we have of getting it fixed.

@charlvnk Agreed 100%! Yip Andy came to do my battery FW upgrade and PC board replacement just before lockdown started. So now I am wondering if anyone else still has the tripping issue post these fixes. Mine was running perfectly after the FW and board fix, probably close to 2 weeks, and then all of a sudden it reappeared. Twice in 24hours. Ah yes, OK I also updated this. This is the FW specific to the BMS. Sorry I though you were referring to some software to be able to interrogate the Dyness batteries. Yip painful, I think now after weeks of raising this with Mahone, and now that you guys have also started noting this, he eventually "understands" what I am referring to. . R&D team need to sort out these bugs asap and release new FW update. Well at least we can update it ourselves vs having to have on site visit, which will not happen now with lockdown. Dont think it is related to comms as I can see my wifi data logger connected to 47.91.67.66 on my router and using the same ports the app/web indicate the datalogger using at that time. A traceroute to 47.91.67.66 also end up at server.growatt.com so all fine there when testing this in the time that I have no data.

Hmmm not sure about that one. You 100% sure this doesn't fluctuate? I know you cant change that setting when BMS is managing the batteries, so could it be that every time you have checked it is on 32A at that moment as that is what the BMS has set it to? What is the Watts reading for charging the batteries at that time?

@Mark R I will try answer based on what I have configured. My idea with my setup also being as independent from Eskom as possible, although not always possible. When you have your inverter and battery comms setup correctly, the BMS takes over all charge/discharge operations. Thus setting 02 and 11 cant be changed, these fluctuate as the BMS decides how much current it needs from the inverter during charging. My setting 14 is currently set to CSO. IF during the early morning, usually just before sunrise, my batteries get to 20% SOC, grid will automatically kick in. This due to SBU setting(01). I have set my "back to battery"(setting 13) as 50% (think this is the default 95% you are seeing). So in the above case where my batteries reached 20% and grid kicked in, my load will be covered by grid and PV (when it comes online) will start charging the batteries. This due to setting 14. PV is now dedicated to only charge batteries and grid only handles the load. This will be the case until batteries reach 50%(setting 13) where after PV will take over the load (IF there is enough to handle the load!). Any dip in PV will see the batteries being used to make up the shortfall to continue covering the load. Any excess from PV, which now handles the load, will go to charging the batteries up to 100% as well. Hope this makes sense, but in short, your setting 13 will need to be lowered for you to release the PV from charging batteries only.

@charlvnkToday again I lost data on my app/web. When I saw it, data stopped reporting about 2hours prior. I changed program 05 to USE (only thing I changed) and 5mins later I had data again. I then changed it back to Li and continued having data as normal. The trend I am seeing happening is that when my batteries get to 99/100% charge via PV and then automatically take the load and start discharging, it is sometime during this phase that the data stream is lost. Might be too early to say, but seems to happening more and more during that phase, but will have to monitor more to confirm. I will update Mahone with these findings and hopefully R&D can sort this out asap. On his suggestion I have now switched off the inverter, no power sources are connected and it is totally off and will leave it now for the whole night so that it can properly discharge. My dreaded power tripping on setting Li(05) has also re-appeared and hoping they can also resolve this in a firmware update. I just need to catch it during the day so that I can confirm the warning codes and if it is again warning 04 and 20. This morning it tripped at 00:35! Power to house off for a few seconds, inverter beeping, and then everything came back on. Just a another question, when you set program 15 to BOF, does your button presses still make the beep sound?

@charlvnk Thanks for the update. My side also SPF 5000TL HVM-P and Dyness B4850 (x3), basically the same batteries as you have in the Powerbox. Powerbox just has 4x B4850s. In my case this has happened a few times in the last +- 2 weeks and also since moving to Li(program 05) and L01(program 36). It's not permanent, but happens for anything from 1 hour to 9hours once. Doing any kind of reset on the datalogger, unplugging datalogger, deleting the datalogger has no effect. Restart router, CPE, whatever, no effect. Just do nothing and then hour\s later the data returns and functions as normal again. Like now I haven't had the issue for 2 days again. All good. Exactly the same here. Have also been chatting to Mahone about this and he also has many screenshots and photos to confirm the issue from my side. His last email indicated that he has sent this to the R&D team and then also suggested the usual restart datalogger\reset datalogger\delete and reconfig datalogger and and and which up to now hasn't worked anyways. I have not tried setting it to USE again once this occurs, but will do so and confirm. Also want to do a traceroute to the Growatt server when this happens. tracert 47.91.67.66 BUT the fact that you say it works when on USE mode it clearly isn't a comms issue then. What is the BMS comms software you are referring to? Please also keep me posted when you do hear anything back from Mahone. I now 1st have to shutdown my inverter and make it lose all charge for a while before I will reply back to him. Just waiting for the time to switch the whole house off and over to Eskom first

I started having those same questions and here is a link to a discussion I started regarding the Dyness batteries. https://powerforum.co.za/topic/5212-dyness-b4850-charge-settings/?do=findComment&comment=72183

@willietes Thats great news! Glad you also got sorted out. Interesting, so the Pin 6 & 7 seems to be related to the non DIP switch models then.

Thanks @Coulomb, appreciate the replies. I have set my back to grid at 15% and low power cut off @ 10%. I have not seen the 15% yet, so far worst has been 19%. Understood, was more referring to it now being able to technically handle 7.2kw for 1 hour, but now the 2.4kw doesn't draw doesn't sound that bad vs just having 1 battery at 2.4kwh. I also found the following data regarding these batteries which gives some more detailed info and basically confirms what you have also said. My only reason for asking all of these questions was to be able to answer the question you also asked, getting the balance between battery life and discharge power. If it will extend my battery life considerably I would rather set my back to grid @ 20% instead of 15% for instance. Also to try and make a plan to be sure the load isn't more than 2.4kw at any point when on batteries. This is a bit difficult as I have seen that the batteries get charged to 99/100% and then PV is disconnected automatically and load is covered by the batteries only, until it gets to 95% again where PV kicks in again and starts the charging up to 99/100%.

Just bumping this one in case it got missed.

I take it you did do both firmware upgrades as per the stuff SiliconKid shared? FIRST and SECOND folders? I would still suggest this before doing a reflash of the firmware: Failing that: "Maybe when you have time, take a few photos of the config you currently have and post here. Cable, battery, inverter configs. Maybe a video of what you are seeing happening. "

Would also love to know what the Mecer's have which Growatt don't. Thought these were all much of the same.