I have Sim800 modem and trying to get connected with the bluetooth of the module but when I send command AT+BTPOWER=1 it returns error so I am unable to get connected.
anyone can help in this????
Your version of Sim800 can be without supporting BT by hardware
If your module has hardware support, try to update firmware
Try command BT+STATUS? probably BT module already powered on
Came late to discussion but I must say that you have to turn it off before turning it on. If you try just setting BTPOWER=1 it'll return ERROR, at least for me.
AT+BTPOWER=1
ERROR
If I set it to 0 before setting to 1 I have success.
AT+BTPOWER=0
OK
AT+BTPOWER=1
OK
Related
I have an Ubuntu 18.04 server on a laptop that has bluetooth adapter. I also have a led strip from China which also has a bluetooth adapter. I can control my led through an app on my phone.
Is there any way to successfully connect to the led strip with my linux laptop and control it?
If so, how could I know which code / key (or I don't know how this bluetooth control works, sorry) is assigned to a color? So basically, I don't know what command should I send to the strip.
Can anybody please write an example program for me?
I tried the rfcomm, bluetoothctl and bluetooth-sendto but they didn't work. :(
Hope we can solve my problem.
You'll need to reverse engineer your device :
with little research I found this
http://nilhcem.com/iot/reverse-engineering-simple-bluetooth-devices
like the title says, i am not able to connect to a le device on my raspberry pi 3.
I tried:
- via bluetoothctl i get an AutenthicationFailure
- via gatttool i get connection refused (111)
I searched a lot for a solution and already tried (made sure that):
- btmgmt le up
- reinstalling bluez/bluez to the newest version
- use of "-t random" when using gatttool
And know i really have no idea what to do next.
What might be important:
uname -r = 4.19.58-v7+
bluetoothctl -v = 5.50
Using the Android App nRF Connect the connection to the le device works fine.
Can somebody help me please?
Thanks in advance,
Magda
It looks like your device needs to be bonded and Bluez fails to successfully bond...
I have the same issue with several devices that need bonding. Bluez can apparently only deal with some variants of bonding but certainly not all. On iOS and Android I have no issues at all with those devices...
Unless you fancy digging into Bluez source code and fixing the issue yourself, I think you can only wait for some Bluez update to fix the issue...
Hi This command in terminal
obexftp –nopath –noconn –uuid none –bluetooth <BTAddr> –channel <OPUSHChannelNo> –put <FileToPut>
Should allow a file to be sent to remote bluetooth device without the requirement of a pin on a remote device.
When i populate this with my data
obexftp –nopath –noconn –uuid none –bluetooth 64:89:9A:DE:49:FA –channel 12 –put DUN.jpg
I get the following error
Try `obexftp --help' for more information.
Nothing to do. Use --help for help.
I can get it to work with this terminal command
obexftp --nopath -noconn --uuid none --bluetooth 64:89:9A:DE:49:FA --channel 12 -put DUN.jpg
But the problem is the remote device asks the user to pair before allowing the file to be received. I need the solution to skip the pair request.
Or if anyone can suggest an alternative terminal solution where i can send a file from a raspberry pi to mobile device without the requirement to pair would be great.
Any suggestions would be gratefully appreciated. Thank you.
Even i am facing these issue. No matter how u use the obexftp with bluez, you need to use the pin to pair the device which was not acceptable by me.
Though there is one way around, use gnome-bluetooth package, you will be able to send the file using bluetooth-sento command with some parameters which i guess you will get it.
I have recently been attempting something similar using an embedded device and an Android phone. I believe what you are seeking is not possible as it would be a security risk for the Android device is you could just simply push a file to the Android device without first asking for permission/pairing. Unless you make modifications to the Android device and underlying code, I do not think you will be able to achieve your desired goal.
I am looking for a solution to monitor BLE devices near my raspberry with their RSSI value. So far I am done with monitoring, all devices and the current rssi value is displayed on screen, but I would like to
store the values in a database or
send them to RabbitMQ (either solution is fine).
I am using btmon for monitoring which has a switch "-s" or "--server". Unfortunately I did not find any useful documentation on it (might be my fault). I thought this might start monitoring in a way that I can query it from another application. Any clue?
The other solution could be node.js/noble, but noble installation always fails.
Well, btmon could not be my solution as device discovery needs to be triggered with hcitool lescan which does not have a recurrence parameter (only hcitool scan has). The solution finally was node.js/noble. The installation failed, because I tried to do it with the latest version of noble.js. Going back to 10.x solved the problem.
I'm trying to get a USB HID device to work on Raspberry Pi.
The code utilizes the RawHID lib for MacOSX/Linux/Windows.
I got it working on MacOSX, but for other reasons I can't use it on that OS anymore. Now I'm trying to get it to work on Raspberry Pi via hid_LINUX.c.
When I tried it out, it just completely fails to connect. I added the debug info, and found out it's failing here:
if (usb_claim_interface(u, i) < 0) {
printf(" unable claim interface %d\n", i);
continue;
}
I tried googling for ages and I see various things about...
modprobe.d blacklist (didn't work, although that looked for for rtl devices... not sure)
updating all packages (didn't work)
compiling your own version of libhid (I don't know why I'd have to do this, considering the creator of the USB device recommended this RawHID lib which uses libusb-dev (usb.h), and which works fine on OS X and Windows)
Does anyone have any possible ideas how I can proceed? How do I 'free' my USB device so I can claim it?
I have a Raspberry Pi B+
Apparently I can not comment (insufficient reputation) so I answer instead:
I finally found the reason for my problem with the comment "Now I solved it by just running the code with sudo rights" above, so I'm grateful!
I use a Pi 3b for Domoticz for > 3 years. (same software on PC before that) After a failed update, followed by a complete re-install, my CM15 Domoticz interface (connected via USB) would be recognized as present with lsusb, but would not work. I boot my PI from a USB key, so maybe the -very old- USB key failed, so I bought a new USB 3.0 key. No joy. USB 3.0 uses more power, maybe draining USB power from my CM15, so I bought a bigger supply. Did not solve the problem.So I bought a new memory card, no change.
Searching for "usb_claim_interface failed -6 mochad" brought me here for a correct diagnostic and the way to make it work "manually"
Not yet the solution; normally libusb starts the "interface" software (mochad) when it finds a new USB device connected, but "claiming it" apparently now requires more permissions. Now that I understand the problem, I'll find the answer.
Thanks much for showing the way dennis-tra!