• Have you tried out dark mode?! Scroll to the bottom of any page to find a sun or moon icon to turn dark mode on or off!

diy solar

diy solar

12000xp off-grid setup overloads

Just letting everyone know that I have not been helped.
Last reply to DM received 5 business days ago. All holidays excluded.

For those unaware, the 6000xp has this same problem.
Do you have a call into SS for your specific issue? DMs can be quick/helpful, but there should be no expectation of issue tracking and fix unless you get a support call into them.
 
I have given my station id, and the date of last example. They could have started a ticket ?
All I’m suggesting is this forum is not an official support component for any vendor. There have been tons of resolutions thanks to vendor engagement (mostly by SS), but that doesn’t make it official.

Support workflows are tied to SLA’s and metrics, which are meant to accelerate resolution. For tracking, escalation and metrics you should place a call to SS and start a case. Refer to this thread and whatever interactions you’ve already had. At the very least someone will get nagged about the open ticket.
 
All I’m suggesting is this forum is not an official support component for any vendor. There have been tons of resolutions thanks to vendor engagement (mostly by SS), but that doesn’t make it official.

Support workflows are tied to SLA’s and metrics, which are meant to accelerate resolution. For tracking, escalation and metrics you should place a call to SS and start a case. Refer to this thread and whatever interactions you’ve already had. At the very least someone will get nagged about the open ticket.
Right on. Point taken. Thank you
 
For those unaware, the 6000xp has this same problem.
Not exactly. EG4 batteries don't have the problem. What BMS do you have? It would be interesting if other BMS brands are experiencing the same issue that you are. Unfortunately just because you're experiencing the same error doesn't mean the cause is exactly the same as the 12000xp were having. If you're lucky it is and a fix could be coming soon.
 
Not exactly. EG4 batteries don't have the problem. What BMS do you have? It would be interesting if other BMS brands are experiencing the same issue that you are. Unfortunately just because you're experiencing the same error doesn't mean the cause is exactly the same as the 12000xp were having. If you're lucky it is and a fix could be coming soon.

The problem is the LUX and pylontech protocol. Not any batteries. The reason this all came to light is because people were forced to use the LUX protocol with thier EG4 batteries in the 12000XP. And hence had the same problem as I do.

Every symptom is the same.
 
@ScrotpusGobbleBottom however reports this same issue on 6000XP for a DIY battery setup.
Stil no acknowledgement of the problem with the 6000xp.

EG4Techsolusionsteam on here has been a complete waste of time.
Its like I am talking with 4 different people that do not read what has been said.... VERY frustrating

I gave SS tech a call and we will see about that.
 
I'm going to have to setup a specific test. Is it:
1. Charge to 100% via whatever (pv or grid) early
2. While on PV and Grid (NOT AC FIRST) connected, turn on a load that exceeds PV
3. Look for EPS overload and switch to grid?
remember to test this.
 
you should place a call to SS and start a case.
I did that, they had me send 20 pictures, gave no response to them, and then told me to talk to EG4.

I emailed eg4 5 days ago and no response.

I am also still being ghosted by EG4 in my direct messages here.

They asked me to screen shot my bms as the problem happened. I did that 5 days ago.

STILL NO RESOLUTION

Edit: This is referring to the 6000xp exhibiting the same behavior with LUX and Pylontech protocols.
 
Last edited:
I did that, they had me send 20 pictures, gave no response to them, and then told me to talk to EG4.

I emailed eg4 5 days ago and no response.

I am also still being ghosted by EG4 in my direct messages here.

They asked me to screen shot my bms as the problem happened. I did that 5 days ago.

STILL NO RESOLUTION

Edit: This is referring to the 6000xp exhibiting the same behavior with LUX and Pylontech protocols.
Sad to hear this, might be they have a former Growatt tech working there.. this has been my experience wit GW for 3 1/2 years finally switched. Hope you get something resolved soon.. Hang in there..
 
View attachment 262918View attachment 262919
14 times timesin 3 hours. average load of 800 watts on 2 6000xps

I have not figured out why or how it eventually stops with less PV input, But once its done, its done, when the sun goes down.
But it resumed in the morning.
View attachment 262926
Yikes. Can't wait to mention this in my video.

I did notice that when you turn off the EPS output, it will momentarily shutdown the solar input. Very annoying.

Edit: solar input** not inverter output oops
 
Last edited:
Just to update everyone.

They replied at the 11-day mark. Not to my email, not to my DM, not to the original thread, but on a thread that I interjected on.

Their reply was more gaslighting. The last thing they told me was to take screenshots of my BMS app while it was occurring. I did.

They didnt even acknowledge that they received the pictures.

POOR

Eg4 told me:
Screenshot_28-1-2025_16217_diysolarforum.com.jpeg

In other words, its not their problem.

I knew they would say this. In fact I told someone in this thread back in Dec, that they would say that.

It is not a problem with the JK BMS. I havent used the coms on my JK BMS for a year yet the problem remains!

I told mutiple reps that its a LUX and Pylontec problem.

This is a joke.... I told them everything 3 different ways, 3 different times.

Still never got a reply to my email. This leaves a terrible impression.

I should screenshot all the correspondence with timestamps here so EG4 "can learn from this" It's quite pathetic.
 
Last edited:
Just to update everyone.

They replied at the 11-day mark. Not to my email, not to my DM, not to the original thread, but on a thread that I interjected on.

Their reply was more gaslighting. The last thing they told me was to take screenshots of my BMS app while it was occurring. I did.

They didnt even acknowledge that they received the pictures.

POOR

Eg4 told me:
View attachment 274013

In other words, its not their problem.

I knew they would say this. In fact I told someone in this thread back in Dec, that they would say that.

It is not a problem with the JK BMS. I havent used the coms on my JK BMS for a year yet the problem remains!

I told mutiple reps that its a LUX and Pylontec problem.

This is a joke.... I told them everything 3 different ways, 3 different times.

Still never got a reply to my email. This leaves a terrible impression.

I should screenshot all the correspondence with timestamps here so EG4 "can learn from this" It's quite pathetic.
@Eddie_LuxPowerTek
Has Lux seen this problem/incompatibility (Lux to JK BMS/Pylontec battery protocol) with the SNA-US 6KW?
 
@Eddie_LuxPowerTek
Has Lux seen this problem/incompatibility (Lux to JK BMS/Pylontec battery protocol) with the SNA-US 6KW?
I haven't spoken to them, but I did find some users in a forum that were describing the same thing.


Im using open loop now. I dont care anymore. The frustration of dealing with EG4 has drained my will. They won.

I can believe that EG4 was solely focused on the JK BMS, when I am not using the communication from it in 2 scenarios that it is happening.
They are saying my problem is something that isnt connected to the coms!

My last week signal chain :
15s battery > Jk BMS > YamBMS software > 6000xp-----JK bms not directly connected to coms

This also happened with
15s battery > Jk BMS no communication> DIYBMS esp32 software >Victron shunt > 6000xp-----JK bms not directly connected to coms
15s battery > Jk Inverer BMS > 6000xp -----JK bms IS directly connected to coms

All of these were used to try and get around this problem. All results were the same.

This problem has been going on since Nov. '22
 
Last edited:
I am now using the Solar assistant automations to do the only thing that I gained from closed loop coms. SOC based grid/battery change.
The 6000xps voltage switch over of +3V is ridicules. And voltage is ridiculous either way.

I have my main Victron shunt connected to solar assistant. Solar assistant uses the shunts SOC for automation.
On the 6000xp I am using voltage for the cutoffs

With the following automation I can do better than the 6000xp. The 6000xp switched to grid at +10% soc from cutoff.
With the Solar assistant automation, I can make this any % spread I want.

Remember, I'm using 15S because Renogy sucks donkey balls. 45V pack voltage is 3.0v/cell for me.
The automation V are to both extremes to make sure it transfers to grid and back.

I am still using the YamBms software, just not connected to the 6000xp.
I can use Home Assistant automations to do everything else closed loop did from HA.



Opera Snapshot_2025-02-03_054844_puscookie.us.solar-assistant.io.png


YamBms software is fantastic since I can see all this info, anywhere I am, with my phone.

Screenshot_3-2-2025_55858_homeassistant2.local.jpeg


Now im just waiting for the problem to happen in lead acid mode so I can give EG4 another earful. I dont think it will happen tho.
 
Last edited:
Im using open loop now.
I am confused, are you using open loop or are you using closed loop, I am seeing both from your replies.

My last week signal chain :
15s battery > Jk BMS > YamBMS software > 6000xp-----JK bms not directly connected to coms
You see where my lack of understanding is coming from.
The 6000xps voltage switch over of +3V is ridicules. And voltage is ridiculous either way.
I don't understand this either.
Can you start a fresh new thread with the exact problem because I'm just seeing a load of jumbled up mumbling and grumbling and dissatisfaction. I'm sure everyone wants this resolved.
 
I am now using the Solar assistant automations to do the only thing that I gained from closed loop coms. SOC based grid/battery change.
The 6000xps voltage switch over of +3V is ridicules. And voltage is ridiculous either way.

I have my main Victron shunt connected to solar assistant. Solar assistant uses the shunts SOC for automation.
On the 6000xp I am using voltage for the cutoffs

With the following automation I can do better than the 6000xp. The 6000xp switched to grid at +10% soc from cutoff.
With the Solar assistant automation, I can make this any % spread I want.

Remember, I'm using 15S because Renogy sucks donkey balls. 45V pack voltage is 3.0v/cell for me.
The automation V are to both extremes to make sure it transfers to grid and back.

I am still using the YamBms software, just not connected to the 6000xp.
I can use Home Assistant automations to do everything else closed loop did from HA.



View attachment 275287


YamBms software is fantastic since I can see all this info, anywhere I am, with my phone.

View attachment 275289


Now im just waiting for the problem to happen in lead acid mode so I can give EG4 another earful. I dont think it will happen tho.
I have not at time to try the test of loads greater than PV yet when at high SOC%. Hope to soon. So you’re just using SA to control inverter. YamBMS is collecting data?
 
I have not at time to try the test of loads greater than PV yet when at high SOC%. Hope to soon. So you’re just using SA to control inverter. YamBMS is collecting data?
Yes, exactly. SA only sees the shunt.
HA sees the rest.


I would like to see the results of your test.
I have a small suspicion that you may be ok simply because you are using 16s batteries.

The only reports I have found with this problem on the 6000xp have been with
Odd 100% voltages.
 
Last edited:
don't understand this either.
Can you start a fresh new thread with the exact problem because I'm just seeing a load of jumbled up mumbling and grumbling and dissatisfaction. I'm sure everyone wants this resolved.
I WAS using closed loop. I have tried 3 differnt ways, 2 not involving direct communication with the jk bms
1 having zero to do with the jk bms.

I don't need to start a thread.
I'm doing fine with open loop.
Your are right tho, if I had any hope of resolution or needed it fixed, i should do that.
 

diy solar

diy solar
Back
Top