When it stops

The words on the cockpit are the diagnosis. Match the badge or the banner to a section below. The fixes are the same facts as the other pages, gathered by symptom.

The chooser never lists the strap

1. The page is https. edgeloop.app is. A file you opened from disk, or a plain http address, is refused before a scan.
2. The browser is Chrome or Edge, or Bluefy on an iPhone or iPad. Bluetooth in the browser is the per-platform permission, including the Linux flag and the Flatpak limitation.
3. Bluetooth is on, and the site is allowed to use it. A previous denial lives behind the lock icon.
4. On Android, Nearby devices was allowed. On older Android, Location was allowed. A denied scan permission opens an empty chooser.
5. The monitor is advertising the Heart Rate service, and nothing else is holding it. Quit the vendor app. Disconnect it in the system Bluetooth list. Then open the chooser again. Make it advertise is the per-device version.
6. A GloryFit or Da Fit watch will never be listed. It does not speak the service. A Garmin strap that is ANT+ only will never be listed either.
7. An Apple Watch broadcast app and Bluefy on the same iPhone cannot see each other. Use a second device, or a chest strap.

"No sensor selected" means the chooser was closed without a pick. "Web Bluetooth is blocked here" means https or the site permission. "Could not connect" means the device was chosen and the connection failed: move closer, and make sure no other app still holds it.

NO SKIN CONTACT

Packets are arriving. They do not contain a usable pulse, or the sensor's own contact flag says it is off the skin. Wet the electrodes. Tighten the strap or the watch band. A number under 35 BPM is treated the same way: ignored, not displayed as a heart rate of zero.

HOLDING LAST READING

The last usable pulse is older than 5 seconds and younger than the signal-loss timeout. Watches and relay apps often update every 2 to 5 seconds, so this badge is normal for them. Leave the timeout at 8 seconds or more. The toys are still moving, on that last number. How often a new number arrives is the full timing.

Motors stopped, session paused

The banner names the device and the reason. The usual heart-rate reasons are: no packets, packets with no pulse, or the Bluetooth link lost after three retries (1 second, 2 seconds, 4 seconds).

Past the timeout, every motor is stopped. With auto-resume on, a good reading starts the session again. With it off, the badge reads that the signal is back and waits for RESUME. The simulator does not count as that signal. If you engage it during a watchdog pause, press RESUME yourself.

Start and Resume refuse to move the toys until a usable reading is younger than the timeout. The transport shows WAITING FOR PULSE instead.

The Handy will not move

• The status line on the Handy card is the error. A wrong key, a sleeping Handy, and an API error are written there. They are not silent.
• The Handy and the browser have to be on a network that can reach HandyFeeling's API. The key is checked against that API.
• The role has to be Primary or Secondary. OFF is connected and still.
• The travel envelope has to be wide enough for a stroke. A sleeve jammed at an end, on a Handy 2 in particular, can look to the firmware like a blocked slider. Raise the end-stop margin, or narrow the envelope so the carriage is not driven into the stop. The default margin is 5 percent.
• If it drops mid-session, the session pauses. Stops keep going out until one is confirmed. Pressing Connect again does not abandon a Handy that might still be moving. It confirms a stop first.

Intiface stays on Connecting

1. Intiface Central is open, and its server is started. The toy is already connected inside Intiface.
2. The address is ws://localhost:12345, with ws://. wss:// is the wrong scheme for a server on the same machine.
3. EdgeLoop and Intiface are on the same machine. localhost is that machine. A tablet running EdgeLoop cannot see Intiface running on a different computer at that address.
4. The toy's role is Primary or Secondary, and you pressed Save & Apply.

An OSSM that stops itself the moment it moves is often Position and Oscillate both enabled. They are one motor. Leave Position on. Connect a toy.

The serial port is missing or busy

• The browser is desktop Chrome or Edge. A phone, a tablet, Firefox, and Safari have no Web Serial, and the card says so.
• Close Intiface, MultiFunPlayer, and any serial monitor that already opened the port. Then press Connect and pick the port again.
• On Linux, the user is in the dialout group, and you have logged out and back in since that was granted.
• Unplugging the device mid-session pauses the session. Plug it back in and connect again. The page does not keep sending strokes at a port that stopped accepting them.

A session feels like it gives up too early

On a max of 140 the toys are supposed to stay up through the middle and give way in the last part of the band, around 126 and above. If they are parking at 120, check the pullback percent. Anything under 100 moves the park down on purpose, and the HOLD TO badge shows the number. Check that both toys are not live on a dual max you set lower than you remember. The DUAL MAX badge is that case.

A watch updating every few seconds will also feel late. The toys move when the notification arrives, on a number that is already a few seconds old. A chest strap is the tighter loop. The comparison is Accuracy.