Regarding new features added in each mew major version, there is always a blog post published to announce them. This is of course a must to read.
Here is where custom tags were announced;
For users preferring defining items in file, of course, metadata can be set easily in the same line you define your item.
I didn’t know there was a blog 
I always scroll through the release notes, but most of them are beyond me. Next time, I’ll search for the blog! (Or it might be an idea to put a link to the blog in the release notes.)
Perhaps it could be possible, to indroduce a mechanism, that there is no need to store user and password data in config file based configurations.
I would like to save my openhab configuration at github… but with account data in the files, of course that is no way.
Greetings,
Thomas
Oh!!
Another 
real user management.
It’s a bother to have to go through CLI… sure most people will use the dashboards but would help in homes where development may be done by different people.
Even if I am the sole developer, using Git would have advantages. I would always have an overview of when and which changes were made and could easily roll back if there were any problems. Currently I have to maintain the headers in my files and note the changes there… like 20 years ago.
Actually, it is amazing how many people don’t know about it. There was talk of allowing people to contribute. Make better use of the blog people!!!
OK
THIS is an epic idea!
This is a great example of how a community can work! One user makes a suggestion. Another user comes up with a totally unique and novel way to address it.
Here is another one! I agree that this may not be being made clear enough. I’m sorry, I’ve been here for 6 years and the semantic model totally $hits me. Sorry
I have learned so much from this thread already. Things I never would have thought of. Let’s try to continue with an open mind and allow everyone to express their opinion and desire for future enhancements
Hi all,
it is hard to read through all 263 posts as everybody has his/her own individual wish and perception. But I also like to give my comments as well from my perspective that hopefully give some constructive impulse to the discussion:
)This is my personal feeling and this threat was opened to gather the wishes of the users. These are the three major features where I wish - from a non techie perspective experience - some enhancement to make it for me easier to understand and to use.
I am fully aware that the techies of you are able to explain workarounds how to achieve this but from my perspective it is a lot of technical understanding necessary to follow this.
I must also damit that I still use the old rule sets as I am not familiar with Javascript programming so that you have just an idea of my level of programming knowledge 
That have been my “2 cents” wishes for OH v5 
Cheers
Justus
For the coming 4.3 announcement on the community forum, the message will link to the release notes for detailed content and to the blog post to be informed about the major changes.
Reading the announcement is important, it is very short but can contain very important information.
Reading the blog post is very useful for a normal user to be aware of new major changes. We try to be not too much technical.
Finally reading the release notes is also very important as it provides upgrade instructions, breaking changes, … in addition to the full list of all contributions. This can be a partial reading.
Finding announcements is I believe intuitive.
When you are on the main page of the community forum, the announcements is the first category proposed:
Then when you enter in that category, you find immediately the announcements of each release:
Look at announcement of last version 4.2, it already contained the link to the blog post and to the release notes:
For chronological releases notes, you have this page in GitHub:
https://github.com/openhab/openhab-distro/releases
The blog is also naturally chronological.
The widgets for such an overview do exist on the marketplace and a grid layout page would be best fit. No need to have coding skils to achieve this. I only have to admit that without customising, you will not have this unique look. Perhaps there will be someone willing to contribute some customised widgets…
Yes please. The iOS app lags a fair bit behind the android one I think. It would be very cool if we could expose more things like we do with android (alarm, battery charging state etc).
No idea if possible though.
?? What? Wait, you really really need to go back and recheck this:
Open any item, open the semantic class field, clear it (set to none) open that field again and scroll down through them.
Make a mental note of those clusters of things you were mentioning before.
I’ll give you an example: “blinds”. These are my blinds in the MainUI equipment tab:
How do you do that?
You just need to pick “blinds” in the semantic class of your item. That’s it you are done after pressing save.
Now do it for all thermostats (HVAC) or door / window sensors (pick the door or window as relevant, or simply “sensors” and dump different sensors in it.) and as you’re choosing the semantic class for each item the Equipment tab in mainUI is automatically filled.
That’s it.
You have three tabs:
Location (rooms with equipment and points inside of each.)
Equipment (I think this is what you want, it’s the actual device layer)
Properties (I cluster here things like all temperature sensors. All humidity sensors , etc, independently of the location or equipment.)
MainUI is absolutely fantastic, just play around with it a bit. Things fall into place I promise.
I already get this from the iCloud binding and have a quick glance at all my iOS devices…
Huh? 
didn’t the iCloud binding broke with the 2step auth?? I have to read the documentation again, I must have missed something… thank you 
Apple fixed it and it is working again, at least here 
Hello @hmerk,
I did not take a look at the marketplace for a while. I will give it a try but I am still convinced that the freely adjusting the weather information is not (yet) so flexible as it is in my HABPanel dashboard. I will use the free time over the xmas holidays to give a new try for the Main UI
I gave it a closer look and think, you don’t really need marketplace widgets, just standards.
I will give it a try this evening, should be possible in under one hour
Right, it can already do what nodeRED does, so there’s no real benefit in using that at all.
Hence probably no interest among developers to work on that. Sorry for you.
Not really though. If you have something else that interacts with node red (like home assistant. Or any of the many nodes available) but doesn’t work directly with OpenHAB, then node red is a great option. Just recently I was on a thread about (I think) a dreame vaccum and to integrate with OpenHAB a home assistant instance was setup.
