The Openmotics system supports following virtual devices:
- Virtual Inputs: For example a doorbell that sends a push notification is translated in an action that switches on a light in the house
- Virtual Outputs: For example a Philips Hue light that acts as a virtual output can be switched on by a normal switch on the Openmotics system (or a virtual switch)
- Virtual Sensors: Any non-openmotics sensors like Z-wave wireless temperature, NEST thermostat temperature and humidity, third party light sensors etc
How does all the Virtual stuff works?
All virtual devices are picked up by the plug-in system:
- Virtual Inputs: Virtual inputs like doorbells, motion detectors etc sends a message to the Gateway that is picked up by Plug-in system. The plug-in system will translate this in actions and for example switch on/off lights, change thermostat settings, change position of shutters etc
- Virtual Outputs: When for example a virtual output (Philips Hue for example) has to be switched when an input on the Openmotics system is pressed, a Virtual Output can be configured. Each Virtual Output that must be switched will be sent to the gateway. On the gateway, a for example Philips plug-in will be installed that converts the virtual output to the necessary commands for the Philips system.
- Virtual Sensors: The Plug-in system will request for example the temperature of a wireless sensor and forward this to the Master. The Master will use this temperature like it was a temperature measured from one of the sensors directly connected to the Openmotics system. In other words, a Virtual sensor can be used to perform any function like it was a directly connected sensor so you can use Virtual sensor and use them for example in the thermostat functions.
See Virtual Plug-in Examples for more information how to use this in combination with the plug-in system.
Virtual Inputs (Available in firmware version 3.142.1 and higher)
As of Firmware Version F3.142.1 and higher, the master allows virtual inputs