OH 4.0.4 Items missing in "Pick from Model" dialogue

Setup, Configuration and Use Scripts & Rules
1
  • Platform information:
    • Hardware: RPI3B
    • OS: Raspbian GNU/Linux 11 (bullseye)
    • Java Runtime Environment:
      openjdk version “17.0.9” 2023-10-17
      OpenJDK Runtime Environment (build 17.0.9+9-Raspbian-1deb11u1rpt1)
      OpenJDK Client VM (build 17.0.9+9-Raspbian-1deb11u1rpt1, mixed mode, emulated-client)
    • openHAB version: 4.0.4
    • Browser: Microsoft Edge Version 119.0.2151.97 (Offizielles Build) (64-Bit) and Chrome Version 120.0.6099.63 (Offizieller Build) (64-Bit)
  • Issue of the topic:
    When using the “Pick from Model” dialogue certain Items are missing, even the “Show non-semantic” box is checked.
    Especially this is an issue in blockly, when trying to use getItem, sendCommand or similar blocks, that are using the “Pick from Model” box.
    image
    image1377×838 47.3 KB

However the issue is not only with blockly, but also when using same “Pick from Model” dialogue e.g. for configuring rules trigger or rules condition. For rules trigger/condition I can fallback to the list of all items (instead of choosing “Item Events” directly, first select “Show all” and then selecting an item event).
In blockly I have not find a similar workaround yet.

Within the semantic model page I do see these items, when “Show non-semantic” option is enabled:

image
image321×191 4.59 KB

  • Please post configurations (if applicable):
    • Items configuration related to the issue
{
  "link": "http://xxx/rest/items/EG_Heizung_PresetTemperatur",
  "state": "20 °C",
  "unitSymbol": "°C",
  "metadata": {
    "setpoint": {
      "value": "EG_Heizung_Soll_Temperatur"
    },
    "fenster": {
      "value": "EG_Fenster"
    }
  },
  "editable": true,
  "type": "Number:Temperature",
  "name": "EG_Heizung_PresetTemperatur",
  "label": "Preset Temperatur",
  "category": "temperature",
  "tags": [],
  "groupNames": [
    "EG_Heizung"
  ]
}
  • If logs where generated please post these here using code fences:
    No specific message in the log files.

Any ideas whats wrong here?
Thanks for your help

2

I have not seen this before in my own system, so I think it has to do with your setup.

Mixing the non-semantic items into the semantic groups is almost certainly the problem. I’ve never seen anyone else with this arrangement and it feels to me that it goes against the design philosophy of the model so I’m not surprised that the UI hasn’t been made to handle it.

3

Thanks for the hint, adding semantics to the item will make it available again.

However the reason for mixing semantic and non-semantic items into the group is, that I don’t want all items visible on the auto-generated location and equipment cards, but only some.
Any tip how to control in a better way, what items will be included in these views?

Thanks

4

It’s really just my opinion, but if you don’t want it in the model cards then there’s no reason to even have the item in the equipment group to begin with. Instead of adding semantics to the item to make it fit, I would just take the item out of the model.

There is no benefit to trying to squeeze every last one of your items into the model. If an end user is not going to interact with it (via the semantic cards or HABbot) then my advice is to just leave it as a regular old item.

There is at least one workaround to keep an item that is part of the semantic model from showing up in the cards. You can use the default list item widget metadata and set that to some widget that just renders nothing. The only down side to this is it also means the item won’t show up in any other autogenerated widgets such as group display popups.

5

Thanks for your advice and point of view, that’s already helpful.

Just for context:
I have a device and created a group item with equipment semantic.
I want all properties of the device as a member of the group, as they belong together.
Some properties should not be visible to regular users. Therefore I’m not sure if not adding the item to the group and keep semantic and non -semantic items separated is really the solution or just a workaround.

Based on the example from initial post:
The radiator is a equipment group item and has current temperature and a setpoint as member. Both should be visible for end-users and have semantic properties. The third item is only a proxy item for the setpoint that I don’t want to be visible. Logically, the proxy item still belongs to the radiator and having it as part of the group will help to organize the items and easily find it again. However I don’t need sematic properties on this item.

Most likely I will add some semantic to the item, to be able to configure my rule. Once done I will remove the semantic properties again. Otherwise I will try the approach of not renewing the widget, as I really only need the item within rules.

But as the sematic model itself is showing the non sematic item correctly, the issue is only with the “pick from model” popup dialogue and sensor model page and “pick from model” behave differently I more thought about that this is a bug.