Skip to content
Discussion options

You must be logged in to vote

The EVCC API offers the prognosis data in two different places of the API...

  1. as part of the state response
  2. as separate API endpoint

The initial implementation is based on the additional /tariff/{type} endpoint - this implied, that per prognosis type (grid & solar) the code must perform an additional request to the evcc backend. Since I am a bit older, I still believe, that taking care about resource usage matters - In my world every bytes matters... So I have implemented a special handing for the /tariff/{type} enpoints - they will be called just every full hour... since they should not change in this period.

That's said, after my initial implementation I have realized, that tariff data…

Replies: 4 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by mpw96
Comment options

You must be logged in to vote
2 replies
@mpw96
Comment options

@UDicke
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants