Is it possible to use MIT App Inventor 2 to connect my phone to two bluetooth devices? I need to connect to another phone and an Arduino(3 devices in total). How could I do that?
Yes, you can.
As you already found out, a bluetooth component in App Inventor can only connect 2 devices.
In your case, just use 2 bluetooth components: component1 to connect to another phone and component2 to connect to an Arduino.
See also the documentation
Related
I am using MIT App Inventor 2 to do some bluetooth connection. I am trying to connect to my Arduino Bluetooth hc05.
I noticed that if I didn't pair my device, the app I wrote can't connect to the device.
Below is the code that I used to connect to my Bluetooth device.
Is there any way to use the code to connect with the Bluetooth device without having to pair it first?
Or is there any way to use the code to input the pairing password using MIT App Inventor 2?
The devices must be paired before being able to connect.
There is no Pairing method available in the App Inventor Bluetooth components. But you could write your own extension, which does the pairing.
More information about how to create an extension see here.
However that will be more advanced and will require some Java skills...
I'm trying to pair my iPhone with my ubuntu computer over bluetooth. I'd like to use CoreBluetooth. I have bluez configured correctly, but I need a UUID for CoreBluetooth to connect to my computer. How do I go about setting a custom UUID in bluez?
Ultimately, I'd like to send commands with my iPhone to my pc and then use https://github.com/eelcocramer/node-bluetooth-serial-port to access the transferred data. Is there a better way to do this? I'm new to bluetooth.
Does your computer supports bluetooth 4.0? You can search for
[centralManager scanForPeripheralsWithServices:nil options:nil];
and every reachable device will be found.
With your other problem i can't help you sry.
You need to use bluetooth classic not the low energy for serial port communication
Has anyone tried SPP service (RFCOMM) on Google glass? I couldn't find any documentation anywhere listing what kind of Bluetooth protocol or profile that Google glass supports.
I have run an OBEX service search on the glass, and it seemed like Google glass doesn't support OBEX. Other than OBEX, what other BT profile is known to work properly on the glass?
So for SPP service (RFCOMM) you can use the UUID "00001101-0000-1000-8000-00805F9B34FB" as you might already know, I'm using this and it works fine at 115.2K of baudrate.
Then in a separate thread you manage the connection, if you go to the developers portal of Android they have an explained example and good info of the protocol.
Using the Bluetooth APIs, an Android application can perform the following:
-Scan for other Bluetooth devices
-Query the local Bluetooth adapter for paired Bluetooth devices
-Establish RFCOMM channels
-Connect to other devices through service discovery
-Transfer data to and from other devices
-Manage multiple connections
Hope this helps!
I am trying to read serial data over Bluetooth LE but can't find any code examples for this type of bluetooth and api19. Does any one have an example?
There is no profile defined for serial data communication over Bluetooth Low Energy till now. For this one can use the Bluetooth classic only.
In any case, Android devices can not broadcast for advertising packets. They can only scan the advertising packets. Hence, these devices will be in Central mode only. But can act as either server or client.
For Bluetooth chat related app example one can refer Android SDK as,
sdk/samples/android-19/legacy/BluetoothChat
The above example is based on Bluetooth classic based on RFCOMM channel for serial communication.
Android 5.0 let mobile to be peripheral. So chat will be possible:
https://developer.android.com/about/versions/android-5.0.html
Bluetooth Classic got the SPP profile. This is not how Bluetooth Low Energy works.
In BLE you have 1 or more Services each with 1 or more Characteristics which are basically just bytes in a predefined format which by default can be max 23 bytes.
To send data from one device to another one must be the Master and the other must be Slave.
Android API19 does not support the Slave (Peripheral) role, it seems Google still doesn't understand the importance of Bluetooth Low Energy. It's so much more than just Pulse-readers.
You can send from an Android API19 phone to e.g. an iPhone which can be Slave/Peripheral.
You cannot send from an Android API19 phone to another API19 phone. For this you must use Bluetooth Classic SPP profile.
I doubt the limitation of PeerFinder class in .NET. Can it make connection only with other laptops when implemented on laptop and phone to same phone when implemented on phone? Is it limited only to communicate with Windows OS devices, or is it able to communicate with any bluetooth device irrespective of OS?
Kindly, help me if you are sure of this class capabilities. I have seen the implementation of 32Feet.NET but my question is limited about PeerFinder class and its limitations.
Start from this link, in which you can find several useful links for WinRT communication (the suggested protocol to use from Windows Phone 8 to communicate using NFC or Bluetooth)
http://blogs.ugidotnet.org/Nick60/archive/2012/12/30/win-rt-proximity-communication.aspx
You have two possible scenarios:
App to Device: you can connect a Windows Phone 8 device to third party devices (for example a LEGO robot or car audio systems) Bluetooth/RFCOMM (that is serial port profile, for the emulation of RS232 serial connections).
App to App: for communications between Windows Phone 8 devices and also Windows 8/Windows RT devices!
The PeerFinder class is the base class for discover another instance of your app on a nearby device and create a socket connection between the peer apps by using a tap gesture or by browsing:
http://msdn.microsoft.com/en-us/library/windows/apps/br241203.aspx
Hope this helps!
Unfortunately, it seems that the only way to stablish a socket connection using Bluetooth between a WP8 app and a Windows 8 app is by triggering the connection using NFC tap gesture. Although the PeerFinder documentation suggests that you might be able to specify AlternateIdentities to advertise peers running on both devices, it seems that Windows 8 relies on WiFi Direct, while WP8 uses Bluetooth.
So, if you are not able to use the NFC tap gesture between both devices to trigger the connection, you might not be able to pair both apps running on the different devices.
See this thread for more info.