MODBUS data from SMA Inverter

pedro.goncalves · July 12, 2019, 6:51am

Mine would work with this. but since the last update it’s stopped working:

configuration.yaml:
modbus:
type: tcp
host: 16.1.1.144
port: 502

sensors.yaml:

platform: modbus
scan_interval: 10
registers:
- name: SMA Power AC
  unit_of_measurement: W
  slave: 3
  register: 30775
  count: 2
  data_type: int
- name: SMA Daily Yield
  unit_of_measurement: Wh
  slave: 3
  register: 30517
  count: 4
  data_type: int
- name: SMA Total
  unit_of_measurement: MWh
  slave: 3
  register: 30513
  count: 4
  data_type: int
- name: SMA Volt
  unit_of_measurement: V
  slave: 3
  register: 30783
  count: 2
  data_type: int
platform: template
sensors:
sma_current_solar:
value_template: “{% if states(‘sensor.sma_power_ac’)|float < 0 or states(‘sensor.sma_power_ac’)|float > 6000 %}0{% else %}{{ states(‘sensor.sma_power_ac’)}}{% endif %}”
friendly_name: ‘Current Solar’
unit_of_measurement: ‘Watt’
icon_template: mdi:flash-circle
sma_power:
value_template: “{% if states(‘sensor.sma_power_ac’)|float < 0 or states(‘sensor.sma_power_ac’)|float > 6000 %}0{% else %}{{ states(‘sensor.sma_power_ac’)}}{% endif %}”
friendly_name: ‘Power’
unit_of_measurement: ‘Watt’
icon_template: mdi:flash-circle
sma_day_production:
value_template: “{{ states(‘sensor.sma_daily_yield’) }}”
friendly_name: ‘Daily Yield’
unit_of_measurement: ‘Wh’
icon_template: mdi:flash-circle
sma_total_production:
value_template: “{{ (states(‘sensor.sma_total’) | float / 1000) | round(2) }}”
friendly_name: ‘Total Yield’
unit_of_measurement: ‘MWh’
icon_template: mdi:flash-circle
sma_voltage:
value_template: “{% if states(‘sensor.sma_volt’)|float < 0 %}0{% else %}{{ states(‘sensor.sma_volt’) | float / 100 | round(2)}}{% endif %}”
friendly_name: ‘Voltage’
unit_of_measurement: ‘V’
icon_template: mdi:flash-circle

Bard · July 14, 2019, 5:21pm

Hi Cheesewine
there are few different modbus function if you would like to read 40037 that means you are working with holding register type. In the sensor declaration, no need to write the entire number but only 37 because the “group” 40000 is already defined by the argument: register_type
for more information related modbus have a look on this site: Data Communication Solutions | Simply Modbus Software

Anyway try the following code:

sensor:
  - platform: modbus
    scan_interval: 10 #scan every 10 secs
    registers:
    - name: SI6ModelID
      hub: SI6
      slave: 1 #with TCP should be optional
      register: 37 # if not working try 36 some modbus map starting from 0 instead of 1
      register_type: holding
      count: 1

    - name: SB5ModelID
      hub: SB5000
      slave: 1
      register: 37
      register_type: holding
      count: 1

let me know
Ciao
Matteo

Cheesenwine · July 16, 2019, 11:51am

Thanks All. I tried all the various variations but still have no success. Although I do have a different error message now. Considering the errors and the tips @techs gave then I’m getting the feeling the problem is in properly connecting to modbus in the first place rather than reading the registers. Does this error mean anything to anyone?

Error while setting up platform modbus
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/modbus/sensor.py", line 92, in setup_platform
    hub = hass.data[MODBUS_DOMAIN][hub_name]
KeyError: 'default'

chris_ka · December 31, 2019, 11:07am

I think I have the solution. I just tried this out with my Sunny Tripower STB 6000TL-20

With slave ID 3 I get the right results with one addition to the sensor definition: register_type: input
Without it I get no data.

here my two snippets:

modbus:
  name: sma
  type: tcp
  host: 192.168.178.101
  port: 502


sensors:
  - platform: modbus
    scan_interval: 30
    registers:
      - name: Gesamtertrag
        hub: sma
        unit_of_measurement: kWh
        slave: 3
        register: 30531
        register_type: input
        count: 2

Morpheus1978 · January 3, 2020, 4:40pm

have u done any changes exept enable modbus udp and tcp at the inverter via sunny explorer ?
I try to connect to my stp 10000tl-20 with no luck so far .The Ip Adresses are choosen automaticaly so i try to get to the modbus via my sunny homemanager 2.0.

chris_ka · January 4, 2020, 8:01pm

Hi morpheus,

To enable this I only activated modbus tcp on the inverter. You must use the IP address from the inverter however.
I also have a home manager 2.0 setup. and I was not able to get any modbus communication with home Manager via tcp going so far. But I realized that the HomeManager 2.0 sends udp multicast messages every second with data from the built in energy meter.

So my approach is twofold.

I use a Node Red Flow to intercept the udp muticast messages from Home Manager 2.0 to get Energy in and out (current values and meters). see here: SMA Energy Meter in Home Assistant
I use the HA modbus integration to read the inverter.

So to get this to work you need to use the IP address from your inverter in the host section.

Cheesenwine · January 6, 2020, 2:22pm

@chris_ka thankyou. I just tried slave 3 and it finally started returning some sort of data. Although the data ins’t totally meaningful. I’m getting -1 as the result. For some other registers I’m getting some sort of number other than -1 but none are correct. Is it the “count” or something else I should be looking at?

chris_ka · January 6, 2020, 8:23pm

OK let’s do this step by step.

Prerequisites:

SMA Inverter which uses speedwire (Ethernet) or WiFi to connect to the local network. (Not bluetooth).
You can connect to the inverter with sunny explorer https://www.sma-america.com/products/monitoring-control/sunny-explorer.html
You have the password to log in as installer/plumber to change settings

Get the IP address of the inverter in your local Network. At daytime when the Inverter is sending data you can check your router to find the ip address. (note it down)
Start Sunny Explorer and connect to your Inverter. Go to Settings and open External Communication: You should find something similar to this
Inverter_Modbus_Setup800×346 31.1 KB
Note down the UnitID and TCP-Server port. Ensure that TCP-Server is active. If not change it!
Now get this document: http://files.sma.de/dl/2585/WEBBOX-MODBUS-TB-en-19.pdf
and have a look on page 28 Section 5.4.1 common Addresses of all SMA Devices. here you find the values for all relevant registers (ADR), the count (CNT) and their description.
configure modbus integration in Home Manager configuration

modbus:
  name: sma
  type: tcp
  host: 192.168.178.101    # use the ip address for your inverter as mentioned in the text
  port: 502                # use the port you saw in sunny explorer

configure modbus sensors in HA

sensors:
  - platform: modbus
    scan_interval: 30
    registers:
      - name: Gesamtertrag
        hub: sma
        unit_of_measurement: kWh   # see register description in section 5.4.1 of the document
        slave: 3                   # use the UnitID you found in Sunny Explorer
        register: 30531            # use a register from section 5.4.1 of the document
        register_type: input       # all registers starting with 3 need to have the type input
        count: 2                   # use the correct count for the register see section 5.4.1 of the document

Have fun

Cheesenwine · January 7, 2020, 8:44pm

Ah turns out getting the slave number, register and count right as per the SMA specs right can lead to point 7.

All seems to be working well except for a couple of registers such as model ID. Maybe my model is actually -1. in any case, it’ unimportant as the other values are working as expected.

Cheesenwine · January 11, 2020, 10:36pm

Just noting that I fount there are 2 different sets of Sunny Island (SI) register specifications. The Excel one that is found on the SMA website seems to be only partially correct which this one http://files.sma.de/dl/2585/WEBBOX-MODBUS-TB-en-19.pdf has registers that mostly work.

MBolt · February 2, 2020, 9:09pm

I use the following. This gets data out of the SMA Tripower 8.0. Not all registers seem to have the right variables I think. And if the power generated by the solar panels is to low or none, the most of the registers will go to the maximum value in the variable or so. Few still make sense like SMA total.

