How To Unbound A Orvibo Camera

# Lutron Binding

This bounden integrates with Lutron (opens new window) lighting command and home automation systems. It contains dissever binding support for 4 dissimilar types of Lutron systems:

• RadioRA 2, HomeWorks QS, and other systems that can be controlled by Lutron Integration Protocol, such as RA2 Select, and Caseta Pro
• The original RadioRA system, referred to here as RadioRA Classic
• Legacy HomeWorks RS232 Processors
• Grafik Center 3x/4x systems with GRX-PRG or GRX-CI-PRG control interfaces

Each is described in a separate section beneath.

# Lutron RadioRA ii/HomeWorks QS Binding

Note: While the integration protocol used by this bounden should largely be compatible with other electric current Lutron systems, this binding has only been fully tested with RadioRA 2, HomeWorks QS, and Caseta with Smart Bridge Pro. Homeworks QS support is still a work in progress, since not all features/devices are supported yet. RA2 Select systems have been reported to work with the binding, but full support is nevertheless unconfirmed. The binding has not been tested with Quantum, QS Standalone, or myRoom Plus systems.

Note: Caseta support is but possible with the Smart Bridge Pro hub. The standard Caseta hub does non back up Lutron Integration Protocol.

# Supported Things

This binding currently supports the following thing types:

• ipbridge - The Lutron main repeater/processor/hub
• dimmer - Dimmer or fan controller
• switch - Switch or relay module
• occupancysensor - Occupancy/vacancy sensor
• keypad - Lutron seeTouch or Hybrid seeTouch Keypad
• ttkeypad - Tabletop seeTouch Keypad
• intlkeypad - International seeTouch Keypad (HomeWorks QS just)
• palladiomkeypad - Palladiom Keypad (HomeWorks QS only)
• pico - Pico Keypad
• grafikeyekeypad - GRAFIK Eye QS Keypad (RadioRA ii/HomeWorks QS simply)
• virtualkeypad - Repeater/processor integration buttons or Caseta Smart Bridge scene buttons
• vcrx - Visor command receiver module (VCRX)
• qsio - QS IO Interface (HomeWorks QS but)
• wci - QS Wallbox Closure Interface (WCI) (HomeWorks QS only)
• cco - Contact closure output module or VCRX CCO
• shade - Lutron shade, motorized mantle, or motor controller
• blind - Lutron venetian bullheaded or horizontal sheer blind [Experimental]
• greenmode - Greenish Mode subsystem
• timeclock - Scheduling subsystem
• sysvar - Arrangement land variable (HomeWorks QS only) [Experimental]

# Discovery

Full discovery is supported for RadioRA ii and HomeWorks QS systems. Both the principal repeaters/processors themselves and the devices connected to them tin can exist automatically discovered. Discovered repeaters/processors volition exist accessed using the default integration credentials. These can be inverse in the bridge thing configuration. Discovered keypad devices should now accept their model parameters automatically set to the correct value.

Caseta Smart Bridge PRO 2 hubs and RA2 Select master repeaters should at present exist discovered automatically via mDNS. Devices attached to them still need to be configured manually.

Other supported Lutron systems must be configured manually.

# Binding Configuration

This bounden does not crave any special configuration.

# Thing Configuration and Usage

Each Lutron matter requires the integration ID of the corresponding detail in the Lutron organisation. The integration IDs can exist retrieved from the integration written report generated past the Lutron software. If a thing volition not come online, but instead has the status "UNKNOWN: Awaiting initial response", it is likely that you take configured the wrong integration ID for it.

# Bridge

A bridge may currently exist a RadioRA 2 main repeater, a HomeWorks QS Processor, a Caseta Smart Bridge Pro, or a RA2 Select main repeater. The bridge configuration requires the IP address of the bridge equally well as the telnet username and password to log in to the bridge.

It is recommended that chief repeaters/processors be configured with static IP addresses. Yet if automated discovery is used, the bridge thing volition work with DHCP-configured addresses.

The optional advanced parameter heartbeat tin can exist used to set the interval betwixt connectedness keepalive heartbeat messages, in minutes. It defaults to five. Note that the handler will wait upwardly to 30 seconds for a heartbeat response before attempting to reconnect. The optional advanced parameter reconnect tin be used to set the connection retry interval, in minutes. It also defaults to five.

The optional advanced parameter delay tin exist used to fix a filibuster (in milliseconds) between transmission of integration commands to the bridge device. This may be used for command transport charge per unit throttling. It tin can be gear up to an integer value between 0 and 250 ms, and defaults to 0 (no filibuster). It is recommended that this parameter exist left at the default unless y'all experience problems with sent commands being dropped/ignored. This has been reported in some rare cases when large numbers of commands were sent in short periods to Caseta hubs. If you feel this problem, effort setting a delay value of around 100 ms as a starting point.

The optional avant-garde parameter discoveryFile tin can be set to forcefulness the device discovery service to read the Lutron configuration XML from a local file rather than retrieving it via HTTP from the RadioRA 2 or HomeWorks QS bridge device. This is useful in the instance of some older Lutron software versions, where the discovery service may have problems retrieving the file from the span device. Note that the user which openHAB runs under must accept permission to read the file.

Thing configuration file example:

# Dimmers

Dimmers tin optionally exist configured to specify a default fade in and fade out time in seconds using the fadeInTime and fadeOutTime parameters. These are used for ON and OFF commands, respectively, and default to 1 second if not set. Commands using a specific percent value will use a default fade time of 0.25 seconds.

Dimmers also support the optional advanced parameters onLevel and onToLast. The onLevel parameter specifies the level to which the dimmer volition get when sent an ON command. It defaults to 100. The onToLast parameter is a boolean that defaults to false. If ready to "truthful", the dimmer volition go to its final non-nil level when sent an ON command. If the last non-goose egg level cannot be determined, the value of onLevel will be used instead.

A dimmer thing has a unmarried channel lightlevel with type Dimmer and category DimmableLight.

Thing configuration file instance:

The dimmer thing supports the thing action setLevel(Double level, Double fadeTime, Double delayTime) for automation rules.

The parameters are:

• level The new light level to fix (0-100)
• fadeTime The time in seconds over which the dimmer should fade to the new level
• delayTime The time in seconds to delay before starting to fade to the new level

The fadeTime and delayTime parameters are meaning to ii digits afterward the decimal point (i.e. to hundredths of a second), but some Lutron systems may round the time to the nearest 0.25 seconds when processing the command. Times of 100 seconds or more will be rounded to the nearest integer value.

See below for an example rule using thing actions.

# Switches

Switches have no boosted parameters also integrationId. A switch thing has a single channel switchstatus with type Switch and category Switch.

Thing configuration file instance:

# Occupancy Sensors

An occupancysensor matter interfaces to Lutron Radio Powr Savr wireless occupancy/vacancy sensors. It accepts no configuration parameters other than integrationId.

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

Affair configuration file example:

# seeTouch and Hybrid seeTouch Keypads

seeTouch and Hybrid seeTouch keypads are interfaced with using the keypad affair. In addition to the usual integrationId parameter, it accepts model and autorelease parameters. The model parameter should be set up 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 volition cause the handler to create all possible channels, some of which volition likely not be appropriate for your model.

The autorelease parameter is a boolean. Setting it to true will crusade each button aqueduct land to transition back to OFF (released) automatically later a going to ON when a button is pressed. Ordinarily, a Lutron keypad will send a "pressed" issue when a push button is pressed, and a "released" result when information technology is released. The handler will fix the push channel state to ON when it receives the "pressed" event, and "off" when it receives the "released" result. This allows you to take deportment on both state changes. However, some integration applications such equally Lutron Dwelling+ just cause a "pressed" event to exist generated when remotely "pressing" a button. A "release" is never sent, therefore the button channel would become "stuck" in the ON country. To forbid this the autorelease parameter defaults to true. If you do not use integration applications that showroom this sort of anti-social behavior and you wish to trigger rules on both push button printing and release, you should fix autorelease to fake.

The autorelease parameter also effects behavior when sending an ON command to a push button aqueduct to trigger a remote push button press. If autorelease is ready, the handler will send action "release" to the device component immediately later on sending activity "press". When the controller responds, the channel state will exist transitioned dorsum to OFF.

A channel push[nn] with item type Switch and category Switch is created for each push, and a channel led[nn] with detail blazon 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 ship ON and OFF commands to remotely printing and release buttons. Ditto for the indicator LED channels. Notation, 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 simply be washed on unbound buttons.

Component numbering: For button and LED layouts and numbering, see the Lutron Integration Protocol Guide (rev. AA) p.104 (https://www.lutron.com/TechnicalDocumentLibrary/040249.pdf (opens new window) ). If you are having problems determining which channels have been created for a given keypad model, click on the thing nether Configuration/Things in the Paper UI, or run the command things show <thingUID> (due east.thousand. things testify lutron:keypad:radiora2:entrykeypad) from the openHAB CLI to list the channels.

Supported settings for model parameter: H1RLD, H2RLD, H3BSRL, H3S, H4S, H5BRL, H6BRL, HN1RLD, HN2RLD, HN3S, HN3BSRL, HN4S, HN5BRL, HN6BRL, W1RLD, W2RLD, W3BD, W3BRL, W3BSRL, W3S, W4S, W5BRL, W5BRLIR, W6BRL, W7B, Generic (default)

Thing configuration file instance:

Example rule triggered past a keypad button printing:

# Tabletop seeTouch Keypads

Tabletop seeTouch keypads utilize the ttkeypad thing. It accepts the aforementioned integrationId, model, and autorelease parameters and creates the same channel types every bit the keypad affair. See the keypad department above for a full discussion of configuration and use.

Component numbering: For button and LED layouts and numbering, see the Lutron Integration Protocol Guide (rev. AA) p.110 (https://www.lutron.com/TechnicalDocumentLibrary/040249.pdf (opens new window) ). If you are having problems determining which channels have been created for a given keypad model, click on the thing under Configuration/Things in the Paper UI, or run the command things bear witness <thingUID> (eastward.g. things testify lutron:ttkeypad:radiora2:bedroomkeypad) from the openHAB CLI to list the channels.

Supported settings for model parameter: T5RL, T10RL, T15RL, T5CRL, T10CRL, T15CRL, Generic (default)

Thing configuration file example:

# International seeTouch Keypads (HomeWorks QS)

International seeTouch keypads used in the HomeWorks QS system use the intlkeypad affair. Information technology accepts the aforementioned integrationId, model, and autorelease parameters and creates the same button and LED channel types as the keypad thing. Run across the keypad section above for a full discussion of configuration and use.

To back up this keypad's contact closure inputs, CCI channels named cci1 and cci2 are created with item type Contact and category Switch. They are marked as Avant-garde, and then they will non be automatically linked to items in the Newspaper UI'south Simple Mode. They nowadays ON/OFF states the aforementioned as a keypad button.

Component numbering: For button and LED layouts and numbering, run across the Lutron Integration Protocol Guide (rev. AA) p.107 (https://www.lutron.com/TechnicalDocumentLibrary/040249.pdf (opens new window) ). If you lot are having problems determining which channels have been created for a given keypad model, click on the thing nether Configuration/Things in the Newspaper UI, or run the command things prove <thingUID> (e.g. things show lutron:intlkeypad:hwprocessor:kitchenkeypad) from the openHAB CLI to list the channels.

Supported settings for model parameter: 2B, 3B, 4B, 5BRL, 6BRL, 7BRL, 8BRL, 10BRL / Generic (default)

Matter configuration file case:

# Palladiom Keypads (HomeWorks QS)

Palladiom keypads used in the HomeWorks QS system use the palladiomkeypad affair. Information technology accepts the same integrationId, model, and autorelease parameters and creates the aforementioned push button and LED aqueduct types as the keypad thing. See the keypad section higher up for a full discussion of configuration and use.

Component numbering: For button and LED layouts and numbering, come across the Lutron Integration Protocol Guide (rev. AA) p.95 (https://www.lutron.com/TechnicalDocumentLibrary/040249.pdf (opens new window) ). If you are having bug determining which channels have been created for a given keypad model, click on the thing under Configuration/Things in the Paper UI, or run the control things prove <thingUID> (east.g. things bear witness lutron:palladiomkeypad:hwprocessor:kitchenkeypad) from the openHAB CLI to listing the channels.

Supported settings for model parameter: 2W, 3W, 4W, RW, 22W, 24W, 42W, 44W, 2RW, 4RW, RRW

Thing configuration file case:

# Pico Keypads

Pico keypads use the pico thing. It accepts the same integrationId, model, and autorelease parameters and creates the aforementioned channel types as the keypad and ttkeypad things. The only deviation is that no LED channels will be created, since Pico keypads have no indicator LEDs. See the word to a higher place for a full discussion of configuration and apply.

Component numbering: For button layouts and numbering, see the Lutron Integration Protocol Guide (rev. AA) p.113 (https://world wide web.lutron.com/TechnicalDocumentLibrary/040249.pdf (opens new window) ). If you are having problems determining which channels have been created for a given keypad model, click on the thing under Configuration/Things in the Paper UI, or run the command things show <thingUID> (e.yard. things prove lutron:pico:radiora2:hallpico) from the openHAB CLI to list the channels.

Supported settings for model parameter: 2B, 2BRL, 3B, 3BRL, 4B, Generic (default)

Matter configuration file example:

# GRAFIK Heart QS Keypads (in RadioRA 2/HomeWorks QS systems)

GRAFIK Eye devices tin contain up to 6 lighting dimmers, a scene controller, a fourth dimension clock, and a front end panel with a column of 5 programmable scene buttons and 0 to 3 columns of programmable shade or lighting control buttons. They can exist used as peripheral devices in a RadioRA 2 or HomeWorks QS arrangement, or tin be used as stand-alone controllers that themselves tin can command other Lutron devices. The grafikeyekeypad thing is used to interface to the GRAFIK Middle QS front panel keypad when it is used in a RadioRA two or HomeWorks QS system. In this configuration, the integrated dimmers volition announced to openHAB equally split output devices.

If your GRAFIK Middle is being used as a stand up-lone device and is not integrated in to a RadioRA 2 or HomeWorks QS system, and so this is non the thing you are looking for. Y'all should instead be using the grafikeye thing (meet below).

The grafikeyekeypad thing accepts the aforementioned integrationId, model, and autorelease parameters and creates the aforementioned push button, LED, and CCI, channel types every bit the other keypad things (see higher up). The model parameter should be set up to indicate whether there are zero, one, two, or three columns of buttons on the left side of the panel. Note that this count does not include the column of 5 scene buttons always establish on the correct side of the panel.

To support the GRAFIK Centre'due south contact closure input, a CCI channel named cci1 will be created with particular type Contact and category Switch. It is marked equally Advanced, and then it will non exist automatically linked to items in the Paper UI's Simple Mode. It presents ON/OFF states the same as a keypad push button.

Component numbering: The buttons and LEDs on the GRAFIK Eye are numbered height to lesser, starting with the 5 scene buttons in a column on the right side of the panel, and then proceeding with the columns of buttons (if any) on the left side of the console, working left to right. If you lot are having bug determining which channels have been created for a given model setting, click on the affair under Configuration/Things in the Paper UI, or run the command things show <thingUID> (e.g. things show lutron:grafikeyekeypad:radiora2:theaterkeypad) from the openHAB CLI to list the channels.

Supported settings for model parameter: 0COL, 1COL, 2COL, 3COL (default)

Thing configuration file instance:

# Virtual Keypads

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

The virtualkeypad thing can also be used to interface to the Smart Bridge scene buttons on Caseta systems. This allows you to trigger your defined scenes via the virtual keypad buttons. For this to piece of work, the optional model parameter must be set to Caseta. When used with Caseta, no virtual indicator LED channels are created.

The behavior of this binding is the same as the other keypad bindings, with the exception that the push button and LED channels created have the Advanced flag prepare. This ways, among other things, that they will not be automatically linked to items in the Paper UI's Simple Mode.

In nearly cases the integrationId parameter should exist fix to one.

Supported settings for model parameter: Caseta, Other (default)

Thing configuration file example:

# VCRX Modules

The Lutron VCRX appears to openHAB every bit multiple devices. The 6 buttons (which can be activated remotely by HomeLink remote controls), half-dozen corresponding LEDs, and 4 contact closure inputs (CCIs) are handled by the vcrx thing, which behaves similar a keypad. The contact closure outputs (CCOs) have their ain integration IDs and are handled by the cco affair (see below).

Supported options are integrationId and autorelease. Supplying a model is not required, equally in that location is merely one model.

To support the contact closure inputs, CCI channels named cci[n] are created with item type Contact and category Switch. The VCRX security (Total/Flash) input controls both the cci1 and cci2 channels, while input connections 1 and 2 map to the cci3 and cci4 channels respectively. The cci channels are marked as Avant-garde, so they will not exist automatically linked to items in the Newspaper UI's Unproblematic Mode. They present OPEN/Airtight states but do not have commands since Contact items are read-merely in openHAB. Notation that the autorelease option does non utilize to CCI channels.

Thing configuration file example:

# QS IO Interface (HomeWorks QS)

The Lutron QS IO Interface (QSE-IO) appears to openHAB every bit multiple devices. The v contact closure inputs (CCIs) are handled by the qsio affair. The 5 contact closure outputs (CCOs) are handled past the cco thing (see below). The only configuration option is integrationId

To support the contact closure inputs, CCI channels named cci[n] are created with item type Contact and category Switch. They are marked equally Avant-garde, so they will not exist automatically linked to items in the Paper UI's Simple Manner. They present Open up/CLOSED states but do not accept commands as Contact items are read-only in openHAB.

Some functionality may depend on QSE-IO DIP switch settings. Come across the Lutron documentation for more data.

Thing configuration file instance:

# QS Wallbox Closure Interface (WCI) (HomeWorks QS only)

The Lutron Wallbox Closure Interface (QSE-CI-WCI) is used to interface to contact closure keypads. Information technology is handled past the wci matter. The eight button inputs appear to the HomeWorks organization every bit normal keypad buttons. There are also viii LEDs, although they are normally hidden and thus mainly useful for setup and diagnostics.

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

See the Lutron documentation for more information.

Matter configuration file case:

# 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 mostly the safer wrong setting. The pulseLength parameter sets the pulse length in seconds for a pulsed output. Information technology tin can range from 0.25 to 99.0 seconds and defaults to 0.5. Information technology is ignored if outputType="Maintained". Be enlightened that the Lutron controller may round the pulse length down to the nearest 0.25 seconds.

Note: The ccopulsed and ccomaintained things are now deprecated. You should use the cco thing with the appropriate outputType setting instead.

Each cco thing creates one switch channel called switchstatus. For pulsed CCOs, sending an ON command volition close the output for the configured pulse time. Sending an OFF command does nothing. Because of limitations in RadioRA ii, you cannot monitor the state of a pulsed CCO. Therefore, the aqueduct state will only transition OFF->ON->OFF when you lot send an 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 alter the CCO device state.

Matter configuration file example:

# Shades

Each Lutron shade, motorized drapery, or QS motor controller output (LQSE-4M-D) is controlled by a shade thing. The just configuration parameter it accepts is integrationId.

A unmarried channel shadelevel with item type Rollershutter and category Rollershutter will be created for each shade affair. It accepts Percent, Upwards, Down, End and Refresh commands. Sending a Percentage control will cause the shade to immediately move so as to be open the specified percentage. Y'all can likewise read the electric current shade level from the channel. Information technology is specified as a percentage, where 0% = closed and 100% = fully open up. Movement delays are not currently supported. The shade handler should be uniform 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.

Motor controller outputs on a LQSE-4M-D (HomeWorks QS only) behave similarly to a shade. The merely deviation is that percentages other than 0% and 100% will exist ignored, since arbitrary positioning is not supported by the hardware. The value of shadelevel for a motor will too always be either 0% or 100%, depending on whether the final control sent was Up or Downward.

Note: While a shade is moving to a specific level because of a Pct control, the system volition report the target level for the shade rather than the actual current level. While a shade is moving because of an Up or Down command, it volition report the previous level until it stops moving.

Matter configuration file case:

# Blinds [Experimental]

Each Lutron Sivoia QS Venetian Blind or Horizontal Sheer Bullheaded is controlled by a bullheaded thing. Too integrationId, it requires that the parameter type be set to either "Venetian" for venetian blinds or "Sheer" for horizontal sheer blinds. There is no default. If discovery is used, the type parameter will set automatically when the bullheaded thing is created.

Two channels, blindliftlevel and blindtiltlevel, with detail type Rollershutter and category Rollershutter will be created for each blind affair. They command the up/down motion and the slat tilt motions of the blinds, respectively. Each channel accepts Pct, Up, Downwardly, End and Refresh commands. Sending a Percent control volition cause the blind to immediately move so as to exist open up the specified percentage. You can besides read the current setting from each channel. It is specified as a percentage, where 0% = airtight and 100% = fully open. Motion delays are not currently supported.

Annotation: While a blind is moving to a specific level because of a Percent command, the Lutron system will written report the target position for the blind rather than the actual current position. While a blind is moving considering of an Up or Down control, it will report the previous level until it stops moving.

Note: Back up for Sivoia QS blinds is new and has been through very limited testing. Please comment on your utilise of it in the openHAB community forum.

Thing configuration file example:

# Greenish Fashion

Radio RA2 and HomeWorks QS systems have a "Green Mode" or "Light-green Button" feature which allows the system to be placed in to one or more user-defined power saving modes called "steps". Each step can take deportment such as trimming down the 100% level on selected lighting dimmers by a specified percentage, shutting off certain loads, modifying thermostat settings, etc. Typically step 1 is "Off" or "Normal", and step 2 is "Greenish Mode", however other steps may exist divers by the installer as desired.

The greenmode thing is used to interface to the green way subsystem. Information technology requires that the integrationId parameter be set to the ID of the green mode subsystem. This should generally be 22. It creates a single channel step that tin can exist used to set up or query the agile light-green mode step number.

Dissimilar other Lutron organisation state settings, the bounden is not automatically notified by the bridge device of changes to the electric current light-green manner pace. This may be due to a bug in the Lutron firmware. The handler can exist fix to poll for the active dark-green mode stride so that the binding will know if information technology has been changed past another station. The optional pollInterval configuration parameter controls how often the handler polls. Information technology can be set to anywhere between 0 and 240 minutes, and defaults to 15 minutes. A setting of 0 volition disabled polling. Yous can likewise initiate a poll at whatsoever time by sending a refresh control (RefreshType.REFRESH) to the step aqueduct. Note that it should usually be unnecessary for the poll interval to be set to less than 5-10 minutes, since the dark-green mode step typically changes rather infrequently and takes effect gradually.

Thing configuration file example:

# Timeclock

RadioRA 2 and Homeworks QS have timeclock subsystems that provide scheduled execution of tasks at set times, randomized times or at capricious offsets from local sunrise/sunset. The tasks executed depend on the currently selected timeclock mode (e.g. Normal, Abroad, Append) and the modes themselves are user-definable (RadioRA ii only). In addition, tasks can be individually executed, and enabled or disabled for scheduled execution.

The timeclock thing provides an interface to timeclock functions. It allows yous to go and gear up the current timeclock mode, get the electric current twenty-four hour period's sunrise and sunset times, execute a specific task, be notified when a task executes, and enable or disable tasks. The integrationId parameter must be ready to the ID of the timeclock subsystem.

Information technology creates the following 6 channels:

• clockmode - Gets or sets the electric current timeclock style.
• sunrise - The timeclock's local sunrise time for the current solar day. Read but. You must send a refresh command (RefreshType.REFRESH) to query the system for the current twenty-four hours's sunrise time, as it is not automatically updated.
• dusk - The timeclock's local dusk time for the current twenty-four hours. Read merely. You must send a refresh command to query the organization for the current twenty-four hours's sunset fourth dimension, equally information technology is non automatically updated.
• execevent - Updates with the alphabetize number of each executing upshot. Send an upshot'south index number to start execution of it.
• enableevent - Updates with an event'south index number when information technology is enabled. Send an event's index number to enable it.
• disableevent - Updates with an event'southward index number when it is disabled. Send an result's index number to disable it.

All channels except clockmode are marked as advanced.

Thing configuration file example:

Case rule to refresh sunrise/dusk channels daily and at restart:

# Arrangement State Variables (HomeWorks QS only) [Experimental]

HomeWorks QS systems allow for conditional programming logic based on state variables. The sysvar matter allows country variable values to be read and set from openHAB. This makes sophisticated integration schemes possible. Each sysvar thing represents 1 system country variable. It has a single aqueduct varstate with type Number and category Number. Automatic discovery of state variables is not yet supported. They must be manually configured.

Thing configuration file example:

# Channels

The following is a summary of channels for all RadioRA 2 binding things:

Thing	Channel	Item Type	Description
dimmer	lightlevel	Dimmer	Increase/decrease the light level
switch	switchstatus	Switch	On/off status of the switch
occupancysensor	occupancystatus	Switch	Occupancy condition
cco	switchstatus	Switch	On/off status of the CCO
keypads (all)	push button*	Switch	Keypad push button
keypads(except pico)	led*	Switch	LED indicator for the associated button
vcrx	cci*	Contact	Contact closure input on/off condition
shade	shadelevel	Rollershutter	Level of the shade (100% = full open)
blind	blindliftlevel	Rollershutter	Level of the blind (100% = total open)
blind	blindtiltlevel	Rollershutter	Tilt of the bullheaded slats
greenmode	step	Number	Get/fix active green mode pace number
timeclock	clockmode	Number	Get/fix active clock fashion index number
timeclock	sunrise	DateTime	Get the timeclock's sunrise time
timeclock	sunset	DateTime	Get the timeclock'southward sunset time
timeclock	execevent	Number	Execute consequence or monitor events executed
timeclock	enableevent	Number	Enable consequence or monitor events enabled
timeclock	disableevent	Number	Disable event or monitor events disabled
sysvar	varstate	Number	Get/gear up organization state variable value

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

# Commands supported past channels

Thing	Channel	Native Blazon	Accepts
dimmer	lightlevel	PercentType	OnOffType, PercentType (rounded/truncated to integer)
switch	switchstatus	OnOffType	OnOffType
occ. sensor	occupancystatus	OnOffType	(readonly)
cco	switchstatus	OnOffType	OnOffType, RefreshType
keypads	button*	OnOffType	OnOffType
	led*	OnOffType	OnOffType, RefreshType
	cci*	OpenClosedType	(readonly)
shade	shadelevel	PercentType	PercentType, UpDownType, StopMoveType.STOP, RefreshType
blind	blindliftlevel	PercentType	PercentType, UpDownType, StopMoveType.STOP, RefreshType
	blindtiltlevel	PercentType	PercentType, UpDownType, StopMoveType.STOP, RefreshType
greenmode	step	DecimalType	DecimalType, OnOffType (ON=two,OFF=1), RefreshType
timeclock	clockmode	DecimalType	DecimalType, RefreshType
	sunrise	DateTimeType	RefreshType (readonly)
	sunset	DateTimeType	RefreshType (readonly)
	execevent	DecimalType	DecimalType
	enableevent	DecimalType	DecimalType
	disableevent	DecimalType	DecimalType
sysvar	varstate	DecimalType	DecimalType (rounded/truncated to integer)

Most channels receive firsthand notifications of device state changes from the Lutron control organisation. The only exceptions are greenmode step, which is periodically polled and accepts REFRESH commands to initiate immediate polling, and timeclock sunrise and sunset, which must be polled daily using REFRESH commands to retrieve current values. Many other channels have REFRESH commands to initiate a poll, only sending 1 should not normally be necessary.

# RadioRA ii/HomeWorks QS Configuration File Examples:

demo.things:

demo.items:

dimmerAction.rules:

# Lutron RadioRA (Archetype) Binding

This bounden integrates with the legacy Lutron RadioRA (Classic) lighting organization.

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

# Supported Things

This bounden currently supports the following thing types:

Thing	Type ID	Clarification
ra-rs232	Span	RadioRA device that supports RS232 communication
ra-dimmer	Affair	Dimmer control
ra-switch	Thing	Switch control
ra-phantomButton	Thing	Phantom Push button to command multiple controls (Scenes)

# Affair 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 inside 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 post-obit channels are supported:

Matter Type	Aqueduct ID	Particular Type	Description
ra-dimmer	lightlevel	Dimmer	Increment/Decrease dimmer intensity
ra-switch/ra-phantomButton	switchstatus	Switch	On/Off country of switch

# Example

lutronradiora.things

lutronradiora.items

# Legacy HomeWorks RS232 (Serial) Processors

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

Please meet HomeWorks RS232 Protocol Guide (opens new window) for data on the protocol.

# Supported Things

• HomeWorks RS232-connected Processor Units
• Dimmers

Supported in time to come updates:

• Keypads
• Keypad LEDs

# Discovery

This binding supports agile and passive discovery. Information technology will discover dimmers equally they are manually raised or lowered, or can exist fabricated 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 up to 9600.

Dimmers have 1 required parameter accost that specifies the device accost (east.grand., [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).

# Channels

The following channels are supported:

Thing Blazon	Channel Type ID	Item Type	Description
dimmer	lightlevel	Dimmer	Increase/decrease the calorie-free level

# Lutron Grafik Center 3x/4x bounden via GRX-PRG or GRX-CI-PRG

This lutron binding will as well work with Grafik Eye 3x/4x systems in conjuction with the GRX-PRG or GRX-CI-PRG interfaces. Please see RS232ProtocolCommandSet (opens new window) for more information.

# Supported Things

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

# Discovery

This binding does not back up discovery of the GRX-PRG or GRX-CI-PRG. You will demand to specify them direct.

# Thing Configuration

The bridge requires the IP address/Host name of the span. Optionally, y'all may specify the username (defaults to 'nwk') and retryPolling (in seconds) to retry connections if the connection fails (defaults to 10 seconds). This span does back up two style 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).

The Grafik Centre matter requires the control unit address (1-eight). Optionally you may specify the default fade time (when raising/lowering zones or setting zone intensities) and polling fourth dimension (in seconds) to refresh the country 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.

# Channels

# Bridge channels

Channel Blazon ID	Readonly	Item Blazon	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	Fourth dimension of Sunrise
sunset	Aye	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	Adjacent sequence number in the Super Sequence
ssnextminute	Yep	Number	How many minutes until the adjacent step in the Super Sequence
ssnextsecond	Yes	Number	How many seconds until the next step in the Super Sequence
buttonpress	Yes	String	Concluding keypad push pressed (run into Appendix A) in protocol guide

# Grafik Eye channels

Channel Blazon ID	Readonly	Item Type	Description
scene	No	Number	The electric 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 side by side
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" aqueduct reports which keypad button was pressed. DIP switch 6 must exist gear up on the interface for this to be reported. The "buttonpress" aqueduct is just useful in rules to take action when a specific button (on a specific keypad) has been pressed.
• Dusk/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" volition bear on zone one. Specifying a zone larger than y'all accept volition accept no effect (such as using zonelower8 on a Grafik Eye 3506 which merely has 6 zones).
• The zonefade value will only be used when zonelower/zonereaise/zoneintensity is issued.
• zoneshade does not support PercentType nor StopMoveType.Movement and those commands volition exist ignored
• zoneintensity tin be used on a shade zone if the intensity is from 0 to v and should be used if wanting to set a QED preset: 0=Terminate, i=Open, 2=Close, 3=Preset ane, 4=Preset 2, 5=Preset 3
• If yous started a zonelower or zoneraise, the only style to end the action is by executing an all zone stop on the bridge (i.due east. zonelowerstop or zoneraisestop). The PRG API does not provide a way to stop the lowering/raising of whatsoever specific zone.

# Example

demo.Things:

demo.items:

Lutron, GRAFIK Eye, HomeWorks, HomeWorks QS, RadioRA, RadioRA 2, RA2 Select, Caseta, Sivoia QS, Serena, seeTouch, Pico, and Quantum 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.

Source: https://v2.openhab.org/addons/bindings/lutron/

Posted by: wrightequill.blogspot.com

Share this post