Can’t claim the UWBs that were purchased by a different email. The app doesn’t work either as it cannot find the beacons that are sitting next to the phone. Pressing the buttons doesn’t do a thing.
Emails go unanswered.
Anyone know how to the resolve.
I just tried to set mine up in the IDE and it says my email (the one I ordered with) has no connection to any purchased beacons. I sent an emal today (Dec 8th). I will see how long it takes to get answered.
Hi guys, unfortunately I already experienced this problem and until the Estimote team adds the beacons to your account, it will be impossible for you to work with them. You can either tell them the account or migrate them to another email. However, we have been having no response from Jakub or anyone from his team for over three weeks. In fact, we bought another dev kit that hasn’t been shipped yet, and we wanted to buy some customized ones for our use case but we are still waiting…
I did get replied to and got my devices added to my account, but I asked if any app worked with them (there are like 5 apps) and have received no response yet. If I cannot get my particular use case answered I will attempt to return the item. Anyone go through the return process?
Honestly, I can’t tell you anything about the return process. However, I can confirm that none of the apps listed for testing in the Estimote IDE work for UWB beacons. You can find the working examples in my repository: GitHub - AuroraPR/Estimote-UWB. They work perfectly 
Hi guys, I was thinking about buying a development kit, but reading this post I’m starting to have some doubts.
In particular I would like to understand a couple of things: without the intervention of estimote are these objects unusable?
do you regret your purchase?
and especially in @Aurora, (p.s. thanks for sharing your repo) which seems to me to be quite advanced in development, do the TAGs work as described on their site?
Hi @astolfo !
Indeed, if Estimote hasn’t assigned the beacons to your email, you won’t be able to program them or communicate with them. In the first kit we bought, we didn’t need to request that they do this since they had already assigned it, but for this second kit, we had to ask for it. We don’t regret the purchase because they are very good products, but the post-sale service and customer support could improve a lot. We’re not sure why Estimote’s team disappears for weeks or even months.
As for the deployment, with the code I shared, it’s very easy to deploy them; you don’t need extensive knowledge, and they work well as described. If you find it useful, I could also share how to upload the code to the beacons in the repository.
The only downside is that if you need to contact Estimote, it can be tricky or you may have to wait quite a while for a response. 
Knowing what we know now, we would have gone with a different vendor. There are a few out there and Google even has an alternative other than Estimote for UWB beacons. A bit more expensive but they look to provide everything you need as part of the package.
As for anyone looking for a refund, I don’t think that would ever happen. If you can’t even get a response from the company for support of their product I don’t think you’ll get anything.
Aurora, thank you for providing what you have.
Hi @Aurora,
The fact that estimote needs to assign email to the beacons to work could be a big problem, because it assumes that the estimote cloud will continue to work forever, and adds a percentage of possible errors during operation. For example, if there is a downtime in the estimote cloud, the beacons would probably stop working, and that is not a good thing!
In any case, I think I will test them anyway, if, as you say, it is true that they work well as described.
Of course, it would be very useful if you would share how to upload the code to the beacons.
“We don’t regret the purchase because they are very good products, but the post-sale service and customer support could improve a lot”
They should hire you 
Now I’ll try to buy the kit, let’s see what happens
Hi @astolfo, I completely agree with your point about the dependency on the Estimote cloud, but I think there’s an important advantage to consider: once you upload the code to the beacon through their IDE, it keeps running without needing to stay connected to the Estimote cloud. So, it’s more like an initial setup step, and unless you need to update the code or check something specific, you can operate without it.
In fact, in my GitHub code, the responder is currently configured to send data to the Estimote cloud, but it’s not necessary, and those lines can be removed. Instead, you could configure it to send the data to a specific IP using MQTT or another protocol—it’s all just JavaScript programming in the end.
Anyway, I’ll try to upload a step-by-step guide to the project’s README or an additional document on GitHub on how to connect and upload the code to the beacons. It’s pretty simple, but having a guide could make things even easier.
Good luck! Feel free to reach out to the forum anytime! Let’s hope the Estimote team starts replying soon.
Thank you for posting this @Aurora! It seems like you’ve done more work than Estimote team has done in the last week…maybe month.
I was able to flash my devices with your provided code.
I am attempting to build an app that interacts with UWB devices. If you get any info on how to obtain the UWB address of a device or how to get a single app of theirs to work, lol, I would be all ears!
Let us know if we can help you with any of your use cases as well.
Best,
Daniel
@m-montoya, happy to help with anything you need
I imagine the other vendor you’re talking about is MK Mobile, which Google also lists on their UWB-compatible page. We’ve also acquired their technology, but I have to be honest—it’s significantly more expensive and less visually appealing. I haven’t had a chance to test the product yet, but their customer service is outstanding. We’ll see if the price difference is worth it and if it meets the functionality.
Thank you so much for your kind comment @danc2050 ! I’m really excited to get this technology working, as I find UWB incredibly fascinating. In our case, we’re using it for indoor monitoring focused on human activity recognition and health, aiming to help people stay in their homes as long as possible.
Regarding creating an app that interacts with UWB devices, could you clarify what you mean? What type of app are you planning to develop?
About the UWB protocol, keep in mind that communication depends on whether the devices follow the FiRa Consortium standard. If they do, UWB devices need to perform a handshake to establish communication. This process involves securely exchanging unique identifiers and synchronizing the devices to ensure they’re compatible and authorized to interact.
The devices we’re working with (this UWB tags) don’t follow the FiRa standard, which means they can’t communicate with devices that do, such as Apple Watches, Pixel phones/watches, or Samsung devices. They can only connect with other non-FiRa-compliant devices. If you want them to work with this kind of device, you should check out the other UWB beacons from Estimote (the rock-shaped ones), but keep in mind they are not programmable.
Best,
Aurora
Great, that’s what I wanted to hear…
it sounds totally different when you say it like that.
Thanks a lot @Aurora, I hope to return the favor soon!