Add support for sending events via MQTT #17278
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
See evcc-io/docs#670 for the corresponding end-user documentation (in German) |
rhuss
force-pushed
the
pr/mqtt-events
branch
from
a7a127d to
016af72
Compare
rhuss
force-pushed
the
pr/mqtt-events
branch
from
016af72 to
2b1f26c
Compare
|
<3 |
|
Thank you for the PR! For sake of consistency replaced by #17211. |
|
You are welcome 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new type,
mqttforservicesdefined inmessagingas endpoints for receiving charging lifecycle events.It reuses a globally configured
mqttserver to send out the events.These events help calculate your charging plan. True, one could also monitor boolean mqtt messages in topic
evcc.loadpoints[].chargingbut one only gets to know about any state change after a delay (30s at worst), while monitoring a status change event is immediate, avoiding any delays for calculating the targettime for the charging plan.