Wellue data won't import in December

[coldfeet7]

I had a Mohs procedure and have avoided CPAP use for the last two days, not wanting to disturb the stitches. I did, however, wear my O2 ring. Nov 30th imported, but not Dec 1st. (These the last two days  - they don't have Resmed data).

How can I tell if the Dec 1st data is corrupted or if there is some other reason it won't import?  I can see both days in the Viatom PC app (I don't use the phone app) and see the data for the 30th in Oscar (v1.5.1).

[Crimson Nape]

Try going to the Import Viatom/Wellue Data and see if they will import.
- Red

[coldfeet7]

Sorry. I should have been clearer.  I don't use the Android app and only import with the Wellue app and then I go to the folder where the files are placed and import them using the OSCAR Import option. I've always done it that way. It just won't this time. I can see there is a night's worth of data (using the Wellue app). I don't get an error message. It just doesn't load.

I can use troubleshooting options as needed. Just let me know what would be helpful.

[joeblough]

you can turn on Help > Troubleshooting > Show Debug Pane and see what is printed there when you try to import the file.

[coldfeet7]

I edited out the username in the file path.

Two files are dated 20231201....  but I am not sure what the remaining digits represent. One is the 30th's recording and the other the 1st.

66415: Debug: ViatomLoader::Open( "C:/Users/------/O2 Insight Pro/DATA/20072C3923/20231201070505" )
66522: Debug: Daily::Load called for "Thu Nov 30 2023" using "MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0"
66522: Debug: Setting App font in Daily::Load
66522: Debug: Application font starts out as QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
66522: Debug: Application font set to QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
66522: Debug: Application font reads back as QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
66522: Debug: system font is "MS Shell Dlg 2"
66607: Debug: Page change time (in ms): Unload = 0 Load = 85 Other = 0

154699: Debug: ViatomLoader::Open( "C:/Users/-------/O2 Insight Pro/DATA/20072C3923/20231201005158" )
154770: Debug: Daily::Load called for "Thu Nov 30 2023" using "MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0"
154770: Debug: Setting App font in Daily::Load
154770: Debug: Application font starts out as QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
154771: Debug: Application font set to QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
154771: Debug: Application font reads back as QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
154771: Debug: system font is "MS Shell Dlg 2"

264416: Debug: ViatomLoader::Open( "C:/Users/-------/O2 Insight Pro/DATA/20072C3923/20231130035328" )
264657: Debug: Daily::Load called for "Thu Nov 30 2023" using "MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0"
264657: Debug: Setting App font in Daily::Load
264658: Debug: Application font starts out as QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
264658: Debug: Application font set to QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
264658: Debug: Application font reads back as QFont(MS Shell Dlg 2,10,-1,5,50,0,0,0,0,0)
264658: Debug: system font is "MS Shell Dlg 2"
264745: Debug: Page change time (in ms): Unload = 0 Load = 87 Other = 0
154849: Debug: Page change time (in ms): Unload = 0 Load = 78 Other = 0

[Crimson Nape]

There might have been a Wellue software update.   They are notorious for reinventing the data code from one revision to the next.  Please send me one or all of those data files.  I'll take a look to see if there are any new differences.

Here is my Dropbox:  https://www.dropbox.com/request/Z7AvAEAahNyegMHb4Snb

- Red

[coldfeet7]

I've upload the two files. I have had success loading later files in Dec. so it isn't a software update issue (I only load with the PC software and I hadn't updated it). I am guessing now it must be some sort of corruption (though the data displayed in the Viatom software).

I don't need it 'fixed' since later uploads (Dec 5-8th) have worked, but perhaps they are of interest to you for data improvement.

Thanks!

[Crimson Nape]

Using OSCAR v1.5.1 the files, 20231201005158 and 20231201070505, opened without error in the November 30th session. This is the correct location, since both of their times were before noon on 12/01.

- Red

[coldfeet7]

Thanks for mentioning this. I went back and looked at the 30th more closely in OSCAR. In Wellue it shows as two separate days, but they both report the date as Dec 1.

What is bizarre is that the two files I sent you show up on the 30th. You can see there are two sessions in the left pane. They are the duration of a typical night's sleep. I assure you I didn't sleep two 6+ hour stretches separated by a couple of minutes. 

I have noticed sometimes that the Wellue Ring gets time mixed up. I always sync the time in the app (twice a week) but it still does this.

Is this a known Wellue/Viatom issue or do you think my ring is at fault?

[Crimson Nape]

I've seen mentions in other posts of this anomaly on the O2Ring. I'm guessing that trying to package everything small enough to fit around your finger comes with a compromise in the reliability.

- Red