GSM, SUPLA or HTTP/HTTPS — how should a gate be controlled?
Location automation answers “when”, while the control method answers “how” the command reaches the gate.
Updated:
In short
The right method depends on the existing controller. Gate Auto Open can trigger the saved method after route conditions are met, but it does not replace the controller that drives the gate.
Terms used in the app
- Opening method
- The channel used to send a command to the existing gate controller. Location logic decides when; the opening method decides how.
- Gate
- The gate point and its saved control method: GSM phone call, SUPLA direct link or another HTTP/HTTPS link.
- Phone readiness
- A panel that checks background location, Bluetooth, notifications and battery settings required by the selected setup.
One drive logic, three ways to send the command
GPS wake-ups, Opening zones, Bluetooth and Wi‑Fi decide whether this is the correct moment. Only then does Gate Auto Open trigger the method stored at the Gate point. You can therefore change from GSM to SUPLA or a webhook without rebuilding the complete route configuration.
GSM — call the gate module
This is suitable for gate modules that recognise the caller number. Enter the international number and the app initiates the call when the automation conditions are met. It is simple and does not require the gate module to use home internet.
Where the controller offers different inputs, a dedicated OPEN action is more predictable than a step input that cycles OPEN/STOP/CLOSE.
SUPLA — direct link
Create a direct link to the gate channel in SUPLA Cloud and paste it into Gate Auto Open. The app expects the secure direct-link format. If SUPLA lets you expose only the Open action, that is more predictable than a link that toggles multiple states.
The full URL is effectively a digital key. Keep it private and do not include it in public screenshots or support messages.
HTTP/HTTPS — webhook or your own controller
Other internet link can be used with Home Assistant, a custom API or a controller that exposes a URL. Select GET, POST or Automatic. Automatic uses POST for recognised Home Assistant links and GET for other links; it does not try a second method afterwards, avoiding duplicate commands.
Use HTTPS for internet-facing systems. Plain HTTP should be limited to a deliberately controlled local/test environment.
How to choose
The best method is the one your existing controller supports reliably, not necessarily the most complex one. Test the command manually at the Gate screen first. If the motor does not react to a manual command, fix the control channel before changing GPS or zone settings.
Key points
- Use GSM for a module that reacts to calls from authorised numbers.
- Use SUPLA when the controller provides a SUPLA Cloud direct link.
- Use HTTP/HTTPS for webhooks, Home Assistant or your own API.
- Prefer HTTPS and keep private tokens/URLs secret.
- Test the command manually before combining it with automatic zones.
Common questions
Can I switch from GSM to SUPLA later?
Yes. The opening method is separate from the location logic, so the route does not need to be rebuilt.
Is plain HTTP supported?
Yes, but HTTPS is safer for anything reachable over the internet. Use HTTP only in a controlled environment.
Does Home Assistant need POST?
Many Home Assistant webhook-style links use POST. Automatic mode recognises such links, and GET/POST can also be selected manually.
Does SUPLA require home Wi‑Fi on the phone?
No. A SUPLA Cloud direct link can be called over 4G/5G when the phone has internet access.
Will Automatic mode try both GET and POST?
No. It chooses one method and does not retry with the other, reducing the risk of sending two opening commands.
Want to configure this in Gate Auto Open?
See the setup guide for zones, car Bluetooth and your gate opening method.
Open configuration guide