Skip to content

Describe how the bridge handles RPDO subscriptions - #174

Merged
michaelarnauts merged 1 commit into
masterfrom
docs-rpdo
Oct 20, 2026
Merged

michaelarnauts merged 1 commit into
masterfrom
docs-rpdo

Conversation

@michaelarnauts

Copy link
Copy Markdown
Owner

Updates the CnRpdoRequest section of docs/PROTOCOL.md:

  • A subscription is identified by its pdid and zone. The bridge has no list of pdids: it accepts any pdid below 16384 (0x4000, higher gets NOT_EXIST) and never checks the type against the pdid.
  • Clients subscribing to the same pdid and zone share one subscription, removed when the last one unsubscribes. Room for 192 subscriptions (NO_RESOURCES when full); unsubscribing from something that isn't subscribed gets NOT_EXIST.
  • The timeout isn't used by the bridge.
  • The interval is in seconds and kept per client: at most one notification per interval, rounded down to a power of 2 (10 → every 8 seconds). The LAN C (R1.5.1) does this; the gateway in a ComfoAir Flex (R1.2.1) ignores it.
  • Unsubscribing (no type) is described as fact instead of "the protobuf definition says".

Documentation only.

🤖 Generated with Claude Code

A subscription is identified by pdid and zone, the bridge accepts any pdid
below 0x4000 and doesn't check the type, clients share subscriptions, and
there is room for 192. The timeout is not used; the interval is in seconds,
per client, rounded down to a power of 2, and only used by the LAN C.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@michaelarnauts
michaelarnauts merged commit 80a4745 into master Oct 20, 2026
4 checks passed
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.

1 participant