My ViHealth Android app just received a major update to v2.74.39. When I opened the app for the first time after the update, I was asked if I wanted to delete all my prior O2 ring data or upload it to my ViHealth account. So, I chose to upload the prior data.
Last night's O2 ring data then synced to the app. But no new binary files were created under
Code:
com.viatom.vihealth\files
Instead, last night's binaries were created under
Code:
com.viatom.vihealth\files\20\host
(without the "O2Ring_" prefix in the filename and with a DAT extension)
OSCAR 1.4.0 doesn't recognize this file naming format for Wellue data. So, it wouldn't import last night's binaries. But renaming these binaries to the naming convention ViHealth used before the update still allows OSCAR import (thus, e.g., "20221216220109.dat" should become "O2Ring_20221216220109").
If you're on Windows and have a directory where you only store ViHealth binaries, you can open that directory in a command prompt and run the following command to convert the all files with the new name format into naming scheme OSCAR 1.4.0 will recognize and allow to be imported.
Code:
forfiles /m *.dat /c "cmd /c rename @file O2Ring_@fname"
Note that this command will give you a "duplicate file name exists, or the file cannot be found" error if you have files already in the folder with the "O2Ring_" naming convention (e.g., from uploads you might have done before the ViHealth app update). And doubtless, the OSCAR developers will have an update out at some point that will allow OSCAR to recognize the new ViHealth naming convention.