Haptics no-power: missed inline switch can fully explain no lights
Confirmed Signal
Ticket 31000 confirms that a customer can report no haptics-kit response and no lights, while the power brick light is on, because they missed the inline button/switch on the haptics power cord.
The support diagnostic asked the customer to verify the inline power switch first. The customer replied: "I figured it out. I didn't see the button on the power cord."
Drafting Rule
For haptics-kit no-power reports where the only visible light is on the power brick, mention the inline power-cord switch early and plainly. Say that the brick light only confirms the adapter has wall power; it does not prove the haptics kit itself is switched on or receiving power.
Keep the next checks in order:
- Inline power switch/button on the haptics power cord.
- 24V plug fully seated in the haptics panel.
- Wiggle test at the panel power socket.
- Internal haptics PCB indicator LED check if the customer is comfortable opening the panel.
Scope
This updates the existing active haptics no-power learning. It does not prove a failed part; it confirms the inline switch is a common enough missed step to keep first in the diagnostic sequence.
Evidence
- Freshdesk ticket 31000 conversation 12382978026: customer confirmed the missed power-cord button/switch.
- Freshdesk private note 12382989749: closure-style acknowledgement draft.
- Existing active learning:
vault/learnings/2026-05-09-haptics-kit-no-power-initial-diagnostics.md.