Do I need a Nabu Casa subscription?

Yes. CheckYout runs in the cloud and needs a reliable HTTPS URL to your Home Assistant instance – exactly what Nabu Casa provides (~€6.50/month). Self-exposed instances (port forwarding, Cloudflare Tunnel) are not supported because they're too fragile for hosts without networking know-how.

Which entities can CheckYout control through Home Assistant?

Any light entity (light.* domain) and any automation (automation.*) your Home Assistant instance knows – regardless of protocol (Zigbee, Z-Wave, Matter, WiFi, Cloud). The area dropdown only shows areas that actually contain lights.

Does CheckYout change anything in my Home Assistant configuration?

No. CheckYout only calls existing services (light.turn_off, automation.turn_off, automation.turn_on, automation.trigger) – exactly what you'd do from the Home Assistant UI. Your YAML files, entities and custom components stay unchanged.

Is the Long-Lived Access Token secure?

Yes. Tokens are encrypted at rest in the CheckYout database (AES-256-GCM). You can revoke the token any time from your Home Assistant profile – CheckYout immediately loses access.

Where does the HA data go?

CheckYout runs on Vercel + Supabase, both EU/Frankfurt. Token + URL are stored encrypted (AES-256-GCM) in the CheckYout database in Frankfurt. HA service calls go through Nabu Casa Cloud (location per Nabu Casa).

+CheckYout

CheckYout + Home Assistant: check-out triggers your areas and automations.

At check-out CheckYout triggers the actions you pick – lights off, automations paused, and automations actively fired, like a "heating setback" automation for your FRITZ!DECT or Zigbee thermostats. Before the next arrival it heats back up and reactivates everything on its own (PMS sync included). Home Assistant itself is a Pro feature, setup about 5 minutes.

Start for free

For hosts who already run Home Assistant + Nabu Casa. You need HA OS/Container/Supervised ≥ 2024.x, Nabu Casa (~€6.50/mo) and a Long-Lived Access Token. Self-hosted tunnels aren't supported.

Pro · CHF 9.90/month – area selection and pre-arrival auto-resume included.

Lights per area or all at once

In the dashboard you pick the HA area that gets switched off at check-out. For example ground floor only, or the whole apartment. CheckYout reads your Home Assistant area registry for this.

Pause and resume automations

You mark which HA automations should pause at check-out, for example irrigation or motion sensors. CheckYout switches them back on before the next arrival. You need a connected PMS for this.

Heating setback at check-out

Pick an HA automation that CheckYout actively fires at check-out – for example your FRITZ!DECT thermostats down to eco. Before the next arrival a second automation heats back up. For FRITZ!DECT there is a ready-made blueprint to import.

One connection for your whole setup

Instead of setting up a separate integration per smart-home brand, CheckYout just needs the connection to Home Assistant. HA handles the translation to Hue, Shelly, Tuya, Zigbee or Matter.

What CheckYout calls in HA

service: light.turn_off→ at check-out, on the selected area

service: automation.turn_off→ at check-out, per flagged automation

service: automation.turn_on→ 6 h before check-in (PMS trigger)

service: automation.trigger→ at check-out, per chosen action (e.g. heating setback)

service: automation.trigger→ 6 h before check-in, per arrival action (e.g. heating comfort)

What it isn't

This integration is focused on the guest changeover: lights off, automations paused or actively fired (such as heating setback), back up before arrival. A freely programmable webhook on arbitrary CheckYout events runs separately via the Partner API.

Token handling

• AES-256-GCM encrypted at rest in Supabase EU/Frankfurt.
• Revoke in HA → CheckYout loses access immediately.
• Read-only isn't possible (HA limitation); we scope via service whitelist.

How it works

Home Assistant: Profile → Security → “Long-Lived Access Tokens” → create a new token.

Paste the Nabu Casa remote URL (https://<id>.ui.nabu.casa) + token into CheckYout → Settings → Integrations → Home Assistant.

Pick area + automations in the dropdown.

What you need

✓

Home Assistant instance

Home Assistant OS, Container or Supervised, version 2024.x or newer.

✓

Nabu Casa Cloud (about €6.50/month)

Enables remote access. Self-hosted or openly exposed instances are not supported.

✓

Long-Lived Access Token

You create it in the HA profile under Security with one click. The token stays valid until you revoke it.

✓

Connected PMS (optional)

Only needed if you want automations to auto-resume before the next arrival.

What CheckYout controls in HA

Controlled

→ light.* – any light
→ automation.* – any automation

Not directly – only via automations

switch.*, cover.*, climate.*, media_player.*

A CheckYout-triggered automation still reaches them – that is exactly how the heating setback works.

Protocol-independent

Zigbee (ZHA / Z2M), Z-Wave, Matter, Wi-Fi, Cloud – e.g. Hue, IKEA Tradfri/Dirigera, Tuya/Smart Life, Shelly, Aqara, Sonoff.

CheckYout only talks to your HA instance. Home Assistant takes care of translating to each vendor's protocol.

What happens at check-out – and before arrival

07:30 Uhr

Guest scans the QR code while leaving the property

07:30 Uhr

Cleaning team receives a WhatsApp notification instantly

07:30 Uhr

Home Assistant turns off lights, pauses automations

→ On arrival days: automations reactivated 6 h before check-in (requires PMS)

08:00 Uhr

Cleaning team arrives (about 30 min drive)

ca. 10:30 Uhr

Cleaning complete, host is notified

ca. 11:00 Uhr

Cleaning team starts the next job

3 h earlier

→ More properties per day, especially in high season

ab 14:00 Uhr

Next guest can check in

2 h earlier

→ Instead of the default 4 PM check-in

It runs entirely on its own over the season: check-out triggers your areas and automations in Home Assistant – lights, heating, shutters, whatever you’ve set up. One scan, and the whole place flips into turnover mode.

Reactivation requires a connected PMS.

More integrations

Philips Hue

If you only use Hue, the native integration is enough. It skips the Nabu Casa subscription and talks directly to your Bridge.

Explore Philips Hue →

Shelly

With only a few Shellys installed, the direct integration is enough. That way you can skip Home Assistant entirely.

Explore Shelly →

How do I connect Home Assistant with CheckYout?

You need an HA instance (OS, Container or Supervised, version 2024.x or newer), Nabu Casa Cloud (~€6.50/month) for remote access and a Long-Lived Access Token from your HA profile. You enter token and Nabu Casa URL into CheckYout, then pick the area of the property.

Which service calls does CheckYout execute in Home Assistant?

At check-out: light.turn_off on the selected area, automation.turn_off per paused automation and automation.trigger per chosen action (e.g. heating setback). Six hours before check-in: automation.turn_on or automation.trigger for the arrival actions. CheckYout never calls climate.*, switch.* or cover.* directly – those are set by your own HA automation that we fire.

Do I need Nabu Casa for the integration?

Yes. CheckYout only connects via Nabu Casa Cloud – no self-hosted tunnel, no open port forwarding. The subscription (~€6.50/month) is paid directly to Nabu Casa and supports the Home Assistant foundation.

Which Home Assistant versions are supported?

Home Assistant OS, Container and Supervised, from version 2024.x onwards. Older versions may lack service calls or API fields. After an upgrade you don't need to do anything – the Long-Lived Token stays valid.

How is the Long-Lived Access Token stored?

AES-256-GCM encrypted in the CheckYout database in Frankfurt (Supabase EU). You can revoke the token at any time in your HA profile – CheckYout loses access immediately. Read-only isn't possible on the HA side (HA limitation); we scope via a service whitelist.

Frequently Asked Questions

View all FAQs→

Multiple properties? Each connected individually.

Several properties in one Home Assistant instance? Each property gets its own area. At check-out, the service calls (light.turn_off, automation.turn_off) only target entities in the matching area – the neighbouring property stays untouched.

One CheckYout account covers your whole portfolio
Per property, its own area, its own lights, its own automations
Configurations don’t interfere with each other

Five minutes of setup, every check-out automated.

Smart Home add-on, Long-Lived Token, pick an area, done.

Go to dashboard →View all integrations

CheckYout + Home Assistant: check-out triggers your areas and automations.

Lights per area or all at once

Pause and resume automations

Heating setback at check-out

One connection for your whole setup

What CheckYout calls in HA

What it isn't

Token handling

How it works

What you need

What CheckYout controls in HA

What happens at check-out – and before arrival

More integrations

Frequently Asked Questions

Multiple properties? Each connected individually.

Five minutes of setup, every check-out automated.

Further reading

Know other hosts with Home Assistant?