Commonly the left-side motor
Strong / low-frequency channel
Requests only strongMagnitude. On a traditional dual-rumble controller this is usually the heavier, lower-frequency motor, but the browser or device may transform the effect.
Send separate strong and weak dual-rumble commands, then record whether you actually felt each response. The result is an observation—not an automatic motor-health verdict.
Commonly the left-side motor
Requests only strongMagnitude. On a traditional dual-rumble controller this is usually the heavier, lower-frequency motor, but the browser or device may transform the effect.
Commonly the right-side motor
Requests only weakMagnitude. On a traditional dual-rumble controller this is usually the lighter, higher-frequency motor. Modern haptics may not map to a distinct side.
Test both channels and record whether you felt each one.
Compatibility first
The browser can report that a command completed without measuring the physical movement in your hands. Your confirmation is part of the test.
Connect the controller, press a button and keep this page visible. Haptic commands can be rejected when the document is hidden or when the browser does not support the requested effect.
If a channel is not felt over Bluetooth, repeat with a direct data-capable USB cable. Then verify vibration in a native game or the controller manufacturer's software.
The web API exposes strong low-frequency and weak high-frequency magnitudes. That commonly corresponds to two handle motors, but modern devices and browser mappings may render the effect differently.
DualSense waveforms, adaptive triggers, speaker output and platform-specific effects are not equivalent to the standard dual-rumble command tested here.
Interpret carefully
No. It sends separate browser commands and asks you to confirm what you felt. A missing sensation can come from browser support, operating-system mapping, firmware, connection mode or hardware. Confirm the result in a native game or manufacturer tool before diagnosing a motor fault.
Gamepad input and haptics are separate browser capabilities. Your browser may expose buttons and axes without exposing a compatible vibration actuator. Keep the tab visible, try a direct USB connection and compare a current Chromium-based desktop browser.
Not always. Traditional dual-rumble controllers commonly use a heavier low-frequency motor on one side and a lighter high-frequency motor on the other. Browsers and modern haptic devices may transform those channels, so the page labels both the API channel and the common physical arrangement.