Note: I’m not a software/hardware engineer, so this report was put together with the help of Claude based on my logs and troubleshooting. Apologies if any of the technical framing is off — happy to clarify or test anything.
Summary
Lelo F1s V3 is detected, connects, completes the security tap authorisation, and is correctly identified by name as “Lelo F1s V3” in Intiface Central. However, moving either of the two vibration sliders in the Devices tab produces no response from the device. Commands appear to be sent (visible in log as write-without-response fallback to write-with-response), but the motors do not activate. Device is fully charged and works normally with the official Lelo app when connected on iOS.
The log shows the device is being handled by the lelo-f1sv2 protocol with identifier F1SV3, suggesting V3 detection is in place but the V2 command protocol may not be fully compatible with V3 hardware.
Environment
- Intiface Central version: 3.0.4+40
- Device config version: 4.197
- OS: macOS Taho 26.5
- Hardware: MacBook Pro 14" M2
- Device: Lelo F1s V3, fully charged
- Bluetooth: System Bluetooth on, Intiface granted Bluetooth permission in System Settings → Privacy & Security
Steps to reproduce
- Quit Lelo mobile app fully (force quit)
- Power on F1s V3
- Start Intiface Central server
- Start scanning in Devices tab
- Device appears in log, prompts for power button tap
- Tap power button on device — authorisation completes, device added as “Lelo F1s V3”
- Move either vibration slider in the Devices tab
Expected: Device vibrates in response to slider position.
Actual: No vibration. Device remains connected. Log shows write-with-response fallback warnings at the moment the slider is moved, but no error and no device response.
Already ruled out
- Battery (fully charged)
- Lelo app interference (force quit before scanning)
- Reconnecting from scratch (toy fully off, then on, fresh scan, re-authorise)
- Both feature indices (index 0 and index 1 sliders) tested at multiple intensities including 100%
- System Bluetooth and Intiface Bluetooth permission confirmed working (device connects)
- No other Bluetooth hosts connected to the F1s V3
Relevant log excerpt
26.687 Lelo F1s V2 isn't authorised: Tap the device's power button to complete connection.
[... repeated authorisation prompts ...]
28.298 Device map does not contain key 0.
28.298 Assigning index 0 to Lelo F1s V3
28.299 Updating device Lelo F1s V3 index to 0
28.299 Device connected: Lelo F1s V3
28.299 Device Added: 0 - Lelo F1s V3 - UserDeviceIdentifier { protocol: "lelo-f1sv2", identifier: Some("F1SV3"), address: "PeripheralId(eb1036f6-da6e-b74e-057e-82d037d1caeb)" }
28.299 ServerDeviceDefinition { name: "Lelo F1s V3", ... features: {0: ServerDeviceFeature { ... vibrate: Some(...) }, 1: ServerDeviceFeature { ... vibrate: Some(...) }} }
32.463 BTLEPlug device doesn't support write-without-response! Falling back to write-with-response!
33.322 BTLEPlug device doesn't support write-without-response! Falling back to write-with-response!
The two write-with-response warnings at 32.463 and 33.322 correspond directly to slider movements. No errors are logged after the writes.
Hypothesis
V3 hardware appears to be detected (correct device name and identifier F1SV3) but routed through the lelo-f1sv2 protocol handler. If the V3 uses a different command format or characteristic structure than the V2, writes would succeed at the BLE layer (hence no error) but the device would silently ignore them. This would match the observed behaviour.