Anyone figured out how to keep data smooth when switching sensors during indoor rides?

Hi everyone! I’ve recently been mixing up my indoor cycling routine with a smart trainer, and I’ve run into a bit of a puzzle I hope someone here can help with. During some sessions, I like to switch focus—sometimes I rely on my chest-strap heart rate monitor, other times I go with a cadence sensor on the crank arm. This switch usually happens mid-ride depending on how I’m feeling or the training target. What’s odd is that while the web tool does record both sensors well, the moment I switch, it kind of “splits” the ride in a strange way. The heart rate data might show a sudden drop-off and restart, or the cadence chart looks broken up even though I didn’t stop pedaling.

It’s not that the tool isn’t doing its job—it definitely is—but I feel like the post-ride graphs don’t tell the full story when sensor changes happen in-session. Has anyone figured out how to keep the ride data more continuous even when switching sensors on the fly? I don’t mean syncing them manually later—I’m wondering if there’s a way to handle it better while riding.

I’ve been pairing both sensors at the start, hoping the tool would “smooth” the transition, but I’m not sure if that’s how it works. I don’t see an option in the settings that helps with this, but maybe I missed something? If any of you regularly ride with more than one sensor type, do you follow a process to avoid these tracking gaps?

At one point, I got inspired by how a cycling tracker I used outdoors managed changes really cleanly. A cycling tracker, for those who are newer to it, is a tool that records real-time data while you ride—like distance, speed, elevation, and heart rate—and it often syncs automatically with your training log. One of my favorite features is the cycling mileage calculator, which shows total distance tracked across rides. That feature really motivated me to keep consistent records, and it made me realize how important seamless data collection is when it comes to seeing real progress.

I’m curious—has anyone figured out a user-level solution for this kind of mid-ride sensor swap? Maybe a setting you always enable, or a way to keep both sensors live so the transition is invisible? Or even just a smart routine to follow when changing sensors manually? I’m trying to make sure the effort I put in shows up accurately in my logs, and this little hiccup has been throwing things off more than I expected.

Let me know if you’ve run into this and how you deal with it!