It’s probably a stupid question, but I can’t find the answer anywhere.
I’ve created a setpoint temperature icon on my floorplan. It displayes the value perfectly, but I want to be able to change the setpoint by clicking on icon. I can find an example where I get a a popup box with up and down arrows or a slider, but I prefer to write the setpoint temperature directly. How do I do that?
If you can create a popup with a slider ot stepper then you can use any of the widget components:
Text entry can be accomplished by an oh-input.
I have a hard time following you. I’ve looked at the oh-input in the component reference, and I have honestly no clue how to use that in a floorplan marker. The OpenHAB documentation REALLY lack samples of how to actually use the components in a real installation.
I admit that the documentation on the floorplan is a bit sparse - did you see this?
I may write a bit more in the next days with some pictures to guide beginners better.
However, you can try Layout Pages instead which is pretty comprehensively explain - see here:
The floorplan is actually similar only that you create markers on which you can right click and let them open up dialog that includes a widget when you are in run mode (you cannot place widgets on a floorplan.
However, you can create nice floorplans with the fixed layout by putting an SVG as a background behind it.
Let me know if that helps.
I have a hard time seeing how floorplans and layout’s compare. The big advantage of the floorplans is that you have the background image where you can place the items you want. It gives a MUCH better overview. Layouts can best be compared to the old school sitemaps IMHO. And since I’m old school and prefer text file configurations when I have many items and little graphics, like I have here, I do prefer the sitemaps over the layout pages. On top of that, the GUI configuration is just an unnecessary annoying overlay IMHO. It does nothing but irritate me and slow me down. Should the GUI make sense it should be possible to drag and drop the widgets etc. But it’s not. It’s nothing but a web interface for entering text configurations, and that is quite frankly stupid.
Regarding documentation. To be honest. It’s the whole OpenHAB that lacks samples. Not just the floorplans. Like, what’s in the documentation for the widgets, is basically just the same as you see when you try to configure one. Nothing else. It would have been nice with some actual use case examples.
But never the less. I appreciate the help and figured out how to use an input-card on a layout page. That will have to do as a workaround until I figure out how to do the same on a floorplan. Or better move the whole thing to a old school sitemap incl. the clickable map that the floorplan gives us.
That’s actually not true: fixed layouts are perfect for putting a floorplan image into the background of a layout. See my latest additions to the interactive background in the URL I provided above.
Frankly speaking, this is nonsense.
The UI does much more than just let you enter text config.
When adding Widgets, you will just see valid options to configure that particular widget, including possibilities to simply select Items from the model instead of needing to know sometimes cryptic names.
For a few of the config parameters, yes, there is a selection box, but for the majority it’s free text, and most of the parameters doesn’t need to be filled, nor is there any validation on the free text parameters. So IMHO. The web config GUI is nothing but a useless web interface for text based config. It has nothing that justifies a web GUI for configuration like drag and drop. It would be much easier if pages could be configured in text files like the sitemaps. It would also be much easier to document and make examples. That is my opinion whether you like it or not.
If everyone who complained about the documentation took the time to learn just one thing and add that thing themselves, the documentation would be an order of magnitude more comprehensive and stuffed with details. You’re absolutely right, the docs could use more examples. They also could use people willing to volunteer their time to make those examples.
You are, of course, welcome to your opinion, and I’m not going to waste any time trying to change it. However, for the benefit of anyone else who may find this thread in the future, I feel it is worth stating again, that this is uninformed and incorrect. The MainUI contains no end of wizards and dialogs and point and click actions (which I’m assuming, despite claiming they don’t exist, the OP actually used to set up the basics of the floorplan in the first place) and configuration checking that simplify OH administration and UI customization considerably. For more advanced users the ability to extend the GUI configurations via text editing comes with the same pros and cons that advanced usage always does.
The issue here is that any UI that offers simplified control of a complex system must make assumptions about the most common user requirements and actions. There is no way to create a point and click UI that covers all the available configuration options, period. That’s why UIs for complex software such as OH usually have an option for advanced configuration such as the OH text configurations in many of the MainUI areas.
When you want to go beyond the basic settings, particularly in a way that is an uncommon personal preference, it is, frankly, not reasonable to expect the same ease of configuration.
Even if it is not laid out in exactly the pattern that you need for your one case, all the information you require to accomplish what you originally asked about is in the documentation somewhere. It is not actually unreasonable to expect a user that wants more advanced control and features to take the time to do deeper dives into the docs to be able to achieve their goal.
It is also not unreasonable to come to these forums for assistance when you are having trouble finding the correct path through the documentation. Your original request was somewhat lacking details, so I pointed you to the portion of the documentation that it seemed to me you were missing.
Fair enough, I’m happy to expand on the information then, but you should be warned, your advanced requirements will necessitate the use of “stupid”, “annoying”, “irritating”, and “useless” text editing.
All of the floorplan markers rely on OH widget actions to perform whatever interaction you want to configure. To go beyond the basics then, you need to understand actions and their various options. Basic introductions to actions are available in the getting starting tutorials:
and a comprehensive list of action (with example configurations) is available in the oh-button reference page:
In this particular case, the action you are interested in is one of the modal actions (popup, popover, sheer actions). Looking into the the details of those, you will see that they each allow you to open up in some way of your choosing any other page or widget you have already created. So, all you need to do is create a custom widget that includes the input component. Then you configure the floorplan marker to open up that custom widget.
You say you’ve already worked out the input card, but just for completeness, here’s a basic example of the minimum config you would need:
uid: my_input_widget
tags: []
props:
parameters: []
parameterGroups: []
component: oh-input-card
config:
title: Input a value
type: text
sendButton: true
outline: true
item: YouItemNameHere
Once you have saved that custom widget, then you can configure the action in the marker wizard:
After that, clicking on your floorplan marker will result in:
