Incorrect output-power value in the web portal

[ditec-de]

Hello Sebastian,

first of all I would like to thank you for this great project.

I have a silent 48V/ 1200W SoyoSource with display in use.
I tapped the connection between the mainboard and the display with an Y- cable and connected it to a Wemos D1 mini. From the D1 mini goes also a RS-485 control cable to the inverter.
I get the consumption values of the house from a Shelly 3EM.
All control and regulation functions are available and the system has been running stable for 2 weeks.

Now I noticed something that I can't explain, maybe someone here has seen this before.
If I limit the inverter to, say, 350 W (Limiter Mode), but my home grid requests more (say, 500 W), the web portal shows almost 400 W in the "output-power" section.
The SoyoSource display shows the approx 350 W and the downstream power meter (Shelly 1PM) also shows values around 350 watts.

Does anyone have an idea or solution to this ?

Thanks
-D

Yaml:

substitutions:
  name: soyosource-controller
  device_description: "Monitor and control the Soyosource GTN (Display version) via the display port and control the power output on demand via RS485"
  external_components_source: github://syssi/esphome-soyosource-gtn-virtual-meter@main
  # The internal display port should be connected to these GPIOs using a JST XH 2.54mm, 4 Pin connector (RX, TX, GND, VCC)
  # A optocoupler / optical isolator (f.e. ADUM1201) between the display port and the ESP is recommended if the ESP isn't powered by the display port!
  tx_pin_ttl_wifi: GPIO4
  rx_pin_ttl_wifi: GPIO5
  tx_pin_rs485: GPIO14
  rx_pin_rs485: GPIO12
  shelly_3em_url: "http://192.xxx.xxx.xxx/status/"

esphome:
  name: ${name}
  comment: ${device_description}
  project:
    name: "syssi.esphome-soyosource-gtn-virtual-meter"
    version: 2.1.0

esp8266:
  board: d1_mini

external_components:
  - source: ${external_components_source}
    refresh: 0s

# Enable Home Assistant API
api:
  encryption:
    key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxx"

# Enable Over The Air updates
ota:
  password: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  manual_ip:
    static_ip: 192.xxx.xxx.xxx
    gateway: 192.xxx.xxx.xxx
    subnet: 255.255.255.0

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Esphome-Web-xxxxx"
    password: "xxxxxxxxxxxxx"

# Enable Web server.
web_server:
  port: 80
  

logger:
  level: DEBUG

# If you use Home Assistant please remove this `mqtt` section and uncomment the `api` component!
# The native API has many advantages over MQTT: https://esphome.io/components/api.html#advantages-over-mqtt
#mqtt:
#  broker: !secret mqtt_host
#  username: !secret mqtt_username
#  password: !secret mqtt_password
#  id: mqtt_client

# Zero readout
http_request:
  id: http_request0
  useragent: esphome/device
  timeout: 1000ms

uart:
  - id: uart_0
    baud_rate: 9600
    tx_pin: ${tx_pin_ttl_wifi}
    rx_pin: ${rx_pin_ttl_wifi}

  - id: uart_1
    baud_rate: 4800
    tx_pin: ${tx_pin_rs485}
    rx_pin: ${rx_pin_rs485}

soyosource_modbus:
  - id: modbus0
    uart_id: uart_1
    # flow_control_pin: GPIO12

    # Optional settings
    #
    # The name is used as prefix for some log messages and should
    # help to distinguish between different instances/devices
    name: firstfloor_inverter

soyosource_virtual_meter:
  - id: virtualmeter0
    soyosource_modbus_id: modbus0

    # The state of this sensor (instantaneous power in watt) is used as source
    power_id: powermeter0

    # Optional settings
    power_sensor_inactivity_timeout: 20s
    power_demand_calculation: NEGATIVE_MEASUREMENTS_REQUIRED
    min_power_demand: 0
    max_power_demand: 900
    zero_output_on_min_power_demand: true
    # Split/distribute the power demand if you have multiple inverters attached to the same RS485 bus
    power_demand_divider: 1
    # A positive buffer value (10) tries to avoid exporting power to the grid (demand - 10 watts)
    # A negative buffer value (-10) exports power to the grid (demand + 10 watts)
    buffer: 10
    # The operation_status_id sensor is expected here. Passing the operation_status won't work
    # The state is used to suspend the limiter if the operation status of the inverter isn't 0x0 (normal)
    operation_status_id: operation_status_id0

    # The update interval is important and defaults to 3 seconds. If the demand is sent too frequently
    # or rarely the interverter stops. TODO: Identify and validate the lower and upper update limit
    update_interval: 3s

soyosource_display:
  - id: display0
    uart_id: uart_0
    protocol_version: SOYOSOURCE_DISPLAY_VERSION
    update_interval: 5s

binary_sensor:
  - platform: soyosource_display
    fan_running:
      name: "${name} fan running"
    limiter_connected:
      name: "${name} limiter connected"

button:
  - platform: soyosource_display
    restart:
      name: "${name} restart"

number:
  - platform: soyosource_virtual_meter
    soyosource_virtual_meter_id: virtualmeter0
    buffer:
      name: "${name} buffer"
      initial_value: 10
      restore_value: true
    manual_power_demand:
      name: "${name} manual power demand"
      max_value: 900
    max_power_demand:
      name: "${name} max power demand"
      initial_value: 600
      max_value: 900
      restore_value: true
    power_demand_divider:
      name: "${name} power demand divider"
      initial_value: 1
      restore_value: true

  - platform: soyosource_display
    start_voltage:
      name: "${name} start voltage"
    shutdown_voltage:
      name: "${name} shutdown voltage"
    # Maximum output power in limiter mode / Output power in constant power mode
    output_power_limit:
      name: "${name} output power limit"
    start_delay:
      name: "${name} start delay"

select:
  - platform: soyosource_display
    operation_mode:
      name: "${name} operation mode"
      optionsmap:
        1: "Battery Constant Power"
        2: "PV"
        16: "Battery Limit"

sensor:
  - platform: soyosource_virtual_meter
    soyosource_virtual_meter_id: virtualmeter0
    power_demand:
      name: "${name} power demand"

  - platform: soyosource_display
    error_bitmask:
      name: "${name} error bitmask"
    operation_mode_id:
      name: "${name} operation mode id"
    operation_status_id:
      name: "${name} operation status id"
      id: operation_status_id0
    battery_voltage:
      name: "${name} battery voltage"
    battery_current:
      name: "${name} battery current"
    battery_power:
      name: "${name} battery power"
    ac_voltage:
      name: "${name} ac voltage"
    ac_frequency:
      name: "${name} ac frequency"
    temperature:
      name: "${name} temperature"
    output_power:
      name: "${name} output power"

  - platform: template
    id: powermeter0
    name: "Instantaneous Power"
    unit_of_measurement: W
    device_class: "power"
    accuracy_decimals: 2
    update_interval: never

switch:
  - platform: soyosource_virtual_meter
    soyosource_virtual_meter_id: virtualmeter0
    manual_mode:
      name: "${name} manual mode"
      restore_mode: RESTORE_DEFAULT_ON
    emergency_power_off:
      name: "${name} emergency power off"
      restore_mode: RESTORE_DEFAULT_OFF

text_sensor:
  - platform: soyosource_virtual_meter
    soyosource_virtual_meter_id: virtualmeter0
    operation_mode:
      name: "${name} limiter operation mode"

  - platform: soyosource_display
    errors:
      name: "${name} errors"
    operation_mode:
      name: "${name} operation mode"
    operation_status:
      name: "${name} operation status"

interval:
  - interval: 1100ms
    then:
      - http_request.get:
          url: ${shelly_3em_url}
          headers:
            Content-Type: application/json
          verify_ssl: false
          on_response:
            then:
              - lambda: |-
                  std::string response_data = id(http_request0).get_string();
                  if(!response_data.empty()) {
                    json::parse_json(response_data, [](JsonObject root) {
                      id(powermeter0).publish_state(root["total_power"]);
                    });
                  }    

[alfa-53]

Hallo ditec,

habe ähnliche Probleme.

Bin >70, keine Ahnung vom Programierung (yaml) und habe auch einige Soyos, und ne Shelly in Betrieb.
Habe die BSG-Version mal probiert, aber damit ist der Limitter meistens offline. Auch auf Tips die 3,3V mal mit Elko, aber auch nur müll.

Somit gefällt mir die Syssi-Version viel besser.

Habe deine yaml mal versucht zu kompilieren:
Compiling .pioenvs/soyo-01-car/src/main.cpp.o
/config/esphome/soyo-01-car.yaml: In lambda function:
/config/esphome/soyo-01-car.yaml:252:50: error: 'class esphome::http_request::HttpRequestArduino' has no member named 'get_string'
252 | std::string response_data = id(http_request0).get_string();
| ^~~~~~~~~~
Generating LD script .pioenvs/soyo-01-car/ld/local.eagle.app.v6.common.ld
/config/esphome/soyo-01-car.yaml:256:10: error: invalid initialization of reference of type 'const json_parse_t&' {aka 'const std::function<bool(ArduinoJson6185_D1::ObjectRef)>&'} from expression of type 'setup()::<lambda(std::shared_ptresphome::http_request::HttpContainer, std::string&)>::<lambda(ArduinoJson::JsonObject)>'
256 | });
| ^
In file included from src/esphome/core/string_ref.h:10,
from src/esphome/core/entity_base.h:5,
from src/esphome/components/binary_sensor/binary_sensor.h:4,
from src/esphome/core/controller.h:5,
from src/esphome/components/api/api_server.h:9,
from src/esphome/components/api/api_connection.h:6,
from src/esphome.h:3,
from src/main.cpp:3:
src/esphome/components/json/json_util.h:26:62: note: in passing argument 2 of 'bool esphome::json::parse_json(const string&, const json_parse_t&)'
26 | bool parse_json(const std::string &data, const json_parse_t &f);
| ~~~~~~~~~~~~~~~~~~~~^
Compiling .pioenvs/soyo-01-car/lib803/ESPAsyncTCP-esphome/AsyncPrinter.cpp.o
*** [.pioenvs/soyo-01-car/src/main.cpp.o] Error 1
========================= [FAILED] Took 350.17 seconds =========================
?????????????????????

Mit der bin und yaml (D1mini-esp8266-display-example-ok.zip) hab ich meine ESP8266MOD mal gefläscht, weiß aber nicht wie ich das TTL_Modul mit den grünen Klemmen anschließen muß.

Ferner fände ich Eingabefelder: für die Shelly IP, die Inverter_Anzahl, Nahmensvergabe (da mehrere Soyos, .... noch besser.
Könntest du mir dabei helfen? Eine yaml zum lesen und verstehen, sowie eine fertige bin zum flashen währen der Hitt.
LG
Bernhard

[syssi]

Hi Bernhard! Lass uns ganz von vorne anfangen. :-) Kannst du eine ganz neue Diskussion eröffnen, in welcher du kurz beschreibst, welche Soyosource-Variante du besitzt, ob ein Akku oder Solar-Panels angeschlossen sind, ob du eine Heimautomation wie Home Assistant nutzt und was dein grobes Ziel ist? Die Fragen klingen simpel. Du wirst aber sehen, dass all diese Details von Bedeutung sein werden.

[alfa-53]

Dank für Deine schnelle Antwort.
Auch damit bin ich Neuling.
Mehrere Soyos 24V mit Bleiakkus, 48V mit Blei sowie Lipos, alle versorgt mit Tracer und Esmart, und auch 72V direkt mit Modulen versorgt, immer 1200W Strings. Home Assistant ja aber mich würde , wie beschrieben, erst mal die Syssi-Version mit 485 Begrenzung und Shelly 3em rein solo mit "Ferner fände ich Eingabefelder: für die Shelly IP, die Inverter_Anzahl, Nahmensvergabe (da mehrere Soyos, .... noch besser." hilfreich sein.

[syssi]

Bitte einmal hier hin spazieren: https://github.com/syssi/esphome-soyosource-gtn-virtual-meter/discussions/categories/general

Und den grünen Button "New discussion" benutzen um eine vollkommen neue Diskussion zu eröffnen.