Actions

Tom Deckers edited this page Feb 16, 2017 · 82 revisions

feature overview

Installation

Setup intro

Linux and OS X

Windows

FreeBSD


Configuration

Automation*

User Interfaces

Persistence


Community

(link to openHAB forum)

Development


Bindings


Application Integration

Misc


Samples

A good source of inspiration and tips from users gathered over the years. Be aware that things may have changed since they were written and some examples might not work correctly.

Please update the wiki if you do come across any out of date information.

Binding configurations

Use case examples

Item definition examples

Sitemap definition examples

Collections of Rules on a single page

Single Rules

Scripts

Syntax highlighting for external editors


Release Notes

Clone this wiki locally

Actions available in Scripts and Rules

Actions are predefined Java methods that are automatically statically imported and can be used within Scripts and Rules to execute openHAB specific operations.

Since openHAB 1.3.0, not all actions are part of the core runtime distribution anymore, but it is possible to easily implement add new actions to your runtime (see the developer section for details).

Table of Contents

Core Actions

Here is the list of available actions in the core runtime:

Event bus related actions

  • sendCommand(String itemName, String commandString): Sends the given command for the specified item to the event bus
  • postUpdate(String itemName, String stateString): Posts the given status update for the specified item to the event bus
  • group.send(Command command_to_send): sends the given Command (ON/OFF/etc.) to every item in the group. Casts from other data types (e.g. switch) are possible

sendCommand vs postUpdate

If you want to tell something to change (turn a light on, change the thermostat to a new temperature, start raising the blinds, etc.), then you want to send a command to an item using sendCommand. If your items' states are not being updated by a binding, the autoupdate feature (see below) or something else external, you will probably want to update the state in a rule, using postUpdate.

When you click on buttons, sliders or other widgets in the UI, that sends commands to items. Usually this causes the state of the item to update automatically at the same time (using the default autoupdate feature, but there are cases where autoupdate is not performed, depending on the binding or configuration in your .items file if autoupdate="false" is present). Commands can also be sent other ways, such as the REST API and CMD servlet.

Your rules can trigger on items receiving commands, items' states updating, or items' states changing to a different value.

  • Map<Item, State> storeStates(Item... items): Stores the current state of a list of items in a map which can be assigned to a variable. Group items are not themselves put into the map, but instead all their members.
  • restoreStates(Map<Item, State> statesMap): Restores item states from a map. If the saved state can be interpreted as a command, a command is sent for the item (and the physical device can send a status update if occurred). If it is no valid command, the item state is directly updated to the saved value.

Table of Contents

Audio actions

  • setMasterVolume(float volume): Sets the volume of the host machine (volume in range 0-1)
  • increaseMasterVolume(float percent): Increases the volume by x percent
  • decreaseMasterVolume(float percent): Decreases the volume by x percent
  • float getMasterVolume(): Returns the volume with the range 0-1
  • playSound(String filename): Plays the given file (must be mp3 or wav and be located in ${openhab.home}/sounds)
  • playStream(String url): Plays the audio stream from the given url.
  • say(String text): Says the given text through Text-to-speech
  • say(String text, String voice): Text-to-speech with a given voice (depends on the TTS engine or voices installed in the OS)
  • say(String text, String voice, String device): Text-to-speech with a given voice to the given output device (only supported on Mac OS). Available voices command: say -v ?. Available devices command: say -a ?

Table of Contents

Logging actions

  • logDebug(String loggerName, String logText, Object[args)): Logs logText on level DEBUG using the openhab Logback configuration
  • logInfo(String loggerName, String logText, Object[](]) args)): Logs logText on level INFO using the openhab Logback configuration
  • logWarn(String loggerName, String logText, Object[args)): Logs logText on level WARN using the openhab Logback configuration
  • logError(String loggerName, String logText, Object[](]) args)): Logs logText on level ERROR using the openhab Logback configuration

    Note: Opened and immediately closed curly braces ({}) in logText are placeholders for args[0], args[1], etc.

    Note2: Remember that if the name of your logger is "kitchen" you have to define it in logback.xml as <logger name="org.openhab.model.script.kitchen" level="DEBUG"/>

Example:

  • logDebug("Garage", "GarageDoorStateChanged Starting. Garage_Door_Open.state: [{}]. Garage_Door_Closed.state: [{}].", Garage_Door_Open.state, Garage_Door_Closed.state);

    • Outputs "GarageDoorStateChanged Starting. Garage_Door_Open.state: [true]. Garage_Door_Closed.state: [false]." to a logger called "Garage". In this example, Garage_Door_Open and Garage_Door_Closed are String items with values of true and false respectively.

Table of Contents

HTTP actions

  • sendHttpGetRequest(String url): Send out a GET-HTTP request.
  • sendHttpPutRequest(String url): Send out a PUT-HTTP request.
  • sendHttpPutRequest(String url, String contentType, String content): Send out a PUT-HTTP request, with parameters.
  • sendHttpPostRequest(String url): Send out a POST-HTTP request.
  • sendHttpPostRequest(String url, String contentType, String content): Send out a POST-HTTP request, with parameters.
  • sendHttpDeleteRequest(String url): Send out a DELETE-HTTP request.

Table of Contents

Timers

  • createTimer(AbstractInstant instant, Procedure procedure): Schedules a block of code (a closure) for future execution.

The method returns a Timer object, for example:

var Timer timer = createTimer(now.plusMinutes(5)) [|
    logInfo("rules", "Timer activated")
]

Timer then supports the following methods:

  • cancel(): Cancels the timer, returns true if successful
  • isRunning(): Returns true if the scheduled code is currently being executed
  • hasTerminated(): Returns true if the scheduled code has laready terminated
  • reschedule(AbstractInstant newTime): Reschedules a new starting time. If the timer has terminated, this method does nothing.

Table of Contents

Other actions

  • callScript(String scriptName): Calls a script which must be located in the configurations/scripts folder
  • executeCommandLine(String commandLine): Executes a command on the command line.

    Note: The commandLine variable has to use a special format where @@ separates the arguments. For example the bash command touch somefile will have to be written as touch@@somefile. See Samples and Tricks for a larger example.

  • executeCommandLine(String commandLine, int timeout): Executes a command on the command line with a timeout
  • transform(String type, String function, String value): Applies a transformation of a given type with some function to a value. Returns the transformed value, or the original value if the transformation failed. See Transformations for available transformations and their usage.

Table of Contents

Add-on Actions

The following actions can be found in the "addons" download package. In order to install them to your runtime, simply copy the according jar file to the ${openhab.home}/addons folder. To make these actions available in the Designer as well, you need to copy the jar files into the addons folder of the Designer (note that you have to view the package content of the Designer in order to find the addons folder, if you are on Mac OS X). If the addons folder does not exist yet, simply create it.

Astro Actions

With the Astro-Action you can calculate sunrise and sunset DataTime values in rules.
Important: The action also requires the corresponding Astro-Binding!

Example:

import org.openhab.core.library.types.*
import java.util.Date

rule "Astro Action Example"
when
    ...
then
    var Date current = now.toDate
    var double lat = xx.xxxxxx
    var double lon = xx.xxxxxx

    logInfo("sunRiseStart: ", new DateTimeType(getAstroSunriseStart(current, lat, lon)).toString)
    logInfo("sunRiseEnd: ", new DateTimeType(getAstroSunriseEnd(current, lat, lon)).toString)

    logInfo("sunSetStart: ", new DateTimeType(getAstroSunsetStart(current, lat, lon)).toString)
    logInfo("sunSetEnd: ", new DateTimeType(getAstroSunsetEnd(current, lat, lon)).toString)
end

Table of Contents

Cisco Spark Actions

Cisco Spark can be used to message individuals and rooms when certain events take place in openHAB.

Send a message to a specific room

sparkMessage('message', 'roomId') 

Send a message to the default room (from config)

sparkMessage('message')

Send a direct message to a person

sparkPerson('message', 'personEmail')

For configuration details see Cisco Spark Action page.

Table of Contents

Ecobee Actions

Available as of openHAB 1.8

The Ecobee Action bundle provides actions such as setting and clearing program holds, sending a text message to the thermostat's display, renaming a remote wireless sensor, and other functions that cannot be performed by setting object properties. The Action bundle requires that the Ecobee Binding is also installed in your addons folder. Read the Ecobee function API documentation to be sure you know the rules for calling these actions.

NOTE: See changes below for actions supported in 1.9 and onwards.

Parameters in italics are optional, in which case each unused parameter must be replaced with null.

Actions supported in openHAB 1.8:

  • ecobeeAcknowledge(Item item, String thermostatIdentifier, String ackRef, String ackType, Boolean remindMeLater) - Acknowledge an alert.
  • ecobeeControlPlug(Item item, String plugName, String plugState, Date startDateTime, Date endDateTime, String holdType, Integer holdHours) - Control the on/off state of a plug by setting a hold on the plug.
  • ecobeeCreateVacation(Item item, String name, DecimalType coolHoldTemp, DecimalType heatHoldTemp, Date startDateTime, Date endDateTime, String fan, Integer fanMinOnTime) - Create a vacation event on the thermostat.
  • ecobeeDeleteVacation(Item item, String name) - Delete a vacation event from a thermostat.
  • ecobeeResetPreferences(Item item) - Set all user configurable settings back to the factory default values.
  • ecobeeResumeProgram(Item item, Boolean resumeAll) - Remove the currently running event providing the event is not a mandatory demand response event.
  • ecobeeSendMessage(Item item, String text) - Send an alert message to the thermostat.
  • ecobeeSetHold(Item item, DecimalType coolHoldTemp, DecimalType heatHoldTemp, String holdClimateRef, Date startDateTime, Date endDateTime, String holdType, Integer holdHours) - Set the thermostat into a hold with the specified temperature.
  • ecobeeSetOccupied(Item item, Boolean occupied, Date startDateTime, Date endDateTime, String holdType, Integer holdHours) - Switches a (EMS model only) thermostat from occupied mode to unoccupied, or vice versa.
  • ecobeeUpdateSensor(Item item, String name, String deviceId, String sensorId) - Update the name of an ecobee3 remote sensor.

Actions supported in openHAB 1.9 and onwards (changes were required for support of openHAB 2):

The selection parameter is a string that identifies the thermostat(s) against which the action is performed, identical in format to <thermostat> used in the binding.

  • ecobeeAcknowledge(String selection, String thermostatIdentifier, String ackRef, String ackType, Boolean remindMeLater) - Acknowledge an alert.
  • ecobeeControlPlug(String selection, String plugName, String plugState, Date startDateTime, Date endDateTime, String holdType, Number holdHours) - Control the on/off state of a plug by setting a hold on the plug.
  • ecobeeCreateVacation(String selection, String name, Number coolHoldTemp, Number heatHoldTemp, Date startDateTime, Date endDateTime, String fan, Number fanMinOnTime) - Create a vacation event on the thermostat.
  • ecobeeDeleteVacation(String selection, String name) - Delete a vacation event from a thermostat.
  • ecobeeResetPreferences(String selection) - Set all user configurable settings back to the factory default values.
  • ecobeeResumeProgram(String selection, Boolean resumeAll) - Remove the currently running event providing the event is not a mandatory demand response event.
  • ecobeeSendMessage(String selection, String text) - Send an alert message to the thermostat.
  • ecobeeSetHold(String selection, Number coolHoldTemp, Number heatHoldTemp, String holdClimateRef, Date startDateTime, Date endDateTime, String holdType, Number holdHours) - Set the thermostat into a hold with the specified temperature.
  • ecobeeSetHold(String selection, Map<String, Object> params, Date startDateTime, Date endDateTime, String holdType, Number holdHours) - Set the thermostat into a hold with the specified event params.
  • ecobeeSetOccupied(String selection, Boolean occupied, Date startDateTime, Date endDateTime, String holdType, Number holdHours) - Switches a (EMS model only) thermostat from occupied mode to unoccupied, or vice versa.
  • ecobeeUpdateSensor(String selection, String name, String deviceId, String sensorId) - Update the name of an ecobee3 remote sensor.

Table of Contents

Mail Actions

This add-on provides SMTP services. Please check openhab_default.cfg for required configuration settings. The to paremeter can contain a semicolon separated list of email addresses.

  • sendMail(String to, String subject, String message): Sends an email via SMTP.
  • sendMail(String to, String subject, String message, String attachmentUrl): Sends an email with attachment via SMTP.
  • sendMail(String to, String subject, String message, List<String> attachmentUrlList): Sends an email with one or more attachments via SMTP (available as of openHAB 1.8). Example:
import java.util.List
...
val List<String> attachmentUrlList = newArrayList(
  "http://some.web/site/snap.jpg&param=value",
  "http://192.168.1.100/data.txt",
  "file:///tmp/201601011031.jpg")
sendMail("you@email.net", "Test", "This is the message.", attachmentUrlList)

Table of Contents

MQTT Action

Available as of openHAB 1.8

  • publish(String brokerName, String topic, String message): Publish the message to topic using specified MQTT broker. The action uses the same transport configuration settings as documented for the MQTT binding.

Table of Contents

NotifyMyAndroid Actions

Sends push messages to your Android devices. All configuration in openhab.cfg is optional

  • notifyMyAndroid(String event, String description): Send a message to a the pre configured api key (account) and use the configured or default values for the other parameters
  • notifyMyAndroid(String apiKey, String event, String description): Send a message to another api key than the configured or use this method if you have not configured a default api key
  • notifyMyAndroid(String apiKey, String event, String description, int priority, String url, boolean html): Send a message overwriting all configured parameters and using the specified values.

Table of Contents

OpenWebIf Action

The openwebif action allows you to send a message to enigma2 based linux sat receivers (Dreambox, VU+, Clarke-Tech, ...) with installed OpenWebIf plugin.

Configure your sat receivers in openhab.cfg, you can specify multiple sat receivers identified by name:

openwebif:receiver.<name>.host=
openwebif:receiver.<name>.port=
openwebif:receiver.<name>.user=
openwebif:receiver.<name>.password=
openwebif:receiver.<name>.https=

Example:

openwebif:receiver.main.host=vusolo2
openwebif:receiver.main.port=81
openwebif:receiver.main.user=root
openwebif:receiver.main.password=xxxxx
openwebif:receiver.main.https=false

Now you can send a message to the configured receiver:

  • sendOpenWebIfNotification(NAME, MESSAGE, TYPE, TIMEOUT);

NAME: The name of the sat receiver configured in openhab.cfg
MESSAGE: The message to send to the receiver
TYPE: The message type (INFO, WARNING, ERROR)
TIMEOUT: How long the text will stay on the screen in seconds

Example:
sendOpenWebIfNotification("main", "Hello World!\n\nThis is a message sent from openHab!", "WARNING", 10);

Table of Contents

Pebble Actions

This action enables you to send pins and notifications directly to your Pebble watch.

You'll need to install the openHAB app on your Pebble and look up the Timeline token. This token is displayed at the bottom of the configuration page when you configure the app on your phone.

You can use this token in each action call, or define an instance from openhab.cfg, like this:

pebble:dave.token=88889999aaaabbbbccccddddeeeeffff

The following methods are available:

  • pebblePin(String instanceOrToken, Date time, String title, String body) Insert a pin at a given time with a title and body.

  • pebblePin(String instanceOrToken, Date time, String pinTitle, String actionTitle, String url) Insert a pin at a given time with a title and add an action. This action is a simple HTTP GET on the given url.

  • pebbleNotification(String instanceOrToken, String title, String body) Push a notification directly, with given title and body.

All actions accept an instance name OR the timeline token as the first parameter.

Examples:

  • pebblePin("88889999aaaabbbbccccddddeeeeffff", now.toDate, "Dave left", "Dave is on his way")
  • pebblePin("dave", new DateTime().withHourOfDay(23).withMinuteOfHour(30).toDate, "Bed time", "Shutdown", "http://192.168.1.15:8090/CMD?Lights_All=OFF")
  • pebbleNotification("dave", "Dave left", "Dave left the house")

Table of Contents

Prowl Actions

Prowl lets you use push notifications on iOS devices (please check openhab.cfg for required configuration settings):

  • pushNotification(String subject, String message): Pushes a Prowl Notification
  • pushNotification(String apikey, String subject, String message, int priority): Pushes a Prowl Notification with the given priority

Table of Contents

Pushover Actions

The pushover action allows you to notify mobile devices of a message using the Pushover API web service.

The following are configuration items for your openhab.cfg file. None of the options are required as you can specify required configuration items in the action call, but you must at least provide an API Token, User/Group Key and a Message in some manner before a message can be pushed.

  • pushover:defaultTimeout - The timeout for the communication with the Pushover service.
  • pushover:defaultToken - Pushover API token to send to devices.
  • pushover:defaultUser - Pushover User or Group key to send to devices.
  • pushover:defaultTitle - Application title for the notification.
  • pushover:defaultPriority - Priority of the notification. Default is 0.
  • pushover:defaultUrl - A URL to send with the notification.
  • pushover:defaultUtlTitle - Title of the URL to send with the notification.
  • pushover:defaultRetry - When priority is 2, how often in seconds should messages be resent. [Added 1.6+]
  • pushover:defaultExpire - When priority is 2, how long to continue resending messages until acknowledged. [Added 1.6+]

The following are valid action calls that can be made when the plugin is loaded. For specific information on each item, see the Pushover API.

  • pushover(String message)
  • pushover(String message, String device)
  • pushover(String message, int priority)
  • pushover(String message, int priority, String url) [Added 1.6+]
  • pushover(String message, int priority, String url, String urlTitle) [Added 1.6+]
  • pushover(String message, int priority, String url, String urlTitle, String soundFile) [Added 1.6+]
  • pushover(String message, String device, int priority)
  • pushover(String message, String device, int priority, String url) [Added 1.6+]
  • pushover(String message, String device, int priority, String url, String urlTitle) [Added 1.6+]
  • pushover(String message, String device, int priority, String url, String urlTitle, String soundFile) [Added 1.6+]
  • pushover(String apiToken, String userKey, String message)
  • pushover(String apiToken, String userKey, String message, String device)
  • pushover(String apiToken, String userKey, String message, int priority)
  • pushover(String apiToken, String userKey, String message, String device, int priority)
  • pushover(String apiToken, String userKey, String message, String device, String title, String url, String urlTitle, int priority, String soundFile)

Table of Contents

Pushsafer Actions

The Pushsafer action allows you to notify iOS, Android & Windows 10 Phone & Desktop devices of a message using the Pushsafer API web service. [Added 1.9+]

You must at least provide an API Token (Private or Alias Key from Pushsafer.com) and a Message in some manner before a message can be pushed. All other parameters are optional. If you use an alias key, the parameters (device, icon, sound, vibration) are overwritten by the alias setting on pushsafer.

The following is a valid action call that can be made when the plugin is loaded. For specific information on each item, see the Pushsafer API.

  • pushsafer(String apiToken, String message, String title, String device, String icon, String vibration, String sound)

Table of Contents

Squeezebox Action

Interact directly with your Squeezebox devices from within rules and scripts. In order to use these actions you must also install the org.openhab.io.squeezeserver bundle and configure the 'squeeze' properties in openhab.cfg.

See the Squeezebox Action page for more details.

Table of Contents

Telegram Action

The Telegram action allows sending formatted messages to Telegram clients (https://telegram.org), by using the Telegram Bot API.

Sample openhab.cfg:

In openhab.cfg both Bot authentication tokens and chatIds must be defined. Multiple bots and chats can be defined as targets.

Example:

telegram:bots=bot1,bot2

telegram:bot1.chatId=22334455
telegram:bot1.token=xxxxxxxxxxx

telegram:bot2.chatId=654321
telegram:bot2.token=yyyyyyyyyyy

It this example two bots can be used (bot1 and bot2).

For each destination chat, the authentication token and the chat id must be defined using

telegram:<bot name>.chatId=<chat id>
telegram:<bot name>.token=<authentication token>

Sample action usage in .rules to send text message to telegram chat

rule "Send telegram with Fixed Message"
when
    Item Foo changed
then
    sendTelegram("bot1", "item Foo changed")
end
rule "Send telegram with Formatted Message"
when
    Item Foo changed
then
    sendTelegram("bot1", "item Foo changed to %s and number is %.1f", Foo.state.toString, 23.56)
end

Sample action usage in .rules to send image to telegram chat

rule "Send telegram with image and caption from image accessible by url"
when
    Item Light_GF_Living_Table changed
then
    sendTelegramPhoto("bot1", "http://www.openhab.org/assets/images/openhab-logo-top.png",
        "sent from openHAB")
end
rule "Send telegram with image without caption from image accessible by url"
when
    Item Light_GF_Living_Table changed
then
    sendTelegramPhoto("bot1", "http://www.openhab.org/assets/images/openhab-logo-top.png",
        null)
end

In case your image is behind an authenticated web server (locked by username and password) you can pass the credentials as additional parameters to the extended sendTelegramPhoto method (available since 1.9).

rule "Send telegram with image without caption from image accessible by url"
when
    Item Light_GF_Living_Table changed
then
    sendTelegramPhoto("bot1", "http://www.openhab.org/assets/images/openhab-logo-top.png",
        null, "username", "password")
end

Do not use username/password in url like in this example http://<username>:<password>@server/image.png; pass the credentials to the sendTelegramPhoto method instead.

http and https are the only protocols allowed.

How to get the Bot authentication token and the chatId

As described in the Telegram Bot API, this is the manual procedure needed in order to get the necessary information.

  1. Create the Bot and get the Token
    • On a Telegram client open a chat with BotFather.
    • write /newbot to BotFather, fill all the needed information, write down the token. This is the authentication token needed.
  2. Create the destination chat and get the chatId
    • Open a new chat with your new Bot and post a message on the chat
    • Open a browser and invoke https://api.telegram.org/bot<token>/getUpdates (where <token> is the authentication token previously obtained)
    • Look at the JSON result and write down the value of result[0].message.from.id. That is the chatId.

Table of Contents

TinkerForge Actions

The TinkerForge Action plugin provides direct interaction with some of the TinkerForge devices (since 1.7.0). The action depends on the TinkerForge binding. In order to use these actions you must install the TinkerForge Action bundle and the TinkerForge Binding and add at least a hosts configuration value for the binding in openhab.cfg. These action functions are available:

  1. tfClearLCD(String uid)

    Clears the display of the LCD with the given uid.

    Example:

    rule "clear lcd"
        when
            Item ClearLCD received command ON
        then
           tfClearLCD("d4j")
    end
    
  2. tfServoSetposition(String uid, String num, String position, String velocity, String acceleration)

    Sets the position of a TinkerForge servo with the uid $uid and servo number to the position $position using the speed $speed and acceleration $acceleration.

    Example:

      rule "move servo"
      when
          Item MoveServo received command ON
      then
         tfServoSetposition("6Crt5W", "servo0", "0", "65535", "65535")
         Thread::sleep(1000)
         tfServoSetposition("6Crt5W", "servo0", "-9000", "65535", "65535")
         Thread::sleep(1000)
        tfServoSetposition("6Crt5W", "servo0", "9000", "65535", "65535")
    end
    
  3. tfDCMotorSetspeed(String uid, String speed, String acceleration, String drivemode)

    Sets the speed of a TinkerForge DC motor with the given uid to $speed using the acceleration $acceleration and the drivemode $drivemode.

    • speed: value between -32767 - 32767
    • drivemode is either "break" or "coast"

      Example:

      rule "move motor"
      when
          Item DCMOVE received command ON
      then
         var String acceleration = "10000"
         var String speed = "15000"
         tfDCMotorSetspeed("62Zduj", speed, acceleration, "break")
         Thread::sleep(1000)
         tfDCMotorSetspeed("62Zduj", speed, acceleration, "break")
         Thread::sleep(1000)
         tfDCMotorSetspeed("62Zduj", speed, acceleration, "break")
         Thread::sleep(1000)
         tfDCMotorSetspeed("62Zduj", speed, acceleration, "break")
      end
      
  4. tfDCMotorSetspeed(String uid, Short speed, Integer acceleration, String drivemode)

    Sets the speed of a TinkerForge DC motor with the given uid to $speed using the acceleration $acceleration and the drivemode $drivemode.

    • speed: value between -32767 - 32767
    • drivemode is either "break" or "coast"

    Example:

      rule "move motor"
      when
          Item DCMOVE received command ON
      then
         var Integer acceleration = 10000
         var Short speed = 15000
         tfDCMotorSetspeed("62Zduj", speed, acceleration, "break")
         Thread::sleep(1000)
         tfDCMotorSetspeed("62Zduj", speed, acceleration, "break")
         Thread::sleep(1000)
         tfDCMotorSetspeed("62Zduj", speed, acceleration, "break")
         Thread::sleep(1000)
         tfDCMotorSetspeed("62Zduj", speed, acceleration, "break")
      end
    
  5. tfRotaryEncoderClear(String uid)

    Clears the rotary encoder counter with the given uid.

    Example:

      rule "Clear"
          when Item Clear changed
      then 
         tfRotaryEncoderClear("kHv")
      end
    
  6. tfLoadCellTare(String uid) Sets tare on the load cell bricklet with the given uid. Example:

      rule "Tare"
          when 
                  Item Tare changed to ON
          then
                  postUpdate(TareValue, Weight.state)
                  tfLoadCellTare("v8V")
      end
    

Table of Contents

Twitter Actions

Connect to Twitter through this action (please check openhab.cfg for required configuration settings):

  • sendTweet(String message): Sends a Tweet via Twitter
  • sendDirectMessage(String recipient, String message): Sends a direct Message via Twitter

See the Twitter Action page for more details.

Table of Contents

Weather Actions

  • getHumidex(double temperature, int hygro): Compute the Humidex index given temperature in Celsius and hygrometry (relative percent). Returns Humidex index value.
  • getBeaufortIndex(double speed): Compute the Beaufort scale for a given wind speed in m/s. Returns the Beaufort Index between 0 and 12. transform/beaufort.map:
0=Calm
1=Light air
2=Light breeze
3=Gentle breeze
4=Moderate breeze
5=Fresh breeze
6=Strong breeze
7=High wind
8=Gale
9=Strong/severe gale
10=Storm
11=Violent storm
12=Hurricane force
  • getSeaLevelPressure(double pressure, double temp, double altitude): Compute the Sea Level Pressure, given absolute pressure in hPa, temperature in Celsius, and altitude in meters. Returns equivalent sea level pressure.
  • getWindDirection(int degree): Transform an orientation angle (in degrees) to its cardinal string equivalent. Returns string representing the direction.

Table of Contents

XBMC Actions

Sends notifications to XBMC

  • sendXbmcNotification(host, port, title, message): Sends a message to a given XBMC instance
  • sendXbmcNotification(host, port, title, message, image, displayTime): Sends a message to a given XBMC instance (image=a URL pointing to an image, displayTime=a display time for the message in milliseconds)

Table of Contents

XMPP Actions

configure XMPP (openhab.cfg)

Example: Google

xmpp:servername=talk.google.com
xmpp:securitymode=required
# You need this "tlspin" if openhab cannot verify the certificat from the google server
xmpp:tlspin=CERTSHA256:9e670d6624fc0c451d8d8e3efa81d4d8246ff9354800de09b549700e8d2a730a
xmpp:proxy=gmail.com
xmpp:username=my.openhab@gmail.com
xmpp:password=mysectret
# you may need to add the cryptic talk.google.com address of your private google account to the allowed users
# check you openhab.log to found the address after you send something via hangout to your openhab account
xmpp:consoleusers=**cryptic**@public.talk.google.com,myname@gmail.com

OpenHAB does not resolve SRV entries like other XMPP clients do, you have to setup the server details manually. Generally, if joe@example.org is your XMPP user ID and xmpp.example.net points to the server running the service, set xmpp:servername to the actual server xmpp.example.net, the user name xmpp:username to joe and xmpp:proxy to the domain name part of your user ID example.org.

using XMPP

This add-on provides XMPP communication. Besides the action methods itself, it also contains the XMPP console (please check openhab.cfg for required configuration settings):

  • sendXMPP(String to, String message): Sends a message to an XMPP user
  • sendXMPP(String to, String message, String attachmentUrl): Sends a message with an attachment to an XMPP user
  • chatXMPP(String message): Sends a message to an multi user chat

Table of Contents