-
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
chip-device-ctrl connected error #7390
Comments
The secure session failed so you cannot send the zcl commands for the provissioning. Now I am not sure why it failed. I see you are using mg21, I think it is a Heap issue, we had that happend on the lock app. RAM on MG21 is getting really slim and we have almost no room. You can try to bump the heap by 1k. I will try it and do a PR for that Like this PR #7241 I also what to point out that you are using the wrong endpoints for the commissioning zcl commands. Here is the flow of commands you should be using
As you see except the OnOff command that use enpoint 1, the others are on endpoint 0 |
I meet the same issue on MG12 while pairing lock-app. Is the same reason failed ? and how to fix this issue? |
@LuDuda ,
Logs of Lock-app
the version of nrf
commit of CHIP:
|
I am looking into this thank you. I will link to this issue when there is a fix |
When I use chip-device-ctrl to configure a device, an error is displayed
chip-device-ctrl and device commit:test_event_3_2021_06_03
bb8a6ef
@jmartinez-silabs
Can you help me find out what caused it, how do I need to solve this problem here?
chip-device-ctrl logs:
device logs (efr32mg21A020F1024):
The text was updated successfully, but these errors were encountered: