Hi @gcorr, welcome to the community.
We’ve had that question for a while in the back of our minds, whether visibly different bicycle setups (also: hi-vis clothing, helmet, kids trailer, …) had an impact on the proximities. We’ve been thinking about how one would tag the data in a way that it describes this, the biggest challenge is that these setups are not static and change for each user per track, so it would have to be a per-track setting, preferably customizable while starting the recording (because you quickly forget these modalities after the ride, and won’t be able to tag them later on hundreds of tracks). But it is hard to build a user interface on a one-button device
This is our biggest challenge – there is a metadata line for arbitrary key-value pairs a the start of each track file that could be used to store this data, and adding support for it to the parser and database in the portal would be trivial.
I’m looking forward to seeing your work and hope you keep us updated. If you need help translating content or internationalizing it in other ways (we’re not very consistent with the left-hand/right-hand traffic support across all software parts yet, for example), please reach out.
Regarding the soldering of a sensor, if you have access to the required equipment and a little bit of technical understanding, it is not that hard, we’ve had very good success with complete beginners building the sensor. The biggest hurdle might be that the (rather well developed) building instructions are only available in German, but I guess online translators are good enough by now for that. Borrowing one will be much easier though, hope you find someone to lend you a device
PS: I’ve put your inquiry on the agenda for tomorrow’s community meeting, hopefully that generates enough visibility. You’re welcome to join the meeting, though it is usually held in German and I don’t think everybody speaks English comfortably enough to switch.