I would like to pair my Bluetooth Low Energy Sport Watch (Suunto Ambit 3) to my Raspberry PI 3 B V1.2
I am using the RaspianOS Version 10 buster with kernel Version 5.4.79-v7+
This OS contains the bluez stack in version 5.50 which was installed from a predefined package via apt-get.
Usually the ble pairing is done with smartphones under android and IOS. When doing the pairing process the watch offers a pincode which has to be entered by the smartphone.
With nRFConnect app under android the pairing works fine.
When I am running the hcitool on my raspberry and the watch is in pairing mode it appears.
sudo hcitool -i hci0 lescan
but when i try to run the sudo bluetoothctl command with scan on my device does not appear and pairing with the correct mac address does not work either.
Other devices still appear in bluetoothctl
I also had a look into https://github.com/raspberrypi/linux/issues/3689 but this seems that this is only related to newer raspberry pi models.
Do have any idea what hinders my device from being found in the bluetoothctl scan mode or what can I do to pair my device with pin code enabled?
I found a solution by myself.
inside bluetoothctl calling the following sequence
menu scan
transport le
back
scan on
finally enables bluetoothctl to find my watch.
The connect command is then also working.
Related
My Node.js project utilizes CEC control and VLC where the app turns on the TV and chooses the HDMI port that the VLC video stream will be viewed on at a scheduled time.
Everything worked on Buster except that too many indeterminate crashes with segmentation faults occur with cec-client.
Since I am nearing a 'production' release, I thought it best to upgrade the OS to Bullseye and find a cec-client replacement. I found cec-ctl and made it asynchronous - ctl-cec works perfectly, everytime, no crashes. BUT, now VLC does not render anything, not even a black screen. Doing a 'ps' command during a time that a video should be playing, I can see that VLC is running.
What I tried: It turns out that changing the /boot/config.txt dtoverlay=vc4-fkms-v3d (Buster) to dtoverlay=vc4-kms-v3d (Bullseye) causes the problem. The Buster version of dtoverlay seems to be required for VLC to run, and The Bullseye version of dtoverlay is required for a /dev/cec0 to be created and used by ctl-cec.
All I can see from my inexperienced view is mutual exclusivity, but this doesn't feel like this is the final answer. Using both dtoverlay version (Buster/Bullseye) will brick the pi (speaking from the very recent experience of one not well-versed in dtoverlays).
I also tried: I Googled this problem to the extent of my search skills and have not been able to resolve this problem.
Any help is greatly appreciated!
Raspbian OS: Bullseye (Desktop)
Raspberry Pi 3 B+
App: Node.js based with ability to make config changes and set schedules via an external browser within the LAN.
The solution for my project, after days of Googling, turned out to be TOO simple (found here: https://www.reddit.com/r/archlinuxarm/comments/lg4z5u/no_hdmi_audio_via_alsa_on_raspberry_pi_400/):
sudo apt install pulseaudio
along with:
dtoverlay=vc4-kms-v3d
VLC and cec-ctl now work together perfectly on Raspberry Pi 3B+/Bullseye
I tried working with my RPi Pico today and my computer doesn't recognize the usb I triple checked the cable is power and data. And yes I'm holding the button
I've also had this annoying issue. Seems to happen even more often on the Pi Pico W.
Use my laptop USB-C port to connect via a USB-C to USB 3.0 hub and this happens every so often.
Bought a powered hub from Amazon: "UGREEN USB C Hub 4 Ports, USB C to USB Hub 3.0". It has a separate USB-C power input in addition to the laptop USB-C connection and it works fine when no other USB devices are connected to the hub. Seems to be an issue similar to what Foibled2 mentioned where the underlying issue may be power related.
I'm struggling with the same thing. Other than uninstalling in Device Manager and rebooting (sometimes several times) I can get it to recover.
There must be a better way.
I've seen references to Zadig, etc. But finally figured out the issue in my circumstance.
I disabled all of my other USB serial devices (Prolific USB for GPS tracker; and CH340 USB for Android Nano).
After that, I could plug / unplug my R Pi Pico between application and USB drive mode without rebooting.
Works now as advertised. Hope this helps short cut a few hours for someone else!
I'd like to use Raspberry Pi 4 to collect data from several BLE mesh supported devices (beacons) that uses a chip like nRF52832, nRF52833 or nRF52840.
I know that Pi 4 comes with bluetooth 5.0.
My question is, can I use Pi 4 as it is without any hat, cape etc. connected to collect data from the beacons that uses those chips and communicates by using the BLE mesh technology.
Yes, you should be able to use the Raspberry Pi for mesh functionality depending on the version of BlueZ that is available there. Mesh functionality was initially added in BlueZ v5.47 (September 2017) and subsequent versions of BlueZ have had bug fixes and additions to this feature. You can find more information here:-
http://www.bluez.org/
You can check the version of BlueZ that is on your Raspberry Pi through the following command:-
bluetoothctl --version
I hope this helps.
Yes I know this problem has been brought up many times, and I have looked through many of the possible solutions over this past afternoon. I'm running Windows8 and have an LG Lucid 3 Device. Android Version 4.4.2
-Usb Debugging is turned on.
-I have tried adb start-server / adb kill-server
-I have tried setting the connection to "PTP mode"
-I have tried that universal google usb thing
-I've tried the the installer for my device specifically.
One thing that I've noticed that is different from other people's problems is that when I go to device manager, it shows my device under "portable devices" instead of "other devices".
"Universal driver":https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Also, when I installed the universal driver, it didn't show up under my list of available drivers to install for the device under device manager.
Has anyone had a similar problem and know how to solve it?
There were a usb connection option "Internet" in LG phones. Select that and try. It worked for me in some LG devices
I downloaded the Suite for the phone, the Google USB drivers and the Phone's connection drivers. So far, the phone works perfectly with the PC but Eclipse still refuses to see the phone and Device Manager is convincing me that I have no hardware compatible with the Google USB drivers. Therefore the Google USB drivers are downloaded but not installed or assigned to any device. I followed every answer on stackoverflow that there is so far, but none have solved the problem.
First, set your device into USB / debug mode.
Second, after you connect your device to the USB make sure your drivers is installed properly.
And last verify that adb.exe can detect you device from cmd (if running in windows) ..(path to your SDK)\platform-tools\adb device
If last step fails, then re-install you device driver, it should be handled automatically by sony pc-companion for your xperia phone.
You also have to enable USB-Debugging in Settings->Developer Options on your phone.