Was thinking about too, but what for central heating / boiler control. We might need it on both levels…
yes i agree, usually for this situations, i use the room where it is located, even if it controls the entire home clima…
I have corrected the widget code in my post from today, please try again. I had mixed up two different code bases….
I use it a different way. My room menus only contain radiator and radiator control, doing settings for rooms individually.
Then I have a central hvac menu, wher I can change some general system params like pre flow temp and fresh water temp.
But let‘s discuss this at a later stage. We now should focus on the general functionality…
Great! Once again you lead me on the right way 
Will post an updated version of @hmerk s last code this evening
@hmerk: I would put this in sum (with your actual state of code) at the GitHub repo, ok?
Of course 
It’s fixed and the GitHub Repo is updated.
Just have to check why the widgets now do not appear anymore. Perhaps I changed to much in my test environment
@rubenfuser does the widgets (blinds and lights) still work for you? I can’t get the appear anymore.
This is my config - if it works for you, could you please have a look if something seems to be wrong?
Was my fault, please change line 270 and 293 to vars.room (on github code)
1 Like
Is it possible to get a post referencing or full code of the needed widgets?
This thread is super long yet I am following every post made as it’s very exciting, and very educational seeing this develop. The collaboration is inspiring. I hope all the work going in may one day translate to another built in UI option in OH.
1 Like
Hi @Andrew_Pawelski ,
For sure:
-
The main code is here:
GitHub - Nic0205/OpenPage -
For now we experiment with “older” community widgets:
Lights: [OH3] Main UI Examples - #222 by elektrolubach
(cell_light_card_2)
Blinds: [OH3] Main UI Examples - #22 by Integer
(cell_shutter_card_1)
Then you will have to set the correct model / non-semantic tags like it is explained here:
https://community.openhab.org/t/oh3-main-ui-examples/117928/512
In the End, we will have to have docs for sure - but for now this should help already. Feel free to ask if something goes wrong or if it works to start the docu and make a small pull Request in the GitHub Repo for the Readme.md
Cheers, Nic
@Nic0205 I think I found a solution for the multi item widgets like temp control.
What about not passing an item config to the widget but the equipment group item.
Within the widget, we than can use oh-repeater to retrieve all needed items. We might need some more custom tags, especially to differentiate between setTemp and ambientTemp.
I will give this approach a play over the weekend, reusing the already posted temp_control widget…
That sounds really comfortable. I think using custom tags is a really good option.
Please let me know if - and how I can support you.
1 Like
Maybe there’s some non technical people out that could help with the doco - I could if I get to understand what’s required - I’ve got the main widget and the light card now thanks but can’t work out from the thread what’s needed for tags - I’ve got a room with a non semantic tag of Room and it doesn’t show and a light with a non semantic tag of Light and that doesn’t show anywhere- I don’t want to turn this thread into a support thread for silly problems but maybe a base of instructions might increase peoples input for testing or contributing if there was some time to do it - perhaps it might be time to move to a new thread where things could be pinned to the top etc?
We really should think of splitting the topic to have it‘s own for thi development.
@rlkoshak could you do this please ?
Of course👍
Guys,
I will start a new topic called „main_widget development and testing“ soon.
First post will be a wiki with all prerequisites, hopefully some documentation and always latest code and sub widgets
This can then be edited by anybody.
Second post could be a summary of @Dimitris designs.
WDYT ?
1 Like
Making good progress, nearly finished modifying the light card…
Stay tuned😉
It’s become quite a long set of posts and I’ve not followed along super closely. Can I just go up to the first post on this discussion or has there been some interleaving of topics? It looks like post 229 is the first. What should I call it?
Yes I think post 229 should be correct. Some post between 229 and 546 may belong to different topics but I think to cut at 229 would be the easisets thing.
In hmerks new Topic all relevant informations for out project will be then at post 1 (code) and 2 (wiki)