The driver installs one of three sub driver types under Input Controllers, depending on how you install:
MagicCubeBinarySensor – one sub driver per binary sensor entity. Installed for devices with a single binary sensor and by the By Entity option.
MagicCubeInputDevice – one sub driver per device with up to 20 inputs. The sub driver automatically discovers all of the device’s binary sensors. Installed for devices with more than one binary sensor and by the By Device option.
MagicCubeInputList – a manual list of up to 40 entities of your choice. Allowed entity types: binary_sensor. event. button. Installed by the By List option; type the entity ids into the sub driver’s Inputs List page.
It is recommended that you follow the below installation process to make sure you are running the latest version of the [driver].
Open Input/output Section, Communication Devices, Add new Communication Device.
In V2, click Import MagicCubeInputPro driver. In V1, Navigate to the folder where the driver is located and Choose the MagicCubeInputPro driver, OK
If you receive a warning that this is not a Native Elan driver, click OK
The Driver will automatically go into trial mode for 90 days. Wait for about 10 seconds and the Status will turn Green
Add the Innovo Activation Code received in the email.
Starting with Magic Cube Aura and V5 Patch 3, you no longer need to add the token. The token is added using the Magic Cube Admin Interface. See Magic Cube User Manual
Click Apply.
Click Discover, and the driver will discover and populate the IP address of the Magic Cube device on the network. If the device is not discovered or you have more than one, enter the IP address manual.
From the Platform dropdown, choose the brand of sensors you would like to install, then click Install Platform. The Driver will automatically discover all sensors connected to the Magic Cube and install them under Input Controllers as sub drivers: devices with a single binary sensor get a MagicCubeBinarySensor sub driver, and devices with more than one get a MagicCubeInputDevice sub driver.
By Entity: installs a single MagicCubeBinarySensor sub driver for one entity. Type the entity id in the Other Platform/Entity field, choose By Entity from the Platform dropdown, click Apply, then Install Platform.
By Device: installs a MagicCubeInputDevice sub driver for the device that owns an entity. Type one of the device’s entity ids in the Other Platform/Entity field, choose By Device from the Platform dropdown, click Apply, then Install Platform. The sub driver discovers all of the device’s binary sensors (up to 20).
By List: installs an empty MagicCubeInputList sub driver (no Magic Cube query). Choose By List from the Platform dropdown and click Install Platform. Then open the sub driver’s Inputs List page and type up to 40 entity ids (binary_sensor. event. button.). Click Install Platform again to add another list.
NOTE: You must have the brand/platform preconfigured in the Magic Cube First. See Magic Cube Manual.
NOTE: If the platform you want to install is not shown on the platform dropdown, then contactsupport@innovo.netto get the exact name of the platform you want. After you get the exact name, choose Other from the platform dropdown, enter the name you have in the Other Platform Field, click Apply, and install.
NOTE: To continue installing platforms from the dropdown you should have the Other Platform field empty
NOTE: Installing requires Magic Cube firmware with API schema 102 or newer. If the driver reports “Magic Cube needs an update!”, update the Magic Cube firmware first.
If you need to add more sensors in the future, click on Install Platform.
Install Magic Cube . Setup all your devices in Magic Cube and name them according to your needs. See Device Integration Notes at the end
The driver relies on a static IP address for each Magic Cube device. Assign a Static IP address using DHCP reservations in your router. If the device IP address changes, then change it manually in the Elan Configurator
Starting with Magic Cube Aura and V5 Patch 3, you no longer need to add the token. The token is added using the Magic Cube Admin Interface. See Magic Cube User Manual
Driver not discovering devices. Try discovery again. Make sure broadcasting is enabled on the network
“Magic Cube needs an update! (API schema x < 102)”. The Magic Cube firmware is too old for this driver. Update the Magic Cube, then click Install Platform again
Add By Device and By List install options with two new sub drivers: MagicCubeInputDevice (per device, up to 20 inputs) and MagicCubeInputList (manual list of up to 40 entities).
Smart platform install: devices with one binary sensor get a per-entity sub driver, devices with more than one get a per-device sub driver.
Require Magic Cube firmware with API schema 102 or newer.