Closed gurmukhp closed 6 months ago
The USB port should be configured where you have the USB device plugged in.
If you refer to mbusd, you have to either run mbusd natively or on Docker. In this case you specify the USB config in mbusd
Otherwise you need to identify, and configure the USB port in the options.yaml
Thanks for the quick reply, I'm not running any additional services for mbus, just the hass-addon-sunsynk-multi image. Should it be something like this?
DRIVER: umodbus
INVERTERS:
- PORT: serial:///dev/ttyUSB0
Yes, that looks better. I would use the pymodbus driver though, not umodbus
Thanks, do I need to run any additional services in Docker or is just the main Sunsynk one enough?
DRIVER: pymodbus
INVERTERS:
- PORT: /dev/ttyUSB0
I got it working, I had to pass in the device to the docker compose file too::
services:
sunsynk-multi:
restart: unless-stopped
image: ghcr.io/kellerza/hass-addon-sunsynk-multi/aarch64:stable
devices:
- /dev/ttyUSB0:/dev/ttyUSB0
volumes:
- ./options.yaml:/data/options.yaml
---
DRIVER: pymodbus
INVERTERS:
- SERIAL_NR: '007'
HA_PREFIX: SS
MODBUS_ID: 1
PORT: /dev/ttyUSB0
I could document this and raise a PR if you want?
A PR would be welcome & help people in the future. Thanks!
PErfect, I'll do that! thanks
That fixed my issue too. I was resorting to using TCP access via the Logger, but I wanted to use a cable.
Issue related to
Sunsynk / mbusd Home Assistant Add-On
Describe the issue/bug
I've copied over options.yaml and the error I'm getting is:
sunsynk-multi-1 | 17:57:45 INFO No response on the Modbus interface tcp://mbusd:502, see https://kellerza.github.io/sunsynk/guide/fault-finding
I haven't defined the dev/USB** device anywhere, I've just used the bundled mbus.
Do I need to define the USB device anywhere or should it 'just work'? I'm using the WAVE to USB adaptor.
Expected behavior Connect successfullly
Your environment
Your configuration
Logs