Ok, thanks for the clarification.
What is the best way to migrate to knx2?
My problem, i have no time to do all in one day. I think i will have to split the work. But i can not use knx1 and knx2 binding together to test the new config-files.
So i think the best would be: write all new files - make a snapshot of OH-VM (my oh runs on esxi) and then change the files and install the new binding. If there are too many errors, go back to previous snapshot and rework the config-files…
Or completely clone the OH virtual machine - use one for knx1 and one for knx2. Is this possible? Will this work, if i only start/stop the two identical virtual clones? So i could go back to knx1 when i have to stop the work and can start again the next day?