Timestamp parsing logic change. Several models when connected initially store invalid timestamp in the packet (invalid means that 0th month and 0th day). These packets caused parsing error resulting in new attempts from device to deliver it. Such timestamps now don't stored at all (filtered out), which results in the message being stored with the timestamp = server.timestamp
