The solution, as I understand it, is a little device which talks the protocol of the door opener that gives you fully local access the way it should be.
I'll try and dig out the link now in case it's of use to you.
EDIT: Here you go https://www.home-assistant.io/blog/2023/11/06/removal-of-myq... Hopefully that can point you towards a solution for your opener (and the state of affairs).
I got one for my decade-old not-smart opener around the time the manufacturer was shutting down API access for their fancy new smart models. Works like a dream. Why would anyone want to spend $$$ buying a fancy new cloud-smart appliance when a simple little chip can make the old one local-smart?
I imagine if you're driving into the garage from outside you have a physical button in the car with you to open it, and if you don't run home automation, the "automation" part is likely not very useful.
Yes, ideally the local user should just hit the local hub directly, but it’s double the development effort for negligible benefit.
Said vendors and I have a disagreement about what constitutes acceptable failure modes...
Failing that, I'd settle for manufacturers adding an option in their app of wherever suitable, that will let me change the server URL and leave me to it, I'll reverse engineer then protocol, or if they're feeling generous they can open source or provide an API doc.
Unfortunately, my experience reverse engineering lots of devices over the years is that they're often sharing more than they should, and subsidising the devices they sell you with your data.
There is also an overwhelming number of hardware manufacturers who just have piss poor software with atrocious security who should probably be embarrassed to release their code.
We already know what it's like in home WiFi router world.
This is carefully planned.