This page is part of archived documentation for openHAB 4.3. Go to the current stable version

# Blockly Reference

One of the core feature that openHAB provides is writing rules to allow specific behaviour with the home automation system. The usual way of developing rules is by coding them like described in the Textual Rules.

The art of textual programming may become intimidating early on and shy away away people with few or almost no experience in programming. So, if you are not a member of the professional coder community or do not have equivalent skills, the ability to create your programs visually might be the ideal option (even though some programming background may still help or can evolve over time). Therefore openHAB also provides a graphical way of writing rules which allows to put together rules in a visual way: Welcome to the world of openHAB Blockyl.

Introduction
Blockly is a code generator or how the 🦏 found the holy Grail
- Some history
- openHAB 3 / openHAB 4 - Migration
Looking for help
Before using blockly
Blockly YouTube Tutorials
Blocks Overview
Tutorials or other useful information

# Introduction

"built on Blockly"

The basic idea behind the visual paradigm and representation within openHAB is based on the Google Blockly Support (opens new window) which has been integrated and which provides the basic blocks for programming like the ones on the left and the right side of the below images Blockly toolbox.

blockly-toolbox-1 blockly-toolbox-2 blockly-toolbox-3

All of these provide general functionality that is not specific to openHAB itself. If you want to learn more about how to use them, search for the many blockly tutorials that are available. However, to leverage the full capabilities more than 50 specific blocks have been provided that are tailored for easy access of openHAB's capabilities.

This section provides a detailed description of the specific blocks and provides examples on how to use them. Note that some of the blocks (like voice, streaming or notifications) need some special setup within openHAB - in these case links to the respective documentation is provided. Also see this youtube Intro (opens new window) Quick Intro Blockly Rules

# Blockly is a code generator or how the 🦏 found the holy Grail

# Some history

Even though you may not notice it directly, the blocks are eventually used to automatically create code that can run on the openHAB server. Please watch the youtube video Blockly as an ECMA-Script code generator (opens new window) for a live demo. The code that is generated can be viewed when clicking the button showcode on the lower right corner of the blockly editor.

In general, the code that Blockly generates is JavaScript (aka ECMAScript) which exists in several flavours or versions. The ECMAScript version that is used by Blockly in openHAB 3 is ECMAScript 5.1 and it is run by a component named NashornJS 🦏. Nashorn JS (opens new window) itself was part of Java until version 14 when it was dropped. The generated rule code is run within the Java runtime (also known as JVM) on the openHAB server and as openHAB 4 has moved to Java 17, the old ECMAScript 5.1 is not directly available anymore within the JVM via Nashorn. A replacement for the Nashorn JS is GraalJS ("the holy grail"), which is currently running ECMAScript 2022 and therefore supports all modern JavaScript features, like arrow functions. GraalJS (opens new window) is already available in openHAB 3 when the JS Scripting Addon (opens new window) is installed.

TIP

Please convert your old rules as quickly as possible because only with GraalJS you can leverage the openHAB JavaScript library (aka openhab-js) in Blockly. Using this library you can not only create much simpler code, it also allows new functionality that is not available with Nashorn. Note that some blocks are only available with the openhab-js library on GraalJS.

# openHAB 3 / openHAB 4 - Migration

# Migrating Blockly rules to openHAB 4 is easy

From openHAB 4 on, the default script engine is GraalJS when Blockly creates new scripts. From a technical perspective a rule internally holds a so-called MIME-type that tells openHAB how the generated JavaScript language has to be interpreted. The (default) MIME-type application/javascript in openHAB 3 runs the rule with NashornJS, while this same MIME-type will run the Blocky rule with GraalJS in openHAB 4. As a result when running a non-converted openHAB 3 Blocky rule on openHAB 4, openHAB 4 will run a rule that was meant for NashornJS with GraalJS, which will fail. Therefore a conversion has to take place which in fact is not a lot of work:

There is the choice to

convert each rule to GraalJS
or keep the NashornJS Rules

but both need some work on each blockly rule you have.

# Migration to GraalJS (recommended)

Make sure the JS Scripting Addon (opens new window) addon is installed.
To convert / migrate a rule that was created in openHAB 3 (NashornJS) to a GraalJS-compatible one for openHAB 4, simply open each Blockly rule once in openHAB 4 and save it - that's it.
In this case, nothing more needs to be installed additionally to openHAB 4.

# Running openHAB 3 Blockly rules without migrating them right away

If you still want to run the Blockly rules that were created in openHAB 3 for the time being without changing them (see above), you have to install the JavaScript Scripting (Nashorn) Addon (opens new window) which provides backwards compatibility until you have converted all rules.
Open each Blockly rule or go to the Code TAB or Search for type: application/javascript;
Replace it by application/javascript;version=ECMAScript-5.1. Open the Blockly rule, find the following symbol and click on it.

javascript-dialog

to choose the old version of JavaScript and then save the rule.

choose-javascript

After the installation of the Addon both old rules created in openHAB 3 and new rules created in openHAB 4 can run on openHAB 4 at the same time.
After all scripts of the rules have been converted, like explained above, please uninstall the JavaScript Scripting (Nashorn) addon to save memory.
Note that this allows you to mix rules that run with NashornJS and some that run with GraalJS (see above).

# Looking for help

A special mention should go towards the Help entry in a block context menu right click on any block that links to a resource that is usually very helpful to understand the context of that particular block. To retrieve the particular help for a block right click on a block to open the context menu and click on the help-entry:

context-help

There is also a help-button available in each section that links to the documentation of the whole section.

main-help-button

Please read this information first before asking questions in the forum. In case you ask for help please always post the respective code that is being generated.

Also there is a good intro about that topic can be viewed at youtube Various Help Documentation available in openHAB Blocky (opens new window)

# Before using blockly

Please visit Getting started with openHAB Blocklies and creating a rule before asking questions in the forum.

# Blockly YouTube Tutorials

Three YouTube tutorials have been made available via the openHAB YouTube channel (opens new window):

# Blocks Overview

Also view youtube Overview of the Blockly Sections (opens new window)

# Using Variables

For a long time Blockly only provided untyped variables. Even though this seems to be more straight forward and provides the flexibility to put any type into that variable, it creates some challenges to openHAB Blockly to generate the right code.

All blocks in Blockly have input and output types defined which allows the editor to check whether one particular block can be used as input for a different block. This becomes challenging with the standard untyped variables because the type of these is basically none which means that the Blockly editor is not able to check whether this block is allowed or not. This requires Blockly to make a default guess on the variable's type, which often is the wrong type guess and therefore causes wrong code to be generated - your rule will not work.

Therefore, a new variable section was introduced:

typed variables

In general, always prefer Typed Variables over normal Variables!

In the very seldom case where you may mix types or you want to use a type that is not provided in the dialog, only then choose non-typed variables.

Create a typed variable by clicking on the following button:

create typed variable

This will open up the following dialog:

create typed variable dialog

Hint: Always choose the type of the variable first because it is not possible to change the type afterwards!

Enter the name of the variable: it is recommended to use a concatenation of the variable name plus the type like powerItemName as it is hard to know later on what type the variable has.
Don't forget to select the right type (here "Item name") before clicking ok because it cannot be changed later.
Click ok to create the variable

You will notice that this typed variable can only be used in inputs where normally an Item (name) block would have been allowed.

Here are some examples how these typed variable can or even should be used:

In the above example the variable name postfix Var was sometimes used which is more like a personal taste and isn't necessary.
Blockly loops can also take typed variables, and it is especially useful in these cases to make sure the type that is returned by the list (e.g. "get members of group") matches the type of the variable because it allows blocks that use the list items (e.g. "get state of item") to behave correctly.
As it can be seen in the loop example it is very helpful if the variable name contains the type.

# Items and Things

Items and Things are the major entities of openHAB (opens new window) to control and monitor the home.

See Items & Things section

# Timers and Delays

Timers and Delays are a little more complex but add important functionality to rules. Whilst the “Wait-For”-block is straightforward, the timer blocks should be well understood before being used - they may behave differently than expected. This chapter explains what these blocks do, sometimes displaying generated code to explain what is happening behind the scenes.

See Timers and Delays section.

# Voice and Multimedia

This section deals with playing or streaming audio to an audio sink e.g a speaker or saying a text via using any Text-to-Speech API (e.g. Google's API)

See Voice and Multimedia section.

# Units of Measurements

See Units of Measurement section.

# Date Handling

Date blocks are used as input parameters for other blocks. Some of these blocks are used by ephemeris blocks, whilst others are used in the persistence section. Therefore blocks are typed to assure correct connection to other blocks.

See Date Handling section.

# Ephemeris

The ephemeris category provides blocks with calendar functionality. The blocks can be used to determine what type of day today is, or a number of days before or after today is. For example, a way to determine if today is a weekend, a bank holiday, someone’s birthday, trash day, etc.

See Ephemeris section.

# Notifications

For use with your openHAB cloud (opens new window) account, these blocks can be used to send notifications to relevant connected devices. Notifications can be used as push message to devices running the openHAB client.

See Notifications section.

# Persistence

Persistence blocks enable access of historical data stored by the default persistence service.

See Persistence section.

# Value Storage

These blocks enable storing information for a rule that is kept after the rule has run, so it can be reused when the rule is run again later in stateful way.

See Value Storage section.

# HTTP

These blocks allow sending HTTP requests and receiving the response.

See HTTP section.

# Run & Process (Rules, Scripts and Transformations)

This section allows calling rules or other scripts, retrieving attributes provided by the rule context or transforming values via different conversion methods (e.g. map, regex, jsonpath)

See Run and Process section.

# Logging

This section allows calling rules or other scripts, retrieving attributes provided by the rule context or transforming values via different conversion methods (e.g. map, regex, jsonpath)

See Logging section.

# openHAB Extensions to the Standard

This section explains only the blocks that have been added to the standard blocks by openHAB

See openHAB Extensions to the standard section.

# openHAB Blocks provided by the community

The core openHAB are meant to cover most of the functionality that is needed to write rules. However, there might be functionality that is not available (yet). These can be provided by the community.

A good explanation on how to write custom blocks can be found at How to write openHAB Blockly Libraries (opens new window)

All published custom blocks can be found at Published Blockly Libraries (opens new window) and can be directly downloaded within your openHAB installation in the Settings -> Automation section

# Tutorials or other useful information

Caught a mistake or want to contribute to the documentation? Edit this page on GitHub (opens new window)