-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Seplos v2 BMS #101
Comments
Hi @andreas-bulling, I need a bit more information to add the support:
|
I'm interrested in a seplos v2 support, too. I posted some of my findings already here Off course I can also create a trace, if this will help. |
Hi! A trace is always helpful. Before that, could you please provide the output of |
Attached requested trace: MAC's here:
|
Thanks, but the file is corrupt and I do not need the MAC addresses but the output of |
In fact it's not corrupt but a different/new format of a snoop trace from a galaxy s24. I'll try to find an old phone to collect traces that can be directly used in wireshark. |
This trace includes scenario with BP00 and BP02 in classic btsnoop_hci.log format. |
Perfect, that format I can read with Wireshark. Thanks a lot. Will have a look soon. |
Thanks a lot for your help @riogrande75 Thanks @patman15 for looking into this - would be fantastic to see this BMS, which is rather popular in the DIY community, supported. |
Hi all and thanks for the wonderful job: here something from the debug file: 2024-12-02 19:58:41.112 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for BP00 (60:6E:41:26:E9:61) as Jiabaida Smart BMS |
@ebagnoli the Seplos V2 is not yet supported, I still need to do the implementation. |
Thank for your replay. Is It something i can do tò help you in this implementation? |
If this can help you I installed nrf connect and thi is the log 00001800-0000-1000-8000-00805f9b34fb
|
If you have a first test version ready, feel free to contact me. I'm already curious and I guess I would be able to deliver useful diagnostic data too. |
With some time on the weekend it should be pretty straightforward. Just give me a bit of time. There have been a lot of requests lately. |
Just pushed the first version. The protocol description is a bit weak, so I had to make some assumption from the V3 logic. @riogrande75, @ebagnoli, @andreas-bulling if some of you could test and provide me feedback with an attached debug log that would be very helpful. Thanks! |
@patman15 Thx for adressing this bms' too. I just gave it a shot, BP0x get detected but fail after adding them: |
Seems that you already had (some) entries for the BMSs. Can you please delete all devices, restart and try again. It still detects JBD version although it shouldn't according to the code. |
Hi, I am out of my installation for one week, Aboard, I will. Do all the testing starting from December 16. Thanks a lot for your work |
Will do - but I first have to figure out an efficient way of downloading all necessary files to custom_components... |
Did what you said, but after removing all BMS' and restarting HA, same result. 2024-12-08 12:16:19.738 DEBUG (MainThread) [custom_components.bms_ble] confirm step for BP01 History: Logs attached. |
Give it some time. |
Will do. So far no luck. With the old version (without Seplos v2 support) BL00 and BL01 were detected right away, though... |
@riogrande75 are you sure, you really replaced all files in the folder |
Sure you replaced all files (see above) and restarted? Can you provide a log? As mentioned I tried it in my test setup, it should work. |
@ebagnoli not fully sure what you mean, but try deleting both devices and let them be rediscovered. |
@andreas-bulling No worries, great that it works now!
I disabled all devices but BP00 because I still think, I can query everything via BP00. If that turns out to be wrong, I will need to re-enable the others.
Please see the FAQ! |
@jambo1980 I just pushed a potential fix. Unfortunately, without having a device, I cannot verify. Could you (or anyone else with more than 1 battery) check and provide me a debug log? Thanks! |
I updated the seplos_v2_bms.py and restarted HA, but I still get identical cell voltages for all 3 batteries. That's the debug log of an update:
|
Ok, seems that the BP00 unit simply ignores the address and always returns the same value. 😞 Looks like I need to reactivate the Bluetooth of the other unit, which makes it a bit tedious. This will consume one BT slot (out of 3 per proxy) for each battery pack. |
Too bad. I thought all cell voltages are correct, but after a close look I had to realize that they really don't fit for BP01 and BP02. |
Do you guys want them as separate batteries or as one? For Seplos V3 they are combined as only one device is exposed, but as we have here three separate BT devices, it is a bit more challenging in case you want them aggregated. Any thoughts? |
I personally would prefer to have them separate. Also because this is a common (and widely discussed) issue with the Seplos BMS: That individual packs cannot easily be monitored (some people run a mix of BT and an additional RS485) to achieve that. |
ok, I just pushed an update that should present the packs individually as it was the easier fix. Not sure what data will be shown at the extension packs, but if you could provide me debug logs and let me know your observations that would be great to complete this topic. |
Cell voltages seem to be correct now. Sensor values of slave batteries are wrong, but I am only interested in the cell voltages ;-).
|
New day, new push, values should be correct now. You will need to add up power and current from each pack. |
@patman15 Thank you, all values seem to be correct now. My third pack has an older BMS version without bluetooth, so it doesn't show up when the packs are read out individually. |
I can confirm that the cell voltages are ok for each BP0x block now. I do also have disconnects and reconnects with BP02. Dunno why, but maybe the log reveals the problem. |
Thank you so much Patrick, after a lot of install/uninstall I think I had it working, now trying to have the individual cell voltage. |
Again, fixed. 😥 Thanks.
You also have them for BP01. The signal strength looks a bit low so you may want to add a proxy or get it closer ... |
Thx. Guess its related to the ammount of bms'. Need to install a 2nd proxy in my server room to have 2 JK's, 3 seplos v2 and one JBD online. In fact 6 connections or do I count incorrect? |
You are right, since Seplos v2 won't let me query everything through one connection... |
Nothing works anymore for me with version 11.3 and seplos 2. Yesterday was ok with 11.2 |
Between v1.11.0-beta.2...v1.11.0-beta.3 I only changed a divisor to correct current and charge value. It's unlikely that this causes a severe issue. |
Excellent work ! I have 3 Seplos V2 units and I can see them all 3. However I request to see some more: -State of Health (SOH) |
SoH is something that only a few BMSs report. Due to maintainability reasons I only add new sensors for values that are either available to all BMS types or can be calculated from other existing ones. |
SoH is something that only a few BMSs report. Due to maintainability reasons I only add new sensors for values that are either available to all BMS types or can be calculated from other existing ones. |
fixed with release v1.11.0 |
@patman15 Finally - the latest version (suddenly) works perfect also for me. I can see both batteries just fine. The connection is a bit unreliable (the batteries become "unavailable" VERY frequently) but this is not a problem of the integration but the BT connection. Thank you very much for implementing Seplos v2 support. I hope that many people will find this integration, as getting access to all values of all batteries is a key problem that many users of these BMS are facing. Usually, only aggregated data from BP00 is available. |
Probably just by accident due to your bad connection? The first initialization is a bit more critical compared to the others. If you have unavailability issues, try to monitor the |
My BMS BT closes down after period of inactivity . The data is then unavailable unless I reload the config. Fix for this ? |
@Leecavturbo since this issue is already closed, please open a new one and provide debug logs so I can check what is happening. Thanks! |
Checklist
Please describe the enhancement you would like to have.
It'd be great to support the v2 of the Seplos BMS (10E). The BMS is already detected correctly using the current version of this integration but a connection is not possible.
Additional context
https://drive.google.com/drive/folders/10pxgNLHovcDZRVGrCZsSkfecBrRw-AdW
The text was updated successfully, but these errors were encountered: