Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
7cb446914a | ||
|
|
084bd39926 | ||
|
|
d5ed9f3388 | ||
|
|
4affade236 | ||
|
|
d9967fc2e5 | ||
|
|
05f7cf2f4e | ||
|
|
ec2aec146b | ||
|
|
5fdaa26eb8 | ||
|
|
d8cd01cb8b | ||
|
|
ab134587c2 | ||
|
|
7c21cba4d1 | ||
|
|
e7bd49e139 | ||
|
|
c199848155 | ||
|
|
3075c9d78c | ||
|
|
deb373eb3f | ||
|
|
4b7c0b17c4 | ||
|
|
91f1af4659 | ||
|
|
db2e19586d | ||
|
|
18d8306de5 | ||
|
|
49c4938052 | ||
|
|
0266f518ee | ||
|
|
93297a3140 | ||
|
|
00109a7c6e | ||
|
|
edbb20b719 | ||
|
|
0576a51842 | ||
|
|
f924af33f4 | ||
|
|
78e8b21977 | ||
|
|
daf2e4fec3 | ||
|
|
b730958aa9 | ||
|
|
463798084c | ||
|
|
8490f9c4ad | ||
|
|
c810ae8f10 | ||
|
|
bcde473157 | ||
|
|
e57196ee5d | ||
|
|
c5086d52ea | ||
|
|
92c177be3b | ||
|
|
32b6e5e8c1 | ||
|
|
dc7470a008 | ||
|
|
0caee3801c | ||
|
|
f3e77c327f | ||
|
|
1888ca31dc | ||
|
|
1a7f83f9ec | ||
|
|
1da3bf9e59 | ||
|
|
6722216f86 | ||
|
|
f081a348e4 | ||
|
|
a3bd991e2f | ||
|
|
e70960cf88 | ||
|
|
0a6e42e1de | ||
|
|
29d4078d1e | ||
|
|
ab5feb1718 | ||
|
|
a343ee32ab | ||
|
|
c0b4fee44f | ||
|
|
47027b0437 | ||
|
|
1804d41f48 | ||
|
|
59cb64181e | ||
|
|
84eb560c66 | ||
|
|
6bc6b5b54e | ||
|
|
2745bf9168 | ||
|
|
da8e3f0200 | ||
|
|
e8cdadce56 | ||
|
|
eaf65ded61 | ||
|
|
547b824b5e | ||
|
|
a3fe73c3a2 | ||
|
|
610309debf | ||
|
|
c55ba4785c | ||
|
|
a9394095d2 | ||
|
|
a6536155c4 | ||
|
|
ea30ea145c | ||
|
|
7c5523eaf4 | ||
|
|
b2c5f65478 | ||
|
|
de6d37e308 | ||
|
|
7e8b88f841 | ||
|
|
93730d856d | ||
|
|
942b7c6fbb | ||
|
|
d1e976123b | ||
|
|
f4f2957558 | ||
|
|
b2f4fb5b87 | ||
|
|
147a176748 | ||
|
|
9847a53755 | ||
|
|
9e196afef3 | ||
|
|
8ce4d7d255 | ||
|
|
6cbf9d72d5 | ||
|
|
4fa50d1c5f | ||
|
|
d635c9c0c8 | ||
|
|
e2de6d6724 | ||
|
|
428f9115c9 | ||
|
|
dcbf3e6b8a | ||
|
|
6107f9e365 | ||
|
|
48cf6da6c2 | ||
|
|
af0ac536a2 | ||
|
|
59ad20f447 | ||
|
|
592a19e87c | ||
|
|
a90071bd87 | ||
|
|
46049be161 | ||
|
|
cba6716eeb | ||
|
|
a1a2ce9e19 | ||
|
|
68a7a6aac6 | ||
|
|
cc2e3fc0eb | ||
|
|
f1f22aa559 | ||
|
|
866c4b39a0 | ||
|
|
3e4c9e18af | ||
|
|
d6f211fdd3 | ||
|
|
fbea8d3ffc | ||
|
|
beb9139d90 | ||
|
|
ff8ab4f21e | ||
|
|
22c0336e8e | ||
|
|
67ef67995a | ||
|
|
e5645d3bfb | ||
|
|
91d421af8d | ||
|
|
b72f2aa40e | ||
|
|
740f226954 | ||
|
|
a94209f5cb | ||
|
|
2e6bd3dddc | ||
|
|
14d249d2d9 | ||
|
|
4e196395e1 | ||
|
|
b92bdfbb2a | ||
|
|
d01de31f7a | ||
|
|
7aefccb33b | ||
|
|
324491e48d | ||
|
|
356bebbf33 | ||
|
|
36ab3f0ce5 | ||
|
|
bcc36b78fd | ||
|
|
ffcc78f711 | ||
|
|
65a2729073 | ||
|
|
083e0daf87 | ||
|
|
54b53294c2 | ||
|
|
28de17c39d | ||
|
|
0f862b2d68 | ||
|
|
9c8892b069 | ||
|
|
7548b75c2f | ||
|
|
308fab7b6e | ||
|
|
fffd7c6087 | ||
|
|
7aa033dd12 | ||
|
|
c2f9a2b388 | ||
|
|
60e96b1cd8 | ||
|
|
39d0ad54d0 | ||
|
|
c451514d4d | ||
|
|
19606eb860 |
No files matched your search
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.30
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -59,10 +59,10 @@ views:
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
yellow: -2500
|
||||
red: -5000
|
||||
max: 5000
|
||||
min: -5000
|
||||
yellow: -5000
|
||||
red: -10000
|
||||
max: 10000
|
||||
min: -10000
|
||||
name: Power
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -130,8 +130,8 @@ views:
|
||||
entity: binary_sensor.yambms_demo_inverter_communication_status
|
||||
name: Inverter comm. status
|
||||
- type: tile
|
||||
entity: binary_sensor.yambms_demo_esp32_online_status
|
||||
name: ESP32 status
|
||||
entity: binary_sensor.yambms_demo_board_online_status
|
||||
name: Board status
|
||||
- type: tile
|
||||
entity: sensor.yambms_demo_yambms_1_charging_status
|
||||
name: Charging Status
|
||||
@@ -175,10 +175,10 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 2
|
||||
- type: tile
|
||||
entity: sensor.yambms_demo_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
entity: sensor.yambms_demo_board_uptime
|
||||
name: Board Uptime
|
||||
- type: tile
|
||||
entity: sensor.yambms_demo_esp32_esphome_version
|
||||
entity: sensor.yambms_demo_board_esphome_version
|
||||
name: ESPHome version
|
||||
- type: entities
|
||||
entities:
|
||||
@@ -206,35 +206,35 @@ views:
|
||||
heading: BMS control
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_bms_1_online_status
|
||||
- entity: switch.yambms_demo_bms_1_charge_switch
|
||||
- entity: switch.yambms_demo_bms_1_discharge_switch
|
||||
- entity: switch.yambms_demo_bms_1_balance_switch
|
||||
- entity: switch.bms_1_online_status_switch
|
||||
- entity: switch.bms_1_charge_switch
|
||||
- entity: switch.bms_1_discharge_switch
|
||||
- entity: switch.bms_1_balance_switch
|
||||
title: BMS 1
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_bms_2_online_status
|
||||
- entity: switch.yambms_demo_bms_2_charge_switch
|
||||
- entity: switch.yambms_demo_bms_2_discharge_switch
|
||||
- entity: switch.yambms_demo_bms_2_balance_switch
|
||||
- entity: switch.bms_2_online_status_switch
|
||||
- entity: switch.bms_2_charge_switch
|
||||
- entity: switch.bms_2_discharge_switch
|
||||
- entity: switch.bms_2_balance_switch
|
||||
title: BMS 2
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_bms_3_online_status
|
||||
- entity: switch.yambms_demo_bms_3_charge_switch
|
||||
- entity: switch.yambms_demo_bms_3_discharge_switch
|
||||
- entity: switch.yambms_demo_bms_3_balance_switch
|
||||
- entity: switch.bms_3_online_status_switch
|
||||
- entity: switch.bms_3_charge_switch
|
||||
- entity: switch.bms_3_discharge_switch
|
||||
- entity: switch.bms_3_balance_switch
|
||||
title: BMS 3
|
||||
- title: Control
|
||||
cards:
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: select.yambms_demo_canbus_1_bms_name
|
||||
name: CANBUS 1 BMS Name
|
||||
- entity: select.yambms_demo_canbus_1_protocol
|
||||
name: CANBUS 1 Protocol
|
||||
- entity: select.yambms_demo_rs485_1_protocol
|
||||
name: RS485 1 Protocol
|
||||
- entity: select.canbus_1_yambms_name
|
||||
name: CANBUS YamBMS name
|
||||
- entity: select.canbus_1_yambms_protocol
|
||||
name: CANBUS YamBMS protocol
|
||||
- entity: select.rs485_1_yambms_protocol
|
||||
name: RS485 YamBMS protocol
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
@@ -293,6 +293,27 @@ views:
|
||||
- entity: number.yambms_demo_yambms_1_auto_float_voltage_step
|
||||
name: Voltage Step
|
||||
title: YamBMS - Auto Float
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_yambms_1_automatic_eoc_current
|
||||
name: Automatic EOC Current
|
||||
- entity: sensor.yambms_demo_yambms_1_auto_eoc_status
|
||||
name: Status
|
||||
- entity: sensor.yambms_demo_yambms_1_auto_eoc_current
|
||||
name: Required Current
|
||||
- entity: number.yambms_demo_yambms_1_auto_eoc_target_hour
|
||||
name: Target hour
|
||||
- entity: number.yambms_demo_yambms_1_auto_eoc_target_minute
|
||||
name: Target minute
|
||||
- entity: number.yambms_demo_yambms_1_auto_eoc_correction
|
||||
name: Current Correction
|
||||
- entity: number.yambms_demo_yambms_1_auto_eoc_capacity_modifier
|
||||
name: Capacity Modifier
|
||||
- entity: number.yambms_demo_yambms_1_auto_eoc_increase_stop_hours
|
||||
name: Stop hours
|
||||
- entity: number.yambms_demo_yambms_1_auto_eoc_increase_stop_soc
|
||||
name: Stop SoC
|
||||
title: YamBMS - Auto EOC
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: number.yambms_demo_yambms_1_rebulk_soc
|
||||
@@ -304,11 +325,17 @@ views:
|
||||
title: YamBMS - ReBulk
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: number.yambms_demo_yambms_1_max_charge_current_percent
|
||||
name: Max charge current (%)
|
||||
- entity: number.yambms_demo_yambms_1_max_discharge_current_percent
|
||||
name: Max discharge current (%)
|
||||
title: YamBMS - Max current (%)
|
||||
- entity: number.yambms_demo_yambms_1_max_requested_charge_current
|
||||
name: Max charge current
|
||||
- entity: number.yambms_demo_yambms_1_max_requested_discharge_current
|
||||
name: Max discharge current
|
||||
- entity: switch.yambms_demo_yambms_1_temperature_based_current_limitation
|
||||
name: Temperature-based current limitation
|
||||
- entity: sensor.yambms_demo_yambms_1_ccl_derating_reason
|
||||
name: CCL Derating Reason
|
||||
- entity: sensor.yambms_demo_yambms_1_dcl_derating_reason
|
||||
name: DCL Derating Reason
|
||||
title: YamBMS - Max requested current
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_yambms_1_request_force_charge
|
||||
@@ -335,29 +362,29 @@ views:
|
||||
entities:
|
||||
- entity: sensor.yambms_demo_yambms_1_last_complete_charge
|
||||
name: Last Complete Charge
|
||||
- entity: binary_sensor.yambms_demo_esp32_online_status
|
||||
name: ESP32 Online Status
|
||||
- entity: sensor.yambms_demo_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
- entity: sensor.yambms_demo_esp32_esphome_version
|
||||
name: ESP32 ESPHome version
|
||||
- entity: button.yambms_demo_esp32_restart
|
||||
name: ESP32 Restart
|
||||
- entity: binary_sensor.yambms_demo_board_online_status
|
||||
name: Board Online Status
|
||||
- entity: sensor.yambms_demo_board_uptime
|
||||
name: Board Uptime
|
||||
- entity: sensor.yambms_demo_board_esphome_version
|
||||
name: Board ESPHome version
|
||||
- entity: button.yambms_demo_board_restart
|
||||
name: Board Restart
|
||||
title: YamBMS - Diagnostic
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: binary_sensor.yambms_demo_canbus_1_status
|
||||
name: CANBUS 1 Status
|
||||
- entity: switch.yambms_demo_canbus_1_inverter_heartbeat_monitoring
|
||||
name: CANBUS 1 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.yambms_demo_canbus_1_inverter_heartbeat
|
||||
name: CANBUS 1 Inverter Heartbeat
|
||||
- entity: binary_sensor.yambms_demo_rs485_1_status
|
||||
name: RS485 1 Status
|
||||
- entity: switch.yambms_demo_rs485_1_inverter_heartbeat_monitoring
|
||||
name: RS485 1 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.yambms_demo_rs485_1_inverter_heartbeat
|
||||
name: RS485 1 Inverter Heartbeat
|
||||
- entity: binary_sensor.canbus_1_status
|
||||
name: CANBUS Status
|
||||
- entity: switch.canbus_1_inverter_heartbeat_monitoring
|
||||
name: CANBUS Inverter Heartbeat Monitoring
|
||||
- entity: sensor.canbus_1_inverter_heartbeat
|
||||
name: CANBUS Inverter Heartbeat
|
||||
- entity: binary_sensor.rs485_1_status
|
||||
name: RS485 Status
|
||||
- entity: switch.rs485_1_inverter_heartbeat_monitoring
|
||||
name: RS485 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.rs485_1_inverter_heartbeat
|
||||
name: RS485 Inverter Heartbeat
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
@@ -365,25 +392,25 @@ views:
|
||||
title: YamBMS - Inverter Status & Heartbeat
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: sensor.yambms_demo_debug_free_psram_percent
|
||||
- entity: sensor.yambms_demo_board_debug_free_psram_percent
|
||||
name: Debug Free PSRAM (%)
|
||||
- entity: sensor.yambms_demo_debug_free_psram
|
||||
- entity: sensor.yambms_demo_board_debug_free_psram
|
||||
name: Debug Free PSRAM
|
||||
- entity: sensor.yambms_demo_debug_heap_free_percent
|
||||
- entity: sensor.yambms_demo_board_debug_heap_free_percent
|
||||
name: Debug Heap free (%)
|
||||
- entity: sensor.yambms_demo_debug_heap_free
|
||||
- entity: sensor.yambms_demo_board_debug_heap_free
|
||||
name: Debug Heap free
|
||||
- entity: sensor.yambms_demo_debug_heap_max_block_percent
|
||||
- entity: sensor.yambms_demo_board_debug_heap_max_block_percent
|
||||
name: Debug Heap max block (%)
|
||||
- entity: sensor.yambms_demo_debug_heap_max_block
|
||||
- entity: sensor.yambms_demo_board_debug_heap_max_block
|
||||
name: Debug Heap max block
|
||||
- entity: sensor.yambms_demo_debug_loop_time
|
||||
- entity: sensor.yambms_demo_board_debug_loop_time
|
||||
name: Debug Loop time
|
||||
- entity: sensor.yambms_demo_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
- entity: sensor.yambms_demo_esp32_esphome_version
|
||||
name: ESPHome version
|
||||
- entity: sensor.yambms_demo_debug_reset_reason
|
||||
- entity: sensor.yambms_demo_board_uptime
|
||||
name: Board Uptime
|
||||
- entity: sensor.yambms_demo_board_esphome_version
|
||||
name: Board ESPHome version
|
||||
- entity: sensor.yambms_demo_board_debug_reset_reason
|
||||
name: Debug Reset reason
|
||||
conditions:
|
||||
- condition: state
|
||||
@@ -404,14 +431,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_demo_bms_1_online_status
|
||||
entity: binary_sensor.bms_1_online_status
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_demo_bms_1_can_be_combined
|
||||
entity: binary_sensor.bms_1_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -439,48 +466,42 @@ views:
|
||||
cards:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('switch.yambms_demo_bms_1_charge_switch', rounded=True)
|
||||
== 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_1_charge_switch', rounded=True)
|
||||
| upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_1_charge_switch', rounded=True)
|
||||
| upper }}</font> {% endif %}
|
||||
<center>Charge : <b>{% if states('switch.bms_1_charge_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.bms_1_charge_switch', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.bms_1_charge_switch', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('switch.yambms_demo_bms_1_discharge_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_1_discharge_switch',
|
||||
rounded=True) | upper }}</font> {% else %} <font
|
||||
color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_1_discharge_switch',
|
||||
rounded=True) | upper }}</font> {% endif %}
|
||||
states('switch.bms_1_discharge_switch', rounded=True) == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('switch.bms_1_discharge_switch', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.bms_1_discharge_switch', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('switch.yambms_demo_bms_1_balance_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_1_balance_switch',
|
||||
states('switch.bms_1_balance_switch', rounded=True) == 'on' %}
|
||||
<font color=#41CD52>{{ states('switch.bms_1_balance_switch',
|
||||
rounded=True) | upper }}</font> {% else %} <font
|
||||
color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_1_balance_switch',
|
||||
color=#3090C7>{{ states('switch.bms_1_balance_switch',
|
||||
rounded=True) | upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_1_total_voltage', rounded=True)
|
||||
}} V</font></b>
|
||||
states('sensor.bms_1_total_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_1_current', rounded=True) }}
|
||||
A</font></b>
|
||||
states('sensor.bms_1_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_1_power', rounded=True) }}
|
||||
W</font>
|
||||
states('sensor.bms_1_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -488,36 +509,34 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font color=#41CD52
|
||||
size=4>{{ states('sensor.yambms_demo_bms_1_battery_soc',
|
||||
rounded=True) }} %</font></font>
|
||||
size=4>{{ states('sensor.bms_1_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font color=#41CD52
|
||||
size=4>{{ states('sensor.yambms_demo_bms_1_battery_soh',
|
||||
rounded=True) }} %</font></font>
|
||||
size=4>{{ states('sensor.bms_1_battery_soh', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_1_battery_capacity',
|
||||
rounded=True) }} Ah</font><br> Cycle Capacity
|
||||
: <font color=#41CD52>12532 Ah</font><br> Ave. Cell
|
||||
Vol. : <font color=#41CD52>3.329 V</font><br>
|
||||
Balance Cur. : <font color=#41CD52>0.00
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_1_max_temperature',
|
||||
rounded=True) }} °C</font>
|
||||
states('sensor.bms_1_battery_capacity', rounded=True) }}
|
||||
Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>12532 Ah</font><br> Ave. Cell Vol.
|
||||
: <font color=#41CD52>3.329 V</font><br> Balance
|
||||
Cur. : <font color=#41CD52>0.00 A</font><br> Max
|
||||
temp. : <font color=#41CD52>{{
|
||||
states('number.bms_1_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_1_capacity_remaining',
|
||||
states('sensor.bms_1_battery_capacity_remaining',
|
||||
rounded=True) }} Ah</font><br> Cycle Count : <font
|
||||
color=#41CD52> {{
|
||||
states('sensor.yambms_demo_bms_1_charging_cycles',
|
||||
color=#41CD52> {{ states('sensor.bms_1_charging_cycles',
|
||||
rounded=True) }}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>0.007 V</font><br> MOS temp. : <font
|
||||
color=#41CD52>25.6 °C</font><br> Min temp. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_1_min_temperature',
|
||||
color=#41CD52>{{ states('number.bms_1_min_temperature',
|
||||
rounded=True) }} °C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -535,21 +554,16 @@ views:
|
||||
11. 3.311 V / 0.050 Ω<br> 12. 3.312 V / 0.050 Ω<br> 13. 3.313
|
||||
V / 0.050 Ω<br> 14. 3.314 V / 0.050 Ω<br> 15. 3.315 V / 0.050
|
||||
Ω<br> 16. 3.316 V / 0.050 Ω<br> </center>
|
||||
- type: entity-filter
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_bms_1_charge_switch
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_demo_bms_1_discharge_switch
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_demo_bms_1_balance_switch
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_demo_bms_1_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_demo_bms_1_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
- entity: switch.bms_1_online_status_switch
|
||||
- entity: switch.bms_1_charge_switch
|
||||
- entity: switch.bms_1_discharge_switch
|
||||
- entity: switch.bms_1_balance_switch
|
||||
- entity: number.bms_1_min_cell_voltage
|
||||
- entity: number.bms_1_max_cell_voltage
|
||||
- entity: number.bms_1_min_temperature
|
||||
- entity: number.bms_1_max_temperature
|
||||
- type: grid
|
||||
column_span: 1
|
||||
cards:
|
||||
@@ -560,14 +574,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_demo_bms_2_online_status
|
||||
entity: binary_sensor.bms_2_online_status
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_demo_bms_2_can_be_combined
|
||||
entity: binary_sensor.bms_2_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -595,48 +609,42 @@ views:
|
||||
cards:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('switch.yambms_demo_bms_2_charge_switch', rounded=True)
|
||||
== 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_2_charge_switch', rounded=True)
|
||||
| upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_2_charge_switch', rounded=True)
|
||||
| upper }}</font> {% endif %}
|
||||
<center>Charge : <b>{% if states('switch.bms_2_charge_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.bms_2_charge_switch', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.bms_2_charge_switch', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('switch.yambms_demo_bms_2_discharge_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_2_discharge_switch',
|
||||
rounded=True) | upper }}</font> {% else %} <font
|
||||
color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_2_discharge_switch',
|
||||
rounded=True) | upper }}</font> {% endif %}
|
||||
states('switch.bms_2_discharge_switch', rounded=True) == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('switch.bms_2_discharge_switch', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.bms_2_discharge_switch', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('switch.yambms_demo_bms_2_balance_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_2_balance_switch',
|
||||
states('switch.bms_2_balance_switch', rounded=True) == 'on' %}
|
||||
<font color=#41CD52>{{ states('switch.bms_2_balance_switch',
|
||||
rounded=True) | upper }}</font> {% else %} <font
|
||||
color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_2_balance_switch',
|
||||
color=#3090C7>{{ states('switch.bms_2_balance_switch',
|
||||
rounded=True) | upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_2_total_voltage', rounded=True)
|
||||
}} V</font></b>
|
||||
states('sensor.bms_2_total_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_2_current', rounded=True) }}
|
||||
A</font></b>
|
||||
states('sensor.bms_2_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_2_power', rounded=True) }}
|
||||
W</font>
|
||||
states('sensor.bms_2_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -644,36 +652,34 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font color=#41CD52
|
||||
size=4>{{ states('sensor.yambms_demo_bms_2_battery_soc',
|
||||
rounded=True) }} %</font></font>
|
||||
size=4>{{ states('sensor.bms_2_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font color=#41CD52
|
||||
size=4>{{ states('sensor.yambms_demo_bms_2_battery_soh',
|
||||
rounded=True) }} %</font></font>
|
||||
size=4>{{ states('sensor.bms_2_battery_soh', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_2_battery_capacity',
|
||||
rounded=True) }} Ah</font><br> Cycle Capacity
|
||||
: <font color=#41CD52>12532 Ah</font><br> Ave. Cell
|
||||
Vol. : <font color=#41CD52>3.329 V</font><br>
|
||||
Balance Cur. : <font color=#41CD52>0.00
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_2_max_temperature',
|
||||
rounded=True) }} °C</font>
|
||||
states('sensor.bms_2_battery_capacity', rounded=True) }}
|
||||
Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>12532 Ah</font><br> Ave. Cell Vol.
|
||||
: <font color=#41CD52>3.329 V</font><br> Balance
|
||||
Cur. : <font color=#41CD52>0.00 A</font><br> Max
|
||||
temp. : <font color=#41CD52>{{
|
||||
states('number.bms_2_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_2_capacity_remaining',
|
||||
states('sensor.bms_2_battery_capacity_remaining',
|
||||
rounded=True) }} Ah</font><br> Cycle Count : <font
|
||||
color=#41CD52> {{
|
||||
states('sensor.yambms_demo_bms_2_charging_cycles',
|
||||
color=#41CD52> {{ states('sensor.bms_2_charging_cycles',
|
||||
rounded=True) }}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>0.007 V</font><br> MOS temp. : <font
|
||||
color=#41CD52>25.6 °C</font><br> Min temp. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_2_min_temperature',
|
||||
color=#41CD52>{{ states('number.bms_2_min_temperature',
|
||||
rounded=True) }} °C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -691,21 +697,16 @@ views:
|
||||
11. 3.311 V / 0.050 Ω<br> 12. 3.312 V / 0.050 Ω<br> 13. 3.313
|
||||
V / 0.050 Ω<br> 14. 3.314 V / 0.050 Ω<br> 15. 3.315 V / 0.050
|
||||
Ω<br> 16. 3.316 V / 0.050 Ω<br> </center>
|
||||
- type: entity-filter
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_bms_2_charge_switch
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_demo_bms_2_discharge_switch
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_demo_bms_2_balance_switch
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_demo_bms_2_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_demo_bms_2_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
- entity: switch.bms_2_online_status_switch
|
||||
- entity: switch.bms_2_charge_switch
|
||||
- entity: switch.bms_2_discharge_switch
|
||||
- entity: switch.bms_2_balance_switch
|
||||
- entity: number.bms_2_min_cell_voltage
|
||||
- entity: number.bms_2_max_cell_voltage
|
||||
- entity: number.bms_2_min_temperature
|
||||
- entity: number.bms_2_max_temperature
|
||||
- type: grid
|
||||
column_span: 1
|
||||
cards:
|
||||
@@ -716,14 +717,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_demo_bms_3_online_status
|
||||
entity: binary_sensor.bms_3_online_status
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_demo_bms_3_can_be_combined
|
||||
entity: binary_sensor.bms_3_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -751,48 +752,42 @@ views:
|
||||
cards:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('switch.yambms_demo_bms_3_charge_switch', rounded=True)
|
||||
== 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_3_charge_switch', rounded=True)
|
||||
| upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_3_charge_switch', rounded=True)
|
||||
| upper }}</font> {% endif %}
|
||||
<center>Charge : <b>{% if states('switch.bms_3_charge_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.bms_3_charge_switch', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.bms_3_charge_switch', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('switch.yambms_demo_bms_3_discharge_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_3_discharge_switch',
|
||||
rounded=True) | upper }}</font> {% else %} <font
|
||||
color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_3_discharge_switch',
|
||||
rounded=True) | upper }}</font> {% endif %}
|
||||
states('switch.bms_3_discharge_switch', rounded=True) == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('switch.bms_3_discharge_switch', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('switch.bms_3_discharge_switch', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('switch.yambms_demo_bms_3_balance_switch',
|
||||
rounded=True) == 'on' %} <font color=#41CD52>{{
|
||||
states('switch.yambms_demo_bms_3_balance_switch',
|
||||
states('switch.bms_3_balance_switch', rounded=True) == 'on' %}
|
||||
<font color=#41CD52>{{ states('switch.bms_3_balance_switch',
|
||||
rounded=True) | upper }}</font> {% else %} <font
|
||||
color=#3090C7>{{
|
||||
states('switch.yambms_demo_bms_3_balance_switch',
|
||||
color=#3090C7>{{ states('switch.bms_3_balance_switch',
|
||||
rounded=True) | upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_3_total_voltage', rounded=True)
|
||||
}} V</font></b>
|
||||
states('sensor.bms_3_total_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_3_current', rounded=True) }}
|
||||
A</font></b>
|
||||
states('sensor.bms_3_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_demo_bms_3_power', rounded=True) }}
|
||||
W</font>
|
||||
states('sensor.bms_3_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -800,36 +795,34 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font color=#41CD52
|
||||
size=4>{{ states('sensor.yambms_demo_bms_3_battery_soc',
|
||||
rounded=True) }} %</font></font>
|
||||
size=4>{{ states('sensor.bms_3_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font color=#41CD52
|
||||
size=4>{{ states('sensor.yambms_demo_bms_3_battery_soh',
|
||||
rounded=True) }} %</font></font>
|
||||
size=4>{{ states('sensor.bms_3_battery_soh', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_3_battery_capacity',
|
||||
rounded=True) }} Ah</font><br> Cycle Capacity
|
||||
: <font color=#41CD52>12532 Ah</font><br> Ave. Cell
|
||||
Vol. : <font color=#41CD52>3.329 V</font><br>
|
||||
Balance Cur. : <font color=#41CD52>0.00
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_3_max_temperature',
|
||||
rounded=True) }} °C</font>
|
||||
states('sensor.bms_3_battery_capacity', rounded=True) }}
|
||||
Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>12532 Ah</font><br> Ave. Cell Vol.
|
||||
: <font color=#41CD52>3.329 V</font><br> Balance
|
||||
Cur. : <font color=#41CD52>0.00 A</font><br> Max
|
||||
temp. : <font color=#41CD52>{{
|
||||
states('number.bms_3_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_3_capacity_remaining',
|
||||
states('sensor.bms_3_battery_capacity_remaining',
|
||||
rounded=True) }} Ah</font><br> Cycle Count : <font
|
||||
color=#41CD52> {{
|
||||
states('sensor.yambms_demo_bms_3_charging_cycles',
|
||||
color=#41CD52> {{ states('sensor.bms_3_charging_cycles',
|
||||
rounded=True) }}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>0.007 V</font><br> MOS temp. : <font
|
||||
color=#41CD52>25.6 °C</font><br> Min temp. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_demo_bms_3_min_temperature',
|
||||
color=#41CD52>{{ states('number.bms_3_min_temperature',
|
||||
rounded=True) }} °C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -847,21 +840,16 @@ views:
|
||||
11. 3.311 V / 0.050 Ω<br> 12. 3.312 V / 0.050 Ω<br> 13. 3.313
|
||||
V / 0.050 Ω<br> 14. 3.314 V / 0.050 Ω<br> 15. 3.315 V / 0.050
|
||||
Ω<br> 16. 3.316 V / 0.050 Ω<br> </center>
|
||||
- type: entity-filter
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_bms_3_charge_switch
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_demo_bms_3_discharge_switch
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_demo_bms_3_balance_switch
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_demo_bms_3_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_demo_bms_3_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
- entity: switch.bms_3_online_status_switch
|
||||
- entity: switch.bms_3_charge_switch
|
||||
- entity: switch.bms_3_discharge_switch
|
||||
- entity: switch.bms_3_balance_switch
|
||||
- entity: number.bms_3_min_cell_voltage
|
||||
- entity: number.bms_3_max_cell_voltage
|
||||
- entity: number.bms_3_min_temperature
|
||||
- entity: number.bms_3_max_temperature
|
||||
- title: Shunt
|
||||
type: sections
|
||||
max_columns: 3
|
||||
@@ -872,7 +860,7 @@ views:
|
||||
heading: Shunt 1
|
||||
- graph: line
|
||||
type: sensor
|
||||
entity: sensor.yambms_demo_shunt_1_voltage
|
||||
entity: sensor.shunt_1_voltage
|
||||
detail: 2
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -881,12 +869,12 @@ views:
|
||||
hours_to_show: 8
|
||||
- graph: line
|
||||
type: sensor
|
||||
entity: sensor.yambms_demo_shunt_1_state_of_charge
|
||||
entity: sensor.shunt_1_state_of_charge
|
||||
detail: 2
|
||||
name: SoC
|
||||
hours_to_show: 8
|
||||
- type: gauge
|
||||
entity: sensor.yambms_demo_shunt_1_current
|
||||
entity: sensor.shunt_1_current
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
@@ -899,7 +887,7 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 3
|
||||
- type: gauge
|
||||
entity: sensor.yambms_demo_shunt_1_power
|
||||
entity: sensor.shunt_1_power
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
@@ -913,29 +901,29 @@ views:
|
||||
grid_rows: 3
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: sensor.yambms_demo_shunt_1_voltage
|
||||
- entity: sensor.shunt_1_voltage
|
||||
name: Shunt 1 Voltage
|
||||
- entity: sensor.yambms_demo_shunt_1_current
|
||||
- entity: sensor.shunt_1_current
|
||||
name: Shunt 1 Current
|
||||
- entity: sensor.yambms_demo_shunt_1_power
|
||||
- entity: sensor.shunt_1_power
|
||||
name: Shunt 1 Power
|
||||
- entity: sensor.yambms_demo_shunt_1_state_of_charge
|
||||
- entity: sensor.shunt_1_state_of_charge
|
||||
name: Shunt 1 SoC
|
||||
- entity: sensor.yambms_demo_shunt_1_temperature
|
||||
- entity: sensor.shunt_1_temperature
|
||||
name: Shunt 1 Temperature
|
||||
- entity: sensor.yambms_demo_shunt_1_charged_power
|
||||
- entity: sensor.shunt_1_charged_power
|
||||
name: Shunt 1 Charged Power
|
||||
- entity: sensor.yambms_demo_shunt_1_discharged_power
|
||||
- entity: sensor.shunt_1_discharged_power
|
||||
name: Shunt 1 Discharged Power
|
||||
- entity: sensor.yambms_demo_shunt_1_battery_capacity
|
||||
- entity: sensor.shunt_1_battery_capacity
|
||||
name: Shunt 1 Battery Capacity
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_demo_shunt_1_combine_enabled
|
||||
- entity: switch.shunt_1_combine_enabled
|
||||
name: Shunt 1 Combine enabled
|
||||
- entity: binary_sensor.yambms_demo_shunt_1_can_be_combined
|
||||
- entity: binary_sensor.shunt_1_can_be_combined
|
||||
name: Shunt 1 Can be combined
|
||||
column_span: 1
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.14
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -59,10 +59,10 @@ views:
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
yellow: -2500
|
||||
red: -5000
|
||||
max: 5000
|
||||
min: -5000
|
||||
yellow: -5000
|
||||
red: -10000
|
||||
max: 10000
|
||||
min: -10000
|
||||
name: Power
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -130,8 +130,8 @@ views:
|
||||
entity: binary_sensor.yambms_inverter_communication_status
|
||||
name: Inverter comm. status
|
||||
- type: tile
|
||||
entity: binary_sensor.yambms_esp32_online_status
|
||||
name: ESP32 status
|
||||
entity: binary_sensor.yambms_board_online_status
|
||||
name: Board status
|
||||
- type: tile
|
||||
entity: sensor.yambms_yambms_1_charging_status
|
||||
name: Charging Status
|
||||
@@ -175,10 +175,10 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 2
|
||||
- type: tile
|
||||
entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- type: tile
|
||||
entity: sensor.yambms_esp32_esphome_version
|
||||
entity: sensor.yambms_board_esphome_version
|
||||
name: ESPHome version
|
||||
- type: entities
|
||||
entities:
|
||||
@@ -203,12 +203,12 @@ views:
|
||||
cards:
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: select.yambms_canbus_1_bms_name
|
||||
name: CANBUS 1 BMS Name
|
||||
- entity: select.yambms_canbus_1_protocol
|
||||
name: CANBUS 1 Protocol
|
||||
- entity: select.yambms_rs485_1_protocol
|
||||
name: RS485 1 Protocol
|
||||
- entity: select.canbus_1_yambms_name
|
||||
name: CANBUS YamBMS name
|
||||
- entity: select.canbus_1_yambms_protocol
|
||||
name: CANBUS YamBMS protocol
|
||||
- entity: select.rs485_1_yambms_protocol
|
||||
name: RS485 YamBMS protocol
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
@@ -267,6 +267,27 @@ views:
|
||||
- entity: number.yambms_yambms_1_auto_float_voltage_step
|
||||
name: Voltage Step
|
||||
title: YamBMS - Auto Float
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_yambms_1_automatic_eoc_current
|
||||
name: Automatic EOC Current
|
||||
- entity: sensor.yambms_yambms_1_auto_eoc_status
|
||||
name: Status
|
||||
- entity: sensor.yambms_yambms_1_auto_eoc_current
|
||||
name: Required Current
|
||||
- entity: number.yambms_yambms_1_auto_eoc_target_hour
|
||||
name: Target hour
|
||||
- entity: number.yambms_yambms_1_auto_eoc_target_minute
|
||||
name: Target minute
|
||||
- entity: number.yambms_yambms_1_auto_eoc_correction
|
||||
name: Current Correction
|
||||
- entity: number.yambms_yambms_1_auto_eoc_capacity_modifier
|
||||
name: Capacity Modifier
|
||||
- entity: number.yambms_yambms_1_auto_eoc_increase_stop_hours
|
||||
name: Stop hours
|
||||
- entity: number.yambms_yambms_1_auto_eoc_increase_stop_soc
|
||||
name: Stop SoC
|
||||
title: YamBMS - Auto EOC
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: number.yambms_yambms_1_rebulk_soc
|
||||
@@ -278,11 +299,17 @@ views:
|
||||
title: YamBMS - ReBulk
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: number.yambms_yambms_1_max_charge_current_percent
|
||||
name: Max charge current (%)
|
||||
- entity: number.yambms_yambms_1_max_discharge_current_percent
|
||||
name: Max discharge current (%)
|
||||
title: YamBMS - Max current (%)
|
||||
- entity: number.yambms_yambms_1_max_requested_charge_current
|
||||
name: Max charge current
|
||||
- entity: number.yambms_yambms_1_max_requested_discharge_current
|
||||
name: Max discharge current
|
||||
- entity: switch.yambms_yambms_1_temperature_based_current_limitation
|
||||
name: Temperature-based current limitation
|
||||
- entity: sensor.yambms_yambms_1_ccl_derating_reason
|
||||
name: CCL Derating Reason
|
||||
- entity: sensor.yambms_yambms_1_dcl_derating_reason
|
||||
name: DCL Derating Reason
|
||||
title: YamBMS - Max requested current
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_yambms_1_request_force_charge
|
||||
@@ -309,29 +336,29 @@ views:
|
||||
entities:
|
||||
- entity: sensor.yambms_yambms_1_last_complete_charge
|
||||
name: Last Complete Charge
|
||||
- entity: binary_sensor.yambms_esp32_online_status
|
||||
name: ESP32 Online Status
|
||||
- entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
- entity: sensor.yambms_esp32_esphome_version
|
||||
name: ESP32 ESPHome version
|
||||
- entity: button.yambms_esp32_restart
|
||||
name: ESP32 Restart
|
||||
- entity: binary_sensor.yambms_board_online_status
|
||||
name: Board Online Status
|
||||
- entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- entity: sensor.yambms_board_esphome_version
|
||||
name: Board ESPHome version
|
||||
- entity: button.yambms_board_restart
|
||||
name: Board Restart
|
||||
title: YamBMS - Diagnostic
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: binary_sensor.yambms_canbus_1_status
|
||||
name: CANBUS 1 Status
|
||||
- entity: switch.yambms_canbus_1_inverter_heartbeat_monitoring
|
||||
name: CANBUS 1 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.yambms_canbus_1_inverter_heartbeat
|
||||
name: CANBUS 1 Inverter Heartbeat
|
||||
- entity: binary_sensor.yambms_rs485_1_status
|
||||
name: RS485 1 Status
|
||||
- entity: switch.yambms_rs485_1_inverter_heartbeat_monitoring
|
||||
name: RS485 1 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.yambms_rs485_1_inverter_heartbeat
|
||||
name: RS485 1 Inverter Heartbeat
|
||||
- entity: binary_sensor.canbus_1_status
|
||||
name: CANBUS Status
|
||||
- entity: switch.canbus_1_inverter_heartbeat_monitoring
|
||||
name: CANBUS Inverter Heartbeat Monitoring
|
||||
- entity: sensor.canbus_1_inverter_heartbeat
|
||||
name: CANBUS Inverter Heartbeat
|
||||
- entity: binary_sensor.rs485_1_status
|
||||
name: RS485 Status
|
||||
- entity: switch.rs485_1_inverter_heartbeat_monitoring
|
||||
name: RS485 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.rs485_1_inverter_heartbeat
|
||||
name: RS485 Inverter Heartbeat
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
@@ -353,10 +380,10 @@ views:
|
||||
name: Debug Heap max block
|
||||
- entity: sensor.yambms_debug_loop_time
|
||||
name: Debug Loop time
|
||||
- entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
- entity: sensor.yambms_esp32_esphome_version
|
||||
name: ESPHome version
|
||||
- entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- entity: sensor.yambms_board_esphome_version
|
||||
name: Board ESPHome version
|
||||
- entity: sensor.yambms_debug_reset_reason
|
||||
name: Debug Reset reason
|
||||
conditions:
|
||||
@@ -378,14 +405,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_1_status_online
|
||||
entity: binary_sensor.jk_bms_1_status_online
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_1_can_be_combined
|
||||
entity: binary_sensor.jk_bms_1_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -396,7 +423,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Time : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_1_total_runtime_formatted', rounded=True)
|
||||
states('sensor.jk_bms_1_total_runtime_formatted', rounded=True)
|
||||
| upper }}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -408,7 +435,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Error : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_1_errors', rounded=True)}}</font>
|
||||
states('sensor.jk_bms_1_errors', rounded=True)}}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
grid_rows: 1
|
||||
@@ -419,43 +446,43 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('binary_sensor.yambms_jk_bms_1_status_charging', rounded=True) == 'on'
|
||||
states('binary_sensor.jk_bms_1_status_charging', rounded=True) == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_status_charging', rounded=True) | upper
|
||||
states('binary_sensor.jk_bms_1_status_charging', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_status_charging', rounded=True) | upper
|
||||
states('binary_sensor.jk_bms_1_status_charging', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_1_status_discharging', rounded=True) ==
|
||||
states('binary_sensor.jk_bms_1_status_discharging', rounded=True) ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_status_discharging', rounded=True) |
|
||||
states('binary_sensor.jk_bms_1_status_discharging', rounded=True) |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_status_discharging', rounded=True) |
|
||||
states('binary_sensor.jk_bms_1_status_discharging', rounded=True) |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_1_status_balancing', rounded=True) ==
|
||||
states('binary_sensor.jk_bms_1_equalizing', rounded=True) ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_status_balancing', rounded=True) |
|
||||
states('binary_sensor.jk_bms_1_equalizing', rounded=True) |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_status_balancing', rounded=True) |
|
||||
states('binary_sensor.jk_bms_1_equalizing', rounded=True) |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_battery_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_1_battery_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_battery_current', rounded=True) }} A</font></b>
|
||||
states('sensor.jk_bms_1_battery_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_battery_power', rounded=True) }} W</font>
|
||||
states('sensor.jk_bms_1_battery_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -464,42 +491,42 @@ views:
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_battery_soc', rounded=True) }}
|
||||
states('sensor.jk_bms_1_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_battery_soh_valuation', rounded=True) }}
|
||||
states('sensor.jk_bms_1_battery_soh_valuation', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('number.yambms_jk_bms_1_battery_capacity_total_setting', rounded=True)
|
||||
states('number.jk_bms_1_battery_capacity_total_setting', rounded=True)
|
||||
}} Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_total_charging_cycle_capacity', rounded=True)
|
||||
states('sensor.jk_bms_1_total_charging_cycle_capacity', rounded=True)
|
||||
}} Ah</font><br> Ave. Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_cell_average_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_1_cell_average_voltage', rounded=True) }}
|
||||
V</font><br> Balance Cur. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_balancing_current', rounded=True) }}
|
||||
states('sensor.jk_bms_1_balancing_current', rounded=True) }}
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_max_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_1_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_battery_capacity_remaining', rounded=True) }}
|
||||
states('sensor.jk_bms_1_battery_capacity_remaining', rounded=True) }}
|
||||
Ah</font><br> Cycle Count : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_charging_cycles', rounded=True)
|
||||
states('sensor.jk_bms_1_charging_cycles', rounded=True)
|
||||
}}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_cell_delta_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_1_cell_delta_voltage', rounded=True) }}
|
||||
V</font><br> MOS temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_temperature_powertube', rounded=True)
|
||||
states('sensor.jk_bms_1_temperature_powertube', rounded=True)
|
||||
}} °C</font><br> Min temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_min_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_1_min_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -525,14 +552,14 @@ views:
|
||||
|
||||
<center>
|
||||
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.jk_bms_1') }}
|
||||
|
||||
</center>
|
||||
- type: markdown
|
||||
@@ -555,27 +582,27 @@ views:
|
||||
|
||||
<center>
|
||||
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.jk_bms_1') }}
|
||||
|
||||
</center>
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: switch.yambms_jk_bms_1_charge_switch
|
||||
- entity: switch.jk_bms_1_charging
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_jk_bms_1_discharge_switch
|
||||
- entity: switch.jk_bms_1_discharging
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_jk_bms_1_balance_switch
|
||||
- entity: switch.jk_bms_1_balancing
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_jk_bms_1_enable_bluetooth_connection
|
||||
- entity: switch.jk_bms_1_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_jk_bms_1_charging_cycles_offset
|
||||
- entity: number.jk_bms_1_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
@@ -590,14 +617,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_2_status_online
|
||||
entity: binary_sensor.jk_bms_2_status_online
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_2_can_be_combined
|
||||
entity: binary_sensor.jk_bms_2_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -608,7 +635,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Time : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_2_total_runtime_formatted', rounded=True)
|
||||
states('sensor.jk_bms_2_total_runtime_formatted', rounded=True)
|
||||
| upper }}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -620,7 +647,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Error : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_2_errors', rounded=True)}}</font>
|
||||
states('sensor.jk_bms_2_errors', rounded=True)}}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
grid_rows: 1
|
||||
@@ -631,43 +658,43 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('binary_sensor.yambms_jk_bms_2_status_charging', rounded=True) == 'on'
|
||||
states('binary_sensor.jk_bms_2_status_charging', rounded=True) == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_status_charging', rounded=True) | upper
|
||||
states('binary_sensor.jk_bms_2_status_charging', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_status_charging', rounded=True) | upper
|
||||
states('binary_sensor.jk_bms_2_status_charging', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_2_status_discharging', rounded=True) ==
|
||||
states('binary_sensor.jk_bms_2_status_discharging', rounded=True) ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_status_discharging', rounded=True) |
|
||||
states('binary_sensor.jk_bms_2_status_discharging', rounded=True) |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_status_discharging', rounded=True) |
|
||||
states('binary_sensor.jk_bms_2_status_discharging', rounded=True) |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_2_status_balancing', rounded=True) ==
|
||||
states('binary_sensor.jk_bms_2_equalizing', rounded=True) ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_status_balancing', rounded=True) |
|
||||
states('binary_sensor.jk_bms_2_equalizing', rounded=True) |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_status_balancing', rounded=True) |
|
||||
states('binary_sensor.jk_bms_2_equalizing', rounded=True) |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_battery_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_2_battery_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_battery_current', rounded=True) }} A</font></b>
|
||||
states('sensor.jk_bms_2_battery_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_battery_power', rounded=True) }} W</font>
|
||||
states('sensor.jk_bms_2_battery_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -676,42 +703,42 @@ views:
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_battery_soc', rounded=True) }}
|
||||
states('sensor.jk_bms_2_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_battery_soh_valuation', rounded=True) }}
|
||||
states('sensor.jk_bms_2_battery_soh_valuation', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('number.yambms_jk_bms_2_battery_capacity_total_setting', rounded=True)
|
||||
states('number.jk_bms_2_battery_capacity_total_setting', rounded=True)
|
||||
}} Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_total_charging_cycle_capacity', rounded=True)
|
||||
states('sensor.jk_bms_2_total_charging_cycle_capacity', rounded=True)
|
||||
}} Ah</font><br> Ave. Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_cell_average_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_2_cell_average_voltage', rounded=True) }}
|
||||
V</font><br> Balance Cur. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_balancing_current', rounded=True) }}
|
||||
states('sensor.jk_bms_2_balancing_current', rounded=True) }}
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_max_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_2_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_battery_capacity_remaining', rounded=True) }}
|
||||
states('sensor.jk_bms_2_battery_capacity_remaining', rounded=True) }}
|
||||
Ah</font><br> Cycle Count : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_charging_cycles', rounded=True)
|
||||
states('sensor.jk_bms_2_charging_cycles', rounded=True)
|
||||
}}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_cell_delta_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_2_cell_delta_voltage', rounded=True) }}
|
||||
V</font><br> MOS temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_temperature_powertube', rounded=True)
|
||||
states('sensor.jk_bms_2_temperature_powertube', rounded=True)
|
||||
}} °C</font><br> Min temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_min_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_2_min_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -737,14 +764,14 @@ views:
|
||||
|
||||
<center>
|
||||
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.jk_bms_2') }}
|
||||
|
||||
</center>
|
||||
- type: markdown
|
||||
@@ -767,27 +794,27 @@ views:
|
||||
|
||||
<center>
|
||||
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.jk_bms_2') }}
|
||||
|
||||
</center>
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: switch.yambms_jk_bms_2_charge_switch
|
||||
- entity: switch.jk_bms_2_charging
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_jk_bms_2_discharge_switch
|
||||
- entity: switch.jk_bms_2_discharging
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_jk_bms_2_balance_switch
|
||||
- entity: switch.jk_bms_2_balancing
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_jk_bms_2_enable_bluetooth_connection
|
||||
- entity: switch.jk_bms_2_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_jk_bms_2_charging_cycles_offset
|
||||
- entity: number.jk_bms_2_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
@@ -802,14 +829,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_3_status_online
|
||||
entity: binary_sensor.jk_bms_3_status_online
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_3_can_be_combined
|
||||
entity: binary_sensor.jk_bms_3_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -820,7 +847,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Time : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_3_total_runtime_formatted', rounded=True)
|
||||
states('sensor.jk_bms_3_total_runtime_formatted', rounded=True)
|
||||
| upper }}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -832,7 +859,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Error : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_3_errors', rounded=True)}}</font>
|
||||
states('sensor.jk_bms_3_errors', rounded=True)}}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
grid_rows: 1
|
||||
@@ -843,43 +870,43 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('binary_sensor.yambms_jk_bms_3_status_charging', rounded=True) == 'on'
|
||||
states('binary_sensor.jk_bms_3_status_charging', rounded=True) == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_status_charging', rounded=True) | upper
|
||||
states('binary_sensor.jk_bms_3_status_charging', rounded=True) | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_status_charging', rounded=True) | upper
|
||||
states('binary_sensor.jk_bms_3_status_charging', rounded=True) | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_3_status_discharging', rounded=True) ==
|
||||
states('binary_sensor.jk_bms_3_status_discharging', rounded=True) ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_status_discharging', rounded=True) |
|
||||
states('binary_sensor.jk_bms_3_status_discharging', rounded=True) |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_status_discharging', rounded=True) |
|
||||
states('binary_sensor.jk_bms_3_status_discharging', rounded=True) |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_3_status_balancing', rounded=True) ==
|
||||
states('binary_sensor.jk_bms_3_equalizing', rounded=True) ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_status_balancing', rounded=True) |
|
||||
states('binary_sensor.jk_bms_3_equalizing', rounded=True) |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_status_balancing', rounded=True) |
|
||||
states('binary_sensor.jk_bms_3_equalizing', rounded=True) |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_battery_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_3_battery_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_battery_current', rounded=True) }} A</font></b>
|
||||
states('sensor.jk_bms_3_battery_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_battery_power', rounded=True) }} W</font>
|
||||
states('sensor.jk_bms_3_battery_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -888,42 +915,42 @@ views:
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_battery_soc', rounded=True) }}
|
||||
states('sensor.jk_bms_3_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_battery_soh_valuation', rounded=True) }}
|
||||
states('sensor.jk_bms_3_battery_soh_valuation', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('number.yambms_jk_bms_3_battery_capacity_total_setting', rounded=True)
|
||||
states('number.jk_bms_3_battery_capacity_total_setting', rounded=True)
|
||||
}} Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_total_charging_cycle_capacity', rounded=True)
|
||||
states('sensor.jk_bms_3_total_charging_cycle_capacity', rounded=True)
|
||||
}} Ah</font><br> Ave. Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_cell_average_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_3_cell_average_voltage', rounded=True) }}
|
||||
V</font><br> Balance Cur. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_balancing_current', rounded=True) }}
|
||||
states('sensor.jk_bms_3_balancing_current', rounded=True) }}
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_max_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_3_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_battery_capacity_remaining', rounded=True) }}
|
||||
states('sensor.jk_bms_3_battery_capacity_remaining', rounded=True) }}
|
||||
Ah</font><br> Cycle Count : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_charging_cycles', rounded=True)
|
||||
states('sensor.jk_bms_3_charging_cycles', rounded=True)
|
||||
}}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_cell_delta_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_3_cell_delta_voltage', rounded=True) }}
|
||||
V</font><br> MOS temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_temperature_powertube', rounded=True)
|
||||
states('sensor.jk_bms_3_temperature_powertube', rounded=True)
|
||||
}} °C</font><br> Min temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_min_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_3_min_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -949,14 +976,14 @@ views:
|
||||
|
||||
<center>
|
||||
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.jk_bms_3') }}
|
||||
|
||||
</center>
|
||||
- type: markdown
|
||||
@@ -979,27 +1006,27 @@ views:
|
||||
|
||||
<center>
|
||||
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.jk_bms_3') }}
|
||||
|
||||
</center>
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: switch.yambms_jk_bms_3_charge_switch
|
||||
- entity: switch.jk_bms_3_charging
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_jk_bms_3_discharge_switch
|
||||
- entity: switch.jk_bms_3_discharging
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_jk_bms_3_balance_switch
|
||||
- entity: switch.jk_bms_3_balancing
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_jk_bms_3_enable_bluetooth_connection
|
||||
- entity: switch.jk_bms_3_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_jk_bms_3_charging_cycles_offset
|
||||
- entity: number.jk_bms_3_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
@@ -1012,7 +1039,7 @@ views:
|
||||
cards:
|
||||
- graph: line
|
||||
type: sensor
|
||||
entity: sensor.yambms_shunt_1_voltage
|
||||
entity: sensor.shunt_1_voltage
|
||||
detail: 2
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -1021,12 +1048,12 @@ views:
|
||||
hours_to_show: 8
|
||||
- graph: line
|
||||
type: sensor
|
||||
entity: sensor.yambms_shunt_1_state_of_charge
|
||||
entity: sensor.shunt_1_state_of_charge
|
||||
detail: 2
|
||||
name: SoC
|
||||
hours_to_show: 8
|
||||
- type: gauge
|
||||
entity: sensor.yambms_shunt_1_current
|
||||
entity: sensor.shunt_1_current
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
@@ -1039,7 +1066,7 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 3
|
||||
- type: gauge
|
||||
entity: sensor.yambms_shunt_1_power
|
||||
entity: sensor.shunt_1_power
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
@@ -1053,30 +1080,30 @@ views:
|
||||
grid_rows: 3
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: sensor.yambms_shunt_1_voltage
|
||||
- entity: sensor.shunt_1_voltage
|
||||
name: Shunt 1 Voltage
|
||||
- entity: sensor.yambms_shunt_1_current
|
||||
- entity: sensor.shunt_1_current
|
||||
name: Shunt 1 Current
|
||||
- entity: sensor.yambms_shunt_1_power
|
||||
- entity: sensor.shunt_1_power
|
||||
name: Shunt 1 Power
|
||||
- entity: sensor.yambms_shunt_1_state_of_charge
|
||||
- entity: sensor.shunt_1_state_of_charge
|
||||
name: Shunt 1 SoC
|
||||
- entity: sensor.yambms_shunt_1_temperature
|
||||
- entity: sensor.shunt_1_temperature
|
||||
name: Shunt 1 Temperature
|
||||
- entity: sensor.yambms_shunt_1_charged_power
|
||||
- entity: sensor.shunt_1_charged_power
|
||||
name: Shunt 1 Charged Power
|
||||
- entity: sensor.yambms_shunt_1_discharged_power
|
||||
- entity: sensor.shunt_1_discharged_power
|
||||
name: Shunt 1 Discharged Power
|
||||
- entity: sensor.yambms_shunt_1_battery_capacity
|
||||
- entity: sensor.shunt_1_battery_capacity
|
||||
name: Shunt 1 Battery Capacity
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_shunt_1_combine_enabled
|
||||
- entity: switch.shunt_1_combine_enabled
|
||||
name: Shunt 1 Combine enabled
|
||||
- entity: binary_sensor.yambms_shunt_1_can_be_combined
|
||||
- entity: binary_sensor.shunt_1_can_be_combined
|
||||
name: Shunt 1 Can be combined
|
||||
title: Shunt 1
|
||||
column_span: 1
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.30
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -59,10 +59,10 @@ views:
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
yellow: -2500
|
||||
red: -5000
|
||||
max: 5000
|
||||
min: -5000
|
||||
yellow: -5000
|
||||
red: -10000
|
||||
max: 10000
|
||||
min: -10000
|
||||
name: Power
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -130,8 +130,8 @@ views:
|
||||
entity: binary_sensor.yambms_inverter_communication_status
|
||||
name: Inverter comm. status
|
||||
- type: tile
|
||||
entity: binary_sensor.yambms_esp32_online_status
|
||||
name: ESP32 status
|
||||
entity: binary_sensor.yambms_board_online_status
|
||||
name: Board status
|
||||
- type: tile
|
||||
entity: sensor.yambms_yambms_1_charging_status
|
||||
name: Charging Status
|
||||
@@ -175,10 +175,10 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 2
|
||||
- type: tile
|
||||
entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- type: tile
|
||||
entity: sensor.yambms_esp32_esphome_version
|
||||
entity: sensor.yambms_board_esphome_version
|
||||
name: ESPHome version
|
||||
- type: entities
|
||||
entities:
|
||||
@@ -203,12 +203,12 @@ views:
|
||||
cards:
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: select.yambms_canbus_1_bms_name
|
||||
name: CANBUS 1 BMS Name
|
||||
- entity: select.yambms_canbus_1_protocol
|
||||
name: CANBUS 1 Protocol
|
||||
- entity: select.yambms_rs485_1_protocol
|
||||
name: RS485 1 Protocol
|
||||
- entity: select.canbus_1_yambms_name
|
||||
name: CANBUS YamBMS name
|
||||
- entity: select.canbus_1_yambms_protocol
|
||||
name: CANBUS YamBMS protocol
|
||||
- entity: select.rs485_1_yambms_protocol
|
||||
name: RS485 YamBMS protocol
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
@@ -267,6 +267,27 @@ views:
|
||||
- entity: number.yambms_yambms_1_auto_float_voltage_step
|
||||
name: Voltage Step
|
||||
title: YamBMS - Auto Float
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_yambms_1_automatic_eoc_current
|
||||
name: Automatic EOC Current
|
||||
- entity: sensor.yambms_yambms_1_auto_eoc_status
|
||||
name: Status
|
||||
- entity: sensor.yambms_yambms_1_auto_eoc_current
|
||||
name: Required Current
|
||||
- entity: number.yambms_yambms_1_auto_eoc_target_hour
|
||||
name: Target hour
|
||||
- entity: number.yambms_yambms_1_auto_eoc_target_minute
|
||||
name: Target minute
|
||||
- entity: number.yambms_yambms_1_auto_eoc_correction
|
||||
name: Current Correction
|
||||
- entity: number.yambms_yambms_1_auto_eoc_capacity_modifier
|
||||
name: Capacity Modifier
|
||||
- entity: number.yambms_yambms_1_auto_eoc_increase_stop_hours
|
||||
name: Stop hours
|
||||
- entity: number.yambms_yambms_1_auto_eoc_increase_stop_soc
|
||||
name: Stop SoC
|
||||
title: YamBMS - Auto EOC
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: number.yambms_yambms_1_rebulk_soc
|
||||
@@ -278,11 +299,17 @@ views:
|
||||
title: YamBMS - ReBulk
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: number.yambms_yambms_1_max_charge_current_percent
|
||||
name: Max charge current (%)
|
||||
- entity: number.yambms_yambms_1_max_discharge_current_percent
|
||||
name: Max discharge current (%)
|
||||
title: YamBMS - Max current (%)
|
||||
- entity: number.yambms_yambms_1_max_requested_charge_current
|
||||
name: Max charge current
|
||||
- entity: number.yambms_yambms_1_max_requested_discharge_current
|
||||
name: Max discharge current
|
||||
- entity: switch.yambms_yambms_1_temperature_based_current_limitation
|
||||
name: Temperature-based current limitation
|
||||
- entity: sensor.yambms_yambms_1_ccl_derating_reason
|
||||
name: CCL Derating Reason
|
||||
- entity: sensor.yambms_yambms_1_dcl_derating_reason
|
||||
name: DCL Derating Reason
|
||||
title: YamBMS - Max requested current
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_yambms_1_request_force_charge
|
||||
@@ -309,29 +336,29 @@ views:
|
||||
entities:
|
||||
- entity: sensor.yambms_yambms_1_last_complete_charge
|
||||
name: Last Complete Charge
|
||||
- entity: binary_sensor.yambms_esp32_online_status
|
||||
name: ESP32 Online Status
|
||||
- entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
- entity: sensor.yambms_esp32_esphome_version
|
||||
name: ESP32 ESPHome version
|
||||
- entity: button.yambms_esp32_restart
|
||||
name: ESP32 Restart
|
||||
- entity: binary_sensor.yambms_board_online_status
|
||||
name: Board Online Status
|
||||
- entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- entity: sensor.yambms_board_esphome_version
|
||||
name: Board ESPHome version
|
||||
- entity: button.yambms_board_restart
|
||||
name: Board Restart
|
||||
title: YamBMS - Diagnostic
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: binary_sensor.yambms_canbus_1_status
|
||||
name: CANBUS 1 Status
|
||||
- entity: switch.yambms_canbus_1_inverter_heartbeat_monitoring
|
||||
name: CANBUS 1 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.yambms_canbus_1_inverter_heartbeat
|
||||
name: CANBUS 1 Inverter Heartbeat
|
||||
- entity: binary_sensor.yambms_rs485_1_status
|
||||
name: RS485 1 Status
|
||||
- entity: switch.yambms_rs485_1_inverter_heartbeat_monitoring
|
||||
name: RS485 1 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.yambms_rs485_1_inverter_heartbeat
|
||||
name: RS485 1 Inverter Heartbeat
|
||||
- entity: binary_sensor.canbus_1_status
|
||||
name: CANBUS Status
|
||||
- entity: switch.canbus_1_inverter_heartbeat_monitoring
|
||||
name: CANBUS Inverter Heartbeat Monitoring
|
||||
- entity: sensor.canbus_1_inverter_heartbeat
|
||||
name: CANBUS Inverter Heartbeat
|
||||
- entity: binary_sensor.rs485_1_status
|
||||
name: RS485 Status
|
||||
- entity: switch.rs485_1_inverter_heartbeat_monitoring
|
||||
name: RS485 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.rs485_1_inverter_heartbeat
|
||||
name: RS485 Inverter Heartbeat
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
@@ -353,10 +380,10 @@ views:
|
||||
name: Debug Heap max block
|
||||
- entity: sensor.yambms_debug_loop_time
|
||||
name: Debug Loop time
|
||||
- entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
- entity: sensor.yambms_esp32_esphome_version
|
||||
name: ESPHome version
|
||||
- entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- entity: sensor.yambms_board_esphome_version
|
||||
name: Board ESPHome version
|
||||
- entity: sensor.yambms_debug_reset_reason
|
||||
name: Debug Reset reason
|
||||
conditions:
|
||||
@@ -378,14 +405,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_1_online_status
|
||||
entity: binary_sensor.jk_bms_1_online_status
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_1_can_be_combined
|
||||
entity: binary_sensor.jk_bms_1_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -396,7 +423,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Time : <b><font color=red>
|
||||
{{ states('sensor.yambms_jk_bms_1_total_runtime_formatted', rounded=True) | upper }}</font>
|
||||
{{ states('sensor.jk_bms_1_total_runtime_formatted', rounded=True) | upper }}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
grid_rows: 1
|
||||
@@ -407,7 +434,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Error : <b><font color=red>
|
||||
{{ states('sensor.yambms_jk_bms_1_errors', rounded=True) }}</font>
|
||||
{{ states('sensor.jk_bms_1_errors', rounded=True) }}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
grid_rows: 1
|
||||
@@ -418,43 +445,43 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('binary_sensor.yambms_jk_bms_1_charging') == 'on'
|
||||
states('binary_sensor.jk_bms_1_charging') == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_charging') | upper
|
||||
states('binary_sensor.jk_bms_1_charging') | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_charging') | upper
|
||||
states('binary_sensor.jk_bms_1_charging') | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_1_discharging') ==
|
||||
states('binary_sensor.jk_bms_1_discharging') ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_discharging') |
|
||||
states('binary_sensor.jk_bms_1_discharging') |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_discharging') |
|
||||
states('binary_sensor.jk_bms_1_discharging') |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_1_balancing') ==
|
||||
states('binary_sensor.jk_bms_1_equalizing') ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_balancing') |
|
||||
states('binary_sensor.jk_bms_1_equalizing') |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_1_balancing') |
|
||||
states('binary_sensor.jk_bms_1_equalizing') |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_total_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_1_total_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_current', rounded=True) }} A</font></b>
|
||||
states('sensor.jk_bms_1_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_power', rounded=True) }} W</font>
|
||||
states('sensor.jk_bms_1_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -463,42 +490,42 @@ views:
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_battery_soc', rounded=True) }}
|
||||
states('sensor.jk_bms_1_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_1_battery_soh', rounded=True) }}
|
||||
states('sensor.jk_bms_1_battery_soh', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_total_battery_capacity_setting', rounded=True)
|
||||
states('sensor.jk_bms_1_total_battery_capacity_setting', rounded=True)
|
||||
}} Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_total_charging_cycle_capacity', rounded=True)
|
||||
states('sensor.jk_bms_1_total_charging_cycle_capacity', rounded=True)
|
||||
}} Ah</font><br> Ave. Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_average_cell_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_1_average_cell_voltage', rounded=True) }}
|
||||
V</font><br> Balance Cur. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_balancing_current', rounded=True) }}
|
||||
states('sensor.jk_bms_1_balancing_current', rounded=True) }}
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_max_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_1_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_capacity_remaining', rounded=True) }}
|
||||
states('sensor.jk_bms_1_battery_capacity_remaining', rounded=True) }}
|
||||
Ah</font><br> Cycle Count : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_charging_cycles', rounded=True)
|
||||
states('sensor.jk_bms_1_charging_cycles', rounded=True)
|
||||
}}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_delta_cell_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_1_delta_cell_voltage', rounded=True) }}
|
||||
V</font><br> MOS temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_power_tube_temperature', rounded=True)
|
||||
states('sensor.jk_bms_1_power_tube_temperature', rounded=True)
|
||||
}} °C</font><br> Min temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_1_min_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_1_min_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -524,14 +551,14 @@ views:
|
||||
|
||||
<center>
|
||||
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.jk_bms_1') }}
|
||||
|
||||
</center>
|
||||
- type: markdown
|
||||
@@ -554,27 +581,27 @@ views:
|
||||
|
||||
<center>
|
||||
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.yambms_jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.jk_bms_1') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.jk_bms_1') }}
|
||||
|
||||
</center>
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: switch.yambms_jk_bms_1_charge_switch
|
||||
- entity: switch.jk_bms_1_charge_switch
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_jk_bms_1_discharge_switch
|
||||
- entity: switch.jk_bms_1_discharge_switch
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_jk_bms_1_balance_switch
|
||||
- entity: switch.jk_bms_1_balance_switch
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_jk_bms_1_enable_bluetooth_connection
|
||||
- entity: switch.jk_bms_1_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_jk_bms_1_charging_cycles_offset
|
||||
- entity: number.jk_bms_1_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
@@ -589,14 +616,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_2_online_status
|
||||
entity: binary_sensor.jk_bms_2_online_status
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_2_can_be_combined
|
||||
entity: binary_sensor.jk_bms_2_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -607,7 +634,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Time : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_2_total_runtime_formatted', rounded=True)
|
||||
states('sensor.jk_bms_2_total_runtime_formatted', rounded=True)
|
||||
| upper }}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -619,7 +646,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Error : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_2_errors', rounded=True)}}</font>
|
||||
states('sensor.jk_bms_2_errors', rounded=True)}}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
grid_rows: 1
|
||||
@@ -630,43 +657,43 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('binary_sensor.yambms_jk_bms_2_charging') == 'on'
|
||||
states('binary_sensor.jk_bms_2_charging') == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_charging') | upper
|
||||
states('binary_sensor.jk_bms_2_charging') | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_charging') | upper
|
||||
states('binary_sensor.jk_bms_2_charging') | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_2_discharging') ==
|
||||
states('binary_sensor.jk_bms_2_discharging') ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_discharging') |
|
||||
states('binary_sensor.jk_bms_2_discharging') |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_discharging') |
|
||||
states('binary_sensor.jk_bms_2_discharging') |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_2_balancing') ==
|
||||
states('binary_sensor.jk_bms_2_equalizing') ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_balancing') |
|
||||
states('binary_sensor.jk_bms_2_equalizing') |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_2_balancing') |
|
||||
states('binary_sensor.jk_bms_2_equalizing') |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_total_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_2_total_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_current', rounded=True) }} A</font></b>
|
||||
states('sensor.jk_bms_2_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_power', rounded=True) }} W</font>
|
||||
states('sensor.jk_bms_2_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -675,42 +702,42 @@ views:
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_battery_soc', rounded=True) }}
|
||||
states('sensor.jk_bms_2_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_2_battery_soh', rounded=True) }}
|
||||
states('sensor.jk_bms_2_battery_soh', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_total_battery_capacity_setting', rounded=True)
|
||||
states('sensor.jk_bms_2_total_battery_capacity_setting', rounded=True)
|
||||
}} Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_total_charging_cycle_capacity', rounded=True)
|
||||
states('sensor.jk_bms_2_total_charging_cycle_capacity', rounded=True)
|
||||
}} Ah</font><br> Ave. Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_average_cell_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_2_average_cell_voltage', rounded=True) }}
|
||||
V</font><br> Balance Cur. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_balancing_current', rounded=True) }}
|
||||
states('sensor.jk_bms_2_balancing_current', rounded=True) }}
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_max_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_2_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_capacity_remaining', rounded=True) }}
|
||||
states('sensor.jk_bms_2_battery_capacity_remaining', rounded=True) }}
|
||||
Ah</font><br> Cycle Count : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_charging_cycles', rounded=True)
|
||||
states('sensor.jk_bms_2_charging_cycles', rounded=True)
|
||||
}}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_delta_cell_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_2_delta_cell_voltage', rounded=True) }}
|
||||
V</font><br> MOS temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_power_tube_temperature', rounded=True)
|
||||
states('sensor.jk_bms_2_power_tube_temperature', rounded=True)
|
||||
}} °C</font><br> Min temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_2_min_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_2_min_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -734,14 +761,14 @@ views:
|
||||
{% endmacro %}
|
||||
|
||||
<center>
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.jk_bms_2') }}
|
||||
|
||||
</center>
|
||||
- type: markdown
|
||||
@@ -762,27 +789,27 @@ views:
|
||||
{% endmacro %}
|
||||
|
||||
<center>
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.yambms_jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.jk_bms_2') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.jk_bms_2') }}
|
||||
|
||||
</center>
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: switch.yambms_jk_bms_2_charge_switch
|
||||
- entity: switch.jk_bms_2_charge_switch
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_jk_bms_2_discharge_switch
|
||||
- entity: switch.jk_bms_2_discharge_switch
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_jk_bms_2_balance_switch
|
||||
- entity: switch.jk_bms_2_balance_switch
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_jk_bms_2_enable_bluetooth_connection
|
||||
- entity: switch.jk_bms_2_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_jk_bms_2_charging_cycles_offset
|
||||
- entity: number.jk_bms_2_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
@@ -797,14 +824,14 @@ views:
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_3_online_status
|
||||
entity: binary_sensor.jk_bms_3_online_status
|
||||
color: state
|
||||
name: Online
|
||||
state_content: name
|
||||
- type: entity
|
||||
show_state: true
|
||||
show_icon: true
|
||||
entity: binary_sensor.yambms_jk_bms_3_can_be_combined
|
||||
entity: binary_sensor.jk_bms_3_can_be_combined
|
||||
color: state
|
||||
name: Combined
|
||||
state_content: name
|
||||
@@ -815,7 +842,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Time : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_3_total_runtime_formatted', rounded=True)
|
||||
states('sensor.jk_bms_3_total_runtime_formatted', rounded=True)
|
||||
| upper }}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -827,7 +854,7 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Error : <b><font color=red>{{
|
||||
states('sensor.yambms_jk_bms_3_errors', rounded=True)}}</font>
|
||||
states('sensor.jk_bms_3_errors', rounded=True)}}</font>
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
grid_rows: 1
|
||||
@@ -838,43 +865,43 @@ views:
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Charge : <b>{% if
|
||||
states('binary_sensor.yambms_jk_bms_3_charging') == 'on'
|
||||
states('binary_sensor.jk_bms_3_charging') == 'on'
|
||||
%} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_charging') | upper
|
||||
states('binary_sensor.jk_bms_3_charging') | upper
|
||||
}}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_charging') | upper
|
||||
states('binary_sensor.jk_bms_3_charging') | upper
|
||||
}}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Discharge : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_3_discharging') ==
|
||||
states('binary_sensor.jk_bms_3_discharging') ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_discharging') |
|
||||
states('binary_sensor.jk_bms_3_discharging') |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_discharging') |
|
||||
states('binary_sensor.jk_bms_3_discharging') |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center>Balance : <b> {% if
|
||||
states('binary_sensor.yambms_jk_bms_3_balancing') ==
|
||||
states('binary_sensor.jk_bms_3_equalizing') ==
|
||||
'on' %} <font color=#41CD52>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_balancing') |
|
||||
states('binary_sensor.jk_bms_3_equalizing') |
|
||||
upper }}</font> {% else %} <font color=#3090C7>{{
|
||||
states('binary_sensor.yambms_jk_bms_3_balancing') |
|
||||
states('binary_sensor.jk_bms_3_equalizing') |
|
||||
upper }}</font> {% endif %}
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_total_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_3_total_voltage', rounded=True) }}
|
||||
V</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_current', rounded=True) }} A</font></b>
|
||||
states('sensor.jk_bms_3_current', rounded=True) }} A</font></b>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_power', rounded=True) }} W</font>
|
||||
states('sensor.jk_bms_3_power', rounded=True) }} W</font>
|
||||
- type: grid
|
||||
square: false
|
||||
columns: 2
|
||||
@@ -883,42 +910,42 @@ views:
|
||||
content: >-
|
||||
<center><b><font size=4>SoC : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_battery_soc', rounded=True) }}
|
||||
states('sensor.jk_bms_3_battery_soc', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center><b><font size=4>SoH : <font
|
||||
color=#41CD52 size=4>{{
|
||||
states('sensor.yambms_jk_bms_3_battery_soh', rounded=True) }}
|
||||
states('sensor.jk_bms_3_battery_soh', rounded=True) }}
|
||||
%</font></font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Battery Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_total_battery_capacity_setting', rounded=True)
|
||||
states('sensor.jk_bms_3_total_battery_capacity_setting', rounded=True)
|
||||
}} Ah</font><br> Cycle Capacity : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_total_charging_cycle_capacity', rounded=True)
|
||||
states('sensor.jk_bms_3_total_charging_cycle_capacity', rounded=True)
|
||||
}} Ah</font><br> Ave. Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_average_cell_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_3_average_cell_voltage', rounded=True) }}
|
||||
V</font><br> Balance Cur. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_balancing_current', rounded=True) }}
|
||||
states('sensor.jk_bms_3_balancing_current', rounded=True) }}
|
||||
A</font><br> Max temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_max_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_3_max_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: markdown
|
||||
content: >-
|
||||
<center> Remain Capacity : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_capacity_remaining', rounded=True) }}
|
||||
states('sensor.jk_bms_3_battery_capacity_remaining', rounded=True) }}
|
||||
Ah</font><br> Cycle Count : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_charging_cycles', rounded=True)
|
||||
states('sensor.jk_bms_3_charging_cycles', rounded=True)
|
||||
}}</font><br> Delta Cell Vol. : <font
|
||||
color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_delta_cell_voltage', rounded=True) }}
|
||||
states('sensor.jk_bms_3_delta_cell_voltage', rounded=True) }}
|
||||
V</font><br> MOS temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_power_tube_temperature', rounded=True)
|
||||
states('sensor.jk_bms_3_power_tube_temperature', rounded=True)
|
||||
}} °C</font><br> Min temp. : <font color=#41CD52>{{
|
||||
states('sensor.yambms_jk_bms_3_min_temperature', rounded=True) }}
|
||||
states('sensor.jk_bms_3_min_temperature', rounded=True) }}
|
||||
°C</font>
|
||||
- type: grid
|
||||
square: false
|
||||
@@ -942,14 +969,14 @@ views:
|
||||
{% endmacro %}
|
||||
|
||||
<center>
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=1, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=2, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=3, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=4, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=5, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=6, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=7, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=8, entity='.jk_bms_3') }}
|
||||
|
||||
</center>
|
||||
- type: markdown
|
||||
@@ -970,27 +997,27 @@ views:
|
||||
{% endmacro %}
|
||||
|
||||
<center>
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.yambms_jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=1, num=9, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=10, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=11, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=12, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=13, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=14, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=15, entity='.jk_bms_3') }}
|
||||
{{ cell_v(lead_zero=0, num=16, entity='.jk_bms_3') }}
|
||||
|
||||
</center>
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: switch.yambms_jk_bms_3_charge_switch
|
||||
- entity: switch.jk_bms_3_charge_switch
|
||||
name: Charge switch
|
||||
- entity: switch.yambms_jk_bms_3_discharge_switch
|
||||
- entity: switch.jk_bms_3_discharge_switch
|
||||
name: Discharge switch
|
||||
- entity: switch.yambms_jk_bms_3_balance_switch
|
||||
- entity: switch.jk_bms_3_balance_switch
|
||||
name: Balance switch
|
||||
- entity: switch.yambms_jk_bms_3_enable_bluetooth_connection
|
||||
- entity: switch.jk_bms_3_enable_bluetooth_connection
|
||||
name: Bluetooth
|
||||
- entity: number.yambms_jk_bms_3_charging_cycles_offset
|
||||
- entity: number.jk_bms_3_charging_cycles_offset
|
||||
name: Charging Cycles Offset
|
||||
conditions:
|
||||
- condition: state
|
||||
@@ -1003,7 +1030,7 @@ views:
|
||||
cards:
|
||||
- graph: line
|
||||
type: sensor
|
||||
entity: sensor.yambms_shunt_1_voltage
|
||||
entity: sensor.shunt_1_voltage
|
||||
detail: 2
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -1012,12 +1039,12 @@ views:
|
||||
hours_to_show: 8
|
||||
- graph: line
|
||||
type: sensor
|
||||
entity: sensor.yambms_shunt_1_state_of_charge
|
||||
entity: sensor.shunt_1_state_of_charge
|
||||
detail: 2
|
||||
name: SoC
|
||||
hours_to_show: 8
|
||||
- type: gauge
|
||||
entity: sensor.yambms_shunt_1_current
|
||||
entity: sensor.shunt_1_current
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
@@ -1030,7 +1057,7 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 3
|
||||
- type: gauge
|
||||
entity: sensor.yambms_shunt_1_power
|
||||
entity: sensor.shunt_1_power
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
@@ -1044,30 +1071,30 @@ views:
|
||||
grid_rows: 3
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: sensor.yambms_shunt_1_voltage
|
||||
- entity: sensor.shunt_1_voltage
|
||||
name: Shunt 1 Voltage
|
||||
- entity: sensor.yambms_shunt_1_current
|
||||
- entity: sensor.shunt_1_current
|
||||
name: Shunt 1 Current
|
||||
- entity: sensor.yambms_shunt_1_power
|
||||
- entity: sensor.shunt_1_power
|
||||
name: Shunt 1 Power
|
||||
- entity: sensor.yambms_shunt_1_state_of_charge
|
||||
- entity: sensor.shunt_1_state_of_charge
|
||||
name: Shunt 1 SoC
|
||||
- entity: sensor.yambms_shunt_1_temperature
|
||||
- entity: sensor.shunt_1_temperature
|
||||
name: Shunt 1 Temperature
|
||||
- entity: sensor.yambms_shunt_1_charged_power
|
||||
- entity: sensor.shunt_1_charged_power
|
||||
name: Shunt 1 Charged Power
|
||||
- entity: sensor.yambms_shunt_1_discharged_power
|
||||
- entity: sensor.shunt_1_discharged_power
|
||||
name: Shunt 1 Discharged Power
|
||||
- entity: sensor.yambms_shunt_1_battery_capacity
|
||||
- entity: sensor.shunt_1_battery_capacity
|
||||
name: Shunt 1 Battery Capacity
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_shunt_1_combine_enabled
|
||||
- entity: switch.shunt_1_combine_enabled
|
||||
name: Shunt 1 Combine enabled
|
||||
- entity: binary_sensor.yambms_shunt_1_can_be_combined
|
||||
- entity: binary_sensor.shunt_1_can_be_combined
|
||||
name: Shunt 1 Can be combined
|
||||
title: Shunt 1
|
||||
column_span: 1
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.30
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -59,10 +59,10 @@ views:
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
yellow: -2500
|
||||
red: -5000
|
||||
max: 5000
|
||||
min: -5000
|
||||
yellow: -5000
|
||||
red: -10000
|
||||
max: 10000
|
||||
min: -10000
|
||||
name: Power
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -130,8 +130,8 @@ views:
|
||||
entity: binary_sensor.yambms_inverter_communication_status
|
||||
name: Inverter comm. status
|
||||
- type: tile
|
||||
entity: binary_sensor.yambms_esp32_online_status
|
||||
name: ESP32 status
|
||||
entity: binary_sensor.yambms_board_online_status
|
||||
name: Board status
|
||||
- type: tile
|
||||
entity: sensor.yambms_yambms_1_charging_status
|
||||
name: Charging Status
|
||||
@@ -175,10 +175,10 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 2
|
||||
- type: tile
|
||||
entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- type: tile
|
||||
entity: sensor.yambms_esp32_esphome_version
|
||||
entity: sensor.yambms_board_esphome_version
|
||||
name: ESPHome version
|
||||
- type: entities
|
||||
entities:
|
||||
@@ -203,12 +203,12 @@ views:
|
||||
cards:
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: select.yambms_canbus_1_bms_name
|
||||
name: CANBUS 1 BMS Name
|
||||
- entity: select.yambms_canbus_1_protocol
|
||||
name: CANBUS 1 Protocol
|
||||
- entity: select.yambms_rs485_1_protocol
|
||||
name: RS485 1 Protocol
|
||||
- entity: select.canbus_1_yambms_name
|
||||
name: CANBUS YamBMS name
|
||||
- entity: select.canbus_1_yambms_protocol
|
||||
name: CANBUS YamBMS protocol
|
||||
- entity: select.rs485_1_yambms_protocol
|
||||
name: RS485 YamBMS protocol
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
@@ -267,6 +267,27 @@ views:
|
||||
- entity: number.yambms_yambms_1_auto_float_voltage_step
|
||||
name: Voltage Step
|
||||
title: YamBMS - Auto Float
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_yambms_1_automatic_eoc_current
|
||||
name: Automatic EOC Current
|
||||
- entity: sensor.yambms_yambms_1_auto_eoc_status
|
||||
name: Status
|
||||
- entity: sensor.yambms_yambms_1_auto_eoc_current
|
||||
name: Required Current
|
||||
- entity: number.yambms_yambms_1_auto_eoc_target_hour
|
||||
name: Target hour
|
||||
- entity: number.yambms_yambms_1_auto_eoc_target_minute
|
||||
name: Target minute
|
||||
- entity: number.yambms_yambms_1_auto_eoc_correction
|
||||
name: Current Correction
|
||||
- entity: number.yambms_yambms_1_auto_eoc_capacity_modifier
|
||||
name: Capacity Modifier
|
||||
- entity: number.yambms_yambms_1_auto_eoc_increase_stop_hours
|
||||
name: Stop hours
|
||||
- entity: number.yambms_yambms_1_auto_eoc_increase_stop_soc
|
||||
name: Stop SoC
|
||||
title: YamBMS - Auto EOC
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: number.yambms_yambms_1_rebulk_soc
|
||||
@@ -278,11 +299,17 @@ views:
|
||||
title: YamBMS - ReBulk
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: number.yambms_yambms_1_max_charge_current_percent
|
||||
name: Max charge current (%)
|
||||
- entity: number.yambms_yambms_1_max_discharge_current_percent
|
||||
name: Max discharge current (%)
|
||||
title: YamBMS - Max current (%)
|
||||
- entity: number.yambms_yambms_1_max_requested_charge_current
|
||||
name: Max charge current
|
||||
- entity: number.yambms_yambms_1_max_requested_discharge_current
|
||||
name: Max discharge current
|
||||
- entity: switch.yambms_yambms_1_temperature_based_current_limitation
|
||||
name: Temperature-based current limitation
|
||||
- entity: sensor.yambms_yambms_1_ccl_derating_reason
|
||||
name: CCL Derating Reason
|
||||
- entity: sensor.yambms_yambms_1_dcl_derating_reason
|
||||
name: DCL Derating Reason
|
||||
title: YamBMS - Max requested current
|
||||
- type: entities
|
||||
entities:
|
||||
- entity: switch.yambms_yambms_1_request_force_charge
|
||||
@@ -309,29 +336,29 @@ views:
|
||||
entities:
|
||||
- entity: sensor.yambms_yambms_1_last_complete_charge
|
||||
name: Last Complete Charge
|
||||
- entity: binary_sensor.yambms_esp32_online_status
|
||||
name: ESP32 Online Status
|
||||
- entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
- entity: sensor.yambms_esp32_esphome_version
|
||||
name: ESP32 ESPHome version
|
||||
- entity: button.yambms_esp32_restart
|
||||
name: ESP32 Restart
|
||||
- entity: binary_sensor.yambms_board_online_status
|
||||
name: Board Online Status
|
||||
- entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- entity: sensor.yambms_board_esphome_version
|
||||
name: Board ESPHome version
|
||||
- entity: button.yambms_board_restart
|
||||
name: Board Restart
|
||||
title: YamBMS - Diagnostic
|
||||
- type: entity-filter
|
||||
entities:
|
||||
- entity: binary_sensor.yambms_canbus_1_status
|
||||
name: CANBUS 1 Status
|
||||
- entity: switch.yambms_canbus_1_inverter_heartbeat_monitoring
|
||||
name: CANBUS 1 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.yambms_canbus_1_inverter_heartbeat
|
||||
name: CANBUS 1 Inverter Heartbeat
|
||||
- entity: binary_sensor.yambms_rs485_1_status
|
||||
name: RS485 1 Status
|
||||
- entity: switch.yambms_rs485_1_inverter_heartbeat_monitoring
|
||||
name: RS485 1 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.yambms_rs485_1_inverter_heartbeat
|
||||
name: RS485 1 Inverter Heartbeat
|
||||
- entity: binary_sensor.canbus_1_status
|
||||
name: CANBUS Status
|
||||
- entity: switch.canbus_1_inverter_heartbeat_monitoring
|
||||
name: CANBUS Inverter Heartbeat Monitoring
|
||||
- entity: sensor.canbus_1_inverter_heartbeat
|
||||
name: CANBUS Inverter Heartbeat
|
||||
- entity: binary_sensor.rs485_1_status
|
||||
name: RS485 Status
|
||||
- entity: switch.rs485_1_inverter_heartbeat_monitoring
|
||||
name: RS485 Inverter Heartbeat Monitoring
|
||||
- entity: sensor.rs485_1_inverter_heartbeat
|
||||
name: RS485 Inverter Heartbeat
|
||||
conditions:
|
||||
- condition: state
|
||||
state_not: unavailable
|
||||
@@ -353,10 +380,10 @@ views:
|
||||
name: Debug Heap max block
|
||||
- entity: sensor.yambms_debug_loop_time
|
||||
name: Debug Loop time
|
||||
- entity: sensor.yambms_esp32_uptime
|
||||
name: ESP32 Uptime
|
||||
- entity: sensor.yambms_esp32_esphome_version
|
||||
name: ESPHome version
|
||||
- entity: sensor.yambms_board_uptime
|
||||
name: Board Uptime
|
||||
- entity: sensor.yambms_board_esphome_version
|
||||
name: Board ESPHome version
|
||||
- entity: sensor.yambms_debug_reset_reason
|
||||
name: Debug Reset reason
|
||||
conditions:
|
||||
|
||||
@@ -7,73 +7,77 @@
|
||||

|
||||
[](https://www.buymeacoffee.com/sleeper85)
|
||||
|
||||
> [!WARNING]
|
||||
> I'm currently working on releasing **YamBMS 1.6.0**, which will be compatible with **ESPHome >= 2025.11**.
|
||||
> **ESPHome 2025.11.0** introduces many changes and still contains many bugs.
|
||||
> For the time being, I advise you to stay with **ESPHome 2025.10.5**.
|
||||
> [!WARNING]
|
||||
> ESPHome `2026.4` introduces major changes, and these may cause problems with YamBMS.
|
||||
> This new version of ESPHome will be tested and validated with the upcoming version `1.7.0` of YamBMS, which is currently in the dev branch.
|
||||
|
||||
> [!TIP]
|
||||
> This page contains many links to other README.
|
||||
> If you don't find answers to your questions, [you'll find all the README in this folder](documents/README).
|
||||
|
||||
> [!TIP]
|
||||
> Not sure which YAML to choose ? ... [YamBMS_Remote_Packages_example.yaml](YamBMS_Remote_Packages_example.yaml)
|
||||
> is a good basis for creating your custom YAML.
|
||||
> Examples of `BMS` and `Shunt` packages can be found in the [examples](examples/single-node/) folder.
|
||||
> You don't have to import a shunt but you must import at least `one BMS`.
|
||||
> Examples of `BMS`, `Shunt` and `Balancer` packages can be found in the [examples](examples/single-node/) folder.
|
||||
> You don't have to import a shunt or balancer but you must import at least `one BMS`.
|
||||
> You can mix different `BMS` models, the only condition is that the `bms_id` are numbered in order starting from `1` !
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The most important thing for proper functioning of YamBMS is that **the voltage of your BMS is well calibrated**.
|
||||
> YamBMS logic is based on the `min_cell_voltage` and `max_cell_voltage` voltages of your `BMS`.
|
||||
> If you use `YamBMS`, the internal charging logic of the `JK-PB BMS` will not be used.
|
||||
> Please read the [documentation](README.md#contents) and the [setup instructions](documents/README/Schematic_and_setup_instructions.md).
|
||||
> Please read the [documentation](README.md#contents) and the [setup instructions](documents/README/Hardware_and_schematic_instructions.md).
|
||||
|
||||
| ESPHome application to monitor BMS and communicate with inverters<br>supporting CAN bus protocol compatible with Pylontech, GoodWe, SMA,<br>Victron or Luxpower (EG4). | <a href="https://www.buymeacoffee.com/Sleeper85" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a> |
|
||||
| :--- | --- |
|
||||
| **Note: Pylontech uses 15S/48V and many others uses 16S/51.2V !**<br><br>Other battery profiles that utilise the **`PYLON`** protocol with different cell counts<br>may also work, e.g. Alpha Ess Smile, BYD Battery-Box LV Flex Lite.<br>Select the correct battery profile in the inverter to match your battery pack !<br>The **`ESP32`** communicates with the BMS using the **`BLE / UART / RS485`**<br>protocol and then sends the CAN bus frames to the inverter via the<br>[CAN bus transceiver](documents/README/Supported_devices.md#supported-can-bus-transceiver). | <a href="https://www.buymeacoffee.com/Sleeper85" target="_blank"><img src="images/BMC_QR.png" alt="Buy Me A Coffee" style="height: 217px !important;width: 217px !important;" ></a> |
|
||||
| ESPHome application to `combine` information coming from<br>your `BMS / Balancer / Shunt` and adds a smart layer before<br>transmitting instructions to your inverter on `RS485 or CAN bus`<br>using the protocols `PYLON`, `SMA`, `Victron` or `LuxPower` (EG4). | <a href="https://www.buymeacoffee.com/Sleeper85" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a> |
|
||||
| --- | --- |
|
||||
| **Note: Pylontech uses 15S/48V and many others uses 16S/51.2V !**<br><br>Other battery profiles that utilise the **`PYLON`** protocol with different cell counts<br>may also work, e.g. Alpha Ess Smile, BYD Battery-Box LV Flex Lite.<br>Select the correct battery profile in the inverter to match your battery pack !<br><br>**DISCLAIMER:** Working with battery systems involves electrical hazards.<br>Please read the complete documentation before installation and use<br>this project at your own risk. | <a href="https://www.buymeacoffee.com/Sleeper85" target="_blank"><img src="images/BMC_QR.png" alt="Buy Me A Coffee" style="height: 217px !important;width: 217px !important;" ></a> |
|
||||
|
||||
**Sends over CAN bus to inverter:**
|
||||
**Sends over CAN / RS485 bus to your inverter :**
|
||||
- Battery Voltage
|
||||
- Battery Current (+charge, -discharge)
|
||||
- [State of Charge (SoC)](documents/README/YamBMS_behavior.md#state-of-charge) **`SoC 100% will be sent to your inverter only when the battery is fully charged`**
|
||||
- State of Health (SoH)
|
||||
- Max cell V. and ID
|
||||
- Min cell V. and ID
|
||||
- BMS temperature
|
||||
- Charging voltage
|
||||
- Charging max amps
|
||||
- Discharge min voltage
|
||||
- Discharge max amps
|
||||
- Requested Charge Voltage
|
||||
- Requested Charge Current
|
||||
- Requested Discharge Voltage
|
||||
- Requested Discharge Current
|
||||
- Min Cell V. and Cell ID
|
||||
- Max Cell V. and Cell ID
|
||||
- Min temperature and sensor ID
|
||||
- Max temperature and sensor ID
|
||||
- Battery name
|
||||
- Alarms: Cell over/under voltage, Charge/discharge over current, High/low Temp, BMS fault
|
||||
|
||||
**Note:** this code support `multi-BMS` and `multi-shunt` connection per inverter with a `single ESP32` and should work with inverters that support the CAN bus protocol `PYLON`, `SMA`, `Victron` or `LuxPower` (EG4). I'm only testing it with my `Deye SUN-6K-SG03-LP1-EU` inverter.
|
||||
- Alarms & Warnings
|
||||
|
||||
**This project is still in development and testing...<br>**
|
||||
|
||||
[Dedicated topic on DIY Solar Forum](https://diysolarforum.com/threads/yambms-jk-bms-can-with-new-cut-off-charging-logic-open-source.79325/)
|
||||
Come and discuss it on the [DIY Solar Forum dedicated topic](https://diysolarforum.com/threads/yambms-jk-bms-can-with-new-cut-off-charging-logic-open-source.79325/).
|
||||
|
||||
## Contents
|
||||
|
||||
1) [Supported devices](documents/README/Supported_devices.md)
|
||||
2) [YamBMS behavior](documents/README/YamBMS_behavior.md)
|
||||
3) [YamBMS functions](documents/README/YamBMS_functions.md)
|
||||
4) [Charging logic](documents/README/Charging_logic.md)
|
||||
5) [CAN bus protocol](documents/README/CANBUS_protocol.md)
|
||||
6) [Hardware and schematic instructions](documents/README/Hardware_and_schematic_instructions.md)
|
||||
7) [Installation procedure](documents/README/Installation_procedure.md)
|
||||
8) [Troubleshooting](documents/README/Troubleshooting.md)
|
||||
2) [Hardware and schematic instructions](documents/README/Hardware_and_schematic_instructions.md)
|
||||
3) [YamBMS behavior](documents/README/YamBMS_behavior.md)
|
||||
4) [YamBMS functions](documents/README/YamBMS_functions.md)
|
||||
5) [YamBMS charging logic](documents/README/Charging_logic.md)
|
||||
6) [Installation procedure](documents/README/Installation_procedure.md)
|
||||
7) [Troubleshooting](documents/README/Troubleshooting.md)
|
||||
8) [Changelog](documents/README/Changelog.md)
|
||||
|
||||
## YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||

|
||||
|
||||
## Home Assistant
|
||||
|
||||

|
||||
|
||||
## Hardware highlighted
|
||||
|
||||
This project works with various `ESP32` variants and also with the `Raspberry Pi Pico (RP2040)`.
|
||||
Note that merging data from multiple BMS, balancers and shunts is resource-intensive, so I highly recommend a board based on the `ESP32-S3` with `PSRAM`.
|
||||
|
||||
| [LilyGo T-Connect](https://github.com/Xinyuan-LilyGO/T-Connect) | [Waveshare ESP32-S3-RS485-CAN](https://www.waveshare.com/esp32-s3-rs485-can.htm) | [M5Stack AtomS3R](https://docs.m5stack.com/en/core/AtomS3R) |
|
||||
| [LilyGo T-Connect](documents/README/Board_LilyGo_T-Connect.md) | [Waveshare RS485-CAN](documents/README/Board_Waveshare_ESP32-S3-RS485-CAN.md) | [M5Stack AtomS3R](documents/README/Board_M5Stack_AtomS3.md) |
|
||||
| --- | --- | --- |
|
||||
| - ESP32-S3<br>- 8MB PSRAM<br>- 3x RS485 port<br>- 1x CAN port<br>- 15x GPIOs | - ESP32-S3<br>- 8MB PSRAM<br>- 1x RS485 port<br>- 1x CAN port<br>- 1x SH1.0 connector<br>- 16x GPIOs | - ESP32-S3<br>- 8MB PSRAM<br>- 1x BASE port (**for adding RS485/CAN base**)<br>- 1x UNIT HY2.0 port (**for adding RS485/CAN unit**)<br>- 6x GPIOs |
|
||||
| <img src="images/MCU_ESP32-S3_LilyGo-T-Connect.jpg" width="300"> | <img src="images/MCU_ESP32-S3_WS-RS485-CAN.png" width="300"> | <img src="images/MCU_AtomS3R.png" width="300"> |
|
||||
| <img src="images/MCU_ESP32-S3_LilyGo-T-Connect_1.jpg" width="300"> | <img src="images/MCU_ESP32-S3_WS-RS485-CAN_2.png" width="300"> | <img src="images/MCU_AtomS3R.png" width="300"> |
|
||||
|
||||
### Single-node
|
||||
|
||||
@@ -85,29 +89,34 @@ You install `YamBMS` on a single ESP32 connected to your BMS and your inverter.
|
||||
|
||||
### Multi-node
|
||||
|
||||
Each BMS/Shunt turns into a `modbus server` with its own address.
|
||||
Each BMS/Shunt/Balancer turns into a `modbus server` with its own address.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The max number of `UART` BMS/Shunt per ESP32 is `2` (unless you use a UART expander) because you need to keep the last `UART` for the `RS485` network.
|
||||
> The max number of `BLE` BMS/Shunt per ESP32 is `2`, ESP32-S3 / AtomS3 can supervise `3` BLE devices.
|
||||
> The max number of `BLE` BMS/Shunt/Balancer per ESP32 is `2`, ESP32-S3 / AtomS3 can supervise `3` BLE devices.
|
||||
|
||||
YamBMS installs on `node1` as a `modbus client` to collect information from all your BMS.
|
||||
The `node1` is also connected to your inverter via the `CAN bus`.
|
||||
|
||||
The BMS/Shunt are connected to other ESP32 nodes connected on a dedicated RS485 bus for YamBMS. Each BMS/Shunt becomes a `modbus server`.
|
||||
The BMS/Shunt are connected to other ESP32 nodes connected on a dedicated RS485 bus for YamBMS. Each BMS/Shunt/Balancer becomes a `modbus server`.
|
||||
|
||||
The theoretical limit is `256` modbus server (BMS/Shunt) per `RS485 bus` but in reality this will depend on the capabilities of `node1` (YamBMS) which will have to combine all the BMS/Shunt together.
|
||||
The theoretical limit is `256` modbus server (BMS/Shunt) per `RS485 bus` but in reality this will depend on the capabilities of `node1` (YamBMS) which will have to combine all the BMS/Shunt/Balancer together.
|
||||
|
||||
[You can find more information about creating your YAML in this How To.](documents/README/YamBMS_main_YAML_HowTo.md)
|
||||
[You can find more information about creating your YAML in this How To.](documents/README/YamBMS_RP_YAML.md)
|
||||
|
||||
> [!TIP]
|
||||
> If you have a lot of `BMS/Shunt` to combine, using an `ESP32-S3` or `AtomS3` for `node1` is recommended.
|
||||
> If you have a lot of `BMS/Shunt/Balancer` to combine, using an `ESP32-S3` or `AtomS3` for `node1` is recommended.
|
||||
|
||||

|
||||
|
||||
## Home Assistant
|
||||
[@GHswitt](https://github.com/GHswitt) multi-node example :
|
||||
|
||||

|
||||

|
||||
|
||||
> [!NOTE]
|
||||
> Some boards with integrated `RS485 transceiver` have already a 120 Ohm resistor installed, for example the `LilyGo T-CAN485`, `LilyGo T-Connect` and `LilyGo T-Connect Pro`.
|
||||
> If these devices are used in the middle, this resistor must be removed!
|
||||
> Otherwise transmission errors can occur.
|
||||
|
||||
## Try YamBMS with the DEMO firmware
|
||||
|
||||
@@ -129,7 +138,7 @@ rx_pin: 22 # to CAN board CRX (with 4.7K resistor except for SN65HVD230)
|
||||
|
||||
## Requirements
|
||||
|
||||
* [ESPHome 2025.6.0 or higher](https://github.com/esphome/esphome/releases)
|
||||
* [ESPHome 2025.11.0 or higher](https://github.com/esphome/esphome/releases)
|
||||
* ESP32 MCU (buying a board with ≥8MB flash is advised if you intend to monitor multiple BMS)
|
||||
* CAN transceiver (only with TJA1050/TJA1051 => 4.7K resistor for 5V to 3V3 level shifing)
|
||||
* BMS JK, JBD, Seplos (other BMS brands already integrated with ESPhome can be added easily)
|
||||
@@ -140,7 +149,7 @@ rx_pin: 22 # to CAN board CRX (with 4.7K resistor except for SN65HVD230)
|
||||
## Data collection
|
||||
|
||||
> [!NOTE]
|
||||
> For your information, in June 2025 there were `100` YamBMS users.
|
||||
> For your information, in January 2026 there were `160` YamBMS users.
|
||||
|
||||
If the ESP32 has an internet connection, the following data is sent to [this script](http://script.opentel.be/yambms.post.php)
|
||||
for statistics collection. Only [@Sleeper85](https://github.com/Sleeper85) have access to this information for the production of statistics, the support and the update service.
|
||||
@@ -158,6 +167,9 @@ for statistics collection. Only [@Sleeper85](https://github.com/Sleeper85) have
|
||||
|
||||
## References
|
||||
|
||||
* Thanks to [@syssi](https://github.com/syssi/esphome-jk-bms) for help and making many BMS components (JK, JBD, Seplos, Pace, etc.)
|
||||
* Thanks to [@txubelaxu](https://github.com/txubelaxu/esphome-jk-bms) for help and making the `JK-PB RS485` component.
|
||||
* Thanks to [@uksa007](https://www.patreon.com/Uksa007Codedevelopment) for making the original CANBUS code.
|
||||
* Thanks to [@syssi](https://github.com/syssi/) for help and developing many BMS components (JK, JBD, Seplos, Pace, etc.).
|
||||
* Thanks to [@txubelaxu](https://github.com/txubelaxu/) for help and developing the `JK_RS485` component.
|
||||
* Thanks to [@shvm](https://github.com/shvmm), [@MrPabloUK](https://github.com/MrPabloUK) and [@GHswitt](https://github.com/GHswitt) for their multiple contributions.
|
||||
* Thanks to [@Fahmula](https://github.com/Fahmula) for developing the `PYLON RS485` component.
|
||||
* Thanks to [@uksa007](https://www.patreon.com/Uksa007Codedevelopment) for the development of the first CANBUS code.
|
||||
* Thanks to all the [contributors](https://github.com/Sleeper85/esphome-yambms/graphs/contributors).
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
# +--------------------------------------+
|
||||
# | UART expander WK2168 |
|
||||
# +--------------------------------------+
|
||||
@@ -184,13 +217,13 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
|
||||
@@ -1,107 +0,0 @@
|
||||
# Updated : 2025.07.29
|
||||
# Version : 1.1.1
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Local Packages Version #########################
|
||||
|
||||
# You need to copy the `packages` folder into the same folder as this YAML in order to compile it.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '5s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | Modbus Settings |
|
||||
# +--------------------------------------+
|
||||
modbus_update_interval: '5s' # frequency with which BMS/Shunt modbus servers are queried
|
||||
modbus_baud_rate: '19200' # 9600 / 19200 / 11520
|
||||
modbus_command_throttle: '0ms' # minimum time in between 2 requests to the device
|
||||
modbus_send_wait_time: '250ms' # time in milliseconds before the next ModBUS command is sent if an answer from a previous command is pending
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_LP_YAML.md
|
||||
|
||||
packages:
|
||||
|
||||
device_board: !include packages/board/board_RP2040_RPi_Pico.yaml
|
||||
|
||||
uart_1: !include packages/board/board_options_itf_uart_1.yaml
|
||||
uart_2: !include packages/board/board_options_itf_uart_2.yaml
|
||||
uart_3: !include packages/board/board_options_itf_uart_3.yaml
|
||||
uart_4: !include packages/board/board_options_itf_uart_4.yaml
|
||||
uart_5: !include packages/board/board_options_itf_uart_5.yaml
|
||||
uart_6: !include packages/board/board_options_itf_uart_6.yaml
|
||||
|
||||
modbus: !include
|
||||
file: packages/base/device_modbus.yaml
|
||||
vars:
|
||||
modbus_role: 'server' # client / server
|
||||
modbus_uart_id: 'uart_1' # RS485 board
|
||||
|
||||
shunt1: !include
|
||||
file: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '1'
|
||||
shunt_name: 'Shunt 1'
|
||||
shunt_uart_id: 'uart_2'
|
||||
|
||||
shunt2: !include
|
||||
file: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '2'
|
||||
shunt_name: 'Shunt 2'
|
||||
shunt_uart_id: 'uart_3'
|
||||
|
||||
shunt3: !include
|
||||
file: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '3'
|
||||
shunt_name: 'Shunt 3'
|
||||
shunt_uart_id: 'uart_4'
|
||||
|
||||
shunt4: !include
|
||||
file: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '4'
|
||||
shunt_name: 'Shunt 4'
|
||||
shunt_uart_id: 'uart_5'
|
||||
|
||||
shunt5: !include
|
||||
file: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '5'
|
||||
shunt_name: 'Shunt 5'
|
||||
shunt_uart_id: 'uart_6'
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,18 +159,22 @@ packages:
|
||||
# This list is incomplete, other board.yaml are available in the board folder
|
||||
|
||||
device_board: !include 'packages/board/board_ESP32_Generic.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32_EVB.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# device_board: !include 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -169,6 +206,13 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# uart_esp_3: !include packages/board/board_options_itf_uart_esp_3.yaml
|
||||
|
||||
# UART flow control
|
||||
# uart_flow_control: !include
|
||||
# file: packages/board/board_options_itf_uart_flow_control.yaml
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
canbus_node_1: !include
|
||||
file: packages/board/board_options_itf_canbus_esp32_can.yaml
|
||||
@@ -200,13 +244,13 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,21 +159,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +203,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +212,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,20 +247,20 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# Basen controller
|
||||
- path: packages/bms/bms_combine_BASEN_RS485_controller.yaml
|
||||
@@ -247,7 +290,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -260,7 +303,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -281,7 +324,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -300,7 +343,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,21 +159,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +203,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +212,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,20 +247,20 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# Deye BMS top unit (required)
|
||||
- path: 'packages/bms/bms_sensors_DEYE_CAN_top_full.yaml'
|
||||
@@ -256,7 +299,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -269,7 +312,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -290,7 +333,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -309,7 +352,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
@@ -0,0 +1,373 @@
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
|
||||
# Please use the native `api` component instead of the `mqtt` section.
|
||||
# If you use Home Assistant, the native API is more lightweight.
|
||||
# If there is no HA server connected to this API, the ESP32 reboots every 15 minutes to try to resolve the problem.
|
||||
# The "reboot_timeout: 0s" option will keep your ESP32 up and running even if you lose connection to your HA server.
|
||||
api:
|
||||
reboot_timeout: 0s
|
||||
|
||||
# If you don't want to use ESPHome's native API you can use MQTT instead.
|
||||
# In this case don't forget to remove the 'api:' section.
|
||||
# mqtt:
|
||||
# broker: !secret mqtt_host
|
||||
# username: !secret mqtt_username
|
||||
# password: !secret mqtt_password
|
||||
# id: mqtt_client
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
# +--------------------------------------+
|
||||
# Please read the cut-off charging logic README to understand how the YamBMS works
|
||||
yambms_id: 'yambms1'
|
||||
yambms_name: 'YamBMS 1'
|
||||
yambms_update_interval: '1s'
|
||||
# Input numbers can be displayed as a slider or an input box, options are 'slider' or 'box'.
|
||||
yambms_input_number_mode: 'slider'
|
||||
# Please check and fill in the options below correctly according to your battery chemistry and number of cells in series.
|
||||
# These parameters are important and used for charging logic.
|
||||
# Battery Chemistry
|
||||
yambms_battery_chemistry: '1' # 1-LFP | 2-Li-ion | 3-LTO
|
||||
# Number of cells in series
|
||||
yambms_cell_count: '16'
|
||||
# Bulk / Absorption Voltage : corresponds to the Bulk voltage that will be used to charge the battery. (LFP : 55.2V = 3.45V/Cell for 16S battery)
|
||||
yambms_bulk_v: '55.2'
|
||||
# Float Voltage : corresponds to the voltage at which the battery would be maintained at the end of charge. (LFP : 53.6V = 3.35V/Cell for 16S battery)
|
||||
yambms_float_v: '53.6'
|
||||
# Rebulk voltage, voltage from which a new Bulk charge can start. (LFP : 52.8V = 3.3V/Cell for 16S battery)
|
||||
yambms_rebulk_v: '52.8'
|
||||
# Maximum time in minutes that the cut-off step can last before charging is complete
|
||||
# If your cells are properly balanced this step ends at the fastest after the `cut-off timer`
|
||||
# This timer can be deactivated with a switch
|
||||
yambms_eoc_timer: '30'
|
||||
# Time in seconds during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
yambms_cutoff_timer: '60'
|
||||
# Max. charge current : corresponds to the maximum charge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_charge_current: '300' # in Ampere
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
|
||||
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_RP_YAML.md
|
||||
|
||||
packages:
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> UNCOMMENT YOUR BOARD
|
||||
# | >>> ONLY ONE BOARD !
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml' # 'packages/board/board_ESP32-S3_AtomS3R.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
# # LilyGo T-Connect Pro - Board
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect-Pro.yaml'
|
||||
# # LilyGo T-Connect Pro - Display - Importing the display also activates PSRAM
|
||||
# - path: 'packages/board/board_options_display_480x222.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Board Options
|
||||
# | >>> Uncomment your interfaces and options
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
# UART 2 (uart_id: uart_esp_2)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_2.yaml'
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
# to bms = canbus_bms_1
|
||||
# to inverter = canbus_inverter_1
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# CAN transceiver - MCP2515
|
||||
# - path: 'packages/board/board_options_itf_canbus_mcp2515.yaml'
|
||||
# vars:
|
||||
# # to bms = canbus_bms_1
|
||||
# # to inverter = canbus_inverter_1
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# PSRAM octal 80Mhz
|
||||
# - path: 'packages/board/board_options_PSRAM_octal_80Mhz.yaml'
|
||||
|
||||
# Web Server
|
||||
# - path: 'packages/yambms/yambms_web_server.yaml'
|
||||
|
||||
# WiFi AP @ 192.168.4.1
|
||||
# - path: 'packages/board/board_options_wifi_ap.yaml'
|
||||
|
||||
# Captive Portal @ 192.168.4.1
|
||||
# - path: 'packages/board/board_options_captive_portal.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# EG4 Modbus
|
||||
- path: 'packages/bms/bms_combine_EG4_RS485_modbus.yaml'
|
||||
vars:
|
||||
eg4_modbus_uart_id: 'uart_esp_1'
|
||||
eg4_modbus_baud_rate: '9600'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'EG4-BMS 1'
|
||||
## BMS address must start at 2 with EG4 LLV2, ID 1 is a special case and has different output.
|
||||
bms_address: 2 # BMS 1 modbus address
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'EG4-BMS 2'
|
||||
bms_address: 3 # BMS 2 modbus address
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'EG4-BMS 3'
|
||||
bms_address: 4 # BMS 3 modbus address
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> YamBMS
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> CAN bus to Inverter
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
canbus_id: 'canbus1'
|
||||
canbus_name: 'CANBUS 1'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (0x305 frame) for 5s
|
||||
# The Deye inverter sends the ACK 0x305 only when it receives the 0x356 frame.
|
||||
canbus_link_timer: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> RS485 bus to Inverter
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
# rs485_id: 'rs485_1'
|
||||
# rs485_name: 'RS485 1'
|
||||
# rs485_uart_id: 'uart_esp_3' # UART interface to which your inverter is connected
|
||||
# rs485_uart_baud_rate: '9600'
|
||||
# rs485_update_timeout: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> DEBUG ( logger level must be DEBUG )
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
# Size of your PSRAM in bits
|
||||
# 8Mb='8388608' | 6Mb='6291456' | 4Mb='4194304' | 2Mb='2097152' | NoPSRAM='0'
|
||||
debug_psram_size: '8388608'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Config and Custom Local Packages
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,21 +159,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +203,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +212,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,26 +247,26 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JBD_UART_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'JBD-BMS 1'
|
||||
bms_uart_id: 'uart_esp_1'
|
||||
bms_rx_timeout: '150ms'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
@@ -241,7 +284,7 @@ packages:
|
||||
- path: 'packages/bms/bms_combine_JBD_BLE_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_name: 'JBD-BMS 2'
|
||||
bms_ble_mac_address: 'C8:47:8C:10:7E:AA' # Your MAC address
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
@@ -264,7 +307,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -277,7 +320,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -298,7 +341,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -317,7 +360,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,21 +159,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +203,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +212,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,96 +247,77 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# RS485 Sniffer with talk_pin (WS-RS485-CAN and other RS485 boards with a flow_control_pin)
|
||||
# - path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer_talk_pin.yaml'
|
||||
# vars:
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: ${talk_pin} # can be replaced by the GPIO number
|
||||
# RS485 Sniffer
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml'
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 ( JK app `Device Addr.` setting )
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 ( JK app `Device Addr.` setting )
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 ( JK app `Device Addr.` setting )
|
||||
# BMS 4
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 ( JK app `Device Addr.` setting )
|
||||
# BMS 5
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 ( JK app `Device Addr.` setting )
|
||||
# BMS 6
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 ( JK app `Device Addr.` setting )
|
||||
# BMS 7
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 ( JK app `Device Addr.` setting )
|
||||
# BMS 8
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 ( JK app `Device Addr.` setting )
|
||||
@@ -307,7 +331,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -320,7 +344,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -341,7 +365,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -360,7 +384,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,18 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
# +--------------------------------------+
|
||||
@@ -126,21 +158,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +202,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +211,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,96 +246,77 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# RS485 Sniffer with talk_pin (WS-RS485-CAN and other RS485 boards with a flow_control_pin)
|
||||
# - path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer_talk_pin.yaml'
|
||||
# vars:
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: ${talk_pin} # can be replaced by the GPIO number
|
||||
# RS485 Sniffer
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml'
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 DIP switch
|
||||
# BMS 4
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 DIP switch
|
||||
# BMS 5
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 DIP switch
|
||||
# BMS 6
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 DIP switch
|
||||
# BMS 7
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 DIP switch
|
||||
# BMS 8
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 DIP switch
|
||||
@@ -307,7 +330,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -320,7 +343,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -341,7 +364,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -360,7 +383,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,21 +159,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +203,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +212,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,20 +247,20 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_BLE_standard.yaml'
|
||||
@@ -249,7 +292,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -262,7 +305,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -283,7 +326,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -302,7 +345,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,18 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
# +--------------------------------------+
|
||||
@@ -126,21 +158,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +202,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +211,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,20 +246,20 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml'
|
||||
@@ -247,7 +289,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -260,7 +302,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -281,7 +323,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -300,7 +342,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
@@ -0,0 +1,364 @@
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
|
||||
# Please use the native `api` component instead of the `mqtt` section.
|
||||
# If you use Home Assistant, the native API is more lightweight.
|
||||
# If there is no HA server connected to this API, the ESP32 reboots every 15 minutes to try to resolve the problem.
|
||||
# The "reboot_timeout: 0s" option will keep your ESP32 up and running even if you lose connection to your HA server.
|
||||
api:
|
||||
reboot_timeout: 0s
|
||||
|
||||
# If you don't want to use ESPHome's native API you can use MQTT instead.
|
||||
# In this case don't forget to remove the 'api:' section.
|
||||
# mqtt:
|
||||
# broker: !secret mqtt_host
|
||||
# username: !secret mqtt_username
|
||||
# password: !secret mqtt_password
|
||||
# id: mqtt_client
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
# +--------------------------------------+
|
||||
# Please read the cut-off charging logic README to understand how the YamBMS works
|
||||
yambms_id: 'yambms1'
|
||||
yambms_name: 'YamBMS 1'
|
||||
yambms_update_interval: '1s'
|
||||
# Input numbers can be displayed as a slider or an input box, options are 'slider' or 'box'.
|
||||
yambms_input_number_mode: 'slider'
|
||||
# Please check and fill in the options below correctly according to your battery chemistry and number of cells in series.
|
||||
# These parameters are important and used for charging logic.
|
||||
# Battery Chemistry
|
||||
yambms_battery_chemistry: '1' # 1-LFP | 2-Li-ion | 3-LTO
|
||||
# Number of cells in series
|
||||
yambms_cell_count: '16'
|
||||
# Bulk / Absorption Voltage : corresponds to the Bulk voltage that will be used to charge the battery. (LFP : 55.2V = 3.45V/Cell for 16S battery)
|
||||
yambms_bulk_v: '55.2'
|
||||
# Float Voltage : corresponds to the voltage at which the battery would be maintained at the end of charge. (LFP : 53.6V = 3.35V/Cell for 16S battery)
|
||||
yambms_float_v: '53.6'
|
||||
# Rebulk voltage, voltage from which a new Bulk charge can start. (LFP : 52.8V = 3.3V/Cell for 16S battery)
|
||||
yambms_rebulk_v: '52.8'
|
||||
# Maximum time in minutes that the cut-off step can last before charging is complete
|
||||
# If your cells are properly balanced this step ends at the fastest after the `cut-off timer`
|
||||
# This timer can be deactivated with a switch
|
||||
yambms_eoc_timer: '30'
|
||||
# Time in seconds during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
yambms_cutoff_timer: '60'
|
||||
# Max. charge current : corresponds to the maximum charge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_charge_current: '300' # in Ampere
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
|
||||
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_RP_YAML.md
|
||||
|
||||
packages:
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> UNCOMMENT YOUR BOARD
|
||||
# | >>> ONLY ONE BOARD !
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml' # 'packages/board/board_ESP32-S3_AtomS3R.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
# # LilyGo T-Connect Pro - Board
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect-Pro.yaml'
|
||||
# # LilyGo T-Connect Pro - Display - Importing the display also activates PSRAM
|
||||
# - path: 'packages/board/board_options_display_480x222.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Board Options
|
||||
# | >>> Uncomment your interfaces and options
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
# UART 2 (uart_id: uart_esp_2)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_2.yaml'
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
# to bms = canbus_bms_1
|
||||
# to inverter = canbus_inverter_1
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# CAN transceiver - MCP2515
|
||||
# - path: 'packages/board/board_options_itf_canbus_mcp2515.yaml'
|
||||
# vars:
|
||||
# # to bms = canbus_bms_1
|
||||
# # to inverter = canbus_inverter_1
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# PSRAM octal 80Mhz
|
||||
# - path: 'packages/board/board_options_PSRAM_octal_80Mhz.yaml'
|
||||
|
||||
# Web Server
|
||||
# - path: 'packages/yambms/yambms_web_server.yaml'
|
||||
|
||||
# WiFi AP @ 192.168.4.1
|
||||
# - path: 'packages/board/board_options_wifi_ap.yaml'
|
||||
|
||||
# Captive Portal @ 192.168.4.1
|
||||
# - path: 'packages/board/board_options_captive_portal.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# Pace Modbus
|
||||
- path: 'packages/bms/bms_combine_PACE_RS485_modbus.yaml'
|
||||
vars:
|
||||
pace_modbus_uart_id: 'uart_esp_1'
|
||||
pace_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Pace BMS model here
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_PACE_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # BMS id and modbus address
|
||||
bms_name: 'PACE-BMS 1'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_PACE_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # BMS id and modbus address
|
||||
bms_name: 'PACE-BMS 2'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> YamBMS
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> CAN bus to Inverter
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
canbus_id: 'canbus1'
|
||||
canbus_name: 'CANBUS 1'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (0x305 frame) for 5s
|
||||
# The Deye inverter sends the ACK 0x305 only when it receives the 0x356 frame.
|
||||
canbus_link_timer: '6s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> RS485 bus to Inverter
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
# rs485_id: 'rs485_1'
|
||||
# rs485_name: 'RS485 1'
|
||||
# rs485_uart_id: 'uart_esp_3' # UART interface to which your inverter is connected
|
||||
# rs485_uart_baud_rate: '9600'
|
||||
# rs485_update_timeout: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> DEBUG ( logger level must be DEBUG )
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
# Size of your PSRAM in bits
|
||||
# 8Mb='8388608' | 6Mb='6291456' | 4Mb='4194304' | 2Mb='2097152' | NoPSRAM='0'
|
||||
debug_psram_size: '8388608'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Config and Custom Local Packages
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,21 +159,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +203,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +212,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,36 +247,32 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# Seplos Modbus 1
|
||||
# Seplos Modbus
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_modbus.yaml'
|
||||
vars:
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
seplos_modbus_uart_id: 'uart_esp_1'
|
||||
seplos_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
seplos_modbus_rx_timeout: '150ms'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'SEPLOS-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
# Required settings cannot be retrieved from BMS
|
||||
@@ -247,14 +286,25 @@ packages:
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_name: 'SEPLOS-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
bms_uart_id: uart_esp_2
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_max_charge_current: '100' # A. Used to calculate maximum charge current
|
||||
bms_max_discharge_current: '100' # A. Used to calculate maximum discharge current
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'SEPLOS-BMS 3'
|
||||
bms_address: '0x03' # BMS 2 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
@@ -273,7 +323,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -286,7 +336,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -307,7 +357,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -326,7 +376,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
@@ -0,0 +1,392 @@
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
|
||||
# Please use the native `api` component instead of the `mqtt` section.
|
||||
# If you use Home Assistant, the native API is more lightweight.
|
||||
# If there is no HA server connected to this API, the ESP32 reboots every 15 minutes to try to resolve the problem.
|
||||
# The "reboot_timeout: 0s" option will keep your ESP32 up and running even if you lose connection to your HA server.
|
||||
api:
|
||||
reboot_timeout: 0s
|
||||
|
||||
# If you don't want to use ESPHome's native API you can use MQTT instead.
|
||||
# In this case don't forget to remove the 'api:' section.
|
||||
# mqtt:
|
||||
# broker: !secret mqtt_host
|
||||
# username: !secret mqtt_username
|
||||
# password: !secret mqtt_password
|
||||
# id: mqtt_client
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
# +--------------------------------------+
|
||||
# Please read the cut-off charging logic README to understand how the YamBMS works
|
||||
yambms_id: 'yambms1'
|
||||
yambms_name: 'YamBMS 1'
|
||||
yambms_update_interval: '1s'
|
||||
# Input numbers can be displayed as a slider or an input box, options are 'slider' or 'box'.
|
||||
yambms_input_number_mode: 'slider'
|
||||
# Please check and fill in the options below correctly according to your battery chemistry and number of cells in series.
|
||||
# These parameters are important and used for charging logic.
|
||||
# Battery Chemistry
|
||||
yambms_battery_chemistry: '1' # 1-LFP | 2-Li-ion | 3-LTO
|
||||
# Number of cells in series
|
||||
yambms_cell_count: '16'
|
||||
# Bulk / Absorption Voltage : corresponds to the Bulk voltage that will be used to charge the battery. (LFP : 55.2V = 3.45V/Cell for 16S battery)
|
||||
yambms_bulk_v: '55.2'
|
||||
# Float Voltage : corresponds to the voltage at which the battery would be maintained at the end of charge. (LFP : 53.6V = 3.35V/Cell for 16S battery)
|
||||
yambms_float_v: '53.6'
|
||||
# Rebulk voltage, voltage from which a new Bulk charge can start. (LFP : 52.8V = 3.3V/Cell for 16S battery)
|
||||
yambms_rebulk_v: '52.8'
|
||||
# Maximum time in minutes that the cut-off step can last before charging is complete
|
||||
# If your cells are properly balanced this step ends at the fastest after the `cut-off timer`
|
||||
# This timer can be deactivated with a switch
|
||||
yambms_eoc_timer: '30'
|
||||
# Time in seconds during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
yambms_cutoff_timer: '60'
|
||||
# Max. charge current : corresponds to the maximum charge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_charge_current: '300' # in Ampere
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
|
||||
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_RP_YAML.md
|
||||
|
||||
packages:
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> UNCOMMENT YOUR BOARD
|
||||
# | >>> ONLY ONE BOARD !
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml' # 'packages/board/board_ESP32-S3_AtomS3R.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
# # LilyGo T-Connect Pro - Board
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect-Pro.yaml'
|
||||
# # LilyGo T-Connect Pro - Display - Importing the display also activates PSRAM
|
||||
# - path: 'packages/board/board_options_display_480x222.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Board Options
|
||||
# | >>> Uncomment your interfaces and options
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
# UART 2 (uart_id: uart_esp_2)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_2.yaml'
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
# to bms = canbus_bms_1
|
||||
# to inverter = canbus_inverter_1
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# CAN transceiver - MCP2515
|
||||
# - path: 'packages/board/board_options_itf_canbus_mcp2515.yaml'
|
||||
# vars:
|
||||
# # to bms = canbus_bms_1
|
||||
# # to inverter = canbus_inverter_1
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# PSRAM octal 80Mhz
|
||||
# - path: 'packages/board/board_options_PSRAM_octal_80Mhz.yaml'
|
||||
|
||||
# Web Server
|
||||
# - path: 'packages/yambms/yambms_web_server.yaml'
|
||||
|
||||
# WiFi AP @ 192.168.4.1
|
||||
# - path: 'packages/board/board_options_wifi_ap.yaml'
|
||||
|
||||
# Captive Portal @ 192.168.4.1
|
||||
# - path: 'packages/board/board_options_captive_portal.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# Seplos Parser
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_modbus_sniffer.yaml'
|
||||
vars:
|
||||
seplos_uart_id: 'uart_esp_1'
|
||||
seplos_baud_rate: '19200' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
seplos_bms_count: '3' # Seplos V3 BMS count
|
||||
seplos_update_interval: '3' # # Time in seconds, update interval for all data points
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '1'
|
||||
bms_prefix: 'bms0' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 1'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2'
|
||||
bms_prefix: 'bms1' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 2'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '3'
|
||||
bms_prefix: 'bms2' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 3'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> YamBMS
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> CAN bus to Inverter
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
canbus_id: 'canbus1'
|
||||
canbus_name: 'CANBUS 1'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (0x305 frame) for 5s
|
||||
# The Deye inverter sends the ACK 0x305 only when it receives the 0x356 frame.
|
||||
canbus_link_timer: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> RS485 bus to Inverter
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
# rs485_id: 'rs485_1'
|
||||
# rs485_name: 'RS485 1'
|
||||
# rs485_uart_id: 'uart_esp_3' # UART interface to which your inverter is connected
|
||||
# rs485_uart_baud_rate: '9600'
|
||||
# rs485_update_timeout: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> DEBUG ( logger level must be DEBUG )
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
# Size of your PSRAM in bits
|
||||
# 8Mb='8388608' | 6Mb='6291456' | 4Mb='4194304' | 2Mb='2097152' | NoPSRAM='0'
|
||||
debug_psram_size: '8388608'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Config and Custom Local Packages
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
@@ -0,0 +1,379 @@
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
|
||||
# Please use the native `api` component instead of the `mqtt` section.
|
||||
# If you use Home Assistant, the native API is more lightweight.
|
||||
# If there is no HA server connected to this API, the ESP32 reboots every 15 minutes to try to resolve the problem.
|
||||
# The "reboot_timeout: 0s" option will keep your ESP32 up and running even if you lose connection to your HA server.
|
||||
api:
|
||||
reboot_timeout: 0s
|
||||
|
||||
# If you don't want to use ESPHome's native API you can use MQTT instead.
|
||||
# In this case don't forget to remove the 'api:' section.
|
||||
# mqtt:
|
||||
# broker: !secret mqtt_host
|
||||
# username: !secret mqtt_username
|
||||
# password: !secret mqtt_password
|
||||
# id: mqtt_client
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
# +--------------------------------------+
|
||||
# Please read the cut-off charging logic README to understand how the YamBMS works
|
||||
yambms_id: 'yambms1'
|
||||
yambms_name: 'YamBMS 1'
|
||||
yambms_update_interval: '1s'
|
||||
# Input numbers can be displayed as a slider or an input box, options are 'slider' or 'box'.
|
||||
yambms_input_number_mode: 'slider'
|
||||
# Please check and fill in the options below correctly according to your battery chemistry and number of cells in series.
|
||||
# These parameters are important and used for charging logic.
|
||||
# Battery Chemistry
|
||||
yambms_battery_chemistry: '1' # 1-LFP | 2-Li-ion | 3-LTO
|
||||
# Number of cells in series
|
||||
yambms_cell_count: '16'
|
||||
# Bulk / Absorption Voltage : corresponds to the Bulk voltage that will be used to charge the battery. (LFP : 55.2V = 3.45V/Cell for 16S battery)
|
||||
yambms_bulk_v: '55.2'
|
||||
# Float Voltage : corresponds to the voltage at which the battery would be maintained at the end of charge. (LFP : 53.6V = 3.35V/Cell for 16S battery)
|
||||
yambms_float_v: '53.6'
|
||||
# Rebulk voltage, voltage from which a new Bulk charge can start. (LFP : 52.8V = 3.3V/Cell for 16S battery)
|
||||
yambms_rebulk_v: '52.8'
|
||||
# Maximum time in minutes that the cut-off step can last before charging is complete
|
||||
# If your cells are properly balanced this step ends at the fastest after the `cut-off timer`
|
||||
# This timer can be deactivated with a switch
|
||||
yambms_eoc_timer: '30'
|
||||
# Time in seconds during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
yambms_cutoff_timer: '60'
|
||||
# Max. charge current : corresponds to the maximum charge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_charge_current: '300' # in Ampere
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_RP_YAML.md
|
||||
|
||||
packages:
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> UNCOMMENT YOUR BOARD
|
||||
# | >>> ONLY ONE BOARD !
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml' # 'packages/board/board_ESP32-S3_AtomS3R.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
# # LilyGo T-Connect Pro - Board
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect-Pro.yaml'
|
||||
# # LilyGo T-Connect Pro - Display - Importing the display also activates PSRAM
|
||||
# - path: 'packages/board/board_options_display_480x222.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Board Options
|
||||
# | >>> Uncomment your interfaces and options
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
# UART 2 (uart_id: uart_esp_2)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_2.yaml'
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
# to bms = canbus_bms_1
|
||||
# to inverter = canbus_inverter_1
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# CAN transceiver - MCP2515
|
||||
# - path: 'packages/board/board_options_itf_canbus_mcp2515.yaml'
|
||||
# vars:
|
||||
# # to bms = canbus_bms_1
|
||||
# # to inverter = canbus_inverter_1
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# PSRAM octal 80Mhz
|
||||
# - path: 'packages/board/board_options_PSRAM_octal_80Mhz.yaml'
|
||||
|
||||
# Web Server
|
||||
# - path: 'packages/yambms/yambms_web_server.yaml'
|
||||
|
||||
# WiFi AP @ 192.168.4.1
|
||||
# - path: 'packages/board/board_options_wifi_ap.yaml'
|
||||
|
||||
# Captive Portal @ 192.168.4.1
|
||||
# - path: 'packages/board/board_options_captive_portal.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# Basen controller
|
||||
- path: 'packages/bms/bms_combine_BASEN_RS485_controller.yaml'
|
||||
vars:
|
||||
basen_uart_id: 'uart_esp_1'
|
||||
basen_uart_baud_rate: '9600'
|
||||
basen_controller_id: "basen_controller_1"
|
||||
# Basen module 1
|
||||
- path: 'packages/bms/bms_combine_BASEN_RS485_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BASEN-BMS 1'
|
||||
bms_address: '0x01'
|
||||
# Basen module 2
|
||||
- path: 'packages/bms/bms_combine_BASEN_RS485_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BASEN-BMS 2'
|
||||
bms_address: '0x02'
|
||||
|
||||
# Balancer 1 linked to BMS 1
|
||||
- path: 'packages/balancer/balancer_sensors_JK_NEEY_BLE.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must match the BMS ID
|
||||
balancer_name: 'Balancer 1'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:66
|
||||
# Balancer 2 linked to BMS 2
|
||||
- path: 'packages/balancer/balancer_sensors_JK_NEEY_BLE.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must match the BMS ID
|
||||
balancer_name: 'Balancer 2'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:67
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> YamBMS
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> CAN bus to Inverter
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
canbus_id: 'canbus1'
|
||||
canbus_name: 'CANBUS 1'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (0x305 frame) for 5s
|
||||
# The Deye inverter sends the ACK 0x305 only when it receives the 0x356 frame.
|
||||
canbus_link_timer: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> RS485 bus to Inverter
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
# rs485_id: 'rs485_1'
|
||||
# rs485_name: 'RS485 1'
|
||||
# rs485_uart_id: 'uart_esp_3' # UART interface to which your inverter is connected
|
||||
# rs485_uart_baud_rate: '9600'
|
||||
# rs485_update_timeout: '5s'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> DEBUG ( logger level must be DEBUG )
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
# Size of your PSRAM in bits
|
||||
# 8Mb='8388608' | 6Mb='6291456' | 4Mb='4194304' | 2Mb='2097152' | NoPSRAM='0'
|
||||
debug_psram_size: '8388608'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Config and Custom Local Packages
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS Demo' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms-demo' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS Demo' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms-demo' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,21 +159,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +203,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +212,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,13 +247,13 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
shunt:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# Shunt 1
|
||||
- path: 'packages/shunt/shunt_combine_FAKE.yaml'
|
||||
@@ -218,15 +261,15 @@ packages:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
# Shunt sensors values
|
||||
shunt_voltage: '53.41' # V
|
||||
shunt_current: '37.5' # A
|
||||
shunt_power: '2003' # W
|
||||
shunt_soc: '86' # %e/
|
||||
shunt_voltage: '52.81' # V
|
||||
shunt_current: '17.5' # A
|
||||
shunt_power: '924' # W
|
||||
shunt_soc: '50' # %
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_FAKE.yaml'
|
||||
@@ -245,10 +288,8 @@ packages:
|
||||
bms_min_voltage_cell: '2' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.341' # V
|
||||
bms_max_voltage_cell: '11' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.1' # °C
|
||||
bms_temperature_sensor_2: '21.3' # °C
|
||||
bms_temperature_sensor_3: '21.5' # °C
|
||||
bms_temperature_sensor_4: '21.7' # °C
|
||||
bms_min_temperature: '9.1' # °C
|
||||
bms_max_temperature: '9.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
@@ -272,10 +313,8 @@ packages:
|
||||
bms_min_voltage_cell: '14' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.339' # V
|
||||
bms_max_voltage_cell: '3' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.8' # °C
|
||||
bms_temperature_sensor_2: '21.6' # °C
|
||||
bms_temperature_sensor_3: '21.4' # °C
|
||||
bms_temperature_sensor_4: '21.2' # °C
|
||||
bms_min_temperature: '15.1' # °C
|
||||
bms_max_temperature: '15.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
@@ -299,10 +338,8 @@ packages:
|
||||
bms_min_voltage_cell: '7' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.336' # V
|
||||
bms_max_voltage_cell: '9' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.9' # °C
|
||||
bms_temperature_sensor_2: '22.0' # °C
|
||||
bms_temperature_sensor_3: '22.1' # °C
|
||||
bms_temperature_sensor_4: '22.2' # °C
|
||||
bms_min_temperature: '20.1' # °C
|
||||
bms_max_temperature: '20.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
@@ -319,7 +356,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -332,7 +369,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -353,7 +390,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -372,7 +409,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,12 +159,14 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> Board Options
|
||||
# | >>> Uncomment your interfaces and options
|
||||
@@ -140,7 +175,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -149,6 +184,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -178,13 +219,13 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/h
|
||||
|
||||
@@ -197,7 +238,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -210,7 +251,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -231,7 +272,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -250,7 +291,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
# +--------------------------------------+
|
||||
# | UART expander WK2168 |
|
||||
# +--------------------------------------+
|
||||
@@ -132,7 +165,7 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32-S3_DevKitC-1_PVbrain2.yaml'
|
||||
|
||||
@@ -146,7 +179,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -194,7 +227,7 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
@@ -202,7 +235,7 @@ packages:
|
||||
|
||||
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
@@ -215,7 +248,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -228,7 +261,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -249,7 +282,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -268,7 +301,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
|
||||
@@ -0,0 +1,103 @@
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Local Packages Version #########################
|
||||
|
||||
# You need to copy the `packages` folder into the same folder as this YAML in order to compile it.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '5s' # frequency at which Shunt data is refreshed
|
||||
|
||||
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_LP_YAML.md
|
||||
|
||||
packages:
|
||||
rpi_pico:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 60min
|
||||
files:
|
||||
# board
|
||||
- path: packages/board/board_RP2040_RPi_Pico.yaml
|
||||
# uart
|
||||
- path: packages/board/board_options_itf_uart_1.yaml
|
||||
- path: packages/board/board_options_itf_uart_2.yaml
|
||||
- path: packages/board/board_options_itf_uart_3.yaml
|
||||
- path: packages/board/board_options_itf_uart_4.yaml
|
||||
- path: packages/board/board_options_itf_uart_5.yaml
|
||||
- path: packages/board/board_options_itf_uart_6.yaml
|
||||
# modbus
|
||||
- path: packages/board/board_options_itf_modbus.yaml
|
||||
vars:
|
||||
modbus_role: 'server' # client / server
|
||||
modbus_uart_id: 'uart_1' # RS485 board
|
||||
modbus_baud_rate: '19200' # 9600 / 19200 / 11520
|
||||
# shunt1
|
||||
- path: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '1'
|
||||
shunt_name: 'Shunt 1'
|
||||
shunt_uart_id: 'uart_2'
|
||||
# shunt2
|
||||
- path: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '2'
|
||||
shunt_name: 'Shunt 2'
|
||||
shunt_uart_id: 'uart_3'
|
||||
# shunt3
|
||||
- path: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '3'
|
||||
shunt_name: 'Shunt 3'
|
||||
shunt_uart_id: 'uart_4'
|
||||
# shunt4
|
||||
- path: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '4'
|
||||
shunt_name: 'Shunt 4'
|
||||
shunt_uart_id: 'uart_5'
|
||||
# shunt5
|
||||
- path: packages/shunt/shunt_modbus_Victron_SmartShunt_UART_minimal.yaml
|
||||
vars:
|
||||
shunt_id: '5'
|
||||
shunt_name: 'Shunt 5'
|
||||
shunt_uart_id: 'uart_6'
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,17 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
@@ -126,21 +159,25 @@ packages:
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -166,7 +203,7 @@ packages:
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
@@ -175,6 +212,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,13 +247,13 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
@@ -223,7 +266,7 @@ packages:
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
@@ -236,7 +279,7 @@ packages:
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
vars:
|
||||
@@ -257,7 +300,7 @@ packages:
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# refresh: 60min
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
# vars:
|
||||
@@ -276,7 +319,7 @@ packages:
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
# - path: packages/base/device_debug_ESP32_PSRAM.yaml
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.12
|
||||
# Version : 1.5.8
|
||||
# Updated : 2026.01.14
|
||||
# Version : 1.6.0
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -36,6 +36,8 @@
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
# baud_rate: 115200 # Send logs to the `hardware_uart` USB output (this consumes a UART interface)
|
||||
# hardware_uart: UART0 # UART0 / USB_SERIAL_JTAG
|
||||
|
||||
ota:
|
||||
- platform: esphome
|
||||
@@ -60,8 +62,8 @@ api:
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of the `entity name`, also used to classify them.
|
||||
hostname: 'yambms' # Name of your ESP32 registered on the IP network (DNS name, must be unique).
|
||||
name: '' # This name can be added as a second prefix, both for the `entity display name` and the `entity id`, you can leave it blank.
|
||||
# +--------------------------------------+
|
||||
# | YamBMS Settings |
|
||||
@@ -96,18 +98,48 @@ substitutions:
|
||||
# Max. discharge current : corresponds to the maximum discharge current which may be requested by YamBMS.
|
||||
# The current requested will be proportional to the BMS count without ever exceeding this value.
|
||||
yambms_max_requested_discharge_current: '300' # in Ampere
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ -0.1, 0.00 },
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# +--------------------------------------+
|
||||
# | Shunt Settings |
|
||||
# +--------------------------------------+
|
||||
shunt_update_interval: '3s' # frequency at which Shunt data is refreshed
|
||||
shunt_combine_interval: '1s' # frequency at which Shunt data is combined in YamBMS
|
||||
# +--------------------------------------+
|
||||
# | BMS Settings |
|
||||
# +--------------------------------------+
|
||||
bms_update_interval: '3s' # frequency at which BMS data is refreshed, going below '3s' can cause problems
|
||||
bms_combine_interval: '1s' # frequency at which BMS data is combined in YamBMS
|
||||
bms_cutoff_timer: '50s' # time during which the end of charge conditions must be respected (cut-off + cells not equalizing)
|
||||
|
||||
|
||||
|
||||
# +--------------------------------------+
|
||||
@@ -125,22 +157,26 @@ packages:
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
ref: dev
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_iBMS_CAN_RS485_V3.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_FlipC3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-ETH.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-RS485-CAN.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-4.3.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_WS-Touch-LCD-7.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_XIAO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_YBoard.yaml'
|
||||
|
||||
@@ -165,7 +201,7 @@ packages:
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
ref: dev
|
||||
refresh: 0s
|
||||
files:
|
||||
# UART 1 (uart_id: uart_esp_1)
|
||||
@@ -175,6 +211,12 @@ packages:
|
||||
# UART 3 (uart_id: uart_esp_3)
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# UART flow control
|
||||
# - path: 'packages/board/board_options_itf_uart_flow_control.yaml'
|
||||
# vars:
|
||||
# uart_id: 'uart_esp_1'
|
||||
# uart_flow_control_pin: ${talk_pin}
|
||||
|
||||
# CAN transceiver - ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
@@ -204,42 +246,16 @@ packages:
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
# | >>> BMS and Shunt
|
||||
# | >>> BMS / Balancer / Shunt
|
||||
# +------------------------------------------------------------------------------+
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
# You can mix different BMS models, the only condition is that the `bms_id` are numbered in order starting from 1 !
|
||||
|
||||
# >>> Copy your BMS and Shunt packages here
|
||||
# >>> Copy your BMS / Balancer / Shunt packages here
|
||||
# >>> You can find examples at this address :
|
||||
# >>> https://github.com/Sleeper85/esphome-yambms/tree/main/examples/single-node/
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Seplos Modbus
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_modbus.yaml'
|
||||
vars:
|
||||
seplos_modbus_uart_id: 'uart_esp_1'
|
||||
seplos_modbus_baud_rate: '19200' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # BMS id and modbus address
|
||||
bms_name: 'BMS 1'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # BMS id and modbus address
|
||||
bms_name: 'BMS 2'
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '3' # BMS id and modbus address
|
||||
bms_name: 'BMS 3'
|
||||
|
||||
|
||||
|
||||
# +------------------------------------------------------------------------------+
|
||||
@@ -248,7 +264,7 @@ packages:
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
ref: dev
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
@@ -261,7 +277,7 @@ packages:
|
||||
|
||||
canbus:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
ref: dev
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/yambms/yambms_canbus.yaml' # yambms_canbus_web_server.yaml
|
||||
@@ -282,7 +298,7 @@ packages:
|
||||
|
||||
# rs485_pylon:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# ref: dev
|
||||
# refresh: 0s
|
||||
# files:
|
||||
# - path: 'packages/yambms/yambms_rs485_pylon.yaml' # yambms_rs485_pylon_web_server.yaml
|
||||
@@ -301,7 +317,7 @@ packages:
|
||||
|
||||
debug:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
ref: dev
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: packages/base/device_debug_ESP32.yaml
|
||||
@@ -0,0 +1,157 @@
|
||||
# Auto Temp-Based Current
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
The YamBMS `Auto Temp-Based Current` function is a software control designed to protect battery cells from damage due to charging or discharging at extreme temperatures.
|
||||
|
||||
It dynamically calculates a "Delta" (reduction value) that adjusts the configured maximum charge and discharge limits based on the thermal environment of the battery.
|
||||
|
||||
Lithium Iron Phosphate (LiFePO4) batteries have specific "C-rate" limits that change with temperature. For example, charging at 0°C may be prohibited or restricted to a very low current, while charging at 25°C allows for the full rated current.
|
||||
|
||||
This function automates that logic by:
|
||||
- Monitoring the minimum and maximum cell temperatures.
|
||||
- Filtering out sensor noise.
|
||||
- Interpolating a safe C-rate from user-defined tables.
|
||||
- Calculating the required current reduction (Delta).
|
||||
|
||||
### Sequence of Operation
|
||||
1. Check Switch: Is the feature enabled?
|
||||
2. Validate Data: Are sensors online and reporting valid numbers?
|
||||
3. Filter: Apply EMA smoothing to the raw temperature values.
|
||||
4. Lookup: Find the C-rate for the current temperature.
|
||||
5. Calculate: Determine the current reduction needed.
|
||||
6. Apply: Round the result and update the relevant globals.
|
||||
|
||||
|
||||
## Core Logic
|
||||
### EMA Filter
|
||||
Battery cells have significant thermal mass; their temperature does not change instantly. However, digital sensors often jitter between values (e.g., bouncing between 6.8°C and 6.9°C).
|
||||
To prevent the charge current unnecessary fluctuations, an Exponential Moving Average (EMA) is used:
|
||||
|
||||
$$S_t = (\alpha \times Y_t) + ((1 - \alpha) \times S_{t-1})$$
|
||||
|
||||
**Alpha** ($\alpha$) - Set to `0.05`. This provides a stable, slow-moving average that ignores minor sensor noise but tracks real thermal trends.
|
||||
|
||||
**Adaptive Filtering** - If the sensor jumps by more than 5°C (for example, during boot-up or BMS connection), the filter ignores the EMA logic and updates immediately to the new value to ensure safety.
|
||||
|
||||
### Linear Interpolation
|
||||
Auto Temp uses a pair of mapping tables (`yambms_charging_rate_table` & `yambms_charging_rate_table`) to define the relationship between temperature and C-Rate for both charging and discharging.
|
||||
|
||||
The interpolation function calculates values between defined points in these tables:
|
||||
|
||||
For example:
|
||||
- **Point A**: $0^\circ\text{C}$ = $0.0\text{C}$ (No charging)
|
||||
- **Point B**: $10^\circ\text{C}$ = $0.1\text{C}$ (Slow charging)
|
||||
|
||||
If the actual battery temperature is $5^\circ\text{C}$, the code determines that 5 is exactly halfway between 0 and 10, so it outputs $0.05\text{C}$.
|
||||
|
||||
#### Logic Walkthrough
|
||||
The function is written as a C++ lambda (a small, self-contained function) that takes two inputs: the mapping table (`m`) and the current temperature (`x`).
|
||||
|
||||
1. **Boundarys and checks**
|
||||
|
||||
```c++
|
||||
if (m.empty()) return 0.0f;
|
||||
if (x <= m.begin()->first) return m.begin()->second;
|
||||
if (x >= m.rbegin()->first) return m.rbegin()->second;
|
||||
```
|
||||
- Empty table: If the table isn't loaded, it returns 0.
|
||||
- Lower bound: If the temperature is colder than the first mapping entry (e.g., $-10^\circ\text{C}$ when the table starts at $0^\circ\text{C}$), it simply returns the rate for $0^\circ\text{C}$.
|
||||
- Upper Bound: If the temperature is hotter than the last mapping entry, it returns the rate for the highest temperature defined.
|
||||
|
||||
2. **Bracketing the input temperature value**
|
||||
|
||||
```c++
|
||||
auto it_upper = m.upper_bound(x);
|
||||
auto it_lower = std::prev(it_upper);
|
||||
```
|
||||
The function looks through the mapping table to find the two points that encompass the current temperature.
|
||||
For a temperature of $7^\circ\text{C}$, it finds the entries for $0^\circ\text{C}$ (lower) and $10^\circ\text{C}$ (upper).
|
||||
|
||||
3. **The Slope Calculation**
|
||||
|
||||
```c++
|
||||
float x0 = it_lower->first, y0 = it_lower->second;
|
||||
float x1 = it_upper->first, y1 = it_upper->second;
|
||||
return y0 + (x - x0) * ((y1 - y0) / (x1 - x0));
|
||||
```
|
||||
This uses the standard slope-intercept formula ($y = mx + b$).
|
||||
It calculates the slope (Rate of change): $\frac{\text{Change in C-Rate}}{\text{Change in Temp}}$, then multiplies that slope by the distance the current temperature is from the lower bracket.
|
||||
Finally, it adds that result to the lower bracket C-rate.
|
||||
|
||||
#### Why Use Interpolation Instead of Simple Steps?
|
||||
Without interpolation, current limits would jump abruptly when the cell temperature passes a threshold.
|
||||
Stepped current limits:
|
||||
- $4.9^\circ\text{C}$ = $14.0\text{A}$
|
||||
- $5.0^\circ\text{C}$ = $33.6\text{A}$
|
||||
|
||||
This creates sudden changes in requested current that can stress equipment.
|
||||
|
||||
Interpolated current limits:
|
||||
- $4.9^\circ\text{C}$ = $33.2\text{A}$
|
||||
- $5.0^\circ\text{C}$ = $33.6\text{A}$
|
||||
|
||||
The current limit adjusts smoothly between C-rate thresholds as the battery temperature changes. This reduces current hunting and minimises equipment stress.
|
||||
|
||||
## The Delta Calculation
|
||||
Unlike some systems that overwrite the maximum current, this function calculates a negative delta to be applied to a configured current limit.
|
||||
|
||||
$$\text{Target Current} = \text{Allowed Rate} \times \text{Battery Capacity (Ah)}$$
|
||||
$$\text{Delta} = \text{Target Current} - \text{Max Configured Current}$$
|
||||
|
||||
Example:
|
||||
- Battery Capacity: 280Ah
|
||||
- Configured Max Charge Limit: 140A
|
||||
- Interpolated Rate at 4.9°C: 0.12C
|
||||
- Calculation: $(0.12 \times 280) - 140 = -106.4\text{A}$
|
||||
- **Result:** The system requests a reduction of 106.4A, effectively setting the limit to 33.6A.
|
||||
|
||||
## Safety & Edge Cases
|
||||
|
||||
- The code contains a clamp that ensures the logic can only lower the current limit, never increase it beyond configured limits settings.
|
||||
- If the `Temperature-based Current Limitation` switch is turned OFF, the Delta is immediately reset to 0 to prevent temperature based current restrictions.
|
||||
- If any critical sensor (temperature or capacity) returns NaN (Not a Number), the system defaults the Delta to 0 to prevent unpredictable behavior.
|
||||
|
||||
## Configuration
|
||||
The behavior is dictated by the following tables defined in the main YAML. These values represent the multiplier of the total Ah capacity (C-rate).
|
||||
|
||||
```YAML
|
||||
# +-------------------------------------------------------------------------
|
||||
# | Temperature-based current limitation
|
||||
# | Can be disabled via the switch "Temperature-based current limitation"
|
||||
# | This factor is applied to the battery capacity (Ah), not the current
|
||||
# | maximum charge/discharge current. For example : 280Ah x 0.5 = 140A
|
||||
# +-------------------------------------------------------------------------
|
||||
# Temperature °C -> Charge Rate (0.0C to 1.0C)
|
||||
yambms_charging_rate_table: |
|
||||
{
|
||||
{ 0.0, 0.05 },
|
||||
{ 5.0, 0.12 },
|
||||
{ 10.0, 0.30 },
|
||||
{ 20.0, 0.50 },
|
||||
{ 25.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
# Temperature °C -> Discharge Rate (0.0C to 1.0C)
|
||||
yambms_discharging_rate_table: |
|
||||
{
|
||||
{-30.0, 0.00 },
|
||||
{-20.0, 0.50 },
|
||||
{-10.0, 0.50 },
|
||||
{ -5.0, 0.50 },
|
||||
{ 0.0, 0.50 },
|
||||
{ 5.0, 0.50 },
|
||||
{ 45.0, 0.50 },
|
||||
{ 50.0, 0.50 },
|
||||
{ 55.0, 0.50 },
|
||||
{ 60.0, 0.00 }
|
||||
}
|
||||
```
|
||||
These values can be adjusted as needed, including adding or removing rows - the function will handle these changes automatically.
|
||||
@@ -11,12 +11,6 @@
|
||||
> Using **DIP switch addresses 1 to 15** does not reliably guarantee that the **UART2 (RS485-2)** port protocol will be automatically configured to **001 - JK BMS RS485 Modbus V1.0**, which allows **YamBMS** to access BMS informations.
|
||||
> YamBMS users have confirmed that it is possible to resolve this issue by performing an [Erase History Data](BMS_JK-PB.md#erase-history-data) from the JK app on a smartphone.
|
||||
|
||||
|
||||
> The alternative solution is to use the **UART1 (RS485-1)** port configured with the **001 - JK BMS RS485 Modbus V1.0** protocol from the JK application.
|
||||
> Downgrading to **V19.10** does not guarantee to correct this problem, [please read this information before downgrading](BMS_JK-PB.md#downgrading-to-1910).
|
||||
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The most important thing for proper functioning of YamBMS is that **the voltage of your BMS is well calibrated**.
|
||||
> YamBMS logic is based on the `min_cell_voltage` and `max_cell_voltage` voltages of your BMS.
|
||||
|
||||
@@ -9,17 +9,21 @@
|
||||
> [!IMPORTANT]
|
||||
> BMS monitoring with `UART` or `RS485` is recommended.
|
||||
|
||||
## Number of BMS supported
|
||||
## BMS Support Capacity
|
||||
|
||||
* 2x BMS with `Bluetooth` (BLE stack consumes significant amount of RAM on device and can cause crash and reboot)
|
||||
* 3x `JK-B` BMS with `UART/RS485`
|
||||
* several `JK-PB` BMS with `RS485` (already tested with 7 BMS)
|
||||
Based on hardware limitations and testing, this board supports:
|
||||
|
||||
Note: these are theoretical limits, not all combinations have been tested.
|
||||
| Communication Method | Maximum BMS | Notes |
|
||||
|----------------------|-------------|-------|
|
||||
| **RS485** | Multiple BMS | Best option for monitoring many BMS units |
|
||||
| **UART** | 3× BMS | Must be connected to the GPIOs header |
|
||||
| **Bluetooth (BLE)** | 3× BMS (ESP32-S3) | BLE stack consumes significant RAM, may cause crashes/reboots |
|
||||
|
||||
**Note:** These are theoretical limits. Not all combinations have been tested.
|
||||
|
||||
## UART/IO Expander
|
||||
|
||||
It would be possible to add one or more [WK2168 4x UART expander](https://esphome.io/components/weikai.html) to increase the number of BMS monitored with `UART`.
|
||||
It would be possible to add one or more [WK2168 4x UART expander](https://esphome.io/components/weikai.html) to increase the number of `UART` port.
|
||||
|
||||
## Build your own PCB
|
||||
|
||||
@@ -0,0 +1,356 @@
|
||||
# YamBMS - LilyGo T-Connect
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
> [!IMPORTANT]
|
||||
> Make sure to order the version with **3x RS485** and **1x CAN**.
|
||||
|
||||
## Overview
|
||||
|
||||
The LilyGo T-Connect is a multi-functional development board based on the ESP32-S3-R8 chip, equipped with 8MB PSRAM and 16MB Flash, supporting Wi-Fi/Bluetooth dual-mode communication and RS485/CAN industrial protocols. This board is particularly well-suited for the YamBMS project thanks to its multiple communication interfaces including up to 3 RS485 ports and 1 CAN bus port.
|
||||
|
||||
**Key Features:**
|
||||
- Multi-protocol Support: Supports up to three sets of RS485 and one set of CAN bus
|
||||
- Industrial Communication: RS485 (UART protocol) and CAN bus (TWAI protocol)
|
||||
- Flexible Configuration: Supports switching between CAN and RS485 modules
|
||||
- Rich Interfaces: Integrated APA102 LED driver, QWIIC expansion interface
|
||||
- Industrial Design: Wide voltage input (7V-12V DC), 4 positioning holes for easy installation
|
||||
|
||||
<img src="../..//images/MCU_ESP32-S3_LilyGo-T-Connect_1.jpg" width="500"> <img src="../..//images/MCU_ESP32-S3_LilyGo-T-Connect_2.jpg" width="500">
|
||||
|
||||
## Board Specifications
|
||||
|
||||
The T-Connect is available as a single version with the following specifications:
|
||||
|
||||
| Specification | Details |
|
||||
|---------------|---------|
|
||||
| Model | T-Connect |
|
||||
| MCU | ESP32-S3-R8 |
|
||||
| FLASH | 16MB |
|
||||
| PSRAM | 8MB (Octal SPI) |
|
||||
| RS485 | 3× Isolated RS485 interface |
|
||||
| CAN Bus | 1× Isolated CAN interface |
|
||||
| LED Driver | APA102 RGB |
|
||||
| Wireless | Wi-Fi 802.11 b/g/n / Bluetooth 5.0 (BLE) |
|
||||
| USB | Type-C (5V/500mA) |
|
||||
| Power Input | 7V-12V DC |
|
||||
| Expansion | 1× QWIIC Interface |
|
||||
| Buttons | RESET + BOOT |
|
||||
| Mounting | 4× 2mm positioning holes |
|
||||
| Dimensions | 94×83×13mm |
|
||||
|
||||
**Note:** The T-Connect supports switching configuration between CAN and RS485 modules through onboard jumpers, allowing maximum flexibility with up to 3 RS485 ports + 1 CAN port simultaneously.
|
||||
|
||||
## Interfaces Support Capacity
|
||||
|
||||
Based on hardware limitations and testing, this board supports:
|
||||
|
||||
| Interface | Maximum | Notes |
|
||||
|-----------|---------|-------|
|
||||
| **CAN** | 1x bus | CAN bus to BMS or Inverter |
|
||||
| **RS485** | 3x bus | Best option for monitoring many BMS of the same brand (**shared with UART**) |
|
||||
| **UART** | 3× devices¹ | Must be connected to the **GPIOs header** (**shared with RS485**) |
|
||||
| **Bluetooth (BLE)** | 3× devices¹ | BLE stack consumes significant RAM, may cause crashes/reboots |
|
||||
|
||||
¹ BMS / Balancer / Shunt
|
||||
|
||||
**Note:** These are theoretical limits. Not all combinations have been tested.
|
||||
|
||||
## UART/IO Expander
|
||||
|
||||
It would be possible to add one or more [WK2168 4x UART expander](https://esphome.io/components/weikai.html) to increase the number of `UART` port.
|
||||
|
||||
## Power Supply
|
||||
|
||||
The LilyGo T-Connect board can be powered using two methods:
|
||||
|
||||
### Option 1: USB-C Port
|
||||
- Connect a USB-C cable to the USB-C port on the board
|
||||
- Provides **5V / 500mA**
|
||||
- Recommended for programming and testing
|
||||
- Supports USB OTG functionality
|
||||
|
||||
### Option 2: External Power Supply (DC Input)
|
||||
- Voltage range: **7V to 12V DC**
|
||||
- Connect to the dedicated DC power terminal (usually labeled VIN/GND or PWR)
|
||||
- Recommended for permanent installations and industrial environments
|
||||
- Provides stable power for all communication interfaces
|
||||
- Internal voltage regulator steps down to 5V and 3.3V for the ESP32-S3
|
||||
|
||||
**Important:** Do not power the board simultaneously through USB-C and the external DC terminal to avoid potential damage to the power regulation circuitry.
|
||||
|
||||
## Port Identification
|
||||
|
||||
### Communication Ports Layout
|
||||
|
||||
The T-Connect board features 4 communication ports that share pins through a switching mechanism. The board supports up to **3 RS485 ports + 1 CAN port** simultaneously through proper configuration.
|
||||
|
||||
**Pin Assignment :**
|
||||
|
||||
| Port | TX Pin | RX Pin | Protocol |
|
||||
|------|--------|--------|----------|
|
||||
| Port 1 | IO4 | IO5 | RS485 |
|
||||
| Port 2 | IO6 | IO7 | RS485 |
|
||||
| Port 3 | IO17 | IO18 | RS485 |
|
||||
| Port 4 | IO9 | IO10 | CAN |
|
||||
|
||||
### RS485 ports
|
||||
|
||||
The RS485 ports are positioned at locations **No.1** to **No.3** (see photo at the beginning of this page).
|
||||
|
||||
**RS485 Terminal Pinout:**
|
||||
- **SG** - Signal Ground (for shield connection and noise immunity)
|
||||
- **L** - RS485 A (Data+)
|
||||
- **H** - RS485 B (Data-)
|
||||
- **DG** - Data Ground (common reference ground)
|
||||
|
||||
### CAN port
|
||||
|
||||
The CAN bus port is positioned at location **No.4** (see photo at the beginning of this page).
|
||||
|
||||
**CAN Terminal Pinout:**
|
||||
- **SG** - Signal Ground (for shield connection and noise immunity)
|
||||
- **L** - CAN L (CAN Low)
|
||||
- **H** - CAN H (CAN High)
|
||||
- **DG** - Data Ground (common reference ground)
|
||||
|
||||
## Wiring Instructions
|
||||
|
||||
### Connecting RS485 Devices
|
||||
|
||||
To connect an RS485 device to any of the configured RS485 ports:
|
||||
|
||||
| RS485 | Terminal Block |
|
||||
|-------|----------------|
|
||||
| - | SG : Shield/Signal Ground (optional but recommended) |
|
||||
| A + | L (RS485 A, Data+ non-inverting) |
|
||||
| B - | H (RS485 B, Data- inverting) |
|
||||
| GND | DG : Data/Device Ground (optional but recommended) |
|
||||
|
||||
**Wiring Steps:**
|
||||
1. Identify the A and B wires from your RS485 device (often labeled as D+/D- or A/B)
|
||||
2. Connect the **A wire (D+)** to the **L pin** of the RS485 port
|
||||
3. Connect the **B wire (D-)** to the **H pin** of the RS485 port
|
||||
4. **Connect the ground wire** to the **DG pin** for common reference (highly recommended)
|
||||
5. If using **shielded cable**, connect the shield to the **SG pin** (recommended for noisy environments)
|
||||
|
||||
**Ground Connection Best Practices:**
|
||||
- **Always connect DG (Data Ground)** to provide a common reference between devices
|
||||
- This prevents communication errors caused by ground potential differences
|
||||
- Over long distances or in industrial environments, ground connection is critical
|
||||
- RS485 can tolerate -7V to +12V common mode voltage, but proper grounding prevents issues
|
||||
|
||||
**Shield Connection (for shielded cables):**
|
||||
- Connect the cable shield to **SG (Signal Ground)** at one end only to avoid ground loops
|
||||
- In electrically noisy environments, shield connection significantly improves noise immunity
|
||||
- The shield should be connected at the end closest to earth ground
|
||||
|
||||
**Important Notes:**
|
||||
- RS485 polarity matters: swapping A and B will prevent communication
|
||||
- If communication fails, try swapping the A and B connections
|
||||
- Use twisted pair cable for RS485 connections to reduce noise and interference
|
||||
- The board supports UART protocol for RS485 communication
|
||||
- According to official testing: RS485 operates at **115200 baud rate** with a **communication distance up to 35 meters**
|
||||
|
||||
### Connecting CAN Bus Devices
|
||||
|
||||
To connect a CAN bus device to the CAN port:
|
||||
|
||||
| CAN bus | Terminal Block |
|
||||
|---------|----------------|
|
||||
| - | SG : Shield/Signal Ground (optional but recommended) |
|
||||
| CAN L | L (CAN Low) |
|
||||
| CAN H | H (CAN High) |
|
||||
| GND | DG : Data/Device Ground (optional but recommended) |
|
||||
|
||||
**Wiring Steps:**
|
||||
1. Identify the CAN H and CAN L wires from your CAN device
|
||||
2. Connect the **CAN H wire** to the **H pin** of the CAN port
|
||||
3. Connect the **CAN L wire** to the **L pin** of the CAN port
|
||||
4. **Connect the ground wire** to the **DG pin** for common reference (optional but recommended)
|
||||
5. If using **shielded cable**, connect the shield to the **SG pin** (recommended for noisy environments)
|
||||
|
||||
**Ground Connection Best Practices:**
|
||||
- **Always connect DG (Data Ground)** to provide a common reference between devices
|
||||
- Ground connection is especially important for CAN bus to prevent communication failures
|
||||
- Helps maintain proper common mode voltage range
|
||||
- Essential for long cable runs or installations with multiple power sources
|
||||
|
||||
**Shield Connection (for shielded cables):**
|
||||
- Connect the cable shield to **SG (Signal Ground)** at one end only to avoid ground loops
|
||||
- In electrically noisy industrial environments, shield connection is highly recommended
|
||||
- Many CAN applications in automotive and industrial settings require shielded cables
|
||||
|
||||
**Important Notes:**
|
||||
- CAN bus requires proper termination at both ends of the bus (see Termination Resistors section)
|
||||
- Use twisted pair cable specifically designed for CAN bus (recommended impedance: 120Ω)
|
||||
- The board uses TWAI (Two-Wire Automotive Interface) protocol for CAN communication
|
||||
- According to official testing: CAN operates at **500 kbps** with a **communication distance up to 35 meters**
|
||||
- Maximum cable length depends on baud rate (shorter distances for higher speeds)
|
||||
|
||||
## Additional Features
|
||||
|
||||
### APA102 LED Driver
|
||||
|
||||
The T-Connect includes an onboard APA102 LED driver for controlling RGB light strips:
|
||||
|
||||
**Pin Assignment:**
|
||||
- **APA102_DATA**: GPIO8
|
||||
- **APA102_CLOCK**: GPIO3
|
||||
|
||||
This allows direct control of addressable RGB LED strips without additional hardware.
|
||||
|
||||
### QWIIC Expansion Interface
|
||||
|
||||
The T-Connect features a **QWIIC interface** for easy connection to the QWIIC ecosystem of I2C sensors and modules, enabling simple plug-and-play expansion without soldering.
|
||||
|
||||
### Mounting
|
||||
|
||||
The board includes **4× 2mm positioning holes** for secure mounting in enclosures or on DIN rails, ideal for permanent industrial installations.
|
||||
|
||||
## Bus Termination
|
||||
|
||||
Both RS485 and CAN bus networks require termination resistors to prevent signal reflections and ensure reliable communication.
|
||||
|
||||
### Important Note About Termination
|
||||
|
||||
**The T-Connect board does not appear to have built-in switchable termination resistors** based on the official documentation. Users will need to add external termination resistors when required.
|
||||
|
||||
### RS485 Termination Requirements
|
||||
|
||||
RS485 networks require **120Ω termination resistors** at both ends of the bus:
|
||||
|
||||
**When You Need Termination:**
|
||||
- At the **first and last devices** on the RS485 bus
|
||||
- For cable runs longer than a few meters
|
||||
- In electrically noisy environments
|
||||
|
||||
**How to Add External Termination:**
|
||||
- Connect a 120Ω resistor between the A (L pin) and B (H pin) terminals
|
||||
- Only install termination at the two endpoints of the bus
|
||||
- If the T-Connect is in the middle of the network, do not add termination
|
||||
|
||||
### CAN Bus Termination Requirements
|
||||
|
||||
CAN bus networks require exactly **two 120Ω termination resistors** (one at each end):
|
||||
|
||||
**Critical CAN Termination Rules:**
|
||||
- Exactly **two 120Ω resistors** must be present on the entire CAN bus
|
||||
- One resistor at each physical end of the bus
|
||||
- Without proper termination, CAN communication will fail
|
||||
- With proper termination, you should measure ~60Ω between CAN H and CAN L
|
||||
|
||||
**How to Add External Termination:**
|
||||
- Connect a 120Ω resistor between CAN H (H pin) and CAN L (L pin) terminals
|
||||
- Only install at the two endpoints of the CAN bus
|
||||
- Many CAN devices (like inverters) have built-in termination - check your device documentation
|
||||
|
||||
**Tip:** For point-to-point connections (e.g., T-Connect ↔ Inverter), you typically need termination at both ends. Check if your inverter has built-in termination before adding external resistors.
|
||||
|
||||
## Typical YamBMS Configuration
|
||||
|
||||
For a typical YamBMS setup with the LilyGo T-Connect board:
|
||||
|
||||
1. **Power Supply:**
|
||||
- For bench testing: Connect USB-C cable (5V/500mA)
|
||||
- For permanent installation: Connect 12V DC to the external power terminal (recommended)
|
||||
|
||||
2. **BMS Communication:**
|
||||
- Connect your BMS (e.g., JK, JBD, SEPLOS, PACE, BASEN) to RS485 ports (No.1 to No.3)
|
||||
- Wire according to: **L=RS485 A**, **H=RS485 B**, **DG=Ground**
|
||||
- Connect shield to SG if using shielded cable
|
||||
|
||||
3. **Inverter Communication:**
|
||||
- Connect your inverter (e.g., Deye, Sofar, Growatt, Victron) to the CAN port (No.4)
|
||||
- Wire according to: **L=CAN L**, **H=CAN H**, **DG=Ground**
|
||||
- Connect shield to SG if using shielded cable
|
||||
- Typical CAN speed: 500 kbps
|
||||
|
||||
4. **Bus Termination:**
|
||||
- **RS485:** Add external 120Ω resistor between L and H pins if the T-Connect is at the end of the RS485 bus
|
||||
- **CAN:** Check if your inverter has built-in termination. If not, add external 120Ω resistor between CAN H and CAN L
|
||||
- For point-to-point connections, you typically need termination at both devices
|
||||
|
||||
## Additional Resources
|
||||
|
||||
### Official Documentation
|
||||
- [LilyGo T-Connect Official Wiki](https://wiki.lilygo.cc/get_started/en/High_speed/T-Connect/T-Connect.html)
|
||||
- [LilyGo Official Store](https://lilygo.cc/products/t-connect)
|
||||
- [LilyGo Official GitHub](https://github.com/Xinyuan-LilyGO)
|
||||
- [T-Connect GitHub Repository](https://github.com/Xinyuan-LilyGO/T-Connect)
|
||||
|
||||
### Datasheets & Schematics
|
||||
- [ESP32-S3 Datasheet](https://www.espressif.com/sites/default/files/documentation/esp32-s3_datasheet_en.pdf)
|
||||
- [T-Connect V1.0 Schematic (PDF)](https://github.com/Xinyuan-LilyGO/T-Connect/blob/main/project/T-Connect_V1.0.pdf)
|
||||
- [TD501MCANFD Datasheet](https://github.com/Xinyuan-LilyGO/T-Connect-Pro/blob/main/information/TD501MCANFD_MORNSUN.pdf)
|
||||
- [TD501D485H-A Datasheet](https://github.com/Xinyuan-LilyGO/T-Connect-Pro/blob/main/information/TD501D485H-A_K-CUT.pdf)
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### No Communication on RS485
|
||||
- Verify the port is configured for RS485 mode (check jumper settings)
|
||||
- Verify correct A/B wiring (L=A, H=B). Try swapping if communication fails
|
||||
- Check baud rate matches between devices (tested at 115200 for T-Connect)
|
||||
- **Add external 120Ω termination resistors** at both ends of the RS485 bus if not already present
|
||||
- Test cable continuity and check for damaged twisted pair cable
|
||||
- Maximum tested distance: 35 meters at 115200 baud
|
||||
|
||||
### No Communication on CAN Bus
|
||||
- Verify the port is configured for CAN mode (check jumper settings)
|
||||
- Verify CAN H and CAN L are correctly connected (H to H pin, L to L pin)
|
||||
- **Ensure exactly two 120Ω termination resistors are present** on the entire CAN bus (add external resistors if needed)
|
||||
- Verify CAN bus speed matches all devices (tested at 500 kbps for T-Connect)
|
||||
- Measure resistance between CAN H and CAN L with multimeter (should be ~60Ω with proper termination)
|
||||
- Check TWAI protocol configuration in your software
|
||||
- Maximum tested distance: 35 meters at 500 kbps
|
||||
|
||||
### Board Not Powering Up
|
||||
- Check power supply voltage (7-12V DC for external power, 5V for USB-C)
|
||||
- Verify polarity of external power connection (check + and - terminals)
|
||||
- Try powering via USB-C for testing
|
||||
- Check for short circuits on terminal blocks
|
||||
- Inspect for damaged components or solder bridges
|
||||
|
||||
### Programming/Upload Issues
|
||||
- Hold down the **BOOT button** while uploading firmware
|
||||
- Verify USB cable supports data transfer (not charge-only cable)
|
||||
- Check that correct COM port is selected in Arduino IDE or PlatformIO
|
||||
- Ensure USB CDC is enabled in Arduino IDE settings
|
||||
- Try different USB cable or USB port on your computer
|
||||
|
||||
### Termination Resistor Tips
|
||||
- **RS485:** Use 1/4W 120Ω resistors between L and H pins at both bus ends
|
||||
- **CAN:** Use 1/4W 120Ω resistors between CAN H and CAN L at both bus ends
|
||||
- Verify termination with multimeter: ~60Ω for CAN, ~60Ω for RS485 (when measured across the entire bus)
|
||||
- Many devices have built-in termination - check documentation before adding external resistors
|
||||
|
||||
## Comparison with Other Boards
|
||||
|
||||
### Waveshare ESP32-S3-RS485-CAN vs LilyGo T-Connect
|
||||
|
||||
| Feature | Waveshare | LilyGo T-Connect |
|
||||
|---------|-----------|------------------|
|
||||
| RS485 Ports | 1 (isolated) | Up to 3 (isolated) |
|
||||
| CAN Ports | 1 (isolated) | 1 (isolated) |
|
||||
| Built-in Termination | ✅ Yes (120Ω jumper-selectable) | ❌ No (external resistors required) |
|
||||
| Power Isolation | ✅ Yes | ❌ No |
|
||||
| Signal Isolation | ✅ Yes (RS485 & CAN) | ✅ Yes (RS485 & CAN up to 2500V) |
|
||||
| Enclosure | ✅ DIN rail ABS case included | ❌ No enclosure |
|
||||
| Power Input | 7-36V DC or USB-C | 7-12V DC or USB-C |
|
||||
| LED Indicators | PWR, RS485 TX/RX, CAN | PWR, APA102 support |
|
||||
| Price | Moderate | Moderate |
|
||||
| Best For | Single RS485 + CAN with isolation | Multiple RS485 + CAN with isolation |
|
||||
|
||||
**Summary:** The Waveshare board excels in **industrial-grade protection and built-in termination**, while the LilyGo offers **more RS485 ports and configuration flexibility**. Choose based on your specific needs:
|
||||
- **Waveshare**: Best for harsh environments, built-in termination, ease of installation
|
||||
- **LilyGo**: Best for multiple RS485 devices, flexible configuration, compact size
|
||||
|
||||
---
|
||||
|
||||
**License:** This documentation is part of the YamBMS project and is licensed under GPLv3.
|
||||
|
||||
**Disclaimer:** Always verify specifications and wiring with the official LilyGo documentation before deployment. This guide is community-created and may not reflect the latest product revisions.
|
||||
@@ -0,0 +1,474 @@
|
||||
# YamBMS - M5Stack AtomS3
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
> [!IMPORTANT]
|
||||
> **GPIO Limitation:** AtomS3 provides **very few GPIOs**. This solution works best for:
|
||||
> - **Supervising multiple RS485 BMS**
|
||||
> - Limited number of UART BMS (3 maximum)
|
||||
> - Applications where compact size is priority
|
||||
|
||||
## Overview
|
||||
|
||||
The M5Stack **AtomS3** combined with the **Atomic CAN Base** provides a compact and powerful solution for YamBMS applications. This combination offers CAN bus communication with isolation, a built-in display, and expandability through additional M5Stack units.
|
||||
|
||||
**Key Features:**
|
||||
- Compact design (24×24×13mm AtomS3 footprint)
|
||||
- ESP32-S3 with 8MB Flash
|
||||
- Built-in 0.85" IPS display (128×128 pixels)
|
||||
- Isolated CAN bus communication (up to 1Mbps)
|
||||
- 6-axis IMU (MPU6886)
|
||||
- Expandable with M5Stack Units (RS485, CAN, etc.)
|
||||
- Programmable button
|
||||
- Multiple development platforms supported
|
||||
|
||||
## Board Variants & Components
|
||||
|
||||
### AtomS3 Controllers
|
||||
|
||||
Choose one AtomS3 controller to clip onto the Atomic CAN Base:
|
||||
|
||||
| [AtomS3 Lite](https://docs.m5stack.com/en/core/AtomS3%20Lite) | [AtomS3](https://docs.m5stack.com/en/core/AtomS3) | [AtomS3R (8MB PSRAM)](https://docs.m5stack.com/en/core/AtomS3R) |
|
||||
|-----|-----|-----|
|
||||
| <img src="../../images/MCU_AtomS3_Lite.png" width="300"> | <img src="../../images/MCU_AtomS3.png" width="300"> | <img src="../../images/MCU_AtomS3R.png" width="300"> |
|
||||
|
||||
| Model | Flash | PSRAM | Display | IMU | Best For |
|
||||
|-------|-------|-------|---------|-----|----------|
|
||||
| **[AtomS3 Lite](https://docs.m5stack.com/en/core/AtomS3%20Lite)** (C124) | 8MB | No | 0.85" IPS | MPU6886 | Budget projects |
|
||||
| **[AtomS3](https://docs.m5stack.com/en/core/AtomS3)** (C123) | 8MB | No | 0.85" IPS | MPU6886 | Standard applications |
|
||||
| **[AtomS3R](https://docs.m5stack.com/en/core/AtomS3R)** (C126) | 8MB | **8MB** | 0.85" IPS | MPU6886 | **Recommended** (extra RAM) |
|
||||
|
||||
**Recommendation:** Choose **AtomS3R (C126)** if using Bluetooth BLE for BMS communication, as the extra 8MB PSRAM helps prevent crashes when the BLE stack consumes significant RAM.
|
||||
|
||||
### Base & Communication Units
|
||||
|
||||
| [Atomic CAN Base](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base) | [CAN Unit](https://docs.m5stack.com/en/unit/can) | [RS485 Unit](https://docs.m5stack.com/en/unit/iso485) |
|
||||
|-----|-----|-----|
|
||||
| <img src="../../images/CAN_Transceiver_M5Stack_Atomic_CAN_Base.png" width="300"> | <img src="../../images/CAN_Transceiver_M5Stack_CAN_Unit.png" width="300"> | <img src="../../images/RS485_Transceiver_M5stack_SKU-U094_RS485_Isolated_Unit.png" width="300"> |
|
||||
|
||||
| Component | Type | Features | Use Case |
|
||||
|-----------|------|----------|----------|
|
||||
| **[Atomic CAN Base](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base)** (A103) | CAN Base | Isolated CAN, up to 1Mbps, 110 nodes | **Recommended** for inverter |
|
||||
| **[CAN Unit](https://docs.m5stack.com/en/unit/can)** (U085) | HY2.0 Unit | Isolated CAN via Grove port | Alternative CAN solution |
|
||||
| **[RS485-ISO Unit](https://docs.m5stack.com/en/unit/iso485)** (U094) | HY2.0 Unit | Isolated RS485, up to 500kbps, 256 nodes | For RS485 BMS or multi-node |
|
||||
|
||||
## Interfaces Support Capacity
|
||||
|
||||
Based on hardware limitations and testing, this board supports:
|
||||
|
||||
| Interface | Maximum | Notes |
|
||||
|-----------|---------|-------|
|
||||
| **CAN** | 1x bus | CAN bus to BMS or Inverter (**after adding a CAN base/unit**) |
|
||||
| **RS485** | 1x bus | Best option for monitoring many BMS of the same brand (**after adding a RS485 base/unit**) |
|
||||
| **UART** | 3× devices¹ | CAN be connected to the **HY2.0 interface** or **Atomic Base GPIOs header** (**shared with RS485**) |
|
||||
| **Bluetooth (BLE)** | 3× devices¹ | BLE stack consumes significant RAM, may cause crashes/reboots |
|
||||
|
||||
¹ BMS / Balancer / Shunt
|
||||
|
||||
**Note:** These are theoretical limits. Not all combinations have been tested. For large installations with many BMS units, consider boards with more GPIOs like the LilyGo T-Connect or Waveshare ESP32-S3-RS485-CAN.
|
||||
|
||||
## AtomS3 Specifications
|
||||
|
||||
### Hardware Specifications
|
||||
|
||||
| Specification | Details |
|
||||
|---------------|---------|
|
||||
| **Microcontroller** | ESP32-S3FN8 |
|
||||
| **Processor** | Xtensa 32-bit LX7 dual-core @ up to 240MHz |
|
||||
| **Flash** | 8MB |
|
||||
| **PSRAM** | None (AtomS3 Lite/AtomS3) / 8MB Octal SPI (AtomS3R) |
|
||||
| **Display** | 0.85" IPS LCD, 128×128 resolution |
|
||||
| **UART** | 1x HY2.0 interface (not isolated) |
|
||||
| **IMU** | MPU6886 (6-axis gyro + accel, I2C 0x68) |
|
||||
| **Button** | 1× Programmable button |
|
||||
| **Infrared** | IR transmitter built-in |
|
||||
| **USB** | USB Type-C (power + programming) |
|
||||
| **DC-DC** | SY8089 (5V to 3.3V) |
|
||||
| **Power Input** | 5V via USB Type-C |
|
||||
| **Operating Temp** | 0°C ~ 40°C |
|
||||
| **Dimensions** | 24.0 × 24.0 × 12.9mm |
|
||||
| **Weight** | 6.9g |
|
||||
|
||||
### GPIO Pinout
|
||||
|
||||
**Available GPIOs (Bottom Pins):**
|
||||
- **G5** / **G6** / **G7** / **G8** / **G38** / **G39**
|
||||
- Power: **5V**, **3.3V**, **GND**
|
||||
|
||||
**HY2.0-4P Expansion Port:**
|
||||
| Pin | Color | Function |
|
||||
|-----|-------|----------|
|
||||
| 1 | Black | GND |
|
||||
| 2 | Red | 5V |
|
||||
| 3 | Yellow | G2 |
|
||||
| 4 | White | G1 |
|
||||
|
||||
**Internal Connections:**
|
||||
|
||||
| Peripheral | GPIO Pins | Notes |
|
||||
|------------|-----------|-------|
|
||||
| **LCD Display** | MOSI: G21, SCK: G17, CS: G15, RS: G33, RST: G34, BL: G16 | SPI interface |
|
||||
| **MPU6886 (IMU)** | SDA: G38, SCL: G39 | I2C address 0x68 |
|
||||
| **IR Transmitter** | Built-in | For infrared control |
|
||||
|
||||
## Atomic CAN Base Specifications
|
||||
|
||||
### Hardware Specifications
|
||||
|
||||
| Specification | Details |
|
||||
|---------------|---------|
|
||||
| **CAN Transceiver** | CA-IS3050G (isolated) |
|
||||
| **Maximum Rate** | 1 Mbps |
|
||||
| **Supported Nodes** | Up to 110 nodes |
|
||||
| **Loop Delay** | 150ns (low) |
|
||||
| **Common-mode Voltage** | -12V to +12V |
|
||||
| **Isolation** | Built-in isolated DC-DC |
|
||||
| **Protection** | Signal protection + electrical line protection |
|
||||
| **External Port** | VH3.96-4P terminal block |
|
||||
| **Operating Temp** | 0°C ~ 40°C |
|
||||
| **Dimensions** | 24 × 48 × 18mm |
|
||||
| **Weight** | 11.1g |
|
||||
|
||||
### Atomic CAN Base Pinout
|
||||
|
||||
The Atomic CAN Base connects to AtomS3 through the bottom pins:
|
||||
|
||||
| Pin | LEFT | RIGHT | Pin |
|
||||
|-----|------|-------|-----|
|
||||
| | | 1 | 3.3V |
|
||||
| | 2 | 3 | UART_TX (CAN_TX) |
|
||||
| | 4 | 5 | UART_RX (CAN_RX) |
|
||||
| 5V | 6 | 7 | |
|
||||
| GND | 8 | 9 | |
|
||||
|
||||
**CAN Terminal Block (VH3.96-4P):**
|
||||
- **CAN H** (CAN High)
|
||||
- **CAN L** (CAN Low)
|
||||
- **GND** (Ground)
|
||||
|
||||
**Note:** The exact UART pins used depend on configuration. Check the schematic for GPIO assignment.
|
||||
|
||||
## RS485-ISO Unit Specifications
|
||||
|
||||
If you need RS485 communication (e.g., for RS485 BMS, multi-node), add the **RS485-ISO Unit (U094)**:
|
||||
|
||||
| Specification | Details |
|
||||
|---------------|---------|
|
||||
| **Isolation Chip** | CA-IS3082W |
|
||||
| **Maximum Rate** | 500 kbps |
|
||||
| **Supported Nodes** | Up to 256 nodes |
|
||||
| **Isolation Voltage** | 1000V RMS |
|
||||
| **Protection** | Fail-safe, Overcurrent, Thermal shutdown, ±15kV ESD |
|
||||
| **Connection** | HY2.0-4P Grove cable to AtomS3 |
|
||||
| **Terminal** | VH-3.96 4P (A, B, GND, +V) |
|
||||
| **Dimensions** | 56.0 × 24.0 × 10.2mm |
|
||||
| **Weight** | 9.1g |
|
||||
|
||||
**RS485-ISO Unit Pinout:**
|
||||
|
||||
| HY2.0-4P | Black | Red | Yellow | White |
|
||||
|----------|-------|-----|--------|-------|
|
||||
| PORT.C | GND | 5V | UART_RX | UART_TX |
|
||||
|
||||
**Termination Resistor:** The RS485-ISO Unit includes a **120Ω termination resistor** (provided separately) that can be connected when the unit is at an endpoint of the RS485 bus.
|
||||
|
||||
## Wiring Instructions
|
||||
|
||||
### Connecting CAN Bus (Atomic CAN Base)
|
||||
|
||||
The Atomic CAN Base provides **isolated CAN communication** via a VH3.96-4P terminal block.
|
||||
|
||||
|
||||
| CAN bus | Terminal Block (VH3.96-4P) |
|
||||
|---------|----------------------------|
|
||||
| CAN H | H (CAN High) |
|
||||
| CAN L | L (CAN Low) |
|
||||
| GND | GND (optional) |
|
||||
|
||||
**Wiring Steps:**
|
||||
1. Clip the AtomS3 onto the Atomic CAN Base (ensure proper alignment)
|
||||
2. Identify CAN H and CAN L wires from your inverter or CAN device
|
||||
3. Connect **CAN H** to **H** (CAN H terminal)
|
||||
4. Connect **CAN L** to **L** (CAN L terminal)
|
||||
5. Connect **GND** to **GND** for common reference (optional)
|
||||
|
||||
**CAN Bus Best Practices:**
|
||||
- The Atomic CAN Base features **built-in isolation** for protection
|
||||
- CAN bus operates at up to **1 Mbps** data rate
|
||||
- Supports up to **110 nodes** on the bus
|
||||
- Use twisted pair cable (120Ω impedance recommended)
|
||||
- **Termination:** Add 120Ω resistors at both ends of the CAN bus
|
||||
- If the AtomS3 is at an endpoint, connect a termination resistor
|
||||
- Check if your inverter has built-in termination before adding external resistors
|
||||
|
||||
### Connecting RS485 (RS485-ISO Unit)
|
||||
|
||||
If using the RS485-ISO Unit for RS485 devices:
|
||||
|
||||
| RS485 | Terminal Block (VH3.96-4P) |
|
||||
|-------|-----------------------------|
|
||||
| A + | A (Data+ non-inverting) |
|
||||
| B - | B (Data- inverting) |
|
||||
| GND | GND (Ground reference) |
|
||||
|
||||
**Wiring Steps:**
|
||||
1. Connect the RS485-ISO Unit to the AtomS3 via the **HY2.0-4P Grove cable** (Yellow=RX, White=TX)
|
||||
2. Identify A and B wires from your RS485 device (often labeled D+/D- or A/B)
|
||||
3. Connect **RS485 A (D+)** to **Pin 1** (A terminal)
|
||||
4. Connect **RS485 B (D-)** to **Pin 2** (B terminal)
|
||||
5. Connect **GND** to **Pin 3** for common reference (recommended)
|
||||
|
||||
**RS485 Best Practices:**
|
||||
- The RS485-ISO Unit features **1000V isolation** for protection
|
||||
- RS485 operates at up to **500 kbps** data rate
|
||||
- Supports up to **256 nodes** on the bus
|
||||
- Use twisted pair cable for noise immunity
|
||||
- **Termination:** Connect the included **120Ω resistor** between A and B if the unit is at an endpoint
|
||||
- The unit includes **fail-safe protection** (outputs high if input is open or shorted)
|
||||
|
||||
## Power Supply
|
||||
|
||||
### AtomS3 Power Options
|
||||
|
||||
**USB Type-C Power:**
|
||||
- Connect a USB Type-C cable for **5V power**
|
||||
- Recommended for programming, debugging, and testing
|
||||
- Built-in **SY8089 DC-DC converter** steps down 5V to 3.3V for ESP32-S3
|
||||
- Typical power consumption: 150-300mA (idle to active WiFi)
|
||||
|
||||
**External 5V via HY2.0-4P Grove port:**
|
||||
- Useful when powering the entire assembly from an external 5V supply
|
||||
|
||||
## Programming & Development
|
||||
|
||||
### Entering Download Mode
|
||||
|
||||
If you have trouble uploading firmware to the AtomS3:
|
||||
|
||||
**Manual Download Mode:**
|
||||
1. **Press and hold the RESET button** (about 2 seconds)
|
||||
2. Wait until the **internal green LED lights up**
|
||||
3. **Release the button**
|
||||
4. The device is now in download mode and ready for flashing
|
||||
|
||||

|
||||
|
||||
### LCD Backlight Control
|
||||
|
||||
**Important:** The PWM signal frequency for the LCD backlight driver should be **500Hz**. A frequency that is too high may cause abnormal brightness adjustment functionality.
|
||||
|
||||
**Backlight GPIO:** G16
|
||||
|
||||
## Display Features
|
||||
|
||||
### Screen Specifications
|
||||
|
||||
| Specification | Details |
|
||||
|---------------|---------|
|
||||
| **Size** | 0.85 inch IPS LCD |
|
||||
| **Resolution** | 128 × 128 pixels |
|
||||
| **Color Depth** | 65K colors |
|
||||
| **Driver IC** | GC9107 |
|
||||
| **Interface** | SPI |
|
||||
| **Backlight** | PWM controlled (GPIO16) |
|
||||
|
||||
### Display Control Parameters
|
||||
|
||||
The AtomS3's display can be controlled with the following parameters (useful for YamBMS display management):
|
||||
|
||||
**Backlight Settings:**
|
||||
- **Backlight control**: Manual brightness control (0-100%)
|
||||
- **Backlight max level**: Limit the maximum brightness in general
|
||||
- **Backlight auto-dim level**: Desired brightness when dimmed down (set to 0 to switch off screen completely)
|
||||
- **Backlight auto-dim time**: Time in minutes after which the screen will dim down (set to 0 to disable auto-dimming)
|
||||
|
||||
**Behavior Notes:**
|
||||
- Device restores last screen brightness after boot
|
||||
- Auto-dim timer does not start automatically - it gets initially started by pressing the screen button
|
||||
- Button press bumps brightness to 100% until the timer dims down again
|
||||
- This provides a lightweight solution without complex automation
|
||||
|
||||
## IMU (MPU6886)
|
||||
|
||||
The AtomS3 includes a built-in **MPU6886** 6-axis IMU:
|
||||
|
||||
| Sensor | Details |
|
||||
|--------|---------|
|
||||
| **Model** | MPU6886 |
|
||||
| **Interface** | I2C (address 0x68) |
|
||||
| **Pins** | SDA: GPIO38, SCL: GPIO39 |
|
||||
| **Features** | 3-axis gyroscope + 3-axis accelerometer |
|
||||
|
||||
**Use Cases for YamBMS:**
|
||||
- Orientation detection
|
||||
- Vibration monitoring
|
||||
- Installation angle verification
|
||||
- Advanced motion-based alerts (optional)
|
||||
|
||||
**Note:** The I2C pins on the back of the AtomS3 share the same bus with the MPU6886.
|
||||
|
||||
## Typical YamBMS Configuration
|
||||
|
||||
### Configuration 1: AtomS3 + Atomic CAN Base + RS485-ISO Unit (Full Setup)
|
||||
|
||||
**Best for:** Multiple RS485 BMS + inverter via CAN
|
||||
|
||||
**Components:**
|
||||
- AtomS3R (recommended)
|
||||
- Atomic CAN Base (A103)
|
||||
- RS485-ISO Unit (U094)
|
||||
|
||||
**Connections:**
|
||||
1. Clip AtomS3R onto Atomic CAN Base
|
||||
2. Connect inverter to CAN terminal (CAN H/L)
|
||||
3. Connect RS485-ISO Unit to AtomS3 via Grove cable (HY2.0-4P)
|
||||
4. Connect BMS RS485 bus to RS485 terminals (A/B)
|
||||
5. Power via USB Type-C
|
||||
6. Add termination resistors at bus endpoints
|
||||
|
||||
**GPIO Usage:**
|
||||
- CAN: Uses UART pins via Atomic CAN Base
|
||||
- RS485: Uses G1/G2 via HY2.0-4P Grove port
|
||||
- Display: Internal SPI (pre-configured)
|
||||
|
||||
### Configuration 2: BLE + CAN (Compact Wireless BMS)
|
||||
|
||||
**Best for:** 2-3 BLE devices + inverter via CAN
|
||||
|
||||
**Components:**
|
||||
- AtomS3R (8MB PSRAM required for stable BLE)
|
||||
- Atomic CAN Base (A103)
|
||||
|
||||
**Connections:**
|
||||
1. Clip AtomS3R onto Atomic CAN Base
|
||||
2. Connect inverter to CAN terminal
|
||||
3. Configure BMS via Bluetooth (up to 3× BMS maximum)
|
||||
4. Power via USB Type-C
|
||||
|
||||
**Limitations:**
|
||||
- BLE stack consumes significant RAM
|
||||
- May cause crashes/reboots with >2 BMS
|
||||
- No physical RS485 connection
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### AtomS3 Not Entering Download Mode
|
||||
- **Solution:** Press and hold RESET button (~2 seconds) until green LED lights up, then release
|
||||
- Try different USB cable (must support data transfer)
|
||||
- Check USB drivers are installed
|
||||
|
||||
### CAN Bus Communication Issues
|
||||
- Verify CAN H and CAN L are correctly connected (not swapped)
|
||||
- Check that CAN bus has **exactly two 120Ω termination resistors** (one at each end)
|
||||
- Verify CAN bus speed matches inverter (typically 500kbps)
|
||||
- Measure resistance between CAN H and CAN L (should be ~60Ω with proper termination)
|
||||
- Check isolation: the Atomic CAN Base has built-in isolation, but verify connections
|
||||
|
||||
### RS485 Communication Issues
|
||||
- Verify A and B wiring (try swapping if communication fails)
|
||||
- Check baud rate matches all RS485 devices
|
||||
- Ensure ground (GND) is connected for common reference
|
||||
- Add 120Ω termination resistor at RS485-ISO Unit if at bus endpoint
|
||||
- The RS485-ISO Unit has **fail-safe protection** - if input is open/shorted, receiver outputs high
|
||||
|
||||
### BLE Connection Issues (Bluetooth BMS)
|
||||
- AtomS3R (8MB PSRAM) strongly recommended for BLE
|
||||
- BLE stack consumes significant RAM - limit to 3 BMS maximum
|
||||
- May cause crashes/reboots if too many BLE connections
|
||||
- Consider switching to RS485 for multiple BMS units
|
||||
|
||||
### Display Issues
|
||||
- **Backlight frequency:** Ensure PWM frequency is **500Hz** (not higher)
|
||||
- **Brightness control:** Use manual control via button or software
|
||||
- **Auto-dim not working:** Timer requires manual activation by pressing button after boot
|
||||
|
||||
### GPIO Limitation Issues
|
||||
- **Problem:** Not enough GPIOs for all sensors/devices
|
||||
- **Solution:** Use I2C-based sensors (shares I2C bus with IMU)
|
||||
- **Alternative:** Consider boards with more GPIOs (LilyGo T-Connect, Waveshare ESP32-S3-RS485-CAN)
|
||||
|
||||
## Additional Resources
|
||||
|
||||
### Official M5Stack Documentation
|
||||
- [AtomS3 Official Docs](https://docs.m5stack.com/en/core/AtomS3)
|
||||
- [AtomS3 Lite Official Docs](https://docs.m5stack.com/en/core/AtomS3%20Lite)
|
||||
- [AtomS3R Official Docs](https://docs.m5stack.com/en/core/AtomS3R)
|
||||
- [Atomic CAN Base Official Docs](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base)
|
||||
- [RS485-ISO Unit Official Docs](https://docs.m5stack.com/en/unit/iso485)
|
||||
|
||||
### Schematics & Datasheets
|
||||
- [AtomS3 Schematic PDF](https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/Sch_M5_AtomS3_v1.0.pdf)
|
||||
- [AtomS3 IMU Schematic PDF](https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/Sch_AtomS3_IMU.pdf)
|
||||
- [ESP32-S3 Datasheet](https://m5stack-doc.oss-cn-shenzhen.aliyuncs.com/472/esp32-s3_datasheet_en.pdf)
|
||||
- [MPU6886 Datasheet](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/MPU-6886-000193%2Bv1.1_GHIC_en.pdf)
|
||||
- [CA-IS3050G Datasheet](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/CA-IS3050G.pdf) (CAN transceiver)
|
||||
- [CA-IS3082W Datasheet](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/IS3082W.pdf) (RS485 transceiver)
|
||||
|
||||
### Software Libraries
|
||||
- [M5AtomS3 Arduino Library](https://github.com/m5stack/M5AtomS3)
|
||||
- [M5Unified Library](https://github.com/m5stack/M5Unified)
|
||||
- [AtomS3 Factory Firmware](https://github.com/m5stack/M5AtomS3-UserDemo)
|
||||
|
||||
### Where to Buy
|
||||
- [M5Stack Official Store](https://m5stack.com/)
|
||||
- [M5Stack AliExpress](https://m5stack.aliexpress.com/store/911661199)
|
||||
- [M5Stack Amazon](https://www.amazon.com/shops/m5stack)
|
||||
- [M5Stack Distributors](https://m5stack.com/distributor)
|
||||
|
||||
## Product Comparison
|
||||
|
||||
### AtomS3 vs Other YamBMS Boards
|
||||
|
||||
| Feature | AtomS3 + Atomic CAN | LilyGo T-Connect | Waveshare ESP32-S3-RS485-CAN |
|
||||
|---------|---------------------|------------------|------------------------------|
|
||||
| **Size** | Very compact (24×24mm) | Medium (94×83mm) | Medium with DIN rail case |
|
||||
| **Display** | ✅ 0.85" IPS (128×128) | ❌ No | ❌ No |
|
||||
| **RS485 Ports** | 1 (via Unit) | Up to 3 | 1 (isolated) |
|
||||
| **CAN Ports** | 1 (isolated) | 1 | 1 (isolated) |
|
||||
| **Isolation** | ✅ Yes (CAN + RS485 Unit) | ✅ Yes (both) | ✅ Yes (both) |
|
||||
| **Termination** | External | External | ✅ 120Ω jumper-selectable |
|
||||
| **GPIOs** | ⚠️ Very limited | Moderate | Moderate |
|
||||
| **PSRAM** | Optional (AtomS3R: 8MB) | 8MB | 8MB |
|
||||
| **Best For** | Compact installations, display needed, RS485 BMS | Multiple RS485 ports | Industrial, built-in termination |
|
||||
| **Price** | Moderate (modular) | Moderate | Moderate |
|
||||
|
||||
**When to Choose AtomS3:**
|
||||
- ✅ Compact size is critical
|
||||
- ✅ Built-in display desired
|
||||
- ✅ Modular expansion preferred
|
||||
- ✅ BMS via RS485 (multiple units)
|
||||
- ❌ Need many GPIOs
|
||||
- ❌ Need multiple RS485 ports simultaneously
|
||||
|
||||
## FAQ
|
||||
|
||||
**Q: Which AtomS3 variant should I choose?**
|
||||
A: For YamBMS, we recommend **AtomS3R (C126)** with 8MB PSRAM if using Bluetooth BLE, as it provides extra RAM to prevent crashes. For RS485-only applications, AtomS3 or AtomS3 Lite is sufficient.
|
||||
|
||||
**Q: Can I use multiple RS485 and CAN simultaneously?**
|
||||
A: Yes, but with limitations. AtomS3 has very few GPIOs. You can use Atomic CAN Base (CAN) + RS485-ISO Unit (RS485) simultaneously, but additional expansion is limited.
|
||||
|
||||
**Q: How many BMS can I monitor via UART?**
|
||||
A: Maximum 3× BMS via UART. The 2nd and 3rd UARTs requires soldering connections on the Atomic CAN Base.
|
||||
|
||||
**Q: Does the Atomic CAN Base require external termination resistors?**
|
||||
A: The Atomic CAN Base does not have built-in switchable termination. You must add external 120Ω resistors at both ends of the CAN bus.
|
||||
|
||||
**Q: Why does my BLE connection crash after adding the 3rd BMS?**
|
||||
A: The BLE stack consumes significant RAM. Use AtomS3R (8MB PSRAM) and limit to 3 BMS maximum.
|
||||
|
||||
**Q: Can I power the AtomS3 from the CAN bus?**
|
||||
A: No, you should power the AtomS3 via USB Type-C (5V). The CAN bus voltage is not suitable for directly powering the device.
|
||||
|
||||
**Q: How do I control the screen backlight?**
|
||||
A: Use PWM on GPIO16 at 500Hz frequency. Brightness can be controlled manually, and auto-dim requires button activation to start the timer.
|
||||
|
||||
---
|
||||
|
||||
**License:** This documentation is part of the YamBMS project and follows the same GPLv3 license.
|
||||
|
||||
**Acknowledgments:** Based on official M5Stack documentation and community contributions.
|
||||
@@ -0,0 +1,377 @@
|
||||
# YamBMS - Waveshare ESP32-S3-RS485-CAN
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
> [!IMPORTANT]
|
||||
> This board uses a `flow_control_pin`, also called a `talk_pin` in the YamBMS documentation and used to manage the direction of data transmission for RS485 transceiver that do not handle this automatically. This `talk_pin` must be specified in your YAML.
|
||||
|
||||
## Overview
|
||||
|
||||
The Waveshare ESP32-S3-RS485-CAN is an industrial-grade WiFi wireless communicator based on the ESP32-S3 microcontroller. This board is designed for professional IoT applications with built-in isolation and protection circuits, making it particularly well-suited for the YamBMS project thanks to its robust RS485 and CAN bus interfaces.
|
||||
|
||||
**Key Features:**
|
||||
- Industrial-grade design with multiple protection circuits
|
||||
- Isolated RS485 and CAN interfaces
|
||||
- Built-in 120Ω termination resistors (jumper-selectable)
|
||||
- Digital isolation to prevent signal interference
|
||||
- Power supply isolation for stable operation
|
||||
- Wide voltage input range (7-36V DC)
|
||||
- DIN rail mountable protective enclosure
|
||||
|
||||
<img src="../..//images/MCU_ESP32-S3_WS-RS485-CAN_1.png" width="500"> <img src="../..//images/MCU_ESP32-S3_WS-RS485-CAN_2.png" width="500">
|
||||
|
||||
## Board Specifications
|
||||
|
||||
| Specification | Details |
|
||||
|-----|-----|
|
||||
| Microcontroller | ESP32-S3-WROOM-1 |
|
||||
| Processor | Xtensa 32-bit LX7 dual-core @ up to 240MHz |
|
||||
| FLASH | 16MB |
|
||||
| PSRAM | 8MB |
|
||||
| Wireless | Wi-Fi 802.11 b/g/n (2.4GHz) / Bluetooth 5.0 (LE) |
|
||||
| RS485 | 1× Isolated RS485 interface |
|
||||
| CAN Bus | 1× Isolated CAN interface |
|
||||
| UART | 1x SH1.0 interface (not isolated) |
|
||||
| Power Input (DC Terminal) | 7-36V DC (wide range) |
|
||||
| Power Input (USB) | 5V via USB Type-C |
|
||||
| Isolation | Power isolation + Optocoupler isolation |
|
||||
| Termination | 120Ω resistors (jumper-selectable for RS485 & CAN) |
|
||||
| LED Indicators | PWR, RS485 TX/RX, CAN |
|
||||
| Enclosure | Rail-mounted ABS protective case |
|
||||
| Programming | USB Type-C (firmware download & debugging) |
|
||||
|
||||
## Interfaces Support Capacity
|
||||
|
||||
Based on hardware limitations and testing, this board supports:
|
||||
|
||||
| Interface | Maximum | Notes |
|
||||
|-----------|---------|-------|
|
||||
| **CAN** | 1x bus | CAN bus to BMS or Inverter |
|
||||
| **RS485** | 1x bus | Best option for monitoring many BMS of the same brand |
|
||||
| **UART** | 3× devices¹ | Can be connected to the **SH1.0 interface** or **GPIOs header** (**shared with RS485**) |
|
||||
| **Bluetooth (BLE)** | 3× devices¹ | BLE stack consumes significant RAM, may cause crashes/reboots |
|
||||
|
||||
¹ BMS / Balancer / Shunt
|
||||
|
||||
**Note:** These are theoretical limits. Not all combinations have been tested.
|
||||
|
||||
## UART/IO Expander
|
||||
|
||||
It would be possible to add one or more [WK2168 4x UART expander](https://esphome.io/components/weikai.html) to increase the number of `UART` port.
|
||||
|
||||
## Power Supply
|
||||
|
||||
The Waveshare ESP32-S3-RS485-CAN can be powered using two methods:
|
||||
|
||||
### Option 1: USB Type-C Port
|
||||
- Connect a USB Type-C cable to the USB port
|
||||
- Provides **5V** power
|
||||
- Recommended for programming, debugging, and testing
|
||||
- Convenient for development and troubleshooting
|
||||
|
||||
### Option 2: External DC Power Supply (Screw Terminal)
|
||||
- Voltage range: **7V to 36V DC** (wide range)
|
||||
- Connect to the dedicated power screw terminal
|
||||
- Recommended for permanent installations and industrial environments
|
||||
- Provides stable power with built-in voltage regulator
|
||||
- **Built-in power supply isolation** provides stable isolated voltage
|
||||
- No extra power supply required for the isolated terminal
|
||||
|
||||
**Important:**
|
||||
- The board features integrated power isolation for enhanced safety and reliability
|
||||
- Suitable for harsh industrial environments with voltage fluctuations
|
||||
- Do not exceed the 36V maximum input voltage
|
||||
|
||||
## Port Identification and Pinout
|
||||
|
||||
### RS485 Port
|
||||
|
||||
The RS485 interface is **isolated** and clearly labeled on the board.
|
||||
|
||||
**RS485 GPIO Pins (Internal):**
|
||||
- **TX (GPIO17)**: RS485 transmit data
|
||||
- **RX (GPIO18)**: RS485 receive data
|
||||
- **EN (GPIO21)**: RS485 transceiver enable (automatic switching) `talk_in`
|
||||
|
||||
**RS485 Terminal Block Pinout:**
|
||||
The RS485 port typically has a **2-pin screw terminal block**:
|
||||
- **A (or +)**: RS485 A / Data+ (non-inverting)
|
||||
- **B (or -)**: RS485 B / Data- (inverting)
|
||||
|
||||
**RS485 Features:**
|
||||
- **Isolated interface** to avoid external signal interference
|
||||
- **Automatic transceiver mode switching** (no manual DE/RE control needed)
|
||||
- Supports RS485 Modbus and other industrial protocols
|
||||
- **LED indicators**:
|
||||
- Green LED: Lights up when RS485 transmits data
|
||||
- Blue LED: Lights up when RS485 receives data
|
||||
|
||||
### CAN Port
|
||||
|
||||
The CAN interface is **isolated** and clearly labeled on the board.
|
||||
|
||||
**CAN GPIO Pins (Internal):**
|
||||
- **TX (GPIO15)**: CAN transmit (TWAI TX)
|
||||
- **RX (GPIO16)**: CAN receive (TWAI RX)
|
||||
|
||||
**CAN Terminal Block Pinout:**
|
||||
The CAN port typically has a **2-pin screw terminal block**:
|
||||
- **H (or CANH)**: CAN High
|
||||
- **L (or CANL)**: CAN Low
|
||||
|
||||
**CAN Features:**
|
||||
- **Isolated CAN interface** for easy access to various CAN devices
|
||||
- Uses ESP32-S3 TWAI (Two-Wire Automotive Interface) controller
|
||||
- **LED indicator**: Blinks during CAN data transmission
|
||||
|
||||
## Wiring Instructions
|
||||
|
||||
### Connecting RS485 Devices
|
||||
|
||||
To connect an RS485 device to the RS485 port:
|
||||
|
||||
| RS485 | Terminal Block |
|
||||
|-------|----------------|
|
||||
| A + | RS485 A+ (Data+ non-inverting) |
|
||||
| B - | RS485 B- (Data- inverting) |
|
||||
|
||||
**Wiring Steps:**
|
||||
1. Identify the A and B wires from your RS485 device (may be labeled as D+/D-, A/B, or +/-)
|
||||
2. Connect the **A wire (D+ / Data+)** to the **A+ terminal**
|
||||
3. Connect the **B wire (D- / Data-)** to the **B- terminal**
|
||||
4. Connect the **ground wire** to the **GND terminal** for common reference
|
||||
|
||||
**RS485 Best Practices:**
|
||||
- **Always connect the ground (GND)** to provide a common reference between devices
|
||||
- The board features **automatic transceiver mode switching**, no manual control needed
|
||||
- RS485 polarity matters: if communication fails, try swapping A and B connections
|
||||
- Use twisted pair cable (recommended) to reduce noise and interference
|
||||
- The **isolation protects** the ESP32-S3 from high-voltage interference on the RS485 bus
|
||||
- Monitor communication using the **green (TX) and blue (RX) LED indicators**
|
||||
|
||||
### Connecting CAN Bus Devices
|
||||
|
||||
To connect a CAN device to the CAN port:
|
||||
|
||||
| CAN bus | Terminal Block |
|
||||
|---------|----------------|
|
||||
| CAN H | CAN H (CAN High) |
|
||||
| CAN L | CAN L (CAN Low) |
|
||||
|
||||
**Wiring Steps:**
|
||||
1. Identify the CAN H and CAN L wires from your CAN device
|
||||
2. Connect the **CAN H wire** to the **H (CANH) terminal**
|
||||
3. Connect the **CAN L wire** to the **L (CANL) terminal**
|
||||
4. Connect the **ground wire** to the **GND terminal** for common reference (optional)
|
||||
|
||||
**CAN Bus Best Practices:**
|
||||
- **Always connect the ground (GND)** for proper common mode voltage reference
|
||||
- The board uses the ESP32-S3 **TWAI (Two-Wire Automotive Interface)** controller
|
||||
- CAN bus requires proper termination (see Termination Resistors section below)
|
||||
- Use twisted pair cable specifically designed for CAN bus (120Ω impedance)
|
||||
- The **isolation protects** the ESP32-S3 from electrical noise on the CAN bus
|
||||
- Monitor CAN communication using the **CAN LED indicator** (blinks during transmission)
|
||||
- Typical CAN bus speeds: 125 kbps, 250 kbps, 500 kbps, or 1 Mbps
|
||||
|
||||
## Termination Resistors
|
||||
|
||||
One of the **key advantages** of the Waveshare ESP32-S3-RS485-CAN is its **built-in 120Ω termination resistors** that can be enabled or disabled via **jumpers**.
|
||||
|
||||
### RS485 Termination
|
||||
|
||||
The board includes an **onboard 120Ω RS485 termination resistor**.
|
||||
|
||||
**How to Enable RS485 Termination:**
|
||||
1. Locate the **RS485 termination jumper** on the board (typically labeled "RS485 120R" or similar)
|
||||
2. **Move the jumper cap to the "120R" position** to enable the termination resistor
|
||||
3. **Move the jumper cap to the "NC" (No Connection) position** to disable termination
|
||||
|
||||
**When to Enable RS485 Termination:**
|
||||
- Enable termination if the board is at **one of the two endpoints** of the RS485 bus
|
||||
- RS485 networks require **120Ω termination at both ends** of the bus
|
||||
- If the board is in the **middle** of the network, keep termination disabled (NC position)
|
||||
- For short cable runs (<10 meters), termination may be optional but is still recommended
|
||||
|
||||
**FAQ Note:** If RS485 communication is not working, the Waveshare wiki recommends: *"Please move the jumper cap to 120R and try again. Some RS485 devices require a 120R resistor to be connected in series."*
|
||||
|
||||
### CAN Bus Termination
|
||||
|
||||
The board includes an **onboard 120Ω CAN termination resistor**.
|
||||
|
||||
**How to Enable CAN Termination:**
|
||||
1. Locate the **CAN termination jumper** on the board (typically labeled "CAN 120R" or similar)
|
||||
2. **Move the jumper cap to the "120R" position** to enable the termination resistor
|
||||
3. **Move the jumper cap to the "NC" (No Connection) position** to disable termination
|
||||
|
||||
**When to Enable CAN Termination:**
|
||||
- Enable termination if the board is at **one of the two endpoints** of the CAN bus
|
||||
- CAN bus requires **exactly two 120Ω termination resistors** on the entire bus (one at each end)
|
||||
- If the board is in the **middle** of the network, keep termination disabled (NC position)
|
||||
- With proper termination, you should measure ~60Ω between CAN H and CAN L
|
||||
|
||||
**Termination Tips:**
|
||||
- Always check termination settings before troubleshooting communication issues
|
||||
- Many CAN devices (like inverters) have built-in termination - verify before adding more
|
||||
- Incorrect termination is a common cause of CAN communication failures
|
||||
|
||||
## LED Indicators
|
||||
|
||||
The board includes several LED indicators for monitoring system status:
|
||||
|
||||
| LED | Color | Function |
|
||||
|-----|-------|----------|
|
||||
| **PWR** | Red/Green | Power indicator - lights up when board is powered |
|
||||
| **RS485 TX** | Green | Lights up when RS485 port **sends** data |
|
||||
| **RS485 RX** | Blue | Lights up when RS485 port **receives** data |
|
||||
| **CAN** | Yellow/Green | Blinks during CAN bus **data transmission** |
|
||||
|
||||
These indicators are extremely useful for troubleshooting communication issues in real-time.
|
||||
|
||||
## Typical YamBMS Configuration
|
||||
|
||||
For a typical YamBMS setup with the Waveshare ESP32-S3-RS485-CAN:
|
||||
|
||||
1. **Power Supply:**
|
||||
- For bench testing: Connect USB Type-C cable (5V)
|
||||
- For permanent installation: Connect 12V or 24V DC to screw terminal (recommended)
|
||||
|
||||
2. **BMS Communication (RS485):**
|
||||
- Connect your BMS (e.g., JK, JBD, SEPLOS, PACE, BASEN) to the RS485 port
|
||||
- Wire according to: **A=RS485 A (Data+)**, **B=RS485 B (Data-)**, **GND=Ground**
|
||||
- **Enable RS485 termination (120R jumper)** if the board is at the end of the RS485 bus
|
||||
- If the BMS is the only RS485 device, enable termination
|
||||
|
||||
3. **Inverter Communication (CAN):**
|
||||
- Connect your inverter (e.g., Deye, Sofar, Growatt, Victron) to the CAN port
|
||||
- Wire according to: **H=CAN H**, **L=CAN L**, **GND=Ground**
|
||||
- **Enable CAN termination (120R jumper)** if the inverter is at the end of the CAN bus
|
||||
- For point-to-point (board ↔ inverter), typically both ends need termination
|
||||
- Check if your inverter has built-in termination before enabling
|
||||
|
||||
4. **Verification:**
|
||||
- Power on the board - the **PWR LED** should light up
|
||||
- Monitor RS485 communication using **green (TX) and blue (RX) LEDs**
|
||||
- Monitor CAN communication using the **CAN LED** (should blink during transmission)
|
||||
|
||||
5. **GPIO Pin Configuration:**
|
||||
- RS485: TX=GPIO17, RX=GPIO18, EN=GPIO21
|
||||
- CAN: TX=GPIO15, RX=GPIO16
|
||||
|
||||
## Protective Enclosure
|
||||
|
||||
The Waveshare ESP32-S3-RS485-CAN comes with a **rail-mounted ABS protective enclosure**:
|
||||
|
||||
**Enclosure Features:**
|
||||
- Industrial-grade ABS plastic case
|
||||
- **DIN rail mountable** for easy installation in electrical cabinets
|
||||
- Protects the board from dust, moisture, and physical damage
|
||||
- Provides professional appearance for industrial installations
|
||||
- Easy to install and safe to use
|
||||
|
||||
**Installation:**
|
||||
- The case clips onto standard 35mm DIN rails
|
||||
- Suitable for use in control panels, switchboards, and industrial enclosures
|
||||
|
||||
## Programming and Development
|
||||
|
||||
### Entering Download Mode
|
||||
|
||||
If you have trouble uploading firmware:
|
||||
|
||||
1. **Long press the BOOT button**
|
||||
2. While holding BOOT, **press the RESET button**
|
||||
3. **Release RESET**, then release BOOT
|
||||
4. The module will enter download mode
|
||||
5. Now you can upload your firmware
|
||||
|
||||
This solves most download/flashing issues.
|
||||
|
||||
### Web Interface Demo
|
||||
|
||||
Waveshare provides demo firmware with a web interface:
|
||||
- Default WiFi AP name: **ESP32-S3-RS485-CAN**
|
||||
- Default password: **waveshare**
|
||||
- The web interface allows control of RS485 and CAN ports
|
||||
- You can get the device IP via Bluetooth debugging assistant
|
||||
|
||||
## Additional Resources
|
||||
|
||||
### Official Waveshare Documentation
|
||||
- [Waveshare ESP32-S3-RS485-CAN Product Page](https://www.waveshare.com/esp32-s3-rs485-can.htm)
|
||||
- [Waveshare ESP32-S3-RS485-CAN Wiki](https://www.waveshare.com/wiki/ESP32-S3-RS485-CAN)
|
||||
- [Schematic Diagram](https://www.waveshare.com/wiki/ESP32-S3-RS485-CAN#Schematic) (available on wiki)
|
||||
|
||||
### Datasheets
|
||||
- [ESP32-S3 Datasheet](https://files.waveshare.com/upload/f/f7/Esp32-s3_datasheet_en_(1).pdf)
|
||||
- [ESP32-S3 Technical Reference Manual](https://files.waveshare.com/wiki/common/Esp32-s3_technical_reference_manual_en.pdf)
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### RS485 Communication Issues
|
||||
- **Check termination jumper** - move to "120R" position if board is at bus endpoint
|
||||
- Verify correct A/B wiring - try swapping if needed
|
||||
- Check that **ground (GND) is connected** between devices
|
||||
- Monitor **green (TX) and blue (RX) LEDs** to verify data transmission
|
||||
- Ensure baud rate matches between all RS485 devices
|
||||
- Test cable continuity and check for damaged twisted pair cable
|
||||
|
||||
### CAN Bus Communication Issues
|
||||
- **Check termination jumper** - move to "120R" position if board is at bus endpoint
|
||||
- Verify exactly **two 120Ω termination resistors** are present on entire CAN bus
|
||||
- Check correct CAN H and CAN L wiring
|
||||
- Verify **ground (GND) is connected** for common mode voltage reference
|
||||
- Measure resistance between CAN H and CAN L (should be ~60Ω with proper termination)
|
||||
- Monitor **CAN LED** - it should blink during transmission
|
||||
- Verify CAN bus speed matches all devices (typically 125k, 250k, 500k, or 1Mbps)
|
||||
|
||||
### Upload/Programming Issues
|
||||
- **Enter download mode** using BOOT + RESET button sequence (see Programming section)
|
||||
- Verify USB cable supports data transfer (not charge-only)
|
||||
- Check correct COM port is selected in IDE
|
||||
- Try different USB cable or USB port on computer
|
||||
- Ensure USB drivers are installed (CH343P chip)
|
||||
|
||||
### Power Issues
|
||||
- Verify power supply voltage is within **7-36V DC** range (or 5V via USB)
|
||||
- Check **PWR LED** lights up when powered
|
||||
- Verify polarity of DC power connection
|
||||
- Do not exceed 36V maximum input voltage
|
||||
- The board's power isolation should prevent most power-related issues
|
||||
|
||||
### Isolation Issues
|
||||
- The board has **built-in isolation** for both power and communication interfaces
|
||||
- If experiencing interference issues, verify:
|
||||
- Ground connections are properly made
|
||||
- Shielded cables are used in noisy environments
|
||||
- Isolation jumpers are correctly configured
|
||||
|
||||
## Comparison with Other Boards
|
||||
|
||||
### Waveshare ESP32-S3-RS485-CAN vs LilyGo T-Connect
|
||||
|
||||
| Feature | Waveshare | LilyGo T-Connect |
|
||||
|---------|-----------|------------------|
|
||||
| RS485 Ports | 1 (isolated) | Up to 3 (isolated) |
|
||||
| CAN Ports | 1 (isolated) | 1 (isolated) |
|
||||
| Built-in Termination | ✅ Yes (120Ω jumper-selectable) | ❌ No (external resistors required) |
|
||||
| Power Isolation | ✅ Yes | ❌ No |
|
||||
| Signal Isolation | ✅ Yes (RS485 & CAN) | ✅ Yes (RS485 & CAN up to 2500V) |
|
||||
| Enclosure | ✅ DIN rail ABS case included | ❌ No enclosure |
|
||||
| Power Input | 7-36V DC or USB-C | 7-12V DC or USB-C |
|
||||
| LED Indicators | PWR, RS485 TX/RX, CAN | PWR, APA102 support |
|
||||
| Price | Moderate | Moderate |
|
||||
| Best For | Single RS485 + CAN with isolation | Multiple RS485 + CAN with isolation |
|
||||
|
||||
**Summary:** The Waveshare board excels in **industrial-grade protection and built-in termination**, while the LilyGo offers **more RS485 ports and configuration flexibility**. Choose based on your specific needs:
|
||||
- **Waveshare**: Best for harsh environments, built-in termination, ease of installation
|
||||
- **LilyGo**: Best for multiple RS485 devices, flexible configuration, compact size
|
||||
|
||||
---
|
||||
|
||||
**License:** This documentation is part of the YamBMS project and follows the same GPLv3 license.
|
||||
|
||||
**Disclaimer:** Always verify specifications and wiring with the official Waveshare documentation before deployment. This guide is community-created and may not reflect the latest product revisions.
|
||||
@@ -1,13 +0,0 @@
|
||||
# YamBMS - CAN bus protocol
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
## CAN bus protocol table
|
||||
|
||||

|
||||
|
||||
Note: the following IDs are not implemented: 0x35B, 0x360, 0x378, 0x380 and 0x381.
|
||||
@@ -1,4 +1,4 @@
|
||||
# YamBMS - Changelog
|
||||
# YamBMS changelog
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||
@@ -6,6 +6,40 @@
|
||||

|
||||

|
||||
|
||||
* YamBMS 1.6.0 :
|
||||
* New dashboards `1.6.0`
|
||||
* Added `iBMS V3.3` board
|
||||
* Updated `JK-PB` readme with **V19** warning and SoC 100% reset solution 1 and 2
|
||||
* Added board option `UART flow control` allows you to activate a `talk_pin` for the UART of your choice (e.g. WS-RS485-CAN)
|
||||
* Added AtomS3 GPIOs for `Atomic RS485 base` (uart_esp_3)
|
||||
* Disabled the `reboot_timeout` after 15 minutes in case of WiFi unavailability
|
||||
* New `Hardware highlighted` documentation (LilyGo / Waveshare / M5Stack)
|
||||
* New readme for **LilyGo T-Connect, WS RS485-CAN and M5Stack AtomS3** boards
|
||||
* Improved documentation.
|
||||
* Fixed [issue 83](https://github.com/Sleeper85/esphome-yambms/issues/83) Add esphome-pace-bms
|
||||
* Fixed [issue 94](https://github.com/Sleeper85/esphome-yambms/issues/94) Multi-BMS Seplos V3 don't work
|
||||
* Fixed [issue 96](https://github.com/Sleeper85/esphome-yambms/issues/96) Improve the SoC returned at the end of discharge
|
||||
* Fixed [issue 100](https://github.com/Sleeper85/esphome-yambms/issues/100) Improve the BMS Seplos V1 V2 examples
|
||||
* Fixed [issue 102](https://github.com/Sleeper85/esphome-yambms/issues/102) Improve Remaining Capacity when using a shunt
|
||||
* Added [issue 106](https://github.com/Sleeper85/esphome-yambms/issues/106) [FEATURE REQUEST] Temperature-based current limiting
|
||||
* Fixed [issue 108](https://github.com/Sleeper85/esphome-yambms/issues/108) [WARNING] esphome::select::Select::state` is deprecated
|
||||
* Fixed [issue 122](https://github.com/Sleeper85/esphome-yambms/issues/122) Adjust `bms_name` in all example YAML to something unique
|
||||
* Fixed [issue 128](https://github.com/Sleeper85/esphome-yambms/issues/128) Align the names of the shunt entities
|
||||
* Fixed [issue 142](https://github.com/Sleeper85/esphome-yambms/issues/142) Maximum capacity needs to be increased for `JK_RS485` BMS
|
||||
* Merged [PR 76](https://github.com/Sleeper85/esphome-yambms/pull/76) Add `Auto EOC` function
|
||||
* Merged [PR 82](https://github.com/Sleeper85/esphome-yambms/pull/82) Add support for external balancer
|
||||
* Merged [PR 85](https://github.com/Sleeper85/esphome-yambms/pull/85) Adding `EG4 LLV2` BMS
|
||||
* Merged [PR 97](https://github.com/Sleeper85/esphome-yambms/pull/97) Add `Basen controller` version with talk/flow control pin
|
||||
* Merged [PR 99](https://github.com/Sleeper85/esphome-yambms/pull/99) Basen: Use new binary sensors for charging/discharging
|
||||
* Merged [PR 112](https://github.com/Sleeper85/esphome-yambms/pull/112) Adding `FLIP_C3` board
|
||||
* Merged [PR 117](https://github.com/Sleeper85/esphome-yambms/pull/117) Round requested charge/discharge current to nearest integer
|
||||
* Change [PR 119](https://github.com/Sleeper85/esphome-yambms/pull/119) Updated `Power` gauge (-10kW to 10kW)
|
||||
* Merged [PR 133](https://github.com/Sleeper85/esphome-yambms/pull/133) Add `Studer XTM-4000` to supported inverters
|
||||
* Merged [PR 142](https://github.com/Sleeper85/esphome-yambms/pull/142) Sub device support
|
||||
* Merged [PR 143](https://github.com/Sleeper85/esphome-yambms/pull/143) Improved `Cut-Off charging` logic equation and documentation
|
||||
* Merged [PR 147](https://github.com/Sleeper85/esphome-yambms/pull/147) Improved `CCL`, `DCL` and `Temp-based` current control
|
||||
* Merged [PR 155](https://github.com/Sleeper85/esphome-yambms/pull/155) Update temperature sensor filters to reduce noise
|
||||
|
||||
* YamBMS 1.5.8 :
|
||||
* New Dashboards `1.5.8` compatible with `CANBUS` and `RS485` inverter communication protocol
|
||||
* Added BMS `SEPLOS V3` (beta)
|
||||
@@ -23,6 +57,7 @@
|
||||
* Merged [PR 77](https://github.com/Sleeper85/esphome-yambms/pull/77) `PYLON RS485` prevent stale data on BMS disconnect
|
||||
* Merged [PR 80](https://github.com/Sleeper85/esphome-yambms/pull/80) BMS Modbus client: Return 0 when not online
|
||||
* Merged [PR 81](https://github.com/Sleeper85/esphome-yambms/pull/81) Fix balance trigger voltage for Basen and Deye
|
||||
|
||||
* YamBMS 1.5.7 :
|
||||
* Adapted the default `min/max` values for the `Float` slider
|
||||
* Merged [PR 53](https://github.com/Sleeper85/esphome-yambms/pull/53) Add feature `Auto Float Voltage`
|
||||
@@ -33,6 +68,7 @@
|
||||
* Merged [PR 70](https://github.com/Sleeper85/esphome-yambms/pull/70) Dashboards compatible with `HA 2025.7`
|
||||
* Merged [PR 70](https://github.com/Sleeper85/esphome-yambms/pull/71) Dashboard `max/min` cell voltage in color using macro
|
||||
* Removed all special characters in entities name + dashboards correction
|
||||
|
||||
* YamBMS 1.5.6 :
|
||||
* Fixed [issue 58](https://github.com/Sleeper85/esphome-yambms/issues/58) Compilation problem with `esphome 2025.5.0`
|
||||
* Fixed [issue 55](https://github.com/Sleeper85/esphome-yambms/issues/55) New CPU frequency option
|
||||
@@ -46,6 +82,7 @@
|
||||
* New `board_ESP32-S3_Touch-LCD-7.yaml` board
|
||||
* New `board_ESP32-S3_YBoard_DJK.yaml` board
|
||||
* New `board_RP2040_RPi_Pico.yaml` board
|
||||
|
||||
* YamBMS 1.5.5 :
|
||||
* New `main.yaml` with LP (local packages) and RP (remote packages) versions
|
||||
* New `board.yaml` with modular UART/CAN interfaces
|
||||
@@ -53,11 +90,13 @@
|
||||
* SoC calculation is now based on remaining capacity for more accuracy (BMS only) [issues #39](https://github.com/Sleeper85/esphome-yambms/issues/39)
|
||||
* SoH calculation is moved to BMS level (for those who do not provide this information)
|
||||
* Improvement of the Victron SmartShunt doc [issues #38](https://github.com/Sleeper85/esphome-yambms/issues/38)
|
||||
|
||||
* YamBMS 1.5.4 :
|
||||
* New low SoC corrected at each BMS level (the corrected SoC is the one transmitted to YamBMS)
|
||||
* New BMS dashboard
|
||||
* New end of charge logic at each BMS level, the charge switch turns off when the cells are equalized (disabled by default)
|
||||
* Fixed `errors_bitamsk` for JK-PB RS485, test OK with YamBMS (forked component)
|
||||
|
||||
* YamBMS 1.5.3 :
|
||||
* Broadcasting JK-PB settings to all BMS set to OFF by default
|
||||
* Reorganizing the `board` folder and YAMLs (device_base.yaml moved to board.yaml)
|
||||
@@ -72,6 +111,7 @@
|
||||
* Added [PR #7547](https://github.com/esphome/esphome/pull/7547) regarding publishing entities via the API
|
||||
* Removed `captive_portal` because it increases the `loop time` too much
|
||||
* `PSRAM` will no longer be enabled by default as this has a bad impact on `BLE BMS`
|
||||
|
||||
* YamBMS 1.5.2 :
|
||||
* Added shunt `Online Status` binary_sensor
|
||||
* Shunt combine condition based on the new binary_sensor `Online Status`
|
||||
@@ -81,6 +121,7 @@
|
||||
* Simplification (fewer options) when importing `BMS / Shunt` YAMLs
|
||||
* New `multi-node` solution using `RS485 modbus` to communicate information to YamBMS
|
||||
* New board `espBerry` with `2-CH-CAN HAT`
|
||||
|
||||
* YamBMS 1.5.1 :
|
||||
* The conditions for `combining` BMS and the `charging` and `discharging` instructions no longer have any relation with the `errors_bitmask` sensor, the new system relies on the three **binary_sensor** `online status`, `charging allowed` and `discharging allowed` being linked to the status of alarms and switches.
|
||||
* The BMS combination procedure has been completely rewritten.
|
||||
@@ -96,17 +137,31 @@
|
||||
* The `UVPR` and `OVPR` sensors are no longer used and replaced by `UVP` and `OVP` to ensure operation with all BMS.
|
||||
* **@txubelaxu** fixed a bug in the `JK-PB RS485` component that could cause a false battery voltage value to be sent, [see this issue](https://github.com/Sleeper85/esphome-yambms/issues/10).
|
||||
* Improved documentation, added a `HowTo` to create its main YAML, warning about galvanic isolation.
|
||||
|
||||
* CANBUS 2.3.7 : If there is no response from the inverter, the time before a new communication test has been reduced from `120s` to `60s`, added Victron `0x372` nbr. of modules `blocking charge/discharge`.
|
||||
|
||||
* YamBMS 1.4.5 : Changed the way to configure WiFi/Ethernet network, added `ESP32-C3 ETH01-EVO` ethernet board, reduction of the number of YAML bms files, UART `rx_buffer_size` is set to `512` by default for JK-B and JK-PB, new JK-BMS BLE sensors (last commits of @syssi) and new BLE `standard` version
|
||||
|
||||
* CANBUS 2.3.6 : Sending CAN frames stops immediately if there are no combined BMS
|
||||
|
||||
* YamBMS 1.4.4 : Multi-shunt support, Simplified and new YamBMS option `battery chemistry`, slider `min/max` values are automatically configured based on the battery chemistry and cell count, added `YamBMS Fallback Hotspot`, added YamBMS `Update service`, added PVbrain2 and Atom Matrix board, added PSRAM settings YAML (not enabled by default), new MIN/MAX temperature sensor, added DC current icon, fixed dual sensor `Cell UVPR (MAX)` bug, Improved `combine` code, Breaking change : Atom S3 `GPIOs 1 and 2` reversed
|
||||
|
||||
* CANBUS 2.3.5 : New MIN/MAX temperature / sensor ID, Improved Victron protocol (online/offline battery modules, installed/available battery capacity)
|
||||
|
||||
* CANBUS 2.3.4 : Fixed bug of canbus link validation without inverter connected
|
||||
|
||||
* YamBMS 1.4.3 : Added Victron and Junctek KH-F `Shunt` support and `Requested Force Charge` function based on `SoC start/stop`, new `Total Daily Energy` sensors
|
||||
|
||||
* CANBUS 2.3.3 : Added `Automatic` BMS name selection and `Requested Force Charge` Bit 3/4/5 (PYLON 0x35C)
|
||||
|
||||
* CANBUS 2.3.2 : Added `LuxPower` protocol with updated `can_id` 0x355, 0x356, 0x359 and 0x35C
|
||||
|
||||
* CANBUS 2.3.1 : Improved the procedure for sending canbus frames with reduced loop time, rewritten of the canbus link validation code and added `Inverter Heartbeat Monitoring` function
|
||||
|
||||
* YamBMS 1.4.2 : Added new `Auto CVL Boost V.` and `Rebulk SoC` functions, new debug.yaml for ESP32 and ESP32-S3, improved code and comments
|
||||
|
||||
* YamBMS 1.4.1 : Rewriting of the alarm system, bug fixes and improvement of the charging logic (new status `Cut-Off`), icon allocation for each sensor, UART and CANBUS `!extend ${vars}`, New sensor `YamBMS Delta Cell V.`, Improved `Battery SOC` logic
|
||||
|
||||
* YamBMS 1.3.2 : New var `yambms_cell_count`, the BMS charge or discharge switches can be activated separately without causing the decombination of the BMS, new `minimal` version of the BMS YAML in order to reduce the loop time
|
||||
|
||||
* YamBMS 1.3.1 : First multi-BMS version named `YamBMS`
|
||||
@@ -1,4 +1,4 @@
|
||||
# YamBMS - Charging Logic
|
||||
# YamBMS charging logic
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||
@@ -19,11 +19,11 @@ The charging voltage and current correspond to the default values in the YAML sc
|
||||
|
||||
Source: [Charging Marine Lithium Battery Banks](https://nordkyndesign.com/charging-marine-lithium-battery-banks)
|
||||
|
||||
Special thanks to [@shvmm](https://github.com/shvmm) for creating the equations.
|
||||
Special thanks to [@shvmm](https://github.com/shvmm) for deriving the equations.
|
||||
|
||||
Note: The equations below are valid for other chemistries like Li-ion and LTO but with other CVmin and CVmax values.
|
||||
Note: The equations below can be adopted for other chemistries like Li-ion and LTO with specific CVmin and CVmax values.
|
||||
|
||||

|
||||
<img src="../..//images/YamBMS_Cut-Off_Charging_Logic_Equation.png" width="500"> <img src="../..//images/YamBMS_Cut-Off_Charging_Logic_Plot.png" width="500">
|
||||
|
||||
## Cut-Off Charging Logic Diagram (what's happening in the yellow diamond)
|
||||
|
||||
@@ -37,6 +37,8 @@ Note: The diagram below is valid for other chemistries like Li-ion and LTO but w
|
||||
- CV min : 3.37 V
|
||||
- CV max : 3.65 V
|
||||
|
||||
To enter the **Cut-Off phase** the only condition is that **cutoff_voltage > cv_min**.
|
||||
|
||||

|
||||
|
||||
## Li-ion Cut-Off Values
|
||||
@@ -45,6 +47,8 @@ Note: The diagram below is valid for other chemistries like Li-ion and LTO but w
|
||||
- CV min : 3.90 V
|
||||
- CV max : 4.20 V
|
||||
|
||||
To enter the **Cut-Off phase** the only condition is that **cutoff_voltage > cv_min**.
|
||||
|
||||

|
||||
|
||||
## LTO Cut-Off Values
|
||||
@@ -53,4 +57,6 @@ Note: The diagram below is valid for other chemistries like Li-ion and LTO but w
|
||||
- CV min : 2.55 V
|
||||
- CV max : 2.85 V
|
||||
|
||||
To enter the **Cut-Off phase** the only condition is that **cutoff_voltage > cv_min**.
|
||||
|
||||

|
||||
@@ -15,7 +15,7 @@
|
||||
┌─────────────┐ ┌──────────┐ ┌───────────┐
|
||||
│ | 3V3/5V--V1>│ |<V2---3V3---<| |
|
||||
│ DEVICE │<RX-------AO<│ UART-TTL │<AI-------TX<| ESP32 |
|
||||
│ BMS / Shunt │>TX-------AI>│ ISOLATOR │>BO-------RX>| |
|
||||
│ BMS / Shunt │>TX-------BI>│ ISOLATOR │>BO-------RX>| |
|
||||
│ │<----GND---->│ │<----GND---->| |
|
||||
└─────────────┘ └──────────┘ └───────────┘
|
||||
```
|
||||
|
||||
@@ -6,14 +6,25 @@
|
||||

|
||||

|
||||
|
||||
## MCU default GPIOs
|
||||
## Default GPIOs
|
||||
|
||||

|
||||

|
||||
|
||||
## Contents
|
||||
## BMS
|
||||
|
||||
1) [Galvanic isolation](Galvanic_isolation.md)
|
||||
2) [JK-B BMS](BMS_JK-B.md)
|
||||
3) [JK-PB BMS](BMS_JK-PB.md)
|
||||
4) [JK RS485 DISPLAY](BMS_JK_RS485_DISPLAY.md)
|
||||
5) [Victron SmartShunt](Shunt_Victron_SmartShunt.md)
|
||||
* [JK-B BMS](BMS_JK-B.md)
|
||||
* [JK-PB BMS](BMS_JK-PB.md)
|
||||
* [JK RS485 DISPLAY](BMS_JK_RS485_DISPLAY.md)
|
||||
|
||||
## Shunts
|
||||
|
||||
* [Victron SmartShunt](Shunt_Victron_SmartShunt.md)
|
||||
|
||||
## Communication interfaces
|
||||
|
||||
* [RS485 bus](Interface_RS485_bus.md)
|
||||
* [CAN bus](Interface_CAN_bus.md)
|
||||
|
||||
## Others
|
||||
|
||||
* [Galvanic isolation](Galvanic_isolation.md)
|
||||
@@ -29,10 +29,21 @@
|
||||
|
||||
### 1. Enter your WiFi credentials in the `SECRETS` YAML in the top right corner
|
||||
|
||||
Copy, past and enter your credentials :
|
||||
|
||||
```YAML
|
||||
# WiFi
|
||||
wifi_ssid: YourSSID
|
||||
wifi_password: YourPassword
|
||||
domain : .local
|
||||
domain: .local
|
||||
|
||||
# WiFi AP
|
||||
wifi_ap_ssid: YamBMS
|
||||
wifi_ap_password: Y4mBM$85
|
||||
|
||||
# Web Server
|
||||
web_server_username: yambms
|
||||
web_server_password: Y4mBM$85
|
||||
```
|
||||
|
||||
### 2. Add your `ESP32` by clicking on `+ NEW DEVICE` at the bottom right
|
||||
@@ -56,7 +67,7 @@ In Home Assistant under **" Settings > Devices and services > Add Intergration "
|
||||
|
||||
### 1. Install ESPHome on your computer
|
||||
|
||||
Before you can flash your ESP32 you need to install the [ESPHome 2025.6.0 or higher](https://github.com/esphome/esphome/releases) command line application.<br>
|
||||
Before you can flash your ESP32 you need to install the [ESPHome 2025.11.0 or higher](https://github.com/esphome/esphome/releases) command line application.<br>
|
||||
[Follow these instructions for installation on Windows, Mac or Linux.](https://esphome.io/guides/installing_esphome)
|
||||
|
||||
> [!TIP]
|
||||
@@ -89,10 +100,19 @@ cd esphome-yambms
|
||||
|
||||
### 3. Enter your WiFi credentials in the `secrets.yaml` files
|
||||
|
||||
```yaml
|
||||
```YAML
|
||||
# WiFi
|
||||
wifi_ssid: YourSSID
|
||||
wifi_password: YourPassword
|
||||
domain : .local
|
||||
domain: .local
|
||||
|
||||
# WiFi AP
|
||||
wifi_ap_ssid: YamBMS
|
||||
wifi_ap_password: Y4mBM$85
|
||||
|
||||
# Web Server
|
||||
web_server_username: yambms
|
||||
web_server_password: Y4mBM$85
|
||||
```
|
||||
|
||||
### 4. Install the `YamBMS.yaml` into your ESP32
|
||||
|
||||
@@ -0,0 +1,608 @@
|
||||
# YamBMS - CAN bus
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
## Overview
|
||||
|
||||
**CAN (Controller Area Network)** is a robust vehicle bus standard designed for reliable communication in harsh environments. Originally developed for automotive applications, CAN bus is now widely used in industrial automation, energy management systems, and battery management applications.
|
||||
|
||||
In the YamBMS ecosystem, CAN bus is primarily used to communicate between the ESP32 controller and the solar inverter, transmitting battery status information to enable proper charge/discharge control.
|
||||
|
||||

|
||||
|
||||
**Key Features:**
|
||||
- Multi-master communication protocol
|
||||
- High immunity to electrical interference
|
||||
- Built-in error detection and fault confinement
|
||||
- Data rates up to 1 Mbps
|
||||
- Supports up to 110 nodes (depending on transceiver)
|
||||
- Differential signaling for noise immunity
|
||||
|
||||
## CAN bus protocol table
|
||||
|
||||

|
||||
|
||||
Note: the following IDs are not implemented: 0x35B, 0x360, 0x378, 0x380 and 0x381.
|
||||
|
||||
## CAN Bus Fundamentals
|
||||
|
||||
### What is CAN Bus?
|
||||
|
||||
CAN bus uses a **two-wire differential signaling system**:
|
||||
- **CAN H (CAN High)**: Dominant state high, recessive state ~2.5V
|
||||
- **CAN L (CAN Low)**: Dominant state low, recessive state ~2.5V
|
||||
|
||||
**Differential Signaling:**
|
||||
```
|
||||
Differential Signal = CAN H - CAN L
|
||||
|
||||
Dominant bit (0): CAN H = ~3.5V, CAN L = ~1.5V → Difference = +2V
|
||||
Recessive bit (1): CAN H = ~2.5V, CAN L = ~2.5V → Difference = 0V
|
||||
```
|
||||
|
||||
This differential approach provides excellent **common-mode noise rejection**, allowing reliable communication even in electrically noisy environments like solar installations with high-voltage batteries and inverters.
|
||||
|
||||
### CAN Bus Speed & Distance
|
||||
|
||||
The maximum cable length depends on the communication speed:
|
||||
|
||||
| Baud Rate | Maximum Distance | Typical Use Case |
|
||||
|-----------|------------------|------------------|
|
||||
| 1 Mbps | 40 meters | Short, high-speed networks |
|
||||
| 500 kbps | 100 meters | **Typical for solar inverters** |
|
||||
| 250 kbps | 250 meters | Medium-distance industrial |
|
||||
| 125 kbps | 500 meters | Long-distance, lower speed |
|
||||
| 50 kbps | 1000 meters | Very long distance |
|
||||
|
||||
**YamBMS Typical Configuration:** Most solar inverters use **500 kbps** for CAN bus communication.
|
||||
|
||||
### CAN Bus Topology
|
||||
|
||||
**Linear Bus (Daisy Chain) - CORRECT:**
|
||||
```
|
||||
[Device 1]───[Device 2]───[Device 3]───[Device 4]
|
||||
↑ ↑
|
||||
120Ω termination 120Ω termination
|
||||
```
|
||||
|
||||
**Important Rules:**
|
||||
- ✅ **Linear topology** (daisy chain)
|
||||
- ✅ **Two termination resistors** (120Ω each at both ends)
|
||||
- ❌ **NOT star topology** (causes signal reflections)
|
||||
- ❌ **NOT ring topology** (not supported)
|
||||
- ❌ **NOT multiple branch points** (stub length < 30cm if unavoidable)
|
||||
|
||||
## CAN Bus Wiring
|
||||
|
||||
### Standard 3-Wire Configuration
|
||||
|
||||
**Recommended wiring for CAN bus:**
|
||||
|
||||
```
|
||||
CAN Bus 3-Wire Configuration
|
||||
=============================
|
||||
Device 1 Device 2 Device 3
|
||||
├─ CAN H ────────────── CAN H ────────────── CAN H
|
||||
├─ CAN L ────────────── CAN L ────────────── CAN L
|
||||
└─ GND ──────────────── GND ──────────────── GND
|
||||
```
|
||||
|
||||
### Pin Identification
|
||||
|
||||
**Common CAN Terminal Labeling:**
|
||||
- **CAN H** / **CANH** / **H** / **+** = CAN High
|
||||
- **CAN L** / **CANL** / **L** / **-** = CAN Low
|
||||
- **GND** / **GND** / **G** / **Signal Ground** = Ground reference
|
||||
|
||||
**Important:** Always verify with your device documentation, as some manufacturers may use different labeling conventions.
|
||||
|
||||
### Cable Requirements
|
||||
|
||||
**Recommended Cable Specifications:**
|
||||
- **Type:** Twisted pair cable designed for CAN bus
|
||||
- **Characteristic Impedance:** 120Ω (this matches the termination resistors)
|
||||
- **Gauge:** 24 AWG to 20 AWG (depending on distance and current)
|
||||
- **Shielding:** Shielded cable recommended for electrically noisy environments
|
||||
- **Quality:** Use cables certified for CAN bus applications
|
||||
|
||||
### Ground Connection - CRITICAL INFORMATION
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **Should you connect the GND wire on CAN bus?**
|
||||
|
||||
**Answer: YES - STRONGLY RECOMMENDED**
|
||||
|
||||
#### Why Ground Connection is Important
|
||||
|
||||
While CAN uses differential signaling and can theoretically work without a ground connection, **in practice you should ALWAYS connect the ground wire**. Here's why:
|
||||
|
||||
**1. Common Mode Voltage Range**
|
||||
- CAN transceivers tolerate **-7V to +12V** common mode voltage
|
||||
- Over long distances or with separate power supplies, ground potential differences can **exceed this range**
|
||||
- Without GND connection: risk of **transceiver damage** and communication failure
|
||||
|
||||
**2. Distance Considerations**
|
||||
- Even over a few meters, ground potential differences can develop
|
||||
- Over hundreds of meters, differences of several volts are common
|
||||
- GND wire equalizes these potential differences
|
||||
|
||||
**3. Multiple Power Sources**
|
||||
- ESP32 and inverter have separate power supplies
|
||||
- Different power supplies = different ground potentials
|
||||
- GND connection provides common reference
|
||||
|
||||
**4. Electrical Noise Protection**
|
||||
- High-voltage batteries and inverters generate electrical noise
|
||||
- Switching power supplies create transients
|
||||
- GND helps stabilize the common mode voltage
|
||||
|
||||
**5. Shielded Cable Grounding**
|
||||
- If using shielded cable (recommended), the shield should be grounded
|
||||
- Improves electromagnetic interference (EMI) immunity
|
||||
- Shield should be grounded at **one end only** to avoid ground loops
|
||||
|
||||
#### When GND Can Be Omitted (NOT RECOMMENDED)
|
||||
|
||||
**Very limited cases where GND might work without connection:**
|
||||
- Distance **< 2 meters**
|
||||
- **Common power supply** (same PSU for all devices)
|
||||
- Clean electrical environment (bench testing only)
|
||||
|
||||
**However:** Even in these cases, it's **better to connect GND** to ensure reliability!
|
||||
|
||||
#### Isolated CAN Transceivers
|
||||
|
||||
**Question:** If my board has isolated CAN (e.g., Waveshare, M5Stack), do I still need to connect GND?
|
||||
|
||||
**Answer:** **YES - Still recommended!**
|
||||
|
||||
```
|
||||
Board with CAN Isolation
|
||||
=========================
|
||||
|
||||
ESP32 Side Isolation CAN Bus Side
|
||||
(non-isolated) ═══════════ (isolated)
|
||||
|
||||
├─ CAN H ──→ to Inverter
|
||||
├─ CAN L ──→ to Inverter
|
||||
└─ GND ──→ to Inverter (RECOMMENDED!)
|
||||
|
||||
Isolation protects the ESP32, but devices on the isolated side
|
||||
of the CAN bus still need a common ground reference!
|
||||
```
|
||||
|
||||
**Explanation:**
|
||||
- **Isolation** protects your ESP32 from voltage spikes and noise on the CAN bus
|
||||
- Devices on the **isolated side** (inverter, etc.) still benefit from a common GND reference
|
||||
- Without GND: communication may be unstable despite isolation
|
||||
|
||||
### Wiring Best Practices
|
||||
|
||||
**DO:**
|
||||
- ✅ Use twisted pair cable (CAN H and CAN L twisted together)
|
||||
- ✅ Keep cable runs as short as practical
|
||||
- ✅ Use proper CAN bus cable (120Ω impedance)
|
||||
- ✅ Connect GND wire between all devices
|
||||
- ✅ Add termination resistors at both ends
|
||||
- ✅ Avoid running CAN cables parallel to power cables
|
||||
- ✅ Use shielded cable in noisy environments
|
||||
|
||||
**DON'T:**
|
||||
- ❌ Use random cable (cat5, speaker wire, etc.)
|
||||
- ❌ Create star or ring topologies
|
||||
- ❌ Exceed maximum cable length for your baud rate
|
||||
- ❌ Add more than two 120Ω termination resistors
|
||||
- ❌ Omit GND connection
|
||||
- ❌ Create long stubs (branches) from the main bus
|
||||
|
||||
## Termination Resistors
|
||||
|
||||
### Why Termination is Necessary
|
||||
|
||||
**Signal Reflections:**
|
||||
- When an electrical signal travels down a cable and reaches the end, it reflects back
|
||||
- These reflections cause signal distortion and communication errors
|
||||
- **Termination resistors** absorb the signal energy, preventing reflections
|
||||
|
||||
**The 120Ω Standard:**
|
||||
- CAN bus cable has a characteristic impedance of 120Ω
|
||||
- Termination resistors match this impedance
|
||||
- Result: clean signal transmission without reflections
|
||||
|
||||
### Proper Termination Configuration
|
||||
|
||||
**Correct: Exactly TWO 120Ω resistors at both ends**
|
||||
|
||||
```
|
||||
CORRECT Termination
|
||||
===================
|
||||
120Ω 120Ω
|
||||
║ ║
|
||||
[Device 1]───[Device 2]───[Device 3]───[Device 4]
|
||||
└─── Start of bus End of bus ───┘
|
||||
```
|
||||
|
||||
**How to verify termination:**
|
||||
1. Disconnect all devices from the CAN bus
|
||||
2. Measure resistance between CAN H and CAN L with a multimeter
|
||||
3. **Expected result: ~60Ω** (two 120Ω resistors in parallel = 60Ω)
|
||||
|
||||
```
|
||||
Termination Math:
|
||||
=================
|
||||
Two 120Ω resistors in parallel:
|
||||
R_total = (R1 × R2) / (R1 + R2)
|
||||
R_total = (120 × 120) / (120 + 120)
|
||||
R_total = 14400 / 240 = 60Ω
|
||||
```
|
||||
|
||||
### Common Termination Mistakes
|
||||
|
||||
**❌ WRONG: No termination**
|
||||
```
|
||||
[Device 1]───[Device 2]───[Device 3]
|
||||
```
|
||||
**Result:** Signal reflections, communication errors, unreliable operation
|
||||
|
||||
**❌ WRONG: Only one termination resistor**
|
||||
```
|
||||
120Ω
|
||||
║
|
||||
[Device 1]───[Device 2]───[Device 3]
|
||||
```
|
||||
**Result:** Partial reflections, reduced noise immunity
|
||||
|
||||
**❌ WRONG: Termination in the middle**
|
||||
```
|
||||
120Ω
|
||||
║
|
||||
[Device 1]───[Device 2]───[Device 3]
|
||||
```
|
||||
**Result:** Both ends are unterminated, causing reflections from both directions
|
||||
|
||||
**❌ WRONG: More than two termination resistors**
|
||||
```
|
||||
120Ω 120Ω 120Ω
|
||||
║ ║ ║
|
||||
[Device 1]───[Device 2]───[Device 3]
|
||||
```
|
||||
**Result:** Total impedance too low (~40Ω), excessive current draw, poor signal quality
|
||||
|
||||
### Built-in vs External Termination
|
||||
|
||||
**Boards with Built-in Termination (Jumper-Selectable):**
|
||||
|
||||
Some boards have onboard 120Ω resistors that can be enabled via jumpers:
|
||||
- **Waveshare ESP32-S3-RS485-CAN**: Jumper for CAN termination (120R/NC)
|
||||
- Many industrial CAN interfaces
|
||||
- Some inverters have built-in switchable termination
|
||||
|
||||
**Boards without Built-in Termination:**
|
||||
|
||||
Some boards require external termination resistors:
|
||||
- **LilyGo T-Connect**: No built-in CAN termination
|
||||
- **M5Stack Atomic CAN Base**: No built-in switchable termination
|
||||
- External 120Ω resistor must be connected between CAN H and CAN L
|
||||
|
||||
**How to add external termination:**
|
||||
```
|
||||
Physical Connection:
|
||||
====================
|
||||
120Ω Resistor
|
||||
┌─────┐
|
||||
CAN H ─────┤ ├───── CAN L
|
||||
└─────┘
|
||||
```
|
||||
|
||||
**Where to buy termination resistors:**
|
||||
- 1/4W or 1/2W 120Ω resistors from any electronics supplier
|
||||
- Pre-made CAN termination plugs (with VH or screw terminals)
|
||||
- DeviceNet/CANopen termination resistors
|
||||
|
||||
### Determining Termination Configuration
|
||||
|
||||
**For a typical YamBMS setup (ESP32 ↔ Inverter):**
|
||||
|
||||
```
|
||||
Point-to-point CAN connection:
|
||||
===============================
|
||||
|
||||
120Ω (if available) 120Ω (check inverter)
|
||||
║ ║
|
||||
[ESP32 Board]───────────────────────[Solar Inverter]
|
||||
└─ Start End ─┘
|
||||
```
|
||||
|
||||
**Steps:**
|
||||
1. **Check your ESP32 board:**
|
||||
- Does it have built-in termination? (check docs/jumpers)
|
||||
- If yes: enable it (move jumper to 120R position)
|
||||
- If no: add external 120Ω resistor between CAN H and CAN L
|
||||
|
||||
2. **Check your inverter:**
|
||||
- Most inverters have built-in termination (check manual)
|
||||
- Some have a termination switch or jumper
|
||||
- If no built-in termination: add external 120Ω resistor
|
||||
|
||||
3. **Verify with multimeter:**
|
||||
- Power off all devices
|
||||
- Measure between CAN H and CAN L
|
||||
- Should read ~60Ω
|
||||
|
||||
## Common CAN Bus Issues & Troubleshooting
|
||||
|
||||
### No Communication on CAN Bus
|
||||
|
||||
**Symptoms:**
|
||||
- No data received from inverter
|
||||
- ESP32 cannot send data
|
||||
- CAN bus appears "dead"
|
||||
|
||||
**Troubleshooting Steps:**
|
||||
|
||||
1. **Check Wiring**
|
||||
- ✓ CAN H to CAN H, CAN L to CAN L (not swapped)
|
||||
- ✓ GND connected between devices
|
||||
- ✓ No loose connections
|
||||
- ✓ Cable integrity (no breaks)
|
||||
|
||||
2. **Verify Termination**
|
||||
- Power off all devices
|
||||
- Measure resistance between CAN H and CAN L
|
||||
- Should be ~60Ω (two 120Ω resistors in parallel)
|
||||
- If not 60Ω: check termination resistor configuration
|
||||
|
||||
3. **Check Baud Rate**
|
||||
- ESP32 and inverter must use same baud rate
|
||||
- Common rates: 500 kbps (most common), 250 kbps, 125 kbps
|
||||
- Check inverter manual for supported baud rate
|
||||
- Verify ESP32 code configuration
|
||||
|
||||
4. **Verify Power**
|
||||
- Both devices powered on
|
||||
- Correct voltage levels (5V for ESP32, as per inverter specs)
|
||||
- Check power supply stability
|
||||
|
||||
5. **Check Cable Length**
|
||||
- Is cable length within limits for your baud rate?
|
||||
- 500 kbps → max 100 meters
|
||||
- 1 Mbps → max 40 meters
|
||||
|
||||
### Intermittent Communication Errors
|
||||
|
||||
**Symptoms:**
|
||||
- Communication works sometimes, fails other times
|
||||
- Occasional corrupted messages
|
||||
- Random disconnections
|
||||
|
||||
**Possible Causes & Solutions:**
|
||||
|
||||
1. **Poor Termination**
|
||||
- Measure resistance: should be exactly ~60Ω
|
||||
- Check termination resistors are securely connected
|
||||
- Verify only two 120Ω resistors present
|
||||
|
||||
2. **Ground Potential Differences**
|
||||
- **Solution:** Ensure GND wire is connected between all devices
|
||||
- Check GND continuity with multimeter
|
||||
- Verify no high resistance in GND path
|
||||
|
||||
3. **Electrical Noise**
|
||||
- Use shielded cable
|
||||
- Route CAN cable away from power cables
|
||||
- Connect shield to earth ground at one end only
|
||||
- Check for nearby sources of EMI (switching PSUs, motors, etc.)
|
||||
|
||||
4. **Cable Quality Issues**
|
||||
- Replace with proper CAN bus cable (120Ω impedance)
|
||||
- Avoid using random cables (cat5, speaker wire, etc.)
|
||||
- Check for damaged or kinked cables
|
||||
|
||||
5. **Too Many Nodes**
|
||||
- CAN transceiver limited to 110 nodes (CA-IS3050G)
|
||||
- In practice, fewer is better for reliability
|
||||
- Typical YamBMS: 2-3 devices only
|
||||
|
||||
### CAN Bus Completely Non-Functional
|
||||
|
||||
**Symptoms:**
|
||||
- No communication at all
|
||||
- Multimeter shows unexpected voltages
|
||||
- CAN transceiver very hot
|
||||
|
||||
**Critical Checks:**
|
||||
|
||||
1. **Correct Polarity**
|
||||
- CAN H to CAN H, CAN L to CAN L
|
||||
- **Not swapped!**
|
||||
- Some transceivers are damaged by reverse polarity
|
||||
|
||||
2. **Over-Termination**
|
||||
- Too many termination resistors (>2) causes excessive current
|
||||
- Measure total resistance: should be ~60Ω, not ~40Ω or less
|
||||
- Remove extra termination resistors
|
||||
|
||||
3. **Short Circuit**
|
||||
- Check for shorts between CAN H and CAN L
|
||||
- Check for shorts to GND or power rails
|
||||
- Inspect terminal blocks for debris or solder bridges
|
||||
|
||||
4. **Damaged Transceiver**
|
||||
- If voltage spikes occurred (no isolation), transceiver may be damaged
|
||||
- Replace board or transceiver IC
|
||||
- Consider using isolated CAN transceiver for future protection
|
||||
|
||||
### Measuring CAN Bus with Multimeter
|
||||
|
||||
**Idle Bus (Recessive State):**
|
||||
```
|
||||
CAN H: ~2.5V
|
||||
CAN L: ~2.5V
|
||||
Differential: ~0V
|
||||
```
|
||||
|
||||
**Active Bus (Mixed Dominant/Recessive):**
|
||||
```
|
||||
CAN H: fluctuating between ~2.5V and ~3.5V
|
||||
CAN L: fluctuating between ~2.5V and ~1.5V
|
||||
Differential: varies
|
||||
```
|
||||
|
||||
**If you see:**
|
||||
- CAN H = 0V or 5V continuously → Problem with transceiver or power
|
||||
- CAN L = 0V or 5V continuously → Problem with transceiver or power
|
||||
- No voltage fluctuation → No activity on bus (check if devices are transmitting)
|
||||
|
||||
## YamBMS-Specific CAN Configuration
|
||||
|
||||
### Typical YamBMS CAN Setup
|
||||
|
||||
**Hardware:**
|
||||
- ESP32-S3 board with CAN transceiver (LilyGo, Waveshare, M5Stack)
|
||||
- Solar inverter with CAN bus interface (Deye, Sofar, Growatt, Victron, etc.)
|
||||
- Twisted pair CAN cable (120Ω impedance)
|
||||
- Two 120Ω termination resistors (may be built-in)
|
||||
|
||||
**Software:**
|
||||
- YamBMS firmware configured for CAN output
|
||||
- CAN baud rate: typically 500 kbps (check inverter manual)
|
||||
- CAN protocol: Pylontech, SMA, Victron, or custom
|
||||
|
||||
**Wiring Example:**
|
||||
```
|
||||
YamBMS ESP32-S3 Solar Inverter
|
||||
(with CAN transceiver) (with CAN interface)
|
||||
┌─────────────────┐ ┌──────────────────┐
|
||||
│ CAN H ──────────┼────────────────┤ CAN H │
|
||||
│ CAN L ──────────┼────────────────┤ CAN L │
|
||||
│ GND ────────────┼────────────────┤ GND │
|
||||
└─────────────────┘ └──────────────────┘
|
||||
120Ω ↑ ↑ 120Ω
|
||||
(if at endpoint) (check inverter)
|
||||
```
|
||||
|
||||
### Inverter-Specific Notes
|
||||
|
||||
**Most Common CAN Speeds:**
|
||||
- **Deye/Sunsynk**: 500 kbps (Pylontech protocol)
|
||||
- **Growatt**: 500 kbps (Pylontech protocol)
|
||||
- **Sofar**: 500 kbps (Pylontech protocol)
|
||||
- **Victron**: 500 kbps (Victron VE.Can protocol)
|
||||
- **SMA**: 500 kbps (SMA CAN protocol)
|
||||
|
||||
**Always verify in your inverter's manual!**
|
||||
|
||||
### Common CAN Protocols for Battery Communication
|
||||
|
||||
- **Pylontech**: Most common, supported by many inverters
|
||||
- **SMA**: Used by SMA inverters
|
||||
- **Victron**: VE.Can protocol for Victron systems
|
||||
- **LG Resu**: Protocol used by LG battery systems
|
||||
- **BYD**: BYD battery protocol
|
||||
|
||||
YamBMS can typically emulate Pylontech or other protocols depending on your inverter.
|
||||
|
||||
## Advanced Topics
|
||||
|
||||
### CAN Bus Isolation
|
||||
|
||||
**What is CAN Isolation?**
|
||||
- Galvanic isolation between the ESP32 and the CAN bus
|
||||
- Protects the ESP32 from voltage spikes, ground loops, and noise
|
||||
- Uses opto-isolators or isolated DC-DC converters
|
||||
|
||||
**Benefits:**
|
||||
- Protects expensive ESP32 boards from damage
|
||||
- Improves noise immunity
|
||||
- Allows operation with ground potential differences
|
||||
- Reduces risk of ground loops
|
||||
|
||||
**Boards with Isolated CAN:**
|
||||
- ✅ Waveshare ESP32-S3-RS485-CAN (isolated)
|
||||
- ✅ M5Stack Atomic CAN Base (isolated, CA-IS3050G)
|
||||
- ❌ Some cheaper CAN modules (not isolated)
|
||||
|
||||
**Recommendation:** Always prefer isolated CAN transceivers for battery/inverter applications!
|
||||
|
||||
### CAN Bus Sniffing & Debugging
|
||||
|
||||
**Tools for CAN Bus Analysis:**
|
||||
- **CAN USB Adapter**: PCAN-USB, CANable, SLCAN
|
||||
- **Logic Analyzer**: Saleae, DSLogic with CAN protocol decoder
|
||||
- **Oscilloscope**: For low-level signal analysis
|
||||
|
||||
**Software Tools:**
|
||||
- **can-utils** (Linux): Command-line CAN tools
|
||||
- **SavvyCAN**: GUI-based CAN analyzer
|
||||
- **Wireshark**: With SocketCAN plugin for Linux
|
||||
|
||||
**Basic CAN Sniffing (Linux example):**
|
||||
```bash
|
||||
# View CAN traffic
|
||||
candump can0
|
||||
|
||||
# Send a CAN frame
|
||||
cansend can0 123#DEADBEEF
|
||||
|
||||
# Log CAN traffic to file
|
||||
candump -l can0
|
||||
```
|
||||
|
||||
### CAN FD (Flexible Data-Rate)
|
||||
|
||||
**What is CAN FD?**
|
||||
- Enhanced version of CAN bus
|
||||
- Higher data rates (up to 5 Mbps for data phase)
|
||||
- Larger payload (up to 64 bytes vs 8 bytes for classical CAN)
|
||||
|
||||
**YamBMS Note:**
|
||||
- Most solar inverters use **Classical CAN** (not CAN FD)
|
||||
- ESP32-S3 TWAI controller supports Classical CAN
|
||||
- CAN FD support requires specific transceivers and software
|
||||
- Not commonly needed for battery/inverter communication
|
||||
|
||||
## Safety & Best Practices
|
||||
|
||||
### Electrical Safety
|
||||
|
||||
⚠️ **WARNING:**
|
||||
- CAN bus in battery systems operates near **high-voltage DC batteries**
|
||||
- Always disconnect battery before working on CAN wiring
|
||||
- Use properly insulated tools
|
||||
- Verify no voltage on CAN bus before connecting/disconnecting
|
||||
|
||||
### Installation Best Practices
|
||||
|
||||
**DO:**
|
||||
- ✅ Plan your wiring layout before installation
|
||||
- ✅ Use proper crimping tools for terminal connections
|
||||
- ✅ Label wires clearly (CAN H, CAN L, GND)
|
||||
- ✅ Secure cables with cable ties to prevent movement
|
||||
- ✅ Protect cables from sharp edges and abrasion
|
||||
- ✅ Document your wiring configuration
|
||||
- ✅ Test with multimeter before powering on
|
||||
|
||||
**DON'T:**
|
||||
- ❌ Work on live circuits
|
||||
- ❌ Use damaged or frayed cables
|
||||
- ❌ Mix CAN cables with high-voltage power cables in same conduit
|
||||
- ❌ Exceed voltage/current ratings of your components
|
||||
- ❌ Modify inverter wiring without consulting manual
|
||||
|
||||
## Sources
|
||||
|
||||
- [CAN Bus Wikipedia](https://en.wikipedia.org/wiki/CAN_bus)
|
||||
- [ISO 11898 Standard (CAN Specification)](https://www.iso.org/standard/63648.html)
|
||||
- [Microchip CAN Bus Basics](https://www.microchip.com/design-centers/can)
|
||||
- [Texas Instruments: Introduction to CAN](https://www.ti.com/lit/an/sloa101b/sloa101b.pdf)
|
||||
|
||||
|
||||
---
|
||||
|
||||
**License:** This documentation is part of the YamBMS project and follows the same GPLv3 license.
|
||||
|
||||
**Disclaimer:** Always consult your device manuals and follow electrical safety procedures. This guide is for educational purposes.
|
||||
@@ -0,0 +1,820 @@
|
||||
# YamBMS - RS485 bus
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
## Overview
|
||||
|
||||
**RS485** (also known as TIA/EIA-485) is a robust serial communication standard designed for long-distance, multi-point industrial communication in electrically noisy environments. It is one of the most widely used communication protocols in industrial automation, building automation, and battery management systems.
|
||||
|
||||
In the YamBMS ecosystem, RS485 is primarily used to communicate with **JK-PB BMS units** (inverter BMS) and other industrial sensors over long distances with excellent noise immunity.
|
||||
|
||||

|
||||
|
||||
**Key Features:**
|
||||
- Multi-point communication (up to 32-256 nodes depending on transceiver)
|
||||
- Long distance capability (up to 1200 meters)
|
||||
- High noise immunity via differential signaling
|
||||
- Data rates up to 10 Mbps (typically 9600-115200 baud for BMS)
|
||||
- Half-duplex communication (one direction at a time)
|
||||
- Simple 2-wire or 3-wire configuration
|
||||
|
||||
## RS485 Fundamentals
|
||||
|
||||
### What is RS485?
|
||||
|
||||
RS485 uses a **two-wire differential signaling system**:
|
||||
- **A (Data+)**: Also called D+, non-inverting line
|
||||
- **B (Data-)**: Also called D-, inverting line
|
||||
|
||||
**Differential Signaling:**
|
||||
```
|
||||
Differential Signal = A - B
|
||||
|
||||
Logic '0' (space): A > B by at least +200mV
|
||||
Logic '1' (mark): A < B by at least -200mV
|
||||
|
||||
Typical levels:
|
||||
Logic '0': A = +3V, B = -1V → Difference = +4V
|
||||
Logic '1': A = -1V, B = +3V → Difference = -4V
|
||||
```
|
||||
|
||||
This differential approach provides excellent **common-mode noise rejection**, meaning that electrical noise affecting both wires equally is ignored, making RS485 extremely reliable in industrial environments.
|
||||
|
||||
### RS485 Speed & Distance
|
||||
|
||||
The maximum cable length depends on the communication speed:
|
||||
|
||||
| Baud Rate | Maximum Distance | Typical Use Case |
|
||||
|-----------|------------------|------------------|
|
||||
| 10 Mbps | 12 meters | Short, very high speed |
|
||||
| 1 Mbps | 50 meters | High speed local networks |
|
||||
| 115200 bps | ~500 meters | **Common for JK-B BMS** |
|
||||
| 9600 bps | ~1200 meters | **Common for JK-PB BMS**, long distance |
|
||||
| 2400 bps | ~1200 meters | Very long distance, slower speed |
|
||||
|
||||
**YamBMS Typical Configurations:**
|
||||
- **JK-B BMS (UART)**: 115200 baud
|
||||
- **JK-PB BMS (RS485)**: 9600 baud
|
||||
- **Modbus devices**: 9600, 19200, or 38400 baud
|
||||
|
||||
### RS485 vs RS232
|
||||
|
||||
| Feature | RS232 | RS485 |
|
||||
|---------|-------|-------|
|
||||
| **Distance** | ~15 meters | Up to 1200 meters |
|
||||
| **Speed** | Up to 115200 bps | Up to 10 Mbps |
|
||||
| **Topology** | Point-to-point only | Multi-drop (up to 256 nodes) |
|
||||
| **Signal** | Single-ended | Differential |
|
||||
| **Noise Immunity** | Poor | Excellent |
|
||||
| **Use Case** | PC serial ports, short connections | Industrial, long distance |
|
||||
|
||||
**Why RS485 for YamBMS?**
|
||||
- Long-distance BMS connections
|
||||
- Noisy electrical environment (batteries, inverters)
|
||||
- Multiple BMS units on one bus (multi-drop)
|
||||
- Superior reliability
|
||||
|
||||
### RS485 Topology
|
||||
|
||||
**Linear Bus (Multi-Drop) - CORRECT:**
|
||||
```
|
||||
[Master/ESP32]───[BMS 1]───[BMS 2]───[BMS 3]───[BMS 4]
|
||||
↑ ↑
|
||||
120Ω term 120Ω term
|
||||
```
|
||||
|
||||
**Important Rules:**
|
||||
- ✅ **Linear topology** (daisy chain, not star)
|
||||
- ✅ **Two termination resistors** (120Ω each at both ends)
|
||||
- ✅ **Short stubs** (branches < 30cm if unavoidable)
|
||||
- ❌ **NOT star topology** (causes signal reflections)
|
||||
- ❌ **NOT ring topology** (not supported)
|
||||
|
||||
## RS485 Wiring
|
||||
|
||||
### Standard 3-Wire Configuration
|
||||
|
||||
**MANDATORY wiring for RS485 bus:**
|
||||
|
||||
```
|
||||
RS485 Bus 3-Wire Configuration (REQUIRED!)
|
||||
===========================================
|
||||
Device 1 Device 2 Device 3
|
||||
├─ A (Data+) ────────── A (Data+) ────────── A (Data+)
|
||||
├─ B (Data-) ────────── B (Data-) ────────── B (Data-)
|
||||
└─ GND ──────────────── GND ──────────────── GND ← MANDATORY!
|
||||
```
|
||||
|
||||
> [!CRITICAL]
|
||||
> **The GND connection is MANDATORY for RS485!**
|
||||
>
|
||||
> Unlike CAN bus where GND is "strongly recommended," RS485 **REQUIRES** a ground reference wire for reliable operation. This is not optional!
|
||||
|
||||
### Pin Identification
|
||||
|
||||
**Common RS485 Terminal Labeling:**
|
||||
|
||||
Different manufacturers use different naming conventions. Here are the most common:
|
||||
|
||||
| Standard | Pin 1 (Data+) | Pin 2 (Data-) | Pin 3 |
|
||||
|----------|---------------|---------------|-------|
|
||||
| **Most Common** | **A** | **B** | **GND** |
|
||||
| Alternative 1 | D+ | D- | GND |
|
||||
| Alternative 2 | T/R+ | T/R- | GND |
|
||||
| Alternative 3 | + | - | GND |
|
||||
| Alternative 4 | H (High) | L (Low) | GND |
|
||||
|
||||
**⚠️ WARNING: A/B Confusion!**
|
||||
|
||||
Some manufacturers label pins **opposite** to the standard:
|
||||
- **Standard (Most Common)**: A = Data+, B = Data-
|
||||
- **Reversed (Some devices)**: A = Data-, B = Data+
|
||||
|
||||
**If communication doesn't work, try swapping A and B!**
|
||||
|
||||
**Waveshare boards:**
|
||||
- L pin = A (Data+)
|
||||
- H pin = B (Data-)
|
||||
|
||||
**Always verify with your device documentation!**
|
||||
|
||||
### Cable Requirements
|
||||
|
||||
**Recommended Cable Specifications:**
|
||||
- **Type:** Twisted pair cable (A and B wires twisted together)
|
||||
- **Characteristic Impedance:** 120Ω (matches termination resistors)
|
||||
- **Gauge:** 24 AWG to 22 AWG for most applications
|
||||
- **Shielding:** Shielded cable (STP) **highly recommended** for noisy environments
|
||||
- **Quality:** Industrial-grade RS485 cable recommended
|
||||
|
||||
**Acceptable Alternative (short distances only):**
|
||||
- CAT5/CAT6 ethernet cable (use one twisted pair for A/B, another for GND)
|
||||
- **Only for distances < 100 meters and low noise environments!**
|
||||
|
||||
### Ground Connection - ABSOLUTELY CRITICAL
|
||||
|
||||
> [!CRITICAL]
|
||||
> **MUST YOU connect the GND wire on RS485 bus?**
|
||||
|
||||
**Answer: YES - ABSOLUTELY MANDATORY!**
|
||||
|
||||
This is **NOT optional**. RS485 **REQUIRES** a ground reference wire between all devices. Let me explain why this is even more critical than for CAN bus.
|
||||
|
||||
#### Why Ground Connection is MANDATORY for RS485
|
||||
|
||||
**1. Common Mode Voltage Range (Stricter than CAN)**
|
||||
- RS485 transceivers tolerate **-7V to +12V** common mode voltage (similar to CAN)
|
||||
- **BUT:** RS485 is significantly **more sensitive** to ground potential differences than CAN
|
||||
- Without GND: communication **WILL FAIL** or be extremely unreliable
|
||||
|
||||
**2. Long Distance Communications**
|
||||
- RS485 is designed for distances up to **1200 meters**
|
||||
- Over these distances, ground potential differences of **several volts** are guaranteed
|
||||
- Without GND connection: **catastrophic communication failure** or **transceiver damage**
|
||||
|
||||
**3. Official RS485/TIA-485 Standard**
|
||||
- The standard **explicitly requires** a signal ground reference
|
||||
- Industry best practices **always include ground wire**
|
||||
|
||||
**Quote from industrial RS485 documentation:**
|
||||
> *"While a differential signal does not require a signal ground to communicate, the ground wire serves an important purpose. Over a distance of hundreds or thousands of feet there can be very significant differences in the voltage level of 'ground.' RS-485 networks can typically maintain correct data with a difference of -7 to +12 Volts. If the grounds differ more than that amount, **data will be lost and often the port itself will be damaged**."*
|
||||
|
||||
**4. Multiple Power Supplies**
|
||||
- ESP32 and BMS units have separate power supplies
|
||||
- Different power supplies = different ground potentials
|
||||
- Can easily exceed the ±7V to +12V common mode range
|
||||
- **Result without GND: Transceiver damage and communication failure**
|
||||
|
||||
**5. Protection Against Ground Loops**
|
||||
- Proper grounding prevents destructive ground loop currents
|
||||
- In long cable runs, ground potential differences create currents in signal wires
|
||||
- GND wire carries these currents, protecting signal integrity
|
||||
|
||||
#### Consequences of Omitting GND on RS485
|
||||
|
||||
**What WILL happen without GND connection:**
|
||||
|
||||
```
|
||||
❌ WITHOUT GND - Guaranteed Problems:
|
||||
✗ Frequent communication errors
|
||||
✗ Complete communication failure over distance
|
||||
✗ Intermittent data corruption
|
||||
✗ Data packets lost or garbled
|
||||
✗ BMS readings incorrect or missing
|
||||
✗ RISK: Transceiver damage (voltage > ±12V)
|
||||
✗ RISK: Complete port failure requiring replacement
|
||||
```
|
||||
|
||||
**Real-world failure modes observed:**
|
||||
- BMS readings work for 5 minutes, then fail
|
||||
- Communication works in the morning, fails in the afternoon (temperature-dependent ground shifts)
|
||||
- Works on the bench (short cables), fails in installation (long cables)
|
||||
- Random disconnections during high battery current (ground bounce)
|
||||
|
||||
#### When GND Can Be Omitted (EXTREMELY RARE - NOT RECOMMENDED)
|
||||
|
||||
**Only in these VERY limited cases (still not recommended):**
|
||||
- Distance **< 1 meter**
|
||||
- **Identical power supply** (same PSU, same ground reference)
|
||||
- Clean bench testing environment only
|
||||
- **Duration:** Temporary testing only
|
||||
|
||||
**Even in these cases, you SHOULD connect GND for these reasons:**
|
||||
- Establishes good habits
|
||||
- What works on the bench may fail in installation
|
||||
- Ground connection costs nothing but saves hours of troubleshooting
|
||||
|
||||
#### Isolated RS485 Transceivers
|
||||
|
||||
**Question:** If my board has isolated RS485 (e.g., Waveshare, M5Stack RS485-ISO), do I still need to connect GND?
|
||||
|
||||
**Answer:** **YES - ABSOLUTELY!**
|
||||
|
||||
```
|
||||
Board with RS485 Isolation
|
||||
===========================
|
||||
|
||||
ESP32 Side Isolation RS485 Bus Side
|
||||
(non-isolated) ═══════════ (isolated)
|
||||
|
||||
├─ A ──→ to BMS
|
||||
├─ B ──→ to BMS
|
||||
└─ GND ──→ to BMS (MANDATORY!)
|
||||
|
||||
Isolation protects the ESP32 from voltage spikes, but devices
|
||||
on the isolated side STILL REQUIRE a common ground reference!
|
||||
```
|
||||
|
||||
**Explanation:**
|
||||
- **Isolation** protects your ESP32 from damage
|
||||
- Devices on the **isolated side** (BMS units, sensors) **MUST** share a common ground
|
||||
- Without GND: communication between BMS units will be unreliable despite isolation
|
||||
- The isolated DC-DC converter provides power isolation, not signal ground
|
||||
|
||||
### Wiring Best Practices
|
||||
|
||||
**DO:**
|
||||
- ✅ **ALWAYS connect GND wire between ALL devices** (mandatory!)
|
||||
- ✅ Use twisted pair cable (A and B twisted together)
|
||||
- ✅ Use proper RS485 cable (120Ω impedance)
|
||||
- ✅ Keep cable runs as short as practical
|
||||
- ✅ Add termination resistors at both ends (120Ω)
|
||||
- ✅ Use shielded cable in electrically noisy environments
|
||||
- ✅ Connect shield to earth ground at **one end only** (prevents ground loops)
|
||||
- ✅ Avoid running RS485 cables parallel to AC power cables
|
||||
- ✅ Use separate conduits for RS485 and high-voltage power
|
||||
|
||||
**DON'T:**
|
||||
- ❌ **NEVER omit the GND wire** (causes guaranteed problems!)
|
||||
- ❌ Use random cable (speaker wire, telephone cable, etc.)
|
||||
- ❌ Create star or ring topologies
|
||||
- ❌ Exceed maximum cable length for your baud rate
|
||||
- ❌ Add more than two 120Ω termination resistors
|
||||
- ❌ Connect shield to ground at both ends (causes ground loops)
|
||||
- ❌ Swap A and B randomly (check device documentation first)
|
||||
|
||||
## Termination Resistors
|
||||
|
||||
### Why Termination is Necessary
|
||||
|
||||
**Signal Reflections:**
|
||||
- When an electrical signal reaches the end of a cable, it reflects back
|
||||
- These reflections cause signal distortion, ringing, and communication errors
|
||||
- **Termination resistors** absorb the signal energy, preventing reflections
|
||||
- Critical for high-speed communication or long cable runs
|
||||
|
||||
**The 120Ω Standard:**
|
||||
- RS485 cable has a characteristic impedance of 120Ω
|
||||
- Termination resistors match this impedance
|
||||
- Result: clean signal transmission without reflections
|
||||
|
||||
### Proper Termination Configuration
|
||||
|
||||
**Correct: Exactly TWO 120Ω resistors at both ends**
|
||||
|
||||
```
|
||||
CORRECT Termination
|
||||
===================
|
||||
120Ω 120Ω
|
||||
║ ║
|
||||
[ESP32]───[BMS 1]───[BMS 2]───[BMS 3]───[BMS 4]
|
||||
└─ Start of bus End of bus ─┘
|
||||
```
|
||||
|
||||
**How to verify termination:**
|
||||
1. **Power off all devices** (important!)
|
||||
2. **Disconnect** one end of the RS485 bus
|
||||
3. Measure resistance between A and B with a multimeter
|
||||
4. **Expected result: ~60Ω** (two 120Ω resistors in parallel = 60Ω)
|
||||
|
||||
```
|
||||
Termination Math:
|
||||
=================
|
||||
Two 120Ω resistors in parallel:
|
||||
R_total = (R1 × R2) / (R1 + R2)
|
||||
R_total = (120 × 120) / (120 + 120)
|
||||
R_total = 14400 / 240 = 60Ω
|
||||
```
|
||||
|
||||
### Built-in vs External Termination
|
||||
|
||||
**Boards with Built-in Termination:**
|
||||
|
||||
Some boards have onboard 120Ω resistors that can be enabled:
|
||||
- **Waveshare ESP32-S3-RS485-CAN**: Jumper for RS485 termination (120R/NC)
|
||||
- **M5Stack RS485-ISO Unit (U094)**: Includes separate 120Ω resistor to connect
|
||||
- Many industrial RS485 devices have switchable termination
|
||||
|
||||
**Boards without Built-in Termination:**
|
||||
|
||||
Some boards require external termination resistors:
|
||||
- **LilyGo T-Connect**: No built-in RS485 termination
|
||||
- External 120Ω resistor must be connected between A and B at bus endpoints
|
||||
|
||||
**How to add external termination:**
|
||||
```
|
||||
Physical Connection:
|
||||
====================
|
||||
120Ω Resistor (1/4W or 1/2W)
|
||||
┌─────┐
|
||||
A ───────┤ ├─────── B
|
||||
└─────┘
|
||||
(at bus endpoint)
|
||||
```
|
||||
|
||||
**Where to buy termination resistors:**
|
||||
- 1/4W or 1/2W 120Ω resistors from any electronics supplier
|
||||
- Pre-made RS485 termination plugs (with screw terminals)
|
||||
- Modbus/Profibus termination resistors
|
||||
|
||||
### Common Termination Mistakes
|
||||
|
||||
**❌ WRONG: No termination**
|
||||
```
|
||||
[ESP32]───[BMS 1]───[BMS 2]
|
||||
```
|
||||
**Result:** Signal reflections, communication errors, unreliable operation
|
||||
|
||||
**❌ WRONG: Only one termination resistor**
|
||||
```
|
||||
120Ω
|
||||
║
|
||||
[ESP32]───[BMS 1]───[BMS 2]
|
||||
```
|
||||
**Result:** One end unterminated, partial reflections
|
||||
|
||||
**❌ WRONG: Termination in the middle**
|
||||
```
|
||||
120Ω
|
||||
║
|
||||
[ESP32]───[BMS 1]───[BMS 2]───[BMS 3]
|
||||
```
|
||||
**Result:** Both ends unterminated, reflections from both directions
|
||||
|
||||
**❌ WRONG: More than two termination resistors**
|
||||
```
|
||||
120Ω 120Ω 120Ω
|
||||
║ ║ ║
|
||||
[ESP32]───[BMS 1]───[BMS 2]───[BMS 3]
|
||||
```
|
||||
**Result:** Total impedance too low (~40Ω), excessive current, signal distortion
|
||||
|
||||
### Determining Termination Configuration
|
||||
|
||||
**For a typical YamBMS setup (ESP32 ↔ Multiple BMS):**
|
||||
|
||||
```
|
||||
Multi-drop RS485 connection:
|
||||
============================
|
||||
|
||||
120Ω (if available) 120Ω (add if needed)
|
||||
║ ║
|
||||
[ESP32]───[BMS 1]───[BMS 2]───[BMS 3]───[BMS 4]
|
||||
└─ Start End ─┘
|
||||
```
|
||||
|
||||
**Steps:**
|
||||
1. **Check your ESP32 board:**
|
||||
- Does it have built-in termination? (check docs/jumpers)
|
||||
- If yes: enable it (move jumper to 120R position)
|
||||
- If no: add external 120Ω resistor between A and B
|
||||
|
||||
2. **Check the last BMS on the bus:**
|
||||
- Most BMS units do NOT have built-in termination
|
||||
- Add external 120Ω resistor between A and B at the last BMS
|
||||
|
||||
3. **Verify with multimeter:**
|
||||
- Power off all devices
|
||||
- Disconnect one end
|
||||
- Measure between A and B
|
||||
- Should read ~60Ω
|
||||
|
||||
### When is Termination Optional?
|
||||
|
||||
**Short, Low-Speed Connections:**
|
||||
- Cable length < 10 meters
|
||||
- Baud rate ≤ 9600 bps
|
||||
- Few communication errors tolerable (not recommended for YamBMS!)
|
||||
|
||||
**However:** For reliability, **always add termination** regardless of distance or speed. It costs almost nothing and prevents hours of troubleshooting!
|
||||
|
||||
## Common RS485 Issues & Troubleshooting
|
||||
|
||||
### No Communication on RS485
|
||||
|
||||
**Symptoms:**
|
||||
- No data received from BMS
|
||||
- ESP32 cannot communicate with devices
|
||||
- RS485 bus appears "dead"
|
||||
|
||||
**Troubleshooting Steps:**
|
||||
|
||||
1. **Check Wiring (MOST COMMON ISSUE)**
|
||||
- ✓ A to A, B to B (not swapped)
|
||||
- ✓ **GND connected between ALL devices** (mandatory!)
|
||||
- ✓ No loose connections
|
||||
- ✓ Cable integrity (no breaks)
|
||||
- ✓ Try swapping A and B if still not working (labeling may be reversed)
|
||||
|
||||
2. **Verify Ground Connection**
|
||||
- **Critical:** Measure continuity between all GND pins
|
||||
- GND must have low resistance (< 1Ω) between all devices
|
||||
- Without GND: guaranteed communication failure
|
||||
|
||||
3. **Check Termination**
|
||||
- Power off all devices
|
||||
- Disconnect one end of bus
|
||||
- Measure resistance between A and B
|
||||
- Should be ~60Ω (two 120Ω resistors in parallel)
|
||||
|
||||
4. **Verify Baud Rate**
|
||||
- ESP32 and BMS must use same baud rate
|
||||
- JK-B BMS (UART): 115200 baud
|
||||
- JK-PB BMS (RS485): 9600 baud
|
||||
- Check BMS documentation
|
||||
|
||||
5. **Check Power**
|
||||
- All devices powered on
|
||||
- Correct voltage levels
|
||||
- Stable power supplies
|
||||
|
||||
6. **Verify Polarity**
|
||||
- Some devices label A/B opposite to standard
|
||||
- **Try swapping A and B connections**
|
||||
- This is a very common issue!
|
||||
|
||||
### Intermittent Communication Errors
|
||||
|
||||
**Symptoms:**
|
||||
- Communication works sometimes, fails other times
|
||||
- Occasional corrupted data
|
||||
- Random BMS disconnections
|
||||
- Works for minutes/hours, then fails
|
||||
|
||||
**Possible Causes & Solutions:**
|
||||
|
||||
1. **Missing or Poor Ground Connection (MOST COMMON)**
|
||||
- **Solution:** Ensure GND wire is connected between ALL devices
|
||||
- Check GND continuity with multimeter (should be < 1Ω)
|
||||
- Verify no high resistance in GND path
|
||||
- **This is the #1 cause of intermittent RS485 problems!**
|
||||
|
||||
2. **Ground Potential Differences**
|
||||
- Without GND: different ground potentials cause voltage shifts
|
||||
- Exceeds common mode range (-7V to +12V)
|
||||
- **Solution:** Connect GND wire securely
|
||||
|
||||
3. **Poor Termination**
|
||||
- Measure resistance: should be exactly ~60Ω
|
||||
- Check termination resistors securely connected
|
||||
- Verify only two 120Ω resistors present
|
||||
|
||||
4. **Electrical Noise Interference**
|
||||
- Use shielded cable (STP)
|
||||
- Route RS485 cable away from AC power cables
|
||||
- Connect shield to earth ground at one end only
|
||||
- Check for nearby sources of EMI (motors, switching PSUs, inverters)
|
||||
|
||||
5. **Cable Quality Issues**
|
||||
- Replace with proper RS485 cable (120Ω impedance)
|
||||
- Avoid using random cables (cat5 for long distances, speaker wire, etc.)
|
||||
- Check for damaged or kinked cables
|
||||
|
||||
6. **Temperature-Related Issues**
|
||||
- Ground potential differences change with temperature
|
||||
- Connections expand/contract
|
||||
- **Solution:** Ensure solid, reliable connections with GND wire
|
||||
|
||||
### Very Slow or Corrupted Data
|
||||
|
||||
**Symptoms:**
|
||||
- Data arrives but is very slow
|
||||
- Frequent CRC errors
|
||||
- Garbled messages
|
||||
|
||||
**Possible Causes:**
|
||||
|
||||
1. **Incorrect Baud Rate**
|
||||
- ESP32 and BMS must match exactly
|
||||
- Common rates: 9600, 19200, 38400, 115200
|
||||
- Even small mismatches cause problems
|
||||
|
||||
2. **Cable Too Long for Baud Rate**
|
||||
- 115200 baud: max ~500 meters
|
||||
- 9600 baud: max ~1200 meters
|
||||
- Higher speeds require shorter cables
|
||||
|
||||
3. **Missing Ground Reference**
|
||||
- Without GND: signal levels shift
|
||||
- Receiver interprets signals incorrectly
|
||||
- **Solution:** Connect GND wire!
|
||||
|
||||
4. **Over-Termination**
|
||||
- Too many termination resistors (>2)
|
||||
- Measure resistance: should be ~60Ω, not ~40Ω
|
||||
- Remove extra terminators
|
||||
|
||||
### RS485 Transceiver Damage
|
||||
|
||||
**Symptoms:**
|
||||
- Complete communication failure
|
||||
- Hot transceiver chip
|
||||
- Burnt smell
|
||||
- No voltage on A or B lines
|
||||
|
||||
**Causes:**
|
||||
- Voltage spike exceeded ±12V common mode range
|
||||
- Ground potential difference too large without GND connection
|
||||
- Reverse polarity connection
|
||||
- Short circuit between A, B, or GND
|
||||
|
||||
**Prevention:**
|
||||
- **Always connect GND wire!**
|
||||
- Use isolated RS485 transceivers (Waveshare, M5Stack RS485-ISO)
|
||||
- Check connections before applying power
|
||||
- Use proper termination
|
||||
|
||||
**Solution if damaged:**
|
||||
- Replace board or transceiver IC
|
||||
- Investigate root cause before reconnecting
|
||||
- Consider upgrading to isolated transceiver
|
||||
|
||||
### Measuring RS485 with Multimeter
|
||||
|
||||
**Idle Bus (Mark State):**
|
||||
```
|
||||
With termination (power ON):
|
||||
A (Data+): ~2.5V to 3.3V
|
||||
B (Data-): ~1.5V to 2.5V
|
||||
Differential: A > B (mark state)
|
||||
```
|
||||
|
||||
**Active Bus (Mixed States):**
|
||||
```
|
||||
A: Fluctuating between ~1.5V and ~3.5V
|
||||
B: Fluctuating opposite to A
|
||||
Differential: Varies with data
|
||||
```
|
||||
|
||||
**If you see:**
|
||||
- A = 0V or 5V continuously → Problem with transceiver or power
|
||||
- B = 0V or 5V continuously → Problem with transceiver or power
|
||||
- A = B (same voltage) → No differential signal, check driver/termination
|
||||
- No voltage fluctuation → No activity (check if devices are transmitting)
|
||||
|
||||
## YamBMS-Specific RS485 Configuration
|
||||
|
||||
### JK-PB BMS via RS485 (Recommended Configuration)
|
||||
|
||||
**Hardware:**
|
||||
- ESP32-S3 board with RS485 transceiver (Waveshare ESP32-S3-RS485-CAN, M5Stack AtomS3 + RS485-ISO Unit)
|
||||
- Multiple JK-PB BMS units (inverter BMS)
|
||||
- Twisted pair RS485 cable (120Ω impedance)
|
||||
- Two 120Ω termination resistors
|
||||
|
||||
**Communication Parameters:**
|
||||
- **Protocol:** RS485 (Modbus RTU)
|
||||
- **Baud Rate:** 9600 bps (typical for JK-PB)
|
||||
- **Data Bits:** 8
|
||||
- **Parity:** None (N)
|
||||
- **Stop Bits:** 1
|
||||
- **Format:** 8N1
|
||||
|
||||
**Wiring Example:**
|
||||
```
|
||||
YamBMS ESP32-S3 JK-PB BMS (Multiple Units)
|
||||
(with RS485)
|
||||
┌──────────────┐ ┌───────┐ ┌───────┐ ┌───────┐
|
||||
│ A ──────────┼──────────────┤ A ├──┤ A ├──┤ A │
|
||||
│ B ──────────┼──────────────┤ B ├──┤ B ├──┤ B │
|
||||
│ GND ─────────┼──────────────┤ GND ├──┤ GND ├──┤ GND │
|
||||
└──────────────┘ └───────┘ └───────┘ └───────┘
|
||||
120Ω ↑ BMS 1 BMS 2 BMS 3
|
||||
(if at endpoint) ↑ 120Ω (add)
|
||||
```
|
||||
|
||||
**Important Notes:**
|
||||
- Each JK-PB BMS must have a **unique address** (ID 1, 2, 3, etc.)
|
||||
- ESP32 polls each BMS sequentially by address
|
||||
- All BMS units share the same RS485 bus (multi-drop)
|
||||
- **GND must be connected between all devices!**
|
||||
|
||||
### JK-B BMS via UART (Direct Serial Connection)
|
||||
|
||||
**Hardware:**
|
||||
- ESP32 board with UART pins
|
||||
- JK-B BMS with UART interface (not RS485)
|
||||
- 3-wire connection (TX, RX, GND)
|
||||
|
||||
**Communication Parameters:**
|
||||
- **Protocol:** UART (Serial)
|
||||
- **Baud Rate:** 115200 bps
|
||||
- **Data Bits:** 8
|
||||
- **Parity:** None (N)
|
||||
- **Stop Bits:** 1
|
||||
- **Format:** 8N1
|
||||
|
||||
**Wiring (Point-to-Point):**
|
||||
```
|
||||
ESP32 UART JK-B BMS UART
|
||||
┌──────────┐ ┌──────────┐
|
||||
│ TX ──────┼───────────┤ RX │
|
||||
│ RX ──────┼───────────┤ TX │
|
||||
│ GND ─────┼───────────┤ GND │
|
||||
└──────────┘ └──────────┘
|
||||
```
|
||||
|
||||
**Notes:**
|
||||
- This is **NOT RS485** - it's direct UART/serial
|
||||
- No RS485 transceiver needed
|
||||
- No termination resistors needed
|
||||
- Limited to short distances (~2 meters recommended)
|
||||
- Only one BMS per UART (point-to-point)
|
||||
- **For multiple JK-B BMS, use multiple UART ports or switch to JK-PB via RS485!**
|
||||
|
||||
### Comparison: JK-B (UART) vs JK-PB (RS485)
|
||||
|
||||
| Feature | JK-B (UART) | JK-PB (RS485) |
|
||||
|---------|-------------|---------------|
|
||||
| **Interface** | Direct UART | RS485 differential |
|
||||
| **Distance** | < 5 meters | Up to 1200 meters |
|
||||
| **Multiple BMS** | Need multiple UARTs | Single RS485 bus (multi-drop) |
|
||||
| **Transceiver** | None (direct) | RS485 transceiver required |
|
||||
| **Baud Rate** | 115200 bps | 9600 bps (typical) |
|
||||
| **Termination** | Not needed | 120Ω at both ends |
|
||||
| **Noise Immunity** | Poor | Excellent |
|
||||
| **Recommended For** | 1-2 BMS, short distance | Multiple BMS, long distance |
|
||||
|
||||
**YamBMS Recommendation:**
|
||||
- **JK-PB BMS + RS485** is the better choice for installations with multiple BMS units or longer distances.
|
||||
|
||||
## Advanced Topics
|
||||
|
||||
### RS485 Isolation
|
||||
|
||||
**What is RS485 Isolation?**
|
||||
- Galvanic isolation between the ESP32 and the RS485 bus
|
||||
- Protects the ESP32 from voltage spikes, ground loops, and electrical noise
|
||||
- Uses opto-isolators and isolated DC-DC converters
|
||||
|
||||
**Benefits:**
|
||||
- Protects expensive ESP32 boards from damage
|
||||
- Allows operation with large ground potential differences
|
||||
- Prevents ground loops
|
||||
- Improves noise immunity in harsh electrical environments
|
||||
|
||||
**Boards with Isolated RS485:**
|
||||
- ✅ Waveshare ESP32-S3-RS485-CAN (isolated, CA-IS3082W chip)
|
||||
- ✅ M5Stack RS485-ISO Unit (U094) (isolated, CA-IS3082W chip, 1000V isolation)
|
||||
- ❌ Some cheaper RS485 modules (not isolated)
|
||||
|
||||
**Isolation Voltage Ratings:**
|
||||
- Waveshare: Isolated DC-DC + optocoupler isolation
|
||||
- M5Stack RS485-ISO Unit: **1000V RMS isolation**
|
||||
|
||||
**Recommendation:** Always prefer isolated RS485 transceivers for battery/BMS applications!
|
||||
|
||||
### Fail-Safe Protection
|
||||
|
||||
**What is Fail-Safe?**
|
||||
- Feature of some RS485 transceivers
|
||||
- If A and B inputs are open or shorted, receiver outputs a known state (high)
|
||||
- Prevents random data output when bus is disconnected
|
||||
|
||||
**Boards with Fail-Safe:**
|
||||
- M5Stack RS485-ISO Unit (CA-IS3082W has fail-safe)
|
||||
|
||||
**Benefit for YamBMS:**
|
||||
- If a BMS is disconnected or cable breaks, ESP32 detects clean "no data" state
|
||||
- Prevents false readings from floating inputs
|
||||
|
||||
### Half-Duplex vs Full-Duplex
|
||||
|
||||
**Half-Duplex (Most Common for RS485):**
|
||||
- Uses 2 wires (A and B) plus GND
|
||||
- Communication in one direction at a time
|
||||
- Transmitter enable (DE/RE) control required
|
||||
- **This is what JK-PB BMS uses**
|
||||
|
||||
**Full-Duplex:**
|
||||
- Uses 4 wires (TX+, TX-, RX+, RX-) plus GND
|
||||
- Simultaneous bidirectional communication
|
||||
- More expensive and complex
|
||||
- Rarely needed for BMS applications
|
||||
|
||||
**YamBMS:** Typically uses half-duplex RS485.
|
||||
|
||||
### RS485 Repeaters
|
||||
|
||||
**What is an RS485 Repeater?**
|
||||
- Device that extends the RS485 bus beyond normal distance/node limits
|
||||
- Regenerates the signal for another 1200 meters
|
||||
- Isolates one segment from another
|
||||
|
||||
**When to Use:**
|
||||
- Very long distances (> 1200 meters)
|
||||
- Very high number of nodes (> 32 without repeater)
|
||||
- Need to isolate bus segments
|
||||
|
||||
**YamBMS:** Rarely needed for typical installations.
|
||||
|
||||
### Modbus Protocol
|
||||
|
||||
**What is Modbus?**
|
||||
- Application layer protocol that runs over RS485 (physical layer)
|
||||
- Standard for industrial device communication
|
||||
- Two variants: Modbus RTU (binary) and Modbus ASCII
|
||||
|
||||
**JK-PB BMS:**
|
||||
- Uses Modbus RTU protocol over RS485
|
||||
- Standard function codes for reading registers
|
||||
- CRC error checking
|
||||
|
||||
**YamBMS Implementation:**
|
||||
- ESPHome Modbus component
|
||||
- Configured for Modbus RTU at 9600 baud
|
||||
- Reads voltage, current, SOC, temperature, etc.
|
||||
|
||||
## Safety & Best Practices
|
||||
|
||||
### Electrical Safety
|
||||
|
||||
⚠️ **WARNING:**
|
||||
- RS485 in battery systems operates near **high-voltage DC batteries**
|
||||
- Always disconnect battery before working on RS485 wiring
|
||||
- Use properly insulated tools and materials
|
||||
- Verify no voltage on RS485 bus before connecting/disconnecting
|
||||
- **Never work on live circuits!**
|
||||
|
||||
### Installation Best Practices
|
||||
|
||||
**DO:**
|
||||
- ✅ **ALWAYS connect GND wire between ALL devices** (mandatory!)
|
||||
- ✅ Plan your wiring layout before installation
|
||||
- ✅ Use proper crimping tools for terminal connections
|
||||
- ✅ Label wires clearly (A, B, GND)
|
||||
- ✅ Secure cables with cable ties to prevent movement
|
||||
- ✅ Protect cables from sharp edges, abrasion, and UV exposure
|
||||
- ✅ Use cable glands for outdoor installations
|
||||
- ✅ Document your wiring configuration (take photos!)
|
||||
- ✅ Test with multimeter before powering on
|
||||
|
||||
**DON'T:**
|
||||
- ❌ **NEVER omit the GND wire** (guaranteed problems!)
|
||||
- ❌ Work on live circuits
|
||||
- ❌ Use damaged or frayed cables
|
||||
- ❌ Mix RS485 cables with high-voltage AC power cables in same conduit
|
||||
- ❌ Exceed voltage/current ratings of components
|
||||
- ❌ Modify BMS wiring without consulting manual
|
||||
- ❌ Use star or ring topology (linear bus only!)
|
||||
|
||||
### Preventive Maintenance
|
||||
|
||||
**Regular Checks:**
|
||||
- Inspect cable condition (wear, damage, UV degradation)
|
||||
- Verify termination resistors still in place
|
||||
- Check GND continuity between all devices
|
||||
- Tighten terminal block screws (can loosen over time)
|
||||
- Monitor communication error rates in YamBMS logs
|
||||
|
||||
**Annual Maintenance:**
|
||||
- Replace cables showing signs of UV damage (outdoor)
|
||||
- Clean terminal blocks (dust, corrosion)
|
||||
- Verify GND resistance still low (< 1Ω between all devices)
|
||||
|
||||
## Sources
|
||||
|
||||
- [TIA/EIA-485 Standard (RS485 Specification)](https://en.wikipedia.org/wiki/RS-485)
|
||||
- [Modbus Protocol Specification](https://modbus.org/docs/Modbus_Application_Protocol_V1_1b3.pdf)
|
||||
- [Schneider Electric RS485 Wiring Guide](https://www.se.com/ca/en/faqs/FA221785/)
|
||||
- [Analog Devices RS485 Design Guide](https://www.analog.com/en/technical-articles/rs485-design-guide.html)
|
||||
|
||||
---
|
||||
|
||||
**License:** This documentation is part of the YamBMS project and follows the same GPLv3 license.
|
||||
|
||||
**Disclaimer:** Always consult your device manuals and follow electrical safety procedures. This guide is for educational purposes. Work with high-voltage batteries requires proper training and certification.
|
||||
@@ -11,6 +11,7 @@
|
||||
* `JK` BMS (BLE / UART / RS485)
|
||||
* `JBD` BMS (BLE / UART)
|
||||
* `Seplos V1 V2 V3` BMS (RS485)
|
||||
* `PACE` BMS (RS485)
|
||||
* `BASEN` BMS (RS485)
|
||||
* `DEYE` BMS (CAN)
|
||||
|
||||
@@ -24,23 +25,29 @@
|
||||
|
||||
**Note: other Shunt brands already integrated with ESPhome can be added easily.**
|
||||
|
||||
## Supported ESP32
|
||||
## Supported balancers
|
||||
|
||||
**Recommended: AtomS3 or ESP32-S3**
|
||||
* `GW-24S4EB: NEEY/Heltec 4A Smart Active Balancer)` (BLE)
|
||||
* `GW-24S4EB: NEEY 4A Smart Active Balancer 4th generation)` (BLE)
|
||||
* `EK-24S15EB: (NEEY 15A Smart Active Balancer)` (BLE)
|
||||
* `EK-24S10EB: (NEEY 10A Smart Active Balancer)` (BLE)
|
||||
|
||||
* [M5Stack AtomS3 dedicated documentation](Supported_devices_M5Stack_AtomS3.md)
|
||||
* [PVbrain2 with ESP32-S3](https://github.com/SeByDocKy/pvbrain2) (up to 11 BMS monitored with `UART`)
|
||||
* [Build your own PCB with ESP32 or ESP32-S3](Supported_devices_Build_your_own_PCB.md)
|
||||
**Note: other Balancer brands already integrated with ESPhome can be added easily.**
|
||||
|
||||
| [AtomS3 Lite](https://docs.m5stack.com/en/core/AtomS3%20Lite) | [AtomS3](https://docs.m5stack.com/en/core/AtomS3) | [AtomS3R (8MB PSRAM)](https://docs.m5stack.com/en/core/AtomS3R) |
|
||||
## Supported MCU
|
||||
|
||||
This project works with various `ESP32` variants and also with the `Raspberry Pi Pico (RP2040)`.
|
||||
Note that merging data from multiple BMS, balancers and shunts is resource-intensive, so I highly recommend a board based on the `ESP32-S3` with `PSRAM`.
|
||||
|
||||
| [AtomS3 Lite](Board_M5Stack_AtomS3.md) | [AtomS3](Board_M5Stack_AtomS3.md) | [AtomS3R (8MB PSRAM)](Board_M5Stack_AtomS3.md) |
|
||||
| --- | --- | --- |
|
||||
| <img src="../../images/MCU_AtomS3_Lite.png" width="300"> | <img src="../../images/MCU_AtomS3.png" width="300"> | <img src="../../images/MCU_AtomS3R.png" width="300"> |
|
||||
|
||||
| [LilyGo T-CAN485 (ESP32)](https://github.com/Xinyuan-LilyGO/T-CAN485) | [LilyGo T-Connect (ESP32-S3)](https://github.com/Xinyuan-LilyGO/T-Connect) | [Waveshare ESP32-S3-RS485-CAN](https://www.waveshare.com/esp32-s3-rs485-can.htm) |
|
||||
| [LilyGo T-CAN485 (ESP32)](https://github.com/Xinyuan-LilyGO/T-CAN485) | [LilyGo T-Connect (ESP32-S3)](Board_LilyGo_T-Connect.md) | [Waveshare ESP32-S3-RS485-CAN](Board_Waveshare_ESP32-S3-RS485-CAN.md) |
|
||||
| --- | --- | --- |
|
||||
| <img src="../../images/MCU_ESP32_LilyGo-T-CAN485.jpg" width="300"> | <img src="../../images/MCU_ESP32-S3_LilyGo-T-Connect.jpg" width="300"> | <img src="../../images/MCU_ESP32-S3_WS-RS485-CAN.png" width="300"> |
|
||||
| <img src="../../images/MCU_ESP32_LilyGo-T-CAN485.jpg" width="300"> | <img src="../../images/MCU_ESP32-S3_LilyGo-T-Connect_1.jpg" width="300"> | <img src="../../images/MCU_ESP32-S3_WS-RS485-CAN_1.png" width="300"> |
|
||||
|
||||
| [ESP32 DevKit-V1](https://a.aliexpress.com/_EG12CJ2) | [ESP32-S3 DevKitC-1](https://a.aliexpress.com/_EzFdrw3) | [ESP32-C3 ETH01-EVO](https://a.aliexpress.com/_Ey29fog) |
|
||||
| [ESP32 DevKit-V1](Board_Build_your_own_PCB.md) | [ESP32-S3 DevKitC-1](Board_Build_your_own_PCB.md) | [ESP32-C3 ETH01-EVO](https://a.aliexpress.com/_Ey29fog) |
|
||||
| --- | --- | --- |
|
||||
| <img src="../../images/MCU_ESP32-DevKit-V1.jpg" width="300"> | <img src="../../images/MCU_ESP32-S3-DevKitC-1.png" width="300"> | <img src="../../images/MCU_ESP32-C3_ETH01-EVO.png" width="300"> |
|
||||
|
||||
@@ -73,7 +80,7 @@ Inverters supporting CAN PYLON/Goodwe/SMA/Victron Low Voltage protocol should wo
|
||||
|
||||
The following are confirmed and known to work:
|
||||
|
||||
| Brand | Model | Satus | Reported by | Inverter bat. mode | BMS | BMS protocol | ESP32 board | CAN name | CAN protocol | CAN transceiver | RS485 board | Multi-BMS | Remarks |
|
||||
| Brand | Model | Status | Reported by | Inverter bat. mode | BMS | BMS protocol | ESP32 board | CAN name | CAN protocol | CAN transceiver | RS485 board | Multi-BMS | Remarks |
|
||||
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|
||||
| Deye | SUN-3.6K-SG03LP1-EU | Working | [@Der_Hannes](https://diysolarforum.com/members/der_hannes.16949/) | Lithium 00 | JK-B | UART | ESP32 DevKit V1 | PYLON | PYLON 1.2 | SN65HVD230 **3.3V** | --- | no | --- |
|
||||
| Deye | SUN-5K-SG03LP1-EU | Working | [@vdiex](https://github.com/vdiex) | Lithium 00 | JK-B | UART | ESP32 DevKit V1 | PYLON | PYLON 1.2 | --- | no | --- |
|
||||
@@ -112,5 +119,6 @@ The following are confirmed and known to work:
|
||||
| Victron | Multiplus 24/1200/25-16 | Working | [@dmsims](https://diysolarforum.com/members/dmsims.23417/) | CAN-bus BMS LV (500 kbit/s) | JK-B (1) | BLE | Atom S3 Lite | Automatic | Victron | [Atomic CAN base (SKU:A103)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base) | --- | no | Plugged into Cerbo Can port (must use supplied Victron terminator in the other port) |
|
||||
| MidNite Solar | MN15-12KW-AIO | Working | [@goldserve](https://diysolarforum.com/members/goldserve.52541/) | PYLON | JK-B | BLE | ESP32-S3 | Automatic | PYLON 1.2 | MCP2515 | --- | no | Stable with Victron Smartshunt, MQTT, BLE, Neopixel LED, Display also working. |
|
||||
| MidNite Solar | MN15-12KW-AIO | Working | [@jahyde](https://diysolarforum.com/members/jahyde.7475/) | PYLON | JK-PB | BLE | ESP32-S3 | Automatic | PYLON 1.2 | MCP2515 | --- | yes | --- |
|
||||
| SMA | Sunny Island | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|
||||
| SRNE | HESP48120U200-H | Working | [@ogremustcrush](https://diysolarforum.com/members/ogremustcrush.116979/) | UZE | JK-PB | RS485 | Atom S3 Lite | Automtic | PYLON V2 | [Atomic CAN Base (SKU:A103)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base) | [Isolated RS485 Unit (SKU:U094)](https://docs.m5stack.com/en/unit/iso485) | Yes | Most of the YamBMS PYLON based protocols show same results on inverter. Inverter itself does not work when it is set to PYLON protocol, but UZE works. Incorrect temp reported on inverter |
|
||||
| Studer | XTM-4000 | Working | [@kolins-cz](https://github.com/kolins-cz) | Pylontech | JK-B | UART | ESP32-S3_XIAO | PYLON | PYLON V2 | XL1051T | --- | no | DIP Switch in Xcom-CAN: 11000110 (1 to 8, ON==1) |
|
||||
| SMA | Sunny Island | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|
||||
@@ -1,56 +0,0 @@
|
||||
# YamBMS - M5Stack AtomS3, the Plug & Play solution (no welding)
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
> [!IMPORTANT]
|
||||
> AtomS3 provides very few GPIOs.
|
||||
> This solution is not the best for supervising a large number of `JK-B BMS` via `UART` but it works very well for supervising a large number of `JK-PB BMS` via `RS485`.
|
||||
|
||||
> [!TIP]
|
||||
> If you have `JK-PB BMS` (inverter BMS) and want to monitor them via `RS485`, please read the [BMS JK-PB RS485](BMS_JK-PB_RS485_solution.md) dedicated topic.
|
||||
|
||||
## Number of BMS supported
|
||||
|
||||
* 3x BMS with `Bluetooth` (BLE stack consumes significant amount of RAM on device and can cause crash and reboot)
|
||||
* 2x `JK-B` BMS with `UART/RS485` (the second UART must be soldered on the Atomic CAN base on GPIOs G7 and G8)
|
||||
* several `JK-PB` BMS with `RS485` (already tested with 7 BMS)
|
||||
|
||||
Note: these are theoretical limits, not all combinations have been tested.
|
||||
|
||||
## List of M5Stack components that can be used depending on needs
|
||||
|
||||
> [!TIP]
|
||||
> Choose an `AtomS3` to clip onto the `Atomic CAN Base`.
|
||||
> Feel free to ask your question on the [DIY solar forum](https://diysolarforum.com/threads/yambms-jk-bms-can-with-new-cut-off-charging-logic-open-source.79325/) if you don't know what to choose.
|
||||
|
||||
- [AtomS3 Lite - SKU:C124](https://docs.m5stack.com/en/core/AtomS3%20Lite)
|
||||
- [AtomS3 - SKU:C123](https://docs.m5stack.com/en/core/AtomS3)
|
||||
- [AtomS3R - SKU:C126 (8MB PSRAM)](https://docs.m5stack.com/en/core/AtomS3R)
|
||||
- [Atomic CAN Base - SKU:A103 (recommended)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base)
|
||||
- [CAN Unit - SKU:U085](https://docs.m5stack.com/en/unit/can)
|
||||
- [RS485 Unit - SKU:U094](https://docs.m5stack.com/en/unit/iso485)
|
||||
|
||||
| [AtomS3 Lite](https://docs.m5stack.com/en/core/AtomS3%20Lite) | [AtomS3](https://docs.m5stack.com/en/core/AtomS3) | [AtomS3R (8MB PSRAM)](https://docs.m5stack.com/en/core/AtomS3R) |
|
||||
| --- | --- | --- |
|
||||
| <img src="../../images/MCU_AtomS3_Lite.png" width="300"> | <img src="../../images/MCU_AtomS3.png" width="300"> | <img src="../../images/MCU_AtomS3R.png" width="300"> |
|
||||
|
||||
| [Atomic CAN Base (isolated)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base) | [CAN Unit (isolated)](https://docs.m5stack.com/en/unit/can) | [RS485 Unit (isolated)](https://docs.m5stack.com/en/unit/iso485) |
|
||||
| --- | --- | --- |
|
||||
| <img src="../../images/CAN_Transceiver_M5Stack_Atomic_CAN_Base.png" width="300"> | <img src="../../images/CAN_Transceiver_M5Stack_CAN_Unit.png" width="300"> | <img src="../../images/RS485_Transceiver_M5stack_SKU-U094_RS485_Isolated_Unit.png" width="300"> |
|
||||
|
||||
## Note regarding the sensors managing the display backlight (ili9xxx platform)
|
||||
|
||||
* **Backlight control** : manual brightness control
|
||||
* **Backlight max level** : limit the max brightness in general
|
||||
* **Backlight Autodim level** : the desired brightness when dimmed down (set to 0 to switch off screen completely instead of dimming down)
|
||||
* **Backlight Autodim time in min** : time in minutes, after the screen will dim down (set to 0 to disable Auto dimming)
|
||||
|
||||
Device will restore last screen brightness after boot, but the timer script does not get start automatically.
|
||||
The auto dim timer gets initially started by pressing the screen button (which bumps up the brightness to 100% until the timer dims down then).
|
||||
|
||||
That seems to be the easiest and lightweight solution.
|
||||
But i guess some user could be confused and expect from the device to react immediately after changing some parameters.
|
||||
@@ -105,7 +105,13 @@ So just one of the packages below :
|
||||
### ESP32-S3 DevKitC-1
|
||||
|
||||
```YAML
|
||||
device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
|
||||
# RGB LED to GPIO 38
|
||||
device_board: !include packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml
|
||||
```
|
||||
|
||||
```YAML
|
||||
# RGB LED to GPIO 48
|
||||
device_board: !include packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml
|
||||
```
|
||||
|
||||
### Atom S3 Lite
|
||||
@@ -151,12 +157,24 @@ This board has an `Ethernet` port and can be powered from `POE` (optional).
|
||||
```YAML
|
||||
device_board: !include packages/board/board_ESP32_LilyGo-T-CAN485.yaml
|
||||
```
|
||||
> [!NOTE]
|
||||
> The device has an integrated 120 Ohm termination resistor. If used as a node in the middle, this resistor must be removed. 
|
||||
|
||||
### ESP32-S3 LilyGo T-Connect
|
||||
|
||||
```YAML
|
||||
device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
|
||||
```
|
||||
> [!NOTE]
|
||||
> The device has an integrated 120 Ohm termination resistor. If used as a node in the middle, this resistor must be removed.
|
||||
|
||||
### ESP32-S3 LilyGo T-Connect Pro
|
||||
|
||||
```YAML
|
||||
device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect-Pro.yaml
|
||||
```
|
||||
> [!NOTE]
|
||||
> The device has an integrated 120 Ohm termination resistor. If used as a node in the middle, this resistor must be removed.
|
||||
|
||||
## YamBMS single-node example
|
||||
|
||||
@@ -184,6 +202,13 @@ This board has an `Ethernet` port and can be powered from `POE` (optional).
|
||||
bms_name: 'BMS 2'
|
||||
# other settings
|
||||
# ...
|
||||
|
||||
balancer1: !include
|
||||
file: packages/balancer/balancer_sensors_JK_NEEY_BLE.yaml
|
||||
vars:
|
||||
bms_id: '1' # must match the BMS ID
|
||||
balancer_name: 'Balancer 1'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:66
|
||||
```
|
||||
|
||||
## YamBMS multi-node RS485 modbus example
|
||||
@@ -249,6 +274,13 @@ This board has an `Ethernet` port and can be powered from `POE` (optional).
|
||||
bms_name: 'BMS 1'
|
||||
# other settings
|
||||
# ...
|
||||
|
||||
balancer1: !include
|
||||
file: packages/balancer/balancer_sensors_JK_NEEY_BLE.yaml
|
||||
vars:
|
||||
bms_id: '1' # must match the BMS ID
|
||||
balancer_name: 'Balancer 1'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:66
|
||||
```
|
||||
|
||||
### ESP32 modbus server `node3`
|
||||
@@ -305,6 +337,13 @@ As soon as you import a `Shunt` and it can be combined ([see condition](YamBMS_b
|
||||
|
||||
You can find `Shunt` import `LP` examples in the [examples/single-node](../../examples/single-node/) folder.
|
||||
|
||||
## Balancer
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You must number your `Balancer` with the same number as the `BMS` it is connected to.
|
||||
|
||||
As soon as the balancer is available/online the values `equalizing` and `balance trigger voltage` of the balancers(s) will take precedence over the BMS values.
|
||||
|
||||
## YamBMS
|
||||
|
||||
> [!TIP]
|
||||
|
||||
@@ -129,12 +129,6 @@ So just one of the packages below :
|
||||
- path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
```
|
||||
|
||||
### ESP32-S3 LilyGo T-Connect
|
||||
|
||||
```YAML
|
||||
- path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
```
|
||||
|
||||
### Atom S3 Lite
|
||||
|
||||
```YAML
|
||||
@@ -159,6 +153,44 @@ In this case you need to specify the `yambms` and `canbus` IDs to display the in
|
||||
display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
```
|
||||
|
||||
### ESP32-C3 DevKitM-1
|
||||
|
||||
```YAML
|
||||
- path: 'packages/board_ESP32-C3_DevKitM-1.yaml'
|
||||
```
|
||||
|
||||
### ESP32-C3 ETH01-EVO
|
||||
|
||||
This board has an `Ethernet` port and can be powered from `POE` (optional).
|
||||
|
||||
```YAML
|
||||
- path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
```
|
||||
|
||||
### ESP32 LilyGo T-CAN485
|
||||
|
||||
```YAML
|
||||
- path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
```
|
||||
> [!NOTE]
|
||||
> The device has an integrated 120 Ohm termination resistor. If used as a node in the middle, this resistor must be removed. 
|
||||
|
||||
### ESP32-S3 LilyGo T-Connect
|
||||
|
||||
```YAML
|
||||
- path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
```
|
||||
> [!NOTE]
|
||||
> The device has an integrated 120 Ohm termination resistor. If used as a node in the middle, this resistor must be removed.
|
||||
|
||||
### ESP32-S3 LilyGo T-Connect Pro
|
||||
|
||||
```YAML
|
||||
- path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect-Pro.yaml'
|
||||
```
|
||||
> [!NOTE]
|
||||
> The device has an integrated 120 Ohm termination resistor. If used as a node in the middle, this resistor must be removed.
|
||||
|
||||
## YamBMS [single-node](../../examples/single-node/) example
|
||||
|
||||
```YAML
|
||||
@@ -184,6 +216,13 @@ In this case you need to specify the `yambms` and `canbus` IDs to display the in
|
||||
bms_name: 'BMS 2'
|
||||
# other settings
|
||||
# ...
|
||||
|
||||
# Balancer 1
|
||||
- path: 'packages/balancer/balancer_sensors_JK_NEEY_BLE.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must match the BMS ID
|
||||
balancer_name: 'Balancer 1'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:66
|
||||
```
|
||||
|
||||
## YamBMS [multi-node](../../examples/multi-node/) RS485 modbus example
|
||||
@@ -243,6 +282,12 @@ In this case you need to specify the `yambms` and `canbus` IDs to display the in
|
||||
bms_name: 'JK-BMS 1'
|
||||
# other settings
|
||||
# ..
|
||||
# Balancer 1
|
||||
- path: 'packages/balancer/balancer_sensors_JK_NEEY_BLE.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must match the BMS ID
|
||||
balancer_name: 'Balancer 1'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:66
|
||||
```
|
||||
|
||||
### ESP32 modbus server `node3`
|
||||
@@ -297,6 +342,12 @@ As soon as you import a `Shunt` and it can be combined ([see condition](YamBMS_b
|
||||
|
||||
You can find `Shunt` import `RP` examples in the [examples/single-node](../../examples/single-node/) folder.
|
||||
|
||||
## Balancer
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You must number your `Balancer` with the same number as the `BMS` it is connected to.
|
||||
|
||||
As soon as the balancer is available/online the values `equalizing` and `balance trigger voltage` of the balancers(s) will take precedence over the BMS values.
|
||||
|
||||
## YamBMS
|
||||
|
||||
|
||||
@@ -6,18 +6,13 @@
|
||||

|
||||

|
||||
|
||||
## Shunt and BMS combination
|
||||
|
||||

|
||||
|
||||
The various counters above allow you to see what state your system is in.
|
||||
|
||||
### Shunt/BMS combine status
|
||||
|
||||

|
||||
|
||||
* **Combine Availability** : This status indicates whether the `BMS` or `Shunt` meets the conditions to be combined.
|
||||
* **Can be combined** : This status indicates whether the `BMS` or `Shunt` is currently combined.
|
||||
**Combined / Can be combined** : This status indicates whether the `BMS` or `Shunt` is currently combined.
|
||||
|
||||
In this example there are **3x BMS** and **1x BMS** is not combined (it is offline or is not sending correct data).
|
||||
|
||||
### Shunt
|
||||
|
||||
@@ -52,12 +47,21 @@ The `binary_sensor` does not only represent the state of the `charge/discharge`
|
||||
|
||||
The `errors_bitmask` should not be a condition to combine a BMS anymore, let the BMS decide if the `charge/discharge` is allowed (its alarm system takes care of that).
|
||||
|
||||
The `errors_bitmask` continues to be analyzed to send `warnings/alarms` on the CAN bus.
|
||||
The `errors_bitmask` continues to be analyzed to send `warnings/alarms` to the inverter.
|
||||
|
||||
The behavior of the `Charging Instruction` and `Discharging Instruction` sensors responsible for the instructions sent to the inverter will also be adapted. Alarm analysis will no longer be checked. If at least one BMS allows charging, charging can continue, if at least one BMS allows discharging, discharging can continue. This will also be based on the `binary_sensor` related to the state of `switchs/alarms` of the BMS.
|
||||
|
||||
If a BMS blocks charging or discharging, the permitted current is automatically reduced.
|
||||
|
||||
## External balancer
|
||||
|
||||
If an external balancer is used instead of the BMS internal one, it can be combined with the BMS.
|
||||
|
||||
Behaviour for `equalizing` and `balance trigger voltage`:
|
||||
|
||||
1) When no external balancer is present for a BMS or it is offline, the BMS values are used for `equalizing` and `balance trigger voltage`.
|
||||
2) When an external balancer is present for a BMS and it is online, the BMS sensor data for `equalizing` and `balance trigger voltage` is overwritten by the external balancer sensor data.
|
||||
|
||||
## State of Charge
|
||||
|
||||
The `SoC` is slightly manipulated before reaching `0%` or `100%`.
|
||||
|
||||
@@ -52,11 +52,28 @@ The `Float voltage` slider allows you to set the voltage used after charging is
|
||||
|
||||
The `Inverter Offset V.` slider allows you to correct the inverter charge voltage, either because it does not respect the requested value or because your inverter is far from your batteries and there is a voltage drop. This allows you to reach the target `Bulk` or `Float` charge voltage by adding an offset.
|
||||
|
||||
### Max current (%)
|
||||
### Max Requested Current
|
||||
|
||||

|
||||

|
||||
|
||||
The allowed charge or discharge current is automatically calculated based on the `OCP` values of your BMS. The `OCP` currents of the combined BMS (not in alarm) are added together and the requested current is a percentage `0~90%` of this value.
|
||||
|
||||
The required `charge/discharge current` is calculated as follows :
|
||||
|
||||
1. You define a **maximum current** that can never be exceeded
|
||||
2. YamBMS calculates the **maximum current** accepted by your BMS (total of OCP values * 0.9)
|
||||
3. The temperature-based current limiting function calculates the **maximum current** `based` on the **temperature**, the **battery capacity** and the **charging_rate_table** / **discharging_rate_table**. For further details see [Auto Temp-Based Current](Auto_temp-based_current.md).
|
||||
|
||||
The **current requested** by YamBMS will be **the lowest** of these three values.
|
||||
|
||||
## Requested Values
|
||||
|
||||

|
||||
|
||||
These 4 sensors allow you to see what is being requested of your inverter.
|
||||
|
||||
In the example below, we are in the `Float` phase at a voltage of `53.6V` and an `Inverter Offset V.` of `0.1V`. The `Requested Charge Voltage` is therefore `53.7V`.
|
||||
|
||||
The `Requested Discharge Voltage` is the `UVP + 0.2` value of your BMS multiplied by the number of cells, in this example (3V * 16).
|
||||
|
||||
### ReBulk
|
||||
|
||||
@@ -78,9 +95,9 @@ Works only with `PYLON`, `LuxPower` and `Victron` protocols.
|
||||
|
||||
## Auto functions
|
||||
|
||||
Thanks to [@MrPabloUK](https://github.com/MrPabloUK) for developing `Auto CVL`, `Auto CCL` and `Auto DCL` functions.
|
||||
Thanks to [@MrPabloUK](https://github.com/MrPabloUK) for developing `Auto CVL`, `Auto CCL`, `Auto DCL` and `Auto Temp-Based Current` functions.
|
||||
|
||||
A [reference spreadsheet](https://docs.google.com/spreadsheets/d/1UwZ94Qca-DBP5gppzKmAjbMJYZGjR4lMwZtwwQR9wWY/edit?usp=sharing) has been created that shows how the `Auto CVL, CCL & DCL` works.
|
||||
A [reference spreadsheet](https://docs.google.com/spreadsheets/d/1UwZ94Qca-DBP5gppzKmAjbMJYZGjR4lMwZtwwQR9wWY/edit?usp=sharing) has been created that shows how the `Auto CCL & DCL` works.
|
||||
|
||||
Thanks to [@GHswitt](https://github.com/GHswitt) for developing `Auto Float` function.
|
||||
|
||||
@@ -135,17 +152,48 @@ This feature might not work with all inverters as good or is not required if the
|
||||
|
||||
The voltage steps can be configured (default `0.1V`) with `Auto Float Voltage Step`. The update interval can be configured (default `3 minutes`) with `Auto Float Update Interval`.
|
||||
|
||||
## Requested Values
|
||||
## Auto EOC
|
||||
|
||||

|
||||

|
||||
|
||||
These 4 sensors allow you to see what is being requested of your inverter.
|
||||
When to use: Your battery would be full early in the day and then be idle for the rest of the day. You want to charge it slowly and have it full at a specified time, for example in the evening.
|
||||
|
||||
In the example below, we are in the `Float` phase at a voltage of `53.6V` and an `Inverter Offset V.` of `0.1V`. The `Requested Charge Voltage` is therefore `53.7V`.
|
||||
This function allows to set a target time when `Bulk` charging. It limits the `Requested Charge Current (CCL)` so the battery should reach full charge at the specified time. As the algorithm is quite simple there are some requirements for it to work correctly:
|
||||
|
||||
The `Requested Discharge Voltage` is the `UVP + 0.2` value of your BMS multiplied by the number of cells, in this example (3V * 16).
|
||||
- The time of the ESPHome device must be correct and available.
|
||||
- The `Battery Capacity` must be correct.
|
||||
- The charger/inverter can deliver the `Requested Charge Current (CCL)` over the time frame -> the sun must be shining.
|
||||
|
||||
There are some configuration options to adjust the behaviour:
|
||||
|
||||
- `Automatic EOC Current`: This switch enables or disables the function. When disabled, it will not limit the `Requested Charge Current (CCL)`.
|
||||
- `Auto EOC Target Hour`: This selects the hour of the desired target time.
|
||||
- `Auto EOC Target Minute`: This selects the minute of the desired target time.
|
||||
- `Auto EOC Correction`: This increases or decreases the `Requested Charge Current (CCL)` and allows for correcting charger/inverter differences, for example if the inverter delivers less current than requested.
|
||||
- `Auto EOC Capacity Modifier`: This allows to lower the target capacity for the calculation. If your battery `Capacity Remaining` does not reach `Battery Capacity` when 100% full, you can adjust the value here.
|
||||
- `Auto EOC Increase Stop Hours`: When nearing the target time but the charge current can not be reached, the `Requested Charge Current (CCL)` will increase until it reaches the max. charge current. To avoid this, a time frame bevor the target time can be chosen in which the current will not be increased. E.g. if this option is set to 1 hour, the `Requested Charge Current (CCL)` is 40A and the time is between `Target Hour - 1 hour` and `Target Hour`, it will stay at 40A.
|
||||
- `Auto EOC Increase Stop SoC`: Similar to `Auto EOC Increase Stop Hours`, this stops increasing the `Requested Charge Current (CCL)` when the `SoC` is equal or above the specified `SoC`.
|
||||
|
||||
The text sensor `Auto EOC Status` will show the current status of the function:
|
||||
- `Stop: Disabled`: Function is disabled or capacity not available.
|
||||
- `Stop: Float`: YamBMS currently in `Float` mode, not `Bulk`.
|
||||
- `Stop: Time not valid`: The ESPHome device time is not valid.
|
||||
- `Stop: Target time passed`: The current time is after the selected target time.
|
||||
- `Stop: Current above limit`: The required charge current is above the current charge limit.
|
||||
- `Run: Current increase stopped`: Running, but no current increase because of `Auto EOC Increase Stop Hours` or `Auto EOC Increase Stop SoC`.
|
||||
- `Run`: Working normally.
|
||||
|
||||
The sensor `Auto EOC Current` will show the calculated charging current. Note that it is filtered by an EWMA filter with a default 3 minute delay.
|
||||
That means that changes to the options or parameters are not immediately visible. This avoids that the `Requested Charge Current (CCL)` will fluctuate too much. It will show 0A when the function is disabled/stopped or there is no solution.
|
||||
|
||||
The function used to calculate the required charging current is very basic. The missing battery capacity (difference between `Battery Capacity` and `Capacity Remaining`) divided by the remaining hours. It will be updated every minute, but afterwards filtered before it is used for `Requested Charge Current (CCL)`. That means it will adapt, but not take into account any special circumstances. For example if `Auto CCL` is enabled and required, the charge current may further be limited by `Auto CCL`. The target time may then not be reached exactly. To account for this, the parameter `Auto EOC Correction` can be used to increase the overall current a little to compensate for the lower end current.
|
||||
|
||||
Here is an example when the target time is set to 18:00. Starting at 00:00, the required current increases as the battery is discharged. When the battery starts charging as the sun is up, the required current stabilizes around 14A.
|
||||
The current is increased at the end as it does not exactly hit its required charge, but at 17:30, the required current is stable because the parameter `Auto EOC Increase Stop Hours` was set to 0.5 hours, so it will not be increased anymore.
|
||||
At about 18:08 the battery is 100% after a short balancing period.
|
||||
|
||||

|
||||
|
||||
The `Requested Charge/Discharge Current` is the `OCP` value of your BMS multiplied by the `Max current` percentage, in this example (150A * 80%).
|
||||
|
||||
## Inverter Heartbeat Monitoring
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.02
|
||||
# Version : 1.1.2
|
||||
# Updated : 2025.08.14
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -96,3 +96,16 @@ packages:
|
||||
# vars:
|
||||
# bms_id: '10' # must be a number
|
||||
# bms_name: 'BMS 10'
|
||||
|
||||
# Balancer
|
||||
balancer2: !include
|
||||
file: packages/balancer/balancer_modbus_client.yaml
|
||||
vars:
|
||||
bms_id: '2' # must match the BMS ID
|
||||
balancer_name: 'Balancer 2'
|
||||
|
||||
balancer3: !include
|
||||
file: packages/balancer/balancer_modbus_client.yaml
|
||||
vars:
|
||||
bms_id: '3' # must match the BMS ID
|
||||
balancer_name: 'Balancer 3'
|
||||
@@ -0,0 +1,52 @@
|
||||
# Updated : 2025.08.14
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
substitutions:
|
||||
friendly_name : 'YamBMS Modbus Server 3' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms-modbus-server-3' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
|
||||
packages:
|
||||
|
||||
modbus: !include
|
||||
file: packages/board/board_options_itf_modbus.yaml
|
||||
vars:
|
||||
modbus_role: 'server' # client / server
|
||||
modbus_uart_id: 'uart_esp_1' # RS485 board
|
||||
|
||||
# Balancer for BMS 2
|
||||
balancer2: !include
|
||||
file: packages/balancer/balancer_modbus_JK_NEEY_BLE.yaml
|
||||
vars:
|
||||
bms_id: '2' # must match BMS ID
|
||||
balancer_name: 'NEEY 1'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:66
|
||||
|
||||
# Balancer for BMS 3
|
||||
balancer3: !include
|
||||
file: packages/balancer/balancer_modbus_JK_NEEY_BLE.yaml
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
balancer_name: 'NEEY 2'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:67
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.08.02
|
||||
# Version : 1.1.2
|
||||
# Updated : 2025.08.14
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -90,3 +90,12 @@ packages:
|
||||
# vars:
|
||||
# bms_id: '10' # must be a number
|
||||
# bms_name: 'BMS 10'
|
||||
# Balancer
|
||||
- path: 'packages/balancer/balancer_modbus_client.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must match the BMS ID
|
||||
balancer_name: 'Balancer 2'
|
||||
- path: 'packages/balancer/balancer_modbus_client.yaml'
|
||||
vars:
|
||||
bms_id: '3' # must match the BMS ID
|
||||
balancer_name: 'Balancer 3'
|
||||
@@ -0,0 +1,53 @@
|
||||
# Updated : 2025.08.14
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
substitutions:
|
||||
friendly_name : 'YamBMS Modbus Server 3' # Prefix added in front of the `entity display name`, also used to classify them.
|
||||
hostname: 'yambms-modbus-server-3' # Name of your ESPHome node registered on the IP network (DNS name, must be unique) and prefix added in front of the `entity id`.
|
||||
|
||||
packages:
|
||||
|
||||
yambms_modbus_server:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Modbus server
|
||||
- path: 'packages/board/board_options_itf_modbus.yaml'
|
||||
vars:
|
||||
modbus_role: 'server' # client / server
|
||||
modbus_uart_id: 'uart_esp_1' # RS485 board
|
||||
# Balancer for BMS 2
|
||||
- path: 'packages/balancer/balancer_modbus_JK_NEEY_BLE.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must match BMS ID
|
||||
balancer_name: 'NEEY 1'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:66
|
||||
# Balancer for BMS 3
|
||||
- path: 'packages/balancer/balancer_modbus_JK_NEEY_BLE.yaml'
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
balancer_name: 'NEEY 2'
|
||||
balancer_ble_mac_address: 11:22:33:44:55:67
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2026.01.15
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -31,10 +31,10 @@ packages:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
# Shunt sensors values
|
||||
shunt_voltage: '53.41' # V
|
||||
shunt_current: '37.5' # A
|
||||
shunt_power: '2003' # W
|
||||
shunt_soc: '86' # %
|
||||
shunt_voltage: '52.81' # V
|
||||
shunt_current: '17.5' # A
|
||||
shunt_power: '924' # W
|
||||
shunt_soc: '50' # %
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_FAKE.yaml
|
||||
@@ -48,15 +48,13 @@ packages:
|
||||
bms_current: '9.2' # A
|
||||
bms_power: '492' # W
|
||||
bms_soc: '87' # %
|
||||
bms_soh: '99' # %
|
||||
bms_soh: '98' # %
|
||||
bms_min_cell_voltage: '3.339' # V
|
||||
bms_min_voltage_cell: '2' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.341' # V
|
||||
bms_max_voltage_cell: '11' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.1' # °C
|
||||
bms_temperature_sensor_2: '21.3' # °C
|
||||
bms_temperature_sensor_3: '21.5' # °C
|
||||
bms_temperature_sensor_4: '21.7' # °C
|
||||
bms_min_temperature: '9.1' # °C
|
||||
bms_max_temperature: '9.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
@@ -81,10 +79,8 @@ packages:
|
||||
bms_min_voltage_cell: '14' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.339' # V
|
||||
bms_max_voltage_cell: '3' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.8' # °C
|
||||
bms_temperature_sensor_2: '21.6' # °C
|
||||
bms_temperature_sensor_3: '21.4' # °C
|
||||
bms_temperature_sensor_4: '21.2' # °C
|
||||
bms_min_temperature: '15.1' # °C
|
||||
bms_max_temperature: '15.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
@@ -109,10 +105,8 @@ packages:
|
||||
bms_min_voltage_cell: '7' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.336' # V
|
||||
bms_max_voltage_cell: '9' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.9' # °C
|
||||
bms_temperature_sensor_2: '22.0' # °C
|
||||
bms_temperature_sensor_3: '22.1' # °C
|
||||
bms_temperature_sensor_4: '22.2' # °C
|
||||
bms_min_temperature: '20.1' # °C
|
||||
bms_max_temperature: '20.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -35,20 +35,20 @@ packages:
|
||||
file: packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'EG4-BMS 1'
|
||||
## BMS address must start at 2 with EG4 LLV2, ID 1 is a special case and has different output.
|
||||
bms_address: 2 # BMS 1 DIP switch
|
||||
bms_address: 2 # BMS 1 modbus address
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_address: 3 # BMS 2 DIP switch
|
||||
bms_name: 'EG4-BMS 2'
|
||||
bms_address: 3 # BMS 2 modbus address
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'BMS 3'
|
||||
bms_address: 4 # BMS 3 DIP switch
|
||||
bms_name: 'EG4-BMS 3'
|
||||
bms_address: 4 # BMS 3 modbus address
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -29,7 +29,7 @@ packages:
|
||||
file: packages/bms/bms_combine_JBD_UART_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'JBD-BMS 1'
|
||||
bms_uart_id: 'uart_esp_1'
|
||||
bms_rx_timeout: '150ms'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
@@ -48,7 +48,7 @@ packages:
|
||||
file: packages/bms/bms_combine_JBD_BLE_full.yaml
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_name: 'JBD-BMS 2'
|
||||
bms_ble_mac_address: 'C8:47:8C:10:7E:AA' # Your MAC address
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -28,18 +28,17 @@ packages:
|
||||
# The sniffer represents the ESP node connected to the JK-BMS PB RS485 bus
|
||||
# If address 0x00 is not detected on the RS485 bus, the sniffer will act directly as a master BMS (mode 2, max 15 BMS)
|
||||
|
||||
# RS485 Sniffer with talk_pin (WS-RS485-CAN and other RS485 boards with a flow_control_pin)
|
||||
# sniffer1: !include
|
||||
# file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer_talk_pin.yaml
|
||||
# vars:
|
||||
# sniffer_id: 'sniffer1'
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
|
||||
# sniffer_talk_pin: ${talk_pin} # can be replaced by the GPIO number
|
||||
|
||||
sniffer1: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
|
||||
@@ -47,9 +46,6 @@ packages:
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
@@ -57,9 +53,6 @@ packages:
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
@@ -67,9 +60,6 @@ packages:
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 DIP switch
|
||||
@@ -77,9 +67,6 @@ packages:
|
||||
bms4: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 DIP switch
|
||||
@@ -87,9 +74,6 @@ packages:
|
||||
bms5: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 DIP switch
|
||||
@@ -97,9 +81,6 @@ packages:
|
||||
bms6: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 DIP switch
|
||||
@@ -107,9 +88,6 @@ packages:
|
||||
bms7: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 DIP switch
|
||||
@@ -117,9 +95,6 @@ packages:
|
||||
bms8: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 DIP switch
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -28,18 +28,17 @@ packages:
|
||||
# The sniffer represents the ESP node connected to the JK-BMS PB RS485 bus
|
||||
# If address 0x00 is not detected on the RS485 bus, the sniffer will act directly as a master BMS (mode 1, max 16 BMS)
|
||||
|
||||
# RS485 Sniffer with talk_pin (WS-RS485-CAN and other RS485 boards with a flow_control_pin)
|
||||
# sniffer1: !include
|
||||
# file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer_talk_pin.yaml
|
||||
# vars:
|
||||
# sniffer_id: 'sniffer1'
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
|
||||
# sniffer_talk_pin: ${talk_pin} # can be replaced by the GPIO number
|
||||
|
||||
sniffer1: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
|
||||
@@ -47,9 +46,6 @@ packages:
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_full.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x00' # BMS 1 DIP switch
|
||||
@@ -57,9 +53,6 @@ packages:
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_full.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x01' # BMS 2 DIP switch
|
||||
@@ -67,9 +60,6 @@ packages:
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_full.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x02' # BMS 3 DIP switch
|
||||
@@ -77,9 +67,6 @@ packages:
|
||||
bms4: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_full.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x03' # BMS 4 DIP switch
|
||||
@@ -87,9 +74,6 @@ packages:
|
||||
bms5: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_full.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x04' # BMS 5 DIP switch
|
||||
@@ -97,9 +81,6 @@ packages:
|
||||
bms6: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_full.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x05' # BMS 6 DIP switch
|
||||
@@ -107,9 +88,6 @@ packages:
|
||||
bms7: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_full.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x06' # BMS 7 DIP switch
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -28,18 +28,17 @@ packages:
|
||||
# The sniffer represents the ESP node connected to the JK-BMS PB RS485 bus
|
||||
# If address 0x00 is not detected on the RS485 bus, the sniffer will act directly as a master BMS (mode 2, max 15 BMS)
|
||||
|
||||
# RS485 Sniffer with talk_pin (WS-RS485-CAN and other RS485 boards with a flow_control_pin)
|
||||
# sniffer1: !include
|
||||
# file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer_talk_pin.yaml
|
||||
# vars:
|
||||
# sniffer_id: 'sniffer1'
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
|
||||
# sniffer_talk_pin: ${talk_pin} # can be replaced by the GPIO number
|
||||
|
||||
sniffer1: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
|
||||
@@ -47,9 +46,6 @@ packages:
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
@@ -57,9 +53,6 @@ packages:
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
@@ -67,9 +60,6 @@ packages:
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 DIP switch
|
||||
@@ -77,9 +67,6 @@ packages:
|
||||
bms4: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 DIP switch
|
||||
@@ -87,9 +74,6 @@ packages:
|
||||
bms5: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 DIP switch
|
||||
@@ -97,9 +81,6 @@ packages:
|
||||
bms6: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 DIP switch
|
||||
@@ -107,9 +88,6 @@ packages:
|
||||
bms7: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 DIP switch
|
||||
@@ -117,9 +95,6 @@ packages:
|
||||
bms8: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 DIP switch
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -25,26 +25,26 @@
|
||||
|
||||
packages:
|
||||
|
||||
seplos_modbus: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V3_RS485_modbus.yaml
|
||||
pace_modbus: !include
|
||||
file: packages/bms/bms_combine_PACE_RS485_modbus.yaml
|
||||
vars:
|
||||
seplos_modbus_uart_id: 'uart_esp_1'
|
||||
seplos_modbus_baud_rate: '19200' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
pace_modbus_uart_id: 'uart_esp_1'
|
||||
pace_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Pace BMS model here
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml
|
||||
file: packages/bms/bms_combine_PACE_RS485_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # BMS id and modbus address
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'PACE-BMS 1'
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml
|
||||
file: packages/bms/bms_combine_PACE_RS485_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '2' # BMS id and modbus address
|
||||
bms_name: 'BMS 2'
|
||||
bms_name: 'PACE-BMS 2'
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml
|
||||
file: packages/bms/bms_combine_PACE_RS485_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '3' # BMS id and modbus address
|
||||
bms_name: 'BMS 3'
|
||||
bms_name: 'PACE-BMS 3'
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -25,22 +25,17 @@
|
||||
|
||||
packages:
|
||||
|
||||
seplos_modbus1: !include
|
||||
seplos_modbus: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_modbus.yaml
|
||||
vars:
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
seplos_modbus_uart_id: 'uart_esp_1'
|
||||
seplos_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
seplos_modbus_rx_timeout: '150ms'
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'SEPLOS-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
# Required settings cannot be retrieved from BMS
|
||||
@@ -55,14 +50,26 @@ packages:
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_name: 'SEPLOS-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
bms_uart_id: uart_esp_2
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_max_charge_current: '100' # A. Used to calculate maximum charge current
|
||||
bms_max_discharge_current: '100' # A. Used to calculate maximum discharge current
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'SEPLOS-BMS 3'
|
||||
bms_address: '0x03' # BMS 2 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
|
||||
@@ -0,0 +1,73 @@
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
seplos_parser: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V3_RS485_modbus_sniffer.yaml
|
||||
vars:
|
||||
seplos_uart_id: 'uart_esp_1'
|
||||
seplos_baud_rate: '19200' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
seplos_bms_count: '3' # Seplos V3 BMS count
|
||||
seplos_update_interval: '3' # # Time in seconds, update interval for all data points
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '1'
|
||||
bms_prefix: 'bms0' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 1'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '2'
|
||||
bms_prefix: 'bms1' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 2'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml
|
||||
vars:
|
||||
bms_id: '3'
|
||||
bms_prefix: 'bms2' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 3'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.26
|
||||
# Version : 1.1.1
|
||||
# Updated : 2026.01.15
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -26,7 +26,7 @@
|
||||
shunt:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# Shunt 1
|
||||
- path: 'packages/shunt/shunt_combine_FAKE.yaml'
|
||||
@@ -34,15 +34,15 @@
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
# Shunt sensors values
|
||||
shunt_voltage: '53.41' # V
|
||||
shunt_current: '37.5' # A
|
||||
shunt_power: '2003' # W
|
||||
shunt_soc: '86' # %
|
||||
shunt_voltage: '52.81' # V
|
||||
shunt_current: '17.5' # A
|
||||
shunt_power: '924' # W
|
||||
shunt_soc: '50' # %
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
refresh: 60min
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_FAKE.yaml'
|
||||
@@ -61,10 +61,8 @@
|
||||
bms_min_voltage_cell: '2' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.341' # V
|
||||
bms_max_voltage_cell: '11' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.1' # °C
|
||||
bms_temperature_sensor_2: '21.3' # °C
|
||||
bms_temperature_sensor_3: '21.5' # °C
|
||||
bms_temperature_sensor_4: '21.7' # °C
|
||||
bms_min_temperature: '9.1' # °C
|
||||
bms_max_temperature: '9.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
@@ -88,10 +86,8 @@
|
||||
bms_min_voltage_cell: '14' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.339' # V
|
||||
bms_max_voltage_cell: '3' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.8' # °C
|
||||
bms_temperature_sensor_2: '21.6' # °C
|
||||
bms_temperature_sensor_3: '21.4' # °C
|
||||
bms_temperature_sensor_4: '21.2' # °C
|
||||
bms_min_temperature: '15.1' # °C
|
||||
bms_max_temperature: '15.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
@@ -115,10 +111,8 @@
|
||||
bms_min_voltage_cell: '7' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.336' # V
|
||||
bms_max_voltage_cell: '9' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.9' # °C
|
||||
bms_temperature_sensor_2: '22.0' # °C
|
||||
bms_temperature_sensor_3: '22.1' # °C
|
||||
bms_temperature_sensor_4: '22.2' # °C
|
||||
bms_min_temperature: '20.1' # °C
|
||||
bms_max_temperature: '20.3' # °C
|
||||
bms_max_charge_current: '100' # A
|
||||
bms_max_discharge_current: '100' # A
|
||||
bms_cell_ovp: '3.650' # V Used by 'Auto CCL' functions
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -39,18 +39,18 @@ packages:
|
||||
- path: 'packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'EG4-BMS 1'
|
||||
## BMS address must start at 2 with EG4 LLV2, ID 1 is a special case and has different output.
|
||||
bms_address: 2 # BMS 1 DIP switch
|
||||
bms_address: 2 # BMS 1 modbus address
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_address: 3 # BMS 2 DIP switch
|
||||
bms_name: 'EG4-BMS 2'
|
||||
bms_address: 3 # BMS 2 modbus address
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_EG4_LLV2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 3'
|
||||
bms_address: 4 # BMS 3 DIP switch
|
||||
bms_name: 'EG4-BMS 3'
|
||||
bms_address: 4 # BMS 3 modbus address
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -34,7 +34,7 @@ packages:
|
||||
- path: 'packages/bms/bms_combine_JBD_UART_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'JBD-BMS 1'
|
||||
bms_uart_id: 'uart_esp_1'
|
||||
bms_rx_timeout: '150ms'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
@@ -52,7 +52,7 @@ packages:
|
||||
- path: 'packages/bms/bms_combine_JBD_BLE_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_name: 'JBD-BMS 2'
|
||||
bms_ble_mac_address: 'C8:47:8C:10:7E:AA' # Your MAC address
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -33,81 +33,62 @@ packages:
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# RS485 Sniffer with talk_pin (WS-RS485-CAN and other RS485 boards with a flow_control_pin)
|
||||
# - path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer_talk_pin.yaml'
|
||||
# vars:
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: ${talk_pin} # can be replaced by the GPIO number
|
||||
# RS485 Sniffer
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml'
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 ( JK app `Device Addr.` setting )
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 ( JK app `Device Addr.` setting )
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 ( JK app `Device Addr.` setting )
|
||||
# BMS 4
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 ( JK app `Device Addr.` setting )
|
||||
# BMS 5
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 ( JK app `Device Addr.` setting )
|
||||
# BMS 6
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 ( JK app `Device Addr.` setting )
|
||||
# BMS 7
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 ( JK app `Device Addr.` setting )
|
||||
# BMS 8
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 ( JK app `Device Addr.` setting )
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -33,81 +33,62 @@ packages:
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# RS485 Sniffer with talk_pin (WS-RS485-CAN and other RS485 boards with a flow_control_pin)
|
||||
# - path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer_talk_pin.yaml'
|
||||
# vars:
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: ${talk_pin} # can be replaced by the GPIO number
|
||||
# RS485 Sniffer
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml'
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 DIP switch
|
||||
# BMS 4
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 DIP switch
|
||||
# BMS 5
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 DIP switch
|
||||
# BMS 6
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 DIP switch
|
||||
# BMS 7
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 DIP switch
|
||||
# BMS 8
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 DIP switch
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -30,23 +30,23 @@ packages:
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Seplos Modbus
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_modbus.yaml'
|
||||
# Pace Modbus
|
||||
- path: 'packages/bms/bms_combine_PACE_RS485_modbus.yaml'
|
||||
vars:
|
||||
seplos_modbus_uart_id: 'uart_esp_1'
|
||||
seplos_modbus_baud_rate: '19200' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
pace_modbus_uart_id: 'uart_esp_1'
|
||||
pace_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Pace BMS model here
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml'
|
||||
- path: 'packages/bms/bms_combine_PACE_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # BMS id and modbus address
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'PACE-BMS 1'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml'
|
||||
- path: 'packages/bms/bms_combine_PACE_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # BMS id and modbus address
|
||||
bms_name: 'BMS 2'
|
||||
bms_name: 'PACE-BMS 2'
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_bms_full.yaml'
|
||||
- path: 'packages/bms/bms_combine_PACE_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '3' # BMS id and modbus address
|
||||
bms_name: 'BMS 3'
|
||||
bms_name: 'PACE-BMS 3'
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2025.07.27
|
||||
# Version : 1.1.1
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.3
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -30,21 +30,16 @@ packages:
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Seplos Modbus 1
|
||||
# Seplos Modbus
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_modbus.yaml'
|
||||
vars:
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
seplos_modbus_uart_id: 'uart_esp_1'
|
||||
seplos_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
seplos_modbus_rx_timeout: '150ms'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_name: 'SEPLOS-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
# Required settings cannot be retrieved from BMS
|
||||
@@ -58,14 +53,25 @@ packages:
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_name: 'SEPLOS-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
bms_uart_id: uart_esp_2
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_max_charge_current: '100' # A. Used to calculate maximum charge current
|
||||
bms_max_discharge_current: '100' # A. Used to calculate maximum discharge current
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'SEPLOS-BMS 3'
|
||||
bms_address: '0x03' # BMS 2 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
|
||||
@@ -0,0 +1,75 @@
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Seplos Parser
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_modbus_sniffer.yaml'
|
||||
vars:
|
||||
seplos_uart_id: 'uart_esp_1'
|
||||
seplos_baud_rate: '19200' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
seplos_bms_count: '3' # Seplos V3 BMS count
|
||||
seplos_update_interval: '3' # # Time in seconds, update interval for all data points
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '1'
|
||||
bms_prefix: 'bms0' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 1'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '2'
|
||||
bms_prefix: 'bms1' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 2'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V3_RS485_sniffer_bms_full.yaml'
|
||||
vars:
|
||||
bms_id: '3'
|
||||
bms_prefix: 'bms2' # DON'T CHANGE THIS NAME !
|
||||
bms_name: 'SEPLOS-BMS 3'
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
|
Before Width: | Height: | Size: 408 KiB After Width: | Height: | Size: 408 KiB |
|
After Width: | Height: | Size: 2.0 MiB |
|
After Width: | Height: | Size: 189 KiB |
|
After Width: | Height: | Size: 120 KiB |
|
After Width: | Height: | Size: 398 KiB |
|
Before Width: | Height: | Size: 82 KiB After Width: | Height: | Size: 68 KiB |
|
After Width: | Height: | Size: 41 KiB |
|
After Width: | Height: | Size: 111 KiB |
|
After Width: | Height: | Size: 61 KiB |
|
Before Width: | Height: | Size: 190 KiB After Width: | Height: | Size: 177 KiB |
|
Before Width: | Height: | Size: 9.0 KiB After Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 49 KiB |
|
Before Width: | Height: | Size: 175 KiB After Width: | Height: | Size: 207 KiB |
|
After Width: | Height: | Size: 92 KiB |
|
After Width: | Height: | Size: 108 KiB |
|
Before Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 35 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 21 KiB |
|
Before Width: | Height: | Size: 265 KiB After Width: | Height: | Size: 157 KiB |
|
After Width: | Height: | Size: 58 KiB |
|
After Width: | Height: | Size: 725 KiB |
|
Before Width: | Height: | Size: 303 KiB |
@@ -0,0 +1,25 @@
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.1
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
esphome:
|
||||
# The 'devices' block will merge into the main config's 'esphome' block.
|
||||
# The ID and Name are uniquely defined by the vars passed in the main config.
|
||||
devices:
|
||||
- id: balancer_${bms_id}
|
||||
name: "${balancer_name}"
|
||||
@@ -0,0 +1,26 @@
|
||||
# Updated : 2025.08.14
|
||||
# Version : 1.1.1
|
||||
# GitHub : https://github.com/syssi/esphome-jk-bms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
substitutions:
|
||||
balancer_model: "JK NEEY"
|
||||
balancer_protocol: "BLE-Modbus"
|
||||
|
||||
packages:
|
||||
balancer_sensors: !include balancer_sensors_JK_NEEY_BLE.yaml
|
||||
balancer_combine: !include balancer_modbus_server.yaml
|
||||
@@ -0,0 +1,120 @@
|
||||
# Updated : 2025.12.23
|
||||
# Version : 1.1.2
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
substitutions:
|
||||
balancer_model: "YamBMS"
|
||||
balancer_protocol: "Modbus"
|
||||
|
||||
packages:
|
||||
sub_device: !include balancer_base_sub_device.yaml
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Component settings |
|
||||
# +--------------------------------------+
|
||||
|
||||
modbus_controller:
|
||||
- id: modbus_controller_balancer${bms_id}
|
||||
modbus_id: ${modbus_id}
|
||||
setup_priority: -10
|
||||
address: 10${bms_id}
|
||||
update_interval: 20s
|
||||
command_throttle: ${modbus_command_throttle}
|
||||
max_cmd_retries: 3
|
||||
# offline_skip_updates: 5
|
||||
on_online:
|
||||
then:
|
||||
- logger.log: "Balancer ${bms_id} modbus server back online !"
|
||||
on_offline:
|
||||
then:
|
||||
- logger.log: "Balancer ${bms_id} modbus server goes offline !"
|
||||
- lambda: |-
|
||||
id(balancer${bms_id}_online_status).publish_state(false);
|
||||
id(balancer${bms_id}_equalizing).publish_state(false);
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Component entities |
|
||||
# +--------------------------------------+
|
||||
|
||||
binary_sensor:
|
||||
# online_status
|
||||
- platform: modbus_controller
|
||||
modbus_controller_id: modbus_controller_balancer${bms_id}
|
||||
id: balancer${bms_id}_online_status
|
||||
device_id: balancer_${bms_id}
|
||||
name: "Online status"
|
||||
register_type: read
|
||||
address: 1
|
||||
trigger_on_initial_state: true
|
||||
on_state:
|
||||
then:
|
||||
- lambda: |-
|
||||
id(bms${bms_id}_var_ext_balancer_online) = x;
|
||||
# equalizing
|
||||
- platform: modbus_controller
|
||||
modbus_controller_id: modbus_controller_balancer${bms_id}
|
||||
id: balancer${bms_id}_equalizing
|
||||
device_id: balancer_${bms_id}
|
||||
name: "balancing"
|
||||
register_type: read
|
||||
address: 2
|
||||
trigger_on_initial_state: true
|
||||
on_state:
|
||||
then:
|
||||
- lambda: |-
|
||||
id(bms${bms_id}_var_ext_balancer_equalizing) = x;
|
||||
|
||||
sensor:
|
||||
# balance_trigger_voltage
|
||||
- platform: modbus_controller
|
||||
modbus_controller_id: modbus_controller_balancer${bms_id}
|
||||
id: balancer${bms_id}_balance_trigger_voltage
|
||||
device_id: balancer_${bms_id}
|
||||
name: "Balance Trigger Voltage"
|
||||
register_type: read
|
||||
address: 3
|
||||
value_type: U_WORD
|
||||
accuracy_decimals: 3
|
||||
unit_of_measurement: V
|
||||
device_class: voltage
|
||||
filters:
|
||||
- multiply: 0.001
|
||||
- or:
|
||||
- throttle: 10s
|
||||
- delta: 0.001
|
||||
on_value:
|
||||
then:
|
||||
- lambda: |-
|
||||
id(bms${bms_id}_var_ext_balancer_trigger_voltage) = x;
|
||||
# balance_starting_voltage
|
||||
- platform: modbus_controller
|
||||
modbus_controller_id: modbus_controller_balancer${bms_id}
|
||||
id: balancer${bms_id}_balance_starting_voltage
|
||||
device_id: balancer_${bms_id}
|
||||
name: "Balance Starting Voltage"
|
||||
register_type: read
|
||||
address: 4
|
||||
value_type: U_WORD
|
||||
accuracy_decimals: 3
|
||||
unit_of_measurement: V
|
||||
device_class: voltage
|
||||
filters:
|
||||
- multiply: 0.001
|
||||
- or:
|
||||
- throttle: 10s
|
||||
- delta: 0.001
|
||||
@@ -0,0 +1,60 @@
|
||||
# Updated : 2025.08.14
|
||||
# Version : 1.1.1
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
globals:
|
||||
# External balancer online
|
||||
- id: bms${bms_id}_var_ext_balancer_online
|
||||
type: bool
|
||||
restore_value: no
|
||||
initial_value: "false"
|
||||
# External balancer equalizing
|
||||
- id: bms${bms_id}_var_ext_balancer_equalizing
|
||||
type: bool
|
||||
restore_value: no
|
||||
initial_value: "false"
|
||||
# External balancer trigger voltage (V)
|
||||
- id: bms${bms_id}_var_ext_balancer_trigger_voltage
|
||||
type: float
|
||||
restore_value: no
|
||||
initial_value: '0.0'
|
||||
|
||||
modbus_controller:
|
||||
- modbus_id: ${modbus_id}
|
||||
address: 10${bms_id} # max 255 (8bit)
|
||||
server_registers:
|
||||
# online_status (1/0)
|
||||
- address: 1
|
||||
value_type: U_WORD
|
||||
read_lambda: |-
|
||||
return uint16_t(id(balancer${bms_id}_online_status).state);
|
||||
# equalizing (1/0)
|
||||
- address: 2
|
||||
value_type: U_WORD
|
||||
read_lambda: |-
|
||||
return uint16_t(id(balancer${bms_id}_equalizing).state);
|
||||
# balance_trigger_voltage (mV)
|
||||
- address: 3
|
||||
value_type: U_WORD
|
||||
read_lambda: |-
|
||||
return uint16_t(id(balancer${bms_id}_balance_trigger_voltage).state * 1000);
|
||||
# balance_starting_voltage (mV)
|
||||
- address: 4
|
||||
value_type: U_WORD
|
||||
read_lambda: |-
|
||||
return uint16_t(id(balancer${bms_id}_balance_starting_voltage).state * 1000);
|
||||