Readme1st

From ago control wiki
Revision as of 10:11, 7 December 2012 by Hari (Talk | contribs)

Jump to: navigation, search

Contents

Basics

ago control uses AMQP as underlying communication protocol. It uses the Apache QPID broker to pass messages. The components communicate over a topic queue "agocontrol". The Resolver component tracks device announcement events to build an inventory. It also enriches the inventory with devicename and room information and provides the device schema. This can be used by user interfaces as it defines the supported commands for each device type.

Installation

We provide packages for Debian Wheezy and Fedora 17. You should install at least the agocontrol and the agocontrol-admin package. You probably also want to install other components for device support.

Configuration

The global configuration is set in the config.ini file residing in /etc/opt/agocontrol. Here you can specify an installation uuid, the host, username and password for the broker configuration and settings for device interfaces like the USB com port to use for the Z-Wave interface device.

Startup

The packages contain systemd service definitions. You can use systemctl to start ago control components, e.g.:

systemctl start agoresolver.service
systemctl start agoadmin.service

You can also enable and start all installed components with this small helper script (this is the recommended approach for beginners):

/opt/agocontrol/bin/agoctrl.sh enable
/opt/agocontrol/bin/agoctrl.sh start

Debugging

The output from the components is logged to syslog. Depending on your syslog configuration it probably ends up in the log /var/log/daemon. You can also take a look at the internal AMQP communication. To watch the messages on the broker use "agodrain.py":

python /opt/agocontrol/bin/agodrain.py

What next?

Now connect to the ago control administration interface. You can get more information here: AgoAdmin

Personal tools