Update raw_event.py to use ISO timestamps#131
Conversation
Changed the eventTimestamp to use isoformat, hopefully eliminating the fatal mismatch with nightscout.
|
hi @VTDARKSIM , can you give some additional context for what you're observing? |
|
Of course!
The timestamps appear to originate in raw_event.py and have a '+' rather than a 'T' like ISO-8601 requires. It seems like the errors occur in a number of downstream modules (query.js, treatments.js, index.js, route.js, etc.) when trying to parse them, so it may be why I'm seeing the 'cannot parse' errors and an absence of data. The change seems to be working on my end, but of course review and do what you need to do. Either way, I appreciate all you've done - this is awesome! |
|
I think |
|
I'm not getting the errors anymore on my local edited copy, but perhaps its a coincidence. In any event, it's working and I'm happy. |
Changed the eventTimestamp to use isoformat, hopefully eliminating the fatal mismatch with nightscout.