could you additionally describe the values and dpt which you expect on 0/5/70 and 0/4/70? 0/5/70 receives commands, e.g., the target temperature, while 0/5/70 receives the status from the actuator, right? Why do you send a read request on the first address using “<”?
Did you try to remove the label from the sitemap and use the default one from the items definition? And also add some minVal / maxVal / step values?
Unfortunately, I’m not familiar with the KNX log information, but it seems that there is an issue with the addresses? I’m sorry but I’m just guessing as I’m not that familiar with the OH2 architecture yet.
I’m not sure whether it’s a knx binding issue or an ui issue. As I mentioned, exactly that items/sitemap definition works fine in OH1. As you can see in the events.log the value is received from knx bus and the item value is updated. But the setpoints label is never updated with the value.
I think DPT 9.001 is correct to hold temperature values. The group address 0/4/70 is used to set the target temperature where on 0/5/70 I can read the current target temperature. This is why I read with <0/5/70.
I also tried to remove the label from the sitemap without success.
I also tried to add the parameters as @robin.muellerbady mentioned without success.
same thing here. Using latest openHAB 2.2 openhabianpi.
I can see in the console with smarthome:items list … that the Items have the correct state, however in none of the UIs it is rendered correctly. After refresh most of the time the data is rendered, but not always. A restart of the openhab2 service did not help.
Edit: not quite true, using the openHAB App on an iPad, the refresh works fine. So I assume the problem lies in the Webkit emulation?