unable to get data from meter via mqtt

[apildk]

Hi all!

Thank you for reading my post.

I am new with evcc, and trying to learn and make my first install work.

Currently i am not getting any meter data.
My meter is from a Growatt inverter, which shares its data from its meter via rs485 that is being collected by an installation of Solar-Assistant which then shares it via MQTT that i am trying to get.

I am getting this "outdated: 10s" error with my data, and i am not sure what it means.

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2023/07/07 08:56:50 evcc 0.118.6
[main  ] INFO 2023/07/07 08:56:50 using config file: /config/evcc.yaml
[main  ] INFO 2023/07/07 08:56:50 starting ui and api at :7070
[mqtt  ] INFO 2023/07/07 08:56:50 connecting evcc-147540838 at tcp://192.168.100.4:1883
[lp-1  ] WARN 2023/07/07 08:56:52 locking phase config to 3p for switchable charger
[site  ] DEBUG 2023/07/07 08:56:52 dynamic grid tariff
[site  ] WARN 2023/07/07 08:56:52 battery configured but residualPower is missing (add residualPower: 100 to site)
[site  ] INFO 2023/07/07 08:56:52 site config:
[site  ] INFO 2023/07/07 08:56:52   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2023/07/07 08:56:52     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/07/07 08:56:52     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/07/07 08:56:52     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✗
[site  ] INFO 2023/07/07 08:56:52   vehicles:
[site  ] INFO 2023/07/07 08:56:52     vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1  ] INFO 2023/07/07 08:56:52 loadpoint 1:
[lp-1  ] INFO 2023/07/07 08:56:52   mode:        pv
[lp-1  ] INFO 2023/07/07 08:56:52   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2023/07/07 08:56:52   meters:      charge ✓
[lp-1  ] INFO 2023/07/07 08:56:52     charge:    power ✓ energy ✓ currents ✓
[site  ] DEBUG 2023/07/07 08:56:52 dynamic grid tariff
[lp-1  ] DEBUG 2023/07/07 08:56:52 phase timer inactive
[lp-1  ] DEBUG 2023/07/07 08:56:52 pv timer inactive
[lp-1  ] DEBUG 2023/07/07 08:56:52 guard timer inactive
[lp-1  ] DEBUG 2023/07/07 08:56:52 max charge current: 6A
[site  ] DEBUG 2023/07/07 08:56:52 ----
[lp-1  ] DEBUG 2023/07/07 08:56:52 charge power: 2062W
[site  ] DEBUG 2023/07/07 08:56:52 dynamic grid tariff
[site  ] ERROR 2023/07/07 08:57:23 pv 1 power: solar_assistant/inverter_1/pv_power/ outdated: 10s
[site  ] DEBUG 2023/07/07 08:57:23 pv power: 0W

my config for my meters looks like this:

meters:
  - name: grid
    type: custom    
    power:
        source: mqtt
        topic: solar_assistant/inverter_1/grid_power/
        timeout: 30s # don't accept values older than timeout
        scale: 0.001
    
  - name: pv
    type: custom    
    power:
        source: mqtt
        topic: solar_assistant/inverter_1/pv_power/
        timeout: 30s # don't accept values older than timeout
        scale: 0.001 
    
  - name: battery
    type: custom    
    power:
        source: mqtt
        topic: solar_assistant/total/battery_power/
        timeout: 30s # don't accept values older than timeout
        scale: 0.001 
    soc:
        source: mqtt
        topic: solar_assistant/total/battery_state_of_charge/
        timeout: 30s # don't accept values older than timeout
        

And here is some data from the MQTT network, that tells me that i use the correct topics for mqtt.

Thank you very much for reading my post, and i hope anyone is able to help me resolve this.

Have a great day!

Best regards

[premultiply]

I am getting this "outdated: 10s" error with my data, and i am not sure what it means.

It means that the update interval of your data on mqtt is too low for operation with the configured control interval of evcc.

If you selected 10s for interval it means your mqtt values need to be updates at cycles of <5s.

In case of mqtt you are self-responsible for pushing the data in time.

So you you should speed up your data provider.

[apildk]

Thank you for your reply.

I see that i have the default config of

interval: 10s # control cycle interval

But when i check the mqtt trafik in a tool called mqtt explorer, then i see new data is provided on these topics every 1 second.

So the data should be coming fast enough ?

Maybe i am misunderstanding something.

Thank you again! :)

[premultiply]

That should be ok.
Maybe timestamps (time/timezone correct?) are away or single values are not updated on regular base.

And btw: [site ] WARN 2023/07/07 08:56:52 battery configured but residualPower is missing (add residualPower: 100 to site)

[apildk]

Hmm okay, in correct timestamps was also my first idea, but the solar assistant, which provides the mqtt data is syncing with a internet time server, and the timestamps when looking at the data from mqtt explorer.

I am not sure how to check the time of the evcc though, i dont see anything in the config file to adjust time.
As it is running as an addon of home assistant, im guessing that it uses the same time as the home assistant?

[site ] WARN 2023/07/07 08:56:52 battery configured but residualPower is missing (add residualPower: 100 to site)
I am not sure what this means, but currently my battery is turn off, which might be it ?

Thanks again!

[apildk]

The timestamps in the log of evcc in homeassistant are correct, down to the secound, same as solar assistant, so time should be the same. ?

Also here is my full config:

network:
  # schema is the HTTP schema
  # setting to `https` does not enable https, it only changes the way URLs are generated
  schema: http
  # host is the hostname or IP address
  # if the host name contains a `.local` suffix, the name will be announced on MDNS
  # docker: MDNS announcements don't work. host must be set to the docker host's name.
  host: 192.168.100.3
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 10s # control cycle interval

# database configuration for persisting charge sessions and settings
# database:
#   type: sqlite
#   dsn: <path-to-db-file>

# sponsor token enables optional features (request at https://sponsor.evcc.io)
sponsortoken: eyJxxzyxKU

# telemetry enables aggregated statistics
#
# Telemetry allows collecting usage data (grid and green energy, charge power).
# Data is aggregated, no individual charging sessions are tracked. The collected,
# anonymous data can be retrieved using https://api.evcc.io.
#
# See https://github.com/evcc-io/evcc/pull/4343 or details.
#
# For time being, this is only available to sponsors, hence data is associated with
# the sponsor token's identity.
#
# telemetry: true

# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error

# modbus proxy for allowing external programs to reuse the evcc modbus connection
# each entry will start a proxy instance at the given port speaking Modbus TCP and
# relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)
modbusproxy:
  #  - port: 5200
  #    uri: solar-edge:502
  #    # rtu: true
  #    # readonly: true

# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for documentation see https://docs.evcc.io/docs/devices/meters
meters:
  - name: grid
    type: custom    
    power:
        source: mqtt
        topic: solar_assistant/inverter_1/grid_power/
        timeout: 30s # don't accept values older than timeout
        scale: 0.001
    
  - name: pv
    type: custom    
    power:
        source: mqtt
        topic: solar_assistant/inverter_1/pv_power/
        timeout: 30s # don't accept values older than timeout
        scale: 0.001 
    
  - name: battery
    type: custom    
    power:
        source: mqtt
        topic: solar_assistant/total/battery_power/
        timeout: 30s # don't accept values older than timeout
        scale: 0.001 
    soc:
        source: mqtt
        topic: solar_assistant/total/battery_state_of_charge/
        timeout: 30s # don't accept values older than timeout
        

# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
  - name: easee
    type: template
    template: easee
    user: xzy@xzy.xzy
    password: xzy
    charger: EHxzy

# vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:
  - name: BanditBussen
    type: template
    template: tesla
    title: BanditBussen
    accessToken: eyxzyQ 
    refreshToken: exzyyA 
    vin: xzy
    capacity: 60 

# site describes the EVU connection, PV and home battery
site:
  title: xzy # display name for UI
  meters:
    grid: grid # grid meter
    pv:
      - pv # list of pv inverters/ meters
    battery:
      - battery # list of battery meters
  residualPower: 0 # additional household usage margin
  prioritySoc: 0 # give home battery priority up to this soc (empty to disable)
  bufferSoc: 0 # continue charging on battery above soc (0 to disable)
  bufferStartSoc: 0 # start charging on battery above soc (0 to disable)
  maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value
  smartCostLimit: 0 # set cost limit for automatic charging in PV mode

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Garage # display name for UI
    charger: easee # charger
    mode: pv # set default charge mode, use "off" to disable by default if charger is publicly available
    # vehicle: car1 # set default vehicle (disables vehicle detection)
    resetOnDisconnect: true # set defaults when vehicle disconnects
    phases: 3 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    minCurrent: 6 # minimum charge current (default 6A)
    maxCurrent: 16 # maximum charge current (default 16A)

    # remaining settings are experts-only and best left at default values
    priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    soc:
      # polling defines usage of the vehicle APIs
      # Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
      # or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
      poll:
        # poll mode defines under which condition the vehicle API is called:
        #   charging: update vehicle ONLY when charging (this is the recommended default)
        #   connected: update vehicle when connected (not only charging), interval defines how often
        #   always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
        mode: charging
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 60m
      estimate: true # set false to disable interpolating between api updates (not recommended)
    enable: # pv mode enable behavior
      delay: 1m # threshold must be exceeded for this long
      threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
    disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)
    guardDuration: 5m # switch charger contactor not more often than this (default 5m)

# tariffs are the fixed or variable tariffs
tariffs:
  currency: DKK # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.294 # EUR/kWh
    zones:
      - days: Mo-Fr
        hours: 2-5
        price: 0.2 # EUR/kWh
      - days: Sa,So
        price: 0.15 # EUR/kWh

    # or variable tariffs
    # type: tibber
    # token: "476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4" # access token
    # homeid: "cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c" # optional if multiple homes associated to account

    # type: awattar
    # region: de # optional, choose at for Austria
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: elering # Nordpool
    # region: ee # or lt, lv, fi
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: energinet # Energinet using the price in DKK
    # region: dk1
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)
  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.08 # EUR/kWh
  co2:
    # co2 tariff provides co2 intensity forecast and is for co2-optimized target charging if no variable grid tariff is specified
    # type: grünstromindex # GrünStromIndex (Germany only)
    # zip: <zip>

    # type: electricitymaps # https://app.electricitymaps.com/map
    # uri: <uri>
    # token: <token>
    # zone: DK1

# mqtt message broker
mqtt:
   broker: 192.168.100.4:1883
   topic: solar_assistant
   user: mqtt_user
   password: xzy

# influx database
influx:
  # url: http://localhost:8086
  # database: evcc
  # user:
  # password:

# eebus credentials
eebus:
  # uri: # :4712
  # interfaces: # limit eebus to specific network interfaces
  # - en0
  # certificate: # local signed certificate, required, can be generated via `evcc eebus-cert`
  #   public: # public key
  #   private: # private key

# push messages
messaging:
  events:
    start: # charge start event
      title: Charge started
      msg: Started charging in "${mode}" mode
    stop: # charge stop event
      title: Charge finished
      msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
    connect: # vehicle connect event
      title: Car connected
      msg: "Car connected at ${pvPower:%.1fk}kW PV"
    disconnect: # vehicle connected event
      title: Car disconnected
      msg: Car disconnected after ${connectedDuration}
    soc: # vehicle soc update event
      title: Soc updated
      msg: Battery charged to ${vehicleSoc:%.0f}%
    guest: # vehicle could not be identified
      title: Unknown vehicle
      msg: Unknown vehicle, guest connected?
  services:
  # - type: pushover
  #   app: # app id
  #   recipients:
  #   - # list of recipient ids
  # - type: telegram
  #   token: # bot id
  #   chats:
  #   - # list of chat ids
  # - type: email
  #   uri: smtp://<user>:<password>@<host>:<port>/?fromAddress=<from>&toAddresses=<to>
  # - type: ntfy
  #   uri: https://<host>/<topics>
  #   priority: <priority>
  #   tags: <tags>

[apildk]

Anyone able to help here ?

Thanks in advance.

Best regards
Apil

[iamdjrain]

Hello, I have exactly the same problem with my configuration. Were you able to find a solution?

[Kentrp]

Hi! Change topic:
topic: solar_assistant/inverter_1/grid_power/state