-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
JK BMS V15 not working anymore with Version 1.11.0 #124
Comments
Can you get me a debug log to see what the integration says? Thanks! |
I don't know why your BMS likes to send additional "AT\r\n" messages while others don't. Seems to be some strange setting. Can you try the branch, which filters them? |
and there it is back maybe it is cause of the newest firmware v35? Thanks for your quick support |
i have to reopen this again. |
Excellent catch, thanks for the logs! Can you try this branch? By the way, this was not a newly introduced issue, but already existent in previous versions. |
interesting, have had sometimes reconnect problems in the past, so that the BMS was offline for some hours, but thought, it is caused of the bad wifi in the Inverter and Battery Room. The Branch is installed, and the BMS both show up, happy Christmas, and don't code to much in these days :) |
Should be fixed now. Reason was an unhandled exception during the initialization. Quite unlikely, but can happen ...
Merry Christmas too you! Good hint, on the other hand the best time for long uninterrupted sessions. 😉 |
Thanks for sharing. To me this looks like a defective cell, not related to the integration at all. If you want me to look deeper, please open a new issue and provide debug logs, since this issue is not at all related to the topic of this thread, neither the BMS type nor the problem. |
I think you can close and merge :) |
Checklist
Provide the type of BMS you used:
JK BMS V15.35
Describe the issue
The BMS gets no connection with the new Release
The attached log is a snipped of the Bluetooth Proxy, witch repeats over and over
Reproduction steps
Debug logs
The text was updated successfully, but these errors were encountered: