Skip to main content

Controllers

Overview to controllers​

There are three types of controllers in Casambi Pro:

  • Switches
  • Sensors
  • Schedules

In Casambi Pro, controllers are first created as virtual placeholders in Casambi Pro for Windows. These placeholders can be configured already in the configuration design phase. At the commissioning phase, the virtual controllers are replaced by the real devices.

Switches and sensors can also be paired into Pro networks as new controller devices (ie., not replacing a virtual controller placeholder). In this case, they will not have a pre-configuration and need to be programmed afterward manually in either Pro for Windows or iOS.

Controller configuration workflow:​

  1. Add a virtual controller element into a space (switch, sensor or schedule) in Casambi Pro for Windows.
  2. Configure the virtual controller (Pro for Windows or iOS)
  3. In Pro for iOS, replace the virtual controller by pairing a real controller device on top of it. The real device’s image appears on the layout.
  4. Test that the controller works.
  5. Fine tune the configuration (Pro for iOS or Windows)

Notes about Controllers​

Notes

  • New virtual controllers can be added only in Casambi Pro for Windows.
  • On Casambi Pro for iOS, a controller can be paired either on top of a virtual controller or as a new unit, without using a virtual placeholder.
  • One controller belongs always to only one space.
  • A controller cannot be moved or copied between spaces. However, they can be duplicated inside one space.
  • It is possible to edit all switch, sensor and schedule properties in Pro for Windows and Pro for iOS.
  • Pairing real controller devices over the controller placeholders is possible only with Casambi Pro for iOS.
  • The schedule controller in Casambi Pro has certain functional limitations compared to the Casambi App:
    • Project (site) wide schedule cannot be created. Schedule’s functional scope is limited to the space where the schedule resides.
    • No Override Presence feature.
    • It is not possible to leave the Deactivation time unset (empty).