Of course, though the answer may be “we don’t know” or “not yet” or “maybe.”
One big change between OH 2.5 and OH 3 is the removal of Joda DateTime. It has been replaced with Java’s native Time classes, in particular ZonedDateTime. Unfortunately it’s not 100% compatible with Joda, most notably missing all of the withTimeAt methods. An equivalent for withTimeAtStartOfDay would be now.withHour(0).withMinute(0).withSecond(0).
Text based rules can only be edited from the text file it’s defined in. There is no plan to edit .rules files from the UI. Only rules stored in the JSONDB can be edited through the UI. However, you can enable or disable rules through the UI no matter where they are defined. But I don’t think disabling a rule from a source file will remain disabled when the file is reloaded. I never tired that. NOTE: This is true for Rules DSL, Jython, JavaScript, and Groovy.
It’s becoming more of personal preference. Many of the things that made PaperUI unusable have been addressed in the MainUI and as I’ve mentioned in other places, things tend to work really well when they run out of the JSONDB. But the fact remains, if you define it in text files you can only edit it in text files. You can see them in the UI but it’ll be read only.
It’s used by HABot which is a chat bot type UI for interacting with OH. It lets you add the metadata where you can ask it stuff like “Are the lights in Nate’s bedroom ON?” It also makes it easier to build Pages as you can populate a page from the model (e.g. you can create a page for Nate’s Room and populate it from the model and all the devices in Nate’s room will be automatically added to the page.
If neither is something you plan on doing anytime soon you can ignore the model. But also, as I’ve said in another thread, building the model makes the search function on the Items page even more useful as you can search using concepts from the model as well.
No.
Add it as a member to the parent Location Group.
Building a sitemap from the MainUI is in work and not yet completed I believe. To get to BasicUI when you first log in there is a little icon in the upper right corner. Click it and it will let you select one of the other UIs that are installed.
They are an alternative UI and they are really super powerful. I don’t know the future plans for when/if HABPanel or BasicUI will become legacy (not necessarily deprecated but there wont be too much continued development). If you like Sitemaps or HABPanel you don’t need to mess with Pages. But I’ve been playing with them and I find them a little bit easier to customize and build exactly what I want than HABPanel but far far more complex than Sitemaps. Some of the big additions though include:
- several new concepts to represent data
- ability to have more complex control over presentation (e.g. only show certain Items based on who is logged in, change the representation of an Item based on other Items, combine multiple Items into one widget)
- ability to enter text and date times
And I’ve just scratched the surface. I’ve never been a huge fan of HABPanel but I’m really liking what I see with Pages.
They are the concepts that describe the parts of a Page. See Building Pages in the OH3 UI: documentation draft (1/3) for the start of the documentation on it.
Absolutely not. They will help us understand where the pain points are and improve the first draft of the docs. And as you learn how to use this new stuff, please consider contributing to the docs. All the pages I linked to are wikis.