[dev-j AND 3.2RC1] AAPS or AAPSClient pushing multiple profile database records to NS

[kristinsmotz]

After I updated to dev-j on 16th June, it seems there is a bug where with every loop run (or even more frequently), either AAPS or AAPSClient or both, send a new profile database record.

I remember last year (oct-nov 22 I think) there was a bug creating multiple profile database records with the same StartDate, but now it is creating with a new value in Created AND in StartDate field.

If I pause NSclient on both apps, it stops posting new records, but if I unpause, it's pushing new records again.

I was able to find a script to remove the duplicate profile values for last year's problem, and customize it for this new issue to get rid of records, here you can see example of created vs startdate (valid from) for the records:

Attached logs here in case you can find some useful info there. AndroidAPS_LOG_1689617704715.log.zip

For now it seems a useful workaround to go back to dev-i version, as it's not currently pushing extra profile store records on that version.

Update: I also tested selecting NSClientV3 in config builder in both apps, and updating to dev-j again, but it still sent new profile store records. In NSClientV3 tab the records show with the heading "WS CREATE/UPDATE profile". They also show up in the Profile editor in Nightscout.

[treebearded]

I can verify this, same issue since update from dev-i to 18f01d7b5930252a01bdbda86d56a1af720a0aa0 yesterday. @kristinsmotz Do you have your updated script avaliable? Im sure there are some of us running on dev-j :)

[Alamo04]

This is an old issue and was fixed a long time ago. Can't confirm if it is back, because since NS Dev 15.0.0 I can see only my active profile and unfortunately this NS Version is needed for AAPS Dev. NS Issue done in 03/2023 and no response. But as far I can see in NS Client v3, everything works ok, no spamming profile switches here.

Since I changed to NS Dev 15.0.0 I can't view, change, or clone older profiles. Also can't create a new one. This will become a big problem for parents. Why can you see that with Dev-J and NS 15.0.0 ?

[someguygg]

Since I changed to NS Dev 15.0.0 I can't view, change, or clone older profiles. Also can't create a new one. This will become a big problem for parents. Why can you see that with Dev-J and NS 15.0.0 ?

It doesn't show the editor in chrome. Try edge browser and you can modify NS profiles for now.

[Alamo04]

@someguygg Chrome works fine, also Firefox. Didn't use Edge. This is a problem on NightScout Dev side. ZehnBe fixed that for me. It was a small patch in NightScout code, on server side.

Because I can now see whats happened in profiles, I can't confirm that problem from OP.

[ohjay73]

I'm experiencing the same problem.. each time WS CREATE/UPDATE is triggered in aaps or aapsclient an entry is created in nightscout that takes the lowest alphabetical profile and triggers it as active with the same created and start date. Happens every 3 to 5 minutes and fills your profiles DB in mongo

[kristinsmotz]

This is still a problem in 3.2 RC1, which will be a huge problem for us.

See log from this evening after 22.00CET, our nightscout is already filling up. AndroidAPS_LOG_1693430335851.log.zip

I had to roll back to dev-i for now to avoid this problem, hoping for a quick fix as it is supposed to stop working within a few days.

[ohjay73]

This is an old issue and was fixed a long time ago. Can't confirm if it is back, because since NS Dev 15.0.0 I can see only my active profile and unfortunately this NS Version is needed for AAPS Dev. NS Issue done in 03/2023 and no response. But as far I can see in NS Client v3, everything works ok, no spamming profile switches here.

Since I changed to NS Dev 15.0.0 I can't view, change, or clone older profiles. Also can't create a new one. This will become a big problem for parents. Why can you see that with Dev-J and NS 15.0.0 ?

Remove your authorization in nightscout and then reload the page and enter your code but DONOT check the remember me tickbox. Then check how many profiles you have.. I'm betting that by the date of creation of your profile being the same date as your comment that you are being flooded but the remember me bug is only letting you see the top level profile. Please test and report back

[blochj]

I can confirm the same issue here. This fills entire mongodb database of 512mb within few hours...

[MilosKozak]

something is modifying profile in NS Do following: change api secret (and tokens if used) and restart NS to be sure nothing has write access update api secret on main phone only see the results you can do one profile modification to see if it's properly updated in NS and no update loop started then you can update api secret on another apps (one by one with testing)

[kristinsmotz]

Between the first time I saw this and updating to 3.2RC1 yesterday, I had actually switched nightscout sites and API_SECRET due to kid changing names. So there shouldn't be anything accessing the profile store except AAPS and AAPSClient apps. The problem pops up right after updating to new version (have tried going back and forth between dev-i and newer versions), even if I don't initiate a profile switch or profile edit. In the NSClient tab on AAPS phone it keeps sending new "profile store" batches every 10-ish seconds.

Currently we have the following setup: FSL3 being read by Juggluco, uploading glucose values to nightscout AND sending sideways to AAPS AAPS on kid's phone AAPSClient on my phone, husband's phone (usually force closed due to battery drain), my mother's phone. Only mine is actually used to upload, the others are just reading (technically allowed to upload, but users haven't been trained to do that). Multiple Fitbit Versa of different generations, reading from NS but not uploading.

I will test your suggestions when kid is home from school today.

[kristinsmotz]

OK did some testing. Changed API secret and only updated in Juggluco and AAPS to start. Switched off "Receive profile store" in NSClient preferences - Synchronization Exported settings Updated to 3.2RC1 on AAPS phone Updated to 3.2RC1 on AAPSClient phone, paused NSClient on AAPSClient phone Made a profile edit from AAPS. one new profile db record was added to the mongodb collection. waited a few minutes, no more profile db records were added. Switched on "receive profile store" no more profile records created

Then tried updating API Secret on AAPSClient phone, and unpausing NSClient Immediately saw new profile record being created with a different/older default profile New profile records keep being added every 10-ish seconds with the same older profile

If I pause NSClient on AAPSClient phone, no more profile records are posted, but I don't get updates either, so monitoring kid is impossible. If I switch off "receive profile store" on AAPS phone, no more profile records are posted to database, but I can no longer update profile from parent phone when kid is in school.

It seems to me the issue is AAPSClient. If profile is edited on AAPS phone, and that profile record (newest profile as defaultProfile) is received on AAPSClient phone, AAPSClient responds by pushing a new profile record to db (with the oldest profile in that record as defaultProfile), which is then pushed back to db from AAPS after being received there from nightscout/NSClient.

For now I'll use workaround by keeping "receive profile store" off, and keep using RC1 so we won't lose looping when dev-i expires. This problem did not exist in dev-i, so hopefully that will give you some more direction for troubleshooting.

Attaching recent logs from this testing: AAPS: AAPS 3.2.0-rc1 Build: 65252eb0ba-2023.08.30 Remote: https://github.com/kristinsmotz/AndroidAPS Flavor: fullrelease Nightscout version: 15.0.0 Engineering mode enabled

AndroidAPS_LOG_1693489454129.log.zip

AAPSClient: AAPSClient 3.2.0-rc1 NSCLIENT Build: 65252eb0ba-2023.08.30 Remote: https://github.com/kristinsmotz/AndroidAPS Flavor: aapsclientrelease Nightscout version: 15.0.0

AndroidAPS_LOG_1693489470446.log.zip

[MilosKozak]

@kristinsmotz using NSCv1 or v3?

[kristinsmotz]

V1 since I couldn't get v3 to work with AAPSClient

[treebearded]

Nsc version is probably relevant. I don't have this problem on 3.2rc1 using nscv3 on all phones.

On Thu, 31 Aug 2023, 20:42 kristinsmotz, @.***> wrote:

V1 since I couldn't get v3 to work with AAPSClient

— Reply to this email directly, view it on GitHub https://github.com/nightscout/AndroidAPS/issues/2626#issuecomment-1701576307, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAT2J74RYBSEYGURJ2KILT3XYDLLHANCNFSM6AAAAAA2NKMHJU . You are receiving this because you commented.Message ID: @.***>

[MilosKozak]

resolved in https://github.com/nightscout/AndroidAPS/commit/919c79ebf9cf77b0e0ec486858092764bf8aad62