Remove group packet filtering by replacing sli_zigbee_am_multicast_member
#112
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.
Instead of using a packet filter callback, replace the EmberZNet-internal
sli_zigbee_am_multicast_member
function with a no-op. This prevents the stack from filtering out the packets we are interested in and is a much lighter-weight approach compared to using a packet filter callback to inject ephemeral entries into the group table. The downside here is API stability but this will be visible when upgrading the SDK.For background, Zigbee has three ways for messages to be sent: unicast (device-to-device), broadcast (device-to-everything), and multicast (device-to-group). Group messages are used by some IKEA devices and remotes to be able to control light bulbs directly from sensors, without using a coordinator in the mesh. The SDK unfortunately requires you to explicitly register a group ID to un-ignore the group, which is not really possible when there are 2^16 of them. This PR bypasses the SDK function responsible for filtering out these messages.