Objektbaumfehler nach der Migration

[TomekWaw]

Ich habe das seltsame Problem dass nach der Migration von Miniserver Go zu einem Miniserver Gen2 alle Eingaben und Ausgaben im Objektbaum auf der nächsten Seite als vorhanden angezeigt werden, als sie tatsächlich sind.
Hat jemand ein solches Problem festgestellt und weiß, wie man es behebt?

Version in English that I know better:
I have this strange problem that after migrating from a Miniserver Go to a Miniserver Gen2 *all* inputs end outputs in the object tree are displayed as being on the next page, than they actually are.
Has anyone encountered such problem and knows how to fix it?






Another example. It should say Input 1 is on "00 Tests" (where it actually is), but it says its on "01 Tryby" instead:




The other problem I've noticed is that I don't have whole "Installation place" section of my Miniserver Gen2 properties at all (Cabinet name, Raw number Position Number):

[Christian Fenzl]

Do you still have the original (old) config file?
If so, try to reproduce, and if this is reproducible, send your old and new file with description to Loxone to check and fix.

[TomekWaw]

I have the old .proj, but I'm unable to reproduce the replacement process it as I've already sold Miniserver Go.
Yeah you're right probably Loxone is the only capable to fix it in the .proj file

[Christian Fenzl]

Not only in the project File, but also in the migration process of Loxone Config.

[TomekWaw]

So my .proj has been sent to Loxone and it was fixed in one hour!
I'm very satisfied with this kind of support!

And AFAIK Loxone is aware of problems causing this strange issue and is working on it.