Hi Charles,
Greeting from Syncfusion support.
By default, date time conversions are occurred in the server side automatically. So, the difference has been occurred in the component value. If we handle the whole component rendering in the server-side, we can avoid this kind of issues.
So, this issue will be resolved after we provide hybrid support for the DateTimePicker component. And this support will be available in the upcoming Volume 2 Main release which is expected to be rolled out by End of June. We appreciate your patience until then.
You can now track the reported issue from the below feedback link,
Regards,
Sevvandhi N