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

Wait wait wait back up, are those widgets inside main ui??

Yes, only stock oh-label-card, oh-image-card used.

1 Like

My “wish” is more an information request. There seems to have been a fair bit of under the hood work with regard to the iOS/Apple Watch apps. Any information on what is coming up for both in the future? Will the Apple Watch ever support anything but sitemaps? Any plans to support sitemaps created through the UI (that it doesn’t seems to be a little confusing for new users as do the correct settings needed for both local and remote access - along with troubleshooting steps when it isn’t working). The addition of interactive notifications though is a game changer. :wink:

Sorry, I don’t know what our iOS devs have in mind…

In an attempt to stear away from the polarising discussions… :slight_smile:

I recently started (at a very slow pace) converting my file based Javascript rules to UI JavaScript rules. And then I noticed that the event object in the UI not only has differently named properties, according to the documentation (JavaScript Scripting - Automation | openHAB vs JavaScript Scripting - Automation | openHAB), it also has significantly less properties.

I’m a simpleton who doesn’t know why that is, but I think it would be nice to have the ‘full option’ when creating UI JavaScript rules…

How about a simple javascript timer where you just type in the command and the device and the amount of time and the action?
example openhabTimer(device, ON, OFF, 10m)

Unless there is one already available that I don’t know about?

Thanks

You mean like this?
https://openhab.github.io/openhab-jruby/main/OpenHAB/DSL/Items/TimedCommand.html

If so, maybe something similar can be added to jsscripting

@hmerk Wow, I am impressed. That is definitely an incentive to start switching to the main UI. It seems that I have put this off for too long as I did not find an access to this as it all seemed to complicated. I kindly appreciate your attempt to show me that it is feasible :+1: .
If you can now also tell me how to include the pressure and temperature graphs then you will make this my best xmas present this year :rofl: - No honestly that was great, I will try my best in the season holidays.

P.S. Can you export this dashboard so that I can import it and learn from your config?

Cheers
Justus!!!

I will send you the page code tomorrow with some additional comments.

For the graphs, I found a non published widget on the marketplace but did not find time to check it.

2 Likes

Yes but not using jruby.
I am flat out using javascript let alone jruby.
I don’t really want to learn another language. Japanese was hard enough. :slightly_smiling_face:

THANK YOU!!!
When I have migrated my dashboard. I will describe it in a tutorial for other non-techies to get an easy entry :+1:

1 Like

I have already though a few times about this and it is on my (very long) list of things I want to have a look at, but is related to how file based and UI based rules differ from the core code perspective.
I think it might be technically challenging to change that, but not impossible.

1 Like

Can you please create an issue on GitHub - openhab/openhab-js: openHAB JavaScript Library for JavaScript Scripting Automation requesting that feature?
Sounds like a good idea that should not get forgotten.

I think I have done it.

Thanks

1 Like

How bout “out of the box” multi-coloured gauges with different severity levels for different colours and a needle on the gauge?

Something like this;
Screenshot from 2024-12-16 19-48-15

This is “borrowed” from home assistant:

type: gauge
entity: sensor.cv_warmtepomp_kwh_current
name: HeatPump-Current
unit: Ampere
min: 0
max: 6
needle: true
severity:

    green: 0.5*
    yellow: 4*
    red: 5*

In the above sample… the gauge runs from 0 - 6
anything below the threshold of 0,5 is blue
anything above 0,5 but below 4 is green
anything above 4 but below 5 is yellow
anything above 5 (but below the max of 6) is red
3 Likes

I’ve moved that somewhat derailed discussion on documentation to an own thread.
From here on please stay on topic, which is about possible OH5 features.

And all: Keep in mind this is a 100% free and volunteer-only driven project.
Please throttle back on your personal attitude when you are requesting anything from those volunteers. When even @rlkoshak finally responds he’s out, something was badly wrong in there. Time also to revisit the forum guidelines and best practices.
Please be a little less demanding and a little more respectful instead with each other and their point of view, not only in X-mas times.
Thank you.

7 Likes

I like this idea, but also support other types of gauge, e.g. a simple bar gauge, adjustable degree gauge (the one shown is a 180° one?), etc.

2 Likes

I would like the option, to define the default theme systemwide in addition of a cookie on a client device.

also the default sitemap settings I would like to have (default) configurable.

I think it’s more appropriate to continue this here (or perhaps a separate topic?)

It would be something that needs to be created / added. As it is now, it doesn’t exist.

I just thought of it because it has the structure that can be easily utilised to achieve it.

Currently the controls in BasicUI / Android App are displayed in a single column. BasicUI added support to split them into 2-3 columns. However, if we have a “FrameGrid”, that works similar to ButtonGrid, except that each grid position is a Frame, which can contain other controls, then we could have something similar to HabPanel.

This is just preliminary idea. Perhaps instead of Framegrid, we could extend Buttongrid to contain other than buttons too, e.g. image, chart, up/down, slider, etc. The difference is Framegrid can contain multiple controls, which might be too cramped, vs Buttongrid in which each cell contains one control.

I guess this will only be displayable on a big screen, not on a phone, although, maybe that FrameGrid could be made “responsive” for narrow screens.
Then add the ability to customise the style to affect background/colours, etc.

@Kim_Andersen would this be close to what you wanted?

I didn’t interpret it that literally, but do you mean to say that this thread is only about concrete “new functionality” and that any other things that might improve OH is forbidden? I read it more generally like “What can we do to make OH 5 better”.

If that’s the case, I certainly don’t have anything to do in this thread, as I think it’s more to be gained from make what already exists “more accessible” than it is from adding new functionality.