@matigo Certainly. I had the same problem on Broadsword, so I set Moment to use the logged in user's timezone instead of the device timezone. Could be wrong, of course, but then it is setting to what the user sets, and doesn't need the user's device info.