PV forecast and Co2 information are lost sometimes

[maduuto]

Describe the bug

Sometimes, the PV Forecast will not go further, like it stops at a specific time and does not load the next days anymore. Sometimes it reloads after some hours. Also sometimes the CO2 information is gone. Like now, pv forecast has been restored my itself after mssing but co2 is still gone with no change. After Restart of evcc everything is available again. According to logfile error 429 too many requests but i dont use another service than evcc to contact the solcast api.

Steps to reproduce

1. waiting a amount of time until it does not load forecast informations anymore
   2.restart
2. forecast data now available
   ...

Configuration details

co2: # carbon intensity forecast data
  type: template
  template: grünstromindex
  zip: xxxxx
currency: EUR
grid:
  type: fixed
  price: 0.2078
feedin: # price for feeding solar energy to the grid
  type: fixed
  price: 0.082 # EUR/kWh
solar:
  type: template
  template: solcast
  site: xxxx
  token:  xxxxx
planner:
    type: fixed
    price: 0.2078
db:1 {Type:template Title: Icon: Product:} map[host:192.168.150.180 template:go-e-v3]
db:8 {Type:template Title: Icon: Product:} map[cache:1e+09 device:00161BE99EA94E heating:true host:192.168.150.220 icon:airpurifier integrateddevice:true meterchannel:6 password:***** port:2010 standbypower:15 switchchannel:26 template:homematic user:*****]
db:11 {Type:sgready Title: Icon: Product:} map[yaml:icon: waterheater
setmode: # set operation mode (1: reduced, 2: normal, 3 boost)
  source: switch
  switch:
  - case: 2
    set:
          source: const
          value: false
          set:
            source: charger
            config:
              type: template
              template: homematic
              host: 192.168.150.220
              port: 2010
              device: '00161BE99EA94E'
              switchchannel: 26
  - case: 3
    set:
          source: const
          value: true
          set:
            source: charger
            config:
              type: template
              template: homematic
              host: 192.168.150.220
              port: 2010
              device: '00161BE99EA94E'
              switchchannel: 26


getmode:
   source: calc
   add:
     - source: const
       value: 2
     - source: charger
       config:
        type: template
        template: homematic
        host: 192.168.150.220
        port: 2010
        device: '00161BE99EA94E'
        switchchannel: 26


#power: # charge power in W
#  source: const
#  value: 11000

temp:
   source: modbus
   id: 4
   uri: 192.168.150.70:502
   register:
    address: 9
    type: input
    decode: int16
   scale: 0.1
   timeout: 10s
#limittemp: # temperature limit (°C) configured in device
#  source: const
#  value: 84

## optional attributes (writeable)

#setmaxpower: # update the maximum charging power
#  source: js
#  script: console.log(maxpower);
]
db:14 {Type:sgready Title: Icon: Product:} map[yaml:icon: heater
setmode: # set operation mode (1: reduced, 2: normal, 3 boost)
  source: switch
  switch:
  - case: 2
    set:
          source: const
          value: false
          set:
            source: charger
            config:
              type: template
              template: homematic
              host: 192.168.150.220
              port: 2010
              device: '00161BE99EA94E'
              switchchannel: 18
  - case: 3
    set:
          source: const
          value: true
          set:
            source: charger
            config:
              type: template
              template: homematic
              host: 192.168.150.220
              port: 2010
              device: '00161BE99EA94E'
              switchchannel: 18


getmode:
   source: calc
   add:
     - source: const
       value: 2
     - source: charger
       config:
        type: template
        template: homematic
        host: 192.168.150.220
        port: 2010
        device: '00161BE99EA94E'
        switchchannel: 18








#power: # charge power in W
#  source: const
#  value: 11000

temp:
   source: modbus
   id: 4
   uri: 192.168.150.70:502
   register:
    address: 2800
    type: input
    decode: int16
   scale: 0.1
   timeout: 10s
#limittemp: # temperature limit (°C) configured in device
#  source: const
#  value: 84

## optional attributes (writeable)

#setmaxpower: # update the maximum charging power
#  source: js
#  script: console.log(maxpower);
]

meter
---
db:4 {Type:template Title: Icon: Product:} map[capacity:6.7 host:192.168.150.52 id:1 maxacpower:4350 modbus:tcpip port:502 template:solaredge-hybrid usage:grid watchdog:60s]
db:5 {Type:template Title:solaredge-hybrid Icon: Product:} map[capacity:6.7 host:192.168.150.52 id:1 maxacpower:4350 modbus:tcpip port:502 template:solaredge-hybrid usage:pv watchdog:60s]
db:6 {Type:template Title:Solaredge Icon: Product:} map[capacity:6.7 host:192.168.150.52 id:1 maxacpower:4350 modbus:tcpip port:502 template:solaredge-hybrid usage:battery watchdog:60s]
db:7 {Type:template Title:huawei Icon: Product:} map[host:192.168.150.181 modbus:tcpip template:huawei-dongle timeout:1.5e+10 usage:pv]
db:13 {Type:custom Title: Icon: Product:} map[yaml:
power: # current power
  source: calc
  mul:
  - source: modbus
    id: 4
    uri: 192.168.150.70:502
    register:
      address: 2305
      type: input
      decode: int16
    scale: 10
    timeout: 2s
  - source: http
    uri: http://localhost:7070/api/state
    jq: if .result.ext.power = 20  then 1 else 0 end

]
db:16 {Type:custom Title: Icon: Product:} map[yaml:
power: # current power
  source: calc
  mul:
  - source: modbus
    id: 4
    uri: 192.168.150.70:502
    register:
      address: 2305
      type: input
      decode: int16
    scale: 10
    timeout: 2s
  - source: http
    uri: http://localhost:7070/api/state
    jq: if .result.ext[0].power ==20  then 1 else 0 end

]
db:17 {Type:custom Title: Icon: Product:} map[yaml:
power: # current power
  source: calc
  mul:
  - source: http
    uri: http://localhost:7070/api/state
    jq: if .result.ext.power =20  then 0 else 1 end
  - source: modbus
    id: 4
    uri: 192.168.150.70:502
    register:
      address: 2305
      type: input
      decode: int16
    scale: 10
    timeout: 2s


]

vehicle
---
db:3 {Type:template Title: Icon: Product:} map[cache:15m capacity:77 icon:car maxCurrent:16 minCurrent:6 mode:pv password:***** phases: priority:5 template:vw timeout:10s title:ID7 user:*****]

loadpoint
---
db:2 {Type: Title: Icon: Product:} map[charger:db:1 circuit:main defaultMode:off limitSoc:0 meter: mode:pv phasesConfigured:0 planEnergy:0 planPrecondition:0 planTime:0001-01-01T00:00:00Z priority:5 smartCostLimit:<nil> soc:map[estimate:true poll:map[interval:6e+11 mode:connected]] thresholds:map[disable:map[delay:1.8e+11 threshold:0] enable:map[delay:6e+10 threshold:0]] title:Carport vehicle:]
db:12 {Type: Title: Icon: Product:} map[charger:db:11 circuit:main defaultMode:pv maxCurrent:13 meter:db:13 minCurrent:2 mode:pv phasesConfigured:3 priority:1 soc:map[estimate:true poll:map[interval:3.6e+12 mode:charging]] thresholds:map[disable:map[delay:3e+11 threshold:0] enable:map[delay:3e+11 threshold:-3000]] title:Wärmepumpe Brauchwasser vehicle:]
db:15 {Type: Title: Icon: Product:} map[charger:db:14 circuit:main defaultMode:pv maxCurrent:13 meter:db:17 minCurrent:2 mode:pv phasesConfigured:1 soc:map[estimate:true poll:map[interval:3.6e+12 mode:charging]] thresholds:map[disable:map[delay:3e+11 threshold:0] enable:map[delay:3e+11 threshold:-1500]] title:Wärmepumpe Heizung Kühlung vehicle:]

Log details

Okt 19 13:01:18 wallbox evcc[227014]: [gsi   ] ERROR 2025/10/19 13:01:18 Get "https://api.corrently.io/v2.0/gsi/prediction?zip=***": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

Okt 19 14:00:49 wallbox evcc[227014]: [solcast] ERROR 2025/10/19 14:00:49 unexpected status: 429 (Too Many Requests)

What type of operating system or environment does evcc run on?

Linux

External automation

• I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

0.209.2

[igotsoul]

same here, sometimes working, sometimes not

[andig]

Both solcast and gsi are cached in evcc beyond restarts. When data expires it's reloaded. When that fails due to api issues it's up to the providers to fix their api.

That said: this issue does not describe any problem with evcc.

[maduuto]

But how can i check that it is a api issue for solcast? Maybe evcc is asking the API too much? Dont want to bother you, if you tell me how can i check the log when evcc tries to contact solcast? Maximum allowed is 10 times per day. I only can see logfiles with error 429 but not how much evcc has asked the api

[maduuto]

Today again lost
I think evcc is requesting the API too much but need to check the logs