Home Assistant

Send your OpenCourt bookings to Home Assistant with webhooks, so they can drive lights, HVAC and anything else you automate — with your club keeping control of the automation itself.

Home Assistant is open-source home and building automation that runs on a small box at your venue. It speaks Zigbee, Z-Wave, Matter, Wi-Fi and most things in between, which makes it the usual choice for clubs that want lights, heating, ventilation and everything else on one system they control. With OpenCourt webhooks, your bookings can drive it.

Why it suits a club that runs unstaffed

A venue open 24/7 with nobody on site has the same problem in every room: the building doesn't know when anyone is coming. Lights burn all night or a customer walks into a dark bay. Heating runs for an empty building or the first booking of the day starts cold.

OpenCourt already knows exactly when every space is occupied, because that's the booking calendar — the same information that issues a door code. Home Assistant already knows how to switch anything you've connected to it. The integration is the wire between the two.

Your automations stay yours

The design is deliberate: OpenCourt sends the facts, your Home Assistant decides what happens. OpenCourt tells Home Assistant when a booking is made, changed or canceled, with its spaces and its start and end times. What that triggers is entirely yours to write.

That matters for three reasons:

Home Assistant is better at automation than a booking platform will ever be. You get its full engine, not the handful of toggles we'd have built.
Nothing is locked to us. Your automations are yours, in your config, running on your hardware.
You set the safety margins. How long lights stay on after a booking ends, what happens when someone's still in the building, which circuits are off-limits — those are decisions for the club, not for us.

What clubs ask us for

The kinds of automation this opens up, based on what operators already tell us they want:

Lighting per bay, court or studio, on before arrival and off after the last booking.
Heating and cooling, either through Home Assistant or through our own thermostat control.
Ventilation and extraction in enclosed simulator bays.
Screens, projectors and audio powered down overnight.
Alarm arming once the last booking of the day has ended.

We're not promising any specific one of these — what OpenCourt provides is the booking signal. Which devices respond to it is a question for your Home Assistant setup.

Connect it with webhooks

A webhook is a message OpenCourt sends to an address you choose each time something changes at your club. Home Assistant can receive these through a webhook trigger in an automation.

Ask us to turn on the API section. Webhooks live in the OpenCourt API settings, which are off for a club by default. Email support@getopencourt.com to switch them on.
Create a webhook trigger in Home Assistant and copy its address. The address must use https and be reachable from the internet.
In OpenCourt, go to Settings → API → Webhooks and click Add endpoint.
Paste the address into Endpoint URL. Under Signals to send, select booking.created, booking.updated and booking.canceled. OpenCourt selects the Bookings access they need for you.
Click Add endpoint to save it. The Webhook deliveries panel on the same page shows every message sent, and lets you send a test.

Each message carries the booking's spaces and its start and end times in your club's timezone. Your automation uses those times to schedule what happens — for example, lights on 10 minutes before the start time and off 15 minutes after the end time. When a booking moves or is canceled, a new message arrives so your automation can change or remove what it scheduled.

Without opening your firewall

Home Assistant Cloud (Nabu Casa) can give a webhook trigger a public address that forwards to your local instance — no ports opened, no static IP, no tunnel to maintain. A self-hosted instance with no such address needs to be reachable another way, in the same shape as making a UniFi console reachable. Home Assistant's own documentation covers the webhook trigger settings that allow an outside service to call it.

Or poll the API

A club comfortable with Home Assistant configuration can also read bookings from OpenCourt's read-only REST API. Its schedule endpoint returns every booking with its spaces and start and end times in your club's timezone. The API is in preview, so response shapes can still change — worth knowing before you build something you depend on.

What's next

Today OpenCourt sends a message when a booking is made, changed or canceled — not at the moment a booking starts or ends, so Home Assistant does the timing. We're looking at messages sent at the start and end of a booking, and a simpler setup made for Home Assistant.

Register your interest

Tell us you run Home Assistant and we'll factor your setup into what we build next.

Email support@getopencourt.com, or
Talk to your OpenCourt account representative.

Useful things to mention: whether you run Home Assistant Cloud or self-host, what you'd want a booking to trigger, and whether your venue operates unstaffed.

On this page