Lutron Binding

This binding integrates with Lutron lighting control systems. It contains binding code for three different types of Lutron systems. The first is for RadioRA 2 and other systems that can be controlled by Lutron Integration Protocol, such as Caseta and Homeworks QS. The second is for the original RadioRA system, referred to here as RadioRA Classic. The third is for Grafik Eye 3x/4x systems with GRX-PRG or GRX-CI-PRG. Each is described in a seperate section below.

Lutron RadioRA 2 Binding

Note: While the integration protocol used by this binding should largely be compatible with other Lutron systems such as Homeworks QS, this binding has only been tested with RadioRA 2 and, to a lesser extent, Caseta. Homeworks QS support is still a work in progress.

Supported Things

This binding currently supports the following thing types:

  • dimmer - Dimmer
  • switch - Switch or relay module
  • cco - Contact closure output module
  • occupancysensor - occupancy/vacancy sensor
  • keypad - seeTouch Keypad or Hybrid seeTouch Keypad
  • ttkeypad - Tabletop seeTouch Keypad
  • pico - Pico Keypad
  • vcrx - Visor control receiver
  • virtualkeypad - Repeater virtual keypad
  • shade - Lutron shade or motorized drape

Discovery

Full discovery is supported for RadioRA 2 systems. Discovered RadioRA 2 main repeaters will be accessed using the default lutron integration credentials. These can be changed in the main repeater thing configuration.

Note: Discovery of devices paired with a bridge may work on systems other than RadioRA 2. However, the bridge itself will need to be manually added as bridge discovery is only supported for RadioRA 2.

Binding Configuration

This binding does not require any special configuration.

Thing Configuration and Usage

Each Lutron thing requires the integration ID of the corresponding item in the Lutron system. The integration IDs can be retrieved from the integration report generated by the Lutron software. If a thing will not come online, but instead has the status "UNKNOWN: Awaiting initial response", it is likely that you have configured the wrong integration ID for it.

Bridge

The bridge may currently be a RadioRA 2 main repeater or a Caseta Smart Bridge Pro. A Homeworks QS Processor should also work, but support is still experimental. The bridge configuration requires the IP address of the bridge as well as the telnet username and password to log in to the bridge. The optional advanced parameter heartbeat can be used to set the interval between connection keepalive heartbeat messages, in minutes. It defaults to 5. Note that the handler will wait up to 30 seconds for a heartbeat response before attempting to reconnect. The optional advanced parameter reconnect can be used to set the connection retry interval, in minutes. It also defaults to 5.

Thing lutron:ipbridge:radiora2 [ ipAddress="192.168.1.2", user="lutron", password="integration" ]

Dimmers

Dimmers can optionally be configured to specify a fade in and fade out time in seconds using the fadeInTime and fadeOutTime parameters. In the thing file, this looks e.g. like:

Thing lutron:dimmer:livingroom (lutron:ipbridge:radiora2) [ integrationId=8, fadeInTime=0.5, fadeOutTime=5 ]

Shades

Each Lutron shade or motorized drape is controlled by a “shade” thing. The only configuration parameter it accepts is integrationId.

A single channel shadelevel with item type Rollershutter and category Rollershutter will be created for each shade thing. It accepts Percent, Up, Down, Stop and Refresh commands. Sending a Percent command will cause the shade to immediately move so as to be open the specified percentage. You can also read the current shade level from the channel. It is specified as a percentage, where 0% = closed and 100% = fully open. Movement delays are not currently supported. The shade handler should be compatible with all Lutron devices which appear to the system as shades, including roller shades, honeycomb shades, pleated shades, roman shades, tension roller shades, drapes, and Kirbe vertical drapes.

Note: While a shade is moving, the Lutron system will report the target level for the shade rather than the actual current level.

Example:

Thing lutron:shade:libraryshade (lutron:ipbridge:radiora2) [ integrationId=33]

Switches

Switches take no additional parameters besides integrationId.

Example:

Thing lutron:switch:porch (lutron:ipbridge:radiora2) [ integrationId=8 ]

CCO Modules

Contact closure output (cco) things accept outputType and pulseLength parameters. The outputType parameter is a string that should be set to "Pulsed" for pulsed CCOs or "Maintained" for non-pulsed CCOs. The default is "Pulsed", since this is generally the safer wrong setting. The pulseLength parameter sets the pulse length in seconds for a pulsed output. It can range from 0.25 to 99.0 seconds and defaults to 0.5. It is ignored if outputType="Maintained". Be aware that the Lutron controller may round the pulse length down to the nearest 0.25 seconds.

The ccopulsed and ccomaintained things are just cco things with the outputType fixed. They are used by autodiscovery to automatically set the correct output type. You can also use them in manual configurations, if you prefer. This may be a good idea if you are interfacing to sensitive equipment where accidentally setting the wrong output type might cause equipment damage.

Example:

Thing lutron:cco:garage (lutron:ipbridge:radiora2) [ integrationId=5, outputType="Pulsed", pulseLength=0.5 ]
Thing lutron:ccopulsed:gate (lutron:ipbridge:radiora2) [ integrationId=6, pulseLength=0.25 ]
Thing lutron:ccomaintained:relay1 (lutron:ipbridge:radiora2) [ integrationId=7 ]

Each cco thing creates one switch channel. For pulsed CCOs, sending an ON command will close the output for the configured pulse time. Sending an OFF command does nothing. Because of limitations in RadioRA 2, you cannot monitor the state of a pulsed CCO. Therefore, the channel state will only transition OFF->ON->OFF when you send a ON command.

For maintained CCOs, sending ON and OFF commands works as expected, and the channel state updates as expected when either OpenHAB commands or external events change the CCO device state.

Occupancy Sensors

An occupancysensor thing interfaces to Lutron Radio Powr Savr wireless occupancy/vacancy Sensors. It accepts no configuration parameters other than integrationID.

Example:

Thing lutron:occupancysensor:shopsensor (lutron:ipbridge:radiora2) [ integrationId=7 ]

The binding creates one occupancystatus channel, Item type Switch, category Motion, read-only state. The channel state can be monitored for occupied (ON) or unoccupied (OFF) events coming from the sensor. It ignores all commands. The sensors cannot be queried for their state, so initial channel state at startup will be undefined (NULL).

SeeTouch and Hybrid SeeTouch Keypads

SeeTouch and Hybrid SeeTouch keypads are interfaced with using the keypad thing. In addition to the usual integrationID parameter, they expect model and autorelease parameters. The model parameter should be set to the Lutron keypad model number. This will cause the handler to create only the appropriate channels for that particular keypad model. The default is "Generic", which will cause the handler to create all possible channels, some of which will likely not be appropriate for your model.

The autorelease parameter is a boolean. Setting it to true will cause each button channel state to transition back to OFF (released) automatically after a going to ON when a button is pressed. Normally, a Lutron keypad will send a "pressed" event when a button is pressed, and a "released" event when it is released. The handler will set the button channel state to ON when it receives the "pressed" event, and "off" when it receives the "released" event. This allows you to take actions on both state changes. However, some integration applications such as Lutron Home+ only cause a "pressed" event to be generated when remotely "pressing" a button. A "release" is never sent, therefore the button channel would become "stuck" in the ON state. To prevent this the autorelease parameter defaults to true. If you do not use integration applications that exhibit this sort of anti-social behavior and you wish to trigger rules on both button press and release, you should set autorelease to false.

The autorelease parameter also effects behavior when sending an ON command to a button channel to trigger a remote button press. If autorelease is set, the handler will send action "release" to the device component immediately after sending action "press". When the controller responds, the channel state will be transitioned back to OFF.

Example:

Thing lutron:keypad:entrykeypad (lutron:ipbridge:radiora2) [ integrationId=10, model="W7B" autorelease="true" ]

A channel with item type Switch and category Switch is created for each button, and a channel with item type Switch and category Light is created for each button indicator LED. You can monitor button channels for ON and OFF state changes to indicate button presses and releases, and send ON and OFF commands to remotely press and release buttons. Ditto for the indicator LED channels. Note, however, that version 11.6 or higher of the RadioRA 2 software may be required in order to drive keypad LED states, and then this may only be done on unbound buttons.

When using auto-discovery, remember to select the correct value for the model parameter after accepting the keypad thing from the inbox. The correct channels will then be automatically configured.

Tabletop SeeTouch Keypads

Tabletop SeeTouch keypads use the ttkeypad thing. It accepts the same integrationID, model, and autorelease parameters and creates the same channels as the keypad thing. See the discussion above for a full discussion of configuration and use.

Example:

Thing lutron:ttkeypad:bedroomkeypad (lutron:ipbridge:radiora2) [ integrationId=11, model="T10RL" autorelease="true" ]

When using auto-discovery, remember to select the correct value for the model parameter after accepting the ttkeypad thing from the inbox. The correct channels will then be automatically configured.

Pico Keypads

Pico keypads use the pico thing. It accepts the same integrationID, model, and autorelease parameters and creates the same channels as the keypad and ttkeypad things. The only difference is that no LED channels will be created, since Pico keypads have no indicator LEDs. See the discussion above for a full discussion of configuration and use.

Example:

Thing lutron:pico:hallpico (lutron:ipbridge:radiora2) [ integrationId=12, model="3BRL", autorelease="true" ]

When using auto-discovery, remember to select the correct value for the model parameter after accepting the pico thing from the inbox. The correct channels will then be automatically configured.

VCRX

The Lutron VCRX appears to OpenHAB as multiple devices. The 6 buttons (which can be activated remotely by HomeLink remote controls), 6 corresponding LEDs, and 4 contact closure inputs (CCIs) are handled by the vcrx thing, which behaves like a keypad. The contact closure outputs (CCOs) have their own integration IDs and are handled by the cco thing.

Supported options are integrationId and autorelease. Supplying a model is not required, as there is only one model.

Example:

Thing lutron:vcrx:vcrx1 (lutron:ipbridge:radiora2) [ integrationId=13, autorelease="true" ]

CCI channels are created with item type Contact and category Switch. They are marked as Advanced, so they will not be automatically linked to items in the Paper UI's Simple Mode. They accept ON/OFF commands and present ON/OFF states the same as a keypad button. Note that the autorelease option also applies to CCI channels.

Virtual Keypads

The virtualkeypad thing is used to interface to the virtual buttons on the RadioRA 2 main repeater. These are sometimes referred to in the documentation as phantom buttons or integration buttons, and are used only for integration. There are 100 of these virtual buttons, and 100 corresponding virtual indicator LEDs.

Example:

Thing lutron:virtualkeypad:repeaterbuttons (lutron:ipbridge:radiora2) [ integrationId=1, autorelease="true" ]

The behavior of this binding is the same as the other keypad bindings, with the exception that the button and led channels created have the Advanced flag set.

Channels

The following channels are supported:

Thing Type Channel ID Item Type Description
dimmer lightlevel Dimmer Increase/decrease the light level
switch switchstatus Switch On/off status of the switch
occupancysensor occupancystatus Switch Occupancy status
cco switchstatus Switch On/off status of the CCO
keypads (all) button* Switch Keypad button
keypads(except pico) led* Switch LED indicator for the associated button
vcrx cci* Contact Contact closure input on/off status
shade shadelevel Rollershutter Accepts Up, Down, Stop, & Percent commands

The channels available on each keypad device (i.e. keypad, ttkeypad, pico, vcrx, and virtualkeypad) will vary with keypad type and model. Appropriate channels will created automatically by the keypad, ttkeypad, and pico handlers based on the setting of the "model" parameter for those thing types.

Full Example

demo.Things:

lutron:dimmer:theater (lutron:ipbridge:radiora2) [ integrationId=8, fadeOutTime=2 ]
lutron:occupancysensor:theater (lutron:ipbridge:radiora2) [ integrationId=9 ]
lutron:keypad:theater (lutron:ipbridge:radiora2) [ integrationId=10 ]

demo.items:

Dimmer TheaterLights { channel="lutron:dimmer:theater:lightlevel" }
Switch TheaterMotion { channel="lutron:occupancysensor:theater:occupancystatus" }
Switch TheaterScene1 { channel="lutron:keypad:theater:button1" }
Switch TheaterScene2 { channel="lutron:keypad:theater:button2" }

Lutron RadioRA (Classic) Binding

This binding integrates with the legacy Lutron RadioRA (Classic) lighting system.

This binding depends on RS232 communication. It has only been tested using the Chronos time module but the RS232 module should work as well.

Supported Things

This binding currently supports the following thing types:

Thing Type ID Description
ra-rs232 Bridge RadioRA device that supports RS232 communication
ra-dimmer Thing Dimmer control
ra-switch Thing Switch control
ra-phantomButton Thing Phantom Button to control multiple controls (Scenes)

Thing Configurations

Thing Config Description
ra-rs232 portName The serial port to use to communicate with Chronos or RS232 module
baud (Optional) Baud Rate (defaults to 9600)
ra-dimmer zoneNumber Assigned Zone Number within the Lutron RadioRA system
fadeOutSec (Optional) Time in seconds dimmer should take when lowering the level
fadeInSec (Optional) Time in seconds dimmer should take when lowering the level
ra-switch zoneNumber Assigned Zone Number within the Lutron RadioRA system
ra-phantomButton buttonNumber Phantom Button Number within the Lutron RadioRA system

Channels

The following channels are supported:

Thing Type Channel ID Item Type Description
ra-dimmer lightlevel Dimmer Increase/Decrease dimmer intensity
ra-switch/ra-phantomButton switchstatus Switch On/Off state of switch

Example

lutronradiora.things

Bridge lutronradiora:ra-rs232:chronos1 [portName="/dev/ttys002"] {
    Thing ra-dimmer dimmer1 [ zoneNumber=1 ]
    Thing ra-dimmer dimmer2 [ zoneNumber=2 ]
    Thing ra-switch switch1 [ zoneNumber=3 ]
    Thing ra-switch switch2 [ zoneNumber=4 ]
    Thing ra-phantomButton1 phantomButton1 [ buttonNumber=1 ]
}

lutronradiora.items

Dimmer Dimmer_Kitchen "Kitchen Lights" { channel="lutronradiora:dimmer:chronos1:dimmer1:lightlevel" }
Dimmer Dimmer_FamilyRoom "Family Room Lights" { channel="lutronradiora:dimmer:chronos1:dimmer2:lightlevel" }
Switch Switch_Patio "Patio Light" { channel="lutronradiora:dimmer:chronos1:switch1:switchstatus" }
Switch Switch_FrontDoor "Front Door Lights" { channel="lutronradiora:switch:chronos1:switch2:switchstatus" }
Switch Phantom_Movie "Movie Scene" { channel="lutronradiora:phantomButton:chronos1:phantomButton1:switchstatus" }

Legacy HomeWorks RS232 (Serial) Processors

The binding supports legacy HomeWorks processors that interface with a Serial RS232 connection. To connect to such a system, you would need to use a RS232 -> USB adapter (assuming you don't have a serial port).

Please see HomeWorks RS232 Protocol Guide for information on the protocol.

Supported Things

  • HomeWorks RS232-connected Processor Units
  • Dimmers

Supported in future updates:

  • Keypads
  • Keypad LEDs

Discovery

This binding supports active and passive discovery. It will detect dimmers as they are manually raised or lowered, or can be made to scan for configured dimmer modules.

Thing Configuration

The bridge requires the port location (e.g., /dev/ttyUSB1 or COM1) and the baud rate. The default baud rate for HomeWorks processors is set to 9600.

lutron:hwserialbridge:home [serialPort="/dev/ttyUSB1", baudRate="9600]

Dimmers have one required parameter address that specifies the device address (e.g., [01:01:03:02:04]) and two optional parameters: fadeTime which sets the time it takes to set the light level when changed, and defaultLevel which sets the level to use for the dimmer when turning it on (with a switch rather than a slider).

lutron:hwdimmer:dimmer1 [address="[01:01:03:02:04]", fadeTime="1", defaultLevel="75"] 

Channels

The following channels are supported:

Thing Type Channel Type ID Item Type Description
dimmer lightlevel Dimmer Increase/decrease the light level

Lutron Grafik Eye 3x/4x binding via GRX-PRG or GRX-CI-PRG

This lutron binding will also work with Grafik Eye 3x/4x systems in conjuction with the GRX-PRG or GRX-CI-PRG interfaces. Please see RS232ProtocolCommandSet for more information.

Supported Things

1-8 Grafik Eye 3x/4x System(s) through the interface

Discovery

This binding does not support discovery of the GRX-PRG or GRX-CI-PRG. You will need to specify them directly.

Thing Configuration

The bridge requires the IP address/Host name of the bridge. Optionally, you may specify the username (defaults to 'nwk') and retryPolling (in seconds) to retry connections if the connection fails (defaults to 10 seconds). This bridge does support two way communication with the Grafik Eye units (if a scene is selected or a zone changed on the unit or via a keypad, that information is immediately available in openhab).

lutron:prgbridge:home [ ipAddress="192.168.1.51", user="nwk", retryPolling=10 ]

The Grafik Eye thing requires the control unit address (1-8). Optionally you may specify the default fade time (when raising/lowering zones or setting zone intensities) and polling time (in seconds) to refresh the state from the Grafik Eye (defaults to 30 seconds). If any of the zones control a QED shade (via the SG/SO-SVCN/SVCI keypad), those zones should be listed (comma separated list) in the shadeZones.

lutron:grafikeye:home (lutron:prgbridge:home) [ controlUnit=1, fade=10, polling=30, shadeZones="2,3,4" ]

Channels

Bridge channels

Channel Type ID Readonly Item Type Description
zonelowerstop No Switch Stops zone lowering on all control units
zoneraisestop No Switch Stops zone raising on all control units
timeclock No DateTime Current time on the PRG
schedule No Number Current Schedule (0=Disabled, 1=Weekday, 2=Weekend)
sunrise Yes DateTime Time of Sunrise
sunset Yes DateTime Time of Sunset
ssstart No Switch Starts the Super Sequence
sspause No Switch Pauses the Super Sequence
ssresume No Switch Resumes the Super Sequence
ssstatus Yes String Status of the Super Sequence (R=Running, S=Stopped)
ssnextstep Yes Number Next sequence number in the Super Sequence
ssnextminute Yes Number How many minutes until the next step in the Super Sequence
ssnextsecond Yes Number How many seconds until the next step in the Super Sequence
buttonpress Yes String Last keypad button pressed (see Appendix A) in protocol guide

Grafik Eye channels

Channel Type ID Readonly Item Type Description
scene No Number The current scene
scenelock No Switch Locks/unlocks the current scene
sceneseq No Switch Starts/Stops the scene sequence
zonelock No Switch Locks/unlocks the zones
zonefade No Number The seconds to fade from one intensity to the next
zonelowerX No Switch Lowers the specified zone
zoneraiseX No Switch Raises the specified zone
zoneintensityX No Number Specifies the zone intensity
zoneshadeX No Rollershutter Specifies the shade zone

Notes

  • The "buttonpress" channel reports which keypad button was pressed. DIP switch 6 must be set on the interface for this to be reported. The "buttonpress" channel is only useful in rules to take action when a specific button (on a specific keypad) has been pressed.
  • Sunset/sunrise will only be available if configured via the Liasion software
  • scenelock, sceneseq, zonelock cannot be determined from the API and will default to OFF on startup
  • Replace the "X" on zonelowerX, zoneraiseX, etc with the zone in question. "zonelower1" will affect zone 1. Specifying a zone larger than you have will have no effect (such as using zonelower8 on a Grafik Eye 3506 which only has 6 zones).
  • The zonefade value will only be used when zonelower/zonereaise/zoneintensity is issued.
  • zoneshade does not support PercentType nor StopMoveType.Move and those commands will be ignored
  • zoneintensity can be used on a shade zone if the intensity is from 0 to 5 and should be used if wanting to set a QED preset: 0=Stop, 1=Open, 2=Close, 3=Preset 1, 4=Preset 2, 5=Preset 3
  • If you started a zonelower or zoneraise, the only way to stop the action is by executing an all zone stop on the bridge (i.e. zonelowerstop or zoneraisestop). The PRG API does not provide a way to stop the lowering/raising of any specific zone.

Example

demo.Things:

lutron:prgbridge:home [ ipAddress="192.168.1.51", user="nwk", retryPolling=10 ]
lutron:grafikeye:home (lutron:prgbridge:home) [ controlUnit=1, fade=10, polling=10 ]

demo.items:

String Prg_ButtonPress "Last Button Press [%s]" { channel = "lutron:prgbridge:home:buttonpress" }
Switch Prg_ZoneLowerStop "Zone Lower Stop" { channel = "lutron:prgbridge:home:zonelowerstop",autoupdate="false" }
Switch Prg_ZoneRaiseStop "Zone Raise Stop" { channel = "lutron:prgbridge:home:zoneraisestop",autoupdate="false" }
DateTime Prg_Time "Current Time: [%1$tF %1$tr]" { channel="lutron:prgbridge:home:timeclock" }
Number Prg_Schedule "Schedule [%s]" { channel="lutron:prgbridge:home:schedule" }
DateTime Prg_Sunrise "Sunrise [%1$tF %1$tr]" { channel="lutron:prgbridge:home:sunrise" }
DateTime Prg_Sunset "Sunset [%1$tF %1$tr]" { channel="lutron:prgbridge:home:sunset" }
Switch Prg_Start "Super Schedule Start" { channel="lutron:prgbridge:home:ssstart", autoupdate="false"  }
Switch Prg_Pause "Super Schedule Pause" { channel="lutron:prgbridge:home:sspause", autoupdate="false"  }
Switch Prg_Resume "Super Schedule Resume" { channel="lutron:prgbridge:home:ssresume", autoupdate="false"  }
String Prg_Status "Super Schedule Status [%s]" { channel="lutron:prgbridge:home:ssstatus" }
Number Prg_NextStep "Super Schedule Next Step [%s]" { channel="lutron:prgbridge:home:ssnextstep" }
Number Prg_NextMinute "Super Schedule Next Step Minutes [%s]" { channel="lutron:prgbridge:home:ssnextminute" }
Number Prg_NextSecond "Super Schedule Next Step Seconds [%s]" { channel="lutron:prgbridge:home:ssnextsecond" }

Number Grx_Scene "Scene [%s]" { channel="lutron:grafikeye:home:scene" }
Switch Grx_SceneLock "Scene Lock" { channel="lutron:grafikeye:home:scenelock" }
Switch Grx_SceneSeq "Scene Sequence" { channel="lutron:grafikeye:home:sceneseq" }
Switch Grx_ZoneLock "Zone Lock" { channel="lutron:grafikeye:home:zonelock" }
Switch Grx_ZoneLower1 "Zone 1 Lower" { channel="lutron:grafikeye:home:zonelower1" }
Switch Grx_ZoneLower2 "Zone 2 Lower" { channel="lutron:grafikeye:home:zonelower2" }
Switch Grx_ZoneLower3 "Zone 3 Lower" { channel="lutron:grafikeye:home:zonelower3" }
Switch Grx_ZoneLower4 "Zone 4 Lower" { channel="lutron:grafikeye:home:zonelower4" }
Switch Grx_ZoneLower5 "Zone 5 Lower" { channel="lutron:grafikeye:home:zonelower5" }
Switch Grx_ZoneLower6 "Zone 6 Lower" { channel="lutron:grafikeye:home:zonelower6" }
Switch Grx_ZoneLower7 "Zone 7 Lower" { channel="lutron:grafikeye:home:zonelower7" }
Switch Grx_ZoneLower8 "Zone 8 Lower" { channel="lutron:grafikeye:home:zonelower8" }
Switch Grx_ZoneRaise1 "Zone 1 Raise" { channel="lutron:grafikeye:home:zoneraise1" }
Switch Grx_ZoneRaise2 "Zone 2 Raise" { channel="lutron:grafikeye:home:zoneraise2" }
Switch Grx_ZoneRaise3 "Zone 3 Raise" { channel="lutron:grafikeye:home:zoneraise3" }
Switch Grx_ZoneRaise4 "Zone 4 Raise" { channel="lutron:grafikeye:home:zoneraise4" }
Switch Grx_ZoneRaise5 "Zone 5 Raise" { channel="lutron:grafikeye:home:zoneraise5" }
Switch Grx_ZoneRaise6 "Zone 6 Raise" { channel="lutron:grafikeye:home:zoneraise6" }
Switch Grx_ZoneRaise7 "Zone 7 Raise" { channel="lutron:grafikeye:home:zoneraise7" }
Switch Grx_ZoneRaise8 "Zone 8 Raise" { channel="lutron:grafikeye:home:zoneraise8" }
Number Grx_ZoneFade "Zone Fade [%s sec]" { channel="lutron:grafikeye:home:zonefade" }
Dimmer Grx_ZoneIntensity1 "Zone 1 Intensity [%d %%]" { channel="lutron:grafikeye:home:zoneintensity1" }
Dimmer Grx_ZoneIntensity2 "Zone 2 Intensity [%d %%]" { channel="lutron:grafikeye:home:zoneintensity2" }
Dimmer Grx_ZoneIntensity3 "Zone 3 Intensity [%d %%]" { channel="lutron:grafikeye:home:zoneintensity3" }
Dimmer Grx_ZoneIntensity4 "Zone 4 Intensity [%d %%]" { channel="lutron:grafikeye:home:zoneintensity4" }
Dimmer Grx_ZoneIntensity5 "Zone 5 Intensity [%d %%]" { channel="lutron:grafikeye:home:zoneintensity5" }
Dimmer Grx_ZoneIntensity6 "Zone 6 Intensity [%d %%]" { channel="lutron:grafikeye:home:zoneintensity6" }
Dimmer Grx_ZoneIntensity7 "Zone 7 Intensity [%d %%]" { channel="lutron:grafikeye:home:zoneintensity7" }
Dimmer Grx_ZoneIntensity8 "Zone 8 Intensity [%d %%]" { channel="lutron:grafikeye:home:zoneintensity8" }
Rollershutter Grx_ZoneShade1 "Zone 1 Shade" { channel="lutron:grafikeye:home:zoneshade1" }
Rollershutter Grx_ZoneShade2 "Zone 2 Shade" { channel="lutron:grafikeye:home:zoneshade2" }
Rollershutter Grx_ZoneShade3 "Zone 3 Shade" { channel="lutron:grafikeye:home:zoneshade3" }
Rollershutter Grx_ZoneShade4 "Zone 4 Shade" { channel="lutron:grafikeye:home:zoneshade4" }
Rollershutter Grx_ZoneShade5 "Zone 5 Shade" { channel="lutron:grafikeye:home:zoneshade5" }
Rollershutter Grx_ZoneShade6 "Zone 6 Shade" { channel="lutron:grafikeye:home:zoneshade6" }
Rollershutter Grx_ZoneShade7 "Zone 7 Shade" { channel="lutron:grafikeye:home:zoneshade7" }
Rollershutter Grx_ZoneShade8 "Zone 8 Shade" { channel="lutron:grafikeye:home:zoneshade8" }

Lutron, GRAFIK Eye, HomeWorks, Pico, Caseta, RadioRA, and seeTouch are trademarks of Lutron Electronics Co., Inc. HomeLink is a registered trademark of Gentex Corporation. This software and its associated documentation are not endorsed or approved by Lutron Electronics Co.