Skip to content
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

Broken rendezvous between the Python controller and devices #6092

Closed
Damian-Nordic opened this issue Apr 16, 2021 · 1 comment
Closed

Broken rendezvous between the Python controller and devices #6092

Damian-Nordic opened this issue Apr 16, 2021 · 1 comment

Comments

@Damian-Nordic
Copy link
Contributor

Problem

After merging #5938, the commissioning no longer works between the Python CHIP Controller and Nordic examples. Since Nordic examples use the common Server/RendezvousServer from src/app/server the issue may be visible on other embedded platforms, too.

chip-device-ctrl > connect -ble 3840 12345678 1
...
CHIP:DL: New BLE connection 0x7fa33c032230, device FB:2F:8F:AE:9C:EE, path /org/bluez/hci0/dev_FB_2F_8F_AE_9C_EE
CHIP:DL: HandlePlatformSpecificBLEEvent 16385
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: HandlePlatformSpecificBLEEvent 16388
CHIP:BLE: subscribe complete, ep = 0x7fa34e287280
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:BLE: peripheral chose BTP version 3; central expected between 2 and 3
CHIP:BLE: using BTP fragment sizes rx 20 / tx 20.
CHIP:BLE: local and remote recv window size = 3
CHIP:BLE: Assigned local session key ID 0
CHIP:BLE: SessionEstablishmentExchangeDispatch::SendMessageImpl mBLETransport 0x2b8ab10, mTransportMgr 0x7fa340007910
CHIP:BLE: Sending message using BLE transport
CHIP:BLE: Sent PBKDF param request
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:EM: OnMessageReceived failed, err = CHIP Error 4112 (0x00001010): Unsolicited msg with originator bit clear
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:DL: Indication received, conn = 0x7fa33c032230
CHIP:DL: HandlePlatformSpecificBLEEvent 16389
CHIP:DL: HandlePlatformSpecificBLEEvent 16387
CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
Failed to establish secure session to device: 4050
CHIP Error 4050 (0x00000FD2): Timeout
chip-device-ctrl > CHIP:DL: HandlePlatformSpecificBLEEvent 16388
CHIP:BLE: Auto-closing end point's BLE connection.
CHIP:DL: Closing BLE GATT connection (con 0x7fa33c032230)
CHIP:DL: BluezDisconnect peer=FB:2F:8F:AE:9C:EE

@pan-apple have you tested the change with any embedded devices? Do you know what can be missing?

Proposed Solution

Find the problem, fix.

@Damian-Nordic
Copy link
Contributor Author

Sorry, false alarm. I must have forgotten to rebuild the firmware. Works correctly now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant