Originally Posted by mstone
Originally Posted by SolipsismX
Not necessarily. Even an iPhone can be turned into an iBeacon. It takes a little hacking to make a Mavericks running Mac into an iBeacon but that is also possible. If you want to make changes to the key/value pairs, that is completely up to you. If you want to move certain merchandise around the store without changing the promotions on the server or the location of the iBeacon you can change the key/value pairs instead.
I don't understand what you mean by changing key/value pairs!
Below is the definition of the CLBeacon Class and it defines what data is received when a listened for iBeacon is detected:
As you can see, everything is (coded into or generated by) the iBeacon. The App must specify the proximityUUID (the iBeacon UUID) t listen for and optionally a major ID and minor ID.
The CLBeacon class represents a beacon that was encountered during region monitoring. You do not create instances of this class directly. The location manager object reports encountered beacons to its associated delegate object. You can use the information in a beacon object to identify which beacon was encountered.The identity of a beacon is defined by its proximityUUID, major, and minor properties. These values are coded into the beacon itself.
For a more thorough description of the meaning of those values, see CLBeaconRegion Class Reference.
Identifying the Beacon
Determining the Beacon Distance
The accuracy of the proximity value, measured in meters from the beacon. (read-only)
Indicates the one sigma horizontal accuracy in meters. Use this property to differentiate between beacons with the same proximity value. Do not use it to identify a precise location for the beacon. Accuracy values may fluctuate due to RF interference.
A negative value in this property signifies that the actual accuracy could not be determined.
The most significant value in the beacon. (read-only)
The least significant value in the beacon. (read-only)
The relative distance to the beacon. (read-only)
The value in this property gives a general sense of the relative distance to the beacon. Use it to quickly identify beacons that are nearer to the user rather than farther away.
The proximity ID of the beacon. (read-only)
The received signal strength of the beacon, measured in decibels. (read-only)
This value is the average RSSI value of the samples received since the range of the beacon was last reported to your app.
Constants that reflect the relative distance to a beacon.
The proximity of the beacon could not be determined.
The beacon is in the user’s immediate vicinity.
The beacon is relatively close to the user.
The beacon is far away.