You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
[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
The text was updated successfully, but these errors were encountered:
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
Configuration details
Log details
What type of operating system or environment does evcc run on?
Linux
External automation
Nightly build
Version
0.200.0
The text was updated successfully, but these errors were encountered: