I started from scratch with OH3 on a Raspberry Pi 4 and build a complete semantic model from my environment. But now I want to start using this in Basic UI so I need a Sitemap.
There is where I get confused !
How can I easy create a sitemap?
Is it correct that I need to do this in a text file?
What is the easiest way to do this and use the same Names, labels, Types, Categories and Semantic classes?
I donāt think basicUI is going to be useful. You have to find posts by rlkoshak showing examples. As far as I know documentation is not complete yet so you have to figure out how to proceed by looking at posts in the forum. I am also in the process of trying to understand how to display the model in the MainUI.
sitemap Sitemap_Haus label="Haus" {
Group icon="house" label="Orte" {
Group icon="cellar" item=Keller label="Keller"
Group icon="groundfloor" label="Erdgeschoss" item=Erdgeschoss
Group icon="firstfloor" label="Obergeschoss" item=Obergeschoss
Group icon="garage" label="Garage" item=Garage
Group icon="garden" label="Garten" item=Garten
Group icon="temperature" label="AuĆen" item=Aussen
}
Group item=Funktionen label="Funktionen" icon="receiver"
}
you do need one for the Android/iOS App, so thereās that!
But as the semantic model is based on groups, you can easily do like Bjƶrn just posted (Thanks @bjoernbrings, saves me doing it! )
As far as I understood so far, the model is a way to organize items in nested groups in a standardized way. In particular, it allows you to add predefined ātagsā to these groups and items so that it is possible (but I have to figure yet how) to have the mainUI build pages for you. These pages are, in principle, viewable also from the browser of a cell phone.
Sitemaps display Groups that you have to explicitly specify and it seems to me that they ignore the tags, but I may be wrong as Iām still learning.
it allows you to add predefined ātagsā to these groups and items so that it is possible (but I have to figure yet how) to have the mainUI build pages for you.
For clarity: the Semantic Model is used by the new MainUI to auto-generate interface pages. It is also used by Habot. It is not used (automatically) by Sitemaps for display in BasicUI - if you want to have a āSemantic Modelā style display in BasicUI, you will have to write the Sitemap yourself: it is not done automatically.
1 and 2. There is a sitemap builder built into MainUI. Go to settings ā Pages ā + and select
āsitemapā as the type of page to create. There are a few things that are not supported such as color and visibility. Alternatively you can write it in a .sitemap file.
The sitemap knows nothing about the semantic model which is wholly encoded using tags and Group membership. However, the sitemap knows all about Items and Groups are Items so some of the semantic model stuff can be used on a sitemap. By default the sitemap will use the label and category set on the Item itās showing. Or you can override those in the sitemap itself.
Are you thinking about Pages which is completely different. And in that case the Overview Pages get automatically populated based on the model and at least for basic stuff itās pretty easy to create custom pages just by clicking around. Only if you want to create custom widgets does it get hard.
And Iām not the one who has examples for those. I donāt know much about building widgets.
No you donāt, unless support is only in the beta Android app. Iāve been using MainUI through the Android app for several weeks now. I donāt even have a sitemap anymore.
You can customize these by editing the page (little pencil icon in top right corner) and by setting the Default X widget metadata on the Items. If I wanted to change how that row for the Garage Door looks in that Family Room card, Iād set it in that Itemās Custom default list widget.
Thatās correct, it doesnāt know anything about tags. But it does support Groups.
This is helping a lot ā¦ Thanks Rich.
just one question;
If i Build the model i can add a ātypeā and there i see āLocationā and āGroupā as a type. But what is the difference in behavior for the model?
Is it possible to define a grid for the location rectangles? I notice you have a high resolution, so, perhaps therefore more such rectangles fit on your screen.
Or is it configurable?
Locations only gets populated if you have equipment in a room. If it is empty or the room just has points then it is not shown in locations. Why can a room not just be a collection of points?
If you have a power switch you only need on/off so a point would do without having to include the tree structure that is equipment.
Also, there is a bug, if you run a copy openhab from a folder not called openhab, lets say openhabcopy, you end up with a folder structure in your openhab folder called openhabcopy that is for the userdata folders (all empty) this is in the same drive partition - It looks like someone has left a hard path in.
This win10 & openhab3. Sorry newbie so donāt know how to report bugs.
I really like the semantic model approach and I build the model representing my home. As I understands this model will be stored in the OH database. It is also very easy to import a items file into the model. But is it also possible to distract or export a kind of item file from the database? It believe that it would be easy to maintain the model via a text file if you have a large model. So extract -> maintain -> import.
I would like to know how you managed to have āEquipmentā and āPropertiesā tab, when you open Family Room? When I open my āGF Bathroomā location, I see only what you may see on screen: