Innovo Wiki

Innovo Wiki

Loading the knowledge...

Concepts

Estimated reading: 4 minutes

Concepts and terminology


Now you’re in Home Assistant, let’s go over important parts of Home Assistant and what they do.

Dashboards

By Default, The Magic Cube relies on Control systems for the UI and doesn’t use dashboards.

Dashboards are customizable pages to display information in Home Assistant. To learn more about dashboards, refer to the dashboard documentation.

Integrations

NOTE: Once you add the integration to Home Assistant, add the corresponding driver in your control system. For example, after install the Philips Hue integration in home assistant, install the Magic Cube Lighting Pro Driver in your controller, choose Philips and Install. This will import all your devices from the Magic Cube into your control System.

Integrations are pieces of software that allow Home Assistant to connect to other software and platforms. For example, a product by Philips called Hue would use the Philips Hue integration and allow Home Assistant to talk to the hardware controller Hue Bridge. Any Home Assistant compatible devices connected to the Hue Bridge would appear in Home Assistant as devices.

For a full list of compatible integrations, refer to the integrations documentation.

Once an integration has been added, the hardware and/or data are represented in Home Assistant as devices and entities.

Devices & entities

Devices are a logical grouping for one or more entities. A device may represent a physical device which can have one or more sensors. The sensors appear as entities associated to the device. For example, a motion sensor is represented as a device. It may provide motion detection, temperature, and light levels as entities. Entities have states such as detected when motion is detected and clear when there is no motion.

Devices and entities are used throughout Home Assistant. To name a few examples:

  • Dashboards can show a state of an entity. For example, if a light is on or off.
  • An automation can be triggered from a state change on an entity. For example, a motion sensor detects motion and triggers a light to turn on.
  • A predefined color and brightness setting for a light saved as a scene.

Automations

A set of repeatable actions that can be set up to run automatically. Automations are made of three key components:

  1. Triggers – event(s) that start an automation like when the sun sets.
  2. Conditions – optional tests that must be met before continuing to running actions. For example, if someone is home.
  3. Actions – interact with devices such as turn on a light.

To learn the basics about automations, refer to the automation basics page or try creating an automation yourself.

Scripts

Similar to automations, repeatable actions that can be run. The difference between scripts and automations is that scripts do not have triggers like automations. This means that scripts cannot automatically run unless they are used in an automation. Scripts are particularly useful if you perform the same actions in different automations or trigger them from a dashboard. For information on how to create scripts, refer to the scripts documentation.

Scenes

Scenes allow you to create predefined settings for your devices. Similar to a driving mode on phones, or driver profiles in cars, it can change an environment to suit you. For example, your watching films scene may dim the lighting, switch on the TV and increase its volume. This can be saved as a scene and used without having to set individual devices every time.

To learn how to use scenes, refer to the scene documentation.

Add-ons

The Magic Cube Does NOT support Add-ons. More Info Here about the installation type,

CONTENTS