Toy remapping when you connect a new device
When you swap toys mid-stream (in this example, let's say you first connect Lovense Gravity during setup, then change to Lush mid-stream), Pokes tries to keep your saved settings working without making you re-pick every toy in every menu.
This page explains what updates automatically, how channels / features (Vibrate, Thrusting, and so on) are handled, and where to look if something still does not fire.
What toy remapping does
After you sync toys, Pokes compares the list your toy connection app reports now vs what you had before. When Pokes knows you've switched to a different device, it replaces saved toy rules IDs in the background so rules and mini-games point at the toy that is online now.
Remapping can update:
- Tip rules (including command maps)
- Wheel Spin Gamba segments and wheel toy list
- Dice Gamba rows and dice profiles
- Control link toy picks
- Overlay / OSC rules that affect toys
Your intensity, duration, and feature choices (for example Vibrate 12 for 30 seconds) are kept when possible. Pokes then attempts to only sends commands the new toy actually supports.
When the new toy has different motors than the old one, Pokes also tries to match your saved feature to the closest channel on the new toy (for example Thrusting on Gravity → Vibrate on Lush) so tips and minigames can keep firing after Sync toys. You should not need to open every rule after a toy swap; see How channels and features are handled below.
When remapping runs
Remapping happens during Sync toys on /toys (or when Pokes refreshes toys from Lovense after connect). It does not generally require opening mini-games or other Tip Rules to update unless something isn't working as it should.
Typical cases:
| Situation | What Pokes tries to do |
|---|---|
| You had one toy online, then connect a different toy (only the new one online) | Move saved picks from the old toy to the new one |
| You re-pair the same model (for example a new Lush ID after factory reset) | Match same toy type, one old + one new, and move settings to the new ID |
| Several toys online at once | Only remap when the pairing is unambiguous (see limits below) |
If you only wear one toy at a time while live, remapping is designed for exactly that: turn off the old toy, connect the new one, sync, and keep going without editing every rule and overlay to display the new toys' info and features.
How channels and features are handled
Toys expose different feature that Pokes, at times, will handle as channels (motors / modes). Gravity might have Vibrate and Thrusting; Lush might only have Vibrate.
When settings move to a simpler toy:
| What you saved | On a toy with fewer features |
|---|---|
| Vibrate only | Works as before. New toy will vibrate |
| Vibrate + Thrusting on one tip rule | Vibrate still runs; Thrusting is skipped (not sent) when new toy only has one feature but your rule has two saved on another toy |
| Per-toy map with both channels | Only supported channels run |
| Wheel / dice row set to Thrusting only | Pokes maps it to the new toy's first channel when possible (Vibrate on Lush in this example). Intensity and duration stay the same |
| Command strings that list multiple motors | Unsupported motors are dropped and ignored; each slot maps to the same channel index on the new toy when it exists |
Pokes will not force / send Thrusting commands on a Vibrate-only Lush. If a rule was only Thrusting on Gravity, command sent tries to run that reward on Vibrate (or the new toy's first feature available) instead of failing silently. You only need to edit the tip rules if you want a different command sent than whats automatically mapped.
What updates on sync vs at tip time
| When | What happens |
|---|---|
| Sync toys (toy swap) | Saved toy IDs in your current rules get swapped to use the new online device. Tip rules, wheel, and dice settings also get features updated when the new toy uses different feature names. Thrusting->Vibrate |
| Tipped | Pokes checks toy capabilities before sending, as a safety net if sync did not run yet |
How profiles work
Profiles will allow you to setup rule profiles that can save all your settings in the section (ie. on page overlays>wheelspin). After saving your profile and connecting a new toy, Pokes will keep you profile settings as you saved them unless you make changes and overwrite your current profile with the new settings. In the case that you would like to keep your old profile as it is, create a new profile before making any changes and new updates will affect the newly selected profile you just created.
You may see a notice on Toys after sync when toy IDs or features were adjusted (for example how many Thrusting rows now use Vibrate). You do not have to act on it for tips to work. This is a new feature i'm adding to make it more apparent of what's changed in case you need to make any adjustments.
You do not need a separate profile per toy for remapping to work. Many creators keep one live setup and swap devices mid-stream.
If you want different rules per toy (for example a Gravity wheel and a Lush wheel with different results/prizes), duplicate or create a Wheel Spin or Dice Gamba profile and switch to it before you change toys. Auto-adapt on sync targets your current live config; it does not replace manual profile switching for creators who prefer separate presets. If you've first duplicated or created new profile, any updated you make will save to the new profile in the case you may forget to switch before making changes.
What does not change automatically
- Rules with no toy picked (all online toys): still follow "whatever is online"; remapping mainly helps when you saved a specific toy command to a rule.
- A second device of the same type (for example a second Lush while your first Lush stays connected): existing rules stay on the first lush. The new lush is treated as a separate toy; add tip rules, wheel rows, or dice picks for it yourself. Pokes treats this as a new device as any other. You would need to add the commands you want in each rule for this new toy.
- Replacing one lush with another (old lush drops off Lovense app, new lush ID appears after sync): saved rules for the old Lush move to that new Lush.
- Two lush online, stale rule still points at an offline lush ID with no clear replacement: Pokes does not guess between them. Run Sync toys after a swap, or pick the toy in the rules.
- Inactive wheel or dice profiles stay on the feature names you saved until you activate that profile or open it with new toys connected.
- After sync on an toy swap, settings should already show the new adapted feature (for example Vibrate instead of Thrusting on Lush). If a label still looks wrong, open that editor once and save, or run Sync toys again with only the new toy.
Where to check settings if something is wrong
Work through these in order:
1. Toys page (/toys)
- Sync toys after swap.
- Confirm the toy you are wearing is online and enabled in Pokes (not dimmed out) and active on the Lovense App.
- Use toy panel to confirm commands are reaching your before checking rules and other settings.
2. Tip rules (/tip-settings or Tip Rules in the dashboard)
- Open the rule that should fire.
- If you use per-toy commands, check that the toy list matches the device online now.
- If the rule targets all toys, confirm at least one eligible toy is online.
3. Wheel Spin (/overlays/wheelspin)
- After Sync toys, your active wheel profile should already point at the online toy with new adapted features. Open the settings if you want to double-check or rename segments.
- Segments with a missing or offline toy can be updated to your current toy (the editor can apply the online toy to those rows).
- Check each prize row: toy, feature (Vibrate vs Thrusting), intensity, and duration to make sure they are set as needed.
See Wheel Spin.
4. Dice Gamba (/overlays/dice-gamba)
- Your active dice profile should update on sync like tip rules and wheel. Review profile toy rosters and each row's toy and feature if something still looks off.
- Rows pointing at a removed toy ID may need a toy re-selected if sync did not remap (for example multiple toys were online).
See Dice Gamba.
5. Control links and pokes
- Control links: Creators should recreate or edit if the ctrl link was set for a toy that is now offline.
- Pokes (
/pokes): confirm the target creator's toy is online if you are sending to someone else.
6. Connection path
- pokesBridge or Lovense App path must be healthy; remapping does not fix a Lovense toy offline error.
- See Toy not responding and Lovense troubleshooting.
Quick test after swapping toys
- Connect the toys you will use while live.
- Sync toys on
/toys. - Test on the toy panel by moving the pall or use Pokes page to send yourself a test poke.
- Run a test tip or your wheel/dice test.
- If one path works (toy test) but tips do not, check tip rules vs minigame separately.
Related pages
| Page | Purpose |
|---|---|
| Sync toys | Refresh the list from Lovense (triggers remapping) |
| Test a toy | Confirm the device path before going live |
| Tip rules | Amount-based toy commands |
| Wheel Spin | Per-segment toy and feature |
| Dice Gamba | Dice profile toys and row features |
| Toy not responding | Connection and sync checklist |