Add new sensor "Wiper Health" #265
Merged
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
|
thx - lgtm - Could you resolve the conflicts please? thx - the wiper support looks quite new. even the EQS does not report this. (Do you get cars with beta features as MB employees? :-)) |
|
😂 Nope, it’s just a regular vehicle with regular software. Could you please merge #267 first before I merge everything together? I’ll take care of it this evening. |
|
Done |
philippwaller
force-pushed
the
feat/wiperHealth
branch
from
5da117d to
9225fbf
Compare
|
ready to ship |
|
Thx! |
# for free
to join this conversation on GitHub.
Already have an account?
# 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 pull request adds a new sensor called "Wiper Health" that indicates the condition of the windshield wipers as a percentage. Additionally, the attribute wiperLifetimeExceeded is included. However, in my experience, it provides implausible results. As a result, I've marked this field as experimental in the documentation.