Add JK-B2A16S support

[magnetus26]

any plans to support JK-B2A16S, hardware version 3.0, software version 3.3.0?

thanks.
best regards,
Miguel

[syssi]

I would like to support the device. Do you know some protocol details already? I assume it's the legacy protocol (0xDD 0xA5). If I prepare a feature branch to retrieve some device responses are you able to test the proof of concept?

[magnetus26]

sorry don't know protocol details, I'm a total newbie. I will be able to test the poc.
I will send you some pictures of the device later.

[syssi]

Please use the config yaml for the proof of concept: https://github.com/syssi/esphome-jk-bms/blob/add-protocol-v4-support/esp32-example.yaml

1. Connect GND, GPIO16 (tx_pin) and GPIO17 to your BMS. Please be careful I'm not sure about the voltage levels. Please be super careful to not touch the VBAT pin of the connector.
2. Flash the config to your ESP: esphome run esp32-example.yaml
3. Check the log

You should see the transmitted command:

[20:24:17][D][uart_debug:114]: >>> DD:A5:03:00:FF:FD:77

If it is working out of the box the BMS should respond with

[20:24:17][D][uart_debug:114]: <<< .... 

Please provide the responses!

[magnetus26]

I flashed 2 different ESP32 boards and the bms wont work. led will blink and beep once per second. if I press and keep holding the reset button in the ESP32 the BMS will boot.

ttl to bt is JDY-18, https://usermanual.wiki/Innovation-technology/JDY-18/pdf
Bluetooth module is configured to UART, select pin (17) is logic high.

I have the black wire to GND, red to VCC and white from TX to GPIO16

bms.mp4

best regards,
Miguel

[syssi]

Why did you attach the cables to the TX/RX of the BLE module? There should be an unused connector labeled "RS485". Could you provide good photos of the entire mainboard?

[syssi]

Please don't attach VCC of the ESP32!! Just connect GND, RX and TX. We want to send and receive data.

[magnetus26]

I don't have a RS485 connector and my BLE module is set to UART instead of IIC as per the manual that I sent you.
will the ESP32 works without VCC or do you want me to power it up via USB?
please see attached pics of my BMS

best regards,
Miguel

[syssi]

Could you provide a better photo of the mainboard? I would like to identify the different chips. This model doesn't provide any communication alternatives next to bluetooth out of the box? I don't see any connectors.

[magnetus26]

ok I uploaded some pics the CPU is an ST32F. that chip does not support RS485 communication just UART I2C and SPI. communication to the BT is UART.
correct no other communication alternative other than Bluetooth
no other connectors just the 2 to connect the batteries a large one with gnd and b1 to b14 and a smaller one with b15 to b20 and B+

[magnetus26]

I uploaded a few pics yesterday
looks like jblance has support for this device but is not thru esphome
JK BMS
JK-B2A24S (HW version 3.0)

[syssi]

Could you point me to the jblance implementation and could you provide the label/name of this chip?

[magnetus26]

here is jblance implementation and will provide info on that chip when I get home.

https://github.com/jblance/mpp-solar

best regards,
Miguel

[syssi]

Some ideas / background:

1. The protocol between the bluetooth module and the MCU is unknown. Nobody tried to replace the bluetooth module by some serial line yet. I've captured some traffic between my bluetooth module and the MCU here: UART traffic capture: BK3432 BLE module <-> HK32F103C8T6 MCU #49
2. https://github.com/jblance/mpp-solar implements multiple protocols. Your BMS is supported via BLE at least. I assume RS485 is supported too. The marked chip is probably the RS485 converter and the free pads can be used to connect a RS485 module + ESP.

Next steps: Identify the marked chip. Lookup the pinout of the chip. Identify the RS485 A/B pins and GND. Trace the lines between the chip and the free pads. Solder a RS485 converter to the pins (A, B, GND). Connect the RS485 converter to the ESP. Bonus: Trace the lines between the chip and the MCU. Lookup the pinout of the MCU and make sure the RS485 converter is connected to UART pins.

As soon everything is in place we will implement this protocol:

JIKONG JK-B1A24S-RS485-protocol-english.pdf

[magnetus26]

ok. chip next to CPU is a serial eeprom PN 24c02A https://pdf1.alldatasheet.com/datasheet-pdf/view/74863/MICROCHIP/24C02A.html
CPU is an ARM based CPU 32f1038 https://pdf1.alldatasheet.com/datasheet-pdf/view/534650/STMICROELECTRONICS/STM32F1038.html
this chip has 3 USART ports
USART2 goes to BLE module, I assume that this is USART TTL communication
pin 12 is RX
pin 13 is TX

USART3 goes to the serial eeprom 24c02a and is I2C communications
pin 21 is SCL
pin 22 is SDA

USART1 goes to an empty heather next to the eeprom
this goes to the bottom 2 pins in the empty heather
pin 30 is TX very bottom one
pin 31 is RX second to the last

I don't have an RS485 converter :)
so do I need an RS485 to TTL converter???
or can i connect this pins to my ESP32???
best regards,
Miguel

[syssi]

Yes! :-) If there is no chip converting the USART1 TTL level (3.3V) into RS485 (-7/12V) the ESP can be attached directly.

[magnetus26]

so whats the next step should I connect the ESP32 with the code that you send me or should I wait for a new code?

[syssi]

I've prepared some code. Please give it a try:

wget https://github.com/syssi/esphome-jk-bms/blob/add-jk-balancer-support/esp32-example.yaml
esphome run esp32-example.yaml

This time you should see the transmitted command:

[20:24:17][D][uart_debug:114]: >>> 55:AA:01:FF:00:00:FF

If it is working out of the box the BMS should respond with

# https://github.com/jblance/mpp-solar/blob/master/mppsolar/protocols/jk485.py#L11
# https://github.com/jblance/mpp-solar/blob/master/mppsolar/protocols/jk485.py#L73
[20:24:17][D][uart_debug:114]: <<< EB:90:01:FF:1E:D3:0F:69:14:13:02:00:00:00:07:00:00:00:05:03:E8:01:14:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:0F:69:00:16:6F

Please provide the responses!

[magnetus26]

will do as soon as I get home. just to make sure TX from cpu goes to GPIO 16 and RX from cpu goes to 17. not crossover...

[syssi]

I don't know for sure. Swapping the lines shouldn't harm the device. I would try both. ;-)

[magnetus26]

im using this module

ahould I keep using GPIO 16 and 17 or change the code to use the UART pins (GPIO1 for TX and GPIO3 for RX) ?
ill be home like in 3 or 4 hrs... :(

[syssi]

Please avoid GPIO1 and GPIO3 -> use 16 and 17. The logger component uses GPIO1 and 3 by default. We don't want to collide with the logger by accident.

[syssi]

73 de DO2KSM ;-)

[magnetus26]

ok will do thanks and hope to find you on the air sometime
73 de KP4MI 🎙

[magnetus26]

"I flashed 2 different ESP32 boards and the bms wont work. led will blink and beep once per second. if I press and keep holding the reset button in the ESP32 the BMS will boot."
well, the beeping sound looks like a power, issue cant power up the ESP32 out 3.3v from the BMS.
(I learned that the hard way, trial and error).

I powered the ESP32 using a microUSB cable and here are the results and they are not good.

GPIO16 to last pad and GPIO17 to the one before the last:
GPIO16 to last pad.txt

GPIO17 to last pad and GPIO16 to the one before the last::
GPIO17 to last pad.txt

GPIO16 to TX, GPIO17 to RX on BLE module:
GPIO16 to BLE TX.txt

GPIO17 to TX, GPIO16 to RX on BLE module:
GPIO17 to BLE TX.txt

73 de KP4MI

[syssi]

This is a pity. Could try this protocol too?

wget https://raw.githubusercontent.com/syssi/esphome-jk-bms/add-protocol-v4-support/esp32-example.yaml
esphome run esp32-example.yaml

Expected request:

>>> DD:A5:03:00:FF:FD:77

Expected response

<<< DD:03:00:1B:17:00:00:00:02:D0:03:E8:00:00:20:78:00:00:00:00:00:00:10:48:03:0F:02:0B:76:0B:82:FB:FF:77

https://github.com/jblance/mpp-solar/blob/master/mppsolar/protocols/jk232.py

[magnetus26]

same issue as last time
GPIO17 BLE TX.txt
GPIO16 last pad.txt
GPIO17 last pad.txt
GPIO16 BLE TX.txt

[syssi]

My last idea is to test different baud rates.

[syssi]

Another idea: Test the protocol of the firmware v6 (main branch of this project) with baud rautes below 115200 (= 38400, 19200, 9600).

[syssi]

@sshoecraft Sorry for bothering you. Do you know this hardware version (JK-B2A16S, v3.0) and do you have an idea about possible connectivity next to bluetooth? We've identified a second USART1 connected to some empty header but the device doesn't respond to known requests/protocols.

[magnetus26]

ill give this a try again, im using a 8266 (ran out of esp32s)
i dont have a modbus, should I use this:

or does it has to be changed?

[syssi]

This config is important. Just use it. Don't think about it. ;-) It's the protocol not the signal level / modulation.

[magnetus26]

sorry for the delay will try tonight been busy with my mom lately
thatnks for tour hard work and support for the community
73
KP4MI
Miguel

[syssi]

Take your time!

[magnetus26]

here are some logs this one is with balance off in the app:
logs_bms_logs (2).txt

this other one is with the balance on in the app:
logs_bms_logs (3).txt

fist byte does change from x01 00 when enabled to x00 00 when disable.

[magnetus26]

I added the following to my yaml
switch:

• platform: jk_bms_ble
  balancer:
  name: "${name} balancer"
  Balancing current sensor still active (balancing) either in with the Banalcer switch on or off
  is this working as it should?
  [20:04:59][D][switch:013]: 'jk-bms balancer' Turning ON.
  [20:04:59][D][jk_bms_ble:1037]: Write register: AA.55.90.EB.1F.04.01.00.00.00.00.00.00.00.00.00.00.00.00.9E (20)
  [20:04:59][D][switch:037]: 'jk-bms balancer': Sending state ON

[20:04:43][D][switch:017]: 'jk-bms balancer' Turning OFF.
[20:04:44][D][jk_bms_ble:1037]: Write register: AA.55.90.EB.1F.04.00.00.00.00.00.00.00.00.00.00.00.00.00.9D (20)
[20:04:44][D][switch:037]: 'jk-bms balancer': Sending state OFF

RPReplay-Final1650932095.mp4

[syssi]

The video shows some "balancing current" > 0 so it looks like turning the balancing off via the switch doesn't have any impact. Could you try again and provide some logs? The full test procedure should look like this:

1. Flash the new version from main
2. Turn the balancing on
3. Press the "retrieve settings button" (the log will contain the settings frame including the balancing bit = 0x01)
4. Turn the balancing via the switch off
5. Press the "retrieve settings button" (the log will contain the settings frame including the balancing bit = 0x00)
6. If the switch is working the switch state shouldn't flip back to on after "retrieve settings button"
7. Provide the log

73 de DO2KSM

[syssi]

If it doesn't work we can sniff the BLE traffic between BMS and Android app. This isn't hard on Android devices:

https://quick-adviser.com/how-do-i-view-btsnoop-logs/
https://medium.com/@charlie.d.anderson/how-to-get-the-bluetooth-host-controller-interface-logs-from-a-modern-android-phone-d23bde00b9fa

As soon you can provide a btsnoop.log / captured traffic containing the "turn balancing on/off" instruction I can extract the command / holding register from the log.

[magnetus26]

as soon as a press "retrieve settings button" the balancing switch turns on
logs_bms_logs.txt

RPReplay-Final1650978154.MP4

will try to sniff BLE traffic later had to undust the android tablet and is charging now and my laptop is old had to wait a long time to install SDK Platform Tool

[syssi]

You don't need the SDK platform tool if you are able to select & transfer some file from the internal storage in a different way. adb is used for downloading the btsnoop.log from the device only.

[magnetus26]

nevermind got it, had to restart the tablet.
btsnoop_hci.log redacted for privacy

well , it's time to visit ( deal ) with my mom will get back later on tonight hope this help and if you get anything will try after 20:00 my local time
best regards,
73
KP4MI
Miguel

[syssi]

Good job! I've found some "write command" frames at the capture:

The chance is high the capture includes all relevant informations to control your device.

[syssi]

# Enable/disable balancing instruction
aa5590eb6c0100796296ede3d082a19b5b3c9ce9
aa5590eb6c01014bd327863be2124db0b6f764f0
aa5590eb6c0100a44e66bd23cccd72811e7eb7fe
aa5590eb6c0101b85601329fbccccc5f356b4e69
aa5590eb6c010058a47af6397058f42c0b23b254
aa5590eb6c0101cd312d28f26b0417766c059b35
        ^^^^^^
         | | |
         | | value (0x00 vs 0x01
         | |
         | length (0x01 = 1 byte)
         |
         holding register (0x6c)

Good news & good job! :-) You've enabled and disabled balancing 3 times.

[syssi]

I've pushed some changes to main. Please recompile and flash again. The balancer switch entity should work now.

[magnetus26]

compiled the new changes and it works thanks, I even added a binary switch and it does works too:
binary_sensor:

• platform: jk_bms_ble
  balancing:
  name: "${name} balancing"
  is there a way to change the binary sensor to display from ON or OFF to Balancing and Waiting?
  ( I know I'm asking for too much lol)

[syssi]

I will add an operation_mode sensor later the day. There is one little piece missing for full device support: Could you prepare another btsnoop capture while changing the settings one after the other? I would like to know the holder register of the different settings (stop voltage, start balancing etc.). Please just apply very small changes/increments to the voltages, so it will be easier to re-identify the commands.

[syssi]

If you turn off the balancer switch is the operation status (shown at the first page top right) "Waiting" or does it show something else next to "Balancing" and "Waiting"?

[syssi]

I've implemented the text sensor: #93

Please let me know if the Android app supports additional status messages.

[magnetus26]

I will add an operation_mode sensor later the day. There is one little piece missing for full device support: Could you prepare another btsnoop capture while changing the settings one after the other? I would like to know the holder register of the different settings (stop voltage, start balancing etc.). Please just apply very small changes/increments to the voltages, so it will be easier to re-identify the commands.
sensor works is showing balancing and idle. I have the delta set to .005v and stop voltage to 3.00v. what do you mean by very small changes/increment to the voltages? just to let you know every time that I make an adjustment to the settings I have to power cycle the BMS (there is not a reset switch and it will not take the changes until the unit reboots).
PS.
I will like to see a change in the status name from Idle to Waiting.
If you turn off the balancer switch is the operation status (shown at the first page top right) "Waiting" or does it show something else next to "Balancing" and "Waiting"?
the only two modes are Balancing when balancer is on and Waiting when Balancer is off or if the delta is =< than .005v

Please let me know if the Android app supports additional status messages.
I don't think that there are any other messages
there are some setting in the "settings tab" (that's in the iPhone app the Android app doesn't have the Start Balance Vol option, I guess that it autodetect the batteries type and adjust the voltage accordingly)

but again they will only take effect if I power cycle the BMS (and there are some settings that if I change it wonk take like start balance volt.
its cloudy and has been raining but the system is charging now, see if the logs works. I changed the Power Off Vol and the Max Balance Cur but idk if the change got logged due to the fact that I have to power cycle the BMS in order to save change in settings. those 2 files were in the zip file that the adb created.

btsnoop captures redacted

[syssi]

Commands from the second capture:

aa5590eb2004cdcc2c4042b3f70b134a93c058a2
        ^^
        0x20
          ^^
          0x04
            ^^^^^^^^
            0xcdcc2c40

aa5590eb680400000040a9fe5358b092ca4addab
aa5590eb68040000803f04d2e36fb8c5d4912edd
        ^^
        0x68
          ^^
          0x04
            ^^^^^^^^
            0x00000040 vs. 0x0000803f

[syssi]

aa5590eb2004000040405601329fbccccc5f352e: 0x20 0x04 0x00004040 (3.0)         # Power off voltage??
aa5590eb200400004040d327863be2124db0b680: 0x20 0x04 0x00004040 (3.0)
aa5590eb2004cdcc2c405601329fbccccc5f35b3: 0x20 0x04 0xcdcc2c40 (2.7)
aa5590eb2004cdcc2c4042b3f70b134a93c058a2: 0x20 0x04 0xcdcc2c40 (2.7)

aa5590eb440466ef40406b4e58a47af6397058bd: 0x44 0x04 0x66ef4040 (3.01461)     # Any idea?

aa5590eb6804000000405601329fbccccc5f3536: 0x68 0x04 0x00000040 (2.0)         # Max balance current?
aa5590eb6804000000406b4e58a47af63970584c: 0x68 0x04 0x00000040 (2.0)
aa5590eb680400000040a9fe5358b092ca4addab: 0x68 0x04 0x00000040 (2.0)
aa5590eb68040000803f04d2e36fb8c5d4912edd: 0x68 0x04 0x0000803f (1.0)

aa5590eb6c0100796296ede3d082a19b5b3c9ce9: 0x6c 0x01 0x00 (Balancer off)
aa5590eb6c01014bd327863be2124db0b6f764f0: 0x6c 0x01 0x01 (Balancer on)

[syssi]

@magnetus26 Could you try to evaluate my guesses? To simplify the testing: You don't need to restart the BMS. Sending commands / write instructions to the BMS is enough. Depending on the transmitted value we try to guess the name of the setting. The conclusion should be something like this:

• If we want to change the "power off voltage" we must update register 0x20.
• If we want to change the "max balance current" we must update register 0x68.
• If we want to change the cell count we must update register ???
• If we want to change the trigger delta voltage ...
• If we want to change the start balance voltage ...

[magnetus26]

@magnetus26 Could you try to evaluate my guesses? To simplify the testing: You don't need to restart the BMS. Sending commands / write instructions to the BMS is enough. Depending on the transmitted value we try to guess the name of the setting. The conclusion should be something like this:

• If we want to change the "power off voltage" we must update register 0x20.
• If we want to change the "max balance current" we must update register 0x68.
• If we want to change the cell count we must update register ???
• If we want to change the trigger delta voltage ...
• If we want to change the start balance voltage ...

I can log the changes in cell count and trigger delta voltage, start balance voltage option is not available in the Android app only in the iPhone app. when I installed the app in my Android tablet it said that the old app got replaced with that one.

iPhone images:

Android images

please see new logs:
redacted

[magnetus26]

I try to provide some test instructions. If you follow the instructions step by step it's easier for me to analyze the btsnoop capture.

1. Make a screenshot of the settings view of the Android app. I would like to know the start values of all parameters.
2. Enable the bluetooth traffic capture
3. Open the BMS android app again & go to the settings page
4. Press "OK" of the cell count setting (without changing the value). The BMS should beep
5. Press "OK" trigger delta voltage setting - the BMS shoukd beep
6. Press "OK" of the "start balance voltage" (if the setting is available at the android app) - the BMS should beep
7. ... and so on.
8. Please provide the btsnoop.log again.

If I extract the write commands from the capture I should find the different ("OK") button presses + the transmitted value. The transmitted value should match with your screenshot from step 1. In best case we know the write commands for all settings afterwards.

[magnetus26]

`aa5590eb2004000040405601329fbccccc5f352e: 0x20 0x04 0x00004040 (3.0) # Power off voltage??
aa5590eb200400004040d327863be2124db0b680: 0x20 0x04 0x00004040 (3.0)
aa5590eb2004cdcc2c405601329fbccccc5f35b3: 0x20 0x04 0xcdcc2c40 (2.7)
aa5590eb2004cdcc2c4042b3f70b134a93c058a2: 0x20 0x04 0xcdcc2c40 (2.7)

aa5590eb6804000000405601329fbccccc5f3536: 0x68 0x04 0x00000040 (2.0) # Max balance current?
aa5590eb6804000000406b4e58a47af63970584c: 0x68 0x04 0x00000040 (2.0)
aa5590eb680400000040a9fe5358b092ca4addab: 0x68 0x04 0x00000040 (2.0)
aa5590eb68040000803f04d2e36fb8c5d4912edd: 0x68 0x04 0x0000803f (1.0)`
yes those are the values that I have chosen for Power off voltage and Max balance current.

aa5590eb440466ef40406b4e58a47af6397058bd: 0x44 0x04 0x66ef4040 (3.01461) # Any idea?
not really I dont see any other value/parameter in my app (joke: btw all this looks German to me, I don't understand a thing lol)

[syssi]

# btsnoop_hci.log

hdr   addr len   value
aa......6c 01 00796296
aa......6c 01 014bd327
aa......20 04 00004040
aa......68 04 00000040
aa......6c 01 00796296
aa......6c 01 014bd327
aa......20 04 cdcc2c40
aa......20 04 00004040
aa......6c 01 00796296
aa......6c 01 014bd327
aa......68 04 00000040
aa......44 04 66ef4040
aa......1c 02 0f00d327
aa......1c 02 1000a44e
aa......64 04 bc74133c
aa......64 04 0ad7a33b
aa......44 04 c8cd4340
aa......44 04 b6123e40
aa......6c 01 00712b99
aa......6c 01 007b3a39
aa......6c 01 0132bc87
aa......1c 02 1000d327
aa......64 04 0ad7a33b
aa......68 04 00000040
aa......20 04 00004040
aa......44 04 cbca3d40
aa......1c 02 1000cd31
aa......64 04 0ad7a33b
aa......68 04 00000040
aa......20 04 00004040
.......... .. ........
aa......44 04 08623e40
aa......1c 02 10003fa3
aa......64 04 0ad7a33b
aa......68 04 00000040
aa......20 04 00004040
aa......44 04 24753d40
aa......1c 02 1000b092

# btsnoop_hci.log.last.txt
aa......6c 01 00796296
aa......6c 01 014bd327
aa......6c 01 00a44e66
aa......6c 01 01b85601
aa......6c 01 0058a47a
aa......6c 01 01cd312d
aa......6c 01 00796296
aa......6c 01 014bd327
aa......6c 01 00a44e66
aa......6c 01 01b85601
aa......6c 01 0058a47a
aa......6c 01 01cd312d
aa......20 04 cdcc2c40
aa......68 04 00000040
aa......68 04 0000803f

[syssi]

# cat cmds.txt | grep -v '\.\.\.6c' # balancer commands removed

hdr   addr len   value
aa......20 04 00004040
aa......68 04 00000040
aa......20 04 cdcc2c40
aa......20 04 00004040
aa......68 04 00000040
aa......44 04 66ef4040
aa......1c 02 0f00d327
aa......1c 02 1000a44e
aa......64 04 bc74133c
aa......64 04 0ad7a33b
aa......44 04 c8cd4340
aa......44 04 b6123e40
aa......1c 02 1000d327
aa......64 04 0ad7a33b
aa......68 04 00000040
aa......20 04 00004040
aa......44 04 cbca3d40
aa......1c 02 1000cd31
aa......64 04 0ad7a33b
aa......68 04 00000040
aa......20 04 00004040
.......... .. ........
aa......44 04 08623e40
aa......1c 02 10003fa3
aa......64 04 0ad7a33b
aa......68 04 00000040
aa......20 04 00004040
aa......44 04 24753d40
aa......1c 02 1000b092

# btsnoop_hci.log.last.txt
aa......20 04 cdcc2c40
aa......68 04 00000040
aa......68 04 0000803f

[syssi]

Different addresses:

0x1c
0x20
0x44
0x64
0x68
0x6c: Balancer

[syssi]

hdr   addr len   value value-as-float
aa......20 04 00004040 3.0
aa......68 04 00000040 2.0
aa......20 04 cdcc2c40 2.7
aa......20 04 00004040 3.0
aa......68 04 00000040 2.0
aa......44 04 66ef4040 3.01461
aa......1c 02 0f00     (int)15
aa......1c 02 1000     (int)16
aa......64 04 bc74133c 0.009
aa......64 04 0ad7a33b 0.005
aa......44 04 c8cd4340 3.05943
aa......44 04 b6123e40 2.96989
aa......1c 02 1000     (int)16
aa......64 04 0ad7a33b 0.005
aa......68 04 00000040 2.0
aa......20 04 00004040 3.0
aa......44 04 cbca3d40 2.9655
aa......1c 02 1000     (int)16
aa......64 04 0ad7a33b 0.005
aa......68 04 00000040 2.0
aa......20 04 00004040 3.0
.......... .. ........
aa......44 04 08623e40 2.97473
aa......1c 02 1000     (int)16
aa......64 04 0ad7a33b 0.005
aa......68 04 00000040 2.0
aa......20 04 00004040 3.0
aa......44 04 24753d40 2.96027
aa......1c 02 1000     (int)16

# btsnoop_hci.log.last.txt
aa......20 04 cdcc2c40 2.7
aa......68 04 00000040 2.0
aa......68 04 0000803f 1.0

[syssi]

# sorted

hdr   addr len   value value-as-float
aa......1c 02 0f00     (int)15
aa......1c 02 1000     (int)16
aa......1c 02 1000     (int)16
aa......1c 02 1000     (int)16
aa......1c 02 1000     (int)16
aa......1c 02 1000     (int)16
aa......20 04 00004040 3.0
aa......20 04 00004040 3.0
aa......20 04 00004040 3.0
aa......20 04 00004040 3.0
aa......20 04 00004040 3.0
aa......20 04 cdcc2c40 2.7
aa......20 04 cdcc2c40 2.7
aa......44 04 08623e40 2.97473
aa......44 04 24753d40 2.96027
aa......44 04 66ef4040 3.01461
aa......44 04 b6123e40 2.96989
aa......44 04 c8cd4340 3.05943
aa......44 04 cbca3d40 2.9655
aa......64 04 0ad7a33b 0.005
aa......64 04 0ad7a33b 0.005
aa......64 04 0ad7a33b 0.005
aa......64 04 0ad7a33b 0.005
aa......64 04 bc74133c 0.009
aa......68 04 00000040 2.0
aa......68 04 00000040 2.0
aa......68 04 00000040 2.0
aa......68 04 00000040 2.0
aa......68 04 00000040 2.0
aa......68 04 00000040 2.0
aa......68 04 0000803f 1.0

Conclusion:

0x1c: Cell count (16)
0x20: Power off voltage (3.0)
0x44: Unknown (2.97473, 2.96027, 3.01461, 2.96989, 3.05943)
0x64: Trigger Delta Vol (0.005)
0x68: Max Balance Current (2.0 A)
0x6c: Balancer (on/off)

[syssi]

I will like to see a change in the status name from Idle to Waiting.

I don't want to change the naming from "Idle" to "Waiting". You could use a template text sensor to use custom texts:

https://esphome.io/components/text_sensor/template.html#text-sensor-template-publish-action

[magnetus26]

hello Sebastian,
I'm trying to add switch to control Bluetooth connection
`switch:

• platform: ble_client
  ble_client_id: client0
  name: "${name} enable bluetooth connection"`

but I get the following error:

any ideas why this is happening?

thanks
Miiuel

[syssi]

Please update your ESPHome install (pip3 install esphome -U) and try esphome clean bms.yaml; esphome run bms.yaml.

[magnetus26]

esphome was up to date, cleaning the build files and compiling again did the trick
thanks.
Miguel
PS.
I also updated the platformio

[magnetus26]

hi Senastian, after adding control BT connections , im experiencing the esp32 to go offline every so often

do you think is something with my code or my esp32 might be going bad? I have 2 others esp32 in the same room 1 for the inverter and 1 for the bms.

I ran out of esp32 spares. do yo think the code can be added to any of the other 2? they both are using serial coms and not using the ble

as last resort I could use an esp 8266 for my inverter and use that esp32 for the bms

thanks
Miguel
73 de KP4MI

[syssi]

Could you try to ping the IP address of the ESP32 (not the *.local name!!) if the node is reported as offline? I've the experience the mDNS discovery of ESP32 nodes isn't possible sometimes. In reality the node is properly connected and working just the mDNS discovery doesn't work. If the sensors of the node are marked as unavailable we are in trouble. ;-)

[magnetus26]

will try that next time it happends. I havent read this until today an I have been unplugin the esp32.
how can I add a restart suitch or button
i tried the following and it validates ok but when i try to compile it will give me an error

I also try as button instead of switch and it wont compile either

thank you
Miguel
73 de KP4MI

[syssi]

Please try a clean build using. esphome clean node.yaml + esphome run node.yaml.

[magnetus26]

it works
thanks
Miguel

[magnetus26]

hello Sebastian,
in a totally different topic I want to ask you about an error that I have creating an automation.
I don't know much about automations and need some help if you can
here is what I'm trying to accomplish I asked in the HA forum but had no answer,

Hi all I’m having some trouble creating an automation.
here is what I’m tryin to accomplish:
if master-bedroom-ac is off then mppsolar-inverter-0 Change
inverter0_output_source_priority_select option is set to SBU else then
ppsolar-inverter-0 Change inverter0_output_source_priority_select option is
set to Utility first.
here is my YAML file

alias: if master-bedroom-ac is off
description: >-
  if master-bedroom-ac is off then mppsolar-inverter-0 Change
  inverter0_output_source_priority_select option is set to SBU else then
  ppsolar-inverter-0 Change inverter0_output_source_priority_select option is
  set to Utility first
mode: single
trigger:
  - platform: device
    device_id: bb7fe9e1a97632a10066960d5adc80fe
    domain: climate
    entity_id: climate.master_bedroom_ac
    type: hvac_mode_changed
condition: []
action:
  - if:
      - condition: device
        device_id: bb7fe9e1a97632a10066960d5adc80fe
        domain: climate
        entity_id: climate.master_bedroom_ac
        type: is_hvac_mode
        hvac_mode: 'off'
    then:
      - device_id: de6313df2cddf16b3469452252e64db3
        domain: select
        entity_id: select.inverter0_output_source_priority_select
        type: select_option
        option: Solar Battery Utility
    else:
      - device_id: de6313df2cddf16b3469452252e64db3
        domain: select
        entity_id: select.inverter0_output_source_priority_select
        type: select_option
        option: Utility first 

and I’m getting this error:
Message malformed: required key not provided @ data[‘to’]

thanks in advanced
Miguel

[syssi]

To simplify the automation I would split the automation into two pieces/automations:

1. If hvac_mode changes to off set source priority SBU
2. If hvac_mode changes to on set the source priority Utility first

As trigger I would use the platform: state to monitor the state of an entity or attribute. This trigger requires a parameter called to: (the sensor value we are going to. Also the value we are coming from could be defined).

As action I would use the select.set_option service. You have to provide the selected option at the data section.

I'm using / suggesting this way because I'm not verify familiar with the new device platform automations.

[syssi]

- alias: Use source prio SBU if AC is off
  id: '1658297060'
  trigger:
    - platform: state
      entity_id: climate.master_bedroom_ac
      to: 'off'
  action:
    - service: service: select.select_option
      entity_id: select.inverter0_output_source_priority_select
      data:
        option: 'Utility first'

- alias: Use source prio utility first if AC is on
  id: '1658297061'
  trigger:
    # List all hvac_modes here unequal "off"
    - platform: state
      entity_id: climate.master_bedroom_ac
      to: 'cool'
    - platform: state
      entity_id: climate.master_bedroom_ac
      to: 'heat'
  action:
    - service: service: select.select_option
      entity_id: select.inverter0_output_source_priority_select
      data:
        option: 'Utility first'

[linuxdep]

Hi, were you able to change the value for "Start Balance Volt"? Is the rest now then with the current version?

[syssi]

Could you rephrase your question? Do you own this device model?

[syssi]

There aren't any number entities of the JK04 protocol implemented and tested yet. The switch and button entities should work. I would like to add the support of numbers if you provide some testing.

[linuxdep]

Yes, I own this model, apparently other values such as temperature are also missing. I'll have to see and do some experimenting. Little time at the moment, but doable soon.
I'll read the things through what can be recorded and how to do it.

[syssi]

I'm happy about any input & support to improve the support of this model / the JK04 protocol.