We’ve finally looked into it, and the error is due to duplicate location identifier.
Location identifier can be passed as an
identifier parameter (in the root object, e.g., next to
name), or if its not there (like in the example request), then its auto-generated from the location name. (e.g., “My location” becomes “my-location”)
So for now, as a quick workaround, just can try passing the
identifier explicitly (and set it to something that’s unique to your account, i.e., not already in use for other indoor locations), or using a unique name.
We’ll probably change the identifier-from-name generation to produce unique names (e.g., by appending a few random/unique characters at the end, “my-location-z65d”, similar to what we do for app tokens). ((And of course, add proper validation and error messaging for this case.))