Settings → Model → Find your Item in the tree or search for it
Click “edit” on the right and you’ll see “Semantic Class” and “Semantic Property” among the list of properties. You can also see what the two tags are in the tree in small print under the Item.
That’s one way to get to it.
You can also go to Settings → Items → Find your Item → Edit so see and change the semantic tags tags.
You can also hit alt-shift-d and search for an pin the Item then click the pencil to go to the Item’s configuration page.
Semantic Class should be “Setpoint” and and Semantic Property should be “Temperature”.
That’s the link between the Channel and the Item. That’s not relevant to the current problem.
For details on the semantic model see Semantic Model | openHAB, and A Deep Dive into the Semantic Model.
Assuming the Insteon binding is implemented like it’s supposed to be, in the furture it will be easier on you to choose “add equipment to model” from the Thing’s Channels page. That should set these semantic tags to reasonable defaults automatically.
No, because it’s a Number:Temperature Item tagged with “Point” as the semantic tag, MainUI is treating it like a sensor instead of a control. By making the Point tag be “Setpoint” it will know it’s an Item to command, not a read only sensor. Interacting with the widget will result in commands to the Item instead of showing the historic values.
Note: Screen shots were fine in this case, but often in order to priovide all the information about something in context, clicking on the “code” tab and pasting in the YAML text you see there to a post will be better for us compared to screen shots. For Items you can find the code tab after clicking “edit” on the Item’s page.
label: Thermostat Target Setpoint
type: Number:Temperature
category: f7:thermometer
groupNames:
- Thermostat
tags:
- Temperature
- Setpoint
Usually there’s a lot more there but this example is a pretty simple sensor.