I’ll go over everything that’s happening here, but apologies if I’ve overexplaining or if you already know all of this
So in the first screenshot
horarioPartida shows a time of
12:00:00 GMT-0300 meaning 12:00 local time (Sao Paulo, as you specified) which is GMT minus 3 hours.
If you’re using Ember Data I assume you’re using the
date transform in your model e.g.
If that’s the case then the transform simply calls
<date>.toISOString() which converts a date object to a string in ISO8601 date format, which is what you see in the second screenshot:
The Z indicates “Zulu time” which is typically GMT/UTC. Since the local timezone is GMT-3, that means the local time of 12:00:00 is 15:00:00 in GMT timezone, so the times are actually the same. The difference is the representation of the time. ISO8601 is very standard format for representing dates, which is why the date transform uses it, and (at least I think) it’s fairly standard for storing them in databases. So it makes sense that you would be sending that format to the server.
So at the end of the day I think everything is probably working how it should and the date being sent is correct. You could verify this by loading the date from the database back into your ember app, which will run it through the other side of the transform, and (should by default, but may require manual specification) show the date in the browser local time the same as when the date was chosen and then saved.