-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group Communication - Unable to verify if the multicast command is working correctly #19608
Comments
We are also unable to control the devices using group messaging. We are testing on EFR32 and ESP32, it seems that the multicasts are not received. According to the logs, the ESP32 device cannot join the multicast group whereas the EFR32 device joins the group but does not receive any messages. ESP32 output:
EFR32 output:
Controller output:
|
@dtodor For ESP32, the issue is known and tracked in #18984 @dtodor For EFR32, groups are expected to work. Please file a separate issue with exact steps to reproduce and logs. For the original issue here, @sethunk thank you for the detailed steps and the complete (and even annotated!) logs. This command in the sequence of commands executed:
adds endpoint 0 of all-clusters-app to the group. That endpoint does not have an On/Off cluster on it. And later when the
(Ignore the wrong command id in that third log line; I'll put up a PR to fix that in a sec.) @sethunk Does fixing that |
Well the problem is right in the logs : Group registered on the EFR32 has an ipv6 address of Since the logs from the ESP32 doesn't have this problem, it might be specific to the implementation |
I don't get it, it is the same IP address actually, right? |
My bad, I did not see the |
@dtodor the complete log for the EFR32 in a different issue would be appreciated since there is a huge amount of reasons why a multicast packet might be discarded. On the EFR32 platform you should be able to see a log that is printed on reception of ANY IPV6 messages with the destinations Addr it starts with |
@jepenven-silabs Yes, I don't see the log. I'm starting to think that the OpenThread Border Router is not configured properly. Is there any documentation on how to compile OTBR to support multicasts? |
@jepenven-silabs I'll move the discussion to this thread: #19624. |
Cert Blocker Review: Please note this comment:
|
I was able to confirm there is no issue device side for efr32 devices.
|
I have been able to get this working. Thank you for the support. |
Problem - We are sending multicast command to DUT for onoff cluster to change the on-off attribute value to "on". We are trying to read the same attribute value in unicast mode to check if the multicast command actually worked but we are not able to see the value changed in the attribute.
Before sending multicast command we are setting the appropriate ACL entry and Group settings command to initialise the test condition.
Sequence of the Commands sent:
1.Initial Commands
2.Sending Multicast commands
12../chip-tool onoff on 0xffffffffffff0001 1
3.Reading on-off attribute
13../chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": [{"cluster": null, "endpoint": 0, "deviceType": null}]}, {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": null, "targets": [{"cluster": null, "endpoint": 1, "deviceType": null}]}]' 1 0
14../chip-tool onoff read on-off 1 1
Note: Response from DUT
[1655278244.271372][3893:3893] CHIP:DMG: ReadRequestMessage =
[1655278244.271400][3893:3893] CHIP:DMG: {
[1655278244.271422][3893:3893] CHIP:DMG: AttributePathIBs =
[1655278244.271448][3893:3893] CHIP:DMG: [
[1655278244.271472][3893:3893] CHIP:DMG: AttributePathIB =
[1655278244.271500][3893:3893] CHIP:DMG: {
[1655278244.271527][3893:3893] CHIP:DMG: Endpoint = 0x1,
[1655278244.271561][3893:3893] CHIP:DMG: Cluster = 0x6,
[1655278244.271589][3893:3893] CHIP:DMG: Attribute = 0x0000_0000,
[1655278244.271619][3893:3893] CHIP:DMG: }
[1655278244.271646][3893:3893] CHIP:DMG:
[1655278244.271671][3893:3893] CHIP:DMG: ],
[1655278244.271699][3893:3893] CHIP:DMG:
[1655278244.271726][3893:3893] CHIP:DMG: isFabricFiltered = true,
[1655278244.271750][3893:3893] CHIP:DMG: InteractionModelRevision = 1
[1655278244.271773][3893:3893] CHIP:DMG: },
[1655278244.271853][3893:3893] CHIP:DMG: IM RH moving to [GeneratingReports]
[1655278244.271945][3893:3893] CHIP:DMG: Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
[1655278244.271975][3893:3893] CHIP:DMG: RE:Run Cluster 6, Attribute 0 is dirty
[1655278244.271996][3893:3893] CHIP:DMG: Reading attribute: Cluster=0x0000_0006 Endpoint=1 AttributeId=0x0000_0000 (expanded=0)
[1655278244.272024][3893:3893] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0006 e=1 p=v
[1655278244.272059][3893:3893] CHIP:DMG: AccessControl: allowed
4.Test Environment
App used - allclusters app
Platform - Chip-tool - RPI-4, 8GB RAM
DUT - RPI - RPI-4, 8GB RAM
Network - Ble-wifi
Commit - 9493d7b
5Logs
DUT_Logs_15.06.2022.txt
TH_Logs_15.06.2022.txt
The text was updated successfully, but these errors were encountered: