About Yombo Gateway
The Yombo Gateway automation software was designed and built around ease of use while at the same time provide flexibility to control any type of device.
The gateway software implements a web interface that allows users to configure and setup the system. This information is saved locally as well at the Yombo cloud servers. Storing this information in the cloud allows mobile apps to control devices remotely. This also allows the user to quickly restore a gateway if needed. Note: Any sensitive data fields will be encrypted using GPG and can only be decrypted by the local gateway, to fully restore a gateway, the user should make make backups.
To assist the user on controlling hard wired devices, such as non-smart garage doors or wired motion sensors in various locations in a building, Yombo has implemented gateway clustering. This allows one Raspberry PI to act as a master while allowing multiple Raspberry PI Zeros to be placed close to wired devices so users do not have to long cable runs.
The Yombo Gateway automation system was designed with these primary goals:
- Make it easy for users to install, configure, and use.
- Users should spend minimal time installing the software and editing configuration files and more time automating.
- Make it work with nearly any type of device imaginable, this includes virtual devices, remote computers, switches, lights, etc.
- Allow multiple ways to control devices.
- Run on low cost and low energy usage devices such as Raspberry PI.
- Allow users (or developers) to easily extend and expand the capabilities of the system through the use of modules.
The gateway provides an easy to use framework that allows control of many types of devices. The gateway treats every device type (a light bulb for example) the same regardless of how it's connected or implemented (Zwave, Insteon, X10, etc). This allows the user to simply devices the same without worring about the implementation details.
Implementation details for any vendor or automation protocol is implemented by modules. The gateway simply routes a command (on, off, dim, channel up, etc) to the module which is responsible for completing the task.