You can see several “9 hours ago” and “10 hours ago” and dates. The hour values will increase until they reach 24 and then a new build will be done. So you need to wait for another 15 hours at least before the fix is in.
Looks indeed like it is related to the failed meridian flip:
[2018-08-23T00:20:29.094 CEST INFO ][ org.kde.kstars.indi] - EQMod Mount : "[ERROR] Error: Communication failed -> tty write failed, check connection: Error: unrecognized error code "
[2018-08-23T00:20:29.098 CEST INFO ][ org.kde.kstars.indi] - EQMod Mount : "[ERROR] Error when disconnecting mount -> tty write failed, check connection: Error: unrecognized error code "
EDIT sorry I was wrong. Ekos successfully reconnects to the mount and then alignment succeeds:
[2018-08-23T00:29:46.748 CEST INFO ][ org.kde.kstars.ekos.align] - "Solution coordinates: RA (20h 17m 09s) DEC (50° 07' 58\") Telescope Coordinates: RA (20h 17m 08s) DEC (50° 07' 46\")"
[2018-08-23T00:29:46.750 CEST INFO ][ org.kde.kstars.ekos.align] - "Target is within 0° 00' 22\" degrees of solution coordinates."
[2018-08-23T00:29:46.757 CEST INFO ][ org.kde.kstars.ekos.align] - "Target is within acceptable range. Astrometric solver is successful."
Silly question but are you sure that the offset was created after the meridian flip? What happens if you stack only the images from before the flip? Or maybe easier, can you check the center of FOV of all images and identify which ones are where you expect them and which ones are off?
The mount was not responsive after the meridian flip. Maybe the flip touched the cable and it got disconnected? I also just updated EQMod driver to retry connection after a tty failure, but it's not yet tested.