Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tibber Grid not updated - 429 Too Many Requests #18961

Closed
2 tasks done
chrstmnn opened this issue Feb 19, 2025 · 1 comment
Closed
2 tasks done

Tibber Grid not updated - 429 Too Many Requests #18961

chrstmnn opened this issue Feb 19, 2025 · 1 comment

Comments

@chrstmnn
Copy link

Describe the bug

Still with version 0.200.0, Tibber API gets blocked when using EVCC.
As soon as I shut down EVCC and refresh my external IP, the API is working again as expected (e.g. in Home Assistant).
After turning of EVCC on again, it takes some hours or days until the API is blocked again.

Steps to reproduce

  1. Set up Tibber in EVCC
  2. Let it run

Configuration details

meters:
- type: template
  template: tibber-pulse 
  usage: grid  
  token: <token>
  homeid: <homeid>
  name: grid1

Log details

[main ] INFO 2025/02/19 09:32:04 evcc 0.200.0
[main ] INFO 2025/02/19 09:32:04 using config file: /etc/evcc.yaml
[db ] INFO 2025/02/19 09:32:04 using sqlite database: /var/lib/evcc/evcc.db
[main ] INFO 2025/02/19 09:32:04 listening at :7070
[main ] FATAL 2025/02/19 09:32:04 meter [grid1] cannot create meter 'grid1': cannot create meter type 'template': cannot create meter type 'tibber-pulse': Message: 429 Too Many Requests, Locations: [], Extensions: map[code:request_error], Path: []
[main ] FATAL 2025/02/19 09:32:04 will attempt restart in: 15m0s
[main ] INFO 2025/02/19 09:32:04 new version available: 0.200.1

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.200.0

@andig
Copy link
Member

andig commented Feb 19, 2025

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

Anscheinend nicht :( Es braucht ein trace log für Tibber. Bitte auf aktueller Version.

@andig andig closed this as completed Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants