Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
c51e694197 | ||
|
|
802511f4d6 | ||
|
|
c83eddecd0 | ||
|
|
cf95333a36 | ||
|
|
5bb5eb99ad | ||
|
|
f5592a005e | ||
|
|
b1e6af7a57 | ||
|
|
5e8ac7f3b1 | ||
|
|
34722c13ce | ||
|
|
b3445c5e3c | ||
|
|
9859d4b0be | ||
|
|
6926f9ef9b | ||
|
|
fca0b6848d | ||
|
|
9b22639405 | ||
|
|
692eb525ca | ||
|
|
d56c2f1457 | ||
|
|
884d4219a6 | ||
|
|
9c4897d87e | ||
|
|
6b7c178093 | ||
|
|
557721f7f7 | ||
|
|
be71ac9340 | ||
|
|
74587aa5f7 | ||
|
|
ec10e09c18 | ||
|
|
0b5773c9c9 | ||
|
|
82493b0a6a | ||
|
|
e0ccd7d07d | ||
|
|
525436db44 | ||
|
|
5aed8e6267 | ||
|
|
5fe8583799 | ||
|
|
01462622d5 | ||
|
|
d0601905e6 | ||
|
|
3775c108ee | ||
|
|
b3bcfdef7e | ||
|
|
3c716fd085 | ||
|
|
7815119183 | ||
|
|
3b490821fe | ||
|
|
1b6c28e954 | ||
|
|
2046f44507 | ||
|
|
098546b65d | ||
|
|
eeee80faa7 | ||
|
|
c0240d44ed | ||
|
|
822b3394f6 | ||
|
|
a538ba3e6e | ||
|
|
95b69225ea | ||
|
|
eb9663b840 | ||
|
|
d5df679b9a | ||
|
|
669dee91d4 | ||
|
|
0424392349 | ||
|
|
c78bb0c465 | ||
|
|
1f3231df5f | ||
|
|
264b83ea8b | ||
|
|
529334683b | ||
|
|
1c4634c820 | ||
|
|
06ed27e8f0 | ||
|
|
de8927ce36 | ||
|
|
3c846ea24a | ||
|
|
a5e6423d03 | ||
|
|
44cb8504d3 | ||
|
|
63bce3f027 | ||
|
|
84c90c11d3 | ||
|
|
3dde676dd8 | ||
|
|
42151934bf | ||
|
|
a8233ea8c6 | ||
|
|
01c443e321 | ||
|
|
9977cc5963 | ||
|
|
f357d23751 | ||
|
|
ae276bb0eb | ||
|
|
f8b677a2b8 | ||
|
|
17d5edb2f0 | ||
|
|
3de5f0e080 | ||
|
|
c4313cc577 | ||
|
|
ea1859068d | ||
|
|
4115a33d87 | ||
|
|
4d52c3bbf8 | ||
|
|
3f9956f4d5 | ||
|
|
3127c7b3d7 | ||
|
|
da658defd8 | ||
|
|
4a0f3c6090 | ||
|
|
d889d091f7 | ||
|
|
bb764ceb01 | ||
|
|
7ec5fc02ac | ||
|
|
df3d9353b6 | ||
|
|
8777dc8688 | ||
|
|
c47b768573 | ||
|
|
e336ac315c | ||
|
|
56fd51e5d4 | ||
|
|
edd3beb0de | ||
|
|
5e1d7ac48e | ||
|
|
c552360fe0 | ||
|
|
088caecd47 | ||
|
|
af59e4307c | ||
|
|
b303244b77 | ||
|
|
91f961fcd6 | ||
|
|
f22ab83e19 | ||
|
|
97f9e38031 | ||
|
|
b4cd402337 | ||
|
|
25a2a88366 | ||
|
|
bdda35a837 | ||
|
|
7af47f5b2e | ||
|
|
0fa4c61667 | ||
|
|
e9e3600686 | ||
|
|
28323c7b29 | ||
|
|
2cb7ba3c6d | ||
|
|
91df96d70c | ||
|
|
6d67b2677c | ||
|
|
29e25e36b6 | ||
|
|
5b36fac1b9 | ||
|
|
58d9ebc02e | ||
|
|
203911fc36 | ||
|
|
0b980a7f42 | ||
|
|
0455cba2da | ||
|
|
cee37cd5b0 | ||
|
|
c7b8c29fbf | ||
|
|
d7de61c675 | ||
|
|
402d895a48 | ||
|
|
485c6cc5fb | ||
|
|
43f995a7a9 | ||
|
|
9b207b5484 | ||
|
|
13d4d78123 | ||
|
|
70a00ff733 | ||
|
|
f193e27e83 | ||
|
|
f79aca0a22 | ||
|
|
408ebb5116 | ||
|
|
f55b2d6601 | ||
|
|
c151f575dc | ||
|
|
b1c26c48dd | ||
|
|
24b90f4bd1 |
No files matched your search
@@ -0,0 +1 @@
|
||||
buy_me_a_coffee: sleeper85
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.1
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -26,7 +26,7 @@ views:
|
||||
cards:
|
||||
- graph: line
|
||||
type: sensor
|
||||
entity: sensor.yambms_yambms_1_total_voltage_o
|
||||
entity: sensor.yambms_yambms_1_total_voltage
|
||||
detail: 2
|
||||
layout_options:
|
||||
grid_columns: 2
|
||||
@@ -40,7 +40,7 @@ views:
|
||||
name: SoC
|
||||
hours_to_show: 8
|
||||
- type: gauge
|
||||
entity: sensor.yambms_yambms_1_current_s
|
||||
entity: sensor.yambms_yambms_1_current
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
@@ -53,7 +53,7 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 3
|
||||
- type: gauge
|
||||
entity: sensor.yambms_yambms_1_power_s
|
||||
entity: sensor.yambms_yambms_1_power
|
||||
needle: true
|
||||
severity:
|
||||
green: 0
|
||||
@@ -66,16 +66,16 @@ views:
|
||||
grid_columns: 2
|
||||
grid_rows: 3
|
||||
- type: tile
|
||||
entity: sensor.yambms_yambms_1_installed_battery_capacity_s
|
||||
entity: sensor.yambms_yambms_1_installed_battery_capacity
|
||||
name: Installed Battery Capacity
|
||||
- type: tile
|
||||
entity: sensor.yambms_yambms_1_battery_soh
|
||||
name: Battery SoH
|
||||
- type: tile
|
||||
entity: sensor.yambms_yambms_1_battery_capacity_s
|
||||
entity: sensor.yambms_yambms_1_battery_capacity
|
||||
name: Battery Capacity
|
||||
- type: tile
|
||||
entity: sensor.yambms_yambms_1_capacity_remaining_s
|
||||
entity: sensor.yambms_yambms_1_capacity_remaining
|
||||
name: Capacity Remaining
|
||||
- type: tile
|
||||
entity: sensor.yambms_yambms_1_delta_cell_voltage
|
||||
|
||||
@@ -8,7 +8,19 @@
|
||||
[](https://www.buymeacoffee.com/sleeper85)
|
||||
|
||||
> [!TIP]
|
||||
> If compiling the source code is too difficult for you, I can provide you a `custom firmware` that is easy to install from a web page. You can [contact me privately](https://diysolarforum.com/direct-messages/add?to=Sleeper85) on the DIY solar forum.
|
||||
> Not sure which YAML to choose ? ... `YamBMS_Remote_Packages_example.yaml` is a good basis for creating your custom YAML.
|
||||
> Examples of BMS and Shunt imports can be found in the [configuration_examples](configuration_examples/) folder.
|
||||
> You can mix different BMS models, the only condition is that they are numbered in order starting from `1`.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The current code for `YamBMS` and other components needs to be fixed to work with `esphome 2025.5.0`.
|
||||
> This will be done as soon as I have more time to devote to it. In the meantime, you should compile with `esphome 2025.4.2` or lower.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The most important thing for proper functioning of YamBMS is that **the voltage of your BMS is well calibrated**.
|
||||
> YamBMS logic is based on the `min_cell_voltage` and `max_cell_voltage` voltages of your BMS.
|
||||
> If you use YamBMS, the internal charging logic of the `JK-PB BMS` will not be used.
|
||||
> Please read the [documentation](README.md#contents) and the [setup instructions](documents/README/Schematic_and_setup_instructions.md).
|
||||
|
||||
| ESPHome application to monitor BMS and communicate with inverters<br>supporting CAN bus protocol compatible with Pylontech, GoodWe, SMA,<br>Victron or Luxpower (EG4). | <a href="https://www.buymeacoffee.com/Sleeper85" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a> |
|
||||
| :--- | --- |
|
||||
@@ -35,14 +47,6 @@
|
||||
|
||||
[Dedicated topic on DIY Solar Forum](https://diysolarforum.com/threads/yambms-jk-bms-can-with-new-cut-off-charging-logic-open-source.79325/)
|
||||
|
||||
## YamBMS
|
||||
|
||||

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

|
||||
|
||||
## Contents
|
||||
|
||||
1) [Supported devices](documents/README/Supported_devices.md)
|
||||
@@ -55,14 +59,52 @@
|
||||
8) [Installation procedure](documents/README/Installation_procedure.md)
|
||||
9) [Troubleshooting](documents/README/Troubleshooting.md)
|
||||
|
||||
## YamBMS
|
||||
|
||||

|
||||
|
||||
### 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.
|
||||
|
||||

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

|
||||
|
||||
## 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]
|
||||
> `YamBMS_DEMO_ESP32.factory.bin` is intended for a generic ESP32, does not work with ESP32-S3.
|
||||
> If you want to test `YamBMS DEMO` with another board you need to compile the firmware with the `multi-bms_DEMO.yaml`.
|
||||
> If you want to test `YamBMS DEMO` with another board you need to compile the firmware with the `YamBMS_RP_DEMO.yaml`.
|
||||
|
||||
1) Download [YamBMS_DEMO_ESP32.factory.bin](firmware/YamBMS_DEMO_ESP32.factory.bin)
|
||||
2) Follow the [procedure explained in this document](https://docs.google.com/document/d/12pOpaG4Iyw3DjC_kB1q0jjBeSKJHK2FvXI1swebL2RI/edit?usp=sharing).
|
||||
@@ -76,15 +118,70 @@ 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)
|
||||
|
||||
## Data collection
|
||||
|
||||
> [!NOTE]
|
||||
> For your information, in May 2025 there were `94` YamBMS users.
|
||||
|
||||
If the ESP32 has an internet connection, the following data is sent to [this script](http://script.opentel.be/yambms.post.php)
|
||||
for statistics collection. Only [@Sleeper85](https://github.com/Sleeper85) have access to this information for the production of statistics, the support and the update service.
|
||||
|
||||
- ESP32 MAC address
|
||||
- YamBMS version
|
||||
- Board chip
|
||||
- Board name
|
||||
- BMS model
|
||||
- BMS count
|
||||
- CAN bus name
|
||||
- CAN bus protocol
|
||||
- Uptime
|
||||
- Current date and time
|
||||
|
||||
## Changelog
|
||||
|
||||
|
||||
* YamBMS 1.5.5 :
|
||||
* New `main.yaml` with LP (local packages) and RP (remote packages) versions
|
||||
* New `board.yaml` with modular UART/CAN interfaces
|
||||
* The name of the JK `bms.yaml` is no longer linked to a specific model
|
||||
* SoC calculation is now based on remaining capacity for more accuracy (BMS only) [issues #39](https://github.com/Sleeper85/esphome-yambms/issues/39)
|
||||
* SoH calculation is moved to BMS level (for those who do not provide this information)
|
||||
* Improvement of the Victron SmartShunt doc [issues #38](https://github.com/Sleeper85/esphome-yambms/issues/38)
|
||||
* YamBMS 1.5.4 :
|
||||
* New low SoC corrected at each BMS level (the corrected SoC is the one transmitted to YamBMS)
|
||||
* New BMS dashboard
|
||||
* New end of charge logic at each BMS level, the charge switch turns off when the cells are equalized (disabled by default)
|
||||
* Fixed `errors_bitamsk` for JK-PB RS485, test OK with YamBMS (forked component)
|
||||
* YamBMS 1.5.3 :
|
||||
* Broadcasting JK-PB settings to all BMS set to OFF by default
|
||||
* Reorganizing the `board` folder and YAMLs (device_base.yaml moved to board.yaml)
|
||||
* `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 +214,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.
|
||||
@@ -1,5 +1,5 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.1
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
@@ -17,10 +17,14 @@
|
||||
# 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-demo
|
||||
######################## YamBMS Local Packages Version #########################
|
||||
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml file
|
||||
# You need to copy the `packages` folder into the same folder as this YAML in order to compile it.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
#
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
@@ -32,7 +36,7 @@ substitutions:
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: DEBUG # DEBUG / INFO / WARN
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
ota:
|
||||
platform: esphome
|
||||
@@ -47,17 +51,64 @@ api:
|
||||
# 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
|
||||
# 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
|
||||
# web_server:
|
||||
# port: 80
|
||||
# log: false
|
||||
# ota: false
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'yambms' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS Demo' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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 |
|
||||
@@ -66,29 +117,65 @@ 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
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
############### >>> UNCOMMENT YOUR BOARD <<< ###############
|
||||
############### >>> ONLY ONE 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_EVB.yaml
|
||||
# device_board: !include packages/board/board_ESP32_Atom-Lite.yaml
|
||||
# device_board: !include packages/board/board_ESP32-C3_DevKitM-1.yaml
|
||||
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_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'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
########### >>> UNCOMMENT YOUR BOARD OPTIONS <<< ###########
|
||||
|
||||
captive_portal: !include packages/board/board_options_captive_portal.yaml
|
||||
|
||||
# uart_esp_1: !include packages/board/board_options_itf_uart_esp_1.yaml
|
||||
# uart_esp_2: !include packages/board/board_options_itf_uart_esp_2.yaml
|
||||
# uart_esp_3: !include packages/board/board_options_itf_uart_esp_3.yaml
|
||||
|
||||
# ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
canbus_node_1: !include
|
||||
file: packages/board/board_options_itf_canbus_esp32_can.yaml
|
||||
vars:
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# MCP2515
|
||||
# canbus_node_2: !include
|
||||
# file: packages/board/board_options_itf_canbus_mcp2515.yaml
|
||||
# vars:
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
############################################################
|
||||
|
||||
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 +183,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
|
||||
@@ -112,6 +194,7 @@ packages:
|
||||
bms_current: '9.2' # A
|
||||
bms_power: '492' # W
|
||||
bms_soc: '87' # %
|
||||
bms_soh: '99' # %
|
||||
bms_min_cell_voltage: '3.339' # V
|
||||
bms_min_voltage_cell: '2' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.341' # V
|
||||
@@ -128,15 +211,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
|
||||
@@ -144,6 +222,7 @@ packages:
|
||||
bms_current: '11.3' # A
|
||||
bms_power: '604' # W
|
||||
bms_soc: '85' # %
|
||||
bms_soh: '89' # %
|
||||
bms_min_cell_voltage: '3.337' # V
|
||||
bms_min_voltage_cell: '14' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.339' # V
|
||||
@@ -160,15 +239,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
|
||||
@@ -176,6 +250,7 @@ packages:
|
||||
bms_current: '15.7' # A
|
||||
bms_power: '838' # W
|
||||
bms_soc: '83' # %
|
||||
bms_soh: '79' # %
|
||||
bms_min_cell_voltage: '3.334' # V
|
||||
bms_min_voltage_cell: '7' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.336' # V
|
||||
@@ -191,45 +266,14 @@ packages:
|
||||
bms_balance_trigger_voltage: '0.010' # V Used by 'Auto CVL' functions
|
||||
bms_charging_cycles: '194' # charging cycles number Used to calculate the SoH
|
||||
|
||||
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'
|
||||
# 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'
|
||||
yambms: !include packages/yambms/yambms.yaml
|
||||
|
||||
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'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
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
|
||||
@@ -0,0 +1,224 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Local Packages Version #########################
|
||||
|
||||
# You need to copy the `packages` folder into the same folder as this YAML in order to compile it.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
#
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'yambms' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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 |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
packages:
|
||||
|
||||
############### >>> UNCOMMENT YOUR BOARD <<< ###############
|
||||
############### >>> ONLY ONE 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_EVB.yaml
|
||||
# device_board: !include packages/board/board_ESP32_Atom-Lite.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'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
########### >>> UNCOMMENT YOUR BOARD OPTIONS <<< ###########
|
||||
|
||||
# RS485
|
||||
uart_esp_1: !include packages/board/board_options_itf_uart_esp_1.yaml
|
||||
|
||||
# ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
canbus_node_1: !include
|
||||
file: packages/board/board_options_itf_canbus_esp32_can.yaml
|
||||
vars:
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# MCP2515
|
||||
canbus_node_2: !include
|
||||
file: packages/board/board_options_itf_canbus_mcp2515.yaml
|
||||
vars:
|
||||
canbus_node_id: 'canbus_bms_1'
|
||||
# If you do not want to use the default settings, uncomment the options below :
|
||||
# canbus_can_id: '4'
|
||||
# canbus_bitrate: '500kbps'
|
||||
# spi_mosi_pin: '12'
|
||||
# spi_miso_pin: '5'
|
||||
# spi_clk_pin: '18'
|
||||
# mcp2515_cs_pin: '32'
|
||||
|
||||
############################################################
|
||||
|
||||
# Deye BMS top unit (required)
|
||||
bms_top: !include
|
||||
file: packages/bms/bms_sensors_DEYE_CAN_top_full.yaml
|
||||
vars:
|
||||
# CAN BUS ID
|
||||
canbus_id: 'canbus_bms_1'
|
||||
deye_name: 'DEYE-Top 1'
|
||||
deye_id: '1'
|
||||
|
||||
# Deye module 1
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_DEYE_CAN_module_full.yaml
|
||||
vars:
|
||||
# CAN BUS ID
|
||||
canbus_id: 'canbus_bms_1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'DEYE-BMS 1'
|
||||
deye_id: '1'
|
||||
deye_module_id: '0' # Modules are numbered with 0-9
|
||||
|
||||
# Deye module 2
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_DEYE_CAN_module_full.yaml
|
||||
vars:
|
||||
# CAN BUS ID
|
||||
canbus_id: 'canbus_bms_1'
|
||||
# BMS vars
|
||||
deye_id: '1'
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'DEYE-BMS 2'
|
||||
deye_module_id: '1' # Second module
|
||||
|
||||
yambms: !include packages/yambms/yambms.yaml
|
||||
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
canbus1: !include
|
||||
file: packages/yambms/yambms_canbus.yaml
|
||||
vars:
|
||||
canbus_id: 'canbus1'
|
||||
canbus_name: 'CANBUS 1'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -0,0 +1,301 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Local Packages Version #########################
|
||||
|
||||
# You need to copy the `packages` folder into the same folder as this YAML in order to compile it.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
#
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'yambms' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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 |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
packages:
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
############### >>> UNCOMMENT YOUR BOARD <<< ###############
|
||||
############### >>> ONLY ONE 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_EVB.yaml
|
||||
# device_board: !include packages/board/board_ESP32_Atom-Lite.yaml
|
||||
# device_board: !include packages/board/board_ESP32-C3_DevKitM-1.yaml
|
||||
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml
|
||||
device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_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'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
########### >>> UNCOMMENT YOUR BOARD OPTIONS <<< ###########
|
||||
|
||||
uart_esp_1: !include packages/board/board_options_itf_uart_esp_1.yaml
|
||||
# uart_esp_2: !include packages/board/board_options_itf_uart_esp_2.yaml
|
||||
# uart_esp_3: !include packages/board/board_options_itf_uart_esp_3.yaml
|
||||
|
||||
# ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
canbus_node_1: !include
|
||||
file: packages/board/board_options_itf_canbus_esp32_can.yaml
|
||||
vars:
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# MCP2515
|
||||
# canbus_node_2: !include
|
||||
# file: packages/board/board_options_itf_canbus_mcp2515.yaml
|
||||
# vars:
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
############################################################
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
|
||||
# vars:
|
||||
# shunt_id: '1' # must be a number
|
||||
# shunt_name: 'Shunt 1'
|
||||
# shunt_uart_id: 'uart_esp_3'
|
||||
|
||||
# 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_RS485_Modbus_sniffer_talk_pin.yaml
|
||||
# vars:
|
||||
# sniffer_id: 'sniffer1'
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
|
||||
|
||||
sniffer1: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
|
||||
# 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_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 DIP switch
|
||||
|
||||
bms4: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 DIP switch
|
||||
|
||||
bms5: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 DIP switch
|
||||
|
||||
bms6: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 DIP switch
|
||||
|
||||
bms7: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 DIP switch
|
||||
|
||||
bms8: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 DIP switch
|
||||
|
||||
yambms: !include packages/yambms/yambms.yaml
|
||||
|
||||
canbus1: !include
|
||||
file: packages/yambms/yambms_canbus.yaml
|
||||
vars:
|
||||
canbus_id: 'canbus1'
|
||||
canbus_name: 'CANBUS 1'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -0,0 +1,208 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Local Packages Version #########################
|
||||
|
||||
# You need to copy the `packages` folder into the same folder as this YAML in order to compile it.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
#
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'pvbrain2' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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)
|
||||
# +--------------------------------------+
|
||||
# | WK2168 UART expander |
|
||||
# +--------------------------------------+
|
||||
uart0_baudrate: '2400' #WKS {RJ45-UART0}
|
||||
uart1_baudrate: '38400' #JSY193
|
||||
uart2_baudrate: '19200' #SmartShunt
|
||||
uart3_baudrate: '9600' #SRNE {RJ45-UART3}
|
||||
uart4_baudrate: '115200' #JK-BMS 1
|
||||
uart5_baudrate: '115200' #JK-BMS 2
|
||||
uart6_baudrate: '115200' #Pylontech
|
||||
uart7_baudrate: '9600' #EPEVER {RJ45-UART7}
|
||||
|
||||
# +--------------------------------------+
|
||||
# | PVbrain2 packages |
|
||||
# +--------------------------------------+
|
||||
packages:
|
||||
|
||||
device_board: !include packages/board/board_ESP32-S3_DevKitC-1_PVbrain2.yaml
|
||||
|
||||
# BUS
|
||||
# bus_i2c0: !include pvbrain2/base/device_bus_i2c0.yaml # SX1509 and BME280/BMP280
|
||||
bus_spi1: !include pvbrain2/base/device_bus_spi1.yaml # MCP2515
|
||||
# bus_one_wire: !include pvbrain2/base/device_bus_one_wire.yaml # Dallas
|
||||
|
||||
# Devices
|
||||
# device_uart_esp: !include pvbrain2/base/device_uart_esp.yaml
|
||||
device_wk2168_spi: !include pvbrain2/base/device_wk2168_spi.yaml
|
||||
# device_wk2168_i2c: !include pvbrain2/base/device_wk2168_i2c.yaml
|
||||
# device_sx1509: !include pvbrain2/base/device_sx1509.yaml
|
||||
device_canbus_node1: !include pvbrain2/base/device_canbus_esp32can.yaml # canbus_node1
|
||||
device_canbus_node2: !include pvbrain2/base/device_canbus_mcp2515.yaml # canbus_node2
|
||||
|
||||
# +--------------------------------------+
|
||||
# | YamBMS packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
|
||||
shunt1: !include
|
||||
file: packages/shunt/shunt_combine_Victron_SmartShunt_UART_expander.yaml # shunt_combine_Junctek_KHF_UART.yaml
|
||||
vars:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
shunt_uart_id: 'uart_${uart_hub_bus}_2'
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_uart_id: 'uart_${uart_hub_bus}_4'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_uart_id: 'uart_${uart_hub_bus}_5'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
yambms: !include packages/yambms/yambms.yaml
|
||||
|
||||
canbus1: !include
|
||||
file: 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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -0,0 +1,222 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Local Packages Version #########################
|
||||
|
||||
# You need to copy the `packages` folder into the same folder as this YAML in order to compile it.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
#
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'yambms' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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 |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
packages:
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
############### >>> UNCOMMENT YOUR BOARD <<< ###############
|
||||
############### >>> ONLY ONE 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_EVB.yaml
|
||||
# device_board: !include packages/board/board_ESP32_Atom-Lite.yaml
|
||||
# device_board: !include packages/board/board_ESP32-C3_DevKitM-1.yaml
|
||||
# device_board: !include packages/board/board_ESP32-C3_ETH01-EVO.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml
|
||||
# device_board: !include packages/board/board_ESP32-S3_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'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
########### >>> UNCOMMENT YOUR BOARD OPTIONS <<< ###########
|
||||
|
||||
uart_esp_1: !include packages/board/board_options_itf_uart_esp_1.yaml
|
||||
uart_esp_2: !include packages/board/board_options_itf_uart_esp_2.yaml
|
||||
uart_esp_3: !include packages/board/board_options_itf_uart_esp_3.yaml
|
||||
|
||||
# ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
canbus_node_1: !include
|
||||
file: packages/board/board_options_itf_canbus_esp32_can.yaml
|
||||
vars:
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# MCP2515
|
||||
# canbus_node_2: !include
|
||||
# file: packages/board/board_options_itf_canbus_mcp2515.yaml
|
||||
# vars:
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
############################################################
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
|
||||
shunt1: !include
|
||||
file: packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml # shunt_combine_Junctek_KHF_UART.yaml
|
||||
vars:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
shunt_uart_id: 'uart_esp_3'
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_uart_id: 'uart_esp_1'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_uart_id: 'uart_esp_2'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
yambms: !include packages/yambms/yambms.yaml
|
||||
|
||||
canbus1: !include
|
||||
file: packages/yambms/yambms_canbus.yaml
|
||||
vars:
|
||||
canbus_id: 'canbus1'
|
||||
canbus_name: 'CANBUS 1'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -0,0 +1,323 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'yambms' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS Demo' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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 |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
packages:
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
############### >>> UNCOMMENT YOUR BOARD <<< ###############
|
||||
############### >>> ONLY ONE BOARD ! <<< ###############
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3R.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
########### >>> UNCOMMENT YOUR BOARD OPTIONS <<< ###########
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Captive Portal
|
||||
- path: 'packages/board/board_options_captive_portal.yaml'
|
||||
# UART 1
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
# UART 2
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_2.yaml'
|
||||
# UART 3
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# MCP2515
|
||||
# - path: 'packages/board/board_options_itf_canbus_mcp2515.yaml'
|
||||
# vars:
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
############################################################
|
||||
|
||||
shunt:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Shunt 1
|
||||
- path: 'packages/shunt/shunt_combine_FAKE.yaml'
|
||||
vars:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
# Shunt sensors values
|
||||
shunt_voltage: '53.41' # V
|
||||
shunt_current: '37.5' # A
|
||||
shunt_power: '2003' # W
|
||||
shunt_soc: '86' # %
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_FAKE.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
# 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_soh: '98' # %
|
||||
bms_min_cell_voltage: '3.339' # V
|
||||
bms_min_voltage_cell: '2' # cell number 1~16
|
||||
bms_max_cell_voltage: '3.341' # V
|
||||
bms_max_voltage_cell: '11' # cell number 1~16
|
||||
bms_temperature_sensor_1: '21.1' # °C
|
||||
bms_temperature_sensor_2: '21.3' # °C
|
||||
bms_temperature_sensor_3: '21.5' # °C
|
||||
bms_temperature_sensor_4: '21.7' # °C
|
||||
bms_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
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_FAKE.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
# 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_soh: '89' # %
|
||||
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
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_FAKE.yaml'
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'BMS 3'
|
||||
# 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_soh: '79' # %
|
||||
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
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
canbus:
|
||||
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_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (0x305 frame) for 5s
|
||||
# The Deye inverter sends the ACK 0x305 only when it receives the 0x356 frame.
|
||||
canbus_link_timer: '5s'
|
||||
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
@@ -0,0 +1,316 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'yambms' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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 |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
packages:
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
############### >>> UNCOMMENT YOUR BOARD <<< ###############
|
||||
############### >>> ONLY ONE BOARD ! <<< ###############
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# - path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
- path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3R.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
########### >>> UNCOMMENT YOUR BOARD OPTIONS <<< ###########
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# UART 1
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
# UART 2
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_2.yaml'
|
||||
# UART 3
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# MCP2515
|
||||
# - path: 'packages/board/board_options_itf_canbus_mcp2515.yaml'
|
||||
# vars:
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
############################################################
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
|
||||
# shunt:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# files:
|
||||
# # Shunt 1
|
||||
# - path: 'packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml' # shunt_combine_Junctek_KHF_UART.yaml
|
||||
# vars:
|
||||
# shunt_id: '1' # must be a number
|
||||
# shunt_name: 'Shunt 1'
|
||||
# shunt_uart_id: 'uart_esp_3'
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# RS485 Sniffer
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml'
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 ( JK app `Device Addr.` setting )
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 ( JK app `Device Addr.` setting )
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 ( JK app `Device Addr.` setting )
|
||||
# BMS 4
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 ( JK app `Device Addr.` setting )
|
||||
# BMS 5
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 ( JK app `Device Addr.` setting )
|
||||
# BMS 6
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 ( JK app `Device Addr.` setting )
|
||||
# BMS 7
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 ( JK app `Device Addr.` setting )
|
||||
# BMS 8
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_JK-B_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 ( JK app `Device Addr.` setting )
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
canbus:
|
||||
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_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (0x305 frame) for 5s
|
||||
# The Deye inverter sends the ACK 0x305 only when it receives the 0x356 frame.
|
||||
canbus_link_timer: '5s'
|
||||
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
@@ -0,0 +1,316 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'yambms' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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 |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
packages:
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
############### >>> UNCOMMENT YOUR BOARD <<< ###############
|
||||
############### >>> ONLY ONE BOARD ! <<< ###############
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# - path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
- path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3R.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
########### >>> UNCOMMENT YOUR BOARD OPTIONS <<< ###########
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# UART 1
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
# UART 2
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_2.yaml'
|
||||
# UART 3
|
||||
# - path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# MCP2515
|
||||
# - path: 'packages/board/board_options_itf_canbus_mcp2515.yaml'
|
||||
# vars:
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
############################################################
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
|
||||
# shunt:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# files:
|
||||
# # Shunt 1
|
||||
# - path: 'packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml' # shunt_combine_Junctek_KHF_UART.yaml
|
||||
# vars:
|
||||
# shunt_id: '1' # must be a number
|
||||
# shunt_name: 'Shunt 1'
|
||||
# shunt_uart_id: 'uart_esp_3'
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# RS485 Sniffer
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml'
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 DIP switch
|
||||
# BMS 4
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 DIP switch
|
||||
# BMS 5
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 DIP switch
|
||||
# BMS 6
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 DIP switch
|
||||
# BMS 7
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 DIP switch
|
||||
# BMS 8
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 DIP switch
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
canbus:
|
||||
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_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (0x305 frame) for 5s
|
||||
# The Deye inverter sends the ACK 0x305 only when it receives the 0x356 frame.
|
||||
canbus_link_timer: '5s'
|
||||
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
@@ -0,0 +1,234 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'pvbrain2' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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)
|
||||
# +--------------------------------------+
|
||||
# | WK2168 UART expander |
|
||||
# +--------------------------------------+
|
||||
uart0_baudrate: '2400' #WKS {RJ45-UART0}
|
||||
uart1_baudrate: '38400' #JSY193
|
||||
uart2_baudrate: '19200' #SmartShunt
|
||||
uart3_baudrate: '9600' #SRNE {RJ45-UART3}
|
||||
uart4_baudrate: '115200' #JK-BMS 1
|
||||
uart5_baudrate: '115200' #JK-BMS 2
|
||||
uart6_baudrate: '115200' #Pylontech
|
||||
uart7_baudrate: '9600' #EPEVER {RJ45-UART7}
|
||||
|
||||
# +--------------------------------------+
|
||||
# | PVbrain2 packages |
|
||||
# +--------------------------------------+
|
||||
packages:
|
||||
|
||||
pvbrain2:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32-S3_DevKitC-1_PVbrain2.yaml'
|
||||
# BUS
|
||||
# - path: 'pvbrain2/base/device_bus_i2c0.yaml' # SX1509 and BME280/BMP280
|
||||
- path: 'pvbrain2/base/device_bus_spi1.yaml' # MCP2515
|
||||
- path: 'pvbrain2/base/device_bus_one_wire.yaml' # Dallas
|
||||
# Devices
|
||||
# - path: 'pvbrain2/base/device_uart_esp.yaml'
|
||||
- path: 'pvbrain2/base/device_wk2168_spi.yaml'
|
||||
# - path: 'pvbrain2/base/device_wk2168_i2c.yaml'
|
||||
# - path: 'pvbrain2/base/device_sx1509.yaml'
|
||||
- path: 'pvbrain2/base/device_canbus_esp32can.yaml' # canbus_node1
|
||||
- path: 'pvbrain2/base/device_canbus_mcp2515.yaml' # canbus_node2
|
||||
|
||||
# +--------------------------------------+
|
||||
# | YamBMS packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
############################################################
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
|
||||
shunt:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Shunt 1
|
||||
- path: 'packages/shunt/shunt_combine_Victron_SmartShunt_UART_expander.yaml' # shunt_combine_Junctek_KHF_UART.yaml
|
||||
vars:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
shunt_uart_id: 'uart_${uart_hub_bus}_2'
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_uart_id: 'uart_${uart_hub_bus}_4'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_uart_id: 'uart_${uart_hub_bus}_5'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
canbus:
|
||||
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'
|
||||
@@ -0,0 +1,270 @@
|
||||
# Updated : 2025.05.13
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
######################## YamBMS Remote Packages Version ########################
|
||||
|
||||
# You can compile this YAML directly without the `packages` folder.
|
||||
# The packages will be automatically downloaded from GitHub.
|
||||
# Don't forget to configure your WiFi credentials in the secrets.yaml
|
||||
|
||||
################################################################################
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# wifi:
|
||||
# manual_ip:
|
||||
# static_ip: 192.168.0.85
|
||||
# gateway: 192.168.0.1
|
||||
# subnet: 255.255.255.0
|
||||
# dns1: 8.8.8.8
|
||||
# dns2: 8.8.4.4
|
||||
|
||||
logger:
|
||||
level: INFO # VERBOSE / DEBUG / INFO / WARN
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Global Settings |
|
||||
# +--------------------------------------+
|
||||
substitutions:
|
||||
# Name
|
||||
name: '' # Name that can be added as a second prefix after the friendly name, you can leave it blank.
|
||||
hostname: 'yambms' # This is the name of the node. It should always be unique in your ESPHome network.
|
||||
friendly_name : 'YamBMS' # Prefix added in front of all entity names and also to classify them.
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
# +--------------------------------------+
|
||||
# | 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 |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
packages:
|
||||
|
||||
################ >>> CONFIG & CUSTOM LP <<< ################
|
||||
|
||||
# Local Packages intended for creating custom codes
|
||||
# or sharing settings between several main.yaml
|
||||
|
||||
# yambms_config: !include yambms_config.yaml
|
||||
# yambms_custom: !include yambms_custom.yaml
|
||||
|
||||
############### >>> UNCOMMENT YOUR BOARD <<< ###############
|
||||
############### >>> ONLY ONE BOARD ! <<< ###############
|
||||
|
||||
board:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/board/board_ESP32_Generic.yaml'
|
||||
# - path: 'packages/board/board_ESP32_DevKit-V1.yaml'
|
||||
# - path: 'packages/board/board_ESP32_LilyGo-T-CAN485.yaml'
|
||||
# - path: 'packages/board/board_ESP32_EVB.yaml'
|
||||
# - path: 'packages/board/board_ESP32_Atom-Lite.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_DevKitM-1.yaml'
|
||||
# - path: 'packages/board/board_ESP32-C3_ETH01-EVO.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-38.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_DevKitC-1_LED-48.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_LilyGo-T-Connect.yaml'
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3-Lite.yaml'
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
# - path: 'packages/board/board_ESP32-S3_AtomS3R.yaml'
|
||||
# vars:
|
||||
# display_auto_next_page_interval: '5s'
|
||||
# display_rotation: '0' # 0/90/180/270 rotation angle in degrees
|
||||
|
||||
########### >>> UNCOMMENT YOUR BOARD OPTIONS <<< ###########
|
||||
|
||||
board_options:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# UART 1
|
||||
- path: 'packages/board/board_options_itf_uart_esp_1.yaml'
|
||||
# UART 2
|
||||
- path: 'packages/board/board_options_itf_uart_esp_2.yaml'
|
||||
# UART 3
|
||||
- path: 'packages/board/board_options_itf_uart_esp_3.yaml'
|
||||
|
||||
# ESP32_CAN (TJA105x, SN65HVD230, M5Stack CAN base/unit)
|
||||
- path: 'packages/board/board_options_itf_canbus_esp32_can.yaml'
|
||||
vars:
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
# MCP2515
|
||||
# - path: 'packages/board/board_options_itf_canbus_mcp2515.yaml'
|
||||
# vars:
|
||||
# canbus_node_id: 'canbus_inverter_1'
|
||||
|
||||
############################################################
|
||||
|
||||
# You don't have to import a shunt but you must import at least one BMS.
|
||||
|
||||
shunt:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Shunt 1
|
||||
- path: 'packages/shunt/shunt_combine_Victron_SmartShunt_UART.yaml' # shunt_combine_Junctek_KHF_UART.yaml
|
||||
vars:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
shunt_uart_id: 'uart_esp_3'
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_uart_id: 'uart_esp_1'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_uart_id: 'uart_esp_2'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
# bms_options:
|
||||
# url: https://github.com/Sleeper85/esphome-yambms
|
||||
# ref: main
|
||||
# refresh: 0s
|
||||
# files:
|
||||
# # BMS 1
|
||||
# - path: 'packages/bms/bms_options_charging_logic.yaml'
|
||||
# vars:
|
||||
# bms_id: '1' # must be a number
|
||||
# # BMS 2
|
||||
# - path: 'packages/bms/bms_options_charging_logic.yaml'
|
||||
# vars:
|
||||
# bms_id: '2' # must be a number
|
||||
|
||||
yambms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
- path: 'packages/yambms/yambms.yaml'
|
||||
|
||||
canbus:
|
||||
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_inverter_1'
|
||||
canbus_light_id: 'esp_light'
|
||||
# The CANBUS link will be considered down if no response from the inverter (0x305 frame) for 5s
|
||||
# The Deye inverter sends the ACK 0x305 only when it receives the 0x356 frame.
|
||||
canbus_link_timer: '5s'
|
||||
|
||||
# +--------------------------------------+
|
||||
# | 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'
|
||||
@@ -0,0 +1,63 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_JBD_UART_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JBD_BLE_full.yaml
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_ble_mac_address: 'C8:47:8C:10:7E:AA' # Your MAC address
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# 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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,48 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_JK_BLE_standard.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_ble_protocol_version: 'JK02_32S' # JK02_24S < hardware version 11.0 >= JK02_32S
|
||||
bms_ble_mac_address: 'C8:47:8C:10:7E:AA'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_BLE_standard.yaml
|
||||
vars:
|
||||
bms_id: '2' # must be a 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:EE:16:EA'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,125 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
# 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_RS485_Modbus_sniffer_talk_pin.yaml
|
||||
# vars:
|
||||
# sniffer_id: 'sniffer1'
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
|
||||
|
||||
sniffer1: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
|
||||
# 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_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 DIP switch
|
||||
|
||||
bms4: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 DIP switch
|
||||
|
||||
bms5: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 DIP switch
|
||||
|
||||
bms6: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 DIP switch
|
||||
|
||||
bms7: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 DIP switch
|
||||
|
||||
bms8: !include
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 DIP switch
|
||||
@@ -0,0 +1,46 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_uart_id: 'uart_esp_1'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_uart_id: 'uart_esp_2'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,73 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
seplos_modbus1: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_modbus.yaml
|
||||
vars:
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
seplos_modbus_uart_id: 'uart_esp_1'
|
||||
seplos_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
seplos_modbus_rx_timeout: '150ms'
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
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
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
bms_uart_id: uart_esp_2
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_max_charge_current: '100' # A. Used to calculate maximum charge current
|
||||
bms_max_discharge_current: '100' # A. Used to calculate maximum discharge current
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
@@ -0,0 +1,104 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
substitutions:
|
||||
modbus_update_interval: '5s' # frequency with which BMS/Shunt modbus servers are queried
|
||||
modbus_baud_rate: '19200' # 9600 / 19200 / 11520
|
||||
modbus_command_throttle: '0ms' # minimum time in between 2 requests to the device
|
||||
modbus_send_wait_time: '250ms' # time in milliseconds before the next ModBUS command is sent if an answer from a previous command is pending
|
||||
|
||||
packages:
|
||||
|
||||
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
|
||||
vars:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_combine_modbus_client.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_modbus_client.yaml
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_combine_modbus_client.yaml
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'BMS 3'
|
||||
|
||||
# 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'
|
||||
@@ -0,0 +1,55 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
substitutions:
|
||||
modbus_update_interval: '5s' # frequency with which BMS/Shunt modbus servers are queried
|
||||
modbus_baud_rate: '19200' # 9600 / 19200 / 11520
|
||||
modbus_command_throttle: '0ms' # minimum time in between 2 requests to the device
|
||||
modbus_send_wait_time: '250ms' # time in milliseconds before the next ModBUS command is sent if an answer from a previous command is pending
|
||||
|
||||
packages:
|
||||
|
||||
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_UART_4G-GPS_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_uart_id: 'uart_esp_3'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,60 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Local Packages Example ############################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
substitutions:
|
||||
modbus_update_interval: '5s' # frequency with which BMS/Shunt modbus servers are queried
|
||||
modbus_baud_rate: '19200' # 9600 / 19200 / 11520
|
||||
modbus_command_throttle: '0ms' # minimum time in between 2 requests to the device
|
||||
modbus_send_wait_time: '250ms' # time in milliseconds before the next ModBUS command is sent if an answer from a previous command is pending
|
||||
|
||||
packages:
|
||||
|
||||
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_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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_modbus_JK_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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,67 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JBD_UART_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JBD_BLE_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_ble_mac_address: 'C8:47:8C:10:7E:AA' # Your MAC address
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# 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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,52 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_BLE_standard.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_ble_protocol_version: 'JK02_32S' # JK02_24S < hardware version 11.0 >= JK02_32S
|
||||
bms_ble_mac_address: 'C8:47:8C:10:7E:AA'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_BLE_standard.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a 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:EE:16:EA'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,113 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
# 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)
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# RS485 Sniffer
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml'
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'JK-BMS 3'
|
||||
bms_address: '0x03' # BMS 3 DIP switch
|
||||
# BMS 4
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '4' # must be a number
|
||||
bms_name: 'JK-BMS 4'
|
||||
bms_address: '0x04' # BMS 4 DIP switch
|
||||
# BMS 5
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '5' # must be a number
|
||||
bms_name: 'JK-BMS 5'
|
||||
bms_address: '0x05' # BMS 5 DIP switch
|
||||
# BMS 6
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '6' # must be a number
|
||||
bms_name: 'JK-BMS 6'
|
||||
bms_address: '0x06' # BMS 6 DIP switch
|
||||
# BMS 7
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '7' # must be a number
|
||||
bms_name: 'JK-BMS 7'
|
||||
bms_address: '0x07' # BMS 7 DIP switch
|
||||
# BMS 8
|
||||
- path: 'packages/bms/bms_combine_JK_RS485_Modbus_bms_standard.yaml'
|
||||
vars:
|
||||
# Sniffer ID
|
||||
sniffer_id: 'sniffer1'
|
||||
# BMS vars
|
||||
bms_id: '8' # must be a number
|
||||
bms_name: 'JK-BMS 8'
|
||||
bms_address: '0x08' # BMS 8 DIP switch
|
||||
@@ -0,0 +1,50 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_uart_id: 'uart_esp_1'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_JK_UART_4G-GPS_full.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'JK-BMS 2'
|
||||
bms_uart_id: 'uart_esp_2'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,76 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
packages:
|
||||
|
||||
bms:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Seplos Modbus 1
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_modbus.yaml'
|
||||
vars:
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
seplos_modbus_uart_id: 'uart_esp_1'
|
||||
seplos_modbus_baud_rate: '9600' # 9600 / 19200 ; please set the baudrate of your Seplos BMS model here
|
||||
seplos_modbus_rx_timeout: '150ms'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
bms_address: '0x01' # BMS 1 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_max_charge_current: '100' # A. Used to calculate maximum charge current
|
||||
bms_max_discharge_current: '100' # A. Used to calculate maximum discharge current
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_SEPLOS_V1_V2_RS485_bms_full.yaml'
|
||||
vars:
|
||||
# Seplos modbus ID
|
||||
seplos_modbus_id: 'seplos_modbus1'
|
||||
# BMS vars
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
bms_address: '0x02' # BMS 2 DIP switch
|
||||
bms_protocol_version: '0x20' # Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)
|
||||
bms_uart_id: uart_esp_2
|
||||
# Required settings cannot be retrieved from BMS
|
||||
# These values must match your BMS settings
|
||||
# LFP values example
|
||||
bms_max_charge_current: '100' # A. Used to calculate maximum charge current
|
||||
bms_max_discharge_current: '100' # A. Used to calculate maximum discharge current
|
||||
bms_cell_ovp: '3.650' # V. Used by 'Auto CCL' functions
|
||||
bms_cell_uvp: '2.800' # V. Used by 'Auto DCL' functions and to calculate maximum discharge voltage
|
||||
bms_balance_trigger_voltage: '0.010' # V. Used by 'Auto CVL' functions
|
||||
@@ -0,0 +1,98 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
substitutions:
|
||||
modbus_update_interval: '5s' # frequency with which BMS/Shunt modbus servers are queried
|
||||
modbus_baud_rate: '19200' # 9600 / 19200 / 11520
|
||||
modbus_command_throttle: '0ms' # minimum time in between 2 requests to the device
|
||||
modbus_send_wait_time: '250ms' # time in milliseconds before the next ModBUS command is sent if an answer from a previous command is pending
|
||||
|
||||
packages:
|
||||
|
||||
yambms_modbus_client:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Modbus client
|
||||
- path: 'packages/base/device_modbus.yaml'
|
||||
vars:
|
||||
modbus_role: 'client' # client / server
|
||||
modbus_uart_id: 'uart_esp_1' # RS485 board
|
||||
# Shunt 1
|
||||
- path: 'packages/shunt/shunt_combine_modbus_client.yaml'
|
||||
vars:
|
||||
shunt_id: '1' # must be a number
|
||||
shunt_name: 'Shunt 1'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
vars:
|
||||
bms_id: '2' # must be a number
|
||||
bms_name: 'BMS 2'
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
vars:
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'BMS 3'
|
||||
# # BMS 4
|
||||
# - path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
# vars:
|
||||
# bms_id: '4' # must be a number
|
||||
# bms_name: 'BMS 4'
|
||||
# # BMS 5
|
||||
# - path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
# vars:
|
||||
# bms_id: '5' # must be a number
|
||||
# bms_name: 'BMS 5'
|
||||
# # BMS 6
|
||||
# - path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
# vars:
|
||||
# bms_id: '6' # must be a number
|
||||
# bms_name: 'BMS 6'
|
||||
# # BMS 7
|
||||
# - path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
# vars:
|
||||
# bms_id: '7' # must be a number
|
||||
# bms_name: 'BMS 7'
|
||||
# # BMS 8
|
||||
# - path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
# vars:
|
||||
# bms_id: '8' # must be a number
|
||||
# bms_name: 'BMS 8'
|
||||
# # BMS 9
|
||||
# - path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
# vars:
|
||||
# bms_id: '9' # must be a number
|
||||
# bms_name: 'BMS 9'
|
||||
# # BMS 10
|
||||
# - path: 'packages/bms/bms_combine_modbus_client.yaml'
|
||||
# vars:
|
||||
# bms_id: '10' # must be a number
|
||||
# bms_name: 'BMS 10'
|
||||
@@ -0,0 +1,58 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
substitutions:
|
||||
modbus_update_interval: '5s' # frequency with which BMS/Shunt modbus servers are queried
|
||||
modbus_baud_rate: '19200' # 9600 / 19200 / 11520
|
||||
modbus_command_throttle: '0ms' # minimum time in between 2 requests to the device
|
||||
modbus_send_wait_time: '250ms' # time in milliseconds before the next ModBUS command is sent if an answer from a previous command is pending
|
||||
|
||||
packages:
|
||||
|
||||
yambms_modbus_server:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Modbus server
|
||||
- path: 'packages/base/device_modbus.yaml'
|
||||
vars:
|
||||
modbus_role: 'server' # client / server
|
||||
modbus_uart_id: 'uart_esp_1' # RS485 board
|
||||
# Shunt 1
|
||||
- path: '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'
|
||||
# BMS 1
|
||||
- path: 'packages/bms/bms_modbus_JK_UART_4G-GPS_full.yaml'
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'JK-BMS 1'
|
||||
bms_uart_id: 'uart_esp_3'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -0,0 +1,63 @@
|
||||
# Updated : 2025.04.01
|
||||
# Version : 1.5.5
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
# YamBMS ( Yet another multi-BMS Merging Solution )
|
||||
|
||||
# This YAML is free software: you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation, either version 3
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program is distributed in the hope that it will be useful,
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
# See the GNU General Public License for more details.
|
||||
#
|
||||
# You should have received a copy of the GNU General Public License
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/gpl.html>.
|
||||
|
||||
############################ Remote Packages Example ###########################
|
||||
|
||||
# This is not a working YAML but just code ready to copy into your main YAML.
|
||||
|
||||
################################################################################
|
||||
|
||||
substitutions:
|
||||
modbus_update_interval: '5s' # frequency with which BMS/Shunt modbus servers are queried
|
||||
modbus_baud_rate: '19200' # 9600 / 19200 / 11520
|
||||
modbus_command_throttle: '0ms' # minimum time in between 2 requests to the device
|
||||
modbus_send_wait_time: '250ms' # time in milliseconds before the next ModBUS command is sent if an answer from a previous command is pending
|
||||
|
||||
packages:
|
||||
|
||||
yambms_modbus_server:
|
||||
url: https://github.com/Sleeper85/esphome-yambms
|
||||
ref: main
|
||||
refresh: 0s
|
||||
files:
|
||||
# Modbus server
|
||||
- path: 'packages/base/device_modbus.yaml'
|
||||
vars:
|
||||
modbus_role: 'server' # client / server
|
||||
modbus_uart_id: 'uart_esp_1' # RS485 board
|
||||
# BMS 2
|
||||
- path: 'packages/bms/bms_modbus_JK_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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
# BMS 3
|
||||
- path: 'packages/bms/bms_modbus_JK_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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
@@ -1,4 +1,4 @@
|
||||
# YamBMS - JK-B BMS UART Solution
|
||||
# YamBMS - JK-B BMS
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||
@@ -6,9 +6,46 @@
|
||||

|
||||

|
||||
|
||||
## External component
|
||||
> [!IMPORTANT]
|
||||
> The most important thing for proper functioning of YamBMS is that **the voltage of your BMS is well calibrated**.
|
||||
> YamBMS logic is based on the `min_cell_voltage` and `max_cell_voltage` voltages of your BMS.
|
||||
|
||||
[esphome-jk-bms](https://github.com/syssi/esphome-jk-bms) by [@syssi](https://github.com/syssi)
|
||||
## JK-B BMS overview
|
||||
|
||||
### UART1 (GPS) port
|
||||
|
||||
The `GPS` port sometimes called `RS485` is not an `RS485` port but `3V3 UART-TTL` port.
|
||||
|
||||
```
|
||||
# UART-TTL GPS port on JK-BMS (4 pin, JST 1.25mm pitch)
|
||||
┌─── ─────── ────┐
|
||||
│ │
|
||||
│ O O O O │
|
||||
│GND RX TX VBAT│
|
||||
└────────────────┘
|
||||
│ │ │ └ VBAT is full battery volatge eg. 56V (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 `UART1` (labeled as `GPS`) socket of the BMS can be attached to any UART pins of the ESP32.<br>
|
||||
A hardware UART should be preferred because of the high baudrate (115200 baud).<br>
|
||||
The connector is called 4 pin JST with 1.25mm pitch.
|
||||
|
||||

|
||||
|
||||
## JK-B BMS protocol
|
||||
|
||||
Historically it was not possible to change the protocol of the `UART1 (GPS)` port and the protocol used was `4G-GPS Remote module Common protocol V4.2` with the component [esphome-jk-bms](https://github.com/syssi/esphome-jk-bms) of [@syssi](https://github.com/syssi).
|
||||
|
||||
If you cannot change the protocol of the `UART1 (GPS)` port you can only monitor one BMS per UART port of the ESP32, so a maximum of `3x BMS` without adding a UART expander.
|
||||
|
||||
If you have a recent BMS, it is now possible to change the protocol of the `UART1 (GPS)` port and with the `JK BMS RS485 Modbus V1.0` protocol you can assign an address (via JK app) to your BMS and monitor several of them from a single `UART-RS485` connection in the same way as the [JK-PB](BMS_JK-PB.md). To use this protocol and monitor all your BMS on a single `RS485 bus` you will need to add the `UART to RS485 adapter` sold by JK or another RS485 board of your choice.
|
||||
|
||||
<img src="../../images/BMS_JK_RS485_Modbus_protocol.png" width="600">
|
||||
|
||||

|
||||
|
||||
## Schematic and setup instructions
|
||||
|
||||
@@ -19,34 +56,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)
|
||||
|
||||

|
||||
|
||||
| [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)
|
||||
|
||||
@@ -59,8 +69,8 @@ You need to import this YAML into the main YAML.
|
||||
```
|
||||
UART-TTL RS232-TTL CAN BUS
|
||||
┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐
|
||||
│ │<TX------RX>│2 5│<TX-------TX>| | | |
|
||||
│ JK-BMS │<RX------TX>│1 6│<RX-------RX>| CA-IS3050G |<---CAN H --->| Inverter |
|
||||
│ │<TX------RX>│1 5│<TX-------TX>| | | |
|
||||
│ JK-BMS │<RX------TX>│2 6│<RX-------RX>| CA-IS3050G |<---CAN H --->| Inverter |
|
||||
│ │<----GND--->│ ESP32 │ | CAN |<---CAN L --->| |
|
||||
│ │ 5V---->│5V 3V3| | | | |
|
||||
└──────────┘ └──────────┘ └────────────┘ └──────────┘
|
||||
@@ -78,8 +88,8 @@ You need to import this YAML into the main YAML.
|
||||
```
|
||||
UART-TTL RS232-TTL CAN BUS
|
||||
┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐
|
||||
│ │<TX------RX>│26 22│<TX-------TX>| | | |
|
||||
│ JK-BMS │<RX------TX>│32 19│<RX-------RX>| CA-IS3050G |<---CAN H --->| Inverter |
|
||||
│ │<TX------RX>│32 22│<TX-------TX>| | | |
|
||||
│ JK-BMS │<RX------TX>│26 19│<RX-------RX>| CA-IS3050G |<---CAN H --->| Inverter |
|
||||
│ │<----GND--->│ ESP32 │ | CAN |<---CAN L --->| |
|
||||
│ │ 5V---->│5V 3V3| | | | |
|
||||
└──────────┘ └──────────┘ └────────────┘ └──────────┘
|
||||
@@ -132,25 +142,3 @@ You need to import this YAML into the main YAML.
|
||||
|
||||
```
|
||||
|
||||
### JK-B BMS UART-TTL GPS port
|
||||
|
||||
The `GPS` port sometimes called `RS485` is not an `RS485` port but `3V3 UART-TTL`.
|
||||
|
||||
```
|
||||
# UART-TTL GPS port on JK-BMS (4 pin, JST 1.25mm pitch)
|
||||
┌─── ─────── ────┐
|
||||
│ │
|
||||
│ 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
|
||||
```
|
||||
|
||||
The UART-TTL (labeled as `GPS`) socket of the BMS can be attached to any UART pins of the ESP.<br>
|
||||
A hardware UART should be preferred because of the high baudrate (115200 baud).<br>
|
||||
The connector is called 4 pin JST with 1.25mm pitch.
|
||||
|
||||

|
||||
@@ -1,4 +1,4 @@
|
||||
# YamBMS - JK-PB BMS RS485 Solution
|
||||
# YamBMS - JK-PB Inverter BMS
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||
@@ -6,68 +6,98 @@
|
||||

|
||||

|
||||
|
||||
## External component
|
||||
> [!IMPORTANT]
|
||||
> The most important thing for proper functioning of YamBMS is that **the voltage of your BMS is well calibrated**.
|
||||
> YamBMS logic is based on the `min_cell_voltage` and `max_cell_voltage` voltages of your BMS.
|
||||
> If you use YamBMS, the internal charging logic of the `JK-PB BMS` will not be used.
|
||||
|
||||
[JK_RS485](https://github.com/txubelaxu/esphome-jk-bms/blob/main/components/jk_rs485_bms/README.md) by [@txubelaxu](https://github.com/txubelaxu)
|
||||
## JK-PB BMS overview
|
||||
|
||||
## ESP32 board
|
||||
||
|
||||
|-|
|
||||
||
|
||||
||
|
||||
|
||||
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.
|
||||
## JK-PB BMS protocol
|
||||
|
||||
### Atom S3
|
||||
The datas from this BMS can be retrieved from the `RS485-2 (UART2)` network using the component [JK_RS485](https://github.com/txubelaxu/esphome-jk-bms/blob/main/components/jk_rs485_bms/README.md) of [@txubelaxu](https://github.com/txubelaxu).
|
||||
|
||||
- [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)
|
||||
The BMS DIP switches must be set from `1` to `15` (server mode) and connected to each other using the `RS485-2` network available on the **two ports at the right ends**. `YamBMS` also connects to one of these two ports.
|
||||
|
||||
Note: `Atom S3 Lite` does not have a display.
|
||||
### **UART2 configuration**
|
||||
|
||||
### ESP32-S3 DevKitC-1
|
||||
> [!NOTE]
|
||||
> The protocol of the `UART2` port is not selectable from the JK application.
|
||||
> It is automatically set based on the address (DIP switch) of the BMS.
|
||||
|
||||
- [ESP32-S3 N16R8](https://a.aliexpress.com/_EzFdrw3)
|
||||
- [SN65HVD230 3V3 CAN transceiver](https://a.aliexpress.com/_Evq9Ra7)
|
||||
In the last software version only two protocols are available on the **RS485-2 (UART2)** ports:
|
||||
|
||||
## RS485 unisolated board (not recommanded)
|
||||
- **001** - JK BMS RS485 Modbus V1.0 **(DIP switch 1 to 15)**
|
||||
- **015** - UART Protocol 015 **(DIP switch 0)**
|
||||
|
||||
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`.
|
||||
### **UART1 configuration**
|
||||
|
||||

|
||||
The following protocols are supported on the **RS485-1 (UART1)** port:
|
||||
|
||||
## RS485 isolated board (recommended for making your own PCB)
|
||||
(*italic options ane not settable*)
|
||||
|
||||
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).
|
||||
- **000** - 4G-GPS Remote module Common protocol V4.2
|
||||
- **001** - **JK BMS RS485 Modbus V1.0**
|
||||
- **002** - NIU U SERIES
|
||||
- **003** - China tower shared battery cabinet V1.1
|
||||
- **004** - PACE_RS485_Modbus_V1.3
|
||||
- **005** - PYLON_low_voltage_Protocol_RS485_V3.5
|
||||
- **006** - Growatt_BMS_RS485_Protocol_1xSxxP_ESS_Rev2.01
|
||||
- **007** - Voltronic_Inverter_and_BMS_485_communication_protocol_20200...
|
||||
- **008** - China tower shared battery cabinet V2.0
|
||||
- **009** - WOW_RS485_Modbus_V1.3
|
||||
- **010** - JK BMS LCD Protocol V2.0
|
||||
- **011** - *UART1 User customization*
|
||||
- **012** - *UART2 User customization*
|
||||
- **013** - (9600)JK BMS RS485 Modbus V1.0
|
||||
- **014** - (9600)PYLON_low_voltage_Protocol_RS485_V3.5
|
||||
- **015** - *UART Protocol 015*
|
||||
|
||||

|
||||
### **CAN port configuration**
|
||||
|
||||
[RS485 isolated board (high speed dual)](https://a.aliexpress.com/_EueIZT5)
|
||||
The following CAN protocols are supported on the CAN port:
|
||||
|
||||
Note: choose the `high speed dual` version !
|
||||
(*italic options ane not settable*)
|
||||
|
||||
## M5stack RS485 isolated unit [SKU:U094] (recommended with M5stack Atom S3 solution)
|
||||
- **000** - JK BMS CAN Protocol (250K) V2.0
|
||||
- **001** - Deye Low-voltage hybrid inverter CAN communication protocol V1.0
|
||||
- **002** - PYLON-Low-voltage-V1.2
|
||||
- **003** - Growatt BMS CAN-Bus-protocol-low-voltage_Rev_05
|
||||
- **004** - Victron_CANbus_BMS_protocol_20170717
|
||||
- **005** - MEGAREVO_Hybird_BMSCAN_Protocol_V1.0
|
||||
- **006** - JK BMS CAN Protocol (500K) V2.0
|
||||
- **007** - INVT BMS CAN Bus protocol V1.02
|
||||
- **008** - GoodWe LV BMS Protocol (EX/EM/S-BP/BP)
|
||||
- **009** - FSS-ConnectingBat-Tl-en-10 | Version 1.0
|
||||
- **010** - MUST PV1800F-CAN communication Protocol1.04.04
|
||||
- **011** - LuxpowerTek Battery CAN protocol V01
|
||||
- **012** - *CAN BUS User customization*
|
||||
- **013** - *CAN BUS Protocol 013*
|
||||
- **014** - *CAN BUS Protocol 014*
|
||||
|
||||
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.
|
||||
## YamBMS hardware
|
||||
|
||||
")
|
||||
> [!TIP]
|
||||
> This solution only requires an ESP32 with a CAN transceiver and a RS485 transceiver.
|
||||
|
||||
## M5stack Atom S3 with CAN base and RS485 unit
|
||||
You are free to choose the hardware you want, the list below are 3 easy to use examples :
|
||||
|
||||
If soldering or creating your own board seems complicated to you, know that it is possible to use the Atom S3 solution from M5Stack.
|
||||
- `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)
|
||||
|
||||
**Choose Atom S3 (display) or Atom S3 Lite + Atomic CAN base + RS485 unit**
|
||||
See the [documentation about supported hardware](Supported_devices.md).
|
||||
|
||||
- [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)
|
||||
### M5Stack AtomS3 example (no welding)
|
||||
|
||||
| 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 `AtomS3` (display) with the `Atomic CAN base` and `RS485 unit`.
|
||||
|
||||
The example below uses an Atom S3 (display) with the CAN base and RS485 unit.
|
||||
|
||||

|
||||

|
||||
|
||||
## Schematic and setup instructions
|
||||
|
||||
@@ -75,19 +105,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 +151,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
|
||||
|
||||

|
||||

|
||||
|
||||
When enabled, this function synchronizes the settings of all your BMS connected to the same RS485 network as soon as you make parameter changes.
|
||||
@@ -1,4 +1,4 @@
|
||||
# YamBMS - JK-B BMS RS485 DISPLAY Solution
|
||||
# YamBMS - JK RS485 DISPLAY
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||
@@ -6,6 +6,10 @@
|
||||

|
||||

|
||||
|
||||
> [!IMPORTANT]
|
||||
> The most important thing for proper functioning of YamBMS is that **the voltage of your BMS is well calibrated**.
|
||||
> YamBMS logic is based on the `min_cell_voltage` and `max_cell_voltage` voltages of your BMS.
|
||||
|
||||
## External component
|
||||
|
||||
[esphome-jk-bms](https://github.com/syssi/esphome-jk-bms) by [@syssi](https://github.com/syssi)
|
||||
@@ -6,6 +6,9 @@
|
||||

|
||||

|
||||
|
||||
> [!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.
|
||||
|
||||
@@ -0,0 +1,39 @@
|
||||
# YamBMS - Galvanic isolation
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
## 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)
|
||||
|
||||

|
||||
|
||||
| [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"> |
|
||||
@@ -8,20 +8,40 @@
|
||||
|
||||
## Installation procedure
|
||||
|
||||
1. **Install ESPHome on your computer**<br>
|
||||
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>
|
||||
### 1. Install ESPHome on your computer
|
||||
|
||||
Before you can flash your ESP32 you need to install the [ESPHome 2025.3.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
|
||||
|
||||
> [!TIP]
|
||||
> This step is not necessary if you are compiling the `Remote Packages` version of the YAML.
|
||||
|
||||
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,62 +49,49 @@ wifi_password: YourPassword
|
||||
domain : .local
|
||||
```
|
||||
|
||||
4. **Install the YamBMS application into your ESP32**<br>
|
||||
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>
|
||||
The goal is that the main YAML which contains all your specific parameters can be preserved and reused each time the other YAMLs classified in the `packaged` folder are updated.**
|
||||
### 4. Install the YamBMS application into your ESP32
|
||||
|
||||
Create a copy of `YamBMS_Remote_Packages_example.yaml` and modify it to match your configuration.
|
||||
Examples of BMS imports can be found in the [configuration_examples](configuration_examples/) folder.
|
||||
You can mix different BMS models, the only condition is that they are numbered in order starting from `1`.
|
||||
|
||||
```bash
|
||||
# To install the multi-bms JK-ALL Bluetooth version
|
||||
esphome run multi-bms_JK-ALL_BLE.yaml
|
||||
|
||||
# To install the multi-bms JK-B UART version
|
||||
esphome run multi-bms_JK-B_UART.yaml
|
||||
|
||||
# To install the multi-bms JK-PB RS485 version
|
||||
esphome run multi-bms_JK-PB_RS485_mode2.yaml
|
||||
# install your YamBMS.yaml
|
||||
# validate the configuration, create a binary, upload it, and start logs.
|
||||
esphome run YamBMS.yaml
|
||||
|
||||
# upgrade via OTA by specifying the IP address of the ESP32
|
||||
esphome run multi-bms_JK-ALL_BLE.yaml --device 192.168.x.x
|
||||
esphome run YamBMS.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
|
||||
esphome clean multi-bms_JK-ALL_BLE.yaml
|
||||
esphome clean YamBMS.yaml
|
||||
|
||||
# test the config
|
||||
esphome config multi-bms_JK-ALL_BLE.yaml
|
||||
esphome config YamBMS.yaml
|
||||
|
||||
# install the config in ESP32
|
||||
esphome run multi-bms_JK-ALL_BLE.yaml
|
||||
esphome run YamBMS.yaml
|
||||
|
||||
# compile the firmware.bin
|
||||
esphome compile multi-bms_JK-ALL_BLE.yaml
|
||||
esphome compile YamBMS.yaml
|
||||
|
||||
# check the logs (the --device option is not required)
|
||||
esphome logs multi-bms_JK-ALL_BLE.yaml --device 192.168.x.x
|
||||
esphome logs YamBMS.yaml --device 192.168.x.x
|
||||
```
|
||||
|
||||
## Debugging
|
||||
|
||||
If this component doesn't work out of the box for your device please update your configuration to enable the debug output of the UART component and increase the log level to the see outgoing and incoming serial traffic:
|
||||
If this component doesn't work out of the box for your device please update your configuration to increase the log level to `DEBUG`.
|
||||
|
||||
```
|
||||
```YAML
|
||||
logger:
|
||||
level: DEBUG
|
||||
|
||||
uart:
|
||||
id: uart_0
|
||||
baud_rate: 115200
|
||||
rx_buffer_size: 384
|
||||
tx_pin: ${tx_pin}
|
||||
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](BMS_JK-B.md)
|
||||
3) [JK-PB BMS](BMS_JK-PB.md)
|
||||
4) [JK RS485 DISPLAY](BMS_JK_RS485_DISPLAY.md)
|
||||
5) [Victron SmartShunt](Shunt_Victron_SmartShunt.md)
|
||||
@@ -0,0 +1,59 @@
|
||||
# Victron SmartShunt
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
## 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.
|
||||
|
||||
Connect to the SmartShunt via Bluetooth under the `Local` tab.
|
||||
|
||||

|
||||

|
||||

|
||||

|
||||
|
||||
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.
|
||||
@@ -6,43 +6,61 @@
|
||||

|
||||

|
||||
|
||||
## 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 @@
|
||||

|
||||

|
||||
|
||||
> [!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.**
|
||||
|
||||

|
||||
|
||||

|
||||

|
||||
@@ -0,0 +1,56 @@
|
||||
# YamBMS - M5Stack AtomS3, the Plug & Play solution (no welding)
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
> [!IMPORTANT]
|
||||
> AtomS3 provides very few GPIOs.
|
||||
> This solution is not the best for supervising a large number of `JK-B BMS` via `UART` but it works very well for supervising a large number of `JK-PB BMS` via `RS485`.
|
||||
|
||||
> [!TIP]
|
||||
> If you have `JK-PB BMS` (inverter BMS) and want to monitor them via `RS485`, please read the [BMS JK-PB RS485](BMS_JK-PB_RS485_solution.md) dedicated topic.
|
||||
|
||||
## Number of BMS supported
|
||||
|
||||
* 3x BMS with `Bluetooth` (BLE stack consumes significant amount of RAM on device and can cause crash and reboot)
|
||||
* 2x `JK-B` BMS with `UART/RS485` (the second UART must be soldered on the Atomic CAN base on GPIOs G7 and G8)
|
||||
* several `JK-PB` BMS with `RS485` (already tested with 7 BMS)
|
||||
|
||||
Note: these are theoretical limits, not all combinations have been tested.
|
||||
|
||||
## List of M5Stack components that can be used depending on needs
|
||||
|
||||
> [!TIP]
|
||||
> Choose an `AtomS3` to clip onto the `Atomic CAN Base`.
|
||||
> Feel free to ask your question on the [DIY solar forum](https://diysolarforum.com/threads/yambms-jk-bms-can-with-new-cut-off-charging-logic-open-source.79325/) if you don't know what to choose.
|
||||
|
||||
- [AtomS3 Lite - SKU:C124](https://docs.m5stack.com/en/core/AtomS3%20Lite)
|
||||
- [AtomS3 - SKU:C123](https://docs.m5stack.com/en/core/AtomS3)
|
||||
- [AtomS3R - SKU:C126 (8MB PSRAM)](https://docs.m5stack.com/en/core/AtomS3R)
|
||||
- [Atomic CAN Base - SKU:A103 (recommended)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base)
|
||||
- [CAN Unit - SKU:U085](https://docs.m5stack.com/en/unit/can)
|
||||
- [RS485 Unit - SKU:U094](https://docs.m5stack.com/en/unit/iso485)
|
||||
|
||||
| [AtomS3 Lite](https://docs.m5stack.com/en/core/AtomS3%20Lite) | [AtomS3](https://docs.m5stack.com/en/core/AtomS3) | [AtomS3R (8MB PSRAM)](https://docs.m5stack.com/en/core/AtomS3R) |
|
||||
| --- | --- | --- |
|
||||
| <img src="../../images/MCU_AtomS3_Lite.png" width="300"> | <img src="../../images/MCU_AtomS3.png" width="300"> | <img src="../../images/MCU_AtomS3R.png" width="300"> |
|
||||
|
||||
| [Atomic CAN Base (isolated)](https://docs.m5stack.com/en/atom/Atomic%20CAN%20Base) | [CAN Unit (isolated)](https://docs.m5stack.com/en/unit/can) | [RS485 Unit (isolated)](https://docs.m5stack.com/en/unit/iso485) |
|
||||
| --- | --- | --- |
|
||||
| <img src="../../images/CAN_Transceiver_M5Stack_Atomic_CAN_Base.png" width="300"> | <img src="../../images/CAN_Transceiver_M5Stack_CAN_Unit.png" width="300"> | <img src="../../images/RS485_Transceiver_M5stack_SKU-U094_RS485_Isolated_Unit.png" width="300"> |
|
||||
|
||||
## Note regarding the sensors managing the display backlight (ili9xxx platform)
|
||||
|
||||
* **Backlight control** : manual brightness control
|
||||
* **Backlight max level** : limit the max brightness in general
|
||||
* **Backlight Autodim level** : the desired brightness when dimmed down (set to 0 to switch off screen completely instead of dimming down)
|
||||
* **Backlight Autodim time in min** : time in minutes, after the screen will dim down (set to 0 to disable Auto dimming)
|
||||
|
||||
Device will restore last screen brightness after boot, but the timer script does not get start automatically.
|
||||
The auto dim timer gets initially started by pressing the screen button (which bumps up the brightness to 100% until the timer dims down then).
|
||||
|
||||
That seems to be the easiest and lightweight solution.
|
||||
But i guess some user could be confused and expect from the device to react immediately after changing some parameters.
|
||||
@@ -1,38 +0,0 @@
|
||||
# YamBMS - M5Stack Atom S3 (ESP32-S3FN8)
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
## 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"> |
|
||||
@@ -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 two 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
|
||||
|
||||

|
||||
|
||||
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`.
|
||||
|
||||
@@ -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%).
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# YamBMS - How to create your YamBMS YAML
|
||||
# YamBMS - How to create your YamBMS YAML (Local Packages examples)
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||
@@ -6,6 +6,10 @@
|
||||

|
||||

|
||||
|
||||
> [!TIP]
|
||||
> Not sure which YAML to choose ? ... `YamBMS_Remote_Packages_example.yaml` is a good basis for creating your custom YAML.
|
||||
> Examples of BMS imports can be found in the [configuration_examples](configuration_examples/) folder.
|
||||
> You can mix different BMS models, the only condition is that they are numbered in order starting from `1`.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> BMS monitoring with `Bluetooth` as well as the `Web server` are RAM-intensive components.
|
||||
@@ -66,7 +70,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 +80,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 +118,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,55 +141,155 @@ 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
|
||||
```
|
||||
|
||||
### 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
|
||||
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_combine_JK_UART_4G-GPS_full.yaml
|
||||
vars:
|
||||
bms_id: '1' # must be a number
|
||||
bms_name: 'BMS 1'
|
||||
# other settings
|
||||
# ...
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_combine_JBD_UART_full.yaml
|
||||
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
|
||||
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
|
||||
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_UART_4G-GPS_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
|
||||
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_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_modbus_JK_BLE_standard.yaml
|
||||
vars:
|
||||
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.
|
||||
|
||||
### Multi-BMS example
|
||||
|
||||
```YAML
|
||||
bms1: !include
|
||||
file: packages/bms/bms_model.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
|
||||
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
|
||||
# ...
|
||||
|
||||
bms3: !include
|
||||
file: packages/bms/bms_model.yaml
|
||||
vars:
|
||||
# YamBMS ID
|
||||
yambms_id: 'yambms1' # YamBMS ID to send information to
|
||||
# BMS vars
|
||||
bms_id: '3' # must be a number
|
||||
bms_name: 'BMS 3'
|
||||
# other settings
|
||||
# ...
|
||||
```
|
||||
|
||||
### [JK-ALL (BLE)](https://github.com/syssi/esphome-jk-bms)
|
||||
### [JK-BMS (BLE)](https://github.com/syssi/esphome-jk-bms)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The BLE software stack on the ESP32 consumes a significant amount of RAM on the device.
|
||||
@@ -208,54 +298,49 @@ 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_BLE_standard.yaml # bms_modbus_JK_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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
```
|
||||
|
||||
### [JK-B (UART)](https://github.com/syssi/esphome-jk-bms)
|
||||
### [JK-BMS (UART 4G-GPS)](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_UART_4G-GPS_full.yaml # bms_modbus_JK_UART_4G-GPS_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'
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
```
|
||||
|
||||
### [JK-B (RS485 DISPLAY)](https://github.com/syssi/esphome-jk-bms)
|
||||
### [JK-BMS (RS485 DISPLAY)](https://github.com/syssi/esphome-jk-bms)
|
||||
|
||||
> [!CAUTION]
|
||||
> The `jk_bms_display` component does not provide all the information needed for an optimal operation of `YamBMS`.
|
||||
> 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_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
|
||||
@@ -264,13 +349,21 @@ The `full` / `standard` versions contain all available sensors while the `minima
|
||||
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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
```
|
||||
|
||||
### [JK-PB (RS485)](https://github.com/txubelaxu/esphome-jk-bms/)
|
||||
### [JK-BMS (RS485 Modbus)](https://github.com/txubelaxu/esphome-jk-bms/)
|
||||
|
||||
> [!TIP]
|
||||
> Compatible with JK-PB, JK-B HW. >= 11A
|
||||
|
||||
A single `RS485 bus` allows you to monitor up to `16` BMS.
|
||||
|
||||
#### JK-PB sniffer
|
||||
[How to make the RS485 connection with the ESP32.](BMS_JK-PB_RS485_solution.md)
|
||||
|
||||
#### JK sniffer
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You need to import only one `sniffer` package of your choice.
|
||||
@@ -283,7 +376,7 @@ Sniffer without `talk_pin` :
|
||||
|
||||
```YAML
|
||||
sniffer1: !include
|
||||
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
|
||||
file: packages/bms/bms_combine_JK_RS485_Modbus_sniffer.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
@@ -294,7 +387,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_RS485_Modbus_sniffer_talk_pin.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
@@ -302,40 +395,31 @@ If your `RS485` board requires a `talk_pin` you must specify which `GPIO` will b
|
||||
sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
|
||||
```
|
||||
|
||||
#### JK-PB BMS
|
||||
#### JK-BMS (JK-PB, JK-B HW. >= 11A)
|
||||
|
||||
```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_RS485_Modbus_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
|
||||
@@ -344,6 +428,31 @@ If your `RS485` board requires a `talk_pin` you must specify which `GPIO` will b
|
||||
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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
```
|
||||
|
||||
### [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
|
||||
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
|
||||
# Maximum cell charging cycles is used to calculate the battey SoH.
|
||||
# MB31=8000.0, LF280K v3=8000.0, LF280K v2=6000.0, LF280=3000.0 (decimal is required)
|
||||
bms_cell_max_cycles: '6000.0'
|
||||
```
|
||||
|
||||
### [Seplos V1/V2 (RS485)](https://github.com/syssi/esphome-seplos-bms)
|
||||
@@ -363,31 +472,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 +505,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 +534,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 +550,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 +572,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'
|
||||
@@ -491,12 +593,14 @@ Take the time to configure `YamBMS` correctly according to your battery chemistr
|
||||
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'
|
||||
```
|
||||
|
||||
## 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,12 +609,10 @@ 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'
|
||||
canbus_node_id: 'canbus_node1'
|
||||
canbus_node_id: 'canbus_inverter_1'
|
||||
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
|
||||
|
||||
@@ -0,0 +1,11 @@
|
||||
# YamBMS - JK-PB BMS RS485 Solution
|
||||
|
||||
[](https://www.gnu.org/licenses/gpl-3.0)
|
||||
[](https://github.com/Sleeper85/esphome-yambms/releases/latest)
|
||||

|
||||

|
||||

|
||||
|
||||
## 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.
|
||||
|
Before Width: | Height: | Size: 441 KiB |
|
Before Width: | Height: | Size: 387 KiB |
|
Before Width: | Height: | Size: 371 KiB |
|
After Width: | Height: | Size: 587 KiB |
|
After Width: | Height: | Size: 106 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 176 KiB |
|
After Width: | Height: | Size: 527 KiB |
|
Before Width: | Height: | Size: 223 KiB After Width: | Height: | Size: 239 KiB |
|
After Width: | Height: | Size: 600 KiB |
|
After Width: | Height: | Size: 500 KiB |
|
Before Width: | Height: | Size: 424 KiB After Width: | Height: | Size: 424 KiB |
|
Before Width: | Height: | Size: 423 KiB After Width: | Height: | Size: 423 KiB |
|
Before Width: | Height: | Size: 352 KiB After Width: | Height: | Size: 352 KiB |
|
After Width: | Height: | Size: 431 KiB |
|
After Width: | Height: | Size: 62 KiB |
|
After Width: | Height: | Size: 339 KiB |
|
After Width: | Height: | Size: 575 KiB |
|
After Width: | Height: | Size: 90 KiB |
|
After Width: | Height: | Size: 468 KiB |
|
After Width: | Height: | Size: 486 KiB |
|
After Width: | Height: | Size: 408 KiB |
|
After Width: | Height: | Size: 1.8 MiB |
|
After Width: | Height: | Size: 185 KiB |
|
After Width: | Height: | Size: 2.1 MiB |
|
Before Width: | Height: | Size: 197 KiB After Width: | Height: | Size: 184 KiB |
|
Before Width: | Height: | Size: 364 KiB After Width: | Height: | Size: 486 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 39 KiB |
|
After Width: | Height: | Size: 44 KiB |
|
Before Width: | Height: | Size: 152 KiB After Width: | Height: | Size: 154 KiB |
|
Before Width: | Height: | Size: 154 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 100 KiB |
@@ -1,242 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms-demo
|
||||
|
||||
# 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: DEBUG # 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# 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
|
||||
|
||||
device_board: !include
|
||||
file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
|
||||
vars:
|
||||
yambms_id: 'yambms1'
|
||||
canbus_id: 'canbus1'
|
||||
display_auto_next_page_interval: '5s'
|
||||
|
||||
shunt1: !include
|
||||
file: packages/shunt/shunt_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
|
||||
shunt_power: '2003' # W
|
||||
shunt_soc: '86' # %
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_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
|
||||
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
|
||||
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
|
||||
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
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,188 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# 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
|
||||
|
||||
# device_board: !include
|
||||
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
|
||||
# vars:
|
||||
# yambms_id: 'yambms1'
|
||||
# canbus_id: 'canbus1'
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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
|
||||
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
|
||||
# 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
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_JBD_UART_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
|
||||
# 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
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,180 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# 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: DEBUG # DEBUG / INFO / WARN
|
||||
logs:
|
||||
esp32_ble_tracker: INFO
|
||||
esp32_ble_client: INFO
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
# Max 3 BLE connections.
|
||||
# The BLE software stack (Bluedroid) on the ESP32 consumes a significant amount of RAM on the device.
|
||||
# Crashes are likely to occur if you include too many additional components in your device’s configuration.
|
||||
# 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
|
||||
|
||||
# device_board: !include
|
||||
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
|
||||
# vars:
|
||||
# yambms_id: 'yambms1'
|
||||
# canbus_id: 'canbus1'
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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
|
||||
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
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_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
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,170 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# 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
|
||||
|
||||
# device_board: !include
|
||||
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
|
||||
# vars:
|
||||
# yambms_id: 'yambms1'
|
||||
# canbus_id: 'canbus1'
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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
|
||||
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
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_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
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,195 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.1
|
||||
# GitHub : https://github.com/SeByDocKy/pvbrain2
|
||||
# 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: 'pvbrain2'
|
||||
|
||||
###### For extended UART ports with the 2 WK2168 ######
|
||||
|
||||
uart0_baudrate: '2400' #WKS {RJ45-UART0}
|
||||
uart1_baudrate: '38400' #JSY193
|
||||
uart2_baudrate: '19200' #smartshunt
|
||||
uart3_baudrate: '9600' #SRNE {RJ45-UART3}
|
||||
uart4_baudrate: '115200' #JK-BMS 1
|
||||
uart5_baudrate: '115200' #JK-BMS 2
|
||||
uart6_baudrate: '115200' #Pylontech
|
||||
uart7_baudrate: '9600' #EPEVER {RJ45-UART7}
|
||||
|
||||
#######################################################
|
||||
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | PVbrain2 packages |
|
||||
# +--------------------------------------+
|
||||
packages:
|
||||
device_base: !include packages/base/device_base.yaml
|
||||
device_board: !include packages/board/board_pvbrain2.yaml
|
||||
|
||||
# BUS
|
||||
# bus_i2c0: !include pvbrain2/base/device_bus_i2c0.yaml # SX1509 and BME280/BMP280
|
||||
bus_spi1: !include pvbrain2/base/device_bus_spi1.yaml # MCP2515
|
||||
# bus_one_wire: !include pvbrain2/base/device_bus_one_wire.yaml # Dallas
|
||||
|
||||
# Devices
|
||||
device_uart_esp: !include pvbrain2/base/device_uart_esp.yaml
|
||||
device_wk2168_spi: !include pvbrain2/base/device_wk2168_spi.yaml
|
||||
# device_wk2168_i2c: !include pvbrain2/base/device_wk2168_i2c.yaml
|
||||
# device_sx1509: !include pvbrain2/base/device_sx1509.yaml
|
||||
device_canbus_node1: !include pvbrain2/base/device_canbus_esp32can.yaml
|
||||
device_canbus_node2: !include pvbrain2/base/device_canbus_mcp2515.yaml
|
||||
|
||||
# +--------------------------------------+
|
||||
# | YamBMS packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
# 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
|
||||
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
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_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
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_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
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
canbus_light_id: 'led_light_1' # on_board_light_io48
|
||||
# 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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: pvbrain2/base/device_debug.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
# Size of your PSRAM in bits
|
||||
# 8Mb='8388608' | 6Mb='6291456' | 4Mb='4194304' | 2Mb='2097152' | NoPSRAM='0'
|
||||
debug_psram_size: '8388608'
|
||||
@@ -1,263 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# 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
|
||||
|
||||
# device_board: !include
|
||||
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
|
||||
# vars:
|
||||
# yambms_id: 'yambms1'
|
||||
# canbus_id: 'canbus1'
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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
|
||||
# vars:
|
||||
# sniffer_id: 'sniffer1'
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
|
||||
|
||||
sniffer1: !include
|
||||
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
|
||||
# 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
|
||||
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'
|
||||
|
||||
bms2: !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: '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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,189 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# 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
|
||||
|
||||
device_board: !include
|
||||
file: packages/board/board_atom-s3.yaml
|
||||
vars:
|
||||
yambms_id: 'yambms1'
|
||||
canbus_id: 'canbus1'
|
||||
display_auto_next_page_interval: '5s'
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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
|
||||
# vars:
|
||||
# sniffer_id: 'sniffer1'
|
||||
# sniffer_protocol: 'JK02_32S'
|
||||
# sniffer_uart_id: 'uart_esp_1'
|
||||
# sniffer_talk_pin: 8 # ESP32: 4, ESP32-S3: 8, ESP32-C3: 10
|
||||
|
||||
sniffer1: !include
|
||||
file: packages/bms/bms_JK-PB_RS485_sniffer.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
|
||||
# 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
|
||||
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'
|
||||
|
||||
bms2: !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: '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'
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,173 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# If needed, configure a static IP here
|
||||
# ethernet:
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# 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
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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.yaml
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: 'uart_esp_1'
|
||||
|
||||
# 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
|
||||
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'
|
||||
|
||||
bms2: !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: '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'
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,280 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.1
|
||||
# GitHub : https://github.com/SeByDocKy/pvbrain2
|
||||
# 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: 'pvbrain2'
|
||||
|
||||
###### For extended UART ports with the 2 WK2168 ######
|
||||
|
||||
uart0_baudrate: '2400' #WKS {RJ45-UART0}
|
||||
uart1_baudrate: '38400' #JSY193
|
||||
uart2_baudrate: '19200' #smartshunt
|
||||
uart3_baudrate: '9600' #SRNE {RJ45-UART3}
|
||||
uart4_baudrate: '115200' #JK-BMS 1
|
||||
uart5_baudrate: '115200' #JK-BMS 2
|
||||
uart6_baudrate: '115200' #Pylontech
|
||||
uart7_baudrate: '9600' #EPEVER {RJ45-UART7}
|
||||
|
||||
#######################################################
|
||||
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | PVbrain2 packages |
|
||||
# +--------------------------------------+
|
||||
packages:
|
||||
device_base: !include packages/base/device_base.yaml
|
||||
device_board: !include packages/board/board_pvbrain2.yaml
|
||||
|
||||
# BUS
|
||||
# bus_i2c0: !include pvbrain2/base/device_bus_i2c0.yaml # SX1509 and BME280/BMP280
|
||||
bus_spi1: !include pvbrain2/base/device_bus_spi1.yaml # MCP2515
|
||||
# bus_one_wire: !include pvbrain2/base/device_bus_one_wire.yaml # Dallas
|
||||
|
||||
# Devices
|
||||
device_uart_esp: !include pvbrain2/base/device_uart_esp.yaml
|
||||
device_wk2168_spi: !include pvbrain2/base/device_wk2168_spi.yaml
|
||||
# device_wk2168_i2c: !include pvbrain2/base/device_wk2168_i2c.yaml
|
||||
# device_sx1509: !include pvbrain2/base/device_sx1509.yaml
|
||||
device_canbus_node1: !include pvbrain2/base/device_canbus_esp32can.yaml
|
||||
device_canbus_node2: !include pvbrain2/base/device_canbus_mcp2515.yaml
|
||||
|
||||
# +--------------------------------------+
|
||||
# | YamBMS packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
# 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
|
||||
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
|
||||
vars:
|
||||
sniffer_id: 'sniffer1'
|
||||
sniffer_protocol: 'JK02_32S'
|
||||
sniffer_uart_id: uart_${uart_hub_bus}_4
|
||||
|
||||
# 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
|
||||
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'
|
||||
|
||||
bms2: !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: '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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
canbus_light_id: 'led_light_1' # on_board_light_io48
|
||||
# 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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: pvbrain2/base/device_debug.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
# Size of your PSRAM in bits
|
||||
# 8Mb='8388608' | 6Mb='6291456' | 4Mb='4194304' | 2Mb='2097152' | NoPSRAM='0'
|
||||
debug_psram_size: '8388608'
|
||||
@@ -1,201 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# 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
|
||||
|
||||
# device_board: !include
|
||||
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
|
||||
# vars:
|
||||
# yambms_id: 'yambms1'
|
||||
# canbus_id: 'canbus1'
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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
|
||||
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
|
||||
|
||||
bms1: !include
|
||||
file: packages/bms/bms_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_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
|
||||
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
|
||||
|
||||
bms2: !include
|
||||
file: packages/bms/bms_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_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
|
||||
# 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
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,168 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# 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: DEBUG # DEBUG / INFO / WARN
|
||||
logs:
|
||||
esp32_ble_tracker: INFO
|
||||
esp32_ble_client: INFO
|
||||
|
||||
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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# PLEASE READ : https://github.com/Sleeper85/esphome-yambms/blob/main/documents/README/YamBMS_main_YAML_HowTo.md
|
||||
|
||||
# Max 3 BLE connections.
|
||||
# The BLE software stack (Bluedroid) on the ESP32 consumes a significant amount of RAM on the device.
|
||||
# Crashes are likely to occur if you include too many additional components in your device’s configuration.
|
||||
# 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
|
||||
|
||||
# device_board: !include
|
||||
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
|
||||
# vars:
|
||||
# yambms_id: 'yambms1'
|
||||
# canbus_id: 'canbus1'
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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
|
||||
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
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||
@@ -1,159 +0,0 @@
|
||||
# Updated : 2024.11.11
|
||||
# Version : 1.5.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:
|
||||
name: yambms
|
||||
|
||||
# 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
|
||||
|
||||
# +--------------------------------------+
|
||||
# | Packages |
|
||||
# +--------------------------------------+
|
||||
|
||||
# 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
|
||||
|
||||
# device_board: !include
|
||||
# file: packages/board/board_atom-s3.yaml # board_atom-s3r.yaml
|
||||
# vars:
|
||||
# yambms_id: 'yambms1'
|
||||
# canbus_id: 'canbus1'
|
||||
# display_auto_next_page_interval: '5s'
|
||||
|
||||
# shunt1: !include
|
||||
# file: packages/shunt/shunt_victron_smartshunt_UART.yaml # shunt_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
|
||||
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
|
||||
|
||||
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'
|
||||
# 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'
|
||||
|
||||
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'
|
||||
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 ) |
|
||||
# +--------------------------------------+
|
||||
|
||||
device_debug: !include
|
||||
file: packages/base/device_debug_ESP32.yaml
|
||||
vars:
|
||||
debug_name: 'Debug'
|
||||
debug_update_interval: '5s'
|
||||