You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Flash device which need to be commission over BLE,
Start BLE advertisement
Apply needed changes to provided script
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'
The text was updated successfully, but these errors were encountered:
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
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.
Reproduction steps
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:
The text was updated successfully, but these errors were encountered: