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
chip-tool doesn't work on OSX Monterey 12.1 and above #13303
Comments
Title says
|
Title updated, and yes, I can confirm that on 12.2 Beta 21D5039d, it does fail in the same way you are describing. |
chip-tool on macOS 12.3 Beta (21E5196i) now able to establish BLE connection. It still fails, but seems to be a different problem, and I also see it on Ubuntu 21.04. I will open a separate issue if I can't find one. |
I have the same issue but not on Mac OS (Intel Monterey 12.0.1) but on my iPhone (iOS 15.2.1). We have narrowed it down to an issue with the ZigBee service (0xFFF6) not being discovered by the CoreBluetooth Framework. It works perfectly with the DUT on the MacBook, but it fails on the same codebase but on iOS. EDIT: I have tried using an older iPhone with older iOS (15.1) and it works, meaning that it can actually find the 0xFFF6 service. @woody-apple are you aware of what is happening on the MacOS and iOS platforms with respect to this issue? |
I updated to Monterey 12.2.1 today and seeing the same issue. It was working yesterday on Big Sur. Log attached of attempting to pair with standalone CHIP tool: |
This is most likely due to iOS (>=15.1) and macOS (>=12.2.1) somehow "swallowing" the Bluetooth Service UUID |
This seems to have been fixed in macOS 12.3 (and 12.3.1) so should we close this issue? |
This is resolved in macOS 12.3. |
I'm using macOS 12.4 and Matter commit b4b3400. For some reason I can commission a device (esp32) using wifi over BLE. But when trying to commission a Thread device (nordic nrf52840dk) with a Thread border router (esp32 ot_br + silabs RCP) over BLE the chip-tool on macOS 12.4 it doesn't work. The chip-tool connects to the thread device over BLE but thread device instantly disconnects with a BLE GAP error. For some reason whenever I use the chip-tool on Ubuntu 20.04 LTS the commissioning process works as expected. I don't have my thread devices with me right now to post the logs but whenever I get back to the office Monday I'll post logs from chip-tool and the thread device. Once I get back I'll post logs from both, the chip-tool on mac logs and thread device logs. |
Most likely it's a bluetooth issue (as Monterey seems to have few), but wanted to double check if maybe it's something else.
I have two examples here (attempt to commission a node and attempt to send a command to an already commissioned one)
Commissioning a new node
stalling at this point.
Send message to existing node
The text was updated successfully, but these errors were encountered: