Join Numbers as Signal Names

Press the Load button to load the scenario.

Press the Run button to run the scenario. You only need to do this if the scenario (the json) has an onStart key.

The Emulator Scenario JSON contains an array of cues and an optional array onStart A cue is defined by: type:string, signal:string, trigger:boolean|string|number, actions:array. An action is defined by: type:string, signal:string, logic:string ... plus other fields ( depending on type)

type for cue or for action can be the string:

b or boolean - for a boolean signal
n or number or numeric - for a number signal
s or string - for a string signal
o or object - for an object signal

signal for cue or for action is a string representing the name of the signal:

trigger can be either a fixed value of the same type as the signal, or the string "&change". If it is a fixed value then, when the emulator detects that the signal has changed to the value given in trigger then it also executes the actions for that signal. If the value is the string "&change", regardless of signal type, then the actions are executed on any change in the value of the signal.

logic can be:

link - passes the value received on the incoming join through to the outgoing join. Using this between incompatible join types will attempt to cast the value. In the event of a cast failure the value will be set to false, 0 or "" (empty string)
set - assigns a specific value to the join. This requires a 5th key of 'value' and the specific value to assign. ie. {"signal":"light_level", "type":"n", "logic": "set","value":5}. If the 5th key is omitted, the default value will be sent (false, 0, "" or {})
toggle - (boolean Only) reads the current state and changes it to the opposite state
pulse - (boolean Only) value goes high and then low.
increment - (Numeric Only) reads the current value of the analog and adds an offset. This logic accepts an optional 5th key of 'offset which determines how many to incrementby. ie. {"signal":"volume_level","type":"n", "logic":"increment","offset":5}. If this 5th key is omitted, the default offset of 1 will be applied.
decrement - (Numeric Only) reads the current value of the analog and subtracts an offset. This logic accepts an optional 5th key of 'offset which determines how many to decrement by. ie. {"signal":"volume_level","type":"n", "logic":"decrement","offset":5}. If this 5th key is omitted, the default offset of 1 will be applied.

RCB logic can be accomplished by defining an action containing an object signal of RCB type:
{ "rcb":{ "value": numeric_value, "time": duration_in_ms } }
Scenario example:


    {
      "cues": [
        {
          "type": "boolean",
          "signal": "trigger",
          "trigger": true,
          "actions": [
            {
              "signal": "action1",
              "type": "boolean",
              "logic": "toggle"
            },
            {
                "signal": "rcb_signal",
                "type": "object",
                "logic": "set",
                "value": {
                    "rcb":{
                        "value": 101,
                        "time": 1500
                    }
                }
            }
          ]
        }
      ],
      "onStart": [
      ]
    }

Crestron Components Lib - Showcase App

Join Numbers as Signal Names

CH5 Button attributes that start with 'receiveState' example

ch5-button

CH5 List attributes that start with 'receiveState' example

ch5-list

CH5 Image attributes that start with 'receiveState' example

ch5-image

CH5 Select attributes that start with 'receiveState' example

ch5-select

ch5-select-option

CH5 Toggle attributes that start with 'receiveState' example

ch5-toggle

CH5 Overlay Panel attributes that start with 'receiveState' example

ch5-overlay-panel

CH5 Modal Dialog attributes that start with 'receiveState' example

ch5-modal-dialog

CH5 Toggle attributes that start with 'receiveState' example

ch5-slider

CH5 Triggerview attributes that start with 'receiveState' example

ch5-triggerview

First View

Second View

Third View

ch5-triggerview-child

First View

Second View

Third View

CH5 Textinput attributes that start with 'receiveState' example

ch5-textinput

CH5 Spinner attributes that start with 'receiveState' example

ch5-spinner