EdgeLoop wiki

Pages for the person using EdgeLoop. How to let the browser see Bluetooth, which heart-rate monitors show up, how to put one into a mode the app can hear, and what the page does with a pulse once it has one.

These pages describe 1.1.3, the build on dev.edgeloop.app during this week's testing, and the build that ships to edgeloop.app when that testing is done. The dev site is a separate copy: a monitor paired on one is not paired on the other. If a step here is wrong on your machine, this is the copy to mark up.

Start with the thing that is not connecting

Browser Allow Bluetooth Windows, Mac, Linux, iPhone, iPad, Android phone, Android tablet. Pulse A heart-rate monitor Which devices work, how to make them advertise, and how often they update. Output Connect a toy The Handy, Intiface, a T-Code stroker, the VacuGlide, and what a role means. Session How a session is decided Two climax numbers, the strokes, the goals, and the rules that stop the motors.

What a page will claim

A number on these pages is a number the program uses, or a report from someone who has run the app. The two are labeled differently.

The heart-rate table is the second kind. It is what people have gotten working, including the author's daily setup (a Pixel Watch 2, The Handy on Wi-Fi, EdgeLoop and Intiface Central on a Pixel Tablet). It is not a bench test of every strap on the market. A monitor that advertises the standard Bluetooth Heart Rate service can be tried even if it is missing from the table. One that does not advertise that service cannot, and no setting in the app changes that.

There is no accuracy percentage here for any monitor. EdgeLoop does not have one. Accuracy says what the page actually does with the number it is given, and why a chest strap and a watch steer the toys differently.

Where the program runs

The session is decided in the browser tab. There is no EdgeLoop account and no EdgeLoop server choosing a speed. How a toy is driven is the long version: the clocks, the curve, and the command each kind of toy actually receives.

A partner link is the exception to "nothing leaves the machine." Share Control introduces the two browsers through PeerJS, and the session commands then go from one browser to the other. That path is A partner on another device.

If a page is wrong

Say so in Discord, or open an issue on GitHub. A correction to a device row is welcome with the model, the operating system, and what the browser chooser showed. Product questions go to Discord. security reports stay off the public server: support@edgeloop.app.