68 Commits
Author SHA1 Message Date
Sleeper85 84c90c11d3 YamBMS Remote Packages example 2025-04-01 23:24:40 +02:00
Sleeper85 3dde676dd8 YamBMS Remote Packages JK-BMS RS485 Modbus 2025-04-01 23:22:56 +02:00
Sleeper85 42151934bf JK-PB RS485 bms sensors version 2025-04-01 22:32:54 +02:00
Sleeper85 a8233ea8c6 Update yambms_remote_packages_example.yaml 2025-03-26 20:09:31 +01:00
Sleeper85 01c443e321 Create board_ESP32_Generic_3xUART.yaml 2025-03-26 20:05:37 +01:00
Sleeper85 9977cc5963 Update yambms_remote_packages_example.yaml 2025-03-24 17:17:39 +01:00
Sleeper85 f357d23751 YamBMS remote packages example 2025-03-21 21:28:15 +01:00
Sleeper85 ae276bb0eb Set min_version to 2025.3.0 2025-03-21 19:44:25 +01:00
Sleeper85 f8b677a2b8 Merge pull request #31 from shvmm/main
Update device_base.yaml remove external component PR#7547 after merge
2025-03-21 19:38:45 +01:00
Shivam Maurya 17d5edb2f0 Update device_base.yaml 2025-03-21 17:24:41 +05:30
Shivam Maurya 3de5f0e080 Merge branch 'Sleeper85:main' into main 2025-03-21 17:20:34 +05:30
Sleeper85 c4313cc577 Fixed configuration error regarding RGB LED with ESP-IDF V5 2025-03-12 22:36:33 +01:00
Sleeper85 ea1859068d Create yambms_custom.yaml 2025-03-12 12:47:56 +01:00
Sleeper85 4115a33d87 Merge pull request #33 from 20after4/olimex-evb
Board package for olimex ESP32-EVB
2025-03-09 22:30:22 +01:00
Sleeper85 4d52c3bbf8 Merge pull request #30 from ogremustcrush/main
Update Supported_devices.md to add SRNE HESP48120U200-H
2025-03-09 22:25:54 +01:00
Mukunda Modell 3f9956f4d5 Board package for olimex ESP32-EVB 2025-03-08 05:35:15 -06:00
Shivam Maurya 3127c7b3d7 Update device_base.yaml
removed external component PR#7547 after merge
2025-02-25 13:30:08 +05:30
Sleeper85 da658defd8 Update README 2025-02-20 16:43:04 +01:00
ogremustcrush 4a0f3c6090 Update Supported_devices.md to add SRNE HESP48120U200-H 2025-02-07 12:05:34 -07:00
Sleeper85 d889d091f7 T-CAN485 chips SN65HVD231DR / MAX13487E 2025-02-07 14:56:09 +01:00
Sleeper85 bb764ceb01 Merge pull request #29 from andrewfraley/patch-1
Add LilyGo T-CAN485 w/ EG4 12000XP and JBD
2025-02-07 14:52:59 +01:00
Andy Fraley 7ec5fc02ac Add afraley 12000XP 2025-02-06 21:57:28 -05:00
Sleeper85 df3d9353b6 Fixed JK-PB dashboard min/max cells coloring bug 2025-02-06 18:11:29 +01:00
Sleeper85 8777dc8688 device_class warnings fixed 2025-01-30 23:33:00 +01:00
Sleeper85 c47b768573 Merge pull request #27 from MrPabloUK/Updated-Auto-Functions
Updated Auto Functions
2025-01-29 18:12:56 +01:00
MrPabloUK e336ac315c Corrected deadband check 2025-01-29 12:20:49 +00:00
Sleeper85 56fd51e5d4 Create RS485-protocol-pylon-low-voltage-V3.3-20180821.pdf 2025-01-29 02:25:17 +01:00
Sleeper85 edd3beb0de Note regarding charging settings 2025-01-28 18:22:10 +01:00
Sleeper85 5e1d7ac48e Update JK-ALL BLE BMS YAMLs 2025-01-28 18:21:14 +01:00
Sleeper85 c552360fe0 Added JBD BMS over Bluetooth 2025-01-28 18:18:42 +01:00
MrPabloUK 088caecd47 Formatting 2025-01-28 12:33:43 +00:00
MrPabloUK af59e4307c Updated version & update date 2025-01-28 12:10:51 +00:00
MrPabloUK b303244b77 Update yambms.yaml 2025-01-28 11:57:33 +00:00
MrPabloUK 91f961fcd6 Updated Auto CCL, DCL, CVL
Updated Auto CCL, DCL and CVL functions to return a delta value instead of absolute value
2025-01-28 11:55:17 +00:00
Sleeper85 f22ab83e19 Update bms_options_charging_logic.yaml 2025-01-27 22:58:39 +01:00
Sleeper85 97f9e38031 Update bms_options_charging_logic.yaml 2025-01-27 22:11:11 +01:00
Sleeper85 b4cd402337 BMS charging logic 1.1.2 2025-01-27 22:07:25 +01:00
Sleeper85 25a2a88366 Dashboard JK-PB battery_capacity_total_setting fixed 2025-01-27 19:25:17 +01:00
Sleeper85 bdda35a837 YamBMS DEMO firmware 1.5.4 2025-01-26 20:36:10 +01:00
Sleeper85 7af47f5b2e YamBMS 1.5.4 2025-01-26 19:22:56 +01:00
Sleeper85 0fa4c61667 Force errors_bitmask to 0 for JK_RS485 component (avoid a bug) 2025-01-21 19:22:41 +01:00
Sleeper85 e9e3600686 YamBMS 1.5.3 2025-01-20 08:47:24 +01:00
Sleeper85 28323c7b29 YamBMS dashboard 1.5.3 2025-01-19 19:23:01 +01:00
Sleeper85 2cb7ba3c6d YamBMS DEMO firmware 1.5.3 2025-01-19 19:22:25 +01:00
Sleeper85 91df96d70c Don't count a uncombined BMS as blocking charge/discharge 2025-01-19 17:33:13 +01:00
Sleeper85 6d67b2677c Fix battery_capacity issue #14 2025-01-19 16:31:58 +01:00
Sleeper85 29e25e36b6 YamBMS 1.5.3 2025-01-18 06:35:01 +01:00
Sleeper85 5b36fac1b9 Merge pull request #19 from shvmm/patch-2
Update README.md to include 8MB flash size recommendation
2025-01-14 18:12:31 +01:00
Sleeper85 58d9ebc02e Merge pull request #18 from shvmm/patch-1
Create board_xiao-s3.yaml
2025-01-14 18:10:22 +01:00
Shivam Maurya 203911fc36 Update README.md to include 8MB flash size recommendation 2025-01-14 20:13:57 +05:30
Shivam Maurya 0b980a7f42 Create board_xiao-s3.yaml 2025-01-14 20:00:43 +05:30
Sleeper85 0455cba2da New packages vars name bms_address for JK-PB and SEPLOS 2025-01-07 16:44:07 +01:00
Sleeper85 cee37cd5b0 Remove logger baud_rate: 0 line 2025-01-06 21:42:17 +01:00
Sleeper85 c7b8c29fbf Update Supported_devices.md 2025-01-06 21:37:30 +01:00
Sleeper85 d7de61c675 Update of supported devices 2025-01-05 22:40:05 +01:00
Sleeper85 402d895a48 Update of supported devices 2025-01-05 22:05:20 +01:00
Sleeper85 485c6cc5fb AtomS3 display rollback to st7789v platform 2025-01-04 16:55:17 +01:00
Sleeper85 43f995a7a9 Merge branch 'main' of https://github.com/Sleeper85/esphome-yambms 2024-12-27 10:26:57 +01:00
Sleeper85 9b207b5484 Update YamBMS_behavior.md 2024-12-27 10:26:55 +01:00
Sleeper85 13d4d78123 Create FUNDING.yml 2024-12-26 11:14:52 +01:00
Sleeper85 70a00ff733 YamBMS 1.5.2 2024-12-23 22:42:35 +01:00
Sleeper85 f193e27e83 Auto CCL-DCL based on OVP-UVP 2024-12-21 15:49:21 +01:00
Sleeper85 f79aca0a22 CANBUS 2.4.1 2024-12-09 16:12:31 +01:00
Sleeper85 408ebb5116 Victron SmartShunt HowTo 2024-12-09 14:03:18 +01:00
Sleeper85 f55b2d6601 Update images 2024-11-25 17:34:25 +01:00
Sleeper85 c151f575dc Update BMS_JK-PB_RS485_solution.md 2024-11-22 16:59:43 +01:00
Sleeper85 b1c26c48dd Create Jikong BMS RS485 modbus protocol V1.1.pdf 2024-11-19 14:00:00 +01:00
Sleeper85 24b90f4bd1 Update README files 2024-11-16 21:37:30 +01:00
167 changed files with 9268 additions and 4890 deletions

No files matched your search

+1
View File
@@ -0,0 +1 @@
buy_me_a_coffee: sleeper85
File diff suppressed because it is too large. Load diff
File diff suppressed because it is too large. Load diff
File diff suppressed because it is too large. Load diff
File diff suppressed because it is too large. Load diff
+65 -7
View File
@@ -39,6 +39,36 @@
![Image](images/YamBMS_packaged_version.png "YamBMS packaged version")
### Single-node
You install `YamBMS` on a single ESP32 connected to your BMS and your inverter.
* Max 3x BMS BLE
* Max 3x BMS UART
* several RS485 BMS on the same bus
### Multi-node
Each BMS/Shunt 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.
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 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.
[You can find more information about creating your YAML in this How To.](documents/README/YamBMS_main_YAML_HowTo.md)
> [!TIP]
> If you have a lot of `BMS/Shunt` to combine, using an `ESP32-S3` or `AtomS3` for `node1` is recommended.
![Image](images/YamBMS_multi-node_RS485_modbus.png "YamBMS multi-node RS485 modbus")
## Home Assistant
![Image](images/YamBMS_HA_Dashboard.png "YamBMS HA Dashboard")
@@ -57,7 +87,7 @@
## Try YamBMS with the DEMO firmware
You can simply test the application with a `generic ESP32` without compiling and connecting anything on your ESP32.<br>
You can simply test the application with a `generic ESP32` without compiling and connecting anything on your ESP32.
The DEMO firmware is composed of `3x BMS` and `1x Shunt` (fake) for a `48V LFP` system.
> [!IMPORTANT]
@@ -76,15 +106,43 @@ rx_pin: 22 # to CAN board CRX (with 4.7K resistor except for SN65HVD230)
## Requirements
* [ESPHome 2024.6.0 or higher](https://github.com/esphome/esphome/releases)
* ESP32 MCU
* CAN Transceiver (only with TJA1050/TJA1051 : 4.7K resistor for 5V to 3V3 level shifing)
* BMS JK-B*, JK-PB* (other BMS brands already integrated with ESPhome can be added easily)
* Inverters supporting CAN PYLON/Goodwe/SMA/Victron Low Voltage protocol
* 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)
* Inverters supporting CAN PYLON/GoodWe/SMA/Victron Low Voltage protocol
* Optional: 48V to 5V DC-DC converter to power the ESP32 from the JK-BMS VBAT pin (URB4805YMD-10WR3 or VRB4805S-6WR3)
* Optional: JK RS485 adaptor and RS485 to TTL 3V3 adaptor (see schematic section)
## Changelog
* 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)
* `device_base.yaml` should no longer be part of `YamBMS_main.yaml`
* New `RGB LED status` light effects (red, green, blue, cyan) as an `options` packages for `board.yaml`
* Increased CPU frequency to `240Mhz` as an `options` packages for `board.yaml`
* Added `ESP32 Generic`, `LilyGo T-CAN485`, `LilyGo T-Connect` and `XIAO` boards
* Fixed SoC logic (low SoC will be detected at BMS level and no longer at YamBMS level)
* Simplified combination logic (removal of the combine switch) + dashboard update
* Check `Battery Capacity` is `> 0` before combining info (see [issue #14](https://github.com/Sleeper85/esphome-yambms/issues/14))
* Improved alarm logic with a common `YamBMS errors bitmask` for all BMS models (see OTP vs UTP bug reported by @ChrisG)
* 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`
* Logger `baud_rate: 0` by default (frees the 3rd UART and avoids some bugs like "WK2168 with canbus" or "BLE client with RS485 modbus")
* Changed names of `bms` and `shunt` YAMLs for modbus `multi-node` solution
* Added shared configuration file to simplify main YAML (centralization of parameters)
* 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.
@@ -117,6 +175,6 @@ rx_pin: 22 # to CAN board CRX (with 4.7K resistor except for SN65HVD230)
## References
* Thanks to [@syssi](https://github.com/syssi/esphome-jk-bms) for help and making the original JK-B UART and BLE code.
* Thanks to [@txubelaxu](https://github.com/txubelaxu/esphome-jk-bms) for help and making the original JK-PB RS485 code.
* 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.
+227
View File
@@ -0,0 +1,227 @@
# Updated : 2025.04.01
# Version : 1.5.4
# 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>.
logger:
level: INFO # VERBOSE / DEBUG / INFO / WARN
ota:
platform: esphome
api:
reboot_timeout: 0s
# Don't forget to configure your WiFi credentials in the secrets.yaml file
#
# 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
# +--------------------------------------+
# | Global Settings |
# +--------------------------------------+
substitutions:
name: yambms # ESP32 name / hostname
# +--------------------------------------+
# | 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'
# Maximum charging cycles is used to calculate the battey SOH, LF280K v3 =8000.0, LF280K v2 =6000.0, LF280=3000.0 (decimal is required)
yambms_max_cycles: '6000.0'
# +--------------------------------------+
# | 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)
# +--------------------------------------+
# | Packages |
# +--------------------------------------+
packages:
############### >>> UNCOMMENT YOUR BOARD <<< ###############
############### >>> ONLY ONE BOARD ! <<< ###############
board:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
# - path: 'packages/board/board_ESP32-S3_DevKitC-1.yaml'
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
- path: 'packages/board/board_ESP32-S3_AtomS3.yaml'
vars:
display_auto_next_page_interval: '5s'
# - path: 'packages/board/board_ESP32-S3_AtomS3R.yaml'
# vars:
# display_auto_next_page_interval: '5s'
############################################################
bms:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
# RS485 Sniffer
- path: 'packages/bms/bms_combine_JK-PB_RS485_sniffer.yaml'
vars:
sniffer_id: 'sniffer1'
sniffer_protocol: 'JK02_32S'
sniffer_uart_id: 'uart_esp_1'
# BMS 1
- path: 'packages/bms/bms_combine_JK-PB_RS485_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-PB_RS485_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-PB_RS485_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-PB_RS485_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-PB_RS485_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-PB_RS485_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-PB_RS485_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
yambms:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
- path: 'packages/yambms/yambms.yaml'
# - path: 'packages/yambms/yambms_custom.yaml'
# Custom Local YAML
# yambms_custom: !include yambms_custom.yaml
canbus1:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
- path: 'packages/yambms/yambms_canbus.yaml'
vars:
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
canbus_light_id: 'esp_light'
# The CANBUS link will be considered down if no response from the inverter (ID 0x305) for 5s
# The Deye inverter sends the ACK (can_id 0x305) only when it receives the can_id 0x356
canbus_link_timer: '5s'
# +--------------------------------------+
# | DEBUG ( logger level must be DEBUG ) |
# +--------------------------------------+
debug:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
- path: packages/base/device_debug_ESP32.yaml
vars:
debug_name: 'Debug'
debug_update_interval: '5s'
+174
View File
@@ -0,0 +1,174 @@
# Updated : 2025.04.01
# Version : 1.5.4
# 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>.
# esp32:
# framework:
# type: esp-idf
# version: 4.4.8
# platform_version: 5.4.0
logger:
level: INFO # VERBOSE / DEBUG / INFO / WARN
ota:
platform: esphome
api:
reboot_timeout: 0s
# Don't forget to configure your WiFi credentials in the secrets.yaml file
#
# 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
# +--------------------------------------+
# | Global Settings |
# +--------------------------------------+
substitutions:
name: yambms # ESP32 name / hostname
# +--------------------------------------+
# | 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'
# Maximum charging cycles is used to calculate the battey SOH, LF280K v3 =8000.0, LF280K v2 =6000.0, LF280=3000.0 (decimal is required)
yambms_max_cycles: '6000.0'
# +--------------------------------------+
# | 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)
# +--------------------------------------+
# | Packages |
# +--------------------------------------+
packages:
############### >>> UNCOMMENT YOUR BOARD <<< ###############
############### >>> ONLY ONE BOARD ! <<< ###############
board:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
- path: 'packages/board/board_ESP32_DevKit-V1.yaml'
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
# - path: 'packages/board/board_ESP32-S3_DevKitC-1.yaml'
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml'
# vars:
# display_auto_next_page_interval: '5s'
# - path: 'packages/board/board_ESP32-S3_AtomS3R.yaml'
# vars:
# display_auto_next_page_interval: '5s'
############################################################
bms:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
- path: 'packages/bms/bms_combine_JK-B_UART_full.yaml'
vars:
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_uart_id: 'uart_esp_1'
- path: 'packages/bms/bms_combine_JK-B_UART_full.yaml'
vars:
bms_id: '2' # must be a number
bms_name: 'JK-BMS 2'
bms_uart_id: 'uart_esp_2'
yambms:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
- path: 'packages/yambms/yambms.yaml'
# - path: 'packages/yambms/yambms_custom.yaml'
# Custom Local YAML
# yambms_custom: !include yambms_custom.yaml
canbus1:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
- path: 'packages/yambms/yambms_canbus.yaml'
vars:
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
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'
# +--------------------------------------+
# | DEBUG ( logger level must be DEBUG ) |
# +--------------------------------------+
debug:
url: https://github.com/Sleeper85/esphome-yambms
ref: main
refresh: 0s
files:
- path: packages/base/device_debug_ESP32.yaml
vars:
debug_name: 'Debug'
debug_update_interval: '5s'
+5 -32
View File
@@ -19,34 +19,7 @@
## Galvanic isolation of the `UART-TTL` connection
> [!CAUTION]
> `V1` and `V2` must be isolated and cannot come from the same source. `V1` (JK GPS port side) can be powered by the `3V3` of the ESP32 via a `DC-DC isolator` (**B0303S = 3V3-to-3V3**), `V2` (ESP32 side) is powered directly by the `3V3` of the ESP32.
```
┌────────────┐ | ┌──────────┐ ┌───────────┐
│ | └─3V3--V1>│ |<V2---3V3---<| |
│ DEVICE │<RX-------AO<│ UART-TTL │<AI-------TX<| ESP32 |
│ JK BMS │>TX-------AI>│ ISOLATOR │>BO-------RX>| |
│ │<----GND---->│ │<----GND---->| |
└────────────┘ └──────────┘ └───────────┘
```
Here are some components available on the market allowing you to set up galvanic isolation. The `UART-TTL isolator 2` seems a little better isolated with more space below the chip.
* [UART-TTL isolator 1](https://a.aliexpress.com/_EuXszn7)
* [UART-TTL isolator 2](https://a.aliexpress.com/_EItDRvX)
* [UART-TTL isolator](https://a.aliexpress.com/_EItDRvX)
![Image](../../images/UART-TTL_isolator_1.png "UART-TTL isolator example")
| [UART-TTL isolator](https://a.aliexpress.com/_EItDRvX) | [DC-DC isolator](https://a.aliexpress.com/_EIsPAoh) |
| --- | --- |
| <img src="../../images/UART-TTL_isolator_2.png" width="400"> | <img src="../../images/DC-DC_3V3-to-3V3_isolator.png" width="400"> |
### Another solution would be the use of M5Stack's isolated RS485 unit.
| [M5Stack RS485 unit (isolated)](https://docs.m5stack.com/en/unit/iso485) |
| --- |
| <img src="../../images/RS485_Transceiver_M5stack_SKU-U094_RS485_Isolated_Unit.png" width="400"> |
> [Please read this page about setting up galvanic isolation of the `UART-TTL` connection.](Galvanic_isolation.md)
### Atom S3 (ESP32-S3)
@@ -143,10 +116,10 @@ The `GPS` port sometimes called `RS485` is not an `RS485` port but `3V3 UART-TTL
│ O O O O │
│GND RX TX VBAT│
└────────────────┘
│ │ │ | VBAT is full battery volatge eg 51.2V (possible to use it via an isolated DC-DC converter)
│ │ └──── to TTL-isolator AI (input)
│ └──────── to TTL-isolator AO (output)
└──────────── to TTL-isolator GND
│ │ │ └ VBAT is full battery volatge eg 51.2V (possible to use it via an isolated DC-DC converter)
│ │ └──── TX to TTL-isolator AI (input)
│ └──────── RX to TTL-isolator AO (output)
└──────────── GND to TTL-isolator GND
```
The UART-TTL (labeled as `GPS`) socket of the BMS can be attached to any UART pins of the ESP.<br>
+15 -59
View File
@@ -10,64 +10,24 @@
[JK_RS485](https://github.com/txubelaxu/esphome-jk-bms/blob/main/components/jk_rs485_bms/README.md) by [@txubelaxu](https://github.com/txubelaxu)
## ESP32 board
## Hardware
Hardware wise, [Atom S3](https://docs.m5stack.com/en/core/AtomS3) solution is easier and cleaner but [ESP32-S3 DevKitC-1](https://docs.espressif.com/projects/esp-idf/en/v5.3/esp32s3/hw-reference/esp32s3/user-guide-devkitc-1.html) has more GPIOs and PSRAM.
> [!TIP]
> This solution only requires an ESP32 with a CAN transceiver and a RS485 transceiver.
### Atom S3
You are free to choose the hardware you want, the list below are 3 easy to use examples :
- [Atom S3 - SKU:C123](https://docs.m5stack.com/en/core/AtomS3)
- [Atom S3 Lite - SKU:C124](https://docs.m5stack.com/en/core/AtomS3%20Lite)
- [Atomic CAN Base - SKU:A103](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base)
- `AtomS3` with the isolated `Atomic CAN base` and `RS485 unit`
- [`LilyGo T-Connect`, ESP32-S3 with 3x RS485 and 1x CAN](https://github.com/Xinyuan-LilyGO/T-Connect)
- [`LilyGo T-CAN485`, ESP32 with 1x RS485 and 1x CAN](https://github.com/Xinyuan-LilyGO/T-CAN485)
Note: `Atom S3 Lite` does not have a display.
See the [documentation about supported hardware](Supported_devices.md).
### ESP32-S3 DevKitC-1
### M5Stack AtomS3 example (no welding)
- [ESP32-S3 N16R8](https://a.aliexpress.com/_EzFdrw3)
- [SN65HVD230 3V3 CAN transceiver](https://a.aliexpress.com/_Evq9Ra7)
The example below uses an `AtomS3` (display) with the `Atomic CAN base` and `RS485 unit`.
## RS485 unisolated board (not recommanded)
This board is the one used by [@txubelaxu](https://github.com/txubelaxu) the developer of the RS485 component for the new JK-PB series BMS.<br>
This board is certainly not the best, it does not have galvanic isolation and requires a `TALK PIN`.
![Image](../../images/RS485_Transceiver_MAX485_TALK_PIN_board.jpg "MAX485 UART-RS485")
## RS485 isolated board (recommended for making your own PCB)
This board has galvanic isolation and does not require a `TALK PIN` (this avoids having to solder a wire to the Atomic CAN base of the Atom S3).
![Image](../../images/RS485_Transceiver_isolated_high_speed_dual_board.png "ADUM3201 B0505XT TTL to RS485")
[RS485 isolated board (high speed dual)](https://a.aliexpress.com/_EueIZT5)
Note: choose the `high speed dual` version !
## M5stack RS485 isolated unit [SKU:U094] (recommended with M5stack Atom S3 solution)
If you are using M5stack solution with Atom S3, this [RS485 unit](https://docs.m5stack.com/en/unit/iso485) is the simplest solution without soldering.
![Image](../../images/RS485_Transceiver_M5stack_SKU-U094_RS485_Isolated_Unit.png "M5stack RS485 isolated unit (SKU:U094)")
## M5stack Atom S3 with CAN base and RS485 unit
If soldering or creating your own board seems complicated to you, know that it is possible to use the Atom S3 solution from M5Stack.
**Choose Atom S3 (display) or Atom S3 Lite + Atomic CAN base + RS485 unit**
- [Atom S3 - SKU:C123](https://docs.m5stack.com/en/core/AtomS3)
- [Atom S3 Lite - SKU:C124](https://docs.m5stack.com/en/core/AtomS3%20Lite)
- [Atomic CAN Base - SKU:A103](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base)
- [RS485 Isolated Unit - SKU:U094](https://docs.m5stack.com/en/unit/iso485)
| Atomic S3 Lite | Atomic CAN Base | RS485 isolated Unit |
| --- | --- | --- |
| <img src="../../images/Atom_S3_Lite.png" width="300"> | <img src="../../images/CAN_Transceiver_Atomic_CAN_Base.png" width="300"> | <img src="../../images/RS485_Transceiver_M5stack_SKU-U094_RS485_Isolated_Unit.png" width="300"> |
The example below uses an Atom S3 (display) with the CAN base and RS485 unit.
![Image](../../images/Solution_M5stack_AtomS3_CAN_base_RS485_unit.png "M5stack Atom S3 solution")
![Image](../../images/Solution_M5stack_AtomS3_CAN_base_RS485_unit.png "M5stack AtomS3 solution")
## Schematic and setup instructions
@@ -75,19 +35,15 @@ The example below uses an Atom S3 (display) with the CAN base and RS485 unit.
> Galvanic isolation of the `RS485` connection is strongly recommended.
> The diagrams below does not show the galvanic isolation of the `RS485` connection !
> [!IMPORTANT]
> The boards `uart` are configured by default with an `rx_buffer_size` of `512` which **normally** is fine for all components. Only one user reported to me an instability problem with his `Atom S3` which he solved by increasing the `rx_buffer_size` to `1024`, this user is also the only one currently using the isolated RS485 unit of M5Stack.
> If you encounter a similar problem, let me know.
**Note:** the choice of RS485 board is not related to the chosen ESP32.
### Atom S3 with unisolated RS485 board
### AtomS3 with unisolated RS485 board
```
┌──────────┐ ┌───────────┐ ┌──────────┐
│ │ │ UART │<-VCC--------------5V--│ │<---5V
│ BMS │ │ TO │ │ ESP32 │
│ JK-PB │<-RJ45-P1-----B->│ RS485 │<-DI-----------TX--G1--│ ATOM S3 │
│ JK-PB │<-RJ45-P1-----B->│ RS485 │<-DI-----------TX--G1--│ Atom S3 │
│ │<-RJ45-P2-----A->│ │--RO-----------RX--G2->│ │ ┌────────────┐ ┌────────────┐
│ RS485 │ │ CONVERTER │<-DE--+ │ │--G5--TX-----CTX->| | | |
│ NETWORK │ │ │<-RE--└--TALK PIN--G8--│ │<-G6--RX-----CRX--| Atomic |<---CAN H--->| Inverter |
@@ -125,8 +81,8 @@ With mode 2, the sniffer (ESP32) will automatically take the address 0x00 and ac
## JK-PB RS485 functions
### Sniffer Broadcast changes to all BMS
### Broadcasting JK-PB settings to all BMS
![Image](../../images/YamBMS_JK-PB_RS485_Sniffer_Broadcast.png "YamBMS_JK-PB_RS485_Sniffer_Broadcast")
![Image](../../images/YamBMS_JK-PB_RS485_Sniffer_Broadcast.png "Broadcasting JK-PB settings to all BMS")
When enabled, this function synchronizes the settings of all your BMS connected to the same RS485 network as soon as you make parameter changes.
+3
View File
@@ -6,6 +6,9 @@
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
> [!NOTE]
> Please read the documentation regarding the [charging settings](YamBMS_functions.md#charging-settings).
## Charging Logic Diagram
The charging voltage and current correspond to the default values in the YAML script and can be modified.
+39
View File
@@ -0,0 +1,39 @@
# YamBMS - Galvanic isolation
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
![GitHub stars](https://img.shields.io/github/stars/Sleeper85/esphome-yambms)
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
## Galvanic isolation of the `UART-TTL` connection
> [!CAUTION]
> `V1` and `V2` (3V3 or 5V) must be isolated and cannot come from the same source. `V1` can be powered by the device or the `3V3` of the ESP32 via a `DC-DC isolator` (**B0303S = 3V3-to-3V3**), `V2` (ESP32 side) is powered directly by the `3V3` of the ESP32.
```
┌─────────────┐ ┌──────────┐ ┌───────────┐
│ | 3V3/5V--V1>│ |<V2---3V3---<| |
│ DEVICE │<RX-------AO<│ UART-TTL │<AI-------TX<| ESP32 |
│ BMS / Shunt │>TX-------AI>│ ISOLATOR │>BO-------RX>| |
│ │<----GND---->│ │<----GND---->| |
└─────────────┘ └──────────┘ └───────────┘
```
Here are some components available on the market allowing you to set up galvanic isolation. The `UART-TTL isolator 2` seems a little better isolated with more space below the chip.
* [UART-TTL isolator 1](https://a.aliexpress.com/_EuXszn7)
* [UART-TTL isolator 2](https://a.aliexpress.com/_EItDRvX)
* [DC-DC isolator](https://a.aliexpress.com/_EIsPAoh)
![Image](../../images/UART-TTL_isolator_1.png "UART-TTL isolator example")
| [UART-TTL isolator](https://a.aliexpress.com/_EItDRvX) | [DC-DC isolator](https://a.aliexpress.com/_EIsPAoh) |
| --- | --- |
| <img src="../../images/UART-TTL_isolator_2.png" width="400"> | <img src="../../images/DC-DC_3V3-to-3V3_isolator.png" width="400"> |
### Another solution would be the use of M5Stack's isolated RS485 unit.
| [M5Stack RS485 unit (isolated)](https://docs.m5stack.com/en/unit/iso485) |
| --- |
| <img src="../../images/RS485_Transceiver_M5stack_SKU-U094_RS485_Isolated_Unit.png" width="400"> |
+26 -7
View File
@@ -8,20 +8,37 @@
## Installation procedure
1. **Install ESPHome on your computer**<br>
### 1. Install ESPHome on your computer
Before you can flash your ESP32 you need to install the [ESPHome 2024.6.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)
2. **Download all YAML files to your computer**<br>
> [!TIP]
> If you are using Windows install the `setuptools` package in addition to `wheel` and `esphome`.
```bash
pip3 install setuptools
pip3 install wheel
pip3 install esphome
```
### 2. Download all YAML files to your computer
You can do this from the command line or in your preferred method.
You need to gather the following three points in the same folder. If you are compiling from your HA server use the `Samba Share` add-on so that you can copy the `packages` folder to the `esphome` folder on the HA server.
1) the `packages` folder
2) your `secrets.yaml`
3) your [custom](YamBMS_main_YAML_HowTo.md) `main.yaml`
```bash
# Clone this external component
git clone https://github.com/Sleeper85/esphome-yambms.git
cd esphome-yambms
```
3. **Enter your WiFi credentials in the secrets.yaml files**
### 3. Enter your WiFi credentials in the secrets.yaml files
```yaml
wifi_ssid: YourSSID
@@ -29,7 +46,8 @@ wifi_password: YourPassword
domain : .local
```
4. **Install the YamBMS application into your ESP32**<br>
### 4. Install the YamBMS application into your ESP32
Choose the main YAML that best suits your needs like for example `multi-bms_JK-ALL_BLE.yaml`.<br>
Validate the configuration, create a binary, upload it, and start logs.<br>
**The only YAML that needs to be checked and configured is the main one like for example `multi-bms_JK-ALL_BLE.yaml` but you can modify other YAMLs if you want.<br>
@@ -49,10 +67,11 @@ esphome run multi-bms_JK-PB_RS485_mode2.yaml
esphome run multi-bms_JK-ALL_BLE.yaml --device 192.168.x.x
```
5. **Optional but recommended: add the ESP32 in your Home Assistant server**<br>
### 5. Optional but recommended, add the ESP32 in your Home Assistant server
In Home Assistant under **" Settings > Devices and services > Add Intergration "** select ESPHome add device `yambms` if found or supply ip address of ESP32.
## ESPHome other bash command
## Other ESPHome command-line
```bash
# clean files before compiling again
@@ -87,4 +106,4 @@ uart:
rx_pin: ${rx_pin}
debug:
direction: BOTH
```
```
@@ -8,6 +8,8 @@
## Contents
1) [JK-B BMS UART (GPS port) solution](BMS_JK-B_UART_solution.md)
2) [JK-B BMS RS485 (Display port) solution](BMS_JK-B_RS485_DISPLAY_solution.md)
3) [JK-PB BMS RS485 solution](BMS_JK-PB_RS485_solution.md)
1) [Galvanic isolation](Galvanic_isolation.md)
2) [JK-B BMS UART (GPS port) solution](BMS_JK-B_UART_solution.md)
3) [JK-B BMS RS485 (Display port) solution](BMS_JK-B_RS485_DISPLAY_solution.md)
4) [JK-PB BMS RS485 solution](BMS_JK-PB_RS485_solution.md)
5) [Victron SmartShunt How To](Shunt_Victron_SmartShunt_HowTo.md)
@@ -0,0 +1,56 @@
# Victron SmartShunt How To
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
![GitHub stars](https://img.shields.io/github/stars/Sleeper85/esphome-yambms)
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
## UART : Schematic
> [!CAUTION]
> [Please read this page about setting up galvanic isolation of the `UART-TTL` connection.](Galvanic_isolation.md)
> [!TIP]
> If you are unsure about to pin order please measure the voltage between GND and VCC (5V). If you measure a positive voltage you know the position of VCC and GND!
```
┌─────────────────┐ ┌──────────┐ ┌───────────┐
│ 5V o│<----5V---V1>│ |<V2---3V3--->| |
│ Victron RX o│<---------AO<│ UART-TTL │<AI-------TX<| ESP32 |
│ SmartShunt TX o│>---------AI>│ ISOLATOR │>BO-------RX>| |
│ GND o│<----GND---->│ │<----GND---->| |
└─────────────────┘ └──────────┘ └───────────┘
# UART-TTL VE.Direct port (JST-PH 2.0mm pinch)
┌─── ─────── ────┐
│ │
│ O O O O │
│GND RX TX VCC │
└────────────────┘
│ │ │ └ 5V
│ │ └──── TX to TTL-isolator AI (input)
│ └──────── RX to TTL-isolator AO (output)
└──────────── GND to TTL-isolator GND
```
## Bluetooth : How to retrieve MAC address and encryption key
To connect to your Victron device with BLE component you must have two information :
- `mac_address` - Bluetooth mac address of device.
- `encryption_key` - AES encryption key.
Use [VictronConnect App v5.93](https://www.victronenergy.com/live/victronconnect:beta) (or later) released on 2023-08-25.
![VictronConnect App Settings page](../../images/Victron_SmartShunt_App_01_Settings.png)
![VictronConnect App Product info page](../../images/Victron_SmartShunt_App_02_ProductInfo.png)
![VictronConnect App Instant readout encryption data](../../images/Victron_SmartShunt_App_03_EncryptionData.png)
1. Open `Settings` of Device.
2. Open `Product Info` page.
3. Ensure `Instant readout via Bluetooth` is enabled.
4. Bottom of page press `SHOW` for Instant readout details Encryption data.
When connected to the device via VictronConnect App no Instant readout (Bluetooth advertising) data is generated.
+37 -15
View File
@@ -6,43 +6,61 @@
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
## Supported ESP32
**Recommended: ESP32-S3 or Atom S3**
* [M5Stack Atom S3](Supported_devices_M5Stack_Atom_S3.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)
## Supported BMS
All `JK-B` and `JK-PB` models with software@ version `>=6.0` are using the implemented protocol and should be supported.
See the [@syssi](https://github.com/syssi) [esphome-jk-bms](https://github.com/syssi/esphome-jk-bms) repository for more information.
* All `JK-B` BMS models with software version `>=6.0`, see [esphome-jk-bms](https://github.com/syssi/esphome-jk-bms)
* `JK-PB` BMS, see [esphome-jk-bms](https://github.com/txubelaxu/esphome-jk-bms/)
* `JBD` BMS, see [esphome-jbd-bms](https://github.com/syssi/esphome-jbd-bms)
* `Seplos V1 V2` BMS, see [esphome-seplos-bms](https://github.com/syssi/esphome-seplos-bms)
**Note: other BMS brands already integrated with ESPhome can be added easily.**
## Supported shunt
`Victron Smartshunt` and `Junctek KH-F`.
* `Victron Smartshunt` (UART)
* `Victron Smartshunt` (BLE)
* `Junctek KH-F` (UART/RS485)
**Note: other Shunt brands already integrated with ESPhome can be added easily.**
## Supported ESP32
**Recommended: AtomS3 or ESP32-S3**
* [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)
| [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"> |
| [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) |
| --- | --- | --- |
| <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"> |
| [espBerry + Waveshare 2-CH CAN HAT](https://copperhilltech.com/esp32-development-board-with-dual-isolated-can-bus-hat/) | [LilyGo T-CAN485 (ESP32)](https://github.com/Xinyuan-LilyGO/T-CAN485) | [LilyGo T-Connect (ESP32-S3)](https://github.com/Xinyuan-LilyGO/T-Connect) |
| --- | --- | --- |
| <img src="../../images/MCU_ESP32-DevKitC_espBerry_2-CH-CAN.png" width="300"> | <img src="../../images/MCU_ESP32_LilyGo-T-CAN485.jpg" width="300"> | <img src="../../images/MCU_ESP32-S3_LilyGo-T-Connect.jpg" width="300"> |
| [Olimex ESP32-EVB](https://github.com/OLIMEX/ESP32-EVB) |
| --- |
| <img src="../../images/MCU_ESP32-EVB.jpg" width="300">|
## Supported CAN bus transceiver
**Note: some inverters only accept a CAN bus at 3.3V in this case please choose the SN65HVD230 chip.**
| TJA1050 | TJA1051 | SN65HVD230 |
| TJA1050 (5V) | [TJA1051T (5V)](https://a.aliexpress.com/_EIdl3b5) | [SN65HVD230 (3V3)](https://a.aliexpress.com/_Evq9Ra7) |
| --- | --- | --- |
| <img src="../../images/CAN_Transceiver_TJA1050.png" width="300"> | <img src="../../images/CAN_Transceiver_TJA1051.jpg" width="300"> | <img src="../../images/CAN_Transceiver_SN65HVD230.jpg" width="300"> |
| [M5Stack Atomic CAN Base (isolated)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base) | [M5Stack CAN Unit (isolated)](https://docs.m5stack.com/en/unit/can) | MCP2515 |
| [M5Stack Atomic CAN Base (isolated)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base) | [M5Stack CAN Unit (isolated)](https://docs.m5stack.com/en/unit/can) | [MCP2515 (5V)](https://a.aliexpress.com/_EGPcjhZ) |
| --- | --- | --- |
| <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/CAN_Transceiver_MCP2515.png" width="300"> |
## Supported RS485 transceiver
| [M5Stack RS485 unit (isolated)](https://docs.m5stack.com/en/unit/iso485) | [RS485 isolated board (high speed dual)](https://a.aliexpress.com/_EueIZT5) | [RS485 Two-way Converter](https://electronics.stackexchange.com/questions/244425/how-is-this-rs485-module-working) |
| [M5Stack RS485 Unit (isolated)](https://docs.m5stack.com/en/unit/iso485) | [RS485 isolated board (high speed dual)](https://a.aliexpress.com/_EueIZT5) | [RS485 Two-way Converter](https://electronics.stackexchange.com/questions/244425/how-is-this-rs485-module-working) |
| --- | --- | --- |
| <img src="../../images/RS485_Transceiver_M5stack_SKU-U094_RS485_Isolated_Unit.png" width="300"> | <img src="../../images/RS485_Transceiver_isolated_high_speed_dual_board.png" width="300"> | <img src="../../images/RS485_Transceiver_Two-way_Converter.jpg" width="300"> |
@@ -85,8 +103,12 @@ The following are confirmed and known to work:
| LuxPower | LXP-LB-US 10K | Working | [@Henny101](https://diysolarforum.com/members/henny101.67026/) | Lithium 6 | JK-PB (2) | RS485 | ESP32-S3 DevKitC-1 | Automatic | LuxPower | SN65HVD230 | [Isolated RS485 (high speed dual)](https://a.aliexpress.com/_EueIZT5) | yes | --- |
| EG4 | 6000XP | Working | [@ChrisG](https://diysolarforum.com/members/chrisg.483/) | Lithium 2 | JK-B (2) | BLE | ESP32 DevKit V1 / ESP32-S3 DevKitC-1 | PYLON | PYLON 1.2 | MCP2515 | --- | yes | --- |
| EG4 | 6000XP (2) | Working | [@SGB](https://diysolarforum.com/members/scrotpusgobblebottom.100804/) | Lithium 6 | JK-B (1) JK-PB (1) | BLE | Atom S3 (display) | Automatic | LuxPower | [Atomic CAN base (SKU:A103)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base) | --- | yes | --- |
| EG4 | 12000XP | Working | [@andrewfraley](https://github.com/andrewfraley) | Lithium 6 | JBD | RS485 | LilyGo T-CAN485 | Automatic | LuxPower | T-CAN485 (SN65HVD231DR) | T-CAN485 (MAX13487E) | no | set UART baud to 9600 |
| EG4 | 18kPV | Working | [@Maintman](https://diysolarforum.com/members/maintman.19007/) | Lithium 6 | JK-B | BLE | ESP32 DevKit V1 | Automatic | LuxPower | MCP2515 | --- | yes | Connected via Bluetooth to Victron SmartShunt. |
| Victron | MultiPlus-II 48/10000/140 | Working | [@cali-clim](https://diysolarforum.com/members/cali-clim.54284/) | CAN-bus BMS LV (500 kbit/s) | JK-PB (2) | RS485 | Atom S3 (display) | Automatic | Victron | [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 | --- |
| Victron | MultiPlus-II 48/10000/140 | Working | [@20after4](https://github.com/20after4) | CAN-bus BMS LV (500 kbit/s) | JBD-BMS (2) | BLE | Olimex ESP32-EVB | Automatic | Victron | SIT1050T (Integrated) | --- | yes | Works well with the integrated Ethernet and CANBus hardware |
| 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 |
@@ -6,12 +6,13 @@
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
> [!IMPORTANT]
> BMS monitoring with `UART` or `RS485` is recommended.
## Number of BMS supported
**Warning:** BMS monitoring with `UART` or `RS485` is recommended, however, if you want to monitor your BMS with `Bluetooth`, please choose an `ESP32-S3`.
* 3x BMS with `Bluetooth` (BLE stack consumes significant amount of RAM on device and can cause crash and reboot)
* 3x `JK-B` BMS with `UART`
* 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)
Note: these are theoretical limits, not all combinations have been tested.
@@ -22,8 +23,12 @@ It would be possible to add one or more [WK2168 4x UART expander](https://esphom
## Build your own PCB
This is an example of an ESP32 DevKit V1 30 pin board powered by the BMS.
> [!CAUTION]
> The `GND` of the `JK-B GPS port` is directly connected with the `B-` of your battery. Even if your BMS is in protection or stopped you can measure the `full voltage` between this `GND` and `B+`. This therefore presents a risk of `bypass` of the BMS `P-` and can be dangerous if the GND of your ESP32 is connected to the GND of your inverter or a measurement shunt for example.
> I therefore strongly advise you to achieve [galvanic isolation](BMS_JK-B_UART_solution.md#galvanic-isolation-of-the-uart-ttl-connection) between your ESP32 and the `UART-TTL` of the `JK-B GPS port`.
This is an example of an `ESP32 DevKit V1` 30 pin board powered by the `JK-B` BMS. **This example uses an RS485 board for the `multi-node` solution which is not mandatory.**
![Image](../../images/PCB_ESP32_JK-BMS-CAN_powered_by_JK-BMS.png "PCB ESP32 JK-BMS-CAN powered by JK-BMS")
![Image](../../images/PCB_ESP32_JK-BMS-CAN_Prototype.jpg "PCB ESP32 JK-BMS-CAN powered by JK-BMS")
![Image](../../images/PCB_ESP32_JK-BMS-CAN_Prototype.png "PCB ESP32 JK-BMS-CAN powered by JK-BMS")
@@ -0,0 +1,56 @@
# YamBMS - M5Stack AtomS3, the Plug & Play solution (no welding)
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
![GitHub stars](https://img.shields.io/github/stars/Sleeper85/esphome-yambms)
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
> [!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.
@@ -1,38 +0,0 @@
# YamBMS - M5Stack Atom S3 (ESP32-S3FN8)
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
![GitHub stars](https://img.shields.io/github/stars/Sleeper85/esphome-yambms)
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
## Number of BMS supported
**Warning:** Atom S3 provides very few GPIOs without UART expander. BMS monitoring with `UART` or `RS485` is recommended.
* 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` (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.
## UART/IO Expander
Theoretically, with the 4 GPIOs available, it would be possible to add one [WK2168 4x UART expander](https://esphome.io/components/weikai.html) for a total of 4x `JK-B` BMS monitored with `UART`.
## M5Stack Atom CAN Kit (the Plug & Play solution)
> [!IMPORTANT]
> If you have JK-PB series BMS (inverter BMS) and want to monitor them via RS485, please read the [README](BMS_JK-PB_RS485_solution.md) dedicated to this topic.
If soldering or creating your own board seems complicated to you, know that it is possible to use the Atom CAN Kit from M5Stack.<br>
**Choose Atom S3 (display) or Atom S3 Lite + Atomic CAN base.**
- [Atom S3 - SKU:C123](https://docs.m5stack.com/en/core/AtomS3)
- [Atom S3 Lite - SKU:C124](https://docs.m5stack.com/en/core/AtomS3%20Lite)
- [Atomic CAN Base - SKU:A103](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base)
| Atomic S3 Lite | Atomic CAN Base |
| --- | --- |
| <img src="../../images/Atom_S3_Lite.png" width="450"> | <img src="../../images/CAN_Transceiver_M5Stack_Atomic_CAN_Base.png" width="450"> |
+26 -17
View File
@@ -23,23 +23,28 @@ The various counters above allow you to see what state your system is in.
Combine condition :
1) the `Combine` switch is enabled
2) the `Voltage` supplied by the shunt is `> 0V`
2) Shunt `Online Status` is `ON` (the shunt `Voltage` is `> 0`)
If one of these two conditions is not respected, the shunt is automatically decombined.
If one of these two conditions is not respected, the shunt is automatically uncombined.
> [!IMPORTANT]
> In RS485 modbus `multi-node`, if a server does not respond (cable or hardware failure) the `Online Status` of the shunt will be set to `OFF` and it will be uncombined.
As soon as you import a `Shunt` and it can be combined (see condition) the values ​​`Voltage`, `Current`, `Power` and `SoC` of the shunt(s) will take precedence over the BMS values.
> [!TIP]
> [!NOTE]
> If all BMS are `uncombined` the shunt data will no longer be published.
### BMS
Combine condition :
1) the `Combine` switch is enabled
2) BMS `Online Status` is `ON` (to detect a loss of connection with the BMS e.g. cable, BMS OFF or dead)
3) BMS `Charging` or `Discharging` is allowed (based on `binary_sensor`, related to the state of `switches/alarms`)
1) BMS `Online Status` is `ON / Connected` (to detect a loss of connection with the BMS e.g. cable, BMS OFF or dead)
2) The BMS `Battery Capacity` is `> 0` (to ensure that the data received is correct)
If one of these three conditions is not met, the BMS is automatically decombined.
If one of these three conditions is not met, the BMS is automatically uncombined.
> [!IMPORTANT]
> In RS485 modbus `multi-node`, if a server does not respond (cable or hardware failure) the `Online Status` of the BMS will be set to `OFF` and it will be uncombined.
From YamBMS `1.5.1` :
@@ -59,11 +64,20 @@ The `SoC` is slightly manipulated before reaching `0%` or `100%`.
SoC `100%` will be sent to your inverter only when the battery is `fully charged` (useful for some inverters stopping charging when the SoC reaches 100%).
SoC behavior:
1) If `min_cell_v <= cell_uvpr` SoC 0% is sent
2) Else if `SOC < 1%` SoC 2% is sent (false 0% sending 2%)
3) Else if `SOC < 99%` real SoC is sent
4) Else if `the battery is fully charged` real SoC is sent
5) Else SoC `98%` is sent
1) If `SOC < 99%` real SoC is sent
2) Else if `the battery is fully charged` real SoC is sent
3) Else SoC `98%` is sent
## RGB LED status
This only applies to boards with an `RGB LED`.
| Color | Status |
| --- | --- |
| $${\color{red}Red}$$ | HA or MQTT KO + CANBUS KO |
| $${\color{green}Green}$$ | HA or MQTT OK + CANBUS KO |
| $${\color{blue}Flashing-Blue}$$ | HA or MQTT KO + CANBUS OK |
| $${\color{cyan}Flashing-Cyan}$$ | HA or MQTT OK + CANBUS OK |
## CAN bus link
@@ -85,9 +99,6 @@ This `5s` delay can be modified in the configuration when importing the canbus p
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
@@ -102,8 +113,6 @@ If the inverter does not respond with an `ACK 0x305` within this `5s` delay the
![Image](../../images/YamBMS_BMS_alarms.png "YamBMS_BMS_alarms")
The BMS `errors_bitmask` values ​​are merged and then analyzed continuously **even if the BMS is uncombined**.
If all BMS have alarms, the alarms are sent to the **CAN bus** as `Protection Alarms`.
If at least one BMS has no alarms, the alarms are sent to the CAN bus as `Warning`.
+4 -4
View File
@@ -101,8 +101,8 @@ You can compare `Auto CVL` to cruise control in a car.
## Auto CCL & DCL
> [!IMPORTANT]
> The `Auto CCL` function uses the `OVPR` value of your BMS which must be higher than `cell_bulk_voltage` to work properly. `e.g. for LFP` : CVL=3.45V / OVPR=3.55V / OVP=3.65V.
> The `Auto DCL` function uses the `UVPR` value of your BMS. `e.g. for LFP` : UVPR=3.00V
> The `Auto CCL` function uses the `OVP` value of your BMS.
> The `Auto DCL` function uses the `UVP` value of your BMS.
Regarding the new `Auto Charge/Discharge Current Limit`, this features has been introduced to hopefully prevent `OVP` and `UVP` alarms.
@@ -111,7 +111,7 @@ This should prevent the runner cell from exceeding the max voltage cutoff, but d
You can compare `Auto CCL` to a max speed limiter in a car.
`Auto DCL` works the same way when a cell approaching `UVPR`.
`Auto DCL` works the same way when a cell approaching `UVP + 0.2`.
Current control should work with any inverter that uses `CAN` control.
@@ -123,7 +123,7 @@ 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 `UVPR` value of your BMS multiplied by the number of cells, in this example (3V * 16).
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 `Requested Charge/Discharge Current` is the `OCP` value of your BMS multiplied by the `Max current` percentage, in this example (150A * 80%).
+220 -124
View File
@@ -6,7 +6,6 @@
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
> [!IMPORTANT]
> BMS monitoring with `Bluetooth` as well as the `Web server` are RAM-intensive components.
> Please note that enabling these components will take up a lot of memory and may decrease the stability of your ESP32.
@@ -66,7 +65,7 @@ api:
If you don't use `Home Assistant`, you can activate the `Web Server` and have access to YamBMS information and also interact with the application.
[ESPHome Web Server Componenet](https://esphome.io/components/web_server.html)
[ESPHome Web Server Component](https://esphome.io/components/web_server.html)
## Importing YamBMS packages
@@ -76,46 +75,36 @@ Package imports are done below this line:
packages:
```
## Base
In any case, you need to import the base package.
### Base for WiFi
```YAML
device_base: !include packages/base/device_base.yaml
```
### Base for Ethernet
```YAML
device_base: !include packages/base/device_base_ethernet.yaml
```
## Board
Next you need to import the package that corresponds to the `board` you are going to use.
First you need to import the package that corresponds to the `board` you are going to use.
There are other `board.yaml` not mentioned here, see in the [board](../../packages/board/) folder.
So just one of the packages below :
### ESP32 Generic
```YAML
device_board: !include packages/board/board_ESP32_Generic.yaml
```
### ESP32 DevKit-V1
```YAML
device_board: !include packages/board/board_esp32-devkit-v1.yaml
device_board: !include packages/board/board_ESP32_DevKit-V1.yaml
```
### ESP32-S3 DevKitC-1
```YAML
device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
```
### Atom S3 Lite
```YAML
device_board: !include packages/board/board_atom-s3-lite.yaml
device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
```
### Atom S3 / S3R (display)
@@ -124,26 +113,22 @@ In this case you need to specify the `yambms` and `canbus` IDs to display the in
```YAML
device_board: !include
file: packages/board/board_atom-s3.yaml
file: packages/board/board_ESP32-S3_AtomS3.yaml
vars:
yambms_id: 'yambms1'
canbus_id: 'canbus1'
display_auto_next_page_interval: '5s'
```
```YAML
device_board: !include
file: packages/board/board_atom-s3r.yaml
file: packages/board/board_ESP32-S3_AtomS3R.yaml
vars:
yambms_id: 'yambms1'
canbus_id: 'canbus1'
display_auto_next_page_interval: '5s'
```
### ESP32-C3 DevKitM-1
```YAML
device_board: !include packages/board_esp32-c3-devkitm-1.yaml
device_board: !include packages/board_ESP32-C3_DevKitM-1.yaml
```
### ESP32-C3 ETH01-EVO
@@ -151,54 +136,169 @@ In this case you need to specify the `yambms` and `canbus` IDs to display the in
This board has an `Ethernet` port and can be powered from `POE` (optional).
```YAML
device_board: !include packages/board/board_esp32-c3-eth01-evo.yaml
device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
```
## BMS
The example YAMLs are just examples, you can mix different BMS models without problems.
There are other `bms.yaml` not mentioned here, see in the [bms](../../packages/bms/) folder.
The `full` / `standard` versions contain all available sensors while the `minimal` version contains the basic sensors without the voltages of each cell and other superfluous sensors.
### Multi-BMS example
### ESP32 LilyGo T-CAN485
```YAML
device_board: !include packages/board/board_ESP32_LilyGo-T-CAN485.yaml
```
### ESP32-S3 LilyGo T-Connect
```YAML
device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
```
## YamBMS single-node example
```YAML
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
shunt1: !include
file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml
vars:
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
# other settings
# ...
bms1: !include
file: packages/bms/bms_model.yaml
file: packages/bms/bms_combine_JK-B_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
# other settings
# ...
bms2: !include
file: packages/bms/bms_model.yaml
file: packages/bms/bms_combine_JBD_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# BMS vars
bms_id: '2' # must be a number
bms_name: 'BMS 2'
# other settings
# ...
```
## YamBMS multi-node RS485 modbus example
> [!IMPORTANT]
> The BMS/Shunt IDs of the `modbus client` must match exactly with the BMS/Shunt IDs of the `modbus server` as in the example below.
### YamBMS modbus client `node1`
```YAML
# Config : this YAMLs contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
config_multinode_modbus: !include packages/config/config_multi-node_modbus.yaml
modbus: !include
file: packages/base/device_modbus.yaml
vars:
modbus_role: 'client' # client / server
modbus_uart_id: 'uart_esp_1' # RS485 board
shunt1: !include
file: packages/shunt/shunt_combine_modbus_client.yaml # a Shunt connected to a node of the RS485 bus
vars:
shunt_id: '1' # must be a number, also represents the modbus server number (200 + shunt_id) !
shunt_name: 'Shunt 1'
bms1: !include
file: packages/bms/bms_combine_modbus_client.yaml # a BMS connected to a node of the RS485 bus
vars:
bms_id: '1' # must be a number, also represents the modbus server number !
bms_name: 'BMS 1'
bms2: !include
file: packages/bms/bms_combine_modbus_client.yaml # a BMS connected to a node of the RS485 bus
vars:
bms_id: '2' # must be a number, also represents the modbus server number !
bms_name: 'BMS 2'
bms3: !include
file: packages/bms/bms_combine_modbus_client.yaml # a BMS connected to a node of the RS485 bus
vars:
bms_id: '3' # must be a number, also represents the modbus server number !
bms_name: 'BMS 3'
```
### ESP32 modbus server `node2`
```YAML
# Config : this YAMLs contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
config_multinode_modbus: !include packages/config/config_multi-node_modbus.yaml
modbus: !include
file: packages/base/device_modbus.yaml
vars:
modbus_role: 'server' # client / server
modbus_uart_id: 'uart_esp_1' # RS485 board
shunt1: !include
file: packages/shunt/shunt_modbus_Victron_SmartShunt_UART.yaml
vars:
shunt_id: '1' # must be a number, also represents the modbus server number (200 + shunt_id) !
shunt_name: 'Shunt 1'
# other settings
# ...
bms1: !include
file: packages/bms/bms_modbus_JK-B_UART_full.yaml
vars:
bms_id: '1' # must be a number, also represents the modbus server number !
bms_name: 'BMS 1'
# other settings
# ...
```
### ESP32 modbus server `node3`
```YAML
# Config : this YAMLs contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
config_multinode_modbus: !include packages/config/config_multi-node_modbus.yaml
modbus: !include
file: packages/base/device_modbus.yaml
vars:
modbus_role: 'server' # client / server
modbus_uart_id: 'uart_esp_1' # RS485 board
bms2: !include
file: packages/bms/bms_modbus_JK-ALL_BLE_standard.yaml
vars:
bms_id: '2' # must be a number, also represents the modbus server number !
bms_name: 'BMS 2'
# other settings
# ...
bms3: !include
file: packages/bms/bms_model.yaml
file: packages/bms/bms_modbus_JK-ALL_BLE_standard.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# BMS vars
bms_id: '3' # must be a number
bms_id: '3' # must be a number, also represents the modbus server number !
bms_name: 'BMS 3'
# other settings
# ...
```
## BMS
> [!IMPORTANT]
> You must number your `BMS` in order starting with the number `1`.
> [!TIP]
> YAML files whose name starts with `bms_combine` are to be used on the main `YamBMS` node connected to your inverter, those whose name starts with `bms_modbus` are to be used on the other nodes connected to the `RS485` bus.
The example YAMLs are just examples, you can mix different BMS models without problems.
There are other `bms.yaml` not mentioned here, see in the [bms](../../packages/bms/) folder.
The `full` / `standard` versions contain all available sensors while the `minimal` version contains the basic sensors without the voltages of each cell and other superfluous sensors.
### [JK-ALL (BLE)](https://github.com/syssi/esphome-jk-bms)
> [!IMPORTANT]
@@ -208,33 +308,25 @@ The `full` / `standard` versions contain all available sensors while the `minima
```YAML
bms1: !include
file: packages/bms/bms_JK-ALL_BLE_standard.yaml
file: packages/bms/bms_combine_JK-ALL_BLE_standard.yaml # bms_modbus_JK-ALL_BLE_standard.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_ble_protocol_version: JK02_32S # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: C8:47:8C:10:7E:AA
bms_ble_protocol_version: 'JK02_32S' # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: 'C8:47:8C:10:7E:AA' # Your MAC address
```
### [JK-B (UART)](https://github.com/syssi/esphome-jk-bms)
[How to make the UART connection with the ESP32.](BMS_JK-B_UART_solution.md)
```YAML
bms1: !include
file: packages/bms/bms_JK-B_UART_full.yaml
file: packages/bms/bms_combine_JK-B_UART_full.yaml # bms_modbus_JK-B_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_esp_1
bms_uart_id: 'uart_esp_1'
```
### [JK-B (RS485 DISPLAY)](https://github.com/syssi/esphome-jk-bms)
@@ -244,18 +336,15 @@ The `full` / `standard` versions contain all available sensors while the `minima
> The missing information has been added in the code by fixed values.
> e.g. it's not possible to know if the BMS is `online` or if the BMS is `equalizing` the cells.
[How to make the RS485 connection with the ESP32.](BMS_JK-B_RS485_DISPLAY_solution.md)
```YAML
bms1: !include
file: packages/bms/bms_JK-B_RS485_DISPLAY_full.yaml
file: packages/bms/bms_combine_JK-B_RS485_DISPLAY_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_esp_1
bms_uart_id: 'uart_esp_1'
# Required settings cannot be retrieved from BMS
# These values ​​must match your BMS settings
# LFP values example
@@ -270,6 +359,8 @@ The `full` / `standard` versions contain all available sensors while the `minima
A single `RS485 bus` allows you to monitor up to `16` BMS.
[How to make the RS485 connection with the ESP32.](BMS_JK-PB_RS485_solution.md)
#### JK-PB sniffer
> [!IMPORTANT]
@@ -283,7 +374,7 @@ Sniffer without `talk_pin` :
```YAML
sniffer1: !include
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
file: packages/bms/bms_combine_JK-PB_RS485_sniffer.yaml
vars:
sniffer_id: 'sniffer1'
sniffer_protocol: 'JK02_32S'
@@ -294,7 +385,7 @@ If your `RS485` board requires a `talk_pin` you must specify which `GPIO` will b
```YAML
sniffer1: !include
file: packages/bms/bms_JK-PB_RS485_sniffer_talk_pin.yaml
file: packages/bms/bms_combine_JK-PB_RS485_sniffer_talk_pin.yaml
vars:
sniffer_id: 'sniffer1'
sniffer_protocol: 'JK02_32S'
@@ -307,35 +398,45 @@ If your `RS485` board requires a `talk_pin` you must specify which `GPIO` will b
```YAML
# Mode2 : configure the DIP switches of your BMS from 0x01 to 0x0F (don't use the 0x00 address, maximum 15 BMS)
bms1: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_rs485_address: '0x01' # BMS 1 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x01' # BMS 1 DIP switch
```
### [JBD (UART)](https://github.com/syssi/esphome-jbd-bms)
```YAML
bms1: !include
file: packages/bms/bms_JBD_UART_full.yaml
file: packages/bms/bms_combine_JBD_UART_full.yaml # bms_modbus_JBD_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_esp_1
bms_rx_timeout: 150ms
bms_uart_id: 'uart_esp_1'
bms_rx_timeout: '150ms'
# 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
```
### [JBD (BLE)](https://github.com/syssi/esphome-jbd-bms)
```YAML
bms1: !include
file: packages/bms/bms_combine_JBD_BLE_full.yaml # bms_modbus_JBD_UART_full.yaml
vars:
bms_id: '1' # must be a number
bms_name: 'BMS 1'
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
# LFP values example
@@ -363,31 +464,27 @@ A single `RS485 bus` allows you to monitor up to `16` BMS.
```YAML
seplos_modbus1: !include
file: packages/bms/bms_SEPLOS_V1_V2_RS485_modbus.yaml
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' # Please set the baudrate of your Seplos BMS model here. It's sometimes 19200 baud instead of 9600.
seplos_modbus_rx_timeout: 150ms
seplos_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
seplos_modbus_rx_timeout: '150ms'
```
#### Seplos V1/V2 BMS
```YAML
bms1: !include
file: packages/bms/bms_SEPLOS_V1_V2_RS485_bms_full.yaml
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# Seplos modbus ID
seplos_modbus_id: 'seplos_modbus1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_rs485_address: '0x01' # BMS 1 DIP switch
bms_address: '0x01' # BMS 1 DIP switch
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
bms_update_interval: '3s' # 10s @syssi example
bms_combine_interval: '1s'
# Required settings cannot be retrieved from BMS
# These values ​​must match your BMS settings
# LFP values example
@@ -400,22 +497,26 @@ A single `RS485 bus` allows you to monitor up to `16` BMS.
## Shunt
> [!IMPORTANT]
> You must number your `Shunt` in order starting with the number `1`.
> [!TIP]
> YAML files whose name starts with `shunt_combine` are to be used on the main `YamBMS` node connected to your inverter, those whose name starts with `shunt_modbus` are to be used on the other nodes connected to the `RS485` bus.
As soon as you import a `Shunt` and it can be combined ([see condition](YamBMS_behavior.md#shunt)) the values ​​`Voltage`, `Current`, `Power` and `SoC` of the shunt(s) will take precedence over the BMS values.
### [Victron Smartshunt (UART)](https://github.com/KinDR007/VictronMPPT-ESPHOME)
[How to make the UART connection with the ESP32.](Shunt_Victron_SmartShunt_HowTo.md)
```YAML
shunt1: !include
file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_modbus_Victron_SmartShunt_UART.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# Shunt vars
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
shunt_update_interval: '3s'
shunt_combine_interval: '1s'
shunt_uart_id: uart_esp_1
shunt_uart_id: 'uart_esp_1'
```
### [Victron Smartshunt (BLE)](https://github.com/Fabian-Schmidt/esphome-victron_ble)
@@ -425,18 +526,15 @@ As soon as you import a `Shunt` and it can be combined ([see condition](YamBMS_b
> Crashes are likely to occur if you include too many additional components in your device’s configuration.
> I recommend using `UART` or `RS485` if possible.
[How to make the BLE connection with the ESP32.](Shunt_Victron_SmartShunt_HowTo.md)
```YAML
shunt1: !include
file: packages/shunt/shunt_victron_smartshunt_BLE.yaml
file: packages/shunt/shunt_combine_Victron_SmartShunt_BLE.yaml # shunt_modbus_Victron_SmartShunt_BLE.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# Shunt vars
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
shunt_update_interval: '3s'
shunt_combine_interval: '1s'
shunt_mac_address: '60:A4:23:91:8F:55'
shunt_mac_address: '60:A4:23:91:8F:55' # Your MAC address
shunt_encryption_key: '0df4d0395b7d1a876c0c33ecb9e70dcd' # Your encryption key
```
@@ -444,20 +542,18 @@ As soon as you import a `Shunt` and it can be combined ([see condition](YamBMS_b
```YAML
shunt1: !include
file: packages/shunt/shunt_junctek_khf_UART.yaml
file: packages/shunt/shunt_combine_Junctek_KHF_UART.yaml # shunt_modbus_Junctek_KHF_UART.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to send information to
# Shunt vars
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
shunt_update_interval: '3s'
shunt_combine_interval: '1s'
shunt_uart_id: uart_esp_1
shunt_uart_id: 'uart_esp_1'
```
## YamBMS
> [!TIP]
> This package is only used with the `YamBMS` main node.
> [!CAUTION]
> By default, `YamBMS` is configured with the values ​​for a 16S LFP battery !
@@ -468,8 +564,6 @@ Take the time to configure `YamBMS` correctly according to your battery chemistr
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -497,6 +591,10 @@ Take the time to configure `YamBMS` correctly according to your battery chemistr
## CAN bus
> [!TIP]
> This package is only used with the `YamBMS` main node.
> It's possible to use this package multiple times in order to send information on two different CAN bus.
The CAN bus connected to your inverter via the CAN transceiver `canbus_node1`.
You can keep the default configuration.
@@ -505,8 +603,6 @@ You can keep the default configuration.
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
@@ -0,0 +1,11 @@
# YamBMS - JK-PB BMS RS485 Solution
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
![GitHub stars](https://img.shields.io/github/stars/Sleeper85/esphome-yambms)
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
## Titre
Each shunt/bms turns into a modbus server with its own address. The max number of BMS per ESP32 (UART/BLE) is 2 but you can use one ESP32 per battery if you want.
Binary file not shown.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 441 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 387 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 371 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 223 KiB

After

Width:  |  Height:  |  Size: 239 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 600 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 500 KiB

File renamed without changes.

Before

Width:  |  Height:  |  Size: 424 KiB

After

Width:  |  Height:  |  Size: 424 KiB

File renamed without changes.

Before

Width:  |  Height:  |  Size: 423 KiB

After

Width:  |  Height:  |  Size: 423 KiB

File renamed without changes.

Before

Width:  |  Height:  |  Size: 352 KiB

After

Width:  |  Height:  |  Size: 352 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 431 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 62 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 339 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 575 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 90 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 468 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 486 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 408 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.8 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 185 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.1 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 197 KiB

After

Width:  |  Height:  |  Size: 184 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 364 KiB

After

Width:  |  Height:  |  Size: 486 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 39 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 152 KiB

After

Width:  |  Height:  |  Size: 154 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 154 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 100 KiB

+24 -39
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -66,29 +66,34 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
# device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
config_captive_portal: !include packages/config/config_captive_portal.yaml
shunt1: !include
file: packages/shunt/shunt_fake.yaml
file: packages/shunt/shunt_combine_FAKE.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Shunt vars
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
shunt_update_interval: '3s'
shunt_combine_interval: '1s'
# Shunt sensors values
shunt_voltage: '53.41' # V
shunt_current: '37.5' # A
@@ -96,15 +101,10 @@ packages:
shunt_soc: '86' # %
bms1: !include
file: packages/bms/bms_FAKE.yaml
file: packages/bms/bms_combine_FAKE.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
# BMS sensors values
bms_battery_capacity: '280' # Ah
bms_battery_capacity_remaining: '243' # Ah
@@ -128,15 +128,10 @@ packages:
bms_charging_cycles: '178' # charging cycles number Used to calculate the SoH
bms2: !include
file: packages/bms/bms_FAKE.yaml
file: packages/bms/bms_combine_FAKE.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'BMS 2'
bms_update_interval: '3s'
bms_combine_interval: '1s'
# BMS sensors values
bms_battery_capacity: '280' # Ah
bms_battery_capacity_remaining: '238' # Ah
@@ -160,15 +155,10 @@ packages:
bms_charging_cycles: '226' # charging cycles number Used to calculate the SoH
bms3: !include
file: packages/bms/bms_FAKE.yaml
file: packages/bms/bms_combine_FAKE.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '3' # must be a number
bms_name: 'BMS 3'
bms_update_interval: '3s'
bms_combine_interval: '1s'
# BMS sensors values
bms_battery_capacity: '280' # Ah
bms_battery_capacity_remaining: '232' # Ah
@@ -195,8 +185,6 @@ packages:
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -224,9 +212,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.28
# Version : 1.5.4
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -66,43 +66,42 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
# device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
bms1: !include
file: packages/bms/bms_JBD_UART_full.yaml
file: packages/bms/bms_combine_JBD_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_esp_1
bms_rx_timeout: 150ms
bms_uart_id: 'uart_esp_1'
bms_rx_timeout: '150ms'
# Required settings cannot be retrieved from BMS
# These values ​​must match your BMS settings
# LFP values example
@@ -113,17 +112,11 @@ packages:
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
bms2: !include
file: packages/bms/bms_JBD_UART_full.yaml
file: packages/bms/bms_combine_JBD_BLE_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'BMS 2'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_esp_2
bms_rx_timeout: 150ms
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
# LFP values example
@@ -137,8 +130,6 @@ packages:
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -166,9 +157,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+26 -37
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -74,63 +74,55 @@ api:
# https://esphome.io/components/ble_client.html
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
# device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
bms1: !include
file: packages/bms/bms_JK-ALL_BLE_standard.yaml
file: packages/bms/bms_combine_JK-ALL_BLE_standard.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_ble_protocol_version: JK02_32S # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: C8:47:8C:10:7E:AA
bms_ble_protocol_version: 'JK02_32S' # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: 'C8:47:8C:10:7E:AA'
bms2: !include
file: packages/bms/bms_JK-ALL_BLE_standard.yaml
file: packages/bms/bms_combine_JK-ALL_BLE_standard.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'JK-BMS 2'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_ble_protocol_version: JK02_32S # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: C8:47:8C:EE:16:EA
bms_ble_protocol_version: 'JK02_32S' # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: 'C8:47:8C:EE:16:EA'
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -158,9 +150,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+24 -35
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -66,61 +66,53 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
# device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
bms1: !include
file: packages/bms/bms_JK-B_UART_full.yaml
file: packages/bms/bms_combine_JK-B_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_esp_1
bms_uart_id: 'uart_esp_1'
bms2: !include
file: packages/bms/bms_JK-B_UART_full.yaml
file: packages/bms/bms_combine_JK-B_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'JK-BMS 2'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_esp_2
bms_uart_id: 'uart_esp_2'
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -148,9 +140,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+14 -32
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/SeByDocKy/pvbrain2
# GitHub : https://github.com/Sleeper85/esphome-yambms
@@ -25,7 +25,7 @@ substitutions:
uart0_baudrate: '2400' #WKS {RJ45-UART0}
uart1_baudrate: '38400' #JSY193
uart2_baudrate: '19200' #smartshunt
uart2_baudrate: '19200' #SmartShunt
uart3_baudrate: '9600' #SRNE {RJ45-UART3}
uart4_baudrate: '115200' #JK-BMS 1
uart5_baudrate: '115200' #JK-BMS 2
@@ -77,8 +77,10 @@ api:
# | PVbrain2 packages |
# +--------------------------------------+
packages:
device_base: !include packages/base/device_base.yaml
device_board: !include packages/board/board_pvbrain2.yaml
device_board: !include packages/board/board_ESP32-S3_DevKitC-1_PVbrain2.yaml
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# BUS
# bus_i2c0: !include pvbrain2/base/device_bus_i2c0.yaml # SX1509 and BME280/BMP280
@@ -102,47 +104,30 @@ packages:
# You don't have to import a shunt but you must import at least one BMS.
shunt1: !include
file: packages/shunt/shunt_victron_smartshunt_UART_pvbrain2.yaml # shunt_junctek_khf_UART.yaml
file: packages/shunt/shunt_combine_Victron_SmartShunt_UART_expander.yaml # shunt_combine_Junctek_KHF_UART.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Shunt vars
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
shunt_update_interval: '3s'
shunt_combine_interval: '1s'
shunt_uart_id: uart_${uart_hub_bus}_2
shunt_uart_id: 'uart_${uart_hub_bus}_2'
bms1: !include
file: packages/bms/bms_JK-B_UART_full.yaml
file: packages/bms/bms_combine_JK-B_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_${uart_hub_bus}_4
bms_uart_id: 'uart_${uart_hub_bus}_4'
bms2: !include
file: packages/bms/bms_JK-B_UART_full.yaml
file: packages/bms/bms_combine_JK-B_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'JK-BMS 2'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_${uart_hub_bus}_5
bms_uart_id: 'uart_${uart_hub_bus}_5'
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -170,9 +155,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
@@ -186,7 +168,7 @@ packages:
# +--------------------------------------+
device_debug: !include
file: pvbrain2/base/device_debug.yaml
file: packages/base/device_debug_ESP32.yaml
vars:
debug_name: 'Debug'
debug_update_interval: '5s'
+36 -65
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -66,36 +66,40 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
# device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
# 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)
# sniffer1: !include
# file: packages/bms/bms_JK-PB_RS485_sniffer_talk_pin.yaml
# file: packages/bms/bms_combine_JK-PB_RS485_sniffer_talk_pin.yaml
# vars:
# sniffer_id: 'sniffer1'
# sniffer_protocol: 'JK02_32S'
@@ -103,7 +107,7 @@ packages:
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
sniffer1: !include
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
file: packages/bms/bms_combine_JK-PB_RS485_sniffer.yaml
vars:
sniffer_id: 'sniffer1'
sniffer_protocol: 'JK02_32S'
@@ -111,109 +115,79 @@ packages:
# Mode2 : configure the DIP switches of your BMS from 0x01 to 0x0F (don't use the 0x00 address, maximum 15 BMS)
bms1: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_rs485_address: '0x01' # BMS 1 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x01' # BMS 1 DIP switch
bms2: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'JK-BMS 2'
bms_rs485_address: '0x02' # BMS 2 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x02' # BMS 2 DIP switch
bms3: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '3' # must be a number
bms_name: 'JK-BMS 3'
bms_rs485_address: '0x03' # BMS 3 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x03' # BMS 3 DIP switch
bms4: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '4' # must be a number
bms_name: 'JK-BMS 4'
bms_rs485_address: '0x04' # BMS 4 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x04' # BMS 4 DIP switch
bms5: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '5' # must be a number
bms_name: 'JK-BMS 5'
bms_rs485_address: '0x05' # BMS 5 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x05' # BMS 5 DIP switch
bms6: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '6' # must be a number
bms_name: 'JK-BMS 6'
bms_rs485_address: '0x06' # BMS 6 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x06' # BMS 6 DIP switch
bms7: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '7' # must be a number
bms_name: 'JK-BMS 7'
bms_rs485_address: '0x07' # BMS 7 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x07' # BMS 7 DIP switch
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -241,9 +215,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+67 -32
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -66,32 +66,30 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
device_board: !include
file: packages/board/board_atom-s3.yaml
file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
vars:
yambms_id: 'yambms1'
canbus_id: 'canbus1'
display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
# 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)
# sniffer1: !include
# file: packages/bms/bms_JK-PB_RS485_sniffer_talk_pin.yaml
# file: packages/bms/bms_combine_JK-PB_RS485_sniffer_talk_pin.yaml
# vars:
# sniffer_id: 'sniffer1'
# sniffer_protocol: 'JK02_32S'
@@ -99,7 +97,7 @@ packages:
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
sniffer1: !include
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
file: packages/bms/bms_combine_JK-PB_RS485_sniffer.yaml
vars:
sniffer_id: 'sniffer1'
sniffer_protocol: 'JK02_32S'
@@ -107,39 +105,79 @@ packages:
# Mode2 : configure the DIP switches of your BMS from 0x01 to 0x0F (don't use the 0x00 address, maximum 15 BMS)
bms1: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_rs485_address: '0x01' # BMS 1 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x01' # BMS 1 DIP switch
bms2: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'JK-BMS 2'
bms_rs485_address: '0x02' # BMS 2 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x02' # BMS 2 DIP switch
# bms3: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x03' # BMS 3 DIP switch
# bms4: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x04' # BMS 4 DIP switch
# bms5: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x05' # BMS 5 DIP switch
# bms6: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x06' # BMS 6 DIP switch
# bms7: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x07' # BMS 7 DIP switch
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -167,9 +205,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -20,8 +20,10 @@
substitutions:
name: yambms
# Don't forget to configure your WiFi credentials in the secrets.yaml file
#
# If needed, configure a static IP here
# ethernet:
# wifi:
# manual_ip:
# static_ip: 192.168.0.85
# gateway: 192.168.0.1
@@ -30,7 +32,7 @@ substitutions:
# dns2: 8.8.4.4
logger:
level: INFO # DEBUG / INFO / WARN
level: DEBUG # DEBUG / INFO / WARN
ota:
platform: esphome
@@ -64,26 +66,35 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base_ethernet.yaml
device_board: !include packages/board/board_esp32-c3-eth01-evo.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
device_board: !include packages/board/board_ESP32_LilyGo-T-CAN485.yaml
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
# 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)
# sniffer1: !include
# file: packages/bms/bms_combine_JK-PB_RS485_sniffer_talk_pin.yaml
# vars:
# sniffer_id: 'sniffer1'
# sniffer_protocol: 'JK02_32S'
# sniffer_uart_id: 'uart_esp_1'
# sniffer_talk_pin: 17
sniffer1: !include
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
file: packages/bms/bms_combine_JK-PB_RS485_sniffer.yaml
vars:
sniffer_id: 'sniffer1'
sniffer_protocol: 'JK02_32S'
@@ -91,39 +102,69 @@ packages:
# Mode2 : configure the DIP switches of your BMS from 0x01 to 0x0F (don't use the 0x00 address, maximum 15 BMS)
bms1: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_minimal.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_rs485_address: '0x01' # BMS 1 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x01' # BMS 1 DIP switch
bms2: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_minimal.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'JK-BMS 2'
bms_rs485_address: '0x02' # BMS 2 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x02' # BMS 2 DIP switch
bms3: !include
file: packages/bms/bms_combine_JK-PB_RS485_bms_minimal.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
bms4: !include
file: packages/bms/bms_combine_JK-PB_RS485_bms_minimal.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
bms5: !include
file: packages/bms/bms_combine_JK-PB_RS485_bms_minimal.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
bms6: !include
file: packages/bms/bms_combine_JK-PB_RS485_bms_minimal.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
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -151,9 +192,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+58 -94
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/SeByDocKy/pvbrain2
# GitHub : https://github.com/Sleeper85/esphome-yambms
@@ -77,8 +77,10 @@ api:
# | PVbrain2 packages |
# +--------------------------------------+
packages:
device_base: !include packages/base/device_base.yaml
device_board: !include packages/board/board_pvbrain2.yaml
device_board: !include packages/board/board_ESP32-S3_DevKitC-1_PVbrain2.yaml
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# BUS
# bus_i2c0: !include pvbrain2/base/device_bus_i2c0.yaml # SX1509 and BME280/BMP280
@@ -102,22 +104,17 @@ packages:
# You don't have to import a shunt but you must import at least one BMS.
shunt1: !include
file: packages/shunt/shunt_victron_smartshunt_UART_pvbrain2.yaml # shunt_junctek_khf_UART.yaml
file: packages/shunt/shunt_combine_Victron_SmartShunt_UART_expander.yaml # shunt_combine_Junctek_KHF_UART.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Shunt vars
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
shunt_update_interval: '3s'
shunt_combine_interval: '1s'
shunt_uart_id: uart_${uart_hub_bus}_2
# 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)
sniffer1: !include
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
file: packages/bms/bms_combine_JK-PB_RS485_sniffer.yaml
vars:
sniffer_id: 'sniffer1'
sniffer_protocol: 'JK02_32S'
@@ -125,109 +122,79 @@ packages:
# Mode2 : configure the DIP switches of your BMS from 0x01 to 0x0F (don't use the 0x00 address, maximum 15 BMS)
bms1: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_rs485_address: '0x01' # BMS 1 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x01' # BMS 1 DIP switch
bms2: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'JK-BMS 2'
bms_rs485_address: '0x02' # BMS 2 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x02' # BMS 2 DIP switch
bms3: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '3' # must be a number
bms_name: 'JK-BMS 3'
bms_rs485_address: '0x03' # BMS 3 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
# bms3: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x03' # BMS 3 DIP switch
bms4: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '4' # must be a number
bms_name: 'JK-BMS 4'
bms_rs485_address: '0x04' # BMS 4 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
# bms4: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x04' # BMS 4 DIP switch
bms5: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '5' # must be a number
bms_name: 'JK-BMS 5'
bms_rs485_address: '0x05' # BMS 5 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
# bms5: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x05' # BMS 5 DIP switch
bms6: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '6' # must be a number
bms_name: 'JK-BMS 6'
bms_rs485_address: '0x06' # BMS 6 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
# bms6: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x06' # BMS 6 DIP switch
bms7: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '7' # must be a number
bms_name: 'JK-BMS 7'
bms_rs485_address: '0x07' # BMS 7 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
# bms7: !include
# file: packages/bms/bms_combine_JK-PB_RS485_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: '0x07' # BMS 7 DIP switch
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -255,9 +222,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
@@ -271,7 +235,7 @@ packages:
# +--------------------------------------+
device_debug: !include
file: pvbrain2/base/device_debug.yaml
file: packages/base/device_debug_ESP32.yaml
vars:
debug_name: 'Debug'
debug_update_interval: '5s'
+27 -36
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -66,53 +66,53 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
# device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
seplos_modbus1: !include
file: packages/bms/bms_SEPLOS_V1_V2_RS485_modbus.yaml
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' # Please set the baudrate of your Seplos BMS model here. It's sometimes 19200 baud instead of 9600.
seplos_modbus_rx_timeout: 150ms
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_SEPLOS_V1_V2_RS485_bms_full.yaml
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Seplos modbus ID
seplos_modbus_id: 'seplos_modbus1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_rs485_address: '0x01' # BMS 1 DIP switch
bms_address: '0x01' # BMS 1 DIP switch
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
bms_update_interval: '3s' # 10s @syssi example
bms_combine_interval: '1s'
# Required settings cannot be retrieved from BMS
# These values ​​must match your BMS settings
# LFP values example
@@ -123,19 +123,15 @@ packages:
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
bms2: !include
file: packages/bms/bms_SEPLOS_V1_V2_RS485_bms_full.yaml
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Seplos modbus ID
seplos_modbus_id: 'seplos_modbus1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'BMS 2'
bms_rs485_address: '0x02' # BMS 2 DIP switch
bms_address: '0x02' # BMS 2 DIP switch
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
bms_update_interval: '3s' # 10s @syssi example
bms_combine_interval: '1s'
bms_uart_id: uart_esp_2
# Required settings cannot be retrieved from BMS
# These values ​​must match your BMS settings
@@ -150,8 +146,6 @@ packages:
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -179,9 +173,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -18,7 +18,7 @@
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
substitutions:
name: yambms-demo
name: yambms-node1
# Don't forget to configure your WiFi credentials in the secrets.yaml file
#
@@ -32,7 +32,7 @@ substitutions:
# dns2: 8.8.4.4
logger:
level: DEBUG # DEBUG / INFO / WARN
level: INFO # DEBUG / INFO / WARN
ota:
platform: esphome
@@ -66,133 +66,105 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
device_board: !include
file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# device_board: !include
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAMLs contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
config_multinode_modbus: !include packages/config/config_multi-node_modbus.yaml
modbus: !include
file: packages/base/device_modbus.yaml
vars:
yambms_id: 'yambms1'
canbus_id: 'canbus1'
display_auto_next_page_interval: '5s'
modbus_role: 'client' # client / server
modbus_uart_id: 'uart_esp_1' # RS485 board
shunt1: !include
file: packages/shunt/shunt_fake.yaml
file: packages/shunt/shunt_combine_modbus_client.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Shunt vars
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
shunt_update_interval: '3s'
shunt_combine_interval: '1s'
# Shunt sensors values
shunt_voltage: '53.41' # V
shunt_current: '37.5' # A
shunt_power: '2003' # W
shunt_soc: '86' # %
bms1: !include
file: packages/bms/bms_FAKE.yaml
file: packages/bms/bms_combine_modbus_client.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
# BMS sensors values
bms_battery_capacity: '280' # Ah
bms_battery_capacity_remaining: '243' # Ah
bms_voltage: '53.45' # V
bms_current: '9.2' # A
bms_power: '492' # W
bms_soc: '87' # %
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_max_charge_current: '100' # A
bms_max_discharge_current: '100' # A
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_charging_cycles: '178' # charging cycles number Used to calculate the SoH
bms2: !include
file: packages/bms/bms_FAKE.yaml
file: packages/bms/bms_combine_modbus_client.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '2' # must be a number
bms_name: 'BMS 2'
bms_update_interval: '3s'
bms_combine_interval: '1s'
# BMS sensors values
bms_battery_capacity: '280' # Ah
bms_battery_capacity_remaining: '238' # Ah
bms_voltage: '53.41' # V
bms_current: '11.3' # A
bms_power: '604' # W
bms_soc: '85' # %
bms_min_cell_voltage: '3.337' # V
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_max_charge_current: '100' # A
bms_max_discharge_current: '100' # A
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_charging_cycles: '226' # charging cycles number Used to calculate the SoH
bms3: !include
file: packages/bms/bms_FAKE.yaml
file: packages/bms/bms_combine_modbus_client.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '3' # must be a number
bms_name: 'BMS 3'
bms_update_interval: '3s'
bms_combine_interval: '1s'
# BMS sensors values
bms_battery_capacity: '280' # Ah
bms_battery_capacity_remaining: '232' # Ah
bms_voltage: '53.37' # V
bms_current: '15.7' # A
bms_power: '838' # W
bms_soc: '83' # %
bms_min_cell_voltage: '3.334' # V
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_max_charge_current: '100' # A
bms_max_discharge_current: '100' # A
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_charging_cycles: '194' # charging cycles number Used to calculate the SoH
# bms4: !include
# file: packages/bms/bms_combine_modbus_client.yaml
# vars:
# bms_id: '4' # must be a number
# bms_name: 'BMS 4'
# bms5: !include
# file: packages/bms/bms_combine_modbus_client.yaml
# vars:
# bms_id: '5' # must be a number
# bms_name: 'BMS 5'
# bms6: !include
# file: packages/bms/bms_combine_modbus_client.yaml
# vars:
# bms_id: '6' # must be a number
# bms_name: 'BMS 6'
# bms7: !include
# file: packages/bms/bms_combine_modbus_client.yaml
# vars:
# bms_id: '7' # must be a number
# bms_name: 'BMS 7'
# bms8: !include
# file: packages/bms/bms_combine_modbus_client.yaml
# vars:
# bms_id: '8' # must be a number
# bms_name: 'BMS 8'
# bms9: !include
# file: packages/bms/bms_combine_modbus_client.yaml
# vars:
# bms_id: '9' # must be a number
# bms_name: 'BMS 9'
# bms10: !include
# file: packages/bms/bms_combine_modbus_client.yaml
# vars:
# bms_id: '10' # must be a number
# bms_name: 'BMS 10'
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -220,9 +192,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+124
View File
@@ -0,0 +1,124 @@
# Updated : 2025.01.16
# Version : 1.5.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>.
substitutions:
name: yambms-node2
# Don't forget to configure your WiFi credentials in the secrets.yaml file
#
# 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 # DEBUG / INFO / WARN
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
# Please note that enabling this component will take up a lot of memory and may decrease
# stability and be the cause of reboot depending on the capabilities of the board used.
#web_server:
# port: 80
# log: false
# ota: false
# Remove canbus_node1 (not necessary)
canbus:
- id: !remove canbus_node1
# +--------------------------------------+
# | Packages |
# +--------------------------------------+
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAMLs contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
config_multinode_modbus: !include packages/config/config_multi-node_modbus.yaml
modbus: !include
file: packages/base/device_modbus.yaml
vars:
modbus_role: 'server' # client / server
modbus_uart_id: 'uart_esp_1' # RS485 board
shunt1: !include
file: packages/shunt/shunt_modbus_Victron_SmartShunt_UART.yaml
vars:
shunt_id: '1' # must be a number
shunt_name: 'Shunt 1'
shunt_uart_id: 'uart_esp_2'
bms1: !include
file: packages/bms/bms_modbus_JK-B_UART_full.yaml
vars:
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_uart_id: 'uart_esp_3'
# +--------------------------------------+
# | DEBUG ( logger level must be DEBUG ) |
# +--------------------------------------+
device_debug: !include
file: packages/base/device_debug_ESP32.yaml
vars:
debug_name: 'Debug'
debug_update_interval: '5s'
+127
View File
@@ -0,0 +1,127 @@
# Updated : 2025.01.16
# Version : 1.5.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>.
substitutions:
name: yambms-node2
# Don't forget to configure your WiFi credentials in the secrets.yaml file
#
# 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 # DEBUG / INFO / WARN
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
# Please note that enabling this component will take up a lot of memory and may decrease
# stability and be the cause of reboot depending on the capabilities of the board used.
#web_server:
# port: 80
# log: false
# ota: false
# Remove canbus_node1 (not necessary)
canbus:
- id: !remove canbus_node1
# +--------------------------------------+
# | Packages |
# +--------------------------------------+
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAMLs contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
config_multinode_modbus: !include packages/config/config_multi-node_modbus.yaml
modbus: !include
file: packages/base/device_modbus.yaml
vars:
modbus_role: 'server' # client / server
modbus_uart_id: 'uart_esp_1' # RS485 board
modbus_baud_rate: '19200' # 9600 / 19200 / 115200
bms2: !include
file: packages/bms/bms_modbus_JK-ALL_BLE_standard.yaml
vars:
bms_id: '2' # must be a number, also represents the modbus server number !
bms_name: 'JK-BMS 2'
bms_ble_protocol_version: JK02_32S # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: C8:47:8C:10:7E:AA
bms3: !include
file: packages/bms/bms_modbus_JK-ALL_BLE_standard.yaml
vars:
bms_id: '3' # must be a number, also represents the modbus server number !
bms_name: 'JK-BMS 3'
bms_ble_protocol_version: JK02_32S # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: C8:47:8C:EE:16:EA
# +--------------------------------------+
# | DEBUG ( logger level must be DEBUG ) |
# +--------------------------------------+
device_debug: !include
file: packages/base/device_debug_ESP32.yaml
vars:
debug_name: 'Debug'
debug_update_interval: '5s'
+23 -30
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -74,51 +74,47 @@ api:
# https://esphome.io/components/ble_client.html
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
# device_board: !include packages/board/board_atom-lite.yaml
# device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
bms1: !include
file: packages/bms/bms_JK-ALL_BLE_standard.yaml
file: packages/bms/bms_combine_JK-ALL_BLE_standard.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_ble_protocol_version: JK02_32S # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: C8:47:80:09:37:ED
bms_ble_protocol_version: 'JK02_32S' # JK02_24S < hardware version 11.0 >= JK02_32S
bms_ble_mac_address: 'C8:47:8C:10:7E:AA'
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -146,9 +142,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+22 -29
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -66,50 +66,46 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
# device_board: !include packages/board/board_atom-lite.yaml
# device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
bms1: !include
file: packages/bms/bms_JK-B_UART_full.yaml
file: packages/bms/bms_combine_JK-B_UART_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_update_interval: '3s'
bms_combine_interval: '1s'
bms_uart_id: uart_esp_1
bms_uart_id: 'uart_esp_1'
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -137,9 +133,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+24 -29
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.16
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -66,36 +66,40 @@ api:
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
packages:
device_base: !include packages/base/device_base.yaml
# Board : uncomment your board
# device_board: !include packages/board/board_esp32-devkit-v1.yaml
# device_board: !include packages/board/board_esp32-s3-devkitc-1.yaml
device_board: !include packages/board/board_atom-s3-lite.yaml
############### >>> UNCOMMENT YOUR BOARD <<< ###############
# 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_LilyGo-T-CAN485.yaml
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1.yaml
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
# device_board: !include packages/board/board_ESP32-S3_AtomS3-Lite.yaml
# device_board: !include
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
# file: packages/board/board_ESP32-S3_AtomS3.yaml # board_ESP32-S3_AtomS3R.yaml
# vars:
# yambms_id: 'yambms1'
# canbus_id: 'canbus1'
# display_auto_next_page_interval: '5s'
############################################################
# Config : this YAML contains the settings shared between all ESP32s
config_yambms: !include packages/config/config_yambms.yaml
# shunt1: !include
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_junctek_khf_UART.yaml
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
# vars:
# # YamBMS ID
# yambms_id: 'yambms1'
# # Shunt vars
# shunt_id: '1' # must be a number
# shunt_name: 'Shunt 1'
# shunt_update_interval: '3s'
# shunt_combine_interval: '1s'
# shunt_uart_id: uart_esp_0
# 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)
# sniffer1: !include
# file: packages/bms/bms_JK-PB_RS485_sniffer_talk_pin.yaml
# file: packages/bms/bms_combine_JK-PB_RS485_sniffer_talk_pin.yaml
# vars:
# sniffer_id: 'sniffer1'
# sniffer_protocol: 'JK02_32S'
@@ -103,7 +107,7 @@ packages:
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
sniffer1: !include
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
file: packages/bms/bms_combine_JK-PB_RS485_sniffer.yaml
vars:
sniffer_id: 'sniffer1'
sniffer_protocol: 'JK02_32S'
@@ -111,25 +115,19 @@ packages:
# Mode2 : configure the DIP switches of your BMS from 0x01 to 0x0F (don't use the 0x00 address, maximum 15 BMS)
bms1: !include
file: packages/bms/bms_JK-PB_RS485_bms_full.yaml
file: packages/bms/bms_combine_JK-PB_RS485_bms_full.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1'
# Sniffer ID
sniffer_id: 'sniffer1'
# BMS vars
bms_id: '1' # must be a number
bms_name: 'JK-BMS 1'
bms_rs485_address: '0x01' # BMS 1 DIP switch
bms_update_interval: '3s' # going below '3s' can cause problems
bms_combine_interval: '1s'
bms_address: '0x01' # BMS 1 DIP switch
yambms1: !include
file: packages/yambms/yambms.yaml
vars:
# 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'
@@ -157,9 +155,6 @@ packages:
canbus1: !include
file: packages/yambms/yambms_canbus.yaml
vars:
# YamBMS ID
yambms_id: 'yambms1' # YamBMS ID to retrieve information from
# CANBUS vars
canbus_id: 'canbus1'
canbus_name: 'CANBUS 1'
canbus_node_id: 'canbus_node1'
+8 -41
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.03.21
# Version : 1.5.4
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -18,7 +18,7 @@
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
substitutions:
yambms_version: "1.5.1"
yambms_version: "1.5.4"
esphome:
name: ${name}
@@ -28,7 +28,7 @@ esphome:
project:
name: Sleeper85.YamBMS
version: ${yambms_version}
min_version: 2024.6.0
min_version: 2025.3.0
time:
# https://esphome.io/components/time/homeassistant
@@ -48,6 +48,10 @@ binary_sensor:
name: ${name} ESP32 Online Status
id: esp32_online_status
entity_category: diagnostic
# Inverter communication status (CANBUS / RS485)
- platform: template
id: inverter_com_status
entity_category: diagnostic
sensor:
# https://esphome.io/components/sensor/uptime
@@ -56,22 +60,6 @@ sensor:
update_interval: 10s
internal: true
# https://esphome.io/components/sensor/wifi_signal
- platform: wifi_signal
name: ${name} ESP32 WiFi power
id: esp32_wifi_power
update_interval: 10s
entity_category: diagnostic
- platform: copy # Reports the WiFi signal strength in %
source_id: esp32_wifi_power
name: ${name} ESP32 WiFi power (%)
id: esp32_wifi_power_percent
unit_of_measurement: '%'
entity_category: diagnostic
filters:
- lambda: 'return min(max(2 * (x + 100.0), 0.0), 100.0);'
# https://esphome.io/components/sensor/internal_temperature
- platform: internal_temperature
name: ${name} ESP32 internal temperature
@@ -112,27 +100,6 @@ text_sensor:
internal: true
lambda: return id(my_time).now().strftime("%Y-%m-%d %H:%M:%S");
# https://esphome.io/components/text_sensor/wifi_info
- platform: wifi_info
ip_address:
name: ${name} ESP32 IP address
id: esp32_ip_address
ssid:
name: ${name} ESP32 connected SSID
id: esp32_connected_ssid
bssid:
name: ${name} ESP32 connected BSSID
id: esp32_connected_bssid
mac_address:
name: ${name} ESP32 MAC WiFi address
id: esp32_mac_wifi_address
scan_results:
name: ${name} ESP32 latest scan results
id: esp32_latest_scan_results
dns_address:
name: ${name} ESP32 DNS address
id: esp32_dns_address
# https://esphome.io/components/text_sensor/version
- platform: version
name: ${name} ESP32 ESPHome version
+4 -89
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.20
# Version : 1.5.3
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -17,85 +17,7 @@
# 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:
yambms_version: "1.5.1"
esphome:
name: ${name}
# friendly_name: ${name}
# comment: 'Solar system braining and more !'
# area: 'Technical local'
project:
name: Sleeper85.YamBMS
version: ${yambms_version}
min_version: 2024.6.0
time:
# https://esphome.io/components/time/homeassistant
# https://esphome.io/components/time/sntp
- platform: homeassistant
id: my_time
button:
# https://esphome.io/components/button/restart
- platform: restart
name: ${name} ESP32 Restart
entity_category: config
binary_sensor:
# https://esphome.io/components/binary_sensor/status
- platform: status
name: ${name} ESP32 Online Status
id: esp32_online_status
entity_category: diagnostic
sensor:
# https://esphome.io/components/sensor/uptime
- platform: uptime
id: esp32_uptime_sec
update_interval: 10s
internal: true
# https://esphome.io/components/sensor/internal_temperature
- platform: internal_temperature
name: ${name} ESP32 internal temperature
id: esp32_internal_temperature
update_interval: 10s
entity_category: diagnostic
text_sensor:
# Uptime Human Readable
- platform: template
name: ${name} ESP32 Uptime
id: esp32_uptime
update_interval: 10s
icon: mdi:clock-start
entity_category: diagnostic
lambda: |-
int uptime_sec = id(esp32_uptime_sec).state;
int days = uptime_sec / 86400;
int hours = (uptime_sec % 86400) / 3600;
int minutes = (uptime_sec % 3600) / 60;
int seconds = uptime_sec % 60;
return {
(
(days ? std::to_string(days) +"d " : "") +
(hours ? std::to_string(hours) +"h " : "") +
(minutes ? std::to_string(minutes) +"m " : "") +
(std::to_string(seconds) +"s")
).c_str()
};
# Now date and time
- platform: template
name: ${name}_esp32_date_time_now
id: esp32_date_time_now
update_interval: 10s
icon: mdi:clock-start
entity_category: diagnostic
internal: true
lambda: return id(my_time).now().strftime("%Y-%m-%d %H:%M:%S");
# https://esphome.io/components/text_sensor/ethernet_info.html
- platform: ethernet_info
ip_address:
@@ -105,12 +27,5 @@ text_sensor:
name: ${name} ESP32 DNS address
id: esp32_dns_address
mac_address:
name: ${name} ESP32 MAC WiFi address
id: esp32_mac_wifi_address
# https://esphome.io/components/text_sensor/version
- platform: version
name: ${name} ESP32 ESPHome version
id: esp32_esphome_version
hide_timestamp: false #true
entity_category: diagnostic
name: ${name} ESP32 MAC address
id: esp32_mac_address
+61
View File
@@ -0,0 +1,61 @@
# Updated : 2025.01.20
# Version : 1.5.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>.
sensor:
# https://esphome.io/components/sensor/wifi_signal
- platform: wifi_signal
name: ${name} ESP32 WiFi power
id: esp32_wifi_power
update_interval: 30s
entity_category: diagnostic
# Reports the WiFi signal strength in %
- platform: template
name: ${name} ESP32 WiFi power (%)
id: esp32_wifi_power_percent
update_interval: 30s
unit_of_measurement: '%'
icon: mdi:wifi
entity_category: diagnostic
accuracy_decimals: 0
lambda: |-
float wifi_power_dbm = id(esp32_wifi_power).state;
return min(max(2 * (wifi_power_dbm + 100.0), 0.0), 100.0);
text_sensor:
# https://esphome.io/components/text_sensor/wifi_info
- platform: wifi_info
ip_address:
name: ${name} ESP32 IP address
id: esp32_ip_address
ssid:
name: ${name} ESP32 connected SSID
id: esp32_connected_ssid
bssid:
name: ${name} ESP32 connected BSSID
id: esp32_connected_bssid
mac_address:
name: ${name} ESP32 MAC address
id: esp32_mac_address
scan_results:
name: ${name} ESP32 latest scan results
id: esp32_latest_scan_results
dns_address:
name: ${name} ESP32 DNS address
id: esp32_dns_address
+28
View File
@@ -0,0 +1,28 @@
# Updated : 2025.03.21
# 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>.
uart:
- id: !extend ${modbus_uart_id}
baud_rate: ${modbus_baud_rate}
modbus:
- uart_id: ${modbus_uart_id}
id: modbus_${modbus_role}
role: ${modbus_role}
send_wait_time: ${modbus_send_wait_time}
+24
View File
@@ -0,0 +1,24 @@
# Updated : 2025.03.21
# 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>.
modbus:
- uart_id: ${modbus_uart_id}
id: modbus_${modbus_role}
role: ${modbus_role}
send_wait_time: ${modbus_send_wait_time}
+25 -2
View File
@@ -1,5 +1,5 @@
# Updated : 2024.08.08
# Version : 1.2.1
# Updated : 2025.01.25
# Version : 1.2.2
# GitHub : https://github.com/Sleeper85/esphome-yambms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -17,6 +17,9 @@
# 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>.
# packages:
# bms_charging_logic: !include bms_options_charging_logic.yaml
sensor:
# +--------------------------------------+
# | Total Daily Energy |
@@ -41,3 +44,23 @@ sensor:
filters:
# Multiplication factor from W to kW is 0.001
- multiply: 0.001
- platform: template
name: ${name} ${bms_name} Battery SoC
id: bms${bms_id}_battery_soc
unit_of_measurement: "%"
device_class: battery
update_interval: ${bms_update_interval}
accuracy_decimals: 0
filters:
- or:
- throttle: 10s
- delta: 1
lambda: |-
float soc = id(bms${bms_id}_state_of_charge).state;
float min_cell_v = id(bms${bms_id}_min_cell_voltage).state;
float cell_low_v = id(bms${bms_id}_cell_uvp).state + 0.2;
if (min_cell_v <= cell_low_v) return 0; // Real 0% => return 0%
else if (soc < 1) return 2; // False 0% => return 2%
else return soc; // Else => return BMS SoC
+86 -96
View File
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.5.1
# Updated : 2025.01.24
# Version : 1.5.4
# GitHub : https://github.com/Sleeper85/esphome-yambms
# This YAML is free software: you can redistribute it and/or
@@ -25,27 +25,6 @@ globals:
restore_value: no
initial_value: "false"
switch:
# Combine Enable-Switch (user controlled switch to en/dis-able combine)
- platform: template
name: "${name} ${bms_name} Combine enabled"
id: bms${bms_id}_switch_combine
restore_mode: RESTORE_DEFAULT_ON
optimistic: true
binary_sensor:
# Combine Availability (indicated, if the BMS is able to be included in combine)
- platform: template
name: "${name} ${bms_name} Combine Availability"
id: bms${bms_id}_availability
lambda: return (id(bms${bms_id}_online_status).state && (id(bms${bms_id}_charging_allowed).state || id(bms${bms_id}_discharging_allowed).state));
# Can be combined (indicated, if the BMS can be combined)
- platform: template
name: "${name} ${bms_name} Can be combined"
id: bms${bms_id}_can_be_combined
lambda: return (id(bms${bms_id}_availability).state && id(bms${bms_id}_switch_combine).state);
# Combine once without conditions
esphome:
on_boot:
@@ -53,76 +32,79 @@ esphome:
# Shunt counter (total)
- lambda: id(${yambms_id}_var_bms_counter) += 1;
binary_sensor:
# Indicates whether the BMS can be combined
- platform: template
name: "${name} ${bms_name} Can be combined"
id: bms${bms_id}_can_be_combined
lambda: return (id(bms${bms_id}_online_status).state && id(bms${bms_id}_battery_capacity).state > 0);
interval:
- interval: ${bms_combine_interval}
then:
- lambda: |-
// Combine only if the device is able to be included in combine
if (id(bms${bms_id}_can_be_combined).state)
{
// Combine once only
if (id(bms${bms_id}_combined_once) == false)
{
id(${yambms_id}_var_total_installed_battery_capacity) += id(bms${bms_id}_battery_capacity).state;
id(bms${bms_id}_combined_once) = true;
}
// Combine (not continuously)
if (id(bms${bms_id}_combined) == false)
{
// To combine bms counter
id(${yambms_id}_var_to_combine_bms_counter) += 1;
// TOTAL cell_count
// id(${yambms_id}_var_total_cell_count) += id(bms${bms_id}_cell_count).state;
// TOTAL battery_capacity
id(${yambms_id}_var_total_battery_capacity) += id(bms${bms_id}_battery_capacity).state;
// Combined
id(bms${bms_id}_combined) = true;
}
}
// Uncombine (not continuously)
else if (id(bms${bms_id}_combined) == true)
{
// To combine bms counter
id(${yambms_id}_var_to_combine_bms_counter) -= 1;
// TOTAL cell_count
// id(${yambms_id}_var_total_cell_count) -= id(bms${bms_id}_cell_count).state;
// TOTAL battery_capacity
id(${yambms_id}_var_total_battery_capacity) -= id(bms${bms_id}_battery_capacity).state;
// Uncombined
id(bms${bms_id}_combined) = false;
}
// Combine continuously (all BMS)
// BMS number to combine ?
if (id(${yambms_id}_var_to_combine_bms_number) == ${bms_id})
{
// TOTAL charging_allowed_counter
if (id(bms${bms_id}_charging_allowed).state) id(${yambms_id}_var_charging_allowed_counter) += 1;
// TOTAL discharging_allowed_counter
if (id(bms${bms_id}_discharging_allowed).state) id(${yambms_id}_var_discharging_allowed_counter) += 1;
// +-----------------------------------------------+
// | Errors bitmask (16bit) |
// +-----------------------------------------------+
if (id(bms${bms_id}_errors_bitmask).state > 1)
{
uint16_t bms_errors_bitmask = id(bms${bms_id}_errors_bitmask).state; // errors_bitmask (16bit)
id(${yambms_id}_var_errors_bitmask) |= bms_errors_bitmask; // OR bitwise
id(${yambms_id}_var_errors_bitmask_counter) += 1; // errors_bitmask_counter
}
// +-----------------------------------------------+
// Combine only if the device is able to be included in combine
// The BMS can be combined ?
if (id(bms${bms_id}_can_be_combined).state)
{
// +-----------------------------------------------+
// | Combine once only |
// +-----------------------------------------------+
if (id(bms${bms_id}_combined_once) == false)
{
id(${yambms_id}_var_total_installed_battery_capacity) += id(bms${bms_id}_battery_capacity).state;
id(bms${bms_id}_combined_once) = true;
}
// +-----------------------------------------------+
// | Combine not continuously |
// +-----------------------------------------------+
if (id(bms${bms_id}_combined) == false)
{
// To combine bms counter
id(${yambms_id}_var_to_combine_bms_counter) += 1;
// Combined
id(bms${bms_id}_combined) = true;
}
// +-----------------------------------------------+
// | Combine continuously |
// +-----------------------------------------------+
// YamBMS Errors Bitmask (16bit)
if (id(bms${bms_id}_yambms_errors_bitmask).state > 0)
{
uint16_t errors_bitmask = id(bms${bms_id}_yambms_errors_bitmask).state; // errors_bitmask (16bit)
id(${yambms_id}_var_errors_bitmask) |= errors_bitmask; // OR bitwise
id(${yambms_id}_var_errors_bitmask_counter) += 1; // errors_bitmask_counter
}
if (id(bms${bms_id}_charging_allowed).state)
{
// TOTAL charging_allowed_counter
id(${yambms_id}_var_charging_allowed_counter) += 1;
// TOTAL max_charge_current
id(${yambms_id}_var_total_max_charge_current) += id(bms${bms_id}_max_charge_current).state;
}
// TOTAL bms_blocking_charge_counter
else id(${yambms_id}_var_bms_blocking_charge_counter) += 1;
if (id(bms${bms_id}_discharging_allowed).state)
{
// TOTAL discharging_allowed_counter
id(${yambms_id}_var_discharging_allowed_counter) += 1;
// TOTAL max_discharge_current
id(${yambms_id}_var_total_max_discharge_current) += id(bms${bms_id}_max_discharge_current).state;
}
// TOTAL bms_blocking_discharge_counter
else id(${yambms_id}_var_bms_blocking_discharge_counter) += 1;
// TOTAL total_voltage
id(${yambms_id}_var_bms_total_voltage) += id(bms${bms_id}_total_voltage).state;
@@ -132,19 +114,14 @@ interval:
// TOTAL power
id(${yambms_id}_var_bms_total_power) += id(bms${bms_id}_power).state;
// TOTAL max_charge_current
if (id(bms${bms_id}_charging_allowed).state)
id(${yambms_id}_var_total_max_charge_current) += id(bms${bms_id}_max_charge_current).state;
// TOTAL max_discharge_current
if (id(bms${bms_id}_discharging_allowed).state)
id(${yambms_id}_var_total_max_discharge_current) += id(bms${bms_id}_max_discharge_current).state;
// TOTAL battery_capacity
id(${yambms_id}_var_total_battery_capacity) += id(bms${bms_id}_battery_capacity).state;
// TOTAL capacity_remaining_ah
id(${yambms_id}_var_total_capacity_remaining_ah) += id(bms${bms_id}_capacity_remaining_ah).state;
// TOTAL soc
id(${yambms_id}_var_bms_total_soc) += id(bms${bms_id}_state_of_charge).state;
// TOTAL SoC
id(${yambms_id}_var_bms_total_soc) += id(bms${bms_id}_battery_soc).state;
// TOTAL charging_cycles
id(${yambms_id}_var_total_charging_cycles) += id(bms${bms_id}_charging_cycles).state;
@@ -197,6 +174,19 @@ interval:
id(${yambms_id}_var_max_temperature_sensor) = id(bms${bms_id}_max_temperature_sensor).state;
}
}
// To combine BMS number
// +-----------------------------------------------+
// | Uncombine not continuously |
// +-----------------------------------------------+
else if (id(bms${bms_id}_combined) == true)
{
// To combine bms counter
id(${yambms_id}_var_to_combine_bms_counter) -= 1;
// Uncombined
id(bms${bms_id}_combined) = false;
}
// Increment the counter for next BMS processing
id(${yambms_id}_var_to_combine_bms_number)++;
}
+26
View File
@@ -0,0 +1,26 @@
# Updated : 2024.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>.
substitutions:
bms_model: "Fake BMS"
bms_protocol: "DEMO"
packages:
bms_sensors: !include bms_sensors_FAKE.yaml
bms_combine: !include bms_combine.yaml
@@ -0,0 +1,26 @@
# Updated : 2025.01.28
# 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:
bms_model: "JBD"
bms_protocol: "BLE"
packages:
bms_sensors: !include bms_sensors_JBD_BLE_full.yaml
bms_combine: !include bms_combine.yaml
@@ -0,0 +1,26 @@
# Updated : 2024.12.23
# 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:
bms_model: "JBD"
bms_protocol: "UART"
packages:
bms_sensors: !include bms_sensors_JBD_UART_full.yaml
bms_combine: !include bms_combine.yaml
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.2.4
# Updated : 2025.01.28
# Version : 1.2.6
# GitHub : https://github.com/syssi/esphome-jk-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -25,6 +25,7 @@ packages:
bms_base: !include bms_base.yaml
bms_combine: !include bms_combine.yaml
bms_temperature_sensor: !include bms_temperature_sensor_2.yaml
bms_errors_bitmask: !include bms_errors_bitmask_JK-ALL_BLE.yaml
ota:
on_begin:
@@ -57,8 +58,8 @@ esp32_ble_tracker:
}
ble_client:
- mac_address: ${bms_ble_mac_address}
id: ble_client${bms_id}
- id: ble_client${bms_id}
mac_address: ${bms_ble_mac_address}
jk_bms_ble:
- ble_client_id: ble_client${bms_id}
@@ -89,11 +90,14 @@ binary_sensor:
heating:
name: "${name} ${bms_name} heating"
switch:
- platform: jk_bms_ble
jk_bms_ble_id: jk_bms_ble${bms_id}
charging:
id: bms${bms_id}_charge_switch
name: "${name} ${bms_name} Charge switch"
discharging:
id: bms${bms_id}_discharge_switch
name: "${name} ${bms_name} Discharge switch"
balancer:
name: "${name} ${bms_name} Balance switch"
@@ -108,7 +112,6 @@ binary_sensor:
name: "${name} ${bms_name} timed stored data"
charging_float_mode:
name: "${name} ${bms_name} charging float mode"
# +--------------------------------------+
- platform: ble_client
ble_client_id: ble_client${bms_id}
@@ -135,6 +138,7 @@ sensor:
id: bms${bms_id}_delta_cell_voltage
name: "${name} ${bms_name} delta cell voltage"
average_cell_voltage:
id: bms${bms_id}_average_cell_voltage
name: "${name} ${bms_name} average cell voltage"
cell_voltage_1:
id: bms${bms_id}_cell_v_01
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.2.4
# Updated : 2025.01.28
# Version : 1.2.6
# GitHub : https://github.com/syssi/esphome-jk-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -25,6 +25,7 @@ packages:
bms_base: !include bms_base.yaml
bms_combine: !include bms_combine.yaml
bms_temperature_sensor: !include bms_temperature_sensor_2.yaml
bms_errors_bitmask: !include bms_errors_bitmask_JK-ALL_BLE.yaml
ota:
on_begin:
@@ -57,8 +58,8 @@ esp32_ble_tracker:
}
ble_client:
- mac_address: ${bms_ble_mac_address}
id: ble_client${bms_id}
- id: ble_client${bms_id}
mac_address: ${bms_ble_mac_address}
jk_bms_ble:
- ble_client_id: ble_client${bms_id}
@@ -90,8 +91,10 @@ switch:
- platform: jk_bms_ble
jk_bms_ble_id: jk_bms_ble${bms_id}
charging:
id: bms${bms_id}_charge_switch
name: "${name} ${bms_name} Charge switch"
discharging:
id: bms${bms_id}_discharge_switch
name: "${name} ${bms_name} Discharge switch"
balancer:
name: "${name} ${bms_name} Balance switch"
@@ -121,6 +124,7 @@ sensor:
id: bms${bms_id}_delta_cell_voltage
name: "${name} ${bms_name} delta cell voltage"
average_cell_voltage:
id: bms${bms_id}_average_cell_voltage
name: "${name} ${bms_name} average cell voltage"
cell_voltage_1:
id: bms${bms_id}_cell_v_01
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.2.4
# Updated : 2025.01.28
# Version : 1.2.6
# GitHub : https://github.com/syssi/esphome-jk-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -25,6 +25,7 @@ packages:
bms_base: !include bms_base.yaml
bms_combine: !include bms_combine.yaml
bms_temperature_sensor: !include bms_temperature_sensor_2.yaml
bms_errors_bitmask: !include bms_errors_bitmask_JK-ALL_BLE.yaml
ota:
on_begin:
@@ -57,8 +58,8 @@ esp32_ble_tracker:
}
ble_client:
- mac_address: ${bms_ble_mac_address}
id: ble_client${bms_id}
- id: ble_client${bms_id}
mac_address: ${bms_ble_mac_address}
jk_bms_ble:
- ble_client_id: ble_client${bms_id}
@@ -90,8 +91,10 @@ switch:
- platform: jk_bms_ble
jk_bms_ble_id: jk_bms_ble${bms_id}
charging:
id: bms${bms_id}_charge_switch
name: "${name} ${bms_name} Charge switch"
discharging:
id: bms${bms_id}_discharge_switch
name: "${name} ${bms_name} Discharge switch"
balancer:
name: "${name} ${bms_name} Balance switch"
@@ -121,6 +124,7 @@ sensor:
id: bms${bms_id}_delta_cell_voltage
name: "${name} ${bms_name} delta cell voltage"
average_cell_voltage:
id: bms${bms_id}_average_cell_voltage
name: "${name} ${bms_name} average cell voltage"
total_voltage:
id: bms${bms_id}_total_voltage
@@ -0,0 +1,26 @@
# Updated : 2024.12.23
# 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:
bms_model: "JK"
bms_protocol: "BLE"
packages:
bms_sensors: !include bms_sensors_JK-ALL_BLE_standard.yaml
bms_combine: !include bms_combine.yaml
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.1.1
# Updated : 2025.01.16
# Version : 1.1.2
# GitHub : https://github.com/syssi/esphome-jk-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -174,6 +174,7 @@ sensor:
id: bms${bms_id}_temperature_sensor_2
name: "${name} ${bms_name} battery temperature"
average_cell_voltage:
id: bms${bms_id}_average_cell_voltage
name: "${name} ${bms_name} average cell voltage"
cell_voltage_1:
name: "${name} ${bms_name} cell voltage 01"
@@ -340,7 +341,7 @@ sensor:
# Alarm management is not supported at this time
# Internal : only specifying an id without a name will implicitly set this to true.
- platform: template
id: bms${bms_id}_errors_bitmask
id: bms${bms_id}_yambms_errors_bitmask
update_interval: ${bms_update_interval}
accuracy_decimals: 0
icon: mdi:alert-circle-outline
@@ -0,0 +1,26 @@
# Updated : 2024.12.23
# 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:
bms_model: "JK-B"
bms_protocol: "UART"
packages:
bms_sensors: !include bms_sensors_JK-B_UART_full.yaml
bms_combine: !include bms_combine.yaml
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.2.4
# Updated : 2025.01.25
# Version : 1.2.6
# GitHub : https://github.com/syssi/esphome-jk-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -25,6 +25,7 @@ packages:
bms_base: !include bms_base.yaml
bms_combine: !include bms_combine.yaml
bms_temperature_sensor: !include bms_temperature_sensor_2.yaml
bms_errors_bitmask: !include bms_errors_bitmask_JK-B_UART.yaml
# +--------------------------------------+
# | Component settings |
@@ -72,8 +73,10 @@ switch:
- platform: jk_bms
jk_bms_id: jk_bms${bms_id}
charging:
id: bms${bms_id}_charge_switch
name: "${name} ${bms_name} Charge switch"
discharging:
id: bms${bms_id}_discharge_switch
name: "${name} ${bms_name} Discharge switch"
# It is not possible to control the balancer from UART-TTL (confirmed by @syssi)
@@ -96,6 +99,7 @@ sensor:
id: bms${bms_id}_delta_cell_voltage
name: "${name} ${bms_name} delta cell voltage"
average_cell_voltage:
id: bms${bms_id}_average_cell_voltage
name: "${name} ${bms_name} average cell voltage"
power_tube_temperature:
id: bms${bms_id}_power_tube_temperature
@@ -0,0 +1,22 @@
# Updated : 2025.03.30
# 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>.
packages:
bms_sensors: !include bms_sensors_JK-PB_RS485_bms_full.yaml
bms_combine: !include bms_combine.yaml
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.2.2
# Updated : 2025.01.25
# Version : 1.2.4
# GitHub : https://github.com/txubelaxu/esphome-jk-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -21,6 +21,7 @@ packages:
bms_base: !include bms_base.yaml
bms_combine: !include bms_combine.yaml
bms_temperature_sensor: !include bms_temperature_sensor_5.yaml
bms_errors_bitmask: !include bms_errors_bitmask_JK-PB_RS485.yaml
# +--------------------------------------+
# | Component settings |
@@ -28,7 +29,7 @@ packages:
jk_rs485_bms:
- id: jk_rs485_bms${bms_id}
rs485_address: ${bms_rs485_address}
rs485_address: ${bms_address}
jk_rs485_sniffer_id: ${sniffer_id}
update_interval: ${bms_update_interval}
@@ -42,11 +43,12 @@ switch:
precharging:
name: "${name} ${bms_name} precharging"
charging:
id: bms${bms_id}_charge_switch
name: "${name} ${bms_name} charging"
discharging:
id: bms${bms_id}_discharge_switch
name: "${name} ${bms_name} discharging"
balancing:
id: bms${bms_id}_switch_balancing
name: "${name} ${bms_name} balancing"
emergency:
name: "${name} ${bms_name} emergency"
@@ -111,6 +113,7 @@ sensor:
cell_delta_voltage:
name: "${name} ${bms_name} cell delta voltage"
cell_average_voltage:
id: bms${bms_id}_average_cell_voltage
name: "${name} ${bms_name} cell average voltage"
cell_resistance_min:
name: "${name} ${bms_name} cell resistance min"
@@ -0,0 +1,22 @@
# Updated : 2025.03.30
# 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>.
packages:
bms_sensors: !include bms_sensors_JK-PB_RS485_bms_standard.yaml
bms_combine: !include bms_combine.yaml
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.2.5
# Updated : 2025.01.25
# Version : 1.2.7
# GitHub : https://github.com/txubelaxu/esphome-jk-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -29,9 +29,12 @@ logger:
# +--------------------------------------+
external_components:
- source: github://txubelaxu/esphome-jk-bms@main
refresh: 0s
components: [ jk_rs485_sniffer , jk_rs485_bms ]
- source: github://Sleeper85/esphome-components@main
refresh: 0s
components: [ jk_rs485_sniffer , jk_rs485_bms ]
# - source:
# type: local
# path: ../esphome-components/components
jk_rs485_sniffer:
- id: ${sniffer_id}
@@ -45,9 +48,9 @@ jk_rs485_sniffer:
switch:
- platform: template
name: ${name} JK-PB RS485 sniffer Broadcast changes to all BMS
name: ${name} Broadcasting JK-PB settings to all BMS
icon: "mdi:cast"
restore_mode: RESTORE_DEFAULT_ON
restore_mode: RESTORE_DEFAULT_OFF
optimistic: true
entity_category: config
turn_on_action:
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.2.5
# Updated : 2025.01.25
# Version : 1.2.7
# GitHub : https://github.com/txubelaxu/esphome-jk-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -29,9 +29,12 @@ logger:
# +--------------------------------------+
external_components:
- source: github://txubelaxu/esphome-jk-bms@main
refresh: 0s
components: [ jk_rs485_sniffer , jk_rs485_bms ]
- source: github://Sleeper85/esphome-components@main
refresh: 0s
components: [ jk_rs485_sniffer , jk_rs485_bms ]
# - source:
# type: local
# path: ../esphome-components/components
jk_rs485_sniffer:
- id: ${sniffer_id}
@@ -46,9 +49,9 @@ jk_rs485_sniffer:
switch:
- platform: template
name: ${name} JK-PB RS485 sniffer Broadcast changes to all BMS
name: ${name} Broadcasting JK-PB settings to all BMS
icon: "mdi:cast"
restore_mode: RESTORE_DEFAULT_ON
restore_mode: RESTORE_DEFAULT_OFF
optimistic: true
entity_category: config
turn_on_action:
@@ -1,5 +1,5 @@
# Updated : 2024.11.11
# Version : 1.1.1
# Updated : 2025.01.16
# Version : 1.1.2
# GitHub : https://github.com/syssi/esphome-seplos-bms
# YamBMS ( Yet another multi-BMS Merging Solution )
@@ -36,7 +36,7 @@ external_components:
seplos_bms:
- id: seplos_bms${bms_id}
address: ${bms_rs485_address}
address: ${bms_address}
protocol_version: ${bms_protocol_version}
seplos_modbus_id: ${seplos_modbus_id}
update_interval: ${bms_update_interval}
@@ -63,6 +63,7 @@ sensor:
delta_cell_voltage:
name: "${name} ${bms_name} delta cell voltage"
average_cell_voltage:
id: bms${bms_id}_average_cell_voltage
name: "${name} ${bms_name} average cell voltage"
cell_voltage_1:
name: "${name} ${bms_name} cell voltage 01"
@@ -215,7 +216,7 @@ sensor:
# Alarm management is not supported at this time
# Internal : only specifying an id without a name will implicitly set this to true.
- platform: template
id: bms${bms_id}_errors_bitmask
id: bms${bms_id}_yambms_errors_bitmask
update_interval: ${bms_update_interval}
accuracy_decimals: 0
icon: mdi:alert-circle-outline
@@ -226,7 +227,6 @@ sensor:
lambda: return 0;
binary_sensor:
# Required sensors cannot be retrieved from BMS
# Required sensors cannot be retrieved from BMS
# online_status
- platform: template
+444
View File
@@ -0,0 +1,444 @@
# Updated : 2025.01.25
# 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>.
substitutions:
bms_model: "YamBMS"
bms_protocol: "Modbus"
packages:
bms_combine: !include bms_combine.yaml
# +--------------------------------------+
# | Component settings |
# +--------------------------------------+
modbus_controller:
- id: modbus_controller${bms_id}
modbus_id: modbus_client
setup_priority: -10
address: ${bms_id}
update_interval: ${modbus_update_interval}
command_throttle: ${modbus_command_throttle}
max_cmd_retries: 3
# offline_skip_updates: 5
on_online:
then:
- logger.log: "BMS ${bms_id} modbus server back online !"
on_offline:
then:
- logger.log: "BMS ${bms_id} modbus server goes offline !"
- lambda: id(bms${bms_id}_online_status).publish_state(false);
# +--------------------------------------+
# | Component entities |
# +--------------------------------------+
binary_sensor:
# online_status
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_online_status
name: "${name} ${bms_name} Online Status"
register_type: read
address: 1
# charging_allowed
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_charging_allowed
name: "${name} ${bms_name} Charging allowed"
register_type: read
address: 2
# discharging_allowed
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_discharging_allowed
name: "${name} ${bms_name} Discharging allowed"
register_type: read
address: 3
# equalizing
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_equalizing
name: "${name} ${bms_name} Equalizing state"
register_type: read
address: 4
sensor:
# total_voltage
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_total_voltage
name: "${name} ${bms_name} Total Voltage"
register_type: read
address: 5
value_type: U_DWORD
accuracy_decimals: 2
unit_of_measurement: V
device_class: voltage
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.01
# current
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_current
name: "${name} ${bms_name} Current"
register_type: read
address: 7
value_type: S_DWORD
accuracy_decimals: 2
unit_of_measurement: A
device_class: current
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.01
# power
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_power
name: "${name} ${bms_name} Power"
register_type: read
address: 9
value_type: S_DWORD
accuracy_decimals: 2
unit_of_measurement: W
device_class: power
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.01
# battery_soc
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_battery_soc
name: "${name} ${bms_name} SoC"
register_type: read
address: 11
value_type: U_WORD
accuracy_decimals: 0
unit_of_measurement: '%'
device_class: battery
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# battery_capacity
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_battery_capacity
name: "${name} ${bms_name} Battery Capacity"
register_type: read
address: 12
value_type: U_WORD
accuracy_decimals: 0
unit_of_measurement: Ah
device_class: energy_storage
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# battery_capacity_ah
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_capacity_remaining_ah
name: "${name} ${bms_name} Capacity Remaining"
register_type: read
address: 13
value_type: U_WORD
accuracy_decimals: 0
unit_of_measurement: Ah
device_class: energy_storage
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# charging_cycles
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_charging_cycles
name: "${name} ${bms_name} charging cycles"
register_type: read
address: 14
value_type: U_WORD
accuracy_decimals: 0
icon: mdi:counter
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# max_charge_current
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_max_charge_current
name: "${name} ${bms_name} Max Charge Current"
register_type: read
address: 15
value_type: U_WORD
accuracy_decimals: 0
unit_of_measurement: A
icon: mdi:current-dc
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# max_discharge_current
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_max_discharge_current
name: "${name} ${bms_name} Max Discharge Current"
register_type: read
address: 16
value_type: U_WORD
accuracy_decimals: 0
unit_of_measurement: A
icon: mdi:current-dc
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# max_cell_voltage
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_max_cell_voltage
name: "${name} ${bms_name} Max Cell Voltage"
register_type: read
address: 17
value_type: U_WORD
accuracy_decimals: 3
unit_of_measurement: V
device_class: voltage
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.001
# max_voltage_cell
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_max_voltage_cell
name: "${name} ${bms_name} Max Voltage Cell"
register_type: read
address: 18
value_type: U_WORD
accuracy_decimals: 0
icon: mdi:numeric
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# min_cell_voltage
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_min_cell_voltage
name: "${name} ${bms_name} Min Cell Voltage"
register_type: read
address: 19
value_type: U_WORD
accuracy_decimals: 3
unit_of_measurement: V
device_class: voltage
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.001
# min_voltage_cell
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_min_voltage_cell
name: "${name} ${bms_name} Min Voltage Cell"
register_type: read
address: 20
value_type: U_WORD
accuracy_decimals: 0
icon: mdi:numeric
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# min_temperature
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_min_temperature
name: "${name} ${bms_name} Min temperature"
register_type: read
address: 21
value_type: S_WORD
accuracy_decimals: 1
unit_of_measurement: °C
device_class: temperature
filters:
- multiply: 0.1
- or:
- throttle: 10s
- delta: 0.1
# min_temperature_sensor
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_min_temperature_sensor
name: "${name} ${bms_name} Min temperature sensor"
register_type: read
address: 22
value_type: U_WORD
accuracy_decimals: 0
icon: mdi:numeric
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# max_temperature
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_max_temperature
name: "${name} ${bms_name} Max temperature"
register_type: read
address: 23
value_type: S_WORD
accuracy_decimals: 1
unit_of_measurement: °C
device_class: temperature
filters:
- multiply: 0.1
- or:
- throttle: 10s
- delta: 0.1
# max_temperature_sensor
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_max_temperature_sensor
name: "${name} ${bms_name} Max temperature sensor"
register_type: read
address: 24
value_type: U_WORD
accuracy_decimals: 0
icon: mdi:numeric
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# cell_ovp
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_cell_ovp
name: "${name} ${bms_name} Cell OVP"
register_type: read
address: 25
value_type: U_WORD
accuracy_decimals: 3
unit_of_measurement: V
device_class: voltage
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.001
# cell_uvp
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_cell_uvp
name: "${name} ${bms_name} Cell UVP"
register_type: read
address: 26
value_type: U_WORD
accuracy_decimals: 3
unit_of_measurement: V
device_class: voltage
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.001
# balance_trigger_voltage
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_balance_trigger_voltage
name: "${name} ${bms_name} Balance Trigger Voltage"
register_type: read
address: 27
value_type: U_WORD
accuracy_decimals: 3
unit_of_measurement: V
device_class: voltage
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.001
# errors_bitmask (16bits)
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_yambms_errors_bitmask
name: "${name} ${bms_name} YamBMS Errors Bitmask"
register_type: read
address: 28
value_type: U_WORD
accuracy_decimals: 0
icon: mdi:alert-circle-outline
filters:
- multiply: 1
- or:
- throttle: 10s
- delta: 1
# charging_power
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_charging_power
name: "${name} ${bms_name} Charging Power"
register_type: read
address: 29
value_type: U_DWORD
accuracy_decimals: 2
unit_of_measurement: W
device_class: power
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.01
# discharging_power
- platform: modbus_controller
modbus_controller_id: modbus_controller${bms_id}
id: bms${bms_id}_discharging_power
name: "${name} ${bms_name} Discharging Power"
register_type: read
address: 31
value_type: U_DWORD
accuracy_decimals: 2
unit_of_measurement: W
device_class: power
filters:
- multiply: 0.001
- or:
- throttle: 10s
- delta: 0.01
+97
View File
@@ -0,0 +1,97 @@
# Updated : 2025.01.25
# Version : 1.1.2
# 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>.
# +--------------------------------------+
# | JBD UART Errors Bitmask (16bit) |
# +--------------------------------------+
# Bit 0 Cell overvoltage 0000 0000 0000 0001 0x0001
# Bit 1 Cell undervoltage 0000 0000 0000 0010 0x0002
# Bit 2 Pack overvoltage 0000 0000 0000 0100 0x0004
# Bit 3 Pack undervoltage 0000 0000 0000 1000 0x0008
# Bit 4 Charging overtemperature 0000 0000 0001 0000 0x0010
# Bit 5 Charging undertemperature 0000 0000 0010 0000 0x0020
# Bit 6 Discharging overtemperature 0000 0000 0100 0000 0x0040
# Bit 7 Discharging undertemperature 0000 0000 1000 0000 0x0080
# Bit 8 Charging overcurrent 0000 0001 0000 0000 0x0100
# Bit 9 Discharging overcurrent 0000 0010 0000 0000 0x0200
# Bit 10 Short circuit 0000 0100 0000 0000 0x0400
# Bit 11 IC front-end error 0000 1000 0000 0000 0x0800
# Bit 12 Mosfet Software Lock 0001 0000 0000 0000 0x1000
# Bit 13 Charge timeout Close 0010 0000 0000 0000 0x2000
# Bit 14 Reserved 0100 0000 0000 0000 0x4000
# Bit 15 Reserved 1000 0000 0000 0000 0x8000
# +--------------------------------------+
# | YamBMS Errors Bitmask (16bit) |
# +--------------------------------------+
# Bit 0 General alarm 0000 0000 0000 0001 0x0001
# Bit 1 Battery high voltage alarm 0000 0000 0000 0010 0x0002
# Bit 2 Battery low voltage alarm 0000 0000 0000 0100 0x0004
# Bit 3 Battery high temperature alarm 0000 0000 0000 1000 0x0008
# Bit 4 Battery low temperature alarm 0000 0000 0001 0000 0x0010
# Bit 5 Battery high temperature charge alarm 0000 0000 0010 0000 0x0020
# Bit 6 Battery low temperature charge alarm 0000 0000 0100 0000 0x0040
# Bit 7 Battery high discharge current alarm 0000 0000 1000 0000 0x0080
# Bit 8 Battery high charge current alarm 0000 0001 0000 0000 0x0100
# Bit 9 Contactor alarm 0000 0010 0000 0000 0x0200
# Bit 10 Short circuit alarm 0000 0100 0000 0000 0x0400
# Bit 11 BMS internal alarm 0000 1000 0000 0000 0x0800
# Bit 12 Cell imbalance alarm 0001 0000 0000 0000 0x1000
# Bit 13 Reserved 0010 0000 0000 0000 0x2000
# Bit 14 Reserved 0100 0000 0000 0000 0x4000
# Bit 15 Reserved 1000 0000 0000 0000 0x8000
sensor:
- platform: template
id: bms${bms_id}_yambms_errors_bitmask
name: "${name} ${bms_name} YamBMS Errors Bitmask"
update_interval: ${bms_update_interval}
accuracy_decimals: 0
icon: mdi:alert-circle-outline
filters:
- or:
- throttle: 10s
- delta: 1
lambda: |-
uint16_t bms_errors_bitmask = id(bms${bms_id}_errors_bitmask).state;
uint16_t yambms_errors_bitmask = 0;
if (bms_errors_bitmask > 0)
{
if (bms_errors_bitmask & 0x0001) yambms_errors_bitmask |= 0x0002;
if (bms_errors_bitmask & 0x0002) yambms_errors_bitmask |= 0x0004;
if (bms_errors_bitmask & 0x0004) yambms_errors_bitmask |= 0x0002;
if (bms_errors_bitmask & 0x0008) yambms_errors_bitmask |= 0x0004;
if (bms_errors_bitmask & 0x0010) yambms_errors_bitmask |= 0x0020;
if (bms_errors_bitmask & 0x0020) yambms_errors_bitmask |= 0x0040;
if (bms_errors_bitmask & 0x0040) yambms_errors_bitmask |= 0x0008;
if (bms_errors_bitmask & 0x0080) yambms_errors_bitmask |= 0x0010;
if (bms_errors_bitmask & 0x0100) yambms_errors_bitmask |= 0x0100;
if (bms_errors_bitmask & 0x0200) yambms_errors_bitmask |= 0x0080;
if (bms_errors_bitmask & 0x0400) yambms_errors_bitmask |= 0x0400;
if (bms_errors_bitmask & 0x0800) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x1000) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x2000) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x4000) yambms_errors_bitmask |= 0x0000;
if (bms_errors_bitmask & 0x8000) yambms_errors_bitmask |= 0x0000;
}
return yambms_errors_bitmask;
@@ -0,0 +1,97 @@
# Updated : 2025.01.25
# Version : 1.1.2
# 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>.
# +--------------------------------------+
# | JK-ALL BLE Errors Bitmask (16bit) |
# +--------------------------------------+
# Bit 0 Charge overtemperature 0000 0000 0000 0001 0x0001
# Bit 1 Charge undertemperature 0000 0000 0000 0010 0x0002
# Bit 2 Coprocessor communication error 0000 0000 0000 0100 0x0004
# Bit 3 Cell undervoltage 0000 0000 0000 1000 0x0008
# Bit 4 Battery pack undervoltage 0000 0000 0001 0000 0x0010
# Bit 5 Discharge overcurrent 0000 0000 0010 0000 0x0020
# Bit 6 Discharge short circuit 0000 0000 0100 0000 0x0040
# Bit 7 Discharge overtemperature 0000 0000 1000 0000 0x0080
# Bit 8 Wire resistance 0000 0001 0000 0000 0x0100
# Bit 9 Mosfet overtemperature 0000 0010 0000 0000 0x0200
# Bit 10 Cell count is not equal to settings 0000 0100 0000 0000 0x0400
# Bit 11 Current sensor anomaly 0000 1000 0000 0000 0x0800
# Bit 12 Cell Overvoltage 0001 0000 0000 0000 0x1000
# Bit 13 Battery pack overvoltage 0010 0000 0000 0000 0x2000
# Bit 14 Charge overcurrent protection 0100 0000 0000 0000 0x4000
# Bit 15 Charge short circuit 1000 0000 0000 0000 0x8000
# +--------------------------------------+
# | YamBMS Errors Bitmask (16bit) |
# +--------------------------------------+
# Bit 0 General alarm 0000 0000 0000 0001 0x0001
# Bit 1 Battery high voltage alarm 0000 0000 0000 0010 0x0002
# Bit 2 Battery low voltage alarm 0000 0000 0000 0100 0x0004
# Bit 3 Battery high temperature alarm 0000 0000 0000 1000 0x0008
# Bit 4 Battery low temperature alarm 0000 0000 0001 0000 0x0010
# Bit 5 Battery high temperature charge alarm 0000 0000 0010 0000 0x0020
# Bit 6 Battery low temperature charge alarm 0000 0000 0100 0000 0x0040
# Bit 7 Battery high discharge current alarm 0000 0000 1000 0000 0x0080
# Bit 8 Battery high charge current alarm 0000 0001 0000 0000 0x0100
# Bit 9 Contactor alarm 0000 0010 0000 0000 0x0200
# Bit 10 Short circuit alarm 0000 0100 0000 0000 0x0400
# Bit 11 BMS internal alarm 0000 1000 0000 0000 0x0800
# Bit 12 Cell imbalance alarm 0001 0000 0000 0000 0x1000
# Bit 13 Reserved 0010 0000 0000 0000 0x2000
# Bit 14 Reserved 0100 0000 0000 0000 0x4000
# Bit 15 Reserved 1000 0000 0000 0000 0x8000
sensor:
- platform: template
id: bms${bms_id}_yambms_errors_bitmask
name: "${name} ${bms_name} YamBMS Errors Bitmask"
update_interval: ${bms_update_interval}
accuracy_decimals: 0
icon: mdi:alert-circle-outline
filters:
- or:
- throttle: 10s
- delta: 1
lambda: |-
uint16_t bms_errors_bitmask = id(bms${bms_id}_errors_bitmask).state;
uint16_t yambms_errors_bitmask = 0;
if (bms_errors_bitmask > 0)
{
if (bms_errors_bitmask & 0x0001) yambms_errors_bitmask |= 0x0020;
if (bms_errors_bitmask & 0x0002) yambms_errors_bitmask |= 0x0040;
if (bms_errors_bitmask & 0x0004) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x0008) yambms_errors_bitmask |= 0x0004;
if (bms_errors_bitmask & 0x0010) yambms_errors_bitmask |= 0x0004;
if (bms_errors_bitmask & 0x0020) yambms_errors_bitmask |= 0x0080;
if (bms_errors_bitmask & 0x0040) yambms_errors_bitmask |= 0x0400;
if (bms_errors_bitmask & 0x0080) yambms_errors_bitmask |= 0x0008;
if (bms_errors_bitmask & 0x0100) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x0200) yambms_errors_bitmask |= 0x0008;
if (bms_errors_bitmask & 0x0400) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x0800) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x1000) yambms_errors_bitmask |= 0x0002;
if (bms_errors_bitmask & 0x2000) yambms_errors_bitmask |= 0x0002;
if (bms_errors_bitmask & 0x4000) yambms_errors_bitmask |= 0x0100;
if (bms_errors_bitmask & 0x8000) yambms_errors_bitmask |= 0x0400;
}
return yambms_errors_bitmask;
@@ -0,0 +1,97 @@
# Updated : 2025.01.25
# Version : 1.1.2
# 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>.
# +--------------------------------------+
# | JK-B UART Errors Bitmask (16bit) |
# +--------------------------------------+
# Bit 0 Low capacity 0000 0000 0000 0001 0x0001
# Bit 1 Power tube overtemperature 0000 0000 0000 0010 0x0002
# Bit 2 Charging overvoltage 0000 0000 0000 0100 0x0004
# Bit 3 Discharging undervoltage 0000 0000 0000 1000 0x0008
# Bit 4 Battery overtemperature 0000 0000 0001 0000 0x0010
# Bit 5 Charging overcurrent 0000 0000 0010 0000 0x0020
# Bit 6 Discharging overcurrent 0000 0000 0100 0000 0x0040
# Bit 7 Cell pressure difference 0000 0000 1000 0000 0x0080
# Bit 8 Battery box overtemperature 0000 0001 0000 0000 0x0100
# Bit 9 Battery undertemperature 0000 0010 0000 0000 0x0200
# Bit 10 Cell overvoltage 0000 0100 0000 0000 0x0400
# Bit 11 Cell undervoltage 0000 1000 0000 0000 0x0800
# Bit 12 309_A protection 0001 0000 0000 0000 0x1000
# Bit 13 309_A protection 0010 0000 0000 0000 0x2000
# Bit 14 Reserved 0100 0000 0000 0000 0x4000
# Bit 15 Reserved 1000 0000 0000 0000 0x8000
# +--------------------------------------+
# | YamBMS Errors Bitmask (16bit) |
# +--------------------------------------+
# Bit 0 General alarm 0000 0000 0000 0001 0x0001
# Bit 1 Battery high voltage alarm 0000 0000 0000 0010 0x0002
# Bit 2 Battery low voltage alarm 0000 0000 0000 0100 0x0004
# Bit 3 Battery high temperature alarm 0000 0000 0000 1000 0x0008
# Bit 4 Battery low temperature alarm 0000 0000 0001 0000 0x0010
# Bit 5 Battery high temperature charge alarm 0000 0000 0010 0000 0x0020
# Bit 6 Battery low temperature charge alarm 0000 0000 0100 0000 0x0040
# Bit 7 Battery high discharge current alarm 0000 0000 1000 0000 0x0080
# Bit 8 Battery high charge current alarm 0000 0001 0000 0000 0x0100
# Bit 9 Contactor alarm 0000 0010 0000 0000 0x0200
# Bit 10 Short circuit alarm 0000 0100 0000 0000 0x0400
# Bit 11 BMS internal alarm 0000 1000 0000 0000 0x0800
# Bit 12 Cell imbalance alarm 0001 0000 0000 0000 0x1000
# Bit 13 Reserved 0010 0000 0000 0000 0x2000
# Bit 14 Reserved 0100 0000 0000 0000 0x4000
# Bit 15 Reserved 1000 0000 0000 0000 0x8000
sensor:
- platform: template
id: bms${bms_id}_yambms_errors_bitmask
name: "${name} ${bms_name} YamBMS Errors Bitmask"
update_interval: ${bms_update_interval}
accuracy_decimals: 0
icon: mdi:alert-circle-outline
filters:
- or:
- throttle: 10s
- delta: 1
lambda: |-
uint16_t bms_errors_bitmask = id(bms${bms_id}_errors_bitmask).state;
uint16_t yambms_errors_bitmask = 0;
if (bms_errors_bitmask > 0)
{
if (bms_errors_bitmask & 0x0001) yambms_errors_bitmask |= 0x0000;
if (bms_errors_bitmask & 0x0002) yambms_errors_bitmask |= 0x0008;
if (bms_errors_bitmask & 0x0004) yambms_errors_bitmask |= 0x0002;
if (bms_errors_bitmask & 0x0008) yambms_errors_bitmask |= 0x0004;
if (bms_errors_bitmask & 0x0010) yambms_errors_bitmask |= 0x0008;
if (bms_errors_bitmask & 0x0020) yambms_errors_bitmask |= 0x0100;
if (bms_errors_bitmask & 0x0040) yambms_errors_bitmask |= 0x0080;
if (bms_errors_bitmask & 0x0080) yambms_errors_bitmask |= 0x1000;
if (bms_errors_bitmask & 0x0100) yambms_errors_bitmask |= 0x0008;
if (bms_errors_bitmask & 0x0200) yambms_errors_bitmask |= 0x0010;
if (bms_errors_bitmask & 0x0400) yambms_errors_bitmask |= 0x0002;
if (bms_errors_bitmask & 0x0800) yambms_errors_bitmask |= 0x0004;
if (bms_errors_bitmask & 0x1000) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x2000) yambms_errors_bitmask |= 0x0800;
if (bms_errors_bitmask & 0x4000) yambms_errors_bitmask |= 0x0000;
if (bms_errors_bitmask & 0x8000) yambms_errors_bitmask |= 0x0000;
}
return yambms_errors_bitmask;
Loaded 100 of 167 files, more files were not shown because too many files have changed in this diff. Show more