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
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.
The text was updated successfully, but these errors were encountered:
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 isevcc/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>
: alsoplan/energy
vsplanenergy
.The text was updated successfully, but these errors were encountered: