I can’t seem to find specifics on the BT antenna for the D1 - everything comes up as the WiFi part.
Funny that laying it on its back doesn’t detect but turn it over and put it on the ceiling and I am having fair luck with it.
1 Like
Bermuda has a built in calibration function. If your enclosure affects the readings you should be able to adjust for this by changing the settings. However I find the calibration process quite complicated so if we can support @agittins with finding a simpler solution I think that will benefit all.
1 Like
Probably more of a Bermuda, ESPHome, or Bluetooth integration question but in all my reconfiguring, at some point all my BT Proxies started getting the FULL naming convention applied. I’ve tried to rename, reinstall, and reboot but cannot seem to get the names to clear out of Bermuda and subsequently for use in BPS on the floorplan.
Any ideas?
Also, I have this in all the ESPHome codes:
esphome:
name: ${name}
name_add_mac_suffix: false
friendly_name: ${friendly_name}
With the latest Bermuda update, have you managed to solve the issue. I had the same issue as well. I removed the old “unused” entities and updated Bermuda and now everything works as intended.
1 Like
It cleaned up the device names, yes!
1 Like
Don’t miss that BPS v0.1.2 is out now! 
@NathanCu I have looked into your comment! 
2 Likes
Hi @Hogster just wanted to give my feedback - great work so far! i had one significant issue setting things up but just got it all working and the results look good already.
the issue i had, i think was mentioned earlier in the thread. the integration needs to create entities with unique id’s. the problem i had was i installed, set things up, and then uninstalled and reinstalled again. The second time around i was having the issue that the integration was trying to create entities with the same id as from the first install - failing and overall not working. i only really solved it by introducing a new to home assistant device.
i’m afraid i can’t help beyond that, but hopefully this is some help as although i’m sure a lot of users are already set with espresence, i was looking for a way to use my esp32 devices as both bluetooth proxies AND doing presence detection and your integration enabled that for me. more people should know about this great addition to Bermuda!
cheers
1 Like
Hi @spaceboy,
Thank you for your kind comments as well as your feedback.
I will look into this. Unfortunately I have not been able to allocate any time to this project recently but with upcoming summer vacation I hope this will change. One of my priorities will be to dig into the robustness to make sure both install and uninstall behaves as expected as well as general improvement of tracking.
Best regards
Erik
Just want to confirm I’m reading the git page correctly. Since I’m on an HA Green (meaning an ARM chip) I shouldn’t even bother trying to add the integration yet, correct? Just want to be sure there’s not something I’m missing as I’m anxious to give this one a try.
Good morning, I’m new to this fascinating BPS adventure, as I use Bermuda, and I’m also very happy with it. The problem is that I have BPS implemented, but it only tracks my iPhone, not any other device like an ibeacon. According to what I’ve read somewhere, BPS can only track devices that are in the private BLE device integration, but here I’m also stuck, as I have an Apple Watch registered, which I also can’t see in BPS. I’ve also created a ble_positioning.yaml file to register the ibeacon to the Mac, but it doesn’t work. I’ve also tried adding the ibeacon from the BPS integration UI, but it doesn’t ask for the device details. Could someone shed some light on this? Thanks.
Anyone else has this issue?
I have an entity that is visibly in the Salon zone; but it shows unknown as the room entity
Edit:
Installed a few more nodes but the issue persists:
Yes you are correct. The issue is the scipy library that is currently not available on ARM based chip. Hopefully that will change in the near future and if someone has any more information about this, please share.
However it is worth trying. If you have a raspberry pi 5 (or anything with ARMv7+) and a 64 bit version of Home Assistant OS it should be able to compile. If you have this, please try and let the rest of us know.
I’m on an HA green, which is on the older architecture it looks like. I’ll keep an eye on the updates for this. And I might be moving to a mini PC base anyway as I’m thinking of getting some cameras and frigate going.
EDIT: I didn’t have the distance entities enabled.
EDIT 2: Can see my tracking devices now. But they all simply show unknown, despite it showing correctly on Bermuda.
Hi all,
I have just configured BPS with floor plans, receivers etc. But the BPS integration only seems to detect one of the two tracking devices (a phone) to create entities. It does not seem to pick up the other phone. Although, the device is does pick up, just says unknown all the time.
Both devices are working fine with Bermuda. Is there anything that I need to enable/check for the second device to appear?
I have the issue that my tracking devices just won’t show up:
However, they do work, as an example, all distances are shown (except in this case ble-proxy which is “Unknown” due to out of range):
Any advice?
Hi, I’m having an issue with the token setup. I’ve put both my token and my url in, but it still thinks I haven’t. Any ideas?
Sorry for my late response but have a hard timme currently in finding time for this project.
Without having analyzed the code, I visually notice that you 1) mix upper and lower case 2) have spacing in you names.
What you could try (no guarantees) is to make sure all are low case and replace spacing with underscore “_”.
Best regards
Erik
Based on the image it seems like the url you are trying to use starts with “http://”. As you can see in the example above, it should only contain the ip e.g. “192.168.0.200” or domain without “www.”
Please try and see if this helps!
Best regards
Erik
Same issue here. But I think it’s because I’m running HA on a pi4. This integration doesnt work with ARMs.
Correct, unfortunately no ARM support!