About compatibility of Eddystone Specification.

[cw-park]

I'm developing nRF52832 to implement the Eddystone (※ 1).

But i'm thinking seriously about what can I do to have the Eddystone Specification and compatibility.

please, Answer me questions below.

(Q1)

Is there such as Eddystone authentication?

If there is no such as authentication processing of Eddystone,
    
What should I do now in order to have also Eddystone Specification and Compatibility?

Is it OK that simply implement a 「nRF5 SDK for Eddystone」(※1) of providing your company?

(Q2)

I know that your'company also has been checked from Google Inc about 「Support for the Google beacon platform」 .

Is 「nRF5 SDK for Eddystone」 the same source that was used when performing this check to?

If Not,  Would do you tell me about the information(source, etc...)?

(Q3)

In order to be compatible with Eddystone Specification Is TLM outgoing required?

If Outgoing of TLM is carried out with dummy data(Battery,Temperature...),

Can't be compatible with Eddystone Specification?

(Q4)

If we want to add company name to the 「Listing as an Eddystone manufacturer」,

Despite the use of your company the 「nRF52 module」 and the 「nRF5 SDK for Eddystone」,

Do you(Google?) need to check our devices?    

(※ 1) github.com/.../nrf5-sdk-for-eddystone

(※ 2) developers.google.com/.../eddystone

[ketil]

Hi CW-Park,

Thank you for your questions regarding Eddystone. My answers are below.

1. By implementing the nRF5 SDK for Eddystone firmware you will comply to the listed characteristics of the Eddystone specification.

2. Yes, nRF5 SDK for Eddystone was the source used to get the qualification.

3. TLM is required in order to get your beacons qualified by Google. You should replace any dummy data with real data in your application.

4. In order to be listed as an Eddystone manufacturer you must send your beacons to Google for testing. Start the process by filling out this form.

We are currently working on making the nRF5 SDK for Eddystone a part of our official nRF5 SDK. This means more support will be available to you. If possible, I recommend you wait for a few days and use the official nRF5 SDK version.

Ketil

[cw-park]

Thank you for answers.

1)I'm sorry, but are you the staff of nordic company?

2)In order to receive information from Eddystone-URL in the Physical Web, Is TLM outgoing required?

Does not alone Eddystone-UID and Eddystone-URL?

(it is OK that TLM is required to get the qualification. Thanks.)

3)In above Number 2, 「nRF5 SDK for Eddystone」was basically implement One(Eddystone-URL).

Nevertheless, Did you get the qualification in the 「nRF5 SDK for Eddystone」 ?

(Basically Not Supported TLM.)

[ketil]

Hi again,

1. Yes, I am Nordic staff.
2. An Eddystone-URL does not require TLM or any other frame types in order to work with the Physical Web.
3. I'm not sure if I understand the question, but yes, we did get the qualification with the nRF5 SDK for Eddystone.

If you only want to use Eddystone URL with the Physical Web we also have examples for that. Take a look at the experimental Eddystone example in the SDK and the nRF52 Blinky Web App example.

Ketil

[cw-park]

Thank you very much for quickly answers.

Wait for official nRF5 SDK version. And expect that.

[ketil]

You are welcome. Good luck!