B2500 Meter

This project emulates Smart Meter devices for Marstek storage systems such as the B2500, Marstek Jupiter, and Marstek Venus energy storage systems while allowing integration with almost any smart meter. It does this by emulating one or more of the following devices:

• CT001
• Shelly Pro 3EM
• Shelly EM gen3
• Shelly Pro EM50

Getting Started

The B2500 Meter project can be installed and run in several ways depending on your needs and environment:

1. Home Assistant Add-on (Recommended for Home Assistant users)

   • Easiest installation method if you're using Home Assistant
   • Provides a user-friendly interface for configuration
   • Integrates seamlessly with your Home Assistant installation

2. Docker (Recommended for standalone server deployment)

   • Containerized solution that works on any Docker-compatible system
   • Easy deployment and updates
   • Consistent environment across different platforms

3. Direct Installation (For development or custom setups)

   • Manual installation on Windows, macOS, or Linux
   • Requires Python environment setup
   • More flexible for customization and development

Home Assistant Add-on Installation

1. Add the Repository to Home Assistant

   

2. Install the Add-on

   • Click on "Add-on Store" in the bottom right corner
   • The B2500 Meter add-on should appear in the add-on store
   • Click on it and then click "Install"

3. Configure the Add-on You can configure the add-on in two ways:

   A) Using the Add-on Configuration Interface:

   • After installation, go to the add-on's Configuration tab
   • For single-phase monitoring:
     • Set the Power Input Alias and optionally the Power Output Alias to the entity IDs of your power sensors
   • For three-phase monitoring:
     • Set the Power Input Alias to a comma-separated list of three entity IDs (one for each phase)
     • If using calculated power, also set the Power Output Alias to a comma-separated list of three entity IDs
     • Example: sensor.phase1,sensor.phase2,sensor.phase3
   • Set Device Types (comma-separated list) to the device types you want to emulate (ct001, shellypro3em, shellyemg3, shellyproem50)
   • Click "Save" to apply the configuration

   B) Using a Custom Configuration File for Advanced Configuration:

   • Create a config.ini file based on the examples in the Configuration section
   • Place the file in /addon_configs/a0ef98c5_b2500_meter/. You can do that via "File editor" Addon in Home Assistant. Make sure to disable the "Enforce Basepath" setting in the File editor Addon config to access the /addon_configs folder.
   • In the add-on configuration, set Custom Config to the filename (e.g., "config.ini" without the path)
   • When using a custom configuration file, other configuration options will be ignored

4. Start the Add-on

   • Go to the add-on's Info tab
   • Click "Start" to run the add-on

Docker Installation

Prerequisites

• Docker installed on your system
• Docker Compose (optional, but recommended)

Installation Steps

1. Create a directory for the project
2. Create your config.ini file
3. Use the provided docker-compose.yaml to start the container:

   docker-compose up -d

Note: Host network mode is required because the B2500 device uses UDP broadcasts for device discovery. Without host networking, the container won't be able to receive these broadcasts properly.

Direct Installation

Prerequisites

1. Python Installation: Make sure you have Python 3.7 or higher installed. You can download it from the official Python website.
2. Configuration: Create a config.ini file in the root directory of the project and add the appropriate configuration as described in the Configuration section.

Installation Steps

1. Open Terminal/Command Prompt

   • Windows: Press Win + R, type cmd, press Enter
   • macOS: Press Cmd + Space, type Terminal, press Enter
   • Linux: Use your preferred terminal emulator

2. Navigate to Project Directory

   cd path/to/b2500-meter

3. Install Dependencies

   pipenv install

4. Run the Script

   pipenv run python main.py

All commands above work across Windows, macOS, and Linux. The only difference is how you open your terminal.

Additional Notes

When the script is running, switch your B2500 to "Self-Adaptation" mode to enable the powermeter functionality.

Configuration

Configuration is managed via config.ini. Each powermeter type has specific settings.

General Configuration

[GENERAL]
# Comma-separated list of device types to emulate (ct001, shellypro3em, shellyemg3, shellyproem50)
DEVICE_TYPE = ct001
# Skip initial powermeter test on startup
SKIP_POWERMETER_TEST = False
# Sum power values of all phases and report on phase 1 (ct001 only and default is False)
DISABLE_SUM_PHASES = False
# Send absolute values (necessary for storage system) (ct001 only and default is False)
DISABLE_ABSOLUTE_VALUES = False
# Interval for sending power values in seconds (ct001 only and default is 1)
POLL_INTERVAL = 1

Shelly

Shelly 1PM

[SHELLY]
TYPE = 1PM
IP = 192.168.1.100
USER = username
PASS = password
METER_INDEX = meter1

Shelly Plus 1PM

[SHELLY]
TYPE = PLUS1PM
IP = 192.168.1.100
USER = username
PASS = password
METER_INDEX = meter1

Shelly EM

[SHELLY]
TYPE = EM
IP = 192.168.1.100
USER = username
PASS = password
METER_INDEX = meter1

Shelly 3EM

[SHELLY]
TYPE = 3EM
IP = 192.168.1.100
USER = username
PASS = password
METER_INDEX = meter1

Shelly 3EM Pro

[SHELLY]
TYPE = 3EMPro
IP = 192.168.1.100
USER = username
PASS = password
METER_INDEX = meter1

Tasmota

[TASMOTA]
IP = 192.168.1.101
USER = tasmota_user
PASS = tasmota_pass
JSON_STATUS = StatusSNS
JSON_PAYLOAD_MQTT_PREFIX = SML
JSON_POWER_MQTT_LABEL = Power
JSON_POWER_INPUT_MQTT_LABEL = Power1
JSON_POWER_OUTPUT_MQTT_LABEL = Power2
JSON_POWER_CALCULATE = True

Shrdzm

[SHRDZM]
IP = 192.168.1.102
USER = shrdzm_user
PASS = shrdzm_pass

Emlog

[EMLOG]
IP = 192.168.1.103
METER_INDEX = 0
JSON_POWER_CALCULATE = True

IoBroker

[IOBROKER]
IP = 192.168.1.104
PORT = 8087
CURRENT_POWER_ALIAS = Alias.0.power
POWER_CALCULATE = True
POWER_INPUT_ALIAS = Alias.0.power_in
POWER_OUTPUT_ALIAS = Alias.0.power_out

HomeAssistant

[HOMEASSISTANT]
IP = 192.168.1.105
PORT = 8123
# Use HTTPS - if empty False is Fallback
HTTPS = ""|True|False
ACCESSTOKEN = YOUR_ACCESS_TOKEN
# The entity or entities (comma-separated for 3-phase) that provide current power
CURRENT_POWER_ENTITY = ""|sensor.current_power|sensor.phase1,sensor.phase2,sensor.phase3
# If False or Empty the power is not calculated - if empty False is Fallback
POWER_CALCULATE = ""|True|False 
# The entity or entities (comma-separated for 3-phase) that provide power input
POWER_INPUT_ALIAS = ""|sensor.power_input|sensor.power_in_1,sensor.power_in_2,sensor.power_in_3
# The entity or entities (comma-separated for 3-phase) that provide power output
POWER_OUTPUT_ALIAS = ""|sensor.power_output|sensor.power_out_1,sensor.power_out_2,sensor.power_out_3
# Is a Path Prefix needed?
API_PATH_PREFIX = ""|/core

Example: Variant 1 with a single combined input & output sensor

[HOMEASSISTANT]
IP = 192.168.1.105
PORT = 8123
HTTPS = True
ACCESSTOKEN = YOUR_ACCESS_TOKEN
CURRENT_POWER_ENTITY = sensor.current_power 

Example: Variant 2 with separate input & output sensors

[HOMEASSISTANT]
IP = 192.168.1.105
PORT = 8123
HTTPS = True
ACCESSTOKEN = YOUR_ACCESS_TOKEN
POWER_CALCULATE = True
POWER_INPUT_ALIAS = sensor.power_input
POWER_OUTPUT_ALIAS = sensor.power_output

Example: Variant 3 with three-phase power monitoring

[HOMEASSISTANT]
IP = 192.168.1.105
PORT = 8123
HTTPS = True
ACCESSTOKEN = YOUR_ACCESS_TOKEN
CURRENT_POWER_ENTITY = sensor.phase1,sensor.phase2,sensor.phase3

Example: Variant 4 with three-phase power calculation

[HOMEASSISTANT]
IP = 192.168.1.105
PORT = 8123
HTTPS = True
ACCESSTOKEN = YOUR_ACCESS_TOKEN
POWER_CALCULATE = True
POWER_INPUT_ALIAS = sensor.power_in_1,sensor.power_in_2,sensor.power_in_3
POWER_OUTPUT_ALIAS = sensor.power_out_1,sensor.power_out_2,sensor.power_out_3

VZLogger

[VZLOGGER]
IP = 192.168.1.106
PORT = 8080
UUID = your-uuid

ESPHome

[ESPHOME]
IP = 192.168.1.107
PORT = 6052
DOMAIN = your_domain
ID = your_id

AMIS Reader

[AMIS_READER]
IP = 192.168.1.108

Modbus TCP

[MODBUS]
HOST = 192.168.1.100
PORT = 502
UNIT_ID = 1
ADDRESS = 0
COUNT = 1

MQTT

[MQTT]
BROKER = broker.example.com
PORT = 1883
TOPIC = home/powermeter
JSON_PATH = $.path.to.value (Optional for JSON payloads)
USERNAME = mqtt_user (Optional)
PASSWORD = mqtt_pass (Optional)

The JSON_PATH option is used to extract the power value from a JSON payload. The path must be a valid JSONPath expression. If the payload is a simple integer value, you can omit this option.

Modbus

[MODBUS]
IP =
PORT =
UNIT_ID =
REGISTER =

Script

You can also use a custom script to get the power values. The script should output at most 3 integer values, separated by a line break.

[SCRIPT]
COMMAND = /path/to/your/script.sh

Multiple Powermeters

You can configure multiple powermeters by adding additional sections with the same prefix (e.g. [SHELLY<unique_suffix>]). Each powermeter should specify which client IP addresses are allowed to access it using the NETMASK setting.

When a storage system requests power values, the script will check the client IP address against the NETMASK settings of each powermeter and use the first that matches.

[SHELLY_1]
TYPE = 1PM
IP = 192.168.1.100
USER = username
PASS = password
NETMASK = 192.168.1.50/32

[SHELLY_2]
TYPE = 3EM
IP = 192.168.1.101
USER = username
PASS = password
# You can specify multiple IPs by separating them with a comma:
NETMASK = 192.168.1.51/32,192.168.1.52/32

[HOMEASSISTANT_1]
IP = 192.168.1.105
PORT = 8123
HTTPS = True
ACCESSTOKEN = YOUR_ACCESS_TOKEN
CURRENT_POWER_ENTITY = sensor.current_power
# No NETMASK specified - will match all clients (0.0.0.0/0)

Node-RED Implementation

This project also provides a Node-RED implementation, allowing integration with various smart meters. The Node-RED flow is available in the nodered.json file. Note that the Node-RED implementation only supports emulating a CT001.

Installation and Setup

1. Import the Node-RED Flow

   • Open your Node-RED dashboard.
   • Navigate to the menu in the top right corner, select "Import" and then "Clipboard".
   • Copy the content of nodered.json and paste it into the import dialog, then click "Import".

2. Hooking Powermeter Readings

   • Ensure your powermeter readings are available as a Node-RED message with the power values in the payload.
   • Connect the output of your powermeter reading nodes to the input node of the subflow named "B2500". The subflow can handle:
     • An array of 3 numbers or strings containing numbers, representing the power values of each phase, e.g. [100, 200, 300].
     • A single number or string containing a number, which will be interpreted as the value for the first phase, with the other two phases set to 0.
   • Ensure that a fresh powermeter reading is sent to the flow every second.

3. Running the Flow

   • Deploy the flow by clicking the "Deploy" button on the top right corner of the Node-RED dashboard.
   • The flow will now listen for powermeter readings and handle the UDP and TCP communications as configured.

License

This project is licensed under the General Public License v3.0 - see the LICENSE file for details.