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

documentation of mqtt api: planEnergy vs. plan/energy #714

Open
Heimschmiede opened this issue Jan 25, 2025 · 0 comments · May be fixed by #746
Open

documentation of mqtt api: planEnergy vs. plan/energy #714

Heimschmiede opened this issue Jan 25, 2025 · 0 comments · May be fixed by #746

Comments

@Heimschmiede
Copy link

Hi,
great product first of all
just a quick issue that caused some headache on my side for an hour: The mqtt api documentation states the topic evcc/loadpoints/<id>/plan/energy . But the correct one is evcc/loadpoints/<id>/planEnergy . -> plan/energy vs. planEnergy.

I am not sure what the correct rest api endpoint is. The documentation states /api/loadpoints/<id>/plan/energy/<energy>/<time> . But I follow your naming convention used by limit energy (mqtt: limitEnergy ; rest: /limitenergy/) then likely the rest api endpoint is /api/loadpoints/<id>/planenergy/<energy>/<time> : also plan/energy vs planenergy.

@Maschga Maschga linked a pull request Feb 21, 2025 that will close this issue
5 tasks
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

Successfully merging a pull request may close this issue.

1 participant