evcc: Error telemetry: upload failed

Describe the bug

telemetry: upload failed: unexpected status: 403 (Forbidden) every few seconds. reboot does not change anything. it worked for a long time. i changed nothing in the config.

Steps to reproduce

…

Configuration details

# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: info
levels:
  cache: error

# unique installation id
plant: xxx

interval: 20s # control cycle interval

sponsortoken: xxx

# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: true

mqtt:
  broker: 192.168.177.175:1883
  topic: # root topic for publishing, set empty to disable publishing
  clientid: evcc
  user: xxx
  password: xxx

meters:
- name: grid1
  type: custom
  power:
    source: mqtt
    topic: homeassistant/sensor/power_meter_active_power/state
    scale: -1 # Bezug/Einspeisung umtauschen
- name: pv_dach
  type: custom
  power:
    source: mqtt
    topic: homeassistant/sensor/inverter_input_power/state
- name: pv_gartenhaus
  type: custom
  power:
    source: mqtt
    topic: homeassistant/sensor/pv_gartenhaus_p_ac/state
- name: battery
  type: custom
  soc:
    source: mqtt
    topic: homeassistant/sensor/battery_state_of_capacity/state
  power:
    source: mqtt
    topic: homeassistant/sensor/battery_charge_discharge_power/state
    scale: -1 # Laden/Entladen umtauschen
  capacity: 10

chargers:
- type: template
  template: easee 
  user: xxx  
  password: xxx 
  charger: xxx 
  name: wallbox3

vehicles:
- type: template
  template: id
  title: ID4
  user: xxx
  password: xxx
  vin: xxx
  capacity: 77
  phases: 3
  icon: car
  cache: 15m
  mode: pv
  minSoc: 10
  targetSoc: 85
  minCurrent: 6
  maxCurrent: 25
  name: ev2

loadpoints:
- title: Carport
  charger: wallbox3
  mode: pv
  phases: 0
  mincurrent: 6
  maxcurrent: 25
  resetOnDisconnect: false

site:
  title: zu Hause
  meters:
    grid: grid1
    pv:
      - pv_dach
      - pv_gartenhaus
    battery: battery
  prioritySoc: 75
  residualPower: 200
  bufferSoc: 80
  smartCostLimit: 0.10

tariffs:
  grid:
    type: tibber
    token: "xxx"
  feedin:
    type: fixed
    price: 0.0683

Log details

site  ] ERROR 2023/07/05 12:02:09 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:02:11 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:02:17 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:02:37 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:02:45 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:02:57 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:03:17 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:03:57 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:04:17 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:04:37 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:04:57 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:05:17 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:05:37 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:05:57 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:06:17 telemetry: upload failed: unexpected status: 403 (Forbidden)
[site  ] ERROR 2023/07/05 12:06:37 telemetry: upload failed: unexpected status: 403 (Forbidden)

What type of operating system are you running?

HomeAssistant Add-on

Version

0.118.5

About this issue

Original URL
State: closed
Created a year ago
Comments: 65 (34 by maintainers)

Most upvoted comments

Ich hatte den Fehler bis eben auch… generell habe ich keinen telemtry Eintrag in der evcc.yaml

Heute morgen Update (Dickes/ Synology) auf v0.119.4 gemacht.
Seitdem kam der Fehler wie hier beschrieben.
Telemetrie über UI ausgeschaltet.
Neustart von evcc --> Fehler trat nicht mehr auf.
Über https://sponsor.evcc.io/ einen neuen Sponsor-Token generiert.
Neuen Token in evcc.yaml eingetragen.
evcc Neustart durchgeführt --> Telemetrie ist noch ausgeschaltet, Fehler tritt nicht auf 😃
Über UI Telemtrie wieder eingeschaltet --> seitdem kein Fehler mehr.

TomS2 on Sep 6, 2023

Ich würde ehr ein Zusammenhang mit https://github.com/evcc-io/evcc/issues/9696 als der Version vermuten.

StefanSchoof on Sep 3, 2023

As of yesterday I have the hope our token management process might work better than before. Let’s see if this pops up again during the next week and then tentatively close.

andig on Aug 3, 2023

Das klingt nach möglichem root cause. Ich schaue mal ob es dazu Logging gibt. Evtl. Könntest du mal „main“ auf trace stellen und schauen ob da was zu sehen ist.

andig on Jul 9, 2023