1.2 HOP Beacon (LwM2M)

HOP Beacons with LwM2M provides beacons with global connectivity capabilities. They can be managed from our backend Homard, connected to your own LwM2M Server or simply used via REST API.

#####Features

• Devices send 5 different advertisement by default (it's possible configure 3 of them and disable 2 of them).
  • iBeacon ID (modificable in 9797/0/4 )
    • Can't be disabled. At least one advertisement must be broadcasted.
    • ID automatically created using the a prefix and mac information
  • Eddystone URL (modificable in 9797/0/15 )
    • Can be disabled by writing 00 in the resource
  • Eddystone UID (modificable in 9797/0/16 )
    • ID automatically created using the a prefix and mac information.
    • Can be disabled by writing 00 in the resource
  • Eddystone TLM - Can't be disabled - Contains Temperature, battery in mv, ...
  • HOP Dynamic Advertisement - Can't be disabled - Contains Temperature, Humidity, ...
• Their behaviour regarding connections is use a non-continuos connection mode (so called UDP Queue in LwM2M). This means the beacons will sync with the backend each certain interval. The interval can be configured using the resource /1/0/5, specified in minutes. The minimum interval should be 10 minutes, but this depends of the number of beacons which will try to connect using the same Ubibox gateway. The maximum time is 8 hours (480 minutes). Our recomended value is 3-4 hours.
• The beacons doesn't have GPS, but information regarding their location can be stored in the "Location" object.

######Examples & Tricks

• Example: Change Eddystone URL advertisement for physical web.

  • Step 0: Following this structure: '0201040303AAFE<len>16AAFE10DC<prefix><address>'
  • Step 1: Select your URL Scheme prefix and replace the <prefix> for the hexadecimal value (Example: 00)
    • 0x00: http://www.
    • 0x01: https://www.
    • 0x02: http://
    • 0x03: https://
  • Step 2: Transform the rest of the url using some tool such as AsciiToHex. (Example: homard.hopu.eu is "686f6d6172642e686f70752e6575")
  • Step 3: Optional: Use a suffix byte (HTTP URL Encoding in Eddystone) instead of put the full suffix in the step 2. HTTP URL Encoding values can be checked here.
  • Step 4: Calculate the length by add 6 to the URL address string and translate this number to hexadecimal number (Example: "homard.hopu.eu" is 14 and we didn't use suffix so 14 + 6 (header including prefix) = 20 to hexadecimal is 0x14)
  • Step 5: Write the result in the resource 9797/0/15 (Example: 0201040303AAFE 14 16AAFE10DC 00 686f6d6172642e686f70752e6575)

• Trick: You can check the advertisements with applications such as the official Eddystone validation tool of google (download a compiled version here) or any other smartphone application (Physical Web, iBeaconDetector, ...). Note: some applications such as iBeaconDetector are not capable to well-manage several advertisements from a unique device.