8000 JK-BD4A17S4P ESP32 Keeps restarting · Issue #221 · syssi/esphome-jk-bms · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

JK-BD4A17S4P ESP32 Keeps restarting #221

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.

Sign up for GitHub

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

Jump to bottom
Closed
Condor-XYZ opened this issue Nov 28, 2022 · 18 comments
Closed

JK-BD4A17S4P ESP32 Keeps restarting #221

Condor-XYZ opened this issue Nov 28, 2022 · 18 comments

Comments

@Condor-XYZ
Copy link

Hello Unfortunately, my ESP32 keeps restarting. Apparently the software is not entirely compatible with my JK-BD4A17S4P BMS.
can i do something there?

logs_jk-bms_logs.txt
@syssi
Copy link
Owner
syssi commented Nov 28, 2022

Could you provide some details (hardware & software version) about your BMS model? Do you miss some important measurements?

@Condor-XYZ
Copy link
Author

measured values are all there that i need
1669642962271

syssi added a commit that referenced this issue Nov 28, 2022
@syssi
Add JK-BD4A17S4P as supported
a43303c 
See #221
@syssi
Copy link
Owner
syssi commented Nov 28, 2022

These log messages are fine:

[18:38:16][D][jk_bms_ble:626]: Unknown168: 9E.06.00.00.00.00.00.00.00.00.00.00.00.00.07.00.01.00.00.00.0B.04.00.00.00.00.B1.28.41.40.00.00.00.00.E2.04.36.E7.00.00.00.01.00.05.00.00 (46)
[18:38:16][D][jk_bms_ble:640]: Unknown189: 04 00
[18:38:16][D][jk_bms_ble:644]: Unknown192: 00
[18:38:16][D][jk_bms_ble:646]: Unknown193: 00 B1 (0x00 0x8D)
[18:38:16][D][jk_bms_ble:648]: Unknown195: 28 41 (0x21 0x40)

There are some bytes at the response payload of which the purpose is not known. You could decrease the log level of the jk_bms_ble component from DEBUG to INFO to get rid of the noise.

Did you build the project with the recommended ESP-IDF framework or Arduino?

@Condor-XYZ
Copy link
Author

I used the ESP-IDF framework.
If I let it run like this for longer, the BMS has probably crashed. definitely no longer accessible with BLE (oh not on the smartphone)

@syssi
Copy link
Owner
syssi commented Nov 28, 2022

Could you check the red status LED? The BMS is able to handle a single BLE connection. If your ESP32 is connected to the BMS you cannot establish a connection with the Android app anymore and vice-versa. An active connection is indicated by a solid red LED. If the LED blinks the BMS is able to pick up a new connection. If the LED is off the BMS did an emergency shutdown.

@Condor-XYZ
Copy link
Author

I know that only one connection works.
In my version, the red LED flashes slowly without a BLE connection and quickly with BLE. The ESP was unplugged and I could no longer connect. LED was blinking slowly but maybe coincidentally... will keep watching

@syssi
Copy link
Owner
syssi commented Nov 28, 2022

Keep me updated. :-) I keep my fingers crossed that it's no general issue of your hardware version. A assume a new / another BLE module is used now.

@Condor-XYZ
Copy link
Author
Condor-XYZ commented Nov 28, 2022 •
edited
Loading

But what still needs to be clarified is why the ESP keeps restarting

@syssi
Copy link
Owner
syssi commented Nov 28, 2022 •
edited
Loading

Could you update to the most recent ESPHome version and rebuild + flash the device? The BLE client implementation has changed.

@Condor-XYZ
Copy link
Author

the same
Log.txt

@syssi
Copy link
Owner
syssi commented Nov 28, 2022

Could you remove the mqtt component just for testing?

@Condor-XYZ
Copy link
Author

Yes, without MQTT it works.
my MQTT server is from Iobroker and runs with the rest of the smart home devices without any problems... is there anything to watch out for with ESPHome?

@syssi
Copy link
Owner
syssi commented Nov 29, 2022 •
edited
Loading

This is another user having the same issue which could be solved by using mosquitto as MQTT broker: #211

Could you try to use another broker? Another idea is to capture the traffic between the ESPHome node and your MQTT broker to get an idea what's the difference (too many messages? different handshake? protocol version?).

@Condor-XYZ
Copy link
Author

I changed the settings of the MQTT client in Iobroker and that's it. Thanks for your help

before:
MQTT-Before
after:
MQTT-after

@syssi
Copy link
Owner
syssi commented Nov 30, 2022

Good job! Feel free to close the issue if it's solved!

This was referenced Mar 19, 2023
Closed
Open
@syssi
Copy link
Owner
syssi commented Apr 18, 2023

@Condor-XYZ Could you flash the most recent release of this component? I would like to make sure you should use protocol_version: JK02_32S in future or not.

@Condor-XYZ
Copy link
Author

this version with protocol JK02_32S does not work with my BMS. There are only illogical values. I continue to use JK02 as protocol.

@syssi
Copy link
Owner
syssi commented Apr 21, 2023

Thanks for your feedback! Good to know the frame structure of your BMS at software version 11 wasn't changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@syssi @Condor-XYZ
0