Skip to content

The openHASP Custom Component simplifies synchronization of objects on one or more openHASP plates with Home Assistant entities. You can map any service supported by any entity in Home Assistant to any object event in openHASP, moreover, you can set any property of any object in openHASP to any value from Home Assistant. This powerful concept gives you full freedom to create a completely customized, hardware-based control user interface for your home automation.

We call plate any device running openHASP in your system.

Installation~

You have the option to install the custom component using HACS or via manual download:

hacs_badge

Install using HACS in one-click. This is the preferred and recommended method, as HACS provides a very effective way to keep the component updated and/or choose between various versions.

  1. Goto Home Assistant > HACS > Integrations.
  2. Click the Explore & Add Repositories button.
  3. Search for openHASP and click on the openHasp logo.
  4. Click Install this repository in HACS. Note: To install the current unstable development version select the Main.
  5. Click Install
  6. Reboot Home-Assistant

Alternatively, you can also install it manually:

Download ZIP

  1. Using the tool of choice open the directory (folder) for your HA configuration (where you find configuration.yaml).
  2. If you do not have a custom_components directory there, you need to create it.
  3. In the custom_components directory create a new folder called openhasp.
  4. Download all the files from the custom_components/openhasp/ directory in this repository.
  5. Place the files you downloaded in the new directory you created.
  6. Edit your configuration.yaml file add an entry similar to the example below.
  7. Restart Home Assistant

Note

The download link points to the actual development code in the master branch.

Warning

You have to use component version consistently with the firmware version on your plates. For example, if your plates are at firmware version 0.6.x, you also need to use component version 0.6.x to ensure interoperability. Home Assistant will show a warning if it finds a version mismatch. Note that you can only have one version of the component installed at a time so a mix of plate versions cannot be deployed.

Configuration~

First prepare your plates to be integrated with Home Assistant (follow steps in order):

  1. Connect your plates to the network. Static DHCP or fixed IP is not needed as communication only happes through MQTT.
  2. Set the GPIO configuration corresponding to your hardware (important for them to be detected as entities), save and reboot.
  3. Restart Home Assistant.
  4. Set the MQTT server settings and make sure each plate has a unique node name, save and reboot.

The component will automatically discover the plates and you will see them appearing in Home Assistant > Configuration > Integrations > HASP-Open Hardware Edition.

When Home Assistant detects your plate, you will have to give it a name. In the examples below both name and node name is plate35.

Currently you will get a warning that you need to add manual configuration for the objects in your configuration.yaml, that's no problem, read ahead.

Example~

To add an openHASP plate to your installation with a sample configuration, upload a pages.jsonl file with the folowing content to your plate first:

1
2
3
4
{"page":1,"id":1,"obj":"btn","x":0,"y":0,"w":240,"h":30,"text":"openHASP","value_font":22,"bg_color":"#2C3E50","text_color":"#FFFFFF","radius":0,"border_side":0}
{"page":1,"id":2,"obj":"btn","x":10,"y":40,"w":105,"h":90,"toggle":true,"text":"\uE335","text_font":32,"mode":"break","align":1}
{"page":1,"id":3,"obj":"dropdown","x":10,"y":140,"w":170,"h":30,"options":"Apples\nBananas\nOranges\nMelon"}
{"page":0,"id":1,"obj":"label","x":175,"y":5,"h":30,"w":62,"text":"00.0°C","align":2,"bg_color":"#2C3E50","text_color":"#FFFFFF"}

Assuming your plate's configured MQTT node name is plate35, add the following to your configuration.yaml file (Home Assistant will deliberatey ask for it when finished autodetection procedure):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
openhasp:
  plate35:
    objects:
      - obj: "p0b1"  # temperature label on all pages
        properties:
          "text": '{{ states("sensor.my_room_temperature") }}°C'
      - obj: "p1b2"  # light-switch toggle button
        properties:
          "val": '{{ 1 if states("light.my_room") == "on" else 0 }}'
          "text": '{{ "\uE6E8" if is_state("light.my_room", "on") else "\uE335" | e }}'
        event:
          "up":
            - service: homeassistant.toggle
              entity_id: "light.my_room"
      - obj: "p1b3"  # dropdown
        event:
          "changed":
            - service: persistent_notification.create
              data:
                message: I like {{ text }}

Variable definitions~

openhasp: (Required)
The platform identifier. Required once in the configuration.
plate35: (Required)
Your plate identifier slug. For each plate in your sytem, such an entry is required, has to be unique. It is generated automatically from the plate name you gave during discovery, which by default equals to the HASP Node Name set in the plate's configuration.
objects: (Optional)
Definition of the objects reacting to changes in Home Assistant, or generating events for Home Assistant.
obj: (string) (Required)
The object identifier which we want to integrate with Home Assistant. Its name has the form pXbY where X represents the page where the object is located, and Y represents the id of the object on that page.
properties: (Optional)
List containing the properties of the object which we want to modify based on changes occurring in Home Assistant. In the example above text property gets updated whenever sensor.my_room_temperature changes.
event: (Optional)
List containing the events generated by the object when touched on the screen. These are object-specific and can be observed accurately with an MQTT client. Each event defines a list of services which will be processed in order (like actions list in an automation).

In the example above, when object p1b2 (which is a toggle button) generates the on event, light.my_room will be turned on by the service call light.turn_on as specified in the event config. And similarily when off event comes through MQTT, the light will be turned off by the corresponding service call.

Note

Any variable coming from the MQTT message can be used between curly brackets and passed to the service call. In the example above when object p1b3 (which is a dropdown selector) generates the changed event, a persistent notification will appear in Home Assistant's Lovelace interface containing the selected text from the object, which was passed over from the MQTT message. See object events for more types of generated events.

Configuration tips~

Multiple plates~

If you have multiple plates you can add them all using different plate identifiers. Their configured topics have to be unique too:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
openhasp:
  plate_my_room_1:
    objects:
      # ...
  plate_my_room_2:
    objects:
      # ...
  plate_my_room_3:
    objects:
      # ...

Split configuration~

You can use Home Assistant's split configuration to help better organizing your config files.

Instead of keeping the configuration of all openHASP plates in Home Assistant's main config file, you can keep openHASP config separately, by adding only this to configuration.yaml:

openhasp: !include openhasp.yaml

After this, you can move your openHASP configuration starting with plate_my_room: level to your separate openhasp.yaml file and restart Home Assistant.

Moreover, if you have multiple plates, you can keep each one in a separate config file, to achieve this, make it like:

openhasp: !include_dir_merge_named openhasp_configs/

Create a directory openhasp_configs right near configuration.yaml, and put in it all your plates configuration (only with plate_my_room: level) in separate yaml files and restart Home Assistant.

Services~

This component implements some specific services to make interactions with the plate even more comfortable.

openhasp.wakeup
Wakes up the display when an external event has occurred, like a presence or a PIR motion sensor.
openhasp.next_page
Changes plate to the next page.
openhasp.prev_page
Changes plate to the previous page.
openhasp.change_page
Changes plate directly to the specified page number.
openhasp.clear_page
Clears the contents of the specified page number. If page number not specified, clears all the pages.
openhasp.load_pages

Loads new design from pages.jsonl file from full path.

The file must be located in an authorised location defined by allowlist_external_dirs (in case of hassio /config/ is the directory where Home Assistant's configuration.yaml resides, so in case of a subdirectory called openhasp the full path would be e.g. /config/openhasp/pages.jsonl, and you need to add /config/openhasp/ to your allowlist_external_dirs).

Important

The contents of the file are loaded line by line thus "page":X has to be defined for each object.

Unless you clear the page first, the objects will be updated.

Check out the example automations for further information on how to use these services within Home Assistant.

Send jsonl files from Home Assistant~

You can save your jsonl files in Home Assistant too. The custom component can send the contents of the file when the plate connects. To allow read-access to the folder, add these lines to your configuration.yaml:

1
2
3
homeassistant:
  allowlist_external_dirs:
    - "/config/openhasp"

Debugging~

Add these lines to your configuration.yaml configuration and restart Home Assistant:

1
2
3
4
logger:
  default: warning
  logs:
    custom_components.openhasp: debug
Last update: 2022-06-04
Back to top