Does anyone else has the same experience?

configuration.yaml:

modbus:
  type: tcp
  host: 192.168.15.35
  port: 502

sensor.yaml

  - platform: modbus
    scan_interval: 10
    registers:
    - name: SMA Power L1
      unit_of_measurement: kW
      slave: 3
      register: 30777
      count: 2
      data_type: uint
      scale: 0.001
      precision: 2
    - name: SMA Power L2
      unit_of_measurement: kW
      slave: 3
      register: 30779
      count: 2
      data_type: uint
      scale: 0.001
      precision: 2
    - name: SMA Power L3
      unit_of_measurement: kW
      slave: 3
      register: 30781
      count: 2
      data_type: uint
      scale: 0.001
      precision: 2
    - name: SMA Stroom L1
      unit_of_measurement: A
      slave: 3
      register: 30977
      count: 2
      data_type: uint
      scale: 0.001
      precision: 2
    - name: SMA Stroom L2
      unit_of_measurement: A
      slave: 3
      register: 30979
      count: 2
      data_type: uint
      scale: 0.001
      precision: 2
    - name: SMA Stroom L3
      unit_of_measurement: A
      slave: 3
      register: 30981
      count: 2
      data_type: uint
      scale: 0.001
      precision: 2
    - name: SMA Spanning L1
      unit_of_measurement: V
      slave: 3
      register: 30783
      count: 2
      data_type: uint
      scale: 0.01
      precision: 1
    - name: SMA Spanning L2
      unit_of_measurement: V
      slave: 3
      register: 30785
      count: 2
      data_type: uint
      scale: 0.01
      precision: 1
    - name: SMA Spanning L3
      unit_of_measurement: V
      slave: 3
      register: 30787
      count: 2
      data_type: uint
      scale: 0.01
      precision: 1
    - name: SMA Netfrequentie
      unit_of_measurement: Hz
      slave: 3
      register: 30803
      count: 2
      data_type: uint
      scale: 0.01
      precision: 2
    - name: SMA power
      unit_of_measurement: k
      slave: 3
      register: 30775
      count: 2
      data_type: int
      scale: 0.001
      precision: 2
    - name: SMA Total
      unit_of_measurement: kW
      slave: 3
      register: 30529
      count: 2
      data_type: uint
      scale: 0.001
      precision: 2
    - name: SMA Today
      unit_of_measurement: kWh
      slave: 3
      register: 30535
      count: 2
      data_type: uint
      scale: 0.001
      precision: 2
    - name: SMA device type 9347 = 8.0
      slave: 3
      register: 30053
      count: 2
      data_type: int 
    - name: SMA grid relay 51=Closed 311= Open
      slave: 3
      register: 30217
      count: 2
      data_type: int

And would colde like the code in the bottom of this message be a good catch to go to ‘0’ in stead of high values?

  - platform: SMA
    sensors:
      sma_power_power:
        value_template: “{% if states(‘sensor.sma_power_l1’)|float < 0 %}0{% else %}{{ states(‘sensor.sma_power_l1’) | float / 100 | round(2)}}{% endif %}”
        friendly_name: ‘Power’
        unit_of_measurement: ‘W’
        icon_template: mdi:flash-circle

chris_ka · February 12, 2020, 2:33pm

Hi MBolt,

I solved this by using an additional template sensor using the modbus sensor as input like this:

      power_sma_filtered:
        friendly_name: "Erzeugung aktuell"
        unit_of_measurement: W
        value_template: >-
          {% if (states('sensor.power_sma')|int >= 10000 or states('sensor.power_smal')|int < 0) %}
            0
          {% else %}
            {{(states('sensor.power_sma')|int)}}
          {% endif %}

filip-van-hoeckel · March 29, 2020, 7:26pm

I use this in config

# SMA over modbus
modbus:
  type: tcp
  host: 192.168.178.171
  port: 502

and this in sensors

- platform: modbus
  scan_interval: 30
  registers:
    - name: Gesamtertrag
      hub: sma
      unit_of_measurement: kWh   # see register description in section 5.4.1 of the document
      slave: 3                   # use the UnitID you found in Sunny Explorer
      register: 30531            # use a register from section 5.4.1 of the document
      register_type: input       # all registers starting with 3 need to have the type input
      count: 2                   # use the correct count for the register see section 5.4.1 of the document

and get this error in my log

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 179, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/modbus/sensor.py", line 129, in setup_platform
    hub = hass.data[MODBUS_DOMAIN][hub_name]
KeyError: 'sma'

I can login to the webinterface just fine. I came here bc the standard SMA integration was not working, but am having issues with this as well. Anyone care to shed some light on this?

djmoonshine · April 1, 2020, 9:49pm

I think it’s because you are missing the sma name for the modbus tcp, port and ip settings.
Add “name: sma” or it might also work if you remove “hub: sma” from the registers.

You have:

# SMA over modbus
modbus:
  type: tcp
  host: 192.168.178.171
  port: 502

Should be (if you use “hub: sma”)

# SMA over modbus
modbus:
  name: sma
  type: tcp
  host: 192.168.178.171
  port: 502

MBolt · April 10, 2020, 11:40am

I will try this too

chris_ka · April 12, 2020, 9:11am

Modbus seems broken in 0.108 before in worked perfectly.
There were fixes in 0.108.2

Fix modbus default delay (@janiversen - #33877) (modbus docs)

The new default delay is 0.

delay
(integer)(Optional)
Time to sleep in seconds after connecting and before sending messages. Some modbus-tcp servers need a short delay typically 1-2 seconds in order to prepare the communication. If a server accepts connecting, but there is no response to the requests send, this parameter might help.

Default value:
0

My modbus integration looked like this

modbus:
  name: sma
  type: tcp
  host: 192.168.178.101
  port: 502

Unfortunately after adding the delay parameter with 1 or 2 doesn’t help. I get the following errors:

Logger: pymodbus.factory
Source: __main__.py:342 
First occurred: 11:26:58 (6 occurrences) 
Last logged: 11:29:32

Unable to decode response Modbus Error: Unknown response 59
Unable to decode response Modbus Error: Unknown response 90
Unable to decode response Modbus Error: Unknown response 125
index out of range

Logger: homeassistant.core
Source: /usr/src/homeassistant/homeassistant/core.py:144 
First occurred: 11:26:58 (6 occurrences) 
Last logged: 11:29:32

Error doing job: Fatal error: protocol.data_received() call failed.
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 826, in _read_ready__data_received
    self._protocol.data_received(data)
  File "/usr/local/lib/python3.7/site-packages/pymodbus/client/asynchronous/asyncio/__init__.py", line 192, in data_received
    self._dataReceived(data)
  File "/usr/local/lib/python3.7/site-packages/pymodbus/client/asynchronous/asyncio/__init__.py", line 139, in _dataReceived
    self.framer.processIncomingPacket(data, self._handleResponse, unit=unit)
  File "/usr/local/lib/python3.7/site-packages/pymodbus/framer/socket_framer.py", line 165, in processIncomingPacket
    self._process(callback, error=True)
  File "/usr/local/lib/python3.7/site-packages/pymodbus/framer/socket_framer.py", line 175, in _process
    raise ModbusIOException("Unable to decode request")
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] Unable to decode request

olalid · April 12, 2020, 9:36pm

I have the same issue with 0.108.1-3.
Reverted to 0.107.7 and it works fine again.

chris_ka · April 13, 2020, 12:53pm

Yes modbus is definitely broken in 0.108 1-3
I stay on 0.108.3 but I switched to NodeRed and MQTT to retrieve my modbus data.
everything works now again.

I wrote a tutorial how to do this:

drmcinnes · April 15, 2020, 4:35am

I thought it was me!, nothing would make my SunGrow inverter connect reliably.

I gave up on the Modbus intergration and went node-red also

chris_ka · April 15, 2020, 7:44am

Hi Darren, welcome to the club!
I see that you use the Modbus reader with input definition via a function block. Do you mind sharing the content of the block. I would like to add this approach to my tutorial with reference to your post

regards Chris