Skip to main content

Shelly Integration

Automatically switch on and off remote shelly switches depending on booking status

Rabea avatar
Written by Rabea
Updated over 3 weeks ago

With the Shelly integration, you can link booking events from anny to your Shelly switches. Shelly Switches are small, Wi-Fi capable switches (also known as relays) that are installed directly in the power line before a device (for example, a lamp) or behind a light switch.

When is the integration relevant to me?
For example, you run a squash center and want to automate the lighting of individual courts.


Prerequisites

  • Wi-Fi capable Shelly switches (Recommendation: Shelly 1 Gen3)

  • Access to your Shelly account and the Secret Key

  • For every switchable area, it is clear which Shelly switch is responsible (Recommendation: 1 resource = 1 switch).

  • Admin rights in the anny account


How does the integration work?

An event (trigger) from a booking activates an action on the associated Shelly switch.

Example sequence:

  • Customer checks in for "Court 6".

  • The system registers "booking checked in".

  • The "Switch on" command is sent to the Shelly switch for Court 6.

  • Light turns on.

  • When checking out, the light is turned off again.

Supported triggers (events)

  • Booking begins

  • Booking ends

  • Booking checked in

  • Booking checked out

Possible actions

  • Switch on

  • Switch off


Step-by-step setup

  • Connect Shelly (authentication)

  • Go in anny via the avatar to account and open the "Integrations" tab

  • Select the Shelly integration

  • Enter the URL of the Shelly service (with https:// at the beginning)

  • Insert Secret Key from your Shelly account

  • Click "verify authentication" until the connection is shown to be successful

This is what it looks like in your anny environment:

Create rules

  • Add a new rule.

  • Select resource (e.g. Court 6).

  • Set trigger (e.g. "Booking checked in").

  • Select Shelly switch that belongs to this resource.

  • Choose action (e.g. "Switch on").

  • Save the rule.
    For the counter action (e.g. "Booking checked out" → "Switch off") create a second rule.

Activate the integration

  • Activate the entire integration so that rules are executed live.

Test Integration

  • Create a test booking

  • Simulate the chosen trigger (e.g. Check-in)

  • Check if the switch responds

In the booking activity log, check which actions the integration has performed or skipped

Special features

  • Directly consecutive bookings: If booking B follows booking A seamlessly, the system skips the "Switch off" at the end of A. This keeps the light on, for example, without immediately switching it on again.

  • Complete traceability: All actions performed (and potentially skipped) by the integration are documented in the booking activity log.

Did this answer your question?