Compatibility check 1: hub and protocol compatibility
For smart scene buttons, record the exact value, standard, measurement, or supported condition behind hub and protocol compatibility before checkout. A broad category label does not prove that the selected variant fits. Confirm the manufacturer, complete model, hardware revision, electrical rating, protocol, controller support, included parts, and region rather than assuming similarly named products share limits.
Compatibility check 2: single, double, hold, or rotation events
Test single, double, hold, or rotation events across the actual fixture, circuit, controller ecosystem, radio path, owner account, and manual fallback—not a product-photo setup. If this smart scene buttons fit depends on a neutral wire, hub, bridge, account, subscription, compatible controller, professional installation, or reliable cloud service, confirm the exact part, service, or behavior as part of compatibility.
Compatibility checks 3 and 4: battery and mounting; local automation latency and labeling
For smart scene buttons, battery and mounting and local automation latency and labeling are the limiting conditions most likely to surface only after installation. Measure the smallest clearance, weakest connection, least compatible user or device, and the most demanding normal task. Passing an ideal bench test is not enough.
Prove fit in a reversible order
Use this sequence: define one high-frequency action, pair the button near its hub, label each gesture, and test response with internet unavailable when local control is expected. Keep labels, packaging, manuals, and the previous system until the product works through normal use and a recovery test. Photograph wiring, measurements, or assembly states that would be difficult to reconstruct.
A failed fit check is a stop signal
Stop when the button requires cloud latency for an essential action or multiple hidden gestures are harder than a normal wall control. Do not repair a fundamental mismatch with unapproved accessories, copied settings, or community anecdotes. Use app and voice controls when it meets the job with a clearer compatibility path.