Expose ESPHome serial proxy mode config - #119
Draft
puddly wants to merge 10 commits into
Draft
Conversation
19 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
ESPHome serial proxies support
tap_modeto allow for (light) handling of the serial stream on-device. Zigbee and Z-Wave proxies will use this to auto-ACK packets autonomously and avoid unnecessary chatter/retries/disconnects due to network hiccups affecting ACK timing.ESPHome serial proxies will still default to
rawmode and it will always be possible (and expected!) for applications to pick the appropriate mode for their use case. ZHA, for example, will only enableprotocolmode for EZSP traffic and will userawfor firmware flashing and all other radio types.OpenHomeFoundation/roadmap#191