urbandroid-team / sleepasfitbit Goto Github PK

There are some differences in the UI, but the backend can stay the same...

So not sure if we can use a git submodule, or probably we can even share the whole codebase, but use two different uiManager and stylesheet files.

The only problem that would happen is having a way to dynamically set the buildTargets, and not sure how we can do it.

Sometimes it can happen that the companion keeps waking up even after sleep tracking session stops.
We can prevent this by checking whether the FitbitHTTPserver is running on the phone, and if not, terminating the wakeUp mode.

We need to make sure wakeup mode is properly enabled when sleep tracking starts. For example by starting it when we get "start" message from the watch?

App should indicate that sleep tracking needs to be started in the phone app, when it's not yet connected

Find a nice color combination of background/text/icons

the corner buttons (right top and bottom corners) are currently not connected to the physical buttons. They should be, by default, but there's a bug in Fitbit which causes them to not be connected to the physical buttons if the button elements are nested deeper in the svg hierarchy.

along with the launchReason, the message should check whether app runs

There should be an indication in messages about which version of the app is sending them.
Those messages should be generated in the companion to not clog up bluetooth

Probably the issue isn't actually of this app, but of fitbit app itself, however sometimes the recording stops during the night, while the watchapp seems to still work and so the companion according to the logs (sleep-logs.json), but Sleep as Android doesn't receive the data for sure.

According to a forum report it seems that this is due to a latest update of fitbit app though: https://forum.urbandroid.org/t/fitbit-ionic-versa-beta-integration/3035/355

right now the app is waiting for the phone to confirm tracking stop, while no feedback about that is provided to the user

The currently available app is not compatible for the new Versa 2 devices.
Is there a plan for implementing this?

I am available for testing, but would need support with getting the dev environment up and running.

We need to be swift with sending messages from the watch when the wakeUp event on the companion occurs.

There should be some handshake between app and phone if the watch app is manually started for the second time, while sleep tracking on the phone is already running.

stop resending when the peerSocket is closed
start resending when it's open