Thanks for your attention. I’ll do that but, funny enough, I have just downgraded Bermuda to have some stability again. Let me try out this version again for a day and I’ll upgrade again and get the diagnostics to upload.
I used to get out of the garage and some 10m ahead I had the automation doing what was supposed to do (so, after the Tesla become unknown but still at “home”). Now I’ll wait about 30 to 40 seconds.
Thanks Ashley. Thinking further on this I removed the Fitbit app permission to “Access nearby devices”. That solved it and I did not have to abandon the Fitbit config settings and history, etc. So I could still use it when away from home if needed. Maybe one day I could automate that setting based on location.
Great thinking! I’ve added this to the Troubleshooting page in the wiki.
Fair enough re the downgrade! There’s at least one fix coming in the next version that might help with this, so don’t feel too much hurry, maybe just wait for the next release.
Hmm actually I think I see this behaviour now that you’ve pointed it out. I think previously it would time out 30s after receiving the last actual packet, but now it looks like it times out 30s after the smoothed value reaches the last received value, which will be later. I’ll look into that further.
Great. May I suggest expanding that to include " … even if the device is removed from the phone’s list of Bluetooth ‘Saved devices.’"
I think the permission option is an Android OS setting and would be for any similar device, not just Fitbit. The actual wording for the setting to Allow/Disallow is “Nearby devices permission”.
I love this integration. That being said, I had been having a lot of issues with my Android phone becoming Unknown recently. Things would start working again as soon as I opened the Companion App. So I did a little digging and found that I had the BLE transmitter configured to Transmit on Home network only. While I’ve got a home network defined for some reason the app would sometimes stop transmitting for me. I’ve disabled that option and things appear to have become much more solid.
I’m just throwing this out there for folks who may be running into issues with their Android devices disappearing as well.
Interesting! I’ve not used that option myself because I want the bluetooth detection to happen well before my phone can connect to the wifi, but good to know that it might not always be triggering.
I’ve created a “Bermuda Cookbook” section in the github discussions. If you have a guide or solution to a particular use-case that you’d like to share, please feel free to contribute!
I plan to put some of my more commonly-typed novels in there too starting with a general guide on how to orient and place proxies for the best results:
If you ain’t got time for that, the whole thing can be summarised with:
Place your ESP32 boards plug-down or plug-up, “facing” you. Put them very close to the spots you tend to loiter, rather than in the centre or edges of areas. Add more proxies for more loitering places. For multi-floor situations, place proxies vertically aligned above/below each other between floors. Read on for whys and wherefores, or just go play.
I was wondering why my announcements were no longer following us around the house. Looks as though after moving from 0.7.4 to 0.8.1 my installation is not tracking anymore.
** Confirmed if I go back to 0.7.4 everything begins to work like normal.
The columns are the history of advertisement measurements, so column zero is the most recent advertisement, column 1 is the previous one to that, and so forth.
Basically you want to get the smallest distance to be correct. When you change the offset and click submit it recalculates all the distances.
That is a really good article on how to position the proxies (link a few posts back).
You warn that using some metal foil to inhibit communications from one direction may have unexpected outcomes. Presumably because it is very reflective. Surely there is some material that could be used to absorb and radically reduce the signal in unwanted directions? For example a steel wool scourer placed behind the proxy? Put it all in a small jiffy box.
I am away for a couple of weeks but I plan to experiment a bit when back.
Yeah, steel wool is an interesting idea, as is the (no doubt eye-wateringly expensive) RF blocking foam that @tom_l linked! (You could contact Linus at LTT, he might have some left over from the first RF Chamber that he bought!)
It’s less a “this won’t work” caution and more a “unexpected results are expected” caution. You’ll have to suck-it-and-see, and you might need to fiddle with stuff in ways that look like superstition. Experiment, but make some effort to measure the results, and don’t waste money on a sticker that’s somehow meant to magically fix it and cure cancer etc.
Also keep in mind that having visitors over that see your foil-covered walls and listen to your rambling explanation about “entities” tracking your phone and “Bermuda” and your “whisper satellites” can easily lead to spending a few years living somewhere else for the safety of society.
Just to clarify … I am talking about making the ESP32 more directional primarily by inhibiting signal through the back. Maybe even a shallow dish reflector in the desired direction. All contained in a box no bigger than a cigarette packet.
I will update on findings … but just basic tests and not until late this month.
Probably not. The Samsung Galaxy SmartTag seems to use Bluetooth MAC address randomization, so you would have to find it’s IRK somehow - I believe this this can be difficult for devices other than phones.