Skip to content
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

Seplos v2 loosing protocol sync due to BT adapter messages #189

Open
patman15 opened this issue Feb 13, 2025 · 5 comments
Open

Seplos v2 loosing protocol sync due to BT adapter messages #189

patman15 opened this issue Feb 13, 2025 · 5 comments

Comments

@patman15
Copy link
Owner

home-assistant_bms_ble_2025-02-13T10-56-41.481Z.log

Originally posted by @bogi9999 in #171

Data disappears and comes back

@patman15 patman15 self-assigned this Feb 13, 2025
@patman15 patman15 added bug Something isn't working more info needed and removed bug Something isn't working labels Feb 13, 2025
@patman15
Copy link
Owner Author

patman15 commented Feb 14, 2025

@bogi9999 I checked the log, the problem is basically, that the BT adapter of the BMS messes up the BMS messages with it's own messages (AT+...). That results in corrupted data which is discarded. The only way to fix that is to disable the BT adapter messages. Not sure this can be done and how.
Does the app work 24/7?
Can you capture the Bluetooth traffic on Android or iOS while starting up the Seplos app with the battery? Maybe I can find some command disabling the AT commands.

@bogi9999
Copy link

Sorry, i don't know if the app work 24/7, because i do not sitt 24/7 in front of the battery. ;)
If i can capture, i first have to check if there is a tool for that available.

@patman15
Copy link
Owner Author

If i can capture, i first have to check if there is a tool for that available.

I linked you two for Android and iOS 😉

@bogi9999
Copy link

Hope this is what you need.

SeplosV2.log

@patman15
Copy link
Owner Author

Thanks, checked. The AT+ replies are also in there. I could see incorrect replies, although the command was not in the middle of some data. I guess with a longer recording we could see that as well.
I'm not 100% sure but I fear the behavior is simply bad design of the BT setup and unavoidable.

@patman15 patman15 removed their assignment Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants