There is a thread on sending NTP time to knx.
You can do this in a similar way.
The key to success is using a knx control-channel in a thing and using the “follow” profile for an item.
It seems the “AND: Its only a Number, not an Number:temperature item” is a crucial hint here.
Yesterday I faced the same issue and spent like half of the evening trying to figure out why it’s not working.
Even if this thread is “solved” I’ll allow myself to re-ignite it with question: is it OH’s design decision to behave like this, ie. to disallow Number channels to follow Number:xxx items? If so, shouldn’t there be at least some trace of this “incompatiblity” in logs? Otherwise it’s very confusing and annoying trying to figure out why such link doesn’t work.
In my case the Item was automattically generated from an OpenWheatherMap channel as Number:temperature and it’s rather obvious that people might want to propage such values to KNX bus.
From user’s point, whether the type is Number or Number:temperate mainly affects the way it’s presented (the latter adds the unit). The value itself is still compatible. Is there any specific reason for OH to ignore such links? The value itself should be still compatible.
No, its a binding author’s decision. In this case the KNX binding was created before OH even had Quantity type Items (with units) and simply doesn’t handle them. Yet.
Volunteer binding maintainers always welcome.