Seplos opinions and experience
- Thread starter Koyaanisqatsi
- Start date
Koyaanisqatsi
Electron addict
I'll be interested in this as well. After my latest battery purchase, I have little patience for slow balancing circuits!
Drunkin Solar
Solar Enthusiast
No need for active balance in any of my three Seplos boxes. They all converge to less than 10mv.
Koyaanisqatsi
Electron addict
That's good to hear. But how long did it take to finally converge? In my bad experience, it took more than 100 hours of holding at high charge voltage to finally balance within 30mV. I guess if I top-balance the cells first, then the only balance drift would be in usage, which so far looks minimal.
Drunkin Solar
Solar Enthusiast
My thinking on the active balance thing is that it may be necessary if you are going to run the pack at high C rates from what I've read or if the cells used are of a lesser quality. I used all A grade cells with the paperwork to back that up and the performance has been excellent.
I did not top balance my cells before installation and on first charge they diverged by about 200mv which scared me. But after a few cycles they came together and have stayed good. I had plenty of time so I just let it work. Top balancing is still a good idea. I just didn't have the power supply to do it and didn't want to spend money on something that will wind up sitting on a shelf unused.
An active balancer can always be added later if you find the need. Doesn't make sense to me to not try the system as is first, as there is really nothing to loose.
Also have another smaller pack I put together with a JBD bms that has a weaker balance circuit than the Seplos and that took a month to converge but eventually did.
The Seplos's V2's are pretty good even with their passive balancing.
Of course they are not perfect, but the only "issue" I found with them is if ran with comms (CAN), the rs485 reporting for secondary monitoring is "choppy" and not smooth in their BMS monitor app. And, like a lot of other BMS, can not used CAN and rs485 ports simultaneously to get cell data on master pack unless also used with bluetooth (BLE)...
If run without coms, you can use both 485 and ble and get cell data ( and lots other) sfor all packs.
I still have some owrk to do but have been able to cobbled some of the github codes together to get decent reporting both from rs485 and ble siimultaneously, directly to HA using rs486/ttl > esp32 devices to capture what's in the screen grab.
The 4 packs below need to use a total of 3 esp32 devices and 1 ttl converter. The BLE leaves a bit still to be desired, but the rs485 is great.
2 columns on the left are rs485 data for packs 1-4 though screen grab is only of 1 and 3, the 2 right are of ble info
Of course they are not perfect, but the only "issue" I found with them is if ran with comms (CAN), the rs485 reporting for secondary monitoring is "choppy" and not smooth in their BMS monitor app. And, like a lot of other BMS, can not used CAN and rs485 ports simultaneously to get cell data on master pack unless also used with bluetooth (BLE)...
If run without coms, you can use both 485 and ble and get cell data ( and lots other) sfor all packs.
I still have some owrk to do but have been able to cobbled some of the github codes together to get decent reporting both from rs485 and ble siimultaneously, directly to HA using rs486/ttl > esp32 devices to capture what's in the screen grab.
The 4 packs below need to use a total of 3 esp32 devices and 1 ttl converter. The BLE leaves a bit still to be desired, but the rs485 is great.
2 columns on the left are rs485 data for packs 1-4 though screen grab is only of 1 and 3, the 2 right are of ble info
This thread gave me the motivation to finish up the integration today. Had to proof read it so many times to make sure the right data is populating in the right places for the respective cells and banks...
The nice thing about this is that we can specify the capture rate ( 30 sec for 18k, 10 sec for the bms) instead of the defaults of 3 min for inv and 1 sec for bms.
Quattrohead
Emperor Of Solar
Home assistant is great
What dashboard is that? I just installed HA a few days ago. I have Solar Assistant data populating as well as an Ecowitt weather station and a couple of other things but right now everything is just in the default dashboard as long lists of sensors and switches. I’ve spend two days trying to create one chart, so far without success, so it feels like this is going to take a very long time.
It's a vertically stacked card. The dashboard consists of 6 cards, 4 of which are the Bats.
I took a look at some of the cards and made the mods to make it cleaner and easier to decipher. Just copy this and paste it in your code editor, change to your actual names.
For other batteries you have to change the entity values for every bank.
Ok, implemented influx databae and grafana for the banks and individual cell stats. A quick glance would show history of any banks/cells out of order. I'll let this populate for a few weeks and reshow.
Anyone know if the "A.mean" can be renamed to its respective bank/cell?
I can do just about everything imaginable in excel but this grafana is new to me
Anyone know if the "A.mean" can be renamed to its respective bank/cell?
I can do just about everything imaginable in excel but this grafana is new to me
Last edited:
Koyaanisqatsi
Electron addict
Set your legend as a
Last edited:
bolhuijo
TechnoGeezer
One option is to manually change the series name to something better:
I usually prefer to turn the legend off entirely unless its important.
Grafana can be confusing with all the options for sure.
I usually prefer to turn the legend off entirely unless its important.
Grafana can be confusing with all the options for sure.
That worked. Thank you! Saves me a LOT of time. Now I just need to figure out why HA can only find one of my batteries and why the connection is so problematic.
Last edited:
Are you running CAN on master pack, close loop?
Did you physically set the dip switch address for each pack?
Described "problematic"
There are a couple "bugs" in the bms and at first seplos engineers denied, but i detailed it welland they said it's due to communication not being fast enough.
The issue I'm having is with a bluetooth integration in Home Assistant. The batteries are not yet installed and aren't connected to the Solar Assistant Orange Pi. The built-in bluetooth on the Raspberry Pi running HA is apparently not very good. The BLE integration could only ever find one of two batteries and could not consistently connect to that one. I'll be trying a couple of different things to improve the situation.
My Seplos batteries have no DIP switches.
My Seplos batteries have no DIP switches.
I finally got the courage to install Home Assistant and have a variety of integrations with my inverter and battery pack working.
The BLE integration is working reliably (finally) with an ESP32 acting as a Bluetooth proxy to forward Bluetooth data grabbed from the Seplos master battery and forwarded to Home Assistant over WiFi. The master battery has the data for both (all) packs. Template sensors are used to extract per pack values and individual cell voltages.
I’ve extensively modified the dashboard cards but they still look pretty much the same. I’m displaying the high cell in red and the low cell in green rather than showing the cell numbers. I had a hell of a time trying to make it readable on an iPhone and never could get it to display the packs one below the other. I ended up just tweaking the fonts to be readable on the small screen. I think it’s the full-width card at the top that’s preventing the card from reformatting but nothing I tried worked and I finally gave up.
I need to send an email to solar assistant support to see if they can include cell voltages as an attribute to an existing sensor like the BLE integration does. An RS485 connection is definitely preferable to Bluetooth, which can be fussy.
Edit: added a screen grab of my battery dashboard
The status of the battery is “problem” because the reset voltage for over protection is below the resting voltage of the pack, so it won’t clear until the battery discharges a bit later today. I’ll change that at some point.
The BLE integration is working reliably (finally) with an ESP32 acting as a Bluetooth proxy to forward Bluetooth data grabbed from the Seplos master battery and forwarded to Home Assistant over WiFi. The master battery has the data for both (all) packs. Template sensors are used to extract per pack values and individual cell voltages.
I’ve extensively modified the dashboard cards but they still look pretty much the same. I’m displaying the high cell in red and the low cell in green rather than showing the cell numbers. I had a hell of a time trying to make it readable on an iPhone and never could get it to display the packs one below the other. I ended up just tweaking the fonts to be readable on the small screen. I think it’s the full-width card at the top that’s preventing the card from reformatting but nothing I tried worked and I finally gave up.
I need to send an email to solar assistant support to see if they can include cell voltages as an attribute to an existing sensor like the BLE integration does. An RS485 connection is definitely preferable to Bluetooth, which can be fussy.
Edit: added a screen grab of my battery dashboard
The status of the battery is “problem” because the reset voltage for over protection is below the resting voltage of the pack, so it won’t clear until the battery discharges a bit later today. I’ll change that at some point.
Attachments
Last edited:
houseofancients
Solar Wizard
try the new beta, the seplos v2 was reworked , and BP0 will not give you values for you entire stack
The new beta of BLE? I am using the beta because it mentioned something about Seplos v3 and I was having some issues. It's been working reliably for the last few days.
What is BPO? Bluetooth Proxy? I am getting values for both of my batteries.
What is BPO? Bluetooth Proxy? I am getting values for both of my batteries.
houseofancients
Solar Wizard
i thought the discuss was about the seplos v2 here ?
a seplos v2 ( 10e) will show up as BP 0 in BLE
Similar threads
