Why some toys need the Lovense app
ToyControl sometimes asks you to set a toy up in the maker's own app first. Here is why, and why it is a one-time step.
When you pair certain toys, ToyControl may point you to the maker's own app to finish setup first. This surprises people who expected ToyControl to do everything. Here is what is going on.
A one-time setup step
Some toys ship needing a first-run setup that only the maker's app can do: a firmware update, or an initial registration that prepares the toy to be driven. Lovense toys are the most common example, which is why this comes up as "the Lovense app".
This is a one-time step. Once the toy has had its first-run setup, ToyControl drives it normally and you do not need the maker's app open during sessions.
Why ToyControl cannot always do it
A firmware update or a registration is specific to the maker's own systems. ToyControl drives toys, it does not impersonate each maker's setup and update servers. Doing the one-time setup in the maker's app, then everything else in ToyControl, is the clean split.
Maker-only features
A few features stay in the maker's app on purpose: sound-activated modes, the maker's own pattern libraries, certain cloud features. ToyControl focuses on funscripts, VR, patterns, Broadcast, Music sync, and remote control. If you specifically want a maker-only feature, use that app for it; the toy can be paired with either at different times.
Not a fault
None of this means the toy is half-supported. It is normal for connected hardware to have a first-run setup. After it, the toy is fully yours to drive from ToyControl. See Lovense toys with ToyControl.
Disclosure
ToyControl earns a commission when you buy through links in this article. We only recommend products we have tested or that the community consistently confirms work with ToyControl. Our recommendations are not affected by commission rates. If a product we link to does not work as described, use the Report a bug button in the app and we will revise the article.