[Question] MI Band - Sleep after waking up #345

Open
by geripgeri opened 6 years ago · 6 comments
geripgeri commented 6 years ago (Migrated from github.com)
Owner

Hi, when I use my Mi Band with the original software it detects when I fall asleep after the alarm. But the GB stops tracking my sleep.

For example: my alarm woke me up ~05:45 but I only woke up ~09:00
device-2016-06-28-103122

App version: 0.11.0 fw: 1.0.10.11.

Hi, when I use my Mi Band with the original software it detects when I fall asleep after the alarm. But the GB stops tracking my sleep. For example: my alarm woke me up ~05:45 but I only woke up ~09:00 ![device-2016-06-28-103122](https://cloud.githubusercontent.com/assets/5065965/16408981/8c43aa86-3d1b-11e6-9356-49f119c94b69.png) App version: 0.11.0 fw: 1.0.10.11.
Owner

That's interesting. Either Mi Fit does some post processing of the data received from the band or there is some other magic. We currently display the data as is, so that's what the band provides.

That's interesting. Either Mi Fit does some post processing of the data received from the band or there is some other magic. We currently display the data as is, so that's what the band provides.
Owner

It could also be that the newer firmwares added an activity type that the original app interprets as sleep and GB as unknown (hence "normal")?

It could also be that the newer firmwares added an activity type that the original app interprets as sleep and GB as unknown (hence "normal")?
Owner

Right, we need to check that.

Right, we need to check that.
geripgeri commented 6 years ago (Migrated from github.com)
Poster
Owner

As far as I know, the alarm tries to make another attempt if you are lying in bed. I think this is a logical way to detect the sleep with the accelerometer.

Thanks!

As far as I know, the alarm tries to make another attempt if you are lying in bed. I think this is a logical way to detect the sleep with the accelerometer. Thanks!
geripgeri commented 5 years ago (Migrated from github.com)
Poster
Owner

It's kinda weird, as you can see, the device correctly recognised that I was awake for ~2 minutes, and after that I fell asleep.
device-2016-07-03-114757

But unfortunately, as you can see, there are pieces that are not recognised (grey bars & no bars)
I think you can read from the graph that I woke up at ~10:38.

device-2016-07-03-114930

Could it be a FW problem or a SW?
Thanks for the help!

It's kinda weird, as you can see, the device correctly recognised that I was awake for ~2 minutes, and after that I fell asleep. ![device-2016-07-03-114757](https://cloud.githubusercontent.com/assets/5065965/16544818/4c9a04f0-4114-11e6-89c6-3658aaa1c7b1.png) But unfortunately, as you can see, there are pieces that are not recognised (grey bars & no bars) I think you can read from the graph that I woke up at ~10:38. ![device-2016-07-03-114930](https://cloud.githubusercontent.com/assets/5065965/16544817/4c95960e-4114-11e6-8e2b-5ce1b0f9c367.png) Could it be a FW problem or a SW? Thanks for the help!
Owner

At the moment we display the data as is, as received from the band. So all the detected activity kinds are provided by the band. For now, we only recognize deep sleep, light sleep and "not worn". Everything else is regarded as "activity". So maybe these green bars actually represent some different kind of sleep. One would need to check the raw value in the database. I guess we need a way to do that in the app.

@robin13 and @geekpete intend to recognize more activity kinds, so hopefully we will see some improvements in this area (see #341).

At the moment we display the data as is, as received from the band. So all the detected activity kinds are provided by the band. For now, we only recognize deep sleep, light sleep and "not worn". Everything else is regarded as "activity". So maybe these green bars actually represent some different kind of sleep. One would need to check the raw value in the database. I guess we need a way to do that in the app. @robin13 and @geekpete intend to recognize more activity kinds, so hopefully we will see some improvements in this area (see #341).
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.