Last time I worked with Nearby and Proximity API as on July of this year, and, according to the docs (last update Fev. 2017):
Any beacon you register with the Proximity Beacon API is associated only with the project under which it was registered. Once registered with a project, the only way to move a beacon to another project is to give the beacon hardware a new beacon ID using the provisioning software from the beacon manufacturer, and then register the beacon with the new project.
If I remember correctly when a beacon was added to the Beacon Dashboard it was possible to add attachments only to the project where the beacon was added. I could configure a namespace, type and data.
Today I had to configure another project and for my surprise when I was in the attachment tab I could choose a different project to add that attachment and the namespace is not editable anymore (is given by default and it's similar to the project id).
Does this mean I can have a "My beacons global project" and then configure attachments to other projects? I've made a test and the attachments where delivered to other projects as configured.
Did something change in the meanwhile or I've always missed this from the beginning?
Thanks for your time.
