Standalone Configuration Help

[SyphonxZA]

Hi, I am trying to setup the standalone option:

• Raspberry Pi 3B with Raspberry OS
• USB to RS485 cable, purchased this one: https://solar-assistant.io/shop/products/sunsynk_rs485
• Using the prebuilt docker image
• Installed mbusd as a system service (https://github.com/3cky/mbusd).

My docker compose:

services:
  sunsynk-multi:
    image: ghcr.io/kellerza/hass-addon-sunsynk-multi/armv7:stable
    container_name: sunsynk-multi
    environment:
    - PUID=${PUID}
    - PGID=${PGID}
    - TZ=${TZ}
    devices:
    - /dev/ttyUSB0:/dev/ttyUSB0
    volumes:
    - /home/user/docker/sunsynk-multi/options.yaml:/data/options.yaml
    restart: unless-stopped

Options file

---
DRIVER: umodbus
INVERTERS:
  - SERIAL_NR: "007"
    HA_PREFIX: SS
    MODBUS_ID: 01
    PORT: tcp://192.168.10.183:502
SENSOR_DEFINITIONS: single-phase
SENSORS:
  - energy_management
  - power_flow_card
SENSORS_FIRST_INVERTER: []
MANUFACTURER: Sunsynk
READ_ALLOW_GAP: 2
READ_SENSORS_BATCH_SIZE: 8
SCHEDULES:
  - KEY: W
    READ_EVERY: 5
    REPORT_EVERY: 60
    CHANGE_ANY: false
    CHANGE_BY: 80
    CHANGE_PERCENT: 0
NUMBER_ENTITY_MODE: auto
MQTT_HOST: 192.168.10.50
MQTT_PORT: 1883
MQTT_USERNAME: hass
MQTT_PASSWORD: 'password'
DEBUG: 0
DEBUG_DEVICE: "/dev/ttyAMA0"

MBUSD config file:

# Serial port device name
device = /dev/ttyUSB0

# Serial port speed (Folow on your PLC or Modbus Device config)
speed = 9600

# Serial port mode (Folow on your PLC or Modbus Device config)
mode = 8n1

# RS-485 data direction control type (addc, rts, sysfs_0, sysfs_1)
trx_control = addc

# Sysfs file to use to control data direction
# trx_sysfile =

############# TCP port settings #############

# TCP server address to bind
address = 0.0.0.0

# TCP server port number
port = 502

# Maximum number of simultaneous TCP connections
maxconn = 32

# Connection timeout value in seconds
timeout = 5

######### Request/response settings #########

# Maximum number of request retries
retries = 3

# Pause between requests in milliseconds
pause = 100

# Response wait time in milliseconds
wait = 500

I am unable to get it working. I am confused as to whether I should be using MBUSD service and connect via TCP or pass the USB device into the container and the image has the necessary code to access the data without MBUSD? Thanks for any assistance.

These are the container logs with the above settings

sunsynk-multi  | s6-rc: info: service s6rc-oneshot-runner: starting
sunsynk-multi  | s6-rc: info: service s6rc-oneshot-runner successfully started
sunsynk-multi  | s6-rc: info: service fix-attrs: starting
sunsynk-multi  | s6-rc: info: service fix-attrs successfully started
sunsynk-multi  | s6-rc: info: service legacy-cont-init: starting
sunsynk-multi  | s6-rc: info: service legacy-cont-init successfully started
sunsynk-multi  | s6-rc: info: service legacy-services: starting
sunsynk-multi  | services-up: info: copying legacy longrun sunsynk (no readiness notification)
sunsynk-multi  | s6-rc: info: service legacy-services successfully started
sunsynk-multi  | 09:19:10 INFO    Loading configuration: /data/options.yaml
sunsynk-multi  | 09:19:10 INFO    sunsynk library version: 0.6.4
sunsynk-multi  | 09:19:10 INFO    Schedules:
sunsynk-multi  | +-----------+-----+------+--------+-----------+----------+------------+
sunsynk-multi  | |    Key    | src | Read | Report | Change by | Change % | Change any |
sunsynk-multi  | +-----------+-----+------+--------+-----------+----------+------------+
sunsynk-multi  | | date_time |     |  60  |   60   |           |          |    True    |
sunsynk-multi  | |     rw    |     |  5   |  300   |           |          |    True    |
sunsynk-multi  | |     w     |  *  |  5   |   60   |     80    |          |            |
sunsynk-multi  | |    kwh    |     | 300  |  300   |           |          |            |
sunsynk-multi  | |  any_unit |     |  15  |  300   |           |          |            |
sunsynk-multi  | |  no_unit  |     |  15  |  300   |           |          |    True    |
sunsynk-multi  | +-----------+-----+------+--------+-----------+----------+------------+
sunsynk-multi  | 09:19:10 INFO    Using Single phase sensor definitions.
sunsynk-multi  | 09:19:10 INFO    Added hidden sensors as other sensors depend on it: Rated power, Serial
sunsynk-multi  | 09:19:10 INFO    Connecting to tcp://192.168.10.183:502
sunsynk-multi  | 09:19:10 INFO    Reading startup sensors Rated power, Serial
sunsynk-multi  | 09:19:14 ERROR   GatewayTargetDeviceFailedToRespondError reading 5 registers from 3: ; GatewayTargetDeviceFailedToRespondError reading 2 registers from 16:
sunsynk-multi  | 09:19:18 ERROR   GatewayTargetDeviceFailedToRespondError reading 5 registers from 3: ; GatewayTargetDeviceFailedToRespondError reading 2 registers from 16:
sunsynk-multi  | 09:19:23 ERROR   GatewayTargetDeviceFailedToRespondError reading 5 registers from 3: ; GatewayTargetDeviceFailedToRespondError reading 2 registers from 16:
sunsynk-multi  | 09:19:23 WARNING Retrying individual sensors: ['rated_power', 'serial']
sunsynk-multi  | 09:19:25 ERROR   GatewayTargetDeviceFailedToRespondError reading 2 registers from 16:  Rated power
sunsynk-multi  | 09:19:27 ERROR   GatewayTargetDeviceFailedToRespondError reading 5 registers from 3:  Serial
sunsynk-multi  | 09:19:27 CRITICAL Could not read sensors: ['Rated power', 'Serial']
sunsynk-multi  | 09:19:27 INFO    ############################################################
sunsynk-multi  | 09:19:27 INFO    No response on the Modbus interface tcp://192.168.10.183:502, see https://kellerza.github.io/sunsynk/guide/fault-finding
sunsynk-multi  | 09:19:27 INFO    ############################################################
sunsynk-multi  | 09:19:27 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.

[kellerza]

It seems like the addon is ok, but not happy with mbusd config

 GatewayTargetDeviceFailedToRespondError

For the mbusd addon I only use these cmdline args - https://github.com/kellerza/sunsynk/blob/main/hass-addon-mbusd/run.sh
why do you set trx_control?

[SyphonxZA]

I just left it as the default, but after commenting it out its still not happy. I am going to try the add on method on a spare Pi to test further.

[kellerza]

Or everything is ok, but your wiring is bad - see the fault finding section

[SyphonxZA]

Same issue with using the repository add on, but I have found the issue. My inverter has the newer combined RS485/CAN port, but next to it is another unused RS485 port (which I was using). Unfortunately that port does not work for this application. I will need to get the splitter cable so I can connect both the battery and Pi at the same time.

[kellerza]

This should be in the fault-finding 😉