OH3, Shutters & Google assistant

Tags: #<Tag:0x00007f1751449908> #<Tag:0x00007f17514494f8> #<Tag:0x00007f1751448ff8>

Hi there,

I’m struggling to get the right configuration for my ROMA shutters and hope someone can point me in the right direction for what is best practice.

see link for picture:
https://www.roma.eu/

First my setup:
-VMWare
-Ubuntu 18.04 docker host
-OH3 3.1 build 2158 running in docker container
-KNX bus
-Shutter actor Merten
-ROMA shutters

Channel configuration:

  - id: kantoor_google_shutter_hoogte
    channelTypeUID: knx:rollershutter
    label: kantoor google shutter hoogte
    description: ""
    configuration:
      upDown: 1/7/28
      stopMove: 1/7/29
      position: 1/7/4+<1/7/6
  - id: Kantoor_google_shutters_stand
    channelTypeUID: knx:rollershutter
    label: Kantoor google shutters stand
    description: ""
    configuration:
      upDown: 0/0/0
      stopMove: 0/0/0
      position: 5.001:1/7/5+<1/7/7

As you can see for height i can provision the upDown & stopMove addresses and also absolute positions. For the rotation I only have a 5.001 1-byte value (%) available to turn the slats.
I tried to trick this by filling in 0/0/0 as addresses because when left empty the item doesn’t show up in Google Home.

Item configuration:

  "KNXgenericdevice_kantoorgoogleshutterhoogte": {
    "class": "org.openhab.core.items.ManagedItemProvider$PersistedItem",
    "value": {
      "groupNames": [],
      "itemType": "Rollershutter",
      "tags": [
        "Point"
      ],
      "label": "kantoor google shutter hoogte",
      "category": ""
    }
  },
  "KNXgenericdevice_Kantoorgooglelamellenstand": {
    "class": "org.openhab.core.items.ManagedItemProvider$PersistedItem",
    "value": {
      "groupNames": [],
      "itemType": "Rollershutter",
      "tags": [
        "Point"
      ],
      "label": "Kantoor google lamellen stand",
      "category": ""
    }
  }

As you can see I created two rollershutter items in order to control height & slats position separately.

Metadata configuration:

  "ga:KNXgenericdevice_kantoorgoogleshutterhoogte": {
    "class": "org.openhab.core.items.Metadata",
    "value": {
      "key": {
        "segments": [
          "ga",
          "KNXgenericdevice_kantoorgoogleshutterhoogte"
        ],
        "uid": "ga:KNXgenericdevice_kantoorgoogleshutterhoogte"
      },
      "value": "Shutter",
      "configuration": {}
    }
  },
  "ga:KNXgenericdevice_Kantoorgooglelamellenstand": {
    "class": "org.openhab.core.items.Metadata",
    "value": {
      "key": {
        "segments": [
          "ga",
          "KNXgenericdevice_Kantoorgooglelamellenstand"
        ],
        "uid": "ga:KNXgenericdevice_Kantoorgooglelamellenstand"
      },
      "value": "Shutter",
      "configuration": {}
    }
  }

Both items are currently exposed as Shutter item in Google and are also available in my Home application. However not displayed with the shutter icon as i expected and have seen in other implementations.

Now the questions are the following:
-Is there a way to combine height & slat position so that it is exposed as one in Google? I’ve used homebridge in the past and it was able to combine these two into one homekit item able to control both.
-Currently i’m able to say open/close, and i’m able to tell how much MORE close or open (delta value), but i don’t now the command for setting the absolute height position.
-Furthermore i would like to ask how to proceed with the slats position, while i do not have any movement object for that. The only thing i have is a dimmer object.

For the OpenHAB visible part i’m satisfied, i created 2 dimmers in sitemap and that works perfect for me for already 3 years, don’t wont to change that.

The google documentation tells me there is an attribute for this…

So far the combination is not possible.
We have already seen a similar feature request that might be taken under consideration.
E.g. [Feature request] Rollershutter rotation trait · Issue #188 · openhab/openhab-google-assistant · GitHub

For now you can only control shutters how you already described it.

Hi Michael,

Thanks for pointing that out!
I’ll wait patiently until the feature is considered viable.

Meanwhile, i’m wondering what to do about the fact that it only takes delta values instead of absolute values. My slats only accept absolute value…