openHAB 4.0 wishlist

[rlkoshak (Rich Koshak)]

Now you’ve done it!

OK, to make this thread a little more usable I’d like to make a suggestion.

1. @joriskofman, take it upon yourself to keep a running list of all the wishes posted in the original post, maybe with a count of how many times it’s mentioned or something.

2. We can turn this into a wiki and everyone can post to the OP themselves. Someone will still have to scan the replies for stuff because some people will simply refuse to edit a wiki post.

@binderth

I’m now left to change a bazilian of items to their correct parent

You should be able to go to the Group and add the Item from there all in one go.

@Oggerschummer

A simple way to set a bindings logging into e.g. DEBUG mode from the UI. This way we could avoid explaining how to do this in the console over and over again.

The REST API part of this is already implemented. We are only missing the UI updates.

@Mclupo

• You are in the items list and scroll miles down to an item or start typing in the name.
• you make the modifications to the item and as soon as you press „store“ it jumps back to the top of the items list.
• so you continue with point 1)

I’d call this a bug. Please file an issue on this one.

@binderth and @mstormi, this thread is going to really long with lots of stuff. I’d like to keep it on topic and especially avoid defending the status quo. It’s a brain storming exercise. When/if any of these ideas get submitted as issues, we can defend the current approach there. I’m already worried this thread is going to become a mess, arguing about some idea is only going to make it worse.

---

Rich’s wish list (there is some overlap with what’ already been mentioned):

• Drag and drop in the Semantic Model UI to more easily move Points and Equipment around in the model.

• I’ll second @splatch’s idea to get support in the UI for custom metadata (note, see UoM default units and consequences for a relevant discussion on units and persistence). Even if we can just get the namespaces of the metadata already applied to that Item it would be a boon.

• I know it’s hard, but a “Code” tab for Items with a YAML representation of the Item’s JSON. Even if it doesn’t include the links and metadata it’d be useful.

• Full text search; I want to search for an Item name (for example) and see which rules, widgets, links, etc. it’s used in by name, even inside the script actions and conditions. Maybe this should be part of the developer sidebar. Finding all the Items with a given metadata would be another use case.

• All lists should be sorted alphabetically based on the most prominent element. Things and rules are already handled well. Items should be sorted based on the label. (This one’s a quibble).

• Ability to post a “collection” of rule templates and ui widgets to the Marketplace. For example, I have three separate posts for each of my MQTT Event Bus rule templates. It would make more sense to have one post with the three rule templates. Another case is the Scene Control which includes both multiple rule templates but also a UI widget. It would be easier to manage if we could include them all in one comprehensive post to the Marketplace.

• Ability to create and deploy a rule template locally. Right now to install and test a rule template one must post it to the Marketplace. This greatly slows down the edit/test loop when creating or enhancing a rule template.

• UI support for rule templates similar to UI Widgets.

• Ability to package library functions in a rule template.

• Support for a functional language for rules (Clojure perhaps) strictly because I love to code in such languages.

• GraalVM Python support because a lot of Jython users are in danger of losing support.

• Honeywell Residio add-on.

• Subaru Starlink add-on

• Wyze camera support

• ability to copy uids (e.g. Item name) from pinned objects in the developer sidebar.

If wishes were fishes we’d all swim in riches.