OK, I’ worked this out from scratch again, so here is the guide for setting it up in MainUI for OH3:
First create the virtual KNX thing, here is the YAML:
UID: knx:device:MDTSecureGateway:VirtualDateTimeWrapper
label: KNX Virtual DateTime Wrapper
thingTypeUID: knx:device
configuration:
pingInterval: 600
readInterval: 0
fetch: false
bridgeUID: knx:ip:MDTSecureGateway
location: UV
channels:
- id: knxDate
channelTypeUID: knx:datetime-control
label: knxDate
description: null
configuration:
ga: 11.001:6/0/4
- id: knxTime
channelTypeUID: knx:datetime-control
label: knxTime
description: null
configuration:
ga: 10.001:6/0/1
- id: knxDateTime
channelTypeUID: knx:datetime-control
label: knxDateAndTime
description: null
configuration:
ga: 19.001:6/0/3
- id: knxNight
channelTypeUID: knx:switch-control
label: Night Switch
description: null
configuration:
ga: 6/0/2
Remember to set your correct bridge ID and to adjust the knx group addresses (6/0/x) to something you are using in ETS!
After this create an item for e.g. channel knxDateTime like this:
Do not forget to set the Type to DateTime.
Create the NTP Thing, code as follows, with refresh interval of 10 seconds (whatever pleases you, but e.g. 600 should be enough):
UID: ntp:ntp:local
label: Lokale Zeit
thingTypeUID: ntp:ntp
configuration:
timeZone: Europe/Berlin
hostname: time.windows.com
serverPort: 123
refreshInterval: 10
refreshNtp: 30
Link the dateTime Channel to the item you just created:
No need for the “follow” profile.
Now the DateTime data appears on the knx bus every 10 seconds, check with the group address monitor:
Hope this clarifies things.
Enjoy