

This reply is extremely informative and helpful.
#Mobilinc radius networks radbeacon install
You can install rbcom with Homebrew if you have a Mac: If your use case doesn't require over-the-air communication, I'd strongly recommend switching to this approach. It requires a USB connection to the beacon, but it supports all versions of RadBeacon USB firmware (including v3.2.3). I'd also like to recommend our command line tool for communicating with RadBeacon USB devices over the USB port, called rbcom. That said, we'd be happy to provide you with any information you need if you'd like to build this functionality for yourself. UUID (bytes 10-25): 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6īecause this is such a major change and would require a large amount of development work on this gem, we don't have any plans at this time to work on adding v3.2.3+ support. Which corresponds to an AltBeacon advertisement with the following identifiers: I am hoping it is as simple as using something different than 0x0020 such as another register.Ġ2 01 06 1b ff 18 01 be ac 2f 23 44 54 cf 6d 4a 0f ad f2 f4 91 1b a9 ff a6 00 01 00 02 be 00 if we need to use another tool (such as the RadBeacon MacOS app) to change the device UUID, or to first downgrade the firmware, it contradicts our aim of using this script. Our specific use case for this (ultimately awesome!) ruby script involves us setting up new beacons. We accept that 0x0020 has been deprecated in 3.2.3, and we are wondering then: what is the way to change the device UUID in 3.2.3? Is there another register akin to 0x0020? When we upgraded it, and tried to run it on 3.2.3, it failed with this failed: char-write-req 0x0020 F7826DA64FA24E988024BC5B71E0894C"] Our attention was directed to UUID because that is where the problem was being encountered.įollowing this: WHAT DO WE DO FOR 3.2.3+?Īs instructed, we downgraded the firmware to 2.2.2 in order to run this, and it was successful.
#Mobilinc radius networks radbeacon for mac
We understand Mac addresses are generally lower case, but we had seen validation in the code for UUID and presumed similar validation existed for Mac address. NewLe = Radbeacon::BluetoothLeDevice.new("00:07:80:C6:1D:B5", "A test name")īy changing our Mac address to our lower case as well, the ruby script worked. Very nice! The most significant item in your sample code is that you used lower case characters in the Mac address. I can see the results of the scan.Īlso the following successfully produces a listing of nearby beacons: Sudo hcitool lescan works when I use it directly in the terminal.

One interesting thing is that I can put in a false mac address, and that will return a similar object. So the object is returned, but the dev_name, major, minor, etc. It seems that a Radbeacon::Usb object IS being returned (because if i print out radbeacon.inspect I can see this info: The purpose of this issue is found in the last line about undefined method for nil. Note that the output regarding no description specified, successfully built, etc. Parsing documentation for radbeacon-0.1.3ĭone installing documentation for radbeacon after 1 secondsĠ0:07:80:C6:1D:B6./provisioning/purple.rb:4:in `': undefined method `dev_name=' for nil:NilClass (NoMethodError)
