Ideas and Discussion: What Features Do You Want in openHAB 5.0?

When I am implementing a new feature to my openhab system, I need the following resources which are accessible through the folowing menus:

  • Settings → Rules
  • Developer Tools → Widgets
  • Settings → Pages

Very often I have several browser windows open as I need simultaneous access to different resources out of the above three.

I can’t even count how many times I needed to leave Settings menu go up to the main menu and start going down the route to Widgets.

I am assuming that some more users experience the same. So I’d like to ask to move the widget menu to the settings section.
I know, creating new widgets has nothing to do with “Settings” - I absolutely agree. But so is developing new Rules or creating new pages.
I just see that they all share the same sort of complexity and belong very tightly to each other if you add individual features to openhab.

3 Likes

yes, I’ve always thought that widgets should be located in settings, next to Pages

Sometimes I do not even remember if I added a custom control directly to a page or created a separate widget. And when I want to change something, for sure I always search at the wrong place :slight_smile:

If I may add an additional idea: How about adding a menu item to the menu shown below which brings you directly to the widget yaml code in a separate window?

sendcommandifdifferent for DSL would be nice to have.

It would be great if the developer sidebar could do a search also in widget code and then it could be possible to pin the widget in the sidebar.

Then you could pin the widget, page and rule in developer sidebar and jump between them without the need to go to settings menu at all.

3 Likes

this is a great idea

1 Like

Agreed, am also thinking about setting up OpenHab in our RV - and of course integrating the two systems so I can monitor one from the other…

On UI rules the but only if section of the rule are AND conditions.
It would be great to have a drop down to select AND/OR in the but only if section.

This gets complicated. A simple drop down won’t support compound conditions. For example

A AND (C OR D)

is not the same as

A AND C OR D

Something more would need to be added to suppor something like that.

But in the mean time, an inline script can handle anything more complciated than a series of AND conditions. If using Blockly, just put a logic block not plugged into anything in the inline script.

image

4 Likes