-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time offset between tsync/tconnect record and NS time parse #47
Comments
Full error text: body { Connect500 Error: Cannot parse 2022-08-12+20:38:37 as a valid ISO-8601 date
|
It appears I'm getting a similar error regarding parsing the date as a valid ISO-8601 date.
|
I'm running into the same issue on Ubuntu 20.04 but it is working on macos. The issue seems to stem from |
Thanks @rstutsman! I figured it had to do with the date filter... will give this a check on my instance sometime today. |
Hey I'm getting a different unknown therapy event error now before I hit the previous iso format time error, can't really verify yet. Will update if I'm able to check it out, hopefully soon. |
|
@ramboozer Ya that’s what I’m seeing as well!
|
It looks like when process.py calls parse_therapy_event in parser/tconnect.py, the type for the first few of my events is 'BG', rather than 'Bolus' or 'CGM', so it throws a UnknownTherapyEventException... not related to this time issue, so I'll open a new issue if it doesnt exist yet... |
Verified it works, will leave the issue open since the PR hasn't been approved... |
@jyaw I ran into the UnknownTherapyEventException for the same reason as you ( |
I created an issue And fixed in issue #52 I think. Thanks for addressing the exception formatting! |
Observed a couple problems with my initial tconnectsync attempts. I'll paste the full content of relevant errors in the next comment. Highlighting 2 items here...
raise ApiException(latest.status_code, "Nightscout last_uploaded_entry response: %s" % latest.text)
tconnectsync.api.common.ApiException: Nightscout last_uploaded_entry response:
Error: Cannot parse 2022-08-12+20:38:37 as a valid ISO-8601 date
The text was updated successfully, but these errors were encountered: