Navigate to the grid view and in the Instance types perspective click on the Push button tab.

You will see all of the instances that are currently on that site. If there are profiles that have been created and assigned to control systems then they will appear on the very right of the view.

You can create a new push button application by ticking the checkbox at the start of the profile column. Applications that can be created will have a white background. Instances that are not assigned to the profile can not be ticked and will have a grey background. Unticking the checkbox will remove the application from that control system.

When you create a new application it will lock the fields until it has successfully been created. It will default the values of the application on creation. Once created these values can be updated to suit the needs of the push button.

The type field contains a list of all of the push button types that can be set for the application. Types that have DT* in brackets after the type (i.e. Custom colour (DT8)) requires the device type of that number to be set for the instance. Each type has different functionality. Only the custom types will enable the behaviour field and allow the values to be changed.

• Dimmer
  • Short press toggles on and off
  • All long presses instruct fitting to dim UP or DOWN in intensity for 200ms using FADE RATE. As long as user holds, will continue to instruct fitting each ~160ms to keep dimming.
• Memory Dimmer
  • First long press increases the fittings intensity
  • Second long press decreases the fittings intensity
  • First short press turns the fitting off
  • Second short press recalls the last level of the fitting
• Up Dimmer
  • Long press increases the fittings intensity if the light is already on.
  • IF the primary (first) target is off, the first command sent will turn the lights on.  
  • Use Custom Short/Long Press with UP/UP as commands to avoid lights being turned on by this config
• Down Dimmer
  • Long press decreases the fittings intensity until minimum level.  Lights will not turn off.
• Dimmer With No Short Press
  
  • Long presses instruct fitting to dim UP or DOWN in intensity for 200ms using FADE RATE. As long as user holds, will continue to instruct fitting each ~160ms to keep dimming.  
  • Note that this configuration does NOT turn lights on or off.  Will only dim between minimum and maximum levels of fitting.
• Tuneable White Dimmer
  • First long press makes the colour cooler
  • Second long press makes the colour warmer
• Tuneable White Memory Dimmer
  • First long press makes the colour cooler
  • Second long press makes the colour warmer
  • First short press turns the fitting off
  • Second short press recalls the last level of the fitting
• Tuneable White Cool Dimmer
  • Long press makes the colour cooler
• Tuneable White Warm Dimmer
  • Long press makes the colour warmer
• Custom Dimmer
  • First long press increases the fittings intensity
  • Second long press decreases the fittings intensity
  • First short press sends custom dali command 1 to the fitting
  • Second short press sends custom dali command 2 to the fitting
• Custom Arc Dimmer
  • First long press increases the fittings intensity
  • Second long press decreases the fittings intensity
  • First short press sends custom arc command 1 to the fitting
  • Second short press sends custom arc command 2 to the fitting
• Custom Toggle
  • First short press sends custom dali command 1 to the fitting
  • Second short press sends custom dali command 2 to the fitting
  • If with lux follow is enabled, will cause lux targets to be modified after 1 minute to current value
• Custom Arc Toggle
  • First short press sends custom arc command 1 to the fitting
  • Second short press sends custom arc command 2 to the fitting
• Custom Push And Release
  • Pushing and holding the switch sends custom dali command 1 to the fitting
  • Releasing the switch sends custom dali command 2 to the fitting
• Custom Arc Push And Release
  • Pushing and holding the switch sends custom arc command 1 to the fitting
  • Releasing the switch sends custom arc command 2 to the fitting
• Custom Short/Long Press
  • Short press sends custom dali command 1 to the fitting
  • Long press sends custom dali command 2 to the fitting
• Custom Arc Short/Long Press
  • Short press sends custom arc command to the fitting
  • Long press sends custom dali command to the fitting
• Custom Tuneable White
  • Long press makes the colour cooler/warmer depending on cooler/warmer setting
  • Short press goes to the colour temp set
• Custom Tuneable White Toggle
  • First short press sends first custom colour temperature to the fitting
  • Second short press sends second custom colour temperature to the fitting
• Custom RGBWAF / XY dimmer
  • Long press makes the colour cooler/warmer depending on cooler/warmer setting
  • Short press goes to the RGBWAF or XY colour depending on which colour type is set
• Override only
  • Sends the only override behaviour, overrides line for time specified in override time
• Analytics only
  • Switch has no effect but still uploads data for analytics
• Action
  • Triggers sequences (and action1/action2/action3)

The behaviour field will be disabled by default. It will only be enabled if a custom push button type is selected in the previous field indicated by the word custom in the type name. Once enabled this field will display default values for the specific custom type. Some custom types have different fields compared to other custom types. This field will dynamically update the input options when the type is changed.

Most custom button actions can be achieved when using a custom toggle button type, the behaviours field will allow users to configure buttons to:

• Send DALI Lighting commands
  
  • Off
  • Up
  • Down
  • Step up
  • Step down
  • Recall max
  • Recall min
  • Step down and off
  • Step up and on
• Go to last active level
• Go to Scene (0 - 11)
• Go to memory dim level
• Manage emergency devices
  • Inhibit emergency
  • Rest
  • Start test (function or duration)
  • Stop test
  • Set emergency relays on
  • Set emergency relays off
• Identify
  • Emergency
  • Control Gears
  • Control Devices
  • All
• Perform profile actions 
  • Go to profile 
    • Go to <Profile Number> - <Profile Name>
  • Force go to profile
  • Return to scheduled profile
• Reboot controller

The override field can be set so that timeouts for instances are overridden for the push button. The supported overrides will be shown in this dropdown. This field works in conjunction with the override time field to the right of this field. There is an override only type which will, as the name suggests, only run the overrides that are specified in these fields and nothing else. There are default timeouts for instances which are run when the button is pushed. Specifying an override time and an override type will override the default timeout with the specified one only for the instance types that have been selected in the override dropdown field.

The override time field is disabled by default and can be enabled by changing the override from Default to any other override type in the dropdown. The time will default to the minimum override time that is allowed for the override type. This can then be changed by opening the time picker for the field and setting it to anything that is within a valid range. If the time is invalid it will go orange to indicate an error and hovering over the cell will give a more in-depth explanation of what is wrong. It should specify the valid time range in the error message for the override type chosen.

LED

The LED column determines the behaviour of the LED that is on the push button.

• Disabled
  • LED is off at all times
• Any (flash if in warn sequence)
  • There are several modes that have "(flash if in warn sequence)" following the label which will do the normal behaviour but if the sequence is currently in a warn state then it will override that behaviour with flashing
• Comms status
  • LED will flash when the button is pressed
• Target
  • LED will turn on when the button is toggled on
• Target (managed)
  • LED will turn on when the button is toggled on, used for when push button doesn't necessarily hear all lighting commands such as wireless devices
• Inverted target
  • LED will turn on when the button is toggled off
• Inverted target (managed)
  • LED will turn on when the button is toggled off, used for when push button doesn't necessarily hear all lighting commands such as wireless devices
• Scene
  • LED will turn on if the primary target for the instance is at the current scene
• Scene (managed)
  • LED will turn on if the primary target for the instance is strictly at the current scene (even step or dim commands will turn the LED back off)
• Inverted scene (managed)
  • LED will turn on if the primary target for the instance is strictly not at the current scene (even step or dim commands will turn the LED back off)
• Last heard scene (managed)
  • LED will turn on if the primary target for the instance is non-strictly at the current scene (must send a different scene to turn the LED off)
• Inverted last heard scene (managed)
  • LED will turn on if the primary target for the instance is non-strictly not at the current scene (must send a different scene to turn the LED off)
• Always on
  • LED is on at all times
• Flash
  • LED flashes at all times
• Lux override
• PIR override
• Colour override
• Intensity override
• Switch override
  • These LED modes are dependent on what condition and state are chosen
  • The conditions are either if the override is active or if it is inactive
  • When the condition is met the LED will either be on or will flash depending on what LED state is picked
• Inhibit
  • Acts the same as the above override options but will only work if there is currently an inhibit that matches the condition

A note on aggregation modes:

If a switch has a remote primary target, it will not hear any command to its target on its own bus.  Therefore, the controller must adjust the LED of the switch itself.  In aggregation mode, the controller will  maintain a status of the remote target and adjust the LED itself.   This is achieved by the controller through subscription to the status of the target on the controller that has the lights to track.  Both the controller with the switch AND the controller with the lights to reflect status for must be a PRO level controller.

• Aggregation target (managed) 
  • Requires a pro controller on both sides.
  • LED will be turned on when the remote target is turned on and off when the remote target is turned off.
• Aggregation inverted target (managed)
  • Requires a pro controller on both sides.
  • LED will be turned on when the remote target is turned off and on when the remote target is turned off.
• Aggregation last heard scene (managed)
  • Requires a pro controller on both sides.
  • LED will be turned on when the last scene that the remote target heard is the scene marked in the application behaviour.  It will only turn off when a different scene is sent.  Other lighting commands will not affect last heard scene.
• Aggregation at scene (managed)
  •  Requires a pro controller on both sides.
  • LED will be turned on when remote target hears the scene marked in the application behaviour.  Any other lighting command that changes the light level of the device will turn the led off (eg recall max, off, min, a different scene, step up or step down).

A colour can also be set for applicable push buttons which change the colour of the LED.

Push button additions as of version 0.8.39

Several additions have been made to the push button configurations since the initial release to the cloud:

• The emergency timer type now has configurable behaviour
  • Users are now able to set the type of test to be run when the button is pushed
  • Duration types will also have a second configurable field which is how long the test will run for
• Custom non-arc types now have more behaviour options added to the command dropdowns
  • These include things such as starting tests, changing to specific profiles that are assigned to the gateway as well as changing to sticky profiles

A new warning has been added in the grid if there are any control systems under version 0.8.39 which is required to support these new features

Push button additions as of version 0.9.0

• More override types added
  • Lockout without switch
  • Lockout with switch
  • Switch overrides
• Apply override column has been added, which indicates how the override is applied

Push button additions as of version 1.5.5

Push buttons can now target DMX channels.