chip-tool connect fail, how to solve #82
Comments
|
@Firesuiry If it is the default example from the repository, you can find the documentation for commissioning using chip-tool here |
|
I follow this but the connect seems failing, the log is at the bottom of the issue~
…---Original---
From: "Hrishikesh ***@***.***>
Date: Sat, Nov 5, 2022 15:09 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [espressif/esp-matter] How to use chip-tool? (Issue #82)
@Firesuiry If it is the default example from the repository, you can find the documentation for commissioning using chip-tool here
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
@Firesuiry Looks like some issue with the chip-tool BLE adapter:
If the Bluetooth interface is available and working fine, then please start afresh: Reset to factory the device by entering the following command on the device (ESP32) console: Chip-tool command: |
Firesuiry
changed the title
Thank you for your reply~
|
|
@Firesuiry If you do not have BLE adapter then you can try on-network commissioning. But the above case won't help as it is in some inconsistent state of being commissioned ie. BLE based commissioning incomplete. Erase flash and re-flash (as reset to factory is not working on your side) and follow this If you want to try out BLE based commissioning then you will require a BLE adapter |
I tried the log is as follows, dose it success? |
what`s more, my device is esp32c3-devkitm, but it has no effect.. |
|
|
|
I success! thank you~ |
@Firesuiry hi, i hv met the same issue, ./chip-tool onoff toggle 1234 0x1 failed, can u share how to solve this issue? thanks |
|
I reflash the device and retry it. it successes.
I don not know why but recomand you use 0x1234 instead of 1234.
…---Original---
From: "Sid ***@***.***>
Date: Thu, Nov 17, 2022 21:31 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [espressif/esp-matter] chip-tool connect fail, how to solve(Issue #82)
@Firesuiry If you do not have BLE adapter then you can try on-network commissioning. But the above case won't help as it is in some inconsistent state of being commissioned ie. BLE based commissioning incomplete.
Erase flash and re-flash (as reset to factory is not working on your side) and follow this
If you want to try out BLE based commissioning then you will require a BLE adapter
what`s more, my device is esp32c3-devkitm, how can I close the led on the board? I tried
>>> onoff off 0x11 0x0 [1667736008.418236][6075:6080] CHIP:TOO: Sending command to node 0x11 [1667736008.418447][6075:6080] CHIP:CSM: FindOrEstablishSession: PeerId = [1:0000000000000011] [1667736008.418481][6075:6080] CHIP:CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found [1667736008.418499][6075:6080] CHIP:CTL: OperationalSessionSetup[1:0000000000000011]: State change 1 --> 2 [1667736008.619154][6075:6080] CHIP:DIS: Checking node lookup status after 200 ms [1667736023.426908][6075:6080] CHIP:DIS: Checking node lookup status after 15008 ms [1667736023.426948][6075:6080] CHIP:DIS: OperationalSessionSetup[1:0000000000000011]: operational discovery failed: ../third_party/connectedhomeip/src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:174: CHIP Error 0x00000032: Timeout [1667736023.426960][6075:6080] CHIP:-: ../third_party/connectedhomeip/src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:174: CHIP Error 0x00000032: Timeout at ../commands/clusters/ModelCommand.cpp:62 [1667736023.427028][6075:6075] CHIP:TOO: Run command failure: ../third_party/connectedhomeip/src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:174: CHIP Error 0x00000032: Timeout [1667736039.442516][6075:6080] CHIP:DIS: Timeout waiting for mDNS resolution. [1667736039.493752][6075:6079] CHIP:DL: No wifi interface name. Ignoring IP update event. [1667736116.506368][6075:6079] CHIP:DL: No wifi interface name. Ignoring IP update event. [1667736186.518540][6075:6079] CHIP:DL: No wifi interface name. Ignoring IP update event.
but it has no effect..
@Firesuiry hi, i hv met the same issue, ./chip-tool onoff toggle 1234 0x1 failed, can u share how to solve this issue? thanks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
@Firesuiry 0x1234 is not work too . |
|
@Firesuiry erase flash and reflash , repairing. it suceses. thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have built a example light with esp32c3
I want to connect it with chip-tool
But it need setup_passcode and I dont know where to get it.
I try it but it seems connecting fail.
The log from esp32c3 is as follows:
the log from chip-tool is as follows:
The text was updated successfully, but these errors were encountered: