Readings taken in the future bork the api
When a device has measurements in the future (as compared to the server's time), calls to /api/<entityId>/station/<deviceId>/measurements?start=all return 502.
Specifically, when the sensor time is set to BST (GMT+1) and the server is set to GMT, then no measurements display.
NB: The incoming timestamps where reported as being GMT times — Z suffix.
It's not clear if just waiting till after the last sensor reading time will clear this problem (I don't want to wait, and that doesn't work if the sensor is still transmitting), but ideally, the server should be agnostic about the date/time range of data that it holds.