yasdi2mqtt will publish a JSON payload on the MQTT channel $MQTT_TOPIC_PREFIX/<device_sn> in the given update interval. Messages will be sent for each inverter individually and have the following format:

{"sn":000,"time":1586608779,"values": {
   "Iac":12580,
   "Uac":239,
   "Fac":50.019998881965876,
   "Pac":3006,
   "Zac":0.17200000816956162,
   "Riso":10000,
   "dI":4,
   "Upv-Ist":416,
   "PPV":3013,
   "E-Total":45358.538154414855,
   "h-Total":47797.772832013434,
   "h-On":51654.766385075491,
   "Netz-Ein":9012,
   "Seriennummer":000,
   "E-Total DC":45694.108978657052,
   "Status":"Mpp",
   "Fehler":"-------"
}}

1. Check yasdi.ini configuration
   • The included blueprint is pre-configured for directly attached RS485 adapters. Usually, no work needs to be done here, as you'll define the adapter mapping in step 3.
   • If you want to use IP-based communication instead, you should have a look on the yasdi manual or check out this discussion (German).
2. Create empty devices directory
   • Not necessary, but yasdi will use this folder as device data cache, so you'll save 1-2 minutes for device data download after the first startup.
3. Start container with the command below
   • Check out the table below for the environment variable mapping (-e flags).
   • You may adjust the serial adapter path (--device flag, the part before the colon) if not mapped to /dev/ttyUSB0 or drop it when using an IP-based setup.
   • After starting up, yasdi2mqtt should immediately connect to your MQTT broker.
   • Detected devices should be printed on stdout quite quickly, but the the initial device data download may delay the first data for 1-2 minutes.

docker run \
   --device /dev/ttyUSB0:/dev/ttyUSB0 \
   -v <project_dir>/devices:/etc/yasdi2mqtt/devices \
   -v <project_dir>/yasdi.ini:/etc/yasdi2mqtt/yasdi.ini:ro \
   -e YASDI_CONFIG="/etc/yasdi2mqtt/yasdi.ini" \
   -e YASDI_MAX_DEVICE_COUNT="1" \
   -e YASDI_UPDATE_INTERVAL="30" \
   -e MQTT_TOPIC_PREFIX="/solar/inverter" \
   -e MQTT_SERVER="example.com" \
   -e MQTT_PORT="1883" \
   -e MQTT_USER="johndoe" \
   -e MQTT_PASSWORD="sEcReT" \
   pkwagner/yasdi2mqtt:alpine

1. Install cJSON, Paho, and other project dependencies
   1. sudo apt install git gcc make cmake openssl libssl-dev libcjson1 libcjson-dev libpaho-mqtt1.3 libpaho-mqtt-dev (assuming an Ubuntu-based OS)
2. Clone and install YASDI
   1. mkdir projects/generic-cmake/build-gcc
   2. cd projects/generic-cmake/build-gcc
   3. cmake -D YASDI_DEBUG_OUTPUT=0 ..
   4. make
   5. sudo make install
3. Clone and install this repository
   1. make YASDI_PATH=<yasdi_dir>
   2. sudo make YASDI_PATH=<yasdi_dir> install
4. Check yasdi.ini configuration
   • The included blueprint is pre-configured for directly attached RS485 adapters, but you may want to adjust the serial adapter path.
   • If you want to use IP-based communication instead, you should have a look on the yasdi manual or check out this discussion (German).
5. Create empty devices directory
   • Not necessary, but yasdi will use this folder as device data cache, so you'll save 1-2 minutes for device data download after the first startup.
6. Set environment variables according to the table below
7. ./yasdi2mqtt
   • After starting up, yasdi2mqtt should immediately connect to your MQTT broker.
   • Detected devices should be printed on stdout quite quickly, but the the initial device data download may delay the first data for 1-2 minutes.

1. Click here to add this repository to your HA instance

   

2. Go to Settings -> Add-ons -> yasdi2mqtt and on the Configuration tab fills all needed information about your MQTT broker like this:

3. Create yasdi.ini file into your /config folder using File editor add-on with this content:

   • If you are connecting using ttyUSB adapter you can use this one as sample:

     [DriverModules]
     Driver0=yasdi_drv_serial
     
     # Configs for communiation over Ethernet/UDP
     # Replace 192.168.178.9 with the real IP address of your device
     
     [COM1]
     Device=/dev/ttyUSB0
     Media=RS485
     Baudrate=1200
     Protocol=SMANet
     

   • If you are connecting using RS485-over-IP you can use this one as sample:

      [DriverModules]
      Driver0=yasdi_drv_ip
     
      # Configs for communiation over Ethernet/UDP
      # Replace 192.168.0.10 with the real IP address of your device, communication is done by UDP ports 24272 and 24273 
     
      [IP0]
      Protocol=SMANet
      Device0=192.168.0.10
     

4. Start the add-on (enable also auto-startup and watch-dog)

   • You should wait about 1-2 minutes before the inverter's data will be visible.

5. Here are some MQTT sensors example that you can add on your Home Assistant instance (based on SunnyBoy SB3000):

   mqtt:
     sensor:
     - name: "Total Energy (from installation)"
       unique_id: "solar_generated_total"
       device_class: "energy"
       state_class: "total"
       unit_of_measurement: "kWh"
       state_topic: "sma/inverter/20xxxxxx"
       value_template: "{{ value_json['values']['E-Total'] }}"
     - name: "Total run time (from installation)"
       unique_id: "solar_hours_total"
       device_class: "duration"
       state_class: "total"
       unit_of_measurement: "h"
       state_topic: "sma/inverter/20xxxxxx"
       value_template: "{{ value_json['values']['h-Total'] }}"    
     - name: "Instant Power"
       unique_id: "solar_power_watt"
       device_class: "power"
       state_class: "measurement"
       unit_of_measurement: "W"
       state_topic: "sma/inverter/20xxxxxx"
       value_template: "{{ value_json['values']['Pac'] }}"
     - name: "CC Power"
       unique_id: "solar_power_cc"
       device_class: "voltage"
       state_class: "measurement"
       unit_of_measurement: "V"
       state_topic: "sma/inverter/20xxxxxx"
       value_template: "{{ value_json['values']['Upv-Ist'] }}"
     - name: "AC Power"
       unique_id: "solar_power_ac"
       device_class: "voltage"
       state_class: "measurement"
       unit_of_measurement: "V"
       state_topic: "sma/inverter/20xxxxxx"
       value_template: "{{ value_json['values']['Uac'] }}"
     - name: "AC Frequency"
       unique_id: "solar_power_ac_freq"
       device_class: "frequency"
       state_class: "measurement"
       unit_of_measurement: "Hz"
       state_topic: "sma/inverter/20xxxxxx"
       value_template: "{{ value_json['values']['Fac'] }}"
     - name: "Inverter State"
       unique_id: "solar_power_state"
       state_topic: "sma/inverter/20xxxxxx"
       value_template: "{{ value_json['values']['Status'] }}"
     - name: "Inverter Errors"
       unique_id: "solar_power_error"
       state_topic: "sma/inverter/20xxxxxx"
       value_template: "{{ value_json['values']['Fehler'] }}"
   

For other data details information, you can refer to your Inverter Installation\User Guide, for example SunnyBoy SB4200 has description of each value at paragraph 6.4