-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[DEV] AAPS/AAPSClient NSV3-tab getting alot of spam and stops sync (V3+WS API) #2792
Comments
olorinmaia
changed the title
[DEV] AAPS/AAPSClient NSV3-tab getting alot of spam (V3+WS API)
[DEV] AAPS/AAPSClient NSV3-tab getting alot of spam and stops sync (V3+WS API)
Sep 17, 2023
Confirmed. |
also confirmed |
nightscout/cgm-remote-monitor#8100 |
When will be merged? Do you have an idea? |
@bewest is maintaining NS repo now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AAPS/AAPSClient 3.2.0-dev-l
Build: f717d7a-2023.09.16
Not sure what triggered it, but last operation I made was enacting TT from AAPSClient around 15:55. Then checked logs and there is alot of spam in both AAPS/AAPSClient NSV3-tab. As a consequence sync isnt working. at 16:05 spam is still there in both tabs.
Workaround:
Disable v3 API, enable v1 API. Then after sync is fixed, v3 API can be used again.
Screens:
AAPSClient:
AAPS:
Logs AAPS:
AndroidAPS_LOG_1694959105301.log.zip
Logs AAPSClient:
AndroidAPS_LOG_1694959080007.log.zip
From 16:05
AndroidAPS_LOG_1694959585235.log.zip
The text was updated successfully, but these errors were encountered: