Use correct broadcast EUI64 #82
Closed
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 was noticing that ZHA's zha.issue_zigbee_group_command wasn't working for the groups I had previously defined. Turns out there's some conflicting information in Digi's documentation on what EUI64 to set for multicast requests.
As per https://www.digi.com/resources/documentation/Digidocs/90002002/Default.htm#Reference/r_frame_0x11.htm%3FTocPath%3DFrame%2520descriptions%7C_____4 only 0x000000000000FFFF (Broadcast), 0x0000000000000000 (Coordinator) and an explicit EUI64 are allowed.
https://www.digi.com/resources/documentation/Digidocs/90002002/Default.htm#Concepts/c_zb_multicast_trans.htm%3FTocPath%3DTransmission%252C%2520addressing%252C%2520and%2520routing%7C_____4 indicates, and this is what zigpy-xbee does, to use 0xFFFFFFFFFFFFFFFF
Long story short. After changing the value to 0x00...FFFF it started working for me on an XSTICK2.
After the change: