Semantic Model Locations properties tab modification

I’m starting to customize my semantic model in my OH 3.4.6 system, and adapt it to how I’d like it to work, but need a little help with the Locations tab.
I’d like 1 of 2 possible solutions to get the tab to present information how I’d like it to:

1st solution (preferable) - Get badges and locations card properties data to work and display from subequipment:
image
So I can group things that don’t need direct interaction or is read-only, like sensors, alarms, low battery warnings etc. like the image below
image

But when I add these alarms, and battery status as subequipment to get the view I want when opening a locations card, the location card does not display the badge icons on the card, ie. no temperatures, lights etc.

2nd solution would be to populate the location card properties, by putting items directly under the location, but then I’d very much like to divide the tab into segments for the different properties, like it is shown under the equipment tab:
So is there a way to get the green marked separators in the properties tab of a location card?


Instead of just this long list

You’ve not really shown enough detailed to tell what’s going on here. All I can really say is it should work as you are trying to do it so maybe it’s a matter of choosing the right symtantic tags for the Equipment.

Here is an example of one of my locations and how it looks on the locations card:

As you can see, I have no point Items that are directly under the Location. They are all members of an equipment.

The Location card appears as follows:

As you can see, badgets appear and the Points are separated by the Euqipment they belong to.

Perhaps you can compare the semantic tags you are using compared to the ones I’m using and find a difference.

However, OH 3.4 is quite aold at this point. There have been a number of changes to how the semantic model is displayed with more configueration options having been made availble over the years. Perhaps is works for me because I’m on the latest 4.2 release. Though I’ve not really messed with my semantic model since OH 3.0 so :man_shrugging: .

Indeed my model works like yours - I’m trying to make a structure that has 1 more level - Location → Equipment → Equipment → Point, in this case my properties do not apply to the location card.
To apply what I’m trying to do in your model, would be putting a new equipment “Front Room AC” as a child to “Front room”, and adding “Main Floor Humidifier” to this “Front Room AC” equipment. Then the humidity properties would dissappear, as the points are located within a sub-equipment ie. not part of equipment that is directly a child of a location.

Does that make more sense?

IIRC this doesn’t work in OH 3 but it does work in OH 4.

Just installed OH4 on a spare Pi.
Location → Equipment → Equipment → Point, does not propagate the point values to the location card, unfortunately.

Show your Items and their tags. I know there was work done in OH for to make this work badges from subequipment work. But only specific point and property tags float up to badges.

I just tried it and maybe it doesn’t work. Or maybe there is a regression. I moved my humidifier to be a subequipment of the thermostat and the badgets were lost.

All I can recommend at this point is to file an issue on the webuis repo.

I’ve used 2 items - test_temp which is part of a sub-equipment,
and test_temp_ok which is part of an equipment, like in your model.

The only thing that isn’t in this mock setup are actual channel links to a Thing, but that I’m confident should not make any difference.

It doesn’t. It’s just not working like I thought it should. I pusposefully have a very standardized and shallow semantic model. All Points are in an Equipment and there is only one layer of Equipment.

Whats the procedure if i can see that there is an old issue regarding this?

Do I make a new issue linking the old post, or will somebody get around to it, when they have the time and energy?

You’ve done what can be done. By linking to it here a new post will appear on GitHub saying that the issue has been mentioned on the forum and the maintainers will see that there was some activity on the issue. If you can’t submit a PR yourself that’s about the best you can do.

Ok - thanks for your help . again! :+1: