I believe I've found a "feature" in Fosstrak. Not quite yet prepared to stick my neck out & call it a bug, but I could do with some clarification:-)
I've got a transaction event that looks like e.g.:
Note that I'm (deliberately) using GMT, as my RFID readers are set up to ignore any summertime changes.
In Fosstrak, this turns into a set of records such as:
# id, eventTime, eventTimeMs, recordTime, recordTimeMs, eventTimeZoneOffset, parentID, action, bizStep, disposition, readPoint, bizLocation
'655754', '2014-07-13 23:12:13', '1405289533000', '2015-10-28 19:50:24', '1446061823523', '+00:00', NULL, 'ADD', '1', '1', '11', '9'
Note that the eventTimeZoneOffset is still +00:00, but my time now has an hour added onto it!
I imagine there is a setting somewhere in MySQL or Apache or Fosstrak or somewhere that's telling the capture client to turn everything into system time (i.e. BST for events in July 2014), and the capture client doesn't have the necessary code to be able to ignore the setting and believe the data it's being sent!
I think my workaround here will have to be to turn everything into summertime before submitting:-(