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

[BUG] [Python][Controller] Creating multiple simulated controllers cause not possible to commission over BLE #34134

Closed
doublemis1 opened this issue Jun 28, 2024 · 3 comments
Labels
bug Something isn't working needs triage python stale Stale issue or PR

Comments

@doublemis1
Copy link
Contributor

Reproduction steps

  1. Flash device which need to be commission over BLE,
  2. Start BLE advertisement
  3. Apply needed changes to provided script
  4. Run Provided script -> Commissioning fail

Bug prevalence

always

GitHub hash of the SDK that was being used

main

Platform

python

Platform Version(s)

1.3

Anything else?

Script to reproduce the issue and logs from the python chip module can be found in below zip file:
script_and_logs.zip

The python controller fail commissioning in presented setup due to:

Traceback (most recent call last):
  File "test.py", line 78, in <module>
    result = controller1.CommissionThread(
  File "/home/michal/.local/lib/python3.8/site-packages/chip/ChipDeviceCtrl.py", line 1826, in CommissionThread
    return self.ConnectBLE(discriminator, setupPinCode, nodeId)
  File "/home/michal/.local/lib/python3.8/site-packages/chip/ChipDeviceCtrl.py", line 440, in ConnectBLE
    self._ChipStack.CallAsync(
AttributeError: 'NoneType' object has no attribute 'raise_on_error'
@doublemis1 doublemis1 added bug Something isn't working needs triage labels Jun 28, 2024
@andy31415
Copy link
Contributor

@doublemis1 what does Apply needed changes to provided script step mean?

@doublemis1
Copy link
Contributor Author

in zip file there is a script with the reproduction and need update the discriminator, path to paa discriminator and passcode.
However the issue was visible before:
#33989

Now I am looking at this PR, which handle other issue found on our side:
#34231

I think that we can close this specific issue.

Copy link

github-actions bot commented Aug 8, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale Stale issue or PR label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage python stale Stale issue or PR
Projects
None yet
Development

No branches or pull requests

3 participants