In truth, KNX xxx-control type channels are “special”, and work in reverse.
Messages from KNX are passed to openHAB as commands, Item state changes are passed to KNX.
It’s meant for use with e.g. glass control panel not an actuator, and mimics the way a GUI works.
Does it, may we see your events.log of that update?
There is scope here for you to post units that the binding won’t like.
Thank you to everyone who chipped in (here and sharing their solutions in other threads)
.
I managed to get this to work by setting the openweather source item to Number:Dimensionless.
Don’t do that, you are storing up trouble. Number:Dimensionless is not “just a number”, it is a ratio like 95% or 15dB or 3-to-1. It is a Quantity, with units. That ‘1’ ratio has a magic property of being invisible, but this is not a regular number.
Openweather wants you to use a Number:Temperature, with units, so do that.
As you have for some reason changed your KNX channel type, you’ll need to send a command not a postUpdate.
Beware that small Thing edits may not be acted on until the next binding restart.
So to adapt your original rule -
var KNX_AT = (OneCallAPIWeatherandForecast_Aussentemperatur.state as QuantityType<Temperature>).toUnit("°C").toBigDecimal
KNXDeviceopenHAB_AussentemperaturtoKNX.sendCommand(KNX_AT)
If you have an existing outdoor temperature item, then just set up an knx channel in an “empty” knx thing as a number-control and link it to the existing item via follow profile.