The answer first
Before troubleshooting, separate an unsupported native connection from a supported intermediary and a retired integration.
Choose the case that matches yours
The five-minute tutorial audit
Find the publication or update date. Identify the exact app, hardware, account type and country. Look for a current official setup link. Read the promised action: status, close and open are not synonyms. Stop if the recipe depends on impersonating another app or defeating authentication.
If an old automation stopped working
Home Assistant announced removal of its myQ integration in December 2023 after third-party access restrictions. Re-entering credentials into obsolete recipes is not a documented restoration path. Do not disable account protections to make a tutorial succeed.
Match the fallback to the job
For everyday garage control, the consumer app supports compatible devices. For an automation, inspect the IFTTT guide. For a building entrance, check Community. If you need a different ecosystem’s native features, first record the exact opener model and required capability; this page does not recommend replacement hardware without model-specific research.
A useful fault report
Record what still works, the last successful date, the integration’s name and the exact error. Separate account sign-in failure from an offline opener. That evidence is more useful than repeated resets or installing a similarly named unofficial app.
Questions before you continue
Common questions
Is Amazon Key the same as Alexa garage control?
No. Do not transfer a capability between distinct services merely because both use Amazon branding.
Can I fix this by adding Matter or Thread?
The current consumer index does not support those connections; a protocol label is not a compatibility upgrade.