Nothing conceptually wrong with the topology as far as I see. If you’re not causing conflicts by actual concurrent changes, then perhaps there is something else going on you’re not telling us (e.g., the Raspberry actually uses an external disk with NTFS from Linux, which doesn’t behave like a filesystem is expected to, etc).
For me ntfs (3g, no idea about the old and new kernel drivers) on linux works fine for me since forever with syncthing without conflicts. You should enable “ignore permissions”, however I don’t think it should cause conflicts - maybe worth a shot still. Otherwise like with any conflicts, the way to figure out why it happens is to check how exactly the files differ then try to figure out where the change was introduced.
OMG, I have been having precisely this problem for years with an almost identical setup with @pjeremie: an RPi sharing 24/7 a folder with several local devices. On the RPi the folder is stored on an external thumbdrive with NTFS. Modifying a file in any of the other devices generated conflicts on the RPi all the time and they were then propagated to the other devices. Other Windows, Linux and Android devices did not generate conflicts and worked just fine together when RPi was paused. ‘Ignore permissions’ on the RPi seems to have solved this after years of head-scratching. Many thanks @imsodin and @pjeremie
Good to know it solved your issues @Mobster1106 ! On my side I activated the “Ignore permission” on all devices and it is ok now too.
Thanks @imsodin for the reminder (I found that activated it on the past on other syncs )