Add JK-B2A8S20P firmware 11.17 support (BLE) #147
Labels
Comments
|
Thanks for providing a |
|
1 task
|
Please update your configuration yaml to: and flash again. The protocol has changed a bit. In the past the maximum supported cells was 24. Now space for 32 cells is reserved / used: |
|
Hei, many thanks, you are crazy fast. It seems to work very well. I've also poked a little bit around in the bytes and I think the mosfet temperature is also at a wrong position. In the source it is at byte 134 but I think in my case it is at byte 144. So not behind Temperature 1 and 2. Instead 2 bytes in front of the total voltage. Again, many thanks for this fast solution. PS you should post somewhere a "by me a coffee" or paypal link, so that I could throw you a dime in the hat, for that amazing performance :) Andy
|
|
Thanks for your feedback and providing more details about your device. I will improve the feature branch ASAP. There is a buy me a coffee link as icon/badge at the top of the README. |
syssi
changed the title
|
Could you do me a favor? Could you verify the position of the You could change the cell count from 8S to 7S. This will raise an error. Is this error reported properly by this component or do we need to adjust the position of the |
|
Sorry for my late response. Here are two responses: //OK // Fault Here a corresponding screenshot of the app while in error state
|
Either your frame does not contain an error or the error bitmask position has changed. Could you double check? |
|
Hi, Here again a bytestream with a different error (overvoltage) maybe you have better eyes Screenshot without error:
Screenshot with error:
|
|
Could you provide 20 frames without errors and 20 frames including the same error? It should be easier to see a pattern here instead of comparing two frames. |
|
|
This line looks like the best match: The error of the |
|
Jop, its cell overvoltage again |
|
I assume byte 166 and 167 is the error bitmask. I will try to prepare something tomorrow to proof it. |
|
Ok, I'll try it, as soon as it is available |
|
I've moved the position of the error bitmask and added a condition to guess the frame version / format. Please update your ESPHome node and try to verify every sensor measurement (plausible or not). In best case the device suppot is complete now. |
|
Seems to work,
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I've received my JK BMS today and directly connected it via your nice library to my home assistant server.
The cell voltages and the configuration data are working flawlessly.
Unfortunately, everything else is 0 or some random numbers.
Could you be so kind and have a look at my configuration? Have I done something wrong?
Here a screenshot of the sensors:
Here a log of the esp device:
logs_pv-battery-bms_upload.txt
Here a screenshot of the Android app:
And finaly here my yaml file:
pv-battery-bms.txt
Thanks in advance
Andy
The text was updated successfully, but these errors were encountered: