OH4 Snapshot
Item Type:
-
Number do not work in Main UI but in Basic UI
-
Switch / Dimmer (Slider) works in the Main UI
OH4 Snapshot
Item Type:
Number do not work in Main UI but in Basic UI
Switch / Dimmer (Slider) works in the Main UI
More details are required. An infinity is contained in the words ādo not workā.
Only the default icon is displayed.
Item configs? Screen shots? Widget configs for MainUI? Sitemap?
This is like going to a mechanic and saying your vehicle doesnāt work but failing to even say if itās a car or a boat.
I apologize for this inaccurate question.
With the last two images, Iām not sure if only the standard icon was always displayed
I forgot to show the working example
I never assumed that this forum is a helpdesk, I know that openHAB is an open source project. I also always mentioned in my posts that I use OH4 Snapshot and I am aware that errors can occur.
The important parts in this case are 8, 9, 10, 11 and 13.
I donāt know what Iām looking at here. Is this a widget placed on a layout page? Is it a default widget or a custom widget?
The icon looks a whole lot like the one from BasicUI, does that mean itās working?
You also forgot to show how you actually configured this Item. How you put the Item on the layout page. Semantic tags on the Item? Did you define default widget metadata?
oh-label-card: Only with icon and (iconUseState: true)
Thatās all the same custom icon temp.svg / temp-{number}.svg
I have tried several different items from Basic: only with Label and Icon, Advanced: incl. Semantic Class (Point / Setpoint / ⦠) / Property (ā¦)
Item Type:
Well, I canāt help. Maybe if all the questions asked and information requested were provided I might have an idea. But with this and playing 20 questions when most of the questions asked never even get answered is no fun.
What is still missing information? Itās not like I write about every little bug in the forum. This behavior has been going on for a while and Iāve spent a lot of time looking in many different forums for a way to fix it. Most of them deal with OH2 and a few with OH3. I donāt have the ability to install an OH3 instance at the moment, otherwise I would have already tried and thus ruled it out.
From my side all relevant information is available. I use OH also already half an eternity, admittedly not in the smallest detail and often the standard configuration was sufficient for me. Now I have just again a little more time to deal more intensively with OH.
Thereās no code tab but a description of what properties are set are good. Screen shots are OK I guess. The JSON from the API Explorer would be the absolute best as it includes everything.
You say āoh-label-cardā but that tells me nothing. What is the config? What parameters did you set?
A good hit is if there is a āCodeā tab, everything we need is in there.
You show a screen shot of a tiny part of it, but not the actual sitemap definition.
See above
You may have answered that but I canāt interpret your answer. I donāt know what this means
only with Label and Icon, Advanced: incl. Semantic Class (Point / Setpoint / ⦠) / Property (ā¦)
And show what it is if you did.
In short, we need your actual configurations as they exist in your system. We need the complete configuration for the Item in question and the stuff that the Item touches.
Vague descriptions do not cut it.
If I had made any special settings, I would have mentioned it. I have only created one item via the Web UI it has no connection to any āthingsā. To make it visible in the Location Card I set the Semantic Class to Point. Thatās all and the images show the result.
I would be surprised if every OH instance configures different settings.
oh-label-card: pages/layout⦠Label Card
Iāve told you what I need to diagnose this problem. Since you seem to know better that I do what I need to help, I wish you luck.
Can you or anyone else, install OH4 and create a number item and tell me if the behavior is occurring, that would already rule out if the error is with the OH service or my configuration.
If you would show us the complete item definition, and donāt say nothing special, as you mentioned to have used as custom icon (temp.svg) but not showing the category setings and the widget yaml config, we could.
But as you are not giving this information, we cannot reproduce what you are seeing.
Not really, no. Nobody can attempt to replicate whatās going on because you still havenāt really provided the details. You need to take the time to be as detailed and explicit as possible. You have been quite forthcoming with numerous vague descriptions, but this has to be a ādonāt tell us, show usā kind of situation.
For example, you havenāt even at any point yet, fully articulated the question here. Your initial post contains no question. You are expecting us to assume a lot.
You are not being targeted or attacked here, but the fact of the matter is that if weāre going to be able to work to a solution we have to be working from information not guesses.
I suggest just starting over completely. Assume that you have given us no information at all. Take the time to express your question clearly then give us the supporting evidence. Something doesnāt work? Ok, then tell us exactly what you expect to see, and show us what you see instead. Give us the full rundown of every part. If this involves an item show us the item configuration file or the page in the UI.
If this involves a widget show us the complete config for the widget. You cannot give us too much information. Pile it on and let us sort through, donāt try to filter it yourself.
works:
"Test_Test": {
"class": "org.openhab.core.items.ManagedItemProvider$PersistedItem",
"value": {
"groupNames": [
"Location_Home"
],
"itemType": "Dimmer",
"tags": [
"Point"
],
"label": "Test Test",
"category": "temp"
}
does not work
"Test_Test": {
"class": "org.openhab.core.items.ManagedItemProvider$PersistedItem",
"value": {
"groupNames": [
"Location_Home"
],
"itemType": "Number",
"tags": [
"Point"
],
"label": "Test Test",
"category": "temp"
}
This is what I mean. Itās great a great start that you have included the item JSON, but āworksā vs ādoes not workā gives us nothing.
This forum is about communication. Single words or basic phrases do not communicate anything. If we donāt know what āworksā and what ādoes not workā we cannot, even though we would very much like to, help you find a solution.
Please stop writing minimally, and start actually communicating in detail. Start from the top and tell us the complete story, not the summary.
Alright, Iāll start from the beginning.
I have since noticed that the temperatures icons, although dynamically configured, are only displayed in the default design. Item Setting / Model Settings / Location Card
So, I created a Test item to investigate this behavior. First try an item with type Number, this showed the above behavior, but in the Basic UI / Page Layout site (Label Card with setting iconUseState: true) the dynamic icon was displayed with ItemType: Number.
In the Location Card I had other dynamic icons configured. The ItemType were Switch and Dimmer and these changed the design when the state changed. Then I changed the type of the TestItem to Dimmer and then the icon was also updated.
We appreciate that youāre trying here, but something is just not getting through. There is more in this post than any of the previous ones, but still not really the level of detail weāve been fairly explicit about.
It is clear that you believe that just telling us youāve done something āstandardā is supplying information, but it really isnāt. The problem is that OH is an extremely complex system. It is very easy (and common) even when using the UI to make a mistake when doing something āstandardā. You would be surprised how many confusing problems just come down to a typo in a āstandardā configuration. You are still just telling us and, no offense, but we canāt take your word for it because we know we all make simple, silly mistakes sometimes. We have to see it to know whatās going on.
Here is one instance of how what youāve given us is still lacking in a great deal of information. From one single statement, I can produce at least 6 relevant questions you have yet to address:
null
state?Dynamic icons are not displayed in some of the areas you list (if I understand your shorthand correctly, again, itās not really clear). For example, the Item Detail Pane in the Model Page will not have a dynamic icon; itās just not configured that way. However, it is possible that you have uncovered some part of the system where this isnāt working and if so itās important that we work through it and figure it out.
Referring back to Richās analogy:
Weāve established now that itās a car, thatās progress. But youāre still just telling the mechanic, āWhen I drive my car in the standard way that everyone does sometimes it makes a noise.ā