-
-
Notifications
You must be signed in to change notification settings - Fork 16
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 wrong Temperature Values #172
Comments
@vchaban88 please do not mix topics and create new issues to be able to separately track them. Regarding your issue, I would need a debug log in order to be able to help you. Can you generate one and attach it to this ticket? Thanks! |
@vchaban88 can you please check the linked branch via manual install? I think I found the issue. |
Yes, thank you, I'll definitely try it.
сб, 8 лют. 2025 р. о 13:24 Patrick ***@***.***> пише:
… @vchaban88 <https://github.com/vchaban88> can you please check the linked
branch via manual install? I think I found the issue.
—
Reply to this email directly, view it on GitHub
<#172 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJLHU57CLJ4OI43FLY2GUV32OXSPRAVCNFSM6AAAAABWNYVIX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBVGA2TGNZZGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
*Володимир Чабан*
+38 067-370-7710
|
After editing jikong_bms.py I got -73 degrees on the sensor (before it was 2550 degrees). The real battery temperature is 10 degrees. |
Can you please attach a debug log? Otherwise I cannot check the issue. |
I need to dig deeper, seems to be an issue with your firmware version. Meanwhile you can take the first temperature sensor (from the attributes) only, by adapting the templates in the FAQ. |
Hi I have a problem with the temperature sensor on the JK BMS. Maybe someone know how to solve it?
I have several JK BMS conected, some work well, but others - incorrect temperature sensore value ~ 2550 C`
Ursprünglich gepostet von @vchaban88 in #150 (comment)
The text was updated successfully, but these errors were encountered: