Came Connect

Share your Projects!
1

Hi everyone,

I’ve built a small Home Assistant add-on that works as a local REST proxy for Came Connect.
It handles login to the Came Connect cloud, token refresh, and exposes your gate with simple REST endpoints inside your HA network.

With it you can:

  • Check normalized gate status (open, closed, opening, closing, stopped, unknown)
  • Execute commands like Open, Close, Stop, Partial opening, Sequential, etc.
  • Inspect and debug your authentication token

Installation

  1. Go to Settings → Add-ons → Add-on Store
  2. Click the ⋮ menu → Repositories
  3. Add the repository:
  1. Install Came Connect from the list.
  2. Fill in the configuration with:
  • client_id and client_secret (from the Came web app, see README for how to find them)
  • your Came Connect username and password
  • your device ID (from the Came Connect portal URL)

Example endpoints

  • Health check → http://homeassistant:9002/health
  • Gate status → http://homeassistant:9002/devices/DEVICE-ID/status
  • Open → http://homeassistant:9002/devices/DEVICE-ID/command/2
  • Close → http://homeassistant:9002/devices/DEVICE-ID/command/5
  • Stop → http://homeassistant:9002/devices/DEVICE-ID/command/129

Home Assistant integration

You can expose the commands in HA using rest_command entries. Example:

rest_command:
  came_open:
    url: "http://homeassistant:9002/devices/DEVICE-ID/command/2"
    method: POST

Or create a template cover that maps status + commands for a full gate entity.

 
 
My configuration: HASSIO installed on Raspberry Pi 4
 
The addon code was written with extensive help from ChatGPT and based on the great work of jasonmadigan (https://github.com/jasonmadigan/came-connect).

1 Like
2

Hello,
Thanks a lot for your project which interess probably lot of peaple like me !

I’ve config my installation in HA but when I want to change the Redirect URI and when i clic on the cog icon i have this message :“500 Internal Server Error Server got itself in trouble”.

For information I use CAME Connect for the connection to come connect

Do you know why ?
Cheers
Guillaume

3

Hi Guillaume,

thanks a lot for the feedback!

You don’t need to change the Redirect URI for this add-on. The OAuth flow uses a fixed redirect (CAME Connect) that is pre-registered for the official CAME client. If you try to edit it (via the cog icon), the CAME side will reject it and that’s why you see the “500 Internal Server Error”.

Please leave the Redirect URI as is and only set these environment variables in the add-on:

CAME_CONNECT_CLIENT_ID, CAME_CONNECT_CLIENT_SECRET, CAME_CONNECT_USERNAME, CAME_CONNECT_PASSWORD.

After saving and restarting the add-on, check /health and then /devices/<your_device_id>/status.

If authentication still fails, delete /data/token.json, restart, and look for any 401 in the logs (the add-on will automatically retry).

Cheers!

4

Greetings people,

I followed all instructions and now I can control my door gate with cameconnect on HA. I had previously added Came Connect on Google Home. But commands are limited to opening and closing.

I have ZN7 and Came Gateway 806sa-0140 WIFI

Many Thanks

5

Thanks to you for the feedback!