I figured it was about time to re-look at the “write to SQL DB” code, especially for the datetime entries when writing to the database.\u00a0 Long story short, I had SQL input the datetime values at the time of recording, but because the code grabbed a few readings to check against the variances, the data ended up being entering with fairly inaccurate datetime correlations (by hundreds of milliseconds or more).\u00a0\u00a0<\/p>\n\n\n\n
So, I changed the code in a few ways.\u00a0 First, I found out how to get the exact same formatting for the datetime as SQL was using, and used that at the time of actually getting the sensor data (through Python datetime).\u00a0 I also made the Trigger variance checks & database recording, work on 5 readings at a time.\u00a0 If any of the 5 readings trigger a recording, all 5 will be recorded, so in theory, it will record entries before and after the event that triggered it.\u00a0<\/p>\n\n\n\n
That’s it for today.\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"
I figured it was about time to re-look at the “write to SQL DB” code, especially for the datetime entries when writing to the database.\u00a0 Long story short, I had SQL input the datetime values at the time of recording, …<\/p>\n