Skip to content

ezsp v4: fix gpepIncomingMessageHandler schema for GP frames#1

Merged
nmingam merged 2 commits into
nmingam:fix-gpep-incoming-message-handlerfrom
mineshaftgap:pr-713-v4fix
Jun 16, 2026
Merged

ezsp v4: fix gpepIncomingMessageHandler schema for GP frames#1
nmingam merged 2 commits into
nmingam:fix-gpep-incoming-message-handlerfrom
mineshaftgap:pr-713-v4fix

Conversation

@mineshaftgap

Copy link
Copy Markdown

Adds the v4 base-schema fix for gpepIncomingMessageHandler that this branch is missing (you invited it in zigpy#713). v4 is inherited by v4..v12.

  • Swaps the five scattered address fields for the EmberGpAddress struct and bidirectionalInfo: Bool -> uint8_t, matching your v13+ fix. v4 keeps status: EmberStatus (v13+ moved to uint8_t).
  • Second commit adds a v4 test that parses the existing BJ6716U_GPEP_PAYLOAD capture against the v4 schema end-to-end, so every EZSP version is exercised against the same real bytes - it needs nothing this branch does not already have.

Targeted at your fix-gpep-incoming-message-handler branch so it folds straight into zigpy#713. v4 + v13 gpep tests pass; black clean.

mineshaftgap and others added 2 commits June 15, 2026 15:13
Replace 5 flat address fields with EmberGpAddress struct.
Fix bidirectionalInfo type Bool->uint8_t (caused parse failures).
Cover the v4 base schema (inherited by v4..v12) with the Busch-Jaeger
6716 U capture reused from the v13 tests: a direct deserialize_dict
parse and an end-to-end frame_rx dispatch. Guards the EmberGpAddress
struct + bidirectionalInfo uint8_t fix, and that the v4-specific
EmberStatus typing accepts the captured 0x7C (EmberStatus.NO_SECURITY).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants