Software Overview  |  Sitemap  |  Downloads  |  Developers  |  Forums

Status Device

The Status Device shows the status of a group of terminals. It is useful when you wish to monitor a set of terminals from a messaging Device such as an email Device or text messaging Device. You define a set of input terminals, wire the terminals to whatever terminals in your system you wish to monitor, and the Status Device creates messages reflecting the state of these terminals.

Here is a typical message from a Status Device. It's from a Device with two inputs called "in1" and "in2" which have values 1 and 2.

"in1: 1, in2: 2"

Notice it is a quoted string (which it has to be, because it wouldn't make sense if it was interpreted), so it can be wired directly to another Device.

Status Device Terminals

The Status Device has two predefined terminals and an unlimited number of user defined input terminals. The predefined terminals are named "in" and "out". The "in" terminal tells the Device when to generate a message, and the "out" terminal emits that message. The user defined terminals and their values are contained in the message.

Anytime the Status Device gets an event on its "in" terminal, it generates a message on its "out" terminal. The value on the "in" terminal is irrelevant - any event will generate a message.

Creating a Status Device

Status Devices are created by running the Status Script. The Status Script takes one input parameter, the "inputs" parameter.

inputs :

  • a set of names defining input terminals. The set is a quoted string with its elements separated by commas.


Running the Status Script with the parameters listed below will add a Status Device with 3 inputs for monitoring status:

id: "status_device"
inputs: "1,2,3"

The inputs will be called "1", "2" and "3". If input "1" has value on, "2" the value off, and "3" the value 10 and the "in" input receives an event, the "out" terminal will generate the value:

"1: on, 2: off, 3: 10"

Catalina Computing, LLC.

Copyright © Catalina Computing, LLC. (2013-2018)

Page last updated: Wed Jan 7 16:15:21 2015 (UTC)