Shelly has become a leading name in Wi-Fi and multi-protocol smart relays, sensors, and actuators for both home and building automation, but the real magic happens inside the Shelly Smart Control app. Powerful hardware is only part of the story; it is the app that ties devices, data, and automation together into something that feels genuinely smart and reliable in day to day use.
This guide is based on a real webinar walkthrough of the Shelly ecosystem and is designed to help you get practical, deployment ready value from the Shelly Smart Control app. We will look at how different generations of Shelly devices behave in the app, how to combine local and cloud control, and how to turn individual relays and sensors into complete automation scenarios.
In the sections that follow, you will learn:
- How Shelly device generations and colour coding affect features and compatibility
- The key differences between local control and cloud control in the Shelly ecosystem
- How to configure device settings, scenes, and groups for real world use cases
- How to work with Shelly sensors, energy monitoring, and installer focused tools
Understanding Shelly Device Generations and Why They Matter
Shelly Gen 1 to Gen 4 at a glance
When you compare Shelly Gen 1 vs Gen 2 vs Gen 3 vs Gen 4, you are not just looking at minor revisions. Each generation introduces new connectivity options and capabilities that directly affect what you can do in the Shelly Smart Control app and how you design your automation projects.
Gen 1 (2017–2020) devices formed the original Shelly portfolio. They relied on Wi-Fi and MQTT only and are now discontinued. They remain very capable for basic automations but lack newer features and integrations.
Gen 2 introduces Bluetooth alongside Wi-Fi and MQTT. This makes pairing easier, speeds up commissioning in the field, and improves integration with other Shelly devices that depend on Bluetooth.
Gen 3 builds on this with wider protocol support and a stronger platform for automation. It is designed to handle more complex scenarios, larger installations, and more advanced software features.
Gen 4 brings true multi connectivity with Matter and Zigbee on top of Wi-Fi and Bluetooth. This makes Shelly far more flexible in mixed ecosystems where you need to work with different smart home platforms and standards.
The generation of a device matters in the app because it directly changes what you see and what options are available:
- Available settings differ by generation – older devices may not expose advanced tabs or options present on newer hardware.
- Compatibility with new sensor lines – for example, working with Shelly Blue sensors depends on having devices with Bluetooth support.
- Advanced functions – features such as richer scripting, energy tools or multi protocol options may only appear on Gen 3 and Gen 4 devices.
Connectivity evolution across generations
Connectivity is one of the clearest ways to understand how Shelly hardware has evolved over time and why that matters for automation designers and installers.
- Gen 1: Wi-Fi and MQTT only, ideal for basic IP based control and simple broker integrations.
- Gen 2: Wi-Fi plus Bluetooth, which speeds up onboarding and enables new Bluetooth based devices and scenarios.
- Gen 3 and Gen 4: Matter support, extra protocols and multi connectivity, so a single device can participate in a wider smart home or building ecosystem.
For installers and integrators, this connectivity evolution brings very practical benefits:
- Easier commissioning via Bluetooth – pairing and initial configuration are faster and less error prone on site.
- Flexible choice of transport – you can choose Wi-Fi, Zigbee or Matter to match the rest of the system, instead of being locked into one stack.
Understanding which generation you are working with is therefore a critical first step before you start planning scenes, groups, sensor triggers or energy monitoring in the Shelly Smart Control app.
Shelly Colour Coding – Quickly Identifying Device Capabilities
Shelly’s product range spans relays, sensors, meters, dimmers, and lighting controllers—each built for specific automation tasks. To make these devices easier to identify during installation or setup, Shelly uses a clear colour coding system across its generations. This visual language becomes especially helpful when working inside the Shelly Smart Control app, where different device types offer different features and configuration options.
Relay and metering devices by colour
Shelly relays and energy monitoring products follow a consistent colour scheme that highlights their electrical capabilities and whether metering is included.
- Light blue – One-channel relay with dry contact, ideal for low-voltage control, gates, and garage integrations.
- Red – One-channel relay with integrated power metering for tracking real-time energy consumption.
- Black – Multi-channel relay with power metering, perfect for controlling multiple loads with energy insights.
- White – Single-phase or three-phase energy meters for monitoring whole rooms, circuits, or full electrical panels.
Lighting and control devices by colour
Lighting, dimming, and control peripherals also follow a dedicated colour code, helping installers and users quickly distinguish devices designed for illumination and analogue control.
- Green – Dimmers for smooth, flicker-free light control.
- Yellow – RGB and RGBW controllers for colour-capable lighting setups.
- Dark blue – 0–10 V controllers for analogue lighting control, architectural lighting, and commercial dimming systems.
Why the colour code matters in the app
Recognising Shelly device colours isn’t just helpful during installation—it's equally valuable when building automations inside the app. The colour system speeds up navigation and prevents configuration mistakes.
- Faster identification when choosing devices for scenes and groups.
- Prevents load mismatches such as combining non-metered and metered relays incorrectly.
- Useful for diagnostics in larger homes, buildings, or multi-device dashboards where quick visual cues reduce confusion.
Local vs Cloud Control in the Shelly Ecosystem
Shelly devices are designed to work reliably in both online and offline environments. To achieve this, the ecosystem is built around two complementary control layers: local control through the device’s own interface and cloud-based control through the Shelly Smart Control app. Understanding the strengths of each layer helps you design automations that remain both flexible and robust.
What is local control on a Shelly device?
Local control refers to interacting with a Shelly device directly on your network, without relying on Shelly Cloud. This is done by accessing the device through its IP address and using the built-in Shelly web UI.
Through local control, you can configure:
- Local timers – delayed switching behaviour stored on the device itself.
- Local schedules – time-based automations that run without any cloud connection.
- Local actions – device-triggered webhooks for fast communication between Shelly devices.
- Local scripts – JavaScript-based logic executed directly on the hardware.
The key advantage of local control is simple: automations continue to operate even if your internet connection fails. For critical loads and essential routines, local logic ensures continuous operation without cloud dependency.
What does cloud-based control add via Shelly Smart Control?
While local control handles essential on-device automation, the Shelly Smart Control app provides a centralised cloud layer that unlocks more advanced features and cross-device coordination.
Cloud-based control enables:
- Group control – manage multiple devices of the same type with a single command.
- Multi-condition scenes – build automations that combine triggers, conditions, and multiple actions.
- Sensor and weather triggers – create responses based on temperature, humidity, motion, light level, or weather data.
- Energy panel and historical analytics – track consumption trends and review long-term performance.
Local and cloud layers are designed to cooperate. The device itself handles real-time switching and low-level logic, while the cloud orchestrates cross-room and cross-device behaviour that would be difficult to manage locally.
Choosing between local and cloud for critical automations
Selecting where to run your automations depends on reliability requirements and the nature of the task.
Use local logic when controlling:
- Security-related systems
- Garage doors and gates
- Pumps, fans, and appliances
- Heating or safety-critical equipment
These functions must remain operational even during internet outages, making device-level logic the safest choice.
Use cloud-based control when you want:
- Whole-home scenes that span multiple rooms or floors
- Coordinated behaviour across several device types
- Weather-based automations
- Rich visual dashboards for energy and device monitoring
In practice, the strongest Shelly installations use a hybrid approach: critical routines stay local, while cloud features handle broader automation, user experience, and analytics.
Navigating the Shelly Smart Control App Interface
The Shelly Smart Control app is designed to give you a clear and structured overview of every device in your system. Whether you are managing a single room or an entire building, the interface organises devices in a way that makes configuration, diagnostics, and automation fast and intuitive.
Device cards and room structure
The app organises your home or building into rooms, each containing the Shelly devices installed in that space. You can switch between room-level views or choose a global overview that displays all devices at once.
Every device is represented by a device card, which provides immediate access to essential controls and status indicators:
- Quick controls such as on/off switches, open/close buttons, or dimming sliders depending on the device type.
- Status indicators showing whether a device is online, offline, triggered, or in an alarm state.
This layout makes it easy to monitor your environment at a glance and take rapid action when needed.
The Device Information tab – your primary diagnostic tool
Inside each device card, selecting the Device Information tab gives you access to the most important technical details. This screen is where installers, integrators, and advanced users spend much of their time when diagnosing issues or planning automations.
Here you will find:
- Device ID, model, and generation for compatibility checks.
- Firmware version to confirm whether the device is current.
- IP address with a one-tap link directly into the local Shelly web UI.
These details matter because they determine how the device behaves in the app. The generation confirms which features are supported. The firmware version indicates whether the latest automation options, energy tools, or connectivity enhancements are available. And the IP link allows you to quickly access local settings when troubleshooting.
Customising device cards for safety and clarity
The Shelly Smart Control app lets you customise how each device card behaves and what level of control it exposes. This is particularly useful in busy dashboards or shared environments.
Customisation options include:
- Showing or hiding direct controls such as toggle buttons or shutter arrows.
- Requiring users to open the device page before changing its state, adding an extra confirmation step.
These settings are ideal for:
- Child safety—preventing accidental activation of shutters, gates, or high-power circuits.
- Cleaner UI management—reducing visual clutter in properties with many devices or in multi-user environments.
By tailoring each card’s interaction level, you can maintain both usability and safety while keeping the overall interface organised and intuitive.
Step by Step Example – Automating a Garage Roller Shutter
A practical way to understand the power of the Shelly Smart Control app is to walk through a real automation scenario. In this example, we use a Shelly 2PM configured as a roller shutter, controlled with a Shelly BLU button, and enhanced with a Shelly door/window sensor to add context-aware behaviour. This setup is ideal for garages, gates, or any motorised cover.
Hardware used in the example
To build this automation, the following devices are used:
- Shelly 2PM configured as a roller shutter (cover relay).
- Shelly BLU button to serve as a wireless control trigger.
- Shelly door/window sensor mounted on the garage door to report open/closed state.
- Optional: Shelly smart bulbs to illuminate the driveway or garden when the door is opened.
Configuring the Shelly 2PM as a shutter in the app
The first step is preparing the Shelly 2PM so that it behaves like a proper shutter controller within the app. This ensures smooth operation, accurate position tracking, and safe motor handling.
- Change the device profile from “switch” to “cover” so the app displays open/close controls instead of simple toggles.
- Run the calibration process so the device learns fully open, fully closed, and intermediate positions.
- Set the input type—choose either button or switch depending on the physical wall control you wired in.
- Configure power thresholds so the 2PM can detect motor start and end conditions with better accuracy.
- Use “swap inputs” if the arrows behave in reverse due to wiring orientation.
-
Set the on power on behaviour:
- Return to last state,
- Automatically close, or
- Stop and wait for new commands.
Creating a basic open and close scene with a Shelly Blue button
With the roller shutter configured, you can now create simple control scenes using the Shelly Blue button. This gives you fast, wireless access to open or close the garage with one press.
Scene 1 – Open the garage door
- Condition: Single press on the Shelly Blue button.
- Action: Open the roller shutter.
Scene 2 – Close the garage door
- Condition: Double press on the same Shelly Blue button.
- Action: Close the roller shutter.
You can also add an optional time window to restrict operation to certain hours—for example, daytime or early evening—enhancing safety and preventing accidental activation.
Extending the scene with a door/window sensor and lights
To add intelligence and improve safety, you can combine the roller shutter automation with a Shelly door/window sensor and outdoor lighting.
Add the door/window sensor as a condition:
- When the garage door is detected as open, trigger an additional action.
Example extended scene:
- Condition: Garage door state = open.
- Action: Toggle or switch on selected garden or driveway lights.
This small enhancement brings real-world benefits:
- Improved visibility when arriving home after dark.
- Instant visual feedback that the garage door is open.
This example showcases how Shelly devices work together—relays, buttons, sensors, and lighting—to create a seamless and practical automation flow inside the Shelly Smart Control app.
Timers, Schedules, Actions and Scripts – Where Shelly Logic Lives
Behind every smart behaviour in the Shelly ecosystem is a layer of device or cloud-based logic. The Shelly Smart Control app, combined with the device’s local capabilities, gives you multiple ways to automate actions depending on how simple, advanced, or resilient you want your system to be. Understanding timers, schedules, actions, and scripts helps you choose the right tool for each task.
Timers for simple delayed switching
Timers are the most straightforward automation method in Shelly devices. They apply a delay before performing an action and are stored directly on the device, making them reliable even without a cloud connection.
What timers do:
- Trigger an action after a defined number of seconds.
- Can be configured in both the local web UI and the Shelly Smart Control app.
Example use cases:
- Automatically turning off a plug 10 seconds after it is switched on.
- Creating auto-off behaviour for fans, lights, or auxiliary circuits.
Time based automation with schedules
Schedules offer precise, time-based control and are ideal for predictable routines that follow fixed hours or daily patterns. They can be configured in both the app and the device’s web UI.
Schedules in the local web UI:
- Usually define one action per schedule.
- You often need two schedules—one for “on” and one for “off.”
Schedules in the Shelly Smart Control app:
- Provide a central overview of all scheduled events.
- Much easier to manage across large installations or many devices.
When to choose schedules over scenes:
- For fixed times such as morning routines, night shutdowns, or daily lighting cycles.
- When behaviour does not depend on other devices or sensor states.
Local actions and webhooks between devices
Actions allow Shelly devices to communicate directly with each other, creating fast and offline-capable automation. Actions are stored on the device, making them independent of cloud connectivity.
How actions work:
- Triggered when a condition on the device is met (e.g., switch turned on).
- Can issue a command to another Shelly device via its IP address.
- Can send HTTP requests (webhooks) to external systems or services.
Example:
- When a Shelly Plug S turns on, send a webhook to activate a Shelly relay controlling ventilation.
Benefit of actions:
- They work fully offline because the logic is stored in the device’s memory.
Advanced customisation with Shelly scripts
For users who need deeper control, Shelly devices support JavaScript-based scripting directly on the hardware. This unlocks powerful automation beyond what scenes or actions can achieve.
About Shelly scripts:
- Written in JavaScript and executed locally on the device.
- Snippets are available in the web UI to accelerate setup and reduce coding effort.
Possible use cases:
- Complex multi-step automation sequences.
- Integrating custom protocols or handling external APIs.
- Building advanced state machines or conditional logic beyond scene capabilities.
Shelly also offers official scripting courses—a basic track and an advanced track—for users and installers who want to expand their automation skills and take full advantage of the device-level programming environment.
Frequently Asked Questions about Shelly Smart Control
Does the Shelly Smart Control app work without the internet?
Yes. Shelly devices support full local control on your LAN, so timers, schedules, actions and scripts continue to work even if your internet connection goes down.
What is the difference between local control and cloud control on Shelly devices?
Local control keeps automation and device communication inside your home network. Cloud control adds remote access, multi-device cloud scenes, energy dashboards, and cross-room coordination.
Can Shelly Blue sensors trigger cloud scenes?
Yes, but only when a Bluetooth-enabled Shelly device (Gen 2, Gen 3 or Gen 4) is acting as a gateway. Without a gateway, Blue sensors can operate locally but cannot reach the cloud.
Can I share my Shelly devices with another account and still limit access?
Yes. Shared devices can be given restricted permissions, allowing basic control without exposing full configuration or advanced settings.
Is Shelly suitable for hotels, rentals and Airbnbs?
Yes. Shelly supports offline-capable automation, limited-access sharing, and remote management via the Installer Portal—ideal for guest environments and multi-unit properties.
Do Shelly Gen 3 and Gen 4 devices support Matter?
Yes. Matter support is available on selected Gen 3 and Gen 4 devices, with ongoing expansion across the lineup.
