Yes, using a certificate for identification to possible yet.
I’d love to have a Map Picker for setting a Location Item though the UI.
In my example, I want to use it to create a widget for creating a list of pre-defined locations. I currently make it work by looking up google maps and typing the coordinates.
Can you please open a feature request issue on the openhab-webui repo?
Done
2 Likes
Someone just sent me this:
Would be cool to have this integrated somehow. Might make some of the notification features others have requested more possible
1 Like
Yes, this is quite nice.
Apple finally decided to play along.
Web Push notifications were implemented in HABot Walkthrough (7/n): Push Notifications back in 2018 (!).
But now that they are universal it might be time to revisit them. For instance they allow your local instance to push notifications securely to your phone, tablet or desktop, without an intermediate service like openHAB Cloud involved. When visiting the main UI you would have an option to receive notifications (like many websites annoyingly try to offer) but if you accept you’ll be notified on your phone or desktop even if you don’t have the UI opened.
2 Likes
I wouldn’t mind having a “select all” button in the inbox for mass delete/ignore/approve. Select all by letter could be nice to have too. I have my ISY connected via MQTT to control my fanlincs and sometimes it fills my inbox with 100+ unnecessary things that I need to check one by one in “select” mode to then ignore because I don’t care about the keypadlincs in OH since there’s nothing really to control there.
in Main UI, in the page editor, when you add a list item to a list and you click to Configure Item and it says Move up or Move down, how about Move to top?
Use case: you have a list with a bunch of list items, when you add another list item it gets added at the bottom and if you want it all the way at the top it is a lot of clicking
Can you please open a feature request/enhancement issue at the openhab-webui repo? Thanks.
1 Like
I wish for better error messages…
2023-03-05 09:46:55.995 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: undefined
How can i find out where it wants to send it to, so that I can either create the item or delete the command that wants to update it?
There are others I came across, but can’t remember.
The message above could say: Attempting to send a state update of item <name> which doesn't exist:
undefined is already the item name. Probably there is an issue when serializing the event before. Can you have a look in the browser at the web information(network information of the requests? My guess would be a request to /events/states/... causes these issues.
Didn’t want to open a normal (support) query; just sayin’ that such messages could be improved on.
BTW: I do not understand how to provide the information you are asking for. Maybe I open a new post… OH3: update of an item which doesn't exist?
These type of messages mostly appear if you are opening a custom widget (in editor mode) and this widget tries to get a state of an item which hasn’t been defined yet.
Error messages are indeed something that can be improved in a number of places and they do continue to be improved over time. However, in this particular case I’m not sure the information exists to provide a better message.
It does. Unfortunately in this case the Item name is undefined. The error message really is
Attempting to send a state update of an item which doesn't exist: <name>
It’s just in this case, whatever is defining the name of the Item for what ever widget is asking for it is failing or was never defined in the first place. And because the Item name is being created on the web page side, all the openHAB server knows is that something requested the state of an Item that doesn’t exist.
You can experiment to see this for yourself. Open a custom widget that takes at least one Item as a property in the Developer Tools → Widgets. When you first open it you’ll see
2023-03-06 07:27:17.153 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: undefined
For some real fun, define a new custom widget with:
uid: test
props:
parameters: []
parameterGroups: []
component: oh-label-item
config:
icon: iconify:carbon:pressure
iconColor: blue
item:
You’ll see it complain about the Item being null. Then you’ll see each letter you type for the item property until you get to the Item’s name.
2023-03-06 07:34:01.197 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: null
2023-03-06 07:34:01.198 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: v
2023-03-06 07:34:01.198 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vW
2023-03-06 07:34:01.198 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWe
2023-03-06 07:34:01.199 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWea
2023-03-06 07:34:01.199 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWeat
2023-03-06 07:34:01.199 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWeath
2023-03-06 07:34:01.200 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWeathe
2023-03-06 07:34:01.200 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWeather
2023-03-06 07:34:01.200 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWeather_
2023-03-06 07:34:01.200 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWeather_T
2023-03-06 07:34:01.201 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWeather_Te
2023-03-06 07:34:01.201 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: vWeather_Tem
1 Like
Hi,
I think it’s too late for 4.0, but here’s my list (maybe for 4.1?):
-
OH UI: Access to items icons (category) and labels from MainUI. What’s the point of defining them with the item definition and then having to re-enter them again when using the item in MainUI (except in oh-repeaters)?
-
OH UI: More documentation and examples. I’m finding it very difficult to tweak or create elements of the UI. Mostly with CSS styling.
-
OH UI Widgets: Beginner friendly use cases. Lots of people must have the same use cases, make it easier for beginners to have a nicer UI. Something like the Main Widget by @hmerk.
-
OH Core: Extendable semantic model and badges. It is very very limited. I know that it adheres to a standard ontology, but it should be extendable at your own risk. And also the badges.
-
Bindings: Google Assistant SDK. Be able to send commands to GA, broadcast messages, and control devices that are supported by GA but not by OH. Just like this: Google Assistant SDK - Home Assistant
-
Bindings: Xbox Xbox - Home Assistant
-
Bindings: +1 for Matter/Thread. I think this should be a top priority for OH.
-
Bindings: Home Assistant integration. HA moves faster than OH and sometimes (like Xbox and GA SDK) there’s already a solution in HA but not still in OH. It would be nice to integrate OH and HA (synchronize items, for example) so you can run both alongside. Home Assistant has a REST API that could be used for this: REST API | Home Assistant Developer Docs
Regards.
1 Like
main_widget is not made by me, I am just supporting the project. When you talk about beginner friendly use cases for UI widget, wht do you have in mind. There are loads of widgets in the marketplace, that’s community work. openHAB itself has just standard widgets and this is unlikely to change.
There are different topics which describe the state and future.
If there is a usable REST API, why not use it with the HTTP Binding ? Our you could link both via MQTT. You see, there are existing solutions…
Thanks for your effort!
When I migrated from OH2.5 to OH3 not long ago I found it very hard to get a nice UI, I had to tweak/create many things. Then I discovered the Main Widget (it isn’t in the marketplace), which looks much nicer than most widgets there, but still had no idea how to get it to work. I’ve used OH form many years, but the change from OH2.5 to OH3 has been very hard. For an OH newcomer this must be impossible.
This is what I had in mind. A beginner will have the typical needs and will want a nice UI. Main Widget is trying to address this, I believe something similar should be part of openHAB.
Happy to hear that. I haven’t seen those topics, I’ll read them.
That’s exactly what I was planning to do, but if there was a binding it would save me (and I suppose many people) a lot of work.
2 Likes
It is in the Marketplace and there are docs in the according topics and in the dev topic.
Ok, than you have to find a volunteer who is going to write that binding, or do it yourself 
It isn’t published, so to find it you have to know that the marketplace is based on this forum, copy and paste the code of all the required widgets and then configure them. I think it’s still too difficult for a beginner, but you are going in the right direction. Keep up the hard work!
Let’s hope a Java dev believes it’s a good idea (it’s what wishlists are for, isn’t it? ). Unfortunately I don’t have enough Java knowledge or time.
1 Like
Yes, this is a wishlist, but i don’t see it as a list for binding demands. This has nothing to do with the openHAB 4 realease.