PalGate Cloud
At a glance
Section titled “At a glance”- Product: PalGate
- Manufacturer: PAL Electronics Systems
- Similar open-source integrations:
- Home Assistant has many gate/relay integrations; use the one that matches your hardware and/or protocol.
Getting started
Section titled “Getting started”Dashboard (recommended)
Section titled “Dashboard (recommended)”- In Integrations, create a new integration and choose provider type PalGate Cloud.
- Follow the setup wizard: enter the PalGate device id (and optional name), then scan the QR code with the PalGate app under Linked devices → Link a device. The dashboard polls the server until linking completes and fills session token, phone number, and token type automatically.
- If you cannot use QR linking, use Enter credentials manually in the wizard to paste values (same fields as below).
- For each gate you want in OpenApp, create a device on that integration. Set PalGate gate ID (stored as
external_id) to the PalGate device id string the API expects (for exampleDEVICEorDEVICE:2for a second output). Metadata is not used for opening gates. From the wizard review step you can open Devices with device id/name prefilled via query params. - Trigger an OpenApp “open” action and confirm the gate opens.
Manual / API-only
Section titled “Manual / API-only”- Create an integration with provider type
palgate_cloudand set the config and secrets fields in the table below (or viaPOST /integrationswithconfig+secrets). - Continue from step 4 above.
Integration-setup API (device linking)
Section titled “Integration-setup API (device linking)”For custom clients or automation, the same linking flow the wizard uses is available over HTTP (same auth as integrations; X-Org must match the org):
POST /api/v1/integration-setup/v1/sessions— body:{ "flow": "palgate_cloud_device_link", "org_id": "<uuid>", "options": { "base_url": "..." } }(optionalbase_url). Returnssession_idand a step payload withpalgate_cloud_device_link.qr_payload(and linking metadata).POST /api/v1/integration-setup/v1/sessions/{session_id}/poll— call repeatedly (e.g. every 1–2s). Responses:awaiting_scan,succeeded(includesconfig+secretsfor the integration), orfailed. Sessions expire after a short TTL (~15 minutes).
Use the returned config and secrets on POST /integrations to create the integration.
Setup reference
Section titled “Setup reference”| Field | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
| base_url | string | optional | Base URL for the PalGate API. | https://api1.pal-es.com | https://api1.pal-es.com |
| session_token_hex Stored securely in Secrets Manager | string | required | Session token (hex) used to authenticate to PalGate Cloud. | — | 0a1b2c3d4e5f... |
| phone_number | number | required | Phone number associated with the PalGate account. | — | 15551234567 |
| token_type | string | required | Token type string: sms, primary, or secondary. | — | primary |