Fixed HomeAssistant integration #45
Merged
Conversation
This file contains hidden or 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
Fixed state of charging_current_limit control.
Increased PayloadBuffer from 512 to 1024 Corrected uniq_id to unique_id Made unique_id really unique Formatted DiscoveryTopic JSON for readability
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I had issues with my wallbox in HomeAssistant and found that messages where not delivered.
This was because my HeidelBridge name was so long it made certain messages exceed 512 characters.
I was able to fix this and also made some other improvements to the auto discovery for HomeAssistant.
I tested it with my wallbox and now all works as expected.