mbproxy - Lightweight Modbus TCP proxy with in-memory caching

[CiNcH83]

I am currently testing a fairly new Modbus Proxy - mbproxy. I have high hopes for it as it might really be able to equalize traffic to the respective device with its caching and cooldown delay after each request.

I am attaching my docker-compose.yml:

services:
  evcc:
    container_name: evcc
    image: evcc/evcc:latest
    command: ["evcc"]
    depends_on:
      - optimizer
      - mbproxy
    network_mode: host
    volumes:
      - /home/Automation/evcc/evcc.yaml:/etc/evcc.yaml
      - /home/Automation/evcc/.evcc:/root/.evcc
    environment:
      - OPTIMIZER_URI=http://localhost:7050
      - TZ=Europe/Berlin
    restart: unless-stopped

  optimizer:
    container_name: optimizer
    image: evcc/optimizer
    environment:
      - TZ=Europe/Berlin
      - OPTIMIZER_NUM_THREADS=2
      - OPTIMIZER_TIME_LIMIT=25
      - GUNICORN_CMD_ARGS=--workers 1 --max-requests 720
    network_mode: host
    restart: unless-stopped

  mbproxy:
    image: ghcr.io/tma/mbproxy
    ports:
      - "5022:5022"
    environment:
      MODBUS_LISTEN: ":5022"
      MODBUS_UPSTREAM: "192.168.1.12:502" # Huawei SUN2000
      MODBUS_CACHE_TTL: "10s"
      MODBUS_SLAVE_ID: "1"
      MODBUS_READONLY: "false"
      MODBUS_REQUEST_DELAY: "50ms" # cooldown delay after each request
      MODBUS_CONNECT_DELAY: "1s"
    restart: unless-stopped

Modbus connections in evcc (and other clients) have to be routed via the proxy on port 5022. URL to the upstream device has to be adapted to the device in use (in my case to the Huawei SUN2000).

Only shortcoming is that it does not support RS485 to the upstream device.