src/controller/CHIPDeviceController.cpp CHIP_ERROR DeviceCommissioner::UnpairDevice(NodeId remoteDeviceId) { // TODO: Send unpairing message to the remote device. return CHIP_NO_ERROR; } It is not supported yet in the chip-tool
@torchiotbootcamp7844Рік тому
It looks like the darwin tool implement the unpair. But I have not Apple developer account to test it. examples/darwin-framework-tool/commands/pairing/PairingCommandBridge.mm void PairingCommandBridge::Unpair() { dispatch_queue_t callbackQueue = dispatch_queue_create("com.chip-tool.command", DISPATCH_QUEUE_SERIAL); MTRDeviceController * commissioner = CurrentCommissioner(); auto * device = [MTRBaseDevice deviceWithNodeID:@(mNodeId) controller:commissioner]; ChipLogProgress(chipTool, "Attempting to unpair device %llu", mNodeId); MTRBaseClusterOperationalCredentials * opCredsCluster = [[MTRBaseClusterOperationalCredentials alloc] initWithDevice:device endpoint:@(0) queue:callbackQueue]; [opCredsCluster readAttributeCurrentFabricIndexWithCompletion:^(NSNumber * _Nullable value, NSError * _Nullable readError) { if (readError) { CHIP_ERROR readErr = MTRErrorToCHIPErrorCode(readError); LogNSError("Failed to get current fabric: ", readError); SetCommandExitStatus(readErr); return; } MTROperationalCredentialsClusterRemoveFabricParams * params = [[MTROperationalCredentialsClusterRemoveFabricParams alloc] init]; params.fabricIndex = value; [opCredsCluster removeFabricWithParams:params completion:^(MTROperationalCredentialsClusterNOCResponseParams * _Nullable data, NSError * _Nullable removeError) { CHIP_ERROR removeErr = CHIP_NO_ERROR; if (removeError) { removeErr = MTRErrorToCHIPErrorCode(removeError); LogNSError("Failed to remove current fabric: ", removeError); } else { ChipLogProgress(chipTool, "Successfully unpaired deviceId %llu", mNodeId); } SetCommandExitStatus(removeErr); }]; }]; }
@@leoxie1971 非常感谢你的分享. 应该是 Session Resumption. “The protocol also provides a means to quickly resume a session using a previously established session. Resumption does not require expensive signature creation and verification which significantly reduces the computation time. Because of this, resumption is favoured for lowpowered devices when applicable. Session resumption SHOULD be used by initiators when the necessary state is known to the initiator.”
@leoxie1971Рік тому
@@torchiotbootcamp7844 up视频全是干货,希望能出更多视频
@torchiotbootcamp7844Рік тому
@@leoxie1971 希望多交流, 共同进步
@leoxie1971Рік тому
我看你写的session id 和 security flags与0.9spec中是反的,是新的文档更正了吗?
@torchiotbootcamp7844Рік тому
我看了1.0 pre的Spec, 没有改变呢 “The Unsecured Session SHALL be indicated when both Session Type and Session ID are set to 0.”
@leoxie1971Рік тому
@@torchiotbootcamp7844 视频51s位置的session id 和 security图片和0.9、1.0的spec不一致,有可能新文档后期更改了这两个字节的顺序
@@torchiotbootcamp7844 it's solved thanks for your support Can you make video on how matter node communicate with chiptool and with each other... TIA
@torchiotbootcamp7844Рік тому
@@hiteshmathukiya1297 You can watch the matter CASE, ukposts.info/have/v-deo/qoWbgX5rf62UloE.html that is capture of the communication between node and chip-tool
@hiteshmathukiya1297Рік тому
Keep it up sir... Very knowledgeable video
@hiteshmathukiya1297Рік тому
Please make video on 1) one chip controller to multi node 2) matter node to matter node communication. 3) chip controller to chip controller communication 3) matter to non matter device This will very helpful. Thanks🙏🙏
@hiteshmathukiya1297Рік тому
Nice
@yurishion5388Рік тому
最好的教程往往用最通俗易懂的方式讲解,赞 !
@hiteshmathukiya1297Рік тому
Nice.... Can you make video on unpairing device.... And.....video on multiple commissioner and multiple commissionee..
@hiteshmathukiya1297Рік тому
Nice video
@torchiotbootcamp7844Рік тому
Thanks so much!
@hiteshmathukiya1297Рік тому
Please make video of multi admin
@torchiotbootcamp7844Рік тому
Put on the todo list. Just publish a new video "matter commissioning"