Make sure timestamp is on all json (http api and mqtt)

[whitedavidp]

The Feature

Sometimes, there is no timestamp in the json data being sent. Here is an except from data sent via mqtt:

{"value": "","raw": "111296.34","pre": "111298.340","error": "Rate too high - Read: 111296.34 - Pre: 111298.34 - Rate: -2.00","rate": "","timestamp": ""}
{"value": "","raw": "111296.35","pre": "111298.340","error": "Rate too high - Read: 111296.35 - Pre: 111298.34 - Rate: -1.99","rate": "","timestamp": ""}
{"value": "111298.34","raw": "1112N8.35","pre": "111298.34","error": "no error","rate": "0.000000","timestamp": "2025-05-26T08:15:00-0700"}
{"value": "","raw": "111288.33","pre": "111298.34","error": "Rate too high - Read: 111288.33 - Pre: 111298.34 - Rate: -10.01","rate": "","timestamp": "2025-05-26T08:15:00-0700"}
{"value": "111298.43","raw": "1112N8.43","pre": "111298.43","error": "no error","rate": "0.009000","timestamp": "2025-05-26T08:25:00-0700"}
{"value": "111298.47","raw": "111298.47","pre": "111298.47","error": "no error","rate": "0.008000","timestamp": "2025-05-26T08:30:00-0700"}
{"value": "","raw": "11123N.54","pre": "111298.47","error": "Rate too high - Read: 111238.54 - Pre: 111298.47 - Rate: -59.93","rate": "","timestamp": "2025-05-26T08:30:00-0700"}
{"value": "111298.66","raw": "1112N8.66","pre": "111298.66","error": "no error","rate": "0.019000","timestamp": "2025-05-26T08:40:00-0700"}
{"value": "111298.55","raw": "1112N8.55","pre": "111298.55","error": "no error","rate": "-0.022000","timestamp": "2025-05-26T08:45:00-0700"}
{"value": "","raw": "1102NN.66","pre": "111298.55","error": "Rate too high - Read: 110298.66 - Pre: 111298.55 - Rate: -999.89","rate": "","timestamp": "2025-05-26T08:45:00-0700"}
{"value": "111298.49","raw": "1112N8.49","pre": "111298.49","error": "no error","rate": "-0.006000","timestamp": "2025-05-26T08:55:00-0700"}
{"value": "","raw": "111238.62","pre": "111298.49","error": "Rate too high - Read: 111238.62 - Pre: 111298.49 - Rate: -59.87","rate": "","timestamp": "2025-05-26T08:55:00-0700"}
{"value": "","raw": "110298.91","pre": "111298.49","error": "Rate too high - Read: 110298.91 - Pre: 111298.49 - Rate: -999.58","rate": "","timestamp": "2025-05-26T08:55:00-0700"}
{"value": "111298.90","raw": "111298.90","pre": "111298.90","error": "no error","rate": "0.027333","timestamp": "2025-05-26T09:10:00-0700"}
{"value": "","raw": "111288.90","pre": "111298.90","error": "Rate too high - Read: 111288.90 - Pre: 111298.90 - Rate: -10.00","rate": "","timestamp": "2025-05-26T09:10:00-0700"}
{"value": "","raw": "111288.90","pre": "111298.90","error": "Rate too high - Read: 111288.90 - Pre: 111298.90 - Rate: -10.00","rate": "","timestamp": "2025-05-26T09:10:00-0700"}

I have seen the same sort of thing delivered via the http api's /json call.

For unknown reasons, the 1st 2 entries lack a timestamp value. I think that value would be helpful always. Thanks

[caco3]

I think this is because the device might not know the NTP time yet.

[whitedavidp]

You may well be correct in this. I am not sure why it may take so long for this to happen. For example, I just now swapped the battery pack powering the ESP32 and the first 2 mqtt messages received both lack timestamps. Oh well, it is good to at least have a possible explanation. Thanks!