That is a good solution, but the problem is not the device time, but how to display the UTC time of the data on a device which is located in a different time zone that UTC/GMT.
I've considered that another option would be to simply set the time of the device to GMT, which works as a solution, but you must admit that it increases the complexity of using the device for the rest of the time you want to use it.
To me, the benefit of doing it my way is that it helps discover/understand the reset triggers for Open, High, and Low, which are not available in the API json.