Controller Vibration Not Working
An unfelt browser command can come from support, targeting, connection, settings, battery, firmware, or hardware. Check the output path before drawing a conclusion.
Evidence-first troubleshooting / updated July 14, 2026
What the browser result means
The tester first uses the selected Gamepad session's standard actuator. A separately paired supported Sony WebHID target is used only after explicit association and only as fallback. The final result combines command acceptance with your subjective confirmation and is excluded from hardware-health scoring.
Safe decision path
- 1
Confirm the selected controller
With multiple controllers connected, verify the active session and explicitly associate any separately paired WebHID output target.
- 2
Check browser support
A controller may expose input without exposing a standard haptic actuator. WebHID support is browser and model specific and remains optional.
- 3
Check battery and connection
Charge the controller, reconnect it, and compare USB with wireless. Stop other tools that may own or remap controller output.
- 4
Check game and platform settings
Confirm vibration is enabled in the game, operating system, Steam Input, console profile, and official controller app.
- 5
Update firmware and retest once
Apply official firmware updates, power-cycle the controller, and rerun one bounded command. Avoid overlapping rumble tests.
- 6
Compare outside the browser
Use an official app, console game, or known working title. If vibration fails everywhere, check warranty or service options.
Verification standard
A browser command that is accepted but not felt is not enough to identify a failed motor. Confirm the correct target and reproduce the symptom in an independent, supported environment.
Before advanced work
Motor replacement requires model-specific teardown, battery isolation, cable handling, and sometimes soldering. Review warranty and official service before opening a controller.
Common questions
Does input support guarantee vibration support?
No. Browsers can expose Gamepad input without exposing a haptic actuator.
Why must a WebHID controller be associated?
The browser cannot prove that a paired HID device and a Gamepad slot are the same physical controller, especially when several are connected.
Does not feeling the test prove a bad motor?
No. Confirm targeting, support, battery, settings, firmware, and behavior outside the browser first.