Lovense connection methods
Lovense connection methods explains why Toys can show your devices as online while battery, live local control, or feature lists still look incomplete, and which setups give Pokes the full picture.
The Toys page links here as Why some connections miss battery and features. The same notice can stay after you Accept catalog features (or Accept and submit for review). Accepting features / channels is not the same as a reliable local connection with to your phone, pc, and toy. Sometimes Battery status and Toys-page sliders, holds, and stop still need pokesBridge (or another local delivery path). It all depends on how you are connecting your toys and what info gets sent to Pokes when you add devices.
Problem this solves
Pairing with Lovense Connect or Lovense Remote (QR or code) is enough for many tips and pokes from chat or the Pokes page. That path often does not give live battery from this tab, or some reliable local commands from the Toys page to your phone then toy.
The Toys page shows a notice so you are not guessing:
| Banner | When you see it |
|---|---|
| Not fully connected | Catalog features may still be pending. Tap the notice to confirm catalog features when Pokes asks. Pokes has a custom catalog saved of toys along with their images and feature so we can try to auto-map your toy upon failure. |
| Connection limited | You already accepted catalog features (or they were already known). Subtitle: No Battery Status or Local Commands. |
Accepting catalog features tells Pokes which motors to use on tips and pokes. It does not make browser-to-phone local control reliable. The notice can remain as Connection limited until Bridge (or equivalent local delivery) is connected. Some apps don't send the full features list and battery status for the toys which causes some issues with a few pokes features. On your end it may look like something is just not working but we have been making changes to try to avoid these issues.
What you need
- A Pokes account
- At least one Lovense-compatible toy
- Lovense Remote (preferable) to pair
- Optional: pokesBridge on the same PC and network as your toys app(recommended for battery, local Toys-page control, OSC, Lumia, and Intiface on this PC)
Premium is not required for pairing. Some other Pokes features may still be plan-gated in the app.
How to use
- Open Toys.
- Pair with QR or a pairing code if you have not already.
- If a Not fully connected or Connection limited notice appears, you can still Accept catalog features (or Accept and submit for review on an unknown toy) so pokes and tips use those motors. Battery from this tab and local Toys-page control (sliders, holds, emergency stop) still need pokesBridge.
- Install pokesBridge from Downloads, sign in, and leave it open on this PC.
- Tap Sync toys and confirm battery and local control look complete on the toy card.
For more pairing steps, see Connect Lovense.
Why Connect-only misses some info
Lovense Connect on a phone can tell Pokes that toys exist after QR or Remote pairing without giving this browser a usable local address to the phone amongst other info we need for certain features to work. The Pokes website often cannot receive full info from Lovense Connect on your home network (phone on cellular, different Wi-Fi, VPN, or the browser blocking talk to devices on the LAN).
pokesBridge runs on your PC. Pokes talks to Bridge over the internet; Bridge talks to Connect or Intiface on that machine. The Pokes servers cannot reach your home PC by itself; Bridge can. Battery and capabilities then show up when Lovense actually reports them.
What the Connect-only notice means
The notice has two columns: Still works and Missing without pokesBridge.
The Missing line Reliable local commands from this browser to your phone / toy is about how a command travels, not which motors the toy has (vibrate vs thrust vs rotate).
Not catalog features. After you Accept catalog features (or Accept and submit for review on an unknown toy), Pokes knows which motors to send. That does not make browser-to-phone local commands fully reliable but may get some features working better than they were without it.
Still works without pokesBridge
These usually still work on Connect-only pairing:
- Tips in chat
- Pokes from the Pokes page or bot
- Most timed toy commands the Pokes server fires
Those go: Pokes servers → Lovense cloud → Connect / Remote on the phone → toy. The Pokes website does not need to reach the phone on Wi-Fi in this case.
Reliable local commands from this browser to your phone / toy
The Toys page (sliders, holds, emergency stop, random) prefers talking directly from this browser tab to Lovense Remote or Connect on the phone or PC (home network or this same computer). That often fails because:
- The Pokes website cannot reliably reach the Lovense App on the phone (different network, phone on cellular, VPN, or the browser blocking talk to devices on the home network)
- QR / Remote pairing often has no usable local address for the site
When that local path fails, the Toys page falls back to cloud. The toy can still move, but:
- Holds (keeping a slider on) are not a true local keep-alive; cloud uses short pulses (about 8 seconds) instead of a continuous local command
- Stop / emergency stop can feel late due to latency on the networks
- Multi-feature holds (vibe + thrust together) are more likely to feel wrong on the cloud fallback since they may stop and start at times.
- Live battery from this tab uses the same blocked local path (that is the other Missing line: Battery status)
What pokesBridge changes
pokesBridge is the desktop app on your PC. Pokes talks to Bridge over the internet; Bridge talks to Connect or Intiface on the local machine. The Pokes cloud cannot reach this PC on its own; Bridge can. You also need Bridge for OSC, Lumia, and Intiface on this PC.
| You do this | Without pokesBridge | With pokesBridge |
|---|---|---|
| Tip / poke from chat or Pokes | Usually fine (cloud) | Fine, often local too |
| Toys page slider / hold / stop | Cloud fallback; holds are pulsed; local path often blocked | Local commands; true holds |
| OSC, Lumia, Intiface on this PC | Cloud cannot reach this PC | Bridge runs it locally |
Connection comparison
| Connection | Toy list / online | Battery | Feature list | Local / LAN commands |
|---|---|---|---|---|
| Lovense Connect or Remote only (QR or code, no Bridge) | Usually yes | Usually no from this tab | Catalog accept can fill motors for pokes; live local list still limited | Cloud pokes and tips usually yes; browser-to-phone local often no |
| Connect on phone + Pokes in the browser (same Wi-Fi, no Bridge) | Yes after pair / sync | Only if this tab can reach Connect (often blocked) | Same as battery | Unreliable from the website |
| Lovense Connect desktop + pokesBridge on this PC | Yes | Yes when Connect reports it | Yes when Connect reports it | Yes, via Bridge |
| pokesBridge + Intiface Central | Yes when Intiface shows the toy | Depends on the device and Intiface | Depends on the device | Yes, via Bridge |
| Chrome extension | Not shipping yet | Planned with local toy info | Planned | Planned |
Recommended for streaming: pokesBridge open on the PC that has Lovense Remote, Connect or Intiface, plus Toys synced in the Pokes dashboard.
Useful settings
| Setting | What it does |
|---|---|
| Sync toys | Refresh the list Pokes stored from Lovense / Bridge |
| Accept catalog features | Tells Pokes which motors to use on tips and pokes; does not unlock local Toys-page commands |
| Edit saved features | In the same notice, change name or motors after a wrong Accept; saves on this toy only |
| pokesBridge status | Confirms the desktop app is signed in and delivering local toy data and commands |
| Disconnect toys | Clears the Pokes link so you can pair again |
How to test
- Pair with QR only. Confirm toys are online and the incomplete-connection notice appears (Not fully connected if catalog features are still pending, or Connection limited / No Battery Status or Local Commands after you accept).
- Accept catalog features if Pokes asks. The notice does not always hide. It may change to Connection limited. Open it and use Saved on this toy if you need to change the name or motors. It hides when pokesBridge (or equivalent local delivery) is connected, not merely when catalog features are accepted.
- Install pokesBridge, sign in, leave it open, then sync. Confirm the notice hides and battery plus local sliders / holds behave as a continuous command, not short pulses.
- Send a low-intensity poke to yourself on Pokes.
Related pages
| Page | Purpose |
|---|---|
| Connect Lovense | QR and pairing code |
| Sync Toys | Refresh the toy list |
| Toy Status and Battery | How online and battery appear |
| What is pokesBridge | Desktop app setup |
| pokesBridge and Intiface | Non-Lovense toys via Intiface |
Troubleshooting
- Sliders or holds feel pulsed, or stop / emergency stop feels late: you are on Connect-only cloud fallback. Install pokesBridge rather than re-pairing in a loop.
- Notice stays as Connection limited after you accepted catalog features: expected until Bridge (or equivalent local delivery) is connected.
- Notice stays up after Bridge is open: confirm Bridge is connected, Lovense Connect is running on that PC, then Sync toys.
- Toys online but sliders feel limited: you are on Connect-only; install Bridge.
- Still stuck: Lovense Troubleshooting or Discord support: https://discord.gg/XBt3UJReF